piCore-5.3rc4

[bmarkus]

Team Tiny Core is pleased to announce the availability of piCore-5.3rc4:

http://tinycorelinux.net/5.x/armv6/release_candidates/

* kernel updated to 3.14.4
* Raspberry Pi firmware updated to May 12, 2014 version
* official BusyBox patches applied
* curaga's wget3 BusyBox patch applied, setting default timeout to 10s
* tce-load: Don't show an error when extension contains multiple modules
* tce-load: Use sudo when unmounting meta-extensions
* patched to enable HDMI sound at 192 kbit/s rate (thanks sbp)
* patched rtl8192cu driver to disable powersaving
* filetool.sh "Done" message cosmetics

Please note, alsa-modules-3.14.4-piCore+.tcz has no startup script to avoid conflicts with DACS, necessary modules must be loaded by user, including on-chip sound device.

Images with preinstalled SSH for headless operation and with GUI also available.

Updating previous versions on Raspberry Pi without removing SD card:

Download piCore-5.3rc4-boot.tar.gz extract to a temporaray folder and overwrite content of /mnt/mmcblk0p1 after mounting it. It will overwrite custom boot options. If you have customied cmdline.txt on config.txt in the old system, do it again. Do not reboot if using wireless remote connection, otherwise you will loose connection due to incompatible kernel modules!

Next download kernel module tcz's from the repo matching new kernel version and reboot. You must have a new, updated system working.

Please note, there may be kernel module extensions which are not yet available in the repo.

Before modifying mmcblk01 content, it is adviced to make backup to a persistent device.

For support visit http://forum.tinycorelinux.net/index.php/board,57.0.html

[bmarkus]

Added QEMU version piCore-5.3rc4-QEMU.zip which includes LINUX and Windows start scripts, QEMU kernel and initrd file customized for QEMU. Original kernel and initrd files do not work.

Tested with QEMU 2.0.0/Linux (TC x86) and 1.5.3/Windows XP. If you see AMBA related modprobe error messages using older QEMU release you can omit it safely.

[Gerrelt]

Hi Béla,
 
 I've done a fresh install with the ssh version. Installed on one Pi with Wifi adapter.
Everything is fine, but I experience one strange thing:

If I execute the reboot command, the Pi starts the reboot, but it doesn't boot.
If I unplug the power and plug the power back in, everything is fine.

I have had this once before, some monthe ago. But I never found the cause of it.
It's not a big problem, everything else is working fine.

Greetings,
   Gerrelt.

[bmarkus]

Gerrelt

do you have any other USB device connected than keyboard and mouse? Is there an USB HUB connected? If so, unplug them and retry. It happened to me in the past with an x86 laptop that a connected USB HD stopped booting.   Reboot work fine here on my RPi.

[Paul_123]

Do you have any network drives mounted.   If I have a SMB(CIFS) share mounted, the reboot takes forever. 

[bmarkus]

Do you have any network drives mounted.   If I have a SMB(CIFS) share mounted, the reboot takes forever.

Are you using cifs-utils? Do you have the same issue with previous rc/alpha and 5.2.x or just rc4?

Can you add umount to /opt/shutdown.sh?

[Rich]

Do you have any network drives mounted.   If I have a SMB(CIFS) share mounted, the reboot takes forever. 

I've noticed this too on my X86 machines and added this  /opt/shutdown.sh  to fix it:

Code: [Select]

# put user shutdown commands here
sync
umount -f /mnt/bbAs I recall, I had to add the  -f  option otherwise shutdown/reboot still sometimes took forever.

[bmarkus]

umount is expected to do sync but the explicit sync is fine

[Paul_123]

Do you have any network drives mounted.   If I have a SMB(CIFS) share mounted, the reboot takes forever. 

I've noticed this too on my X86 machines and added this  /opt/shutdown.sh  to fix it:

Code: [Select]

# put user shutdown commands here
sync
umount -f /mnt/bbAs I recall, I had to add the  -f  option otherwise shutdown/reboot still sometimes took forever.

I did put an unmount in the shutdown script before, but I never tried the -f option.   Thanks for the tip.

[Paul_123]

Do you have any network drives mounted.   If I have a SMB(CIFS) share mounted, the reboot takes forever.

Are you using cifs-utils? Do you have the same issue with previous rc/alpha and 5.2.x or just rc4?

Can you add umount to /opt/shutdown.sh?

I just have the cifs module, and use the normal fstab/mount/unmount.   I has done it with every version of piCore, and Raspbian.   Pretty sure my 64 bit debian image does that too.

[bmarkus]

Paul,

I would say it is not piCore-5.3rc4 bug.

[Rich]

Hi Paul_123

I did put an unmount in the shutdown script before, but I never tried the -f option.

You do realize it's  umount  not  unmount , Right? If there are any syntax errors in the command it will not execute and you won't know it.

[Gerrelt]

do you have any other USB device connected than keyboard and mouse? Is there an USB HUB connected? If so, unplug them and retry. It happened to me in the past with an x86 laptop that a connected USB HD stopped booting.   Reboot work fine here on my RPi.

I don't have a keyboard or mouse connected, I do everything remote (thanks to the SSH image!  ). I connected it to a wired network first and then install everything using putty on my PC.
But there is a USB hub connected, and to that USB hub is a soundcard and wifi adapter connected.

I've just tried it with the wifi adapter unplugged, but that didn't matter. Unplugging the hub is harder, because it's all inside a 1980's radio cassette player. 

Do you have any network drives mounted.

Nope.


The strange thing is that with the previous release, I didn't have this "problem". And I used exactly the same components.
I will connect a screen to one of the other raspberries and try it again. Maybe there's a message on the screen.

Greetings,
    Gerrelt.

[bmarkus]

The strange thing is that with the previous release, I didn't have this "problem". And I used exactly the same components.
I will connect a screen to one of the other raspberries and try it again. Maybe there's a message on the screen.

Greetings,
    Gerrelt.

What do you mean previous release, 5.2?

When you enter reboot, is your SSH connection terminated by the Pi?

[Gerrelt]

What do you mean previous release, 5.2?

No, piCore-5.2.2.

When you enter reboot, is your SSH connection terminated by the Pi?

Yes, the SSH connection is terminated, and Squeezelite is shutdown too.