> > lspci shows this:
> >
> > 05:00.0 Network controller: Broadcom Corporation BCM4310 USB
> Controller
> > (rev 01)
>
> That does not seem to be a wireless LAN controller; it looks like the
> [14e4:4315] USB controller to me.
>
> What output do you get from
>
> lspci -nn | grep -Ei 'net|ether|wire|lan'
>
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-11-2008, 06:16 PM
David O'Toole
debian lenny on Acer Extensa 4420-5963
The bugreport i filed is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498612
On Thu, 2008-09-11 at 15:35 +0200, Florian Kulzer wrote:
> On Thu, Sep 11, 2008 at 09:11:31 -0400, David O'Toole wrote:
> > On Thu, 2008-09-11 at 10:07 -0300, Ricardo Ichizo wrote:
> > > On Thu, Sep 11, 2008 at 08:45:46AM -0400, David O'Toole wrote:
> > > > > >
> > > > > > The somewhat stale lenny netinst disc I had lying around did not
> > > > > > detect any of the laptop's network hardware
>
> [...]
>
> > > > I'm sorry I forgot to mention this---the boot log is from the successful
> > > > install with the later netinst CD, so the Marvell is detected just fine.
> > > > It's the wireless that I'm having trouble with now---nothing shows up in
> > > > dmesg...
> > > >
> > >
> > > What is the driver ?
> > >
> > > Do lspci or lshw commands show something ?
> > >
> >
> > lspci shows this:
> >
> > 05:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller
> > (rev 01)
>
> That does not seem to be a wireless LAN controller; it looks like the
> [14e4:4315] USB controller to me.
>
> What output do you get from
>
> lspci -nn | grep -Ei 'net|ether|wire|lan'
>
> ?
>
> --
> Regards, | http://users.icfo.es/Florian.Kulzer
> Florian |
>
>
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-11-2008, 06:24 PM
"Fabricio Cannini - Yahoo"
debian lenny on Acer Extensa 4420-5963
On Thursday 11 September 2008 10:47:09 David O'Toole wrote:
> Thanks for your help Ricardo. It sucks that I'll have to run an EXE but
> perhaps the 4310 will work sometime soon.
Hi David!
It seems you're out of luck right now:
http://www.linuxwireless.org/en/users/Drivers/b43#unsupported
But don't worry about .exes. Most of them are .zip or .cab files, and the other
ones can be extracted with the 'unshield' package.
Good luck!
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-11-2008, 06:26 PM
David O'Toole
debian lenny on Acer Extensa 4420-5963
On Thu, 2008-09-11 at 16:59 +0200, Florian Kulzer wrote:
> By the way: Right after I sent my earlier message I realized that I had
> not run update-pciids for a while. With an up-to-date PCI ID list, the
> description of [14e4:4315] has changed from "BCM4310 USB Controller" to
> "BCM4312 802.11b/g".
So, would this mean that the device is actually supported? It seems to
be at least partially supported at
http://wireless.kernel.org/en/users/Drivers/b43
What would be my next step?
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-11-2008, 07:09 PM
Florian Kulzer
debian lenny on Acer Extensa 4420-5963
On Thu, Sep 11, 2008 at 14:26:08 -0400, David O'Toole wrote:
> On Thu, 2008-09-11 at 16:59 +0200, Florian Kulzer wrote:
>
> > By the way: Right after I sent my earlier message I realized that I had
> > not run update-pciids for a while. With an up-to-date PCI ID list, the
> > description of [14e4:4315] has changed from "BCM4310 USB Controller" to
> > "BCM4312 802.11b/g".
>
> So, would this mean that the device is actually supported?
Well, the above only means that older versions of the PCI database had a
mistake in the device description. If you correct your own database by
running "update-pciids" as root then you should also see the correct
description the next time you run "lspci". At least we know now for sure
that you do have the 14e4:4315 (from what you posted in your other
message).
As I wrote in my earlier mail, the b43 uses a mechanism for identifying
supported devices that does not rely on the PCI IDs, and I unfortunately
do not know the details of how this "Sonics Silicon Backplane" subsystem
works.
> It seems to be at least partially supported at
> http://wireless.kernel.org/en/users/Drivers/b43
Indeed, it says that 2.4 GHz is supported for the BCM4312, and 802.11 b
and g are both based on the 2.4 GHz band AFAIK.
> What would be my next step?
I would try to load the module and check the syslog for messages, i.e.
modprobe -v b43
grep -i b43 /var/log/syslog
If your computer loads the module and then complains about missing
firmware then you know what you have to investigate next.
If your computer loads the module and produces another error message
then you have something to feed to Google and hope for the best.
If your computer loads the module without error message but does not
create a wireless device node (check with /sbin/iwconfig) then you may
have to try going via ndiswrapper as has already been suggested earlier.
In any case it is probably a good idea to post here what you get from
the syslog; maybe somebody else will have a better idea about what is
going on.
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-11-2008, 10:43 PM
David O'Toole
debian lenny on Acer Extensa 4420-5963
On Thu, 2008-09-11 at 21:09 +0200, Florian Kulzer wrote:
> I would try to load the module and check the syslog for messages, i.e.
>
> modprobe -v b43
>
> grep -i b43 /var/log/syslog
>
> If your computer loads the module and then complains about missing
> firmware then you know what you have to investigate next.
>
> If your computer loads the module and produces another error message
> then you have something to feed to Google and hope for the best.
>
> If your computer loads the module without error message but does not
> create a wireless device node (check with /sbin/iwconfig) then you may
> have to try going via ndiswrapper as has already been suggested earlier.
>
> In any case it is probably a good idea to post here what you get from
> the syslog; maybe somebody else will have a better idea about what is
> going on.
>
> --
> Regards, | http://users.icfo.es/Florian.Kulzer
> Florian |
>
>
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-12-2008, 06:26 PM
Florian Kulzer
debian lenny on Acer Extensa 4420-5963
On Thu, Sep 11, 2008 at 18:43:34 -0400, David O'Toole wrote:
> On Thu, 2008-09-11 at 21:09 +0200, Florian Kulzer wrote:
> > I would try to load the module and check the syslog for messages, i.e.
> >
> > modprobe -v b43
> >
> > grep -i b43 /var/log/syslog
> >
>
> monad:/home/dto# modprobe -v b43
> insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/input/input-polldev.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/net/wireless/cfg80211.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/net/mac80211/mac80211.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/char/hw_random/rng-core.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/net/rfkill/rfkill.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/ssb/ssb.ko
> insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/net/wireless/b43/b43.ko
> monad:/home/dto#
>
> Sep 11 18:41:06 monad kernel: [17374.556631] Broadcom 43xx driver loaded
> [ Features: PMLR, Firmware-ID: FW13 ]
> monad:/home/dto#
> monad:/home/dto# /sbin/iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
Looking at drivers/ssb/main.c, I think there has to be something like
this in the syslog when the ssb module is loaded:
Sonics Silicon Backplane found on PCI device 05:00.0
Do you see such a message? If it is absent then the SSB bus is not
recognized on your device.
I am not too optimistic now, because I found a MODULE_DEVICE_TABLE in
drivers/ssb/b43_pci_bridge.c which does not include your PCI device ID.
You could try to "modprobe b43_pci_bridge" if it is not loaded already,
but this is grasping at straws.
The general PCI ID table lists two different BCM4312 wlan adapters; it
seems that currently only the one with the device ID 0x4312 is
supported, while yours with the device ID 0x4315 is not.
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-12-2008, 06:58 PM
"Fabricio Cannini - Yahoo"
debian lenny on Acer Extensa 4420-5963
On Friday 12 September 2008 15:26:05 Florian Kulzer wrote:
> On Thu, Sep 11, 2008 at 18:43:34 -0400, David O'Toole wrote:
> > On Thu, 2008-09-11 at 21:09 +0200, Florian Kulzer wrote:
> > > I would try to load the module and check the syslog for messages, i.e.
> > >
> > > modprobe -v b43
> > >
> > > grep -i b43 /var/log/syslog
> >
> > monad:/home/dto# modprobe -v b43
> > insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/input/input-polldev.ko
> > insmod /lib/modules/2.6.26.5-rt8/kernel/net/wireless/cfg80211.ko
> > insmod /lib/modules/2.6.26.5-rt8/kernel/net/mac80211/mac80211.ko
> > insmod
> > /lib/modules/2.6.26.5-rt8/kernel/drivers/char/hw_random/rng-core.ko
> > insmod /lib/modules/2.6.26.5-rt8/kernel/net/rfkill/rfkill.ko
> > insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/ssb/ssb.ko
> > insmod /lib/modules/2.6.26.5-rt8/kernel/drivers/net/wireless/b43/b43.ko
> > monad:/home/dto#
> >
> > Sep 11 18:41:06 monad kernel: [17374.556631] Broadcom 43xx driver loaded
> > [ Features: PMLR, Firmware-ID: FW13 ]
> > monad:/home/dto#
> > monad:/home/dto# /sbin/iwconfig
> > lo no wireless extensions.
> >
> > eth0 no wireless extensions.
>
> Looking at drivers/ssb/main.c, I think there has to be something like
> this in the syslog when the ssb module is loaded:
>
> Sonics Silicon Backplane found on PCI device 05:00.0
>
> Do you see such a message? If it is absent then the SSB bus is not
> recognized on your device.
>
> I am not too optimistic now, because I found a MODULE_DEVICE_TABLE in
> drivers/ssb/b43_pci_bridge.c which does not include your PCI device ID.
> You could try to "modprobe b43_pci_bridge" if it is not loaded already,
> but this is grasping at straws.
>
> The general PCI ID table lists two different BCM4312 wlan adapters; it
> seems that currently only the one with the device ID 0x4312 is
> supported, while yours with the device ID 0x4315 is not.
>
> Check out this link dealing with ndiswrapper:
>
> http://www.linuxquestions.org/questions/linux-wireless-networking-41/bcm431
>5-card-no-wlan0-device-no-wireless-extensions-621795/
If this is of any help, here's the `lspci -v` output of my notebook with a
working BCM 4312 a/b/g card:
01:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02)
Subsystem: Hewlett-Packard Company Device 1370
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at b3000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [13c] Virtual Channel <?>
Capabilities: [160] Device Serial Number 1a-00-6b-ff-ff-73-bb-87
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Good luck!
--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
debian lenny on Acer Extensa 4420-5963
