Re: kernel versus broadcom wlan

2008-02-01 Thread Florian Kulzer
On Thu, Jan 31, 2008 at 20:58:32 -0700, wauhugo AT yahoo DOT com wrote: > Celejar wrote: [...] > Thank you. > According to this post > https://lists.berlios.de/pipermail/bcm43xx-dev/2008-January/006622.html > did I fetch the patch from > http://linuxwireless.org/download/b43/patch_2.6.24_for_

SOLVED: kernel versus broadcom wlan

2008-02-01 Thread [EMAIL PROTECTED]
Celejar wrote: [snip] The installation runs finally into this error: [...] Setting up linux-image-2.6.24-b43 (2.6.24-b43-10.00.Custom) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unrecognised device: /sys/devices/LNXSYSTM:00 yai

Re: kernel versus broadcom wlan

2008-02-01 Thread Celejar
On Thu, 31 Jan 2008 20:58:32 -0700 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: [snip] > According to this post > https://lists.berlios.de/pipermail/bcm43xx-dev/2008-January/006622.html > did I fetch the patch from > http://linuxwireless.org/download/b43/patch_2.6.24_for_4311_2 > and copied

Re: kernel versus broadcom wlan

2008-01-31 Thread [EMAIL PROTECTED]
Celejar wrote: The status of support for [9]4311 rev 02 cards is not entirely clear; Larry Finger (one of the devs) wrote on Sep. 24, 2007[0]: Harry Wert wrote: Don't know if this will help but it might. I am using a HP Pavillion dv9210 with AMD dual processor 64bit and 2G memory. It

Re: kernel versus broadcom wlan

2008-01-31 Thread Celejar
On Thu, 31 Jan 2008 09:54:34 -0700 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Just in case, that this information could be helpful. Here is the PCI > address of Broadcom WLAN interface: > > # lspci > 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan > mini-PCI (rev 02) Th

Re: kernel versus broadcom wlan

2008-01-31 Thread [EMAIL PROTECTED]
Just in case, that this information could be helpful. Here is the PCI address of Broadcom WLAN interface: # lspci 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02) - From /var

Re: kernel versus broadcom wlan

2008-01-30 Thread [EMAIL PROTECTED]
Florian Kulzer wrote: On Wed, Jan 30, 2008 at 16:36:00 -0700, wauhugo AT yahoo DOT com wrote: I think no output with "-v" means that the module was already loaded before the command was run. Maybe you could try to unload it ("modprobe -rv b43") and then reload it. If that does not lead to a

Re: kernel versus broadcom wlan

2008-01-30 Thread Florian Kulzer
On Wed, Jan 30, 2008 at 16:36:00 -0700, wauhugo AT yahoo DOT com wrote: > Florian Kulzer wrote: [...] >> Try to load the module manually (as root) with verbose messages: >> >> modprobe -v b43 >> >> Hopefully that will give us a clue. >> >> > There is NO OUTPUT from the "-v" option. But the mod

Re: kernel versus broadcom wlan

2008-01-30 Thread [EMAIL PROTECTED]
Florian Kulzer wrote: [...] Did you try to follow these instructions? http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Celejar posted this link earlier; it looks like a good source of information to me. [...] Yes, I have tried several firmware versions. The "bcm43xx" driver had

Re: kernel versus broadcom wlan

2008-01-30 Thread Florian Kulzer
On Wed, Jan 30, 2008 at 12:25:46 -0700, wauhugo AT yahoo DOT com wrote: > Florian Kulzer wrote: [...] >> The two bugzilla links above suggest that this chip will show up as two >> network interfaces when using the new driver, one is the interface that >> you will use normally and the other one is

Re: kernel versus broadcom wlan

2008-01-30 Thread [EMAIL PROTECTED]
Florian Kulzer wrote: Udev is responsible for managing the device nodes in /dev and the names of the network devices. More information is here: /usr/share/doc/udev/writing_udev_rules/index.html Thanks, I will have a look. The problem with the broadcom chip appears to be that the firmware is

Re: kernel versus broadcom wlan

2008-01-30 Thread [EMAIL PROTECTED]
Florian Kulzer wrote: Udev is responsible for managing the device nodes in /dev and the names of the network devices. More information is here: /usr/share/doc/udev/writing_udev_rules/index.html Thank you. I'll have a look. The two bugzilla links above suggest that this chip will show up as t

Re: kernel versus broadcom wlan

