Core v4.4rc1

[roberts]

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

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

[roberts]

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.

[nim108]

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. 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.

[roberts]

Updated change log. Thanks and thanks for help in testing the new features.

[AbNoRMiS]

works perfect on my compaq evo d500 with 512mb ram
though i don't use scm for practical purpose except test

[AbNoRMiS]

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

[coreplayer2]

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....

[AbNoRMiS]

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

[coreplayer2]

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  

I guess this is a result of bypassing a couple of upgrades

[thane]

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).

[curaga]

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.

[netnomad]

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

[gerald_clark]

You will need to copy over the wireless-3.0.21-tinycore.tcz.

[nim108]

...
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.

[netnomad]

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"...