Carl Lowenstein wrote: > I have just installed Ubuntu 7.10 (gutsy) on my Compaq AMD64 laptop. > Used the "Restricted Drivers Manager" to install the Broadcom driver. > It seems to have automated all the fwcutter stuff. Using the GUI > "network-admin" I set the SSID and WEP key and tried to activate eth1. > But I still can't get a connection to my wireless access point. > > $ sudo /sbin/iwconfig eth1 # gives back the values I set with > network-admin > > The relevant kernel modules installed (selected from lsmod output) are: > ieee80211softmac 34944 1 bcm43xx > ieee80211 38344 2 bcm43xx,ieee80211softmac > ieee80211_crypt 8192 2 ieee80211_crypt_wep,ieee80211 > > I did not look at lsmod output before doing the driver installation, > so I don't know if something changed. > > What steps have I missed?
dmesg has no complaints about firmware when it boots? or loads the bcm43xx module? Last week, there were shellscripts installed by the package that had to be run manually to install the firmware files into /lib/firmware. The bmb43xx-fwcutter package, if I remember correctly, had a file named like *install*.sh, and when I ran it, it extracted firmware from a tarball and dumped it into the lib/firmware dir. (something like that.) I was puzzled because sometimes the "Restricted Drivers Manager" seemed to _just work_, and sometimes not. Sorry I don't have a clearer picture. But one thing is sure, the device doesn't work without a firmware infusion. One clue to that is trying to run # ifconfig eth1 up ..... (or wlan0, or whatever) gives an error if there's no firmware. With firmware that works fine, as well as # iwlist eth1 scan >From that point on, only configuration nightmares remain. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