2008-01-30 Thread Florian Kulzer
On Wed, Jan 30, 2008 at 07:26:59 -0500, Celejar wrote: > On Wed, 30 Jan 2008 10:21:19 +0100 Florian Kulzer wrote: > > [snip] > > > The problem with the broadcom chip appears to be that the firmware is > > not present at the first boot of a Debian system, so only the master > > device is detected

Re: kernel versus broadcom wlan

2008-01-30 Thread Celejar
On Wed, 30 Jan 2008 10:21:19 +0100 Florian Kulzer <[EMAIL PROTECTED]> wrote: [snip] > The problem with the broadcom chip appears to be that the firmware is > not present at the first boot of a Debian system, so only the master > device is detected and added to z25_persistent-net.rules. This seem

Re: kernel versus broadcom wlan

2008-01-30 Thread Florian Kulzer
On Tue, Jan 29, 2008 at 18:00:42 -0700, wauhugo AT yahoo DOT com wrote: > Florian Kulzer wrote: >> The two b43* modules depend on the mac80211 stack instead of the >> ieee80211 one; with a self-compiled kernel and an older "inherited" >> configuration file you might first have to activate the new s

Re: kernel versus broadcom wlan

2008-01-29 Thread Angus Auld
--- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have got the Broadcom WLAN Chip BCM943111MCG in my > PC. > "b43-fwcutter" installed some firmware. > But it works in Debian SID with ndiswrapper only so > far. > But, you know, ndiswrapper imports parts of WINDOWS > into Debian. I don't > wa

Re: kernel versus broadcom wlan

2008-01-29 Thread [EMAIL PROTECTED]
Florian Kulzer wrote: The two b43* modules depend on the mac80211 stack instead of the ieee80211 one; with a self-compiled kernel and an older "inherited" configuration file you might first have to activate the new stack in "Networking > Wireless" to be able to select the b43* modules in "Device

Re: kernel versus broadcom wlan

2008-01-29 Thread Celejar
On Tue, 29 Jan 2008 11:11:19 -0700 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have got the Broadcom WLAN Chip BCM943111MCG in my PC. > "b43-fwcutter" installed some firmware. > But it works in Debian SID with ndiswrapper only so far. > But, you know, ndiswrapper imports parts of WINDOWS in

Re: kernel versus broadcom wlan

2008-01-29 Thread Celejar
On Tue, 29 Jan 2008 22:40:16 +0100 Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Tue, Jan 29, 2008 at 21:20:25 +0100, David Paleino wrote: > > Il giorno Tue, 29 Jan 2008 20:46:56 +0100 Florian Kulzer ha scritto: > > > > > According to /usr/share/misc/pci.ids your chip should have the vendor-ID >

Re: kernel versus broadcom wlan

2008-01-29 Thread Florian Kulzer
On Tue, Jan 29, 2008 at 21:20:25 +0100, David Paleino wrote: > Il giorno Tue, 29 Jan 2008 20:46:56 +0100 Florian Kulzer ha scritto: > > > According to /usr/share/misc/pci.ids your chip should have the vendor-ID > > 0x14e4 and the prodcut-ID 0x4311. Check with "lspci -nn" if this is > > correct; yo

Re: kernel versus broadcom wlan

2008-01-29 Thread David Paleino
Il giorno Tue, 29 Jan 2008 20:46:56 +0100 Florian Kulzer <[EMAIL PROTECTED]> ha scritto: > According to /usr/share/misc/pci.ids your chip should have the vendor-ID > 0x14e4 and the prodcut-ID 0x4311. Check with "lspci -nn" if this is > correct; you should see these numbers listed as "[14e4:4311]"

Re: kernel versus broadcom wlan

2008-01-29 Thread Florian Kulzer
On Tue, Jan 29, 2008 at 11:11:19 -0700, wauhugo AT yahoo DOT com wrote: > I have got the Broadcom WLAN Chip BCM943111MCG in my PC. > "b43-fwcutter" installed some firmware. > But it works in Debian SID with ndiswrapper only so far. > But, you know, ndiswrapper imports parts of WINDOWS into Debian.

kernel versus broadcom wlan

2008-01-29 Thread [EMAIL PROTECTED]
I have got the Broadcom WLAN Chip BCM943111MCG in my PC. "b43-fwcutter" installed some firmware. But it works in Debian SID with ndiswrapper only so far. But, you know, ndiswrapper imports parts of WINDOWS into Debian. I don't want that. Searching the web have I found, that there are two new Li