Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on February 25, 2012, 08:09:21 AM
-
The first release candidate of Core 4.4 is ready for public testing:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates (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.
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
-
Heads up to only for core64.gz users.
core64.gz has been reposted in the relase_candidate/distribution_files
to correct having both 32 and 64 bit modules.
Repost only contains 64 bit modules.
-
Thank you for the kernel update! You should also add that this kernel update fixes CIFS shares as reported by myself here: http://forum.tinycorelinux.net/index.php?topic=11896.0. (http://forum.tinycorelinux.net/index.php?topic=11896.0.) I appreciate this, the earlier 3.0 kernels were very buggy, this should fix a lot of intermittent issues.
Also appreciate you're adding this: ** isa libata enabled for very old laptops. Most of the systems I work on are old embedded systems and libata could certainly prove very useful to me. Will test shortly.
-
Updated change log. Thanks and thanks for help in testing the new features.
-
works perfect on my compaq evo d500 with 512mb ram
though i don't use scm for practical purpose except test
-
in the AppBrowser and ScmBrowser
not indicate information on the Depends and Files tabs
when return to the Info tab then information also is lost
wget: server returned error: HTTP/1.1 404 Not Found
-
Great new update thanks :)
Attempted to update a perfect working 4.1 tinycore and copied the core files plus xprogs, xlibs wbar, xvesa, fltk-1.1.0 (tce-audit builddb & fetchmissing did not find this dependency) flwm_topside. many attempts to reboot to x fails. Ok must be missing something here..
Rebooted again to "udevadm settle timeout" error message...
seems like a mismatch of deps here.. ok have almost exhausted my charm on this system today, am going to revert to 4.3 if I can and try again..
ok on 4.3 now and error message has left the building (hopefully to stay gone..) still can't start X
Added desktop=flwm_topside to boot config file, but still no desktop. boots to a a command line, ran tceaudit builddb and fetchmissing additionally ran tce-update still no joy..
Rebooted again to "udevadm settle timeout" error message...
clearly have missed something...
Ok one more time....
-
in the AppBrowser and ScmBrowser
not indicate information on the Depends and Files tabs
when return to the Info tab then information also is lost
wget: server returned error: HTTP/1.1 404 Not Found
sorry Robert, i want to correct my previous post
this error occurs when running kernel 3.0.3-tinycore and updated Xprogs.tcz
when running kernel 3.0.21-tinycore with updated Xprogs.tcz it works perfectly
-
Ok found the problem.
The MBR expected to find extlinux (with it's contents) in /boot along with tinycore.gz and vmliuz as required by extlinux.conf per the old install (originally setup up using tinycore installer). However core.gz and vmlinuz will not boot when it's installed directory is located in root (or so it appeared). It is clear i had to separate the two.
Placing core.gz and vmlinuz in it's own boot directory under sda1/tce/boot, also move extlinux directory and it's contents to sda1/boot with minor edits to extlinux.conf to point to /tce/boot proved a success, core 4.4 boots (no wbar, but am sure I'll figure that out a lot quicker than fixing the path to ldlinux.sys)
wbar is not a dep of any loaded file, so after setting wbar to load onboot all is well :D
I guess this is a result of bypassing a couple of upgrades
-
Per roberts as of 4.3 the boot directory is under /mnt/sda1/tce/ (I install to USB). My 4.2 (and previous) installation had boot under /mnt/sda1/. I've been installing using tc-install from CorePlus and before that TinyCore. That puts core.gz, vmlinuz, and the extlinux directory under the boot directory. This is for 4.3 (haven't tried 4.4rc1).
-
However core.gz and vmlinuz will not boot when it's installed directory is located in root (or so it appeared). It is clear i had to separate the two.
There is no forced location, that's just the default.
-
hi friends,
with that release candidate my network card isn't loaded anymore.
thats from my dmesg:
b44: Unknown symbol ssb_device_is_enabled (err 0)
b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0)
b44: Unknown symbol ssb_bus_may_powerdown (err 0)
b44: Unknown symbol ssb_pcihost_register (err 0)
b44: Unknown symbol ssb_device_disable (err 0)
b44: Unknown symbol ssb_device_enable (err 0)
b44: Unknown symbol ssb_driver_unregister (err 0)
b44: Unknown symbol __ssb_driver_register (err 0)
b44: Unknown symbol ssb_bus_powerup (err 0)
b44: Unknown symbol ssb_clockspeed (err 0)
b44: Unknown symbol ssb_dma_translation (err 0)
these are my boot-codes:
waitusb=5
protect
restore=LABEL=tc
tce=LABEL=tc/tce4
lst=onboot_fluxbox.lst
vga=795
psmouse.proto=imps
settime
laptop
multivt
mydata=core-test
blacklist=snd_usb_audio
initrd=/live/core-testing/boot/core.gz
BOOT_IMAGE=/live/core-testing/boot/vmlinuz
-
You will need to copy over the wireless-3.0.21-tinycore.tcz.
-
...
Rebooted again to "udevadm settle timeout" error message...
clearly have missed something...
Ok one more time....
I still get udevadm settle timeouts with the new kernel as well (mostly on older hardware). What would be the impact of decreasing the timeout or taking the call to udevadm out all together? It seems that there are always events left in the queue no matter what the timeout is.
-
hi gerald clark,
you have to know that b44 is my internal ethernet-card,
but nevertheless i tried the wireless-3.0.21-tinycore.tcz... without any success.
do you have another hint or proposal?
by the way:
debian deleted the broadcom-drivers in the kernel, i think they call them plop-divers or so...
and with debian you can install a nonfree-package with broadcom-modules,
although everything works fine without that additional package...
from the result, it has the function almost like a dummy-package... ;-)
... like "i just want to inform you that this is a non-free-driver"...
-
netnomad, have you tried wl-modules-3.0.21-tinycore.tcz? See info file for blacklist requirements.
-
hi roberts,
i tried wl-modules-3.0.21-tinycore.tcz in my onboot.lst and succeeded.
i used following blacklist-bootcodes:
blacklist=snd_usb_audio
blacklist=ssb
blacklist=b43
but the further boot-messages are not so nice:
at the beginning there are still these messages i posted with missing b44...
later after loading the wl-module over the onboot.lst all drivers are initiated without further problems.
is this the only way to solve this with this error messages:
b44: Unknown symbol ssb_device_is_enabled (err 0)
b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0)
b44: Unknown symbol ssb_bus_may_powerdown (err 0)
b44: Unknown symbol ssb_pcihost_register (err 0)
b44: Unknown symbol ssb_device_disable (err 0)
b44: Unknown symbol ssb_device_enable (err 0)
b44: Unknown symbol ssb_driver_unregister (err 0)
b44: Unknown symbol __ssb_driver_register (err 0)
b44: Unknown symbol ssb_bus_powerup (err 0)
b44: Unknown symbol ssb_clockspeed (err 0)
b44: Unknown symbol ssb_dma_translation (err 0)
EXT4-fs (sdb2): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sdb2): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
intel_rng: FWH not detected
lib80211: common routines for IEEE802.11 drivers
b44 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
libipw: 802.11 data/management/control stack, git-1.1.13
libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ssb: Sonics Silicon Backplane found on PCI device 0000:02:05.0
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
b44: b44.c:v2.0
ipw2200 0000:02:07.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:00:f0:7d:e9:6b
ipw2200 0000:02:07.0: PCI INT A disabled
ipw2200: probe of 0000:02:07.0 failed with error -5
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
-
IIRC this was fixed after the previous kernel release too, and I forgot to add it to sorter.sh. b44 is a wired card, please move ssb to base again Robert.
-
Strictly speaking this might be seen as an extension request, but I guess we could do with a new linux-headers-3.0.21-tinycore.tcz as the other new kernel modules have now been added to the 4.x repository.
-
hats usually takes care of that, I either don't care about external modules or just use the full source. Ping him on irc :)
-
Placing core.gz and vmlinuz in it's own boot directory under sda1/tce/boot, also move extlinux directory and it's contents to sda1/boot with minor edits to extlinux.conf to point to /tce/boot proved a success, core 4.4 boots (no wbar, but am sure I'll figure that out a lot quicker than fixing the path to ldlinux.sys)
This points to 1) inconsistencies in your Syslinux config and 2) changes in the default install/search folders for TC. Forcing the search folder or fully aligning with the current patterns would have likely solved this.
If you move the extlinux/ directory to sda1:tce/boot/ then run 'extlinux -u /mnt/sda1/tce/boot/extlinux/' then update config file references appropriately, this will solve your issue. You can also watch the return value of the installer extlinux by doing something like 'echo $?' immediately afterwards. 0 is success.
-
IIRC this was fixed after the previous kernel release too, and I forgot to add it to sorter.sh. b44 is a wired card, please move ssb to base again Robert.
Done. Will be in rc2.
-
There are still some wbar problems when loading Xprogs ondemand:
http://forum.tinycorelinux.net/index.php/topic,12339.msg69076.html#msg69076 (http://forum.tinycorelinux.net/index.php/topic,12339.msg69076.html#msg69076)
-
I've been getting some practice in updating more frugal systems from tc4.1 to tc4.4rc1 lately. So far the most reliable method has been to make backups of filetool.lst and onboot.lst, then load up the latest tc-install and use that tool to install to an existing partition (using install boot loader option) and copy over new tcz's. After a reboot delete the existing boot directory and append the new filetool and onboot files as necessary from the old backed up versions and reboot.
I forgot something, run the tc-update and/or AppsAudit updates.
Also from 4.2 just realised these files needed updating. Since they are not in a backup only a permanent store, deleted them and rebooted.
.setbackground
.profile
.xsession
Not sure if I missed any other files?
Things are looking up now !
-
'Set' button at the lower-right corner of ScmBrowser is inactive, can't change path tp local repository. Same in TC 4.3
-
The Set button has only ever been active when the tcedir is on /tmp and the initial status bar displaying tcedir is red. No other purpose.