Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on March 10, 2012, 11:25:27 PM
-
The third release candidate of Core 4.4 is ready for public testing:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates
The major theme for Core v4.4 is a kernel & modules update and tag searching.
Changelog for 4.4rc1:
* Minor kernel update to 3.0.21 to support the following:
** ax25 / ham radio support
** kexec
** efficeon agp patch
** r6040 mii fix
** isa libata enabled for very old laptops
** xts, gf128mul for truecrypt uses
** resolves the kernel panic issue when mounting CIFS shares.
* Updated tc-config with syslog/rsyslog patch
* Updated Xprogs.tcz: scmbrowser and smc-fetch.sh tweaks
Update instructions, from the release candidate area:
1. Copy over new vmlinuz
2. Copy over new core.gz
3. Copy over new Xprogs.tcz
4. boot into new system
if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing
or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing
=====================
Change log for 4.4rc2
* Updated search.sh added -t option for tag search.
* Updated provides.sh for CLI use.
* Updated appbrowser for new tag search.
* Updated ab keyword is now a tag search.
* Updated tce-size with date check on sizefile update.
* Updated tce-setup fixed when base boot code is used with missing /tmp/tce/optional directory.
* Updated tce-setdrive with a required readlink.
* Updated filetool.sh with a required readlink when used after tce-setdrive.
* Recompressed modules to save space.
* Added ssb module to base.
Note: Xprogs.tcz has been updated and is in the release candidate area.
=========================
Change log for 4.4rc3
* Updated busybox 1.19.4 plus patches to fix busybox tftpd vulnerability.
* Updated tc-terminal-server to accomodate busybox tftpd vulnerability.
* Updated scm-search -t for tag searching.
* Updated scmbrowser for tag searching.
* Updated filetool.sh improved invalid device handling.
* Updated tce-setdrive now sets default backup device without a reboot.
* New boot code, e.g., iso=sdb1 booting from a single ISO file to load embedded extensions.
* New fromISOfile script for after boot support of a single ISO file embedded extensions.
* Updated rebuildfstab fixed pid checking.
* Updated exittc and filetool spelling.
Note: Xprogs.tcz has been updated and is in the release candidate area.
Note: Feature freeze.
-
Starting with v4.4rc3 it is now possible to load the embedded extensions inside an iso image file.
Booting from an iso as supplied by various boot loaders, eg YUMI, the embedded extensions were not readily available.
The new fromISOfile now provides for full X/GUI+ experience.
It can be used as a boot code:
boot: tc iso=sdb1
This short version will scan sdb1 for isos and if one is found will attempt to mount and process it.
Optionally one can use the full path to avoid the scanning delay with:
boot: tc iso=/mnt/sdb1/multiboot/ISOS/TinyCore-4.4.iso
After boot is also supported. If the system booted from an iso file and you are at:
$
they use either the short/scan style or fullpath
$ sudo fromISOfile /mnt/sdb1
$ startx
Once you have it working and you have set your tce directory, tce-setdrive
then you can add fromISOfile to /opt/bootsync.sh as
/usr/bin/fromISOfile /mnt/sdb1/multiboot/ISOS/TinyCore-4.4.iso
This will result in the familair X/GUI from a single ISO image file.
-
I propose a tce.installed fix:
http://forum.tinycorelinux.net/index.php/topic,12339.msg69994.html#msg69994
Regards
Uggla
-
but this features is only able to start tinycore or can act as "boot loader" for any bootable ISO?
-
It's only for loading extensions from an iso file, in the running session.
-
Seems fromiso doesn't support label/uuid?
-
[...] or can act as "boot loader" for any bootable ISO?
you could use memdisk (http://www.syslinux.org/wiki/index.php/MEMDISK) for that purpose ...
-
from version to version remains forgotten and nobody needed cde/optional/libiconv.tcz.dep with zero size
and i have a question, can't understand for what instlist-files are used? i can't find anything about it
-
hi roberts,
with the actual release candidate my ethernet-card works flawless now.
b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet
b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb0:0: eth0: Flow control is off for TX and off for RX
thank you.
-
from version to version remains forgotten and nobody needed cde/optional/libiconv.tcz.dep with zero size
and i have a question, can't understand for what instlist-files are used? i can't find anything about it
The instlist files are used by tc-install when running from Core Plus. When you select the categories of extensions to install from tc-install (such as "Wireless Firmware", "Wireless", etc) these ".instlist" files contain the list of extensions that will be installed for each category.
-
thanks for clarifying, now it's clear :)
i always installed tc manually and never used tc-install
and therefore could not understand what is this
-
It's only for loading extensions from an iso file, in the running session.
Uhm I misread!
you could use memdisk (http://www.syslinux.org/wiki/index.php/MEMDISK) for that purpose ...
effectively I remember I had tried some time ago, trying to start [remaster] iso from tinycore.
now that you reminded me, what was exactly happening is that it started without the extensions.
So that means I can start other distros using tinycore as bootloader for derived and not derived?
-
Tiny core is not working as a bootloader.
Your bootloader is loading the tinycore kernel and initrd.
With the new iso=option, tinycore can now find the tce directory inb that iso.
-
Thank You for 4.4rc3 Roberts !
With `fromISOfile` I get just what I needed when try to experiment with cde boot option - a possibility to boot a system to a customizable starting X/GUI configuration, without using .tcz or .scm extensions from standard /tce directory.
You were quite right with:
" On a usb install you should be using a normal live tce directory and not cde.
cde is intended for cdrom and isohybrid for delivery of read-only extensions due to the
factoring out of X/GUI from the initrd strting with version 4.2"
in 4.4rc2 conversation:
-
error permissions issued during the backup
tc@box:~$ filetool.sh -b
sed: can't create temp file '/opt/.filetool.lstrjEe5X': Permission denied
Backing up files to /mnt/sda1/tce/mydata.tgz Done.
sed (string 158) haven't permissions to delete the empty lines
sed -i /^$/d /opt/.filetool.lstsudo should be used
sudo sed -i /^$/d /opt/.filetool.lst
-
Hi AbNoRMiS
I think your /opt directory may not have its permissions set correctly. I just checked under TC2.1, TC3.4, and TC4.1
which all show the permissions set to 775.
-
yep really, it's my fault, sorry
my /opt has permissions 755 and member of root group, not staff
owing you i found the excessive sudo in my script for core repackaging :)
thanks
-
Hi AbNoRMiS
Your welcome. Yes, I should have also mentioned the correct ownership is root:staff
-
hi roberts,
with the actual release candidate my ethernet-card works flawless now.
b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet
b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb0:0: eth0: Flow control is off for TX and off for RX
thank you.
Thanks for sharing. Good news and success strories are always welcomed!
-
isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05
isolinux 3.82 and 3.84 continue to boot fine.
-
While booting PLOP Boot Manager from a cd to boot TinyCore-4.4rc3.iso using YUMI from a multiboot USB (this specific machine can neither boot USB or any version of tc using isolinux version 4.x ) I've failed in all but one time, to find and mount sdb1 using "fromISOfile" with bootcode or after boot using YUMI as described, short method or full path yet still unable to find or mount /mnt/sdb1/multiboot/ISOS/TinyCore-4.4rc3.iso
Using either
sudo fromISOfile /mnt/sdb1
or
sudo fromISOfile /mnt/sdb1/multiboot/ISOS/TinyCore-4.4rc3.iso
the script complains that it can't find either in fstab which incidentally only contains /dev/sda1 and /dev/sr0 + a few other non pertinent entries..
Any ideas what we're missing here?
Update: the key was in using something like " sudo fromISOfile /sr0 " which then mounted the tc.iso to /mnt/cdrom
-
The next gotcha, is trying to establish a wifi connection. wireless-3.0.3-tinycore.tcz is installed to cde/optional
You know this is coming.. the latest TinyCore-4.4rc3 needs wireless-3.0.21-tinycore.tcz to function
please :)
-
there is missing checksum cde/optional/wireless-3.0.21-tinycore.tcz.md5.txt in CorePlus-4.4rc3.iso
-
isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05
isolinux 3.82 and 3.84 continue to boot fine.
Please report this bug to syslinux, if you haven't already.
-
isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05
no problems with a dual PIII 700MHz (BX chipset) with AMI BIOS and booting via PloP from an USB stick the CorePlus-4.4rc3.iso image with iso=sdb1 ...
PS: take care that there is no other iso image on the stick, otherwise you have to specify the full name and path to the iso (see also: http://forum.tinycorelinux.net/index.php/topic,12724.msg69967.html#msg69967 (http://forum.tinycorelinux.net/index.php/topic,12724.msg69967.html#msg69967))
Bernhard
-
The ISOLINUX problem is consistently reproducible with each and every isolinux version since IIRC 4.0, 4.01, 4.02, 4.03, 4.05, I believe I just attempted 4.06 it's a shame but they all fail to boot on old equipment I have.. Pity really because Grub is considerably slower to boot than isolinux on PC's that it works on.
Isolinux 3.x (all versions) work great on my old notebook, yet for some reason I have trouble booting TC after version 4.1 with it. I don't think there is any reason for this, right? Am really looking for tc4.4 to run on older equipment but the isolinux issue makes this a non starter.
Thanks bernhard for that link, I spent hours looking for that thread again yesterday without any luck.. :) But what is a "Dual PIII" anyhow?? A dual core or a dual proc.? either of which is a newer design than the notebook I'm using
-
Additionally, I still get the "udevadm settle - timeout of 5 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (874) " issue which hangs until depressing the enter key which then brings up a command prompt :(
-
Additionally, I still get the "udevadm settle - timeout of 5 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (874) " issue which hangs until depressing the enter key which then brings up a command prompt :(
It's not a hang, it's merely printed on top of the terminal...
-
..On top of the terminal, ok agreed but there is no command line prompt until after some user input, because we are waiting for the prompt to appear, it doesn't until after some user initiated keyboard input, which kinda constitutes a hang right?
How about not having the status message at all? instead have the command exit to a prompt??
-
Thanks bernhard for that link, I spent hours looking for that thread again yesterday without any luck.. :)
you're welcome ...
But what is a "Dual PIII" anyhow?? A dual core or a dual proc.?
a dual processor. It is an industrial dual slot 1 motherboard and about 10 years old. Bios is dated back to 2001.
either of which is a newer design than the notebook I'm using
oh, what is it dated?
Bernhard
-
WOW I don't ever remember a dual slot PIII, but then I forget a lot too..
this old notebook which incidentally runs great, has run flawlessly since 2000 :D
-
I just rechecked it, the board is even older than I remembered.
Bios dates back to 04/11/2000. Its an IEI Rocky P220BX.
The manual has copyright year 1998 :-)
It has an usb 2 board in the PCI bus and PloP sits in the MBR of the hard disk so I can
boot from USB without hassle since this old bios does not support booting over USB.
--
Bernhard
-
Mine was End Of Line in 2000, so same era I guess
either way it still doesn't boot with any version of isolinux/syslinux above 4.0 :(
Am still attempting to boot tc4.4rc3 with isolinux 3.82..
-
Hi bernhard
To determine the approximate age of the motherboard, check the the date codes on the chips and use
the most recent one.
-
Hello,
i had issues using TinyCore 4.x on Neoware ThinClient. 3.x ran fine, but new cpufreq feature in the base install causing problem for me. (freeze)
I could resolve that by adding longhaul.disable=1 to the bootparams, but i`m not sure if others will easily find this post or workaround. I also reported that upstream and longhaul module is considered to be a candidate for being marked as broken again - Dave Miller needs to decide. btw, blacklist=longhaul did not work, i`m curious, isn`t that param especially for such case?
There is a suggestion at http://forum.tinycorelinux.net/index.php?topic=12788.new;topicseen#new to move the longhaul module into a separate tzc. I don´t know how many people using longhaul actively and successfully.
What about adding a "safe mode" feature as boot option, like other distros typically offer (acpi=off, noapic, edd=off, no cpufreq etc) ? That would at least make troubleshooting easier....
regards
Roland
-
The ISOLINUX problem is consistently reproducible with each and every isolinux version since IIRC 4.0, 4.01, 4.02, 4.03, 4.05, I believe I just attempted 4.06 it's a shame but they all fail to boot on old equipment I have.. Pity really because Grub is considerably slower to boot than isolinux on PC's that it works on.
Isolinux 3.x (all versions) work great on my old notebook, yet for some reason I have trouble booting TC after version 4.1 with it. I don't think there is any reason for this, right? Am really looking for tc4.4 to run on older equipment but the isolinux issue makes this a non starter.
UPDATE: Have successfully created a new ISO blending CorePlus4.4rc3 and isolinux 3.82 with a rewrite of the boot menu structure which now boots perfectly on my old notebook, I'm a happy camper thank you
8)
-
... or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing
When I updated from 4.3, following instructions carefully, I didn't get a GUI at boot. waitforX eventually gave up and I was granted a command prompt, so I entered the commands quoted above. Some kernel-dependent extensions got installed, but the one that I needed to start the GUI was not included: graphics-3.0.21-tinycore.tcz. After installing that one manually, everything is fine. Please investigate. Thanks!
-
I don´t know how many people using longhaul actively and successfully.
In my case integrated cpuscaling work fine
What about adding a "safe mode" feature as boot option, like other distros typically offer (acpi=off, noapic, edd=off, no cpufreq etc) ? That would at least make troubleshooting easier....
could be a solution
-
... or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing
When I updated from 4.3, following instructions carefully, I didn't get a GUI at boot. waitforX eventually gave up and I was granted a command prompt, so I entered the commands quoted above. Some kernel-dependent extensions got installed, but the one that I needed to start the GUI was not included: graphics-3.0.21-tinycore.tcz. After installing that one manually, everything is fine. Please investigate. Thanks!
Was tested against an Xvesa as well as an Xorg setup. Could be that your dep files were not updated. Using Update .dep files would take care of that,
-
Seems fromiso doesn't support label/uuid?
Added support for LABEL & UUID