Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on November 21, 2009, 06:10:29 PM
-
The Third Release Candidate of v2.6 (tinycore_2.6rc3.iso), is now posted and ready for testing only.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates
tinycore_2.6rc3.iso
tinycore_2.6rc3.iso.md5.txt
Change log for v2.6rc3:
* Dropped upx'ed bzImage due to reported system errors.
* Updated rebuildfstab to reflect removals..
* Updated select utility added paging through long select lists.
* Updated tc-restore.sh. restore boot option overrides default backup location.
Notes:
You must have your tcz collection updated, i.e., all squashfs and all with 4096 block size.
Be sure to update your kernel..
The distribution files are also availble:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/distribution_files
Please check md5sums after downloading..
-
This new RC rocks! No more ACPI errors in virtualbox, and it booted in 15 seconds, including BIOS start-up stuff! ;D
-
Fast boot and wifi works with rc3. Mouse movement is smooth. ACPI works. No BIOS errors. Great job everyone involved. Thanks!
-
Does not find my persistent stuff so boots into cloud mode. I dropped it into an existing test partition with extensions and also started from scratch, same result.
-
Try adding waitusb=5 to see if that helps.
-
I am booting from internal HD.
I have done some tests and it is associated with the file tinycore.gz. I can boot OK with tinycore-2.5 and bzImage-2.6rc3 but no combination that includes tinycore.gz-26.rc3 succeeds.
As it boots I see a brief message about it not finding device, and that persistent home is disabled or something. This is on partition sda8.
-
Please post the output of "fdisk -l" , "cat /etc/fstab", and "showbootcodes"
-
On my Acer Aspire One netbook (where an 8GB SSD replaces a conventional HDD) I dual-boot Ubuntu and TC using grub to choose. All TC materials are on the SSD. In this setup the boot option waitusb is essential for 2.6rc3 to notice the extensions in /dev/sda1/tce in time to load them. (When they don't get noticed, the boot is extremely quick!) This issue is new with 2.6rc3; everything up to 2.6rc2 needed no waitusb. I know that waitusb=3 works and that no waitusb parameter doesn't; I haven't experimented on how low I can go. [This extra wrinkle may confuse newcomers to TC, but IMHO it's a good sign that the init scripts are getting ever faster and more efficient. So please receive these remarks as a report and not at all a complaint.]
A confusing behaviour: even with waitusb=3 or 5, 2.6rc3 seems not to find the file mydata.tgz on the root of device /dev/sda1. The result is that /opt does not get populated with my preferred scripts, and /opt/bootlocal.sh does not get recalled from the backup, so a bunch of user-specified initialization is not happening. I know that the file mydata.tgz is still intact because booting TC2.5 still loads it OK.
It may be useful to mention that the kernel in 2.6rc3 is the same one used in all versions 2.0-2.5. Users (like me) who kept the old one around can just go back to using it ... the experimental kernel in earlier RC's for 2.6 was functionally identical, only compressed for size. [I think this means that users like me for whom the upx-compressed kernel actually worked could keep using it instead of reverting, but that would slightly violate the spirit of helping test the full RC as proposed.]
With thanks, as always.
-
Philip, are you using restore=sda1 or autoscan?
-
My bootcodes:
quiet tce=sda8 opt=sda8 home=sda8 max_loop=255 tz=EST,M10.1.0/2,M4.1.0/2
These were gathered while booting off v 2.6rc3 both files.
-
Thanks for the feedback. I think it may be a race condition.
I might have a fix. We will see.
-
That sounds like it could be it. I just tried again and it was successful once, then cloud again afterwards.
-
Philip, are you using restore=sda1 or autoscan?
$ cat /proc/cmdline
waitusb=3 tce=sda1 vga=789 desktop=flwm host=min toram nodhcp quiet elevator=noop
Thanks.
-
FWIW, I boot off a read-only CD and have the backup file and tce directory on a usb stick (i.e. both directly under sda1).
When I booted 2.6 rc3 with waitusb=5 TCL loaded my extensions OK but didn't load the mydata.tgz info (e.g. no Opera settings, no wallpaper). Didn't see the boot message indicating that it was restoring from backup either. Tried using waitusb=5 restore=sda1 and same result,
-
First, booting problems are gone, it loads and starts fine.
Installing wicd.tcz with appbrowser I get consequently a HTTP server error message echoed by wget:
... Range Not Satisfiable on wicd.tcz
Strange is, that wicd.tcz is not stored in /tce but the module itself is loaded into the RAM and listed in tcz2ram.lst too.
-
First, booting problems are gone, it loads and starts fine.
Installing wicd.tcz with appbrowser I get consequently a HTTP server error message echoed by wget:
... Range Not Satisfiable on wicd.tcz
Strange is, that wicd.tcz is not stored in /tce but the module itself is loaded into the RAM and listed in tcz2ram.lst too.
cause wicd.tcz is listed as its own dep. Think this needs to be placed in extensions topics...
-
cause wicd.tcz is listed as its own dep. Think this needs to be placed in extensions topics...
Right, thanks for finding it. Itw as put there accidentaly and for testing purposes :) However, it is not handled properly by appbrowser. Not an everyday situation though...
-
The road to 2.6 has been difficult as the changes were all in critical areas, kernel, fstab, and restore. Thanks to great feedback, the kenrel issue was solved, fstab issues I believe was a race condition, I have prepared an adjustment there, and the restore had a bug which I have fixed. Will post rc4.