On Wed, Mar 5, 2008 at 6:12 PM, Franz Apeltauer <franz.apeltauer@xxxxxx> wrote: > Luis R. Rodriguez schrieb: > > > Forced a new tarball out with new changes applied, would appreciate > > some testing on 2.6.21, 2.6.22. You can get the tarball from the > > usual place: > > http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 > > Thank you very much! > Now everything compiles fine on 2.6.22. > > I cannot send you test results yet. It looks like I have to read some > more documentation first. For now I can only tell you this: > > a) Test on a PC with a Broadcom 4306 rev 03: > - Downloaded and installed the firmware. > - The module b43legacy loads without errors, but nothing else happens. > ifconfig doesn't show any new interface, like eth0 or wlan0. > # modprobe b43legacy > => messages: Mar 5 23:14:02 af-nb-3 kernel: [10519.728000] Broadcom > 43xx driver loaded [ Features: PID, Firmware-ID: FW10 ] > => dmesg: [10519.728000] Broadcom 43xx driver loaded [ Features: PID, > Firmware-ID: FW10 ] > > Maybe this is important: dmesg says "Firmware-ID: FW10", but there is no > ucode10.fw in /lib/firmware/b43legacy, only 2, 4, 5, 11 (downloaded > today, as described in the wiki). > > # lsmod | grep 43 > b43legacy 102040 0 > ssb 36484 1 b43legacy > mac80211 220020 1 b43legacy > > # lspci > 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset > Host Bridge > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge > 00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g > Wireless LAN Controller (rev 03) > ... > > > b) Test on a PC with MSI PC54G2 ... RaLink rt2500 > You wrote "For now I'll disable rt2x00 in compat-wireless." > So, the result of this test seems to be unimportant (it tried to load > the old driver). You can test this now, I've enabled rt2x00 drivers by fixing dependencies on config.mk. Forced re-generation of new tarball based on latest updates too. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
