Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on May 13, 2014, 12:52:54 PM
-
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
-
Added QEMU version piCore-5.3rc4-QEMU.zip (http://tinycorelinux.net/5.x/armv6/release_candidates/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.
-
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.
-
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.
-
Do you have any network drives mounted. If I have a SMB(CIFS) share mounted, the reboot takes forever.
-
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?
-
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:
# 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.
-
umount is expected to do sync but the explicit sync is fine :)
-
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:
# 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.
-
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.
-
Paul,
I would say it is not piCore-5.3rc4 bug.
-
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.
-
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! 8) ). 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. ;D
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.
-
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?
-
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.
-
Gerrelt,
In the 3.14.y kernel there were changes in the USB part, probably it is causing the difference. Officially the latest stable kernel for the Pi is the 3.12.y, 3.13.y/3.14.y is still experimental and changing in every two weeks.
When you connect the monitor, please check shutdown also, does it work normally or not.
-
BTW, it can be also the new RPi firmware, not the kernel.
gerrelt@
Can you try 5.3rc4 with the RPi firmware from 5.2.2?
-
Hi Béla,
I will try that, but not tonight anymore.
But, I have done some testing.
I have put the SD card that was in my radio cassette player into the livingroom Raspberry. Normally that raspberry contains a Raspbmc image with Squeezelite installed on it.
With TinyCore in it, it worked normally, the reboot worked as it should be.
Then I put the piCore SD card back into the radio cassette player and connected a HDMI cable (I was just able to put it in through the battery compartment) to it and the TV.
After I issued the reboot command, shutdown looked normal. Afther the shutdown the "rainbow screen" appeared and it wanted to boot. But it gets stuck on these messages:
(http://www.gerrelt.nl/RaspberryPi/tinycore/piCore_5.3rc4_after_reboot.jpg)
The funny thing is, when I uploaded this picture I found another picture from a year ago. That was with piCore 4.7.7, but it was exactly the same message ;D :
(http://www.gerrelt.nl/RaspberryPi/tinycore/after_reboot_command.jpg)
It must be something with the Hub or USB soundcard that is causing this. But I still think it is strange it was fine for a year, but now it came back.
But, don't worry about this, it is probably some incidental combination. I will update the other piCore raspberries with 5.3rc4 and see if it gives me the same behaviour.
Greetings,
Gerrelt.
-
hi Gerrelt,
I have been playing with piCorePlayer a lot over the last few weeks, going through hundreds of shutdown and reboots. I have seen my share of "corruptions".
Whenever I get a problem booting the Rasberry Pi like you have, I simply replace config.txt and/or cmdline.txt by mounting the SD card in a Debian VM.
regards
-
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.
yes....a typo from a quick response. I just added the -f to the command line, and that did not help.
what is the best way to troubleshoot the shutdown scripts for a reboot. syslog??
-
Hi Paul_123
What happens if you enter the command in a terminal? Does that take a long time to execute? Error messages?
-
Hi Paul_123
What happens if you enter the command in a terminal? Does that take a long time to execute? Error messages?
the dismounting is nearly instantaneous when ran from command line. Provided I remember to dismount first, the pi halts and begins to restart in a few seconds.
-
Hi Béla,
I will try that, but not tonight anymore.
But, I have done some testing.
I have put the SD card that was in my radio cassette player into the livingroom Raspberry. Normally that raspberry contains a Raspbmc image with Squeezelite installed on it.
With TinyCore in it, it worked normally, the reboot worked as it should be.
Then I put the piCore SD card back into the radio cassette player and connected a HDMI cable (I was just able to put it in through the battery compartment) to it and the TV.
After I issued the reboot command, shutdown looked normal. Afther the shutdown the "rainbow screen" appeared and it wanted to boot. But it gets stuck on these messages:
(http://www.gerrelt.nl/RaspberryPi/tinycore/piCore_5.3rc4_after_reboot.jpg)
The funny thing is, when I uploaded this picture I found another picture from a year ago. That was with piCore 4.7.7, but it was exactly the same message ;D :
(http://www.gerrelt.nl/RaspberryPi/tinycore/after_reboot_command.jpg)
It must be something with the Hub or USB soundcard that is causing this. But I still think it is strange it was fine for a year, but now it came back.
But, don't worry about this, it is probably some incidental combination. I will update the other piCore raspberries with 5.3rc4 and see if it gives me the same behaviour.
Greetings,
Gerrelt.
gerrelt
does it stuck when you start it after power on or only when reboot?
-
Hi Béla,
Only when I do a reboot.
I have tested on 3 more raspberries now. One of them does not have this problem.
The other ones have the same problem. And one of them only has it sometimes. ???
Unplugging the USB soundcard from the USB hub seems to improve it.
Greetings,
Gerrelt.
-
Gerrelt, thanks. I can't reproduce it unfortunately. What I'm thinking is to release 5.2.3 which is in fact the same as 5.3 regarding core scripts, the only difference is the kernel which is unchanged 3.13.6 and the RPi firmware which may be updated. We can keep 5.3 testing a bit longer. Maybe audio sound devices behave better in 3.14.y but I see other small issue; when I create a directory to loopmount an extension, first mount fails as directory wouldn't exists. Waiting a bit same command works. Tghis happened already with early 3.13.y too which was not used for production. Otherwise it is stable.
-
Hi Béla,
My problem is only minor. So, you could file it under "known issue".
Maybe it will be fixed in the next release of the Raspberry firmware.
Greetings,
Gerrelt.
-
Enabling FIQ-FSM fix the reboot hang issue. Stay tuned for 5.3