Tiny Core Base > Alpha Releases

Tiny Core v4.0 Alpha 2 Testing

<< < (3/7) > >>

hiro:
I don't see your problem. fltk 1.3 is already available in the repository.


--- Quote ---It supposedly offers Unicode support, and I did have small issues with special characters when browsing the Web, but in general, an update would not bring many benefits.
--- End quote ---
What browser are you using that is built against fltk 1.1?

hiro:
Has anybody tried building the core graphic apps statically against fltk 1.1?

netnomad:
hi roberts,

just that you are informed:
with alpha2 the b44-modul of my broadcast-wired-eth0 isn't loaded.

that's my dmesg in alpha2:
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)

with 3.8.4 it's loaded properly and my dmesg looks like that:
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.

Juanito:
I see two possibilities:

1. The ssb module needs to be loaded

or

2. The ssb module is loaded and it needs to be blacklisted (blacklist= boot code)

curaga:
Right, ssb should be in the base and not in the wireless extension.

Navigation

[0] Message Index

[#] Next page

[*] Previous page