[driverloader] Suse 9.2 and broadcom BCM4306
Linuxant support (Jonathan)
support at linuxant.com
Tue Dec 7 09:50:18 EST 2004
after executing the 'ifup wlan0' command, can you see the 'wlan0'
interface in the output of the 'iwconfig' command? We can see that the
'ifup' script tries to replace the default route but it is quite
possible that if the default route was not already set, the command will
fail. Do you see a default route in the output of the 'ip route' command
just before you run the 'ifup wlan0' command?
If you require more assistance, please send at support at linuxant.com the
output of the following commands entered in a root shell while you are
close to the access point you are trying to connect to.
iwlist wlan0 scanning
ping www.linuxant.com -I wlan0 -c 5
ping 220.127.116.11 -I wlan0 -c 5
tail -f -n 30 /var/log/messages
Technical specialist / Linuxant
support at linuxant.com
Ian K. Harrell wrote:
> Hello everyone,
> Running into a slight problem....
> I was running a copy of Suse 9.0 for evaluating installing linux on a
> few of our laptops and had driverloader working with it.
> Decided to make a real go on one system and installed Suse 9.1
> Professional, did all the updates to Suse via "you" and then got the
> correct version of driverloader and installed it via rpm.
> When enter ifup wlan0 to activate the device I get the following error:
> wlan0 device: Broadcom Corporation BCM4306 802.11b/g Wireless
> LAN Controller (rev 03)
> wlan0 warning: using NO encryption
> ERROR: Error while executing:
> Command 'ip route replace to 169.254.0.0/16 dev wlan0' returned:
> RTNETLINK answers: No such device
> Configuration line: 169.254.0.0 - 255.255.0.0 wlan0
> SuSEfirewall2: Warning: no interface active
> SuSEfirewall2: Firewall rules successfully set from
> This is on a Dell Inspiron 1150 laptop with a minipci dell 1350 802.11g
> card. The dell 1350 card uses the broadcom 4306 driver or at least did
> when I had Suse 9.0 installed on the same computer.
> Also the command iwlist scan can see the wireless network so I am
> thinking that I have missed something with iwconfig and with me it is
> probably something simple.
> The iwconfig command I use is as follows:
> iwconfig wlan0 essid "fireman71" mode Managed nick "laptop1"
> and that is the same line I used under Suse9.0 when everything worked
> Is there something else I need to add or am I just missing something
> IK Harrell
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader