On Dec 10, 2007 1:21 AM, James G. Sack (jim) <[EMAIL PROTECTED]> wrote:
> 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.)
Found /lib/firmware/bcm43xx_microcode11.fw which was an ASCII file
saying "this is a fake".
Looks like the fwcutter package got installed but not run. So I ran
it, and it put a bunch of stuff in /lib/firmware.
Second look. Last night's session installed all the bcm43xx drivers
in /lib/firmware/2.6.22-14-generic. The current running kernel is
2.6.22-14-generic which matches.
Looking at /var/log/messages, I see two consecutive lines:
. . . bcm43xx driver
. . . PCI: No IRQ known for interrupt pin A of device 0000.03:000.0
Please try using pci=biosirq.
Looking at the output of lspci I see that device 03:00.0 is Broadcom BCM4312
Tried adding pci=biosirq to the grub boot line, got the message right away:
PCI: unknown option biosirq
Google search for "pci=biosirq" doesn't help much. All references
seem to be 4 or more years old, which ks a long time in Linux years.
If it makes a difference, I am also using boot add-ons noapic
acpi=off. One or the other of these is necessary to keep the system
from hanging at boot time. But that's an orthogonal problem, I hope.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
