Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on December 31, 2014, 07:33:43 AM
-
First release candidate of piCore 6.0 is available.
Download link:
http://repo.tinycorelinux.net/6.x/armv6/release_candidates/
This is a beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Since this is an beta cut, although the team has worked through several preview cuts, we ask that only experienced users test. This cut is not for production use. The features in any beta may change before a public release candidate is available.
Note that the fltk library has been updated to 1.3.3 to enable unicode. fltk-1.1 and 1.3 can be installed at the same time, and old apps using 1.1 will continue to work.
We appreciate testing and feedback.
Changelog for 6.0 rc1:
* first partion, mmcblk0p1 size reduced
* serial terminal restarts with login after exit
* safe overclocking enabled by deafult, startup time is 20% less now
* default cpufreq governor changed to performance
* cpufreq governor set to ondemand when startup finished
* shell history deleted
Changelog for 6.0 Beta355:
* kernel updated to 3.12.35
Changelog for 6.0 Beta200:
* kernel updated to 3.14.23
Changelog for 6.0 Beta100:
* kernel updated to 3.18.0
Changelog for 6.0 Beta2:
* kernel updated to 3.17.4
* RPi firmware updated to December 3 release
* serial terminal now started by default
* preinstalled components updated
Changelog for 6.0 Beta1:
* kernel updated to 3.17.3
* glibc updated to 2.20
* gcc updated to 4.9.2
* e2fsprogs base libs/apps updated to 1.42.12
* util-linux base libs/apps updated to 2.25.2
-
Additional notes:
- X version will follow in next days
- if you are using the SSH image, make a backup (sudo filetool.sh -b) to save your SSH keys generated at first use to get new keys at every boot
- If you are using images with preinstalled extensions, do not forget to resize mmcblk0p2 partion, as described in README!
Request:
Please test your system removing waitusb=5 option in cmdline.txt It was necessary in 5.x to get mmcblk0p2 recognized and for safety left in rc1 but not needed at least in my test enveronment. Let me know your result.
-
Installed my squeezelite radio with WiFi, and everything is working, even after removing "waitusb = 5".
It's very handy the SSH key files are allready in teh filetools.lst file, thanks!
One thing I noticed: If I change the volume through alsamixer, the setting isn't saved.
Do I have to add some config file to filetools.lst? I will investigate further.
Have a great 2015! :)
-
This version is working with my A+, wifi, and w1 temp sensor. Removing waitusb=5 did not cause any problems. 40 seconds from power on until I receive a text on my phone from the rpi with the temperature.
Also, I was reading on cmdline.txt and it was mentioned that initrd= parameter is not required. I removed initrd=0x00a00000,3730404 as well as the waitusb=5 and it still boots fine. Is there a reason to leave the initrd= in cmdline.txt?
-
Thanks for trying.
Also, I was reading on cmdline.txt and it was mentioned that initrd= parameter is not required. I removed initrd=0x00a00000,3730404 as well as the waitusb=5 and it still boots fine. Is there a reason to leave the initrd= in cmdline.txt?
Thanks for mentioning. It is a heritage from previos versions. I can confirm rc1 boots without this parameter. BTW, where did you read it?
-
Thanks for mentioning. It is a heritage from previos versions. I can confirm rc1 boots without this parameter. BTW, where did you read it?
Hi bmarkus, I tried to find the page so I could include the reference in my post but I wasn't able to find it again, even in my browser history. I was trying to find out if you can have multiple initramfs files like you can with a pxe boot and while searching for that I noted the comment about not needing the initrd= line.
There is one reference here but he doesn't mention where he found the info:
update: Adding initrd=0x00f00000 to /boot/cmdline.txt does not appear to be necessary (My Pi boots file to an LVM root without it). The initramfs entry in /boot/config.txt is required, however.
http://johnlane.ie/boot-a-raspberry-pi-with-an-lvm-root-partition.html (http://johnlane.ie/boot-a-raspberry-pi-with-an-lvm-root-partition.html)
I'll see if I can find a more official reference.
-
Please test your system removing waitusb=5 option in cmdline.txt It was necessary in 5.x to get mmcblk0p2 recognized and for safety left in rc1 but not needed at least in my test enveronment. Let me know your result.
Worked fine.
Are the vnc server and clients on the 6.0 repo?
-
sodface@
Thanks for the info. I haven't seen it mentioned before and now searching the net I found in every docs saying it is needed in command line. However it boots up fine without which makes life a bit easier and cleaner.
Paul_123@
Thanks!
-
Hi bmarkus, I've been trying to understand the initrd= and why it works without it and maybe this explains it?
http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532 (http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532)
Is it that earlier versions of start.elf did not set ATAG_INITRD2 which is why the initrd= entry was needed in cmdline.txt but then start.elf was updated to set ATAG_INITRD2 making the initrd entry in cmdline.txt redundant?
-
I've removed the initrd= entry too, and everything is still working.
-
Do you have the X version ready? I can get X to start, but no menu....I cannot seem to find the complete list of extensions needed.
Not sure if you saw my note.....can you put the vnc client and server in the v6.x repo
-
Hi Paul,
X version is work in progress, first I wanted to finish base. Will make it soon as well as adding vnc.
Regards... Béla
-
X version uploaded. waitusb and initrd settings now removed from cmdline.txt otherwise base is the same.
-
hi bmarkus,
The README file needs a couple of minor updates.
1. piCore-5.x -> piCore-6.x (4 times)
2. The heading "Core Book" should be preceded with 2 blank lines not 1.
regards
Greg
-
Thanks, fixed.
-
Hi Gerrelt,
One thing I noticed: If I change the volume through alsamixer, the setting isn't saved.
Do I have to add some config file to filetools.lst? I will investigate further.
The backup and restore of the ALSA state need to be done this way:
sudo alsactl store
This saves the complete setting of the ALSA module including the volumes of all the sound cards in the /var/lib/alsa directory.
Than add this line to the /opt/.filetool.lst
var/lib/alsa
This saves the ALSA state every shutdown.
Finaly need to be loaded the ALSA state during startup:
Add this line to the /opt/bootlocal.sh:
alsa restore
That's all.
-
Hi Fany,
Yes! Thanks, that worked. 8)
There is a small typo in your instructions. The command that has to be added to bootlocal.sh is alsactl .
I've added this to bootlocal:
alsactl restore
Greetings,
Gerrelt.
-
I've tried to make the automatic store of the ALSA state during shutdown / reboot.
I have the link
alsactl store
at the beginning of the /opt/shutdown.sh file, but the ALSA state is not stored. Seems that this file is executed after the /opt/ /home/ directories backup and therefor the state file is not saved correctly. Is there some other way how to do so?
-
Hi bm!
I've tried the X version of piCore 6.0 rc1 with wifi and my Netgear wifi adapter works just as before. I had in mind to compile GO in piCore so I installed compile-essentials but I ran in to a problem. The compiler (gcc) can't be found. It seems that the path to it hasn't been set. I would really like some help here go get it working. Thanks for a good work!
Kind greetings,
meo
-
Hi again!
Sorry, my bad! I had it ondemand so no wonder it couldn't be found. However I ran into another problem. A dependency that is needed - linux/limits.h - so I still can use some help. I've compiled GO in the latest Raspbian and it went without problems. But in piCore I certainly can use some help since I haven't a clue what linux/limits.h is.
Kindest Greetings,
meo
-
Install linux headers fom repo.
Use provides function in apps to find tcz has specific file.
Go 1.4 is in the repo already.
-
Hi Béla!
Do you refer to: "linux-3.17.y-api.headers.tcz"?
Greetings,
meo
-
Didn't notice that you beat me to it when it comes to go. It feels more rewarding thought to have compiled it oneself.
Thanks for a great work with piCore!
meo
-
Hi again Béla!
Nevermind my question about the kernel headers before. Go is done compiling now and the, for GO, ubiquitous test programs are running. ;) Thanks for your help!
Greetings from a sunny town in Sweden,
meo
-
Complete set of modules can be downloaded for the now final kernel:
http://tinycorelinux.net/6.x/armv6/release/src/kernel/
-
Hi Béla,
A thing I noticed in the output of "p" from fdisk:
Command (m for help): p
Disk /dev/mmcblk0: 1000 MB, 1000079360 bytes
2 heads, 8 sectors/track, 122080 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 513 2344 14649 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 2344 3442 8789+ 83 Linux
Previously the start of partition two was the end of partition one + 1. But now these two numbers are the same: 2344. Is this correct?
Greetings,
Gerrelt.
-
Hi Béla,
A thing I noticed in the output of "p" from fdisk:
Command (m for help): p
Disk /dev/mmcblk0: 1000 MB, 1000079360 bytes
2 heads, 8 sectors/track, 122080 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 513 2344 14649 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 2344 3442 8789+ 83 Linux
Previously the start of partition two was the end of partition one + 1. But now these two numbers are the same: 2344. Is this correct?
Greetings,
Gerrelt.
I see the same thing.
-
I noticed tha same thing but when I followed the README file to make the second partition larger it didn't seem to matter. Everything works just fine as far as I can see.
Have fun,
meo
-
By default BusyBox fdisk displays cylinders:
root@box:/# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 4023 MB, 4023386112 bytes
2 heads, 8 sectors/track, 491136 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 513 2344 14649 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 2344 3442 8789+ 83 Linux
Use -u to display sectors:
root@box:/# fdisk -lu /dev/mmcblk0
Disk /dev/mmcblk0: 4023 MB, 4023386112 bytes
2 heads, 8 sectors/track, 491136 cylinders, total 7858176 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 8192 37489 14649 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 37490 55068 8789+ 83 Linux
fdisk (including BusyBox) do not allow to create overlapping partitions.
It is written in README:
1) Start fdisk partitioning tool as root:
sudo fdisk -u /dev/mmcblk0
Now list partitions with 'p' command and write down the starting and
ending sectors of the second partition.
-
Couple of problems:
1) i2c-dev is not loaded on demand like previous versions. i2c_bcm2708 is loaded on demand, but pretty much useless without i2c-dev getting loaded first. Loading them in boot local in the proper order works.
2) unable to mount cifs (smb) shares. cifs kernel module is loading on demand (The share is mounted just fine on older piCore devices) This error is in dmesg
[ 306.469540] CIFS VFS: could not allocate crypto hmacmd5
[ 306.469562] CIFS VFS: could not crypto alloc hmacmd5 rc -2
[ 306.469572] CIFS VFS: Error -2 during NTLMSSP authentication
[ 306.469586] CIFS VFS: Send error in SessSetup = -2
3) Having problems with squeezelite recognizing the USB DAC....but aplay does. so I need to investigate this a bit more.
-
3) Having problems with squeezelite recognizing the USB DAC....but aplay does. so I need to investigate this a bit more.
Was missing alsa-config.tcz I'm not sure what the desired dependency is....
Also, can you add ffmpeg development extensions to the repo. (And all of the libavxxxxxx-dev)
-
2) unable to mount cifs (smb) shares. cifs kernel module is loading on demand (The share is mounted just fine on older piCore devices) This error is in dmesg
[ 306.469540] CIFS VFS: could not allocate crypto hmacmd5
[ 306.469562] CIFS VFS: could not crypto alloc hmacmd5 rc -2
[ 306.469572] CIFS VFS: Error -2 during NTLMSSP authentication
[ 306.469586] CIFS VFS: Send error in SessSetup = -2
Yes, I ran into this yesterday. Made the mistake of trying to fix it on the other end by adding the NFS role on my WHS2011 box which I never got working either.
-
2) unable to mount cifs (smb) shares. cifs kernel module is loading on demand (The share is mounted just fine on older piCore devices) This error is in dmesg
[ 306.469540] CIFS VFS: could not allocate crypto hmacmd5
[ 306.469562] CIFS VFS: could not crypto alloc hmacmd5 rc -2
[ 306.469572] CIFS VFS: Error -2 during NTLMSSP authentication
[ 306.469586] CIFS VFS: Send error in SessSetup = -2
Try
sudo modprobe md5
before mounting.
BTW, which extension are you using to work with CIFS?
-
Try
sudo modprobe md5
before mounting.
BTW, which extension are you using to work with CIFS?
same result
I have filesystems-3.12.35-piCore+.tcz which also loads raid-dm-3.12.35-piCore+.tcz
here are the current modules loaded.
Module Size Used by Not tainted
nls_utf8 1235 0
cifs 285421 0
md5 1784 0
i2c_dev 5657 2
snd_usb_audio 118129 0
8192cu 537925 0
snd_soc_tas5713 5739 0
snd_soc_pcm512x 9034 0
snd_soc_wm8804 8098 0
snd_usbmidi_lib 19231 1 snd_usb_audio
snd_rawmidi 21760 1 snd_usbmidi_lib
snd_soc_bcm2708_i2s 6298 0
snd_seq_device 6481 1 snd_rawmidi
snd_soc_core 128665 4 snd_soc_tas5713,snd_soc_pcm512x,snd_soc_wm8804,snd_soc_bcm2708_i2s
snd_pcm_dmaengine 5529 1 snd_soc_core
snd_pcm 82413 3 snd_usb_audio,snd_soc_core,snd_pcm_dmaengine
leds_gpio 2083 0
snd_hwdep 5854 1 snd_usb_audio
led_class 4110 1 leds_gpio
snd_page_alloc 5140 1 snd_pcm
snd_timer 20541 1 snd_pcm
snd_compress 8323 1 snd_soc_core
snd 62326 9 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_seq_device,snd_soc_core,snd_pcm,snd_hwdep,snd_timer,snd_compress
regmap_i2c 1661 4 snd_soc_tas5713,snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
regmap_spi 1909 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
regmap_mmio 2826 1 snd_soc_bcm2708_i2s
evdev 10477 0
spi_bcm2708 4864 0
i2c_bcm2708 4743 0
-
What type of mount options do you use ??
And what type of share are you trying to mount ? Guest, User, Anonymous ??
Maybe you just to try to use option sec=ntlm
mount.cifs //cifs-server/share /localfolder -o guest,sec=ntlm
Have you tested some of this, like openwrt ??
http://wiki.openwrt.org/doc/howto/cifs.client
-
What type of mount options do you use ??
And what type of share are you trying to mount ? Guest, User, Anonymous ??
Maybe you just to try to use option sec=ntlm
mount.cifs //cifs-server/share /localfolder -o guest,sec=ntlm
Have you tested some of this, like openwrt ??
http://wiki.openwrt.org/doc/howto/cifs.client
Just username and password. Mount options have not been required in the past. And no sec=ntlm doesn't help. ntlm uses MD4, and it just fails with a MD4 encryption failure.
-
Just building samba, cifs-utils and their dependencies on 6.0. As soon as finished I can test. Most probably you need a crypto kernel module which is not in the base. You can download kernel modules from the server and install all crypto modules to find out which one is missing in the mean time (arc4?)
-
Just building samba, cifs-utils and their dependencies on 6.0. As soon as finished I can test. Most probably you need a crypto kernel module which is not in the base. You can download kernel modules from the server and install all crypto modules to find out which one is missing in the mean time (arc4?)
Will try that tonight. I'll look at an old picore 5.x system to see if something stands out.
-
Just building samba, cifs-utils and their dependencies on 6.0. As soon as finished I can test. Most probably you need a crypto kernel module which is not in the base. You can download kernel modules from the server and install all crypto modules to find out which one is missing in the mean time (arc4?)
hmac.ko is required. If I manually load this module first, the system will automatically load md5.ko and the mount is successful. on older versions of piCore, both of those modules were on the builtin list.
-
hmac.ko is required. If I manually load this module first, the system will automatically load md5.ko and the mount is successful. on older versions of piCore, both of those modules were on the builtin list.
Thanks. Yes, modules are rearranged in this version with the 3.12.35 kernel. I will add tem to bas in rc2.
-
Hi Béla,
I´ve recently bought a WiFi adapter with the mt7601 chipset.
That didn´t work with piCore, because it is missing the driver.
I found the sourcecode for this driver here (https://github.com/porjo/mt7601), and I´ve compiled it against the kernel (3.12.35) of this picore version.
And I got it working! Which makes me pretty proud of myself, this is my first time compiling a driver on Linux. 8)
It seems to work quit well, but I've just testet it for a couple of hours.
Is this something that would be nice to put in a tce?
If yes, I can provide the two files (RT2870STA.dat and mt7601Usta.ko) and the instructions.
Greetings,
Gerrelt.
-
Gi Gerrelt
it sounds great, congrats! For sure we must add it to the repo, please send.
Béla
-
Hi Béla,
I will send you a PM.
Greetings,
Gerrelt.
-
I got it :)