Tiny Core Base > Release Candidate Testing

Core v4.4rc1

<< < (3/6) > >>

curaga:

--- Quote ---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.
--- End quote ---

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:

--- Quote from: coreplayer2 on February 26, 2012, 12:58:56 AM ---...
Rebooted again to "udevadm settle timeout" error message...

clearly have missed something...

Ok one more time....

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page