Tiny Core 3.0 Alpha 2 Testing

[curaga]

Is there a 3.0 version of firewall-2.6.29.1-tinycore.tcz? Perhaps  the name changed for 3.0?

Enjoying 3.0 alpha. Great work TC team!!!!

Best regards,

sci_fi

Yes, the new name is netfilter-xxx. Note that iptables might need an update, not sure if the 2.x iptables runs fine with the new kernel.

Pure idle curiosity: How did the team pick a kernel version?

Early plans were either .33 or .34. After .33 was stable, we tested it and the patchlevels, but faced oopses until 33.3.

[jano]

Boot errors in Tiny Core 3.0 Alpha 2 (not present in Alpha 1 or 2.10 or 2.11).
I have TC installed in an ext2 sd card, from which I boot. After the EXTLINUX greetings, usual boot messages, when loading the  Tiny Core Extension I get  error messages and after a while the system boots.
Things go very fast, so I have only been able to read something like:

/etc/init.d/rcS : line 460 : usleep : text file busy
repeated about 20 times
after taht, sometimes it says 'done' and continues booting, while other times I get another error message before the 'done' and booting.

After rebooting with syslog enabled, I've found the following messages:

daemon.err udevd-work[594] exec of program '/sbin/modprobe' failed 
daemon.err udevd-work[593] exec of program '/sbin/modprobe' failed 
.... up to 10 times total (with different numbers inside the brackets), and then:

daemon.err udevd-work[671] exec of program '/bin/sh' failed 
daemon.err udevd[93] can not read '/etc/udev/rules.d/56-lsusb.rules'
daemon.err udevd[93] can not read '/etc/udev/rules.d/64-md-raid.rules'

and then a lot of more info that seems normal to me (messages about mounting things from tce/optional)

I've booted several more times, and the syslog seems to vary:
* sometimes the daemon.err udevd-work[xxx] exec of program '/sbin/modprobe' failed are missing
* sometimes  the daemon.err udevd[93] can not read '/etc/udev/rules.d/56-lsusb.rules' or daemon.err udevd[93] can not read '/etc/udev/rules.d/64-md-raid.rules' is missing

Hope it helps

Replaced bzImage and tinycore.gz from alpha2 with a copy from alpha1 and all the errors are gone. Therefore I think there is clearly a problem with alpha2

[gerald_clark]

The b44 network driver is broken.
Excerpt from dmesg shown below.

Code: [Select]

b44: Unknown symbol ssb_device_is_enabled
b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable
b44: Unknown symbol ssb_bus_may_powerdown
b44: Unknown symbol ssb_dma_free_consistent
b44: Unknown symbol ssb_pcihost_register
b44: Unknown symbol ssb_device_disable
b44: Unknown symbol ssb_dma_alloc_consistent
b44: Unknown symbol ssb_dma_set_mask
b44: Unknown symbol ssb_device_enable
b44: Unknown symbol ssb_driver_unregister
b44: Unknown symbol __ssb_driver_register
b44: Unknown symbol ssb_bus_powerup
b44: Unknown symbol ssb_clockspeed
b44: Unknown symbol ssb_dma_translation


[curaga]

Ah, I was under the impression that only Broadcom wireless required ssb. Will add in the base for the next alpha.

[gerald_clark]

Thanks.

[roberts]

Moving on to alpha3