Wireless not working on Knoppix 6.7.1

[Alphonsu]

Hello,

That's in contrast to Knoppix 6.2.1 where Wireless works OK.

I just got delivery of Knoppix 6.7.1 DVD.
Hardware used:
Dell Alienware M17x laptop with
Wireless 1529 802.11n Half MiniCard

Knoppix 6.2.1 (kernel 2.6.32.6, udev-150) detects the wireless module,
loads the "wl" driver as device "eth1":
iwconfig -> eth1

Knoppix 6.7.1 (kernel 3.0.4, udev-172) loads the "wl" driver on boot but
iwconfig -> nothing (i.e., no wireless device detected)

In graphics mode (LXDE, for example) the applet "Wired network connection"
(bottom right icon), does not offer any wireless Access Points lists.
In the only other choice to "Wired Network", "VPN connections / Configure VPN",
it's impossible to add your wireless capability with this applet.
Whether in the "Wireless" tab or "VPN", even if you fill in the "questionnaires"
with your data, the "Save" button never gets activated.
Bottom line, you can NOT connect to your Access Point or any other.

By contrast, on the old Knoppix 6.2.1, the wireless AP's in the neighborhood
(including mine) are listed immediately, and then establishing the connection
presents no problems.
But then, here, on (auto) loading the "wl" driver, an "eth1" wireless device
is created, so you have a fighting chance to connect later on.

NOTE
In troubleshooting, I've tried to understand the mechanism used by Knoppix to
detect and create wireless devices.
Normally, one uses Udev rules (in /lib/udev/ or /etc/udev/, etc.) but you
couldn't find anything similar in Knoppix (for eth1 or wlan).
For example, a test wireless device, Linksys USB 802.11b, _is_ detected by
both Knoppix's as Atmel driver module "at76c50x_usb" and a corresponding
device "wlan0" does appear from somewhere (IMHO, the name "wlan0" is more
appropriate than "eth1", anyway).

Thanks

[utu]

My broadcom 802.11 a/b/g uses wl & connects to eth1 ok.
You might try g instead of n if you can.

[utu]

Also, FWIW, I notice this offering from Broadcom
with a relatively recent date on it.

http://www.broadcom.com/support/802.11/linux_sta.php

[Alphonsu]

Thank you for your comments but it seems you've missed the main point of the problem (and OP).
The "old" disk (Knoppix 6.2.1) sees the wireless card (be it a,b,g,n,x,y,z) and works with it seamlessly.
The "new", latest disk (Knoppix 6.7.1) does not recognize the card, and concequently the wireless does not work.
It's as simple as that. Let's not complicate it.
Thanks again.

[utu]

I note that I have 5.100.82.38-2 installed and it works ok for me, but that
5.100.82.112-4 is an available update for broadcom-STA-common on Synaptic.
You might also try that if you haven't already.

[Alphonsu]

Hi utu,
Thank you for your comments.
The main, and simple idea in my OP has been missed.
On the _same_ hardware (laptop - as described in the OP) the "old" 6.2.1 disk handles the wireless OK and seamlessly.
The new (latest) 6.7.1 disk cannot handle wireless at all (as described in more detail in OP).
It's as simple as that. Let's not make it any more complcated as this simple comparison, Good vs. Bad.
The point is for somebody to resolve this contradiction or to officialy declare the 6.7.1. disk faulty and fix it.
Thanks again.

[utu]

@ Alphonsu

I think there are a number of possibilities that something
may be different in your 6.7.1 and 6.2.1 set-ups, such as:
1. You might have a flawed 6.7.1 DVD;
2. You may have disabled your wifi;
3. You name it for some critical difference; and
4. You may indeed have discovered a 'special' case.

In my experience, 1 or 2 usually explain the situation.
I'm not aware of any such case 4 for 'wl' in Knoppix 6,
but I can't speak to the 'n' case.

Good luck on filing a bug report.

[Alphonsu]

Hi Utu,

Let's eliminate case no 1., where by "flawed" I assume you
imply a _physical_ problem of some sort (manufacture, shipping, etc.)

I start with the machine down, the wireless router up and running OK.

A. I insert the 6.2.1. disk.

B. I boot the machine all the way.
I connect wireless without any problems.

C. I shut down the machine.

D. I remove the 6.2.1 disc from the machine.

E. I insert the 6.7.1 disk.

F. I boot the machine all the way.
I can NOT connect wireless no matter what I do.

G. I shut down the machine.

H. I remove the 6.7.1 disc from the machine

I. I go back to step A.

I repeat the above loop 20 times.

I stop to write my OP where I describe the possible _technical_ differences
between the two discs the best I can. In the process I'm hoping to convey the notion
that I have some idea about the Linux system workings, and technical acumen in general.

I then, repeat the loop (starting at A) until I'm blue in the face.

Then I pause and try to pass along the idea that 6.7.1. is not bad physically
but bad technically, which would make it possibility no 5 on your list.
Please note that in running the 6.7.1. for some other functions,
I haven't discovered any "flaw" that might make the disc suspect physically.
Other than the simple (but critical for me) wireless failure the disc appears
functional.

Your case no 2, is not applicable (as described in the "A" loop above).
I do not understand your case no 3 (name?), not that it matters much by now.

As for your case no 4, there's nothing "special" here and if there's any
"discovery", it's just that for an identical configuration the 6.7.1 disc
does not work at all (instead of just working like the 6.2.1 one,
without any "special" considerations). For 6.2.1., the configuration
I've been using is (and appears to be detected by 6.2.1. as) just
run-of-the-mill, nothing special about it.

Thank you for your interest and comments.

BTW, I don't know how/where to file a bug report.
Maybe you can help. Basically the 6.7.1. is worthless for me.
The point is for somebody to identify the technical problem and fix it.

[klaus2008]

@Alphonsu

It could be helpful to know the PCI-ID of your wireless card. The command
lspci -vnn should give you the PCI-IDs of all installed PCI devices.

[utu]

I start with the machine down, the wireless router up and running OK.

A. I insert the 6.2.1. disk.

B. I boot the machine all the way.
I connect wireless without any problems.

C. I shut down the machine.

D. I remove the 6.2.1 disc from the machine.

E. I insert the 6.7.1 disk.

F. I boot the machine all the way.
I can NOT connect wireless no matter what I do.

G. I shut down the machine.

H. I remove the 6.7.1 disc from the machine

I. I go back to step A.

I repeat the above loop 20 times.


.
My first test is always to look for thumbprints.
A greasy thumbprint is enough to cause a DVD to 'be flawed'.

You can usually see thumbprints on the shiny side of a DVD
if you hold the DVD up to the light at the right angle.
Clean this with isopropyl alcohol & kleenex.

If this doesn't clear things up, then maybe the DVD is flawed
in manufacture. If the DVD is flawed in manufacture it will
not pass MD5 tests, and the supplier should replace it.

Most folks I'm sure do the md5 test first. I'm lazy; almost
all my flawed DVDs turn out to be thumbprint problems, so I
check that first.

[Alphonsu]

Hi Klaus,

Thank you for your interest (ant anticipated help).

Reference: my OP

INTRO:
In the following I got some readings (based on your request, lspci ...) on
both discs (6.2.1, the "old", good one and 6.7.1, the "new". bad one)
In so doing I went a little beyond the call of duty in anticipation of maybe
further questions.
The results should by rights be sent in an attachment, but I don't know how
to do it here (if at all possible). I apologize for any inconvenience.

DISC 6.2.1 (the good one)

[]$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:06.0 PCI bridge: Intel Corporation Core Processor Secondary PCI Express Root Port (rev 12)
00:19.0 Ethernet controller: Intel Corporation 82577LC Gigabit Network Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
02:00.0 VGA compatible controller: ATI Technologies Inc M98 XT [Mobility Radeon HD 4870]
02:00.1 Audio device: ATI Technologies Inc HD48x0 audio
06:00.0 Network controller: Broadcom Corporation Device 4353 (rev 01)
08:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
08:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
08:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01)
08:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

[]$ lspci -vvnnks 06:00:0
06:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4353] (rev 01)
Subsystem: Dell Device [1028:000e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f0800000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us
ClockPM+ Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [13c v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntrySize=0
Arb: Fixed- WRR32- WRR64- WRR128- 100ns- onfig- - - TableOffset=0
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Fixed- RR32-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 00-00-fe-ff-ff-94-c4-17
Capabilities: [16c v1] Power Budgeting <?>
Kernel driver in use: wl

[Alphonsu]

Hi Klaus (cont'd)

Disc 6.7.1 (the faulty one)

[]$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:06.0 PCI bridge: Intel Corporation Core Processor Secondary PCI Express Root Port (rev 12)
00:19.0 Ethernet controller: Intel Corporation 82577LC Gigabit Network Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
02:00.0 VGA compatible controller: ATI Technologies Inc M98 XT [Mobility Radeon HD 4870]
02:00.1 Audio device: ATI Technologies Inc HD48x0 audio
06:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
08:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01)
08:00.1 System peripheral: Ricoh Co Ltd Memory Stick Host Controller (rev 01)
08:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01)
08:00.3 FireWire (IEEE 1394): Ricoh Co Ltd FireWire Host Controller (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

[]$ lspci -vvnnks 06:00:0
06:00.0 Network controller [0280]: Broadcom Corporation BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Device [1028:000e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f0800000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us
ClockPM+ Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [13c v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 00-00-fe-ff-ff-94-c4-17
Capabilities: [16c v1] Power Budgeting <?>
Kernel driver in use: bcma-pci-bridge

[]$ modprobe -v bcma-pci-bridge
FATAL: Module bcma_pci_bridge not found.

[]$ lsmod | grep bcma
bcma 9051 0

[]$ lspci -k | grep wl

[]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

[]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:26:b9:fe:f9:63
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:f0e00000-f0e20000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)

[klaus2008]

Hi, Alphonsu!

Now we know that you have got a Broadcom BCM43224 wireless network card. This card should be supported by the Linux kernel module brcm80211 as you can find out by reading the web page brcm80211 (http://wiki.debian.org/brcm80211) in the Debian wiki. But if you read the configuration file /etc/modprobe.d/broadcom-sta-common.conf of Knoppix 6.7.1 you will find that this module is blacklisted in order to avoid conflicts with other kernel modules.

I would suggest that you issue
modprobe -r wl
modprobe brcm80211
chvt 12 in a root terminal and examine carefully the last lines of kernel messages. You can switch back to the desktop environment by pressing the key comination Alt-F5.

If the kernel module was loaded properly you could issue
iwconfigI hope this helps.

[Alphonsu]

Hi Klaus,

Thank you for your help.
As you can see from the following, I followed your suggestions but (still) no cigar.
IMHO, the 6.7.1 made some major changes in the way it deals with my wireless
card (thinking it would lead to progress) but failed in the process, as
evident in square one (bottom line, my OP).
If you don't mind, I made again a few extra tests (for progress? :).
I apologize for my constant "tardiness" but the authorities have been blocking my
replies for at least 12 hours, to check for cleanliness.
This also gives them a chance to allow utu to insert his insightful comments
during my "silence".
------

[]$ lsmod | grep wl
wl 1936903 0

[]$ modprobe -r wl
rmmod /lib/modules/3.0.4/kernel/drivers/net/wireless/wl.ko

[]$ lsmod | grep wl

[]$ modprobe -v brcm80211
FATAL: Module brcm80211 not found.

[]$ ls -og /etc/modprobe.d/
-rw-r--r-- 1 4891 Aug 27 2010 aliases.conf
-rw-r--r-- 1 281 Sep 6 2009 alsa-base-blacklist.conf
-rw-r--r-- 1 1183 Jun 2 2010 alsa-base.conf
-rw-r--r-- 1 41 Sep 16 2009 blacklist-capiutils.conf
-rw-r--r-- 1 108 Aug 22 10:13 blacklist-cups-usblp.conf
-rw-r--r-- 1 262 Jan 23 2011 blacklist-knoppix.conf
-rw-r--r-- 1 622 Jul 12 2010 blacklist.conf
-rw-r--r-- 1 249 May 16 2011 broadcom-sta-common.conf
-rw-r--r-- 1 456 Jul 12 2010 fbdev-blacklist.conf
-rw-r--r-- 1 30 Jul 3 15:56 hpsa.conf
-rw-r--r-- 1 23 Oct 28 2010 i915-kms.conf
-rw-r--r-- 1 25 Nov 11 2010 intelfb-knoppix.conf
-rw-r--r-- 1 22 Apr 5 2009 kqemu-common.conf
-rw-r--r-- 1 16 Sep 23 2009 libpisock9.conf
lrwxrwxrwx 1 41 Nov 4 2010 linux-sound-base_noOSS.conf ->
/lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r-- 1 98 Apr 2 2009 mt-st.conf
-rw-r--r-- 1 38 Jan 31 2011 nouveau-kms.conf
lrwxrwxrwx 1 21 Mar 31 2009 oss-compat.conf -> /lib/oss-compat/linux
-rw-r--r-- 1 51 Jan 14 2011 psb.conf
-rw-r--r-- 1 26 Nov 5 2010 radeon-kms.conf

[]$ cat /etc/modprobe.d/broadcom-sta-common.conf
# wl module from Broadcom conflicts with ssb
# We must blacklist the following modules:
blacklist b44
blacklist b43legacy
blacklist b43
blacklist brcm80211
blacklist brcmsmac
blacklist ssb
install wl /sbin/modprobe --ignore-install wl $CMDLINE_OPTS

[]$ find /lib/modules/3.0.4/kernel/drivers -name "brcm*.ko"
/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/brcmfmac/brcmfmac.ko
/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/brcmsmac/brcmsmac.ko
/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/util/brcmutil.ko

[]$ ls -ogR /lib/modules/3.0.4/kernel/drivers/staging/brcm80211/
/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/:
drwxr-xr-x 2 2048 Sep 8 20:26 brcmfmac
drwxr-xr-x 2 2048 Sep 8 20:26 brcmsmac
drwxr-xr-x 2 2048 Sep 8 20:26 util

/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/brcmfmac:
-rw-r--r-- 1 179484 Sep 8 03:38 brcmfmac.ko

/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/brcmsmac:
-rw-r--r-- 1 568024 Sep 8 03:38 brcmsmac.ko

/lib/modules/3.0.4/kernel/drivers/staging/brcm80211/util:
-rw-r--r-- 1 13100 Sep 8 03:38 brcmutil.ko

[]$ modprobe brcmfmac

[]$ lsmod | grep brcm
brcmfmac 129669 0
cfg80211 105480 1 brcmfmac
brcmutil 4463 1 brcmfmac

[]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

[]$ modprobe brcmsmac

[]$ lsmod | grep brcm
brcmsmac 481998 0
mac80211 155646 1 brcmsmac
brcmfmac 129669 0
cfg80211 105480 3 brcmsmac,mac80211,brcmfmac
brcmutil 4463 2 brcmsmac,brcmfmac

[]$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

# For completeness, a quick:
[]$ ls /lib/modules/3.0.4/kernel/drivers/net/wireless
adm8211.ko
airo.ko
airo_cs.ko
at76c50x-usb.ko
ath
atmel.ko
atmel_cs.ko
atmel_pci.ko
b43legacy
hostap
ipw2x00
iwlegacy
iwlwifi
iwmc3200wifi
libertas
libertas_tf
mac80211_hwsim.ko
mwifiex
mwl8k.ko
orinoco
p54
prism54
ray_cs.ko
rndis_wlan.ko
rt2x00
rtl818x
rtlwifi
wl.ko
wl1251
wl12xx
wl3501_cs.ko
zd1201.ko
zd1211rwbrcm*.ko

[klaus2008]

My next attempt would be based on the section Wheezy (http://wiki.debian.org/wl#Wheezy) of the web page wl (http://wiki.debian.org/wl) of the Debian wiki.

0. You need the Knoppix 6.7.1 DVD and a working internet connection.

1. Open a terminal and issue
sudo leafpad /etc/apt/apt.conf.d/00knoppix Find the line
APT::Default-Release "squeeze"; and change it to
APT::Default-Release "wheezy"; Save the file and exit leafpad.

2. Issue
sudo apt-get update
sudo apt-get install broadcom-sta-common
sudo m-a prepare
sudo m-a a-i broadcom-sta This will create and install the new package /usr/src/broadcom-sta-modules-3.0.4_5.100.82.112-4+3.0.4-10.00.Custom_i386.deb I would copy this file and /var/cache/apt/archives/broadcom-sta-common_5.100.82.112-4_all.deb to a USB stick for further usage. If you need these packages again you could install them by using the dpkg program.

3. Issue
sudo modprobe -r brcmfmac
sudo modprobe -r brcmsmac if the kernel modules brcmfmac and brcmsmac are still loaded. Then issue
sudo modprobe -r wl
sudo modprobe wl
iwconfig

[Alphonsu]

Hi Klaus,

Thank you for the help.
Unfortunately, the new procedure failed as well.
I followed your instructions to the letter, but on the final (and critical) step,
iwconfig
there's still no output with a wireless device.

The procedure you recommended does create a new "wl.ko" module, size 2623850
but on loading, wl does not create a device /dev/wlan0 (or some such, like
/dev/eth1) as expected so iwconfig output remains empty of any wireless device.

Any other ideas? As I said, on 6.2.1 disc, "wl" works so smoothly (as it should)
in creating a wireless device.
With an unfortunate name to be sure, eth1, but what's in a name these days!

PS The Dell Alienware M17x product (and its wireless module) came out on the
market two years ago. I cannot imagine the driver for it bacame obsolete (and bad)
(in Linux, things work the other way around normally, two years might be
too _new_ for a device to have a driver for it yet! )

[klaus2008]

Hi, Alphonsu!

If you read http://www.broadcom.com/docs/linux_sta/README.txt you can find a list of the devices supported by the driver. Since your wireless card is on the list I do not understand why you did not succeed.

I would remaster Knoppix with the latest Linux kernel and repeat the two procedures. Be aware that compiling a new Linux kernel is really time consuming because you have to answer many questions. But if you do not have the time to do so I would suggest that you use the old Knoppix 6.2.1 until the next release of Knoppix.

[fongpwf]

This does not seem to work on 6.7.1. The b43 module seems to be missing.

sudo modprobe b43
FATAL: Module b43 not found.In /lib/modules/3.0.4/kernel/drivers/net/wireless/ there is b43legacy but not b43.

[Alphonsu]

Hi Klaus,

Now I finally understand why our elders (and some webmasters)
keep beating it into our heads, "RTFM".

As soon as I hit the link you gave me,
I noticed the "manual",

Broadcom Linux hybrid wireless driver
Version 5.100.82.1XX,

clearly states at some point,

<<
lsmod | grep "b43\|ssb\|bcma\|wl"

if any of these are installed, remove them
>>

Of those three, "bcma" happens to be up on this machine for some reason.
Once removed and "wl" reloaded, the wireless started humming
its sweet tune ("eth1". OK, maybe not so sweet after all,
but let's not be too picky).

Thank you very much for your time and invaluable help.

[tmq]

I note that I have 5.100.82.38-2 installed and it works ok for me, but that
5.100.82.112-4 is an available update for broadcom-STA-common on Synaptic.
You might also try that if you haven't already.

Do I understand you to suggest a broadcom driver update (for A's problem)? I ask because I've been unable to connect to a wireless network under 6.7.1. It tries, then it loops through & requests my pw again, and again, etc. In my case the machine is a Dell 1545 about 4-5 years old. I'd appreciate any help.

[utu]

@ tmq

I just noticed your post.
Sorry, I had turned off my notifications on this thread.

If you are being 'asked for a pw' , then perhaps you already have installed the driver,
but are just not using the right security id for your router.

Tell us more about just what's going on.
Also see what lspci | grep BCM says, and lsmod | grep wl.

[utu]

Having reviewed this thread, I offer this summary, FWIW.

I have a Dell 1545 that's about two years old. It has a Broadcom wifi
which uses the wl driver. Knoppixes from 6.2 through 6.7.1, luckily
for me, work without any attention on my part to identify and to
install this driver. Very few other Linuxes do so without a LOT of
extra effort.

However, I observe that getting the right match for a Broadcom wifi
can be a tricky matter. I recommend the following reference in sorting
this out, at least insofar as deciding which Dells work with wl:
http://www.broadcom.com/docs/linux_sta/README.txt

In my case, lspci -n | grep 14e4 gives 0c:00.0 0280: 14e4:4315 (rev 01)
and I did not need to dis-install any other drivers nor change any
blacklists.

This thread shows how Alphonsu worked through this problem for a
situation that required actually removing some conflicting drivers
as suggested in the Broadcom reference. His post #19 seems to spell-out
the secret to solving his problem.

If all else fails, perhaps a personal message to Klaus2008 may get
you some competent and patient help.

[tmq]

I greatly appreciate the help; in the end I concluded Knoppix would fit well as my desktop's 2nd linux OS. Even so, I'm sure I'll have more questions in the future ;)

[utu]

@ tmq

Nice to hear your appreciation,
but can't imagine Knoppix as #2.
;D

[Werner P. Schulz]

Why not #2?

Knoppix cannot handle users, does not use passwords and isn't designed for security updates.

[utu]

Greetings, Werner.

I can't imagine Knoppix as my #2 Linux.
It best meets my needs & lack of expertise.

I think your comment may be the best short answer
to the question of how Knoppix & Debian are different.

I can imagine more expert Linux users, certainly commercial
and professional users, may have other first choices.

Also, I count on you, KK and a few others on this
forum to keep me out of trouble.

[ChriguK]

Hi everyone,

Tried to make Broadcom BCM43224 work on Knoppix 7.0.2 on a USB stick, but could install broadcom-sta-common using


sudo apt-get update
sudo apt-get install broadcom-sta-common
sudo m-a prepare
sudo m-a a-i broadcom-sta

This is my buildlog:



for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/3.3.7/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/3.3.7/g ;s/#KVERS#/3.3.7/g ; s/_KVERS_/3.3.7/g ; s/##KDREV##/3.3.7-10.00.Custom/g ; s/#KDREV#/3.3.7-10.00.Custom/g ; s/_KDREV_/3.3.7-10.00.Custom/g ' < $templ > ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean KBUILD=/usr/src/linux KVERS=3.3.7
Kernel architecture is X86_32
make[1]: Entering directory `/usr/src/modules/broadcom-sta'
KBUILD_NOPEDANTIC=1 make -C /lib/modules/3.3.7/build M=/usr/src/modules/broadcom-sta clean
make[2]: Entering directory `/usr/src/linux-headers-3.3.7'
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_32
make[2]: Leaving directory `/usr/src/linux-headers-3.3.7'
make[1]: Leaving directory `/usr/src/modules/broadcom-sta'
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/broadcom-sta'
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/3.3.7/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/3.3.7/g ;s/#KVERS#/3.3.7/g ; s/_KVERS_/3.3.7/g ; s/##KDREV##/3.3.7-10.00.Custom/g ; s/#KDREV#/3.3.7-10.00.Custom/g ; s/_KDREV_/3.3.7-10.00.Custom/g ' < $templ > ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean KBUILD=/usr/src/linux KVERS=3.3.7
Kernel architecture is X86_32
make[2]: Entering directory `/usr/src/modules/broadcom-sta'
KBUILD_NOPEDANTIC=1 make -C /lib/modules/3.3.7/build M=/usr/src/modules/broadcom-sta clean
make[3]: Entering directory `/usr/src/linux-headers-3.3.7'
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_32
make[3]: Leaving directory `/usr/src/linux-headers-3.3.7'
make[2]: Leaving directory `/usr/src/modules/broadcom-sta'
make[1]: Für das Ziel »kdist_config« ist nichts zu tun.
dh_testdir
dh_testroot
dh_prep
# Build and install the module
make -C /usr/src/linux M=/usr/src/modules/broadcom-sta
make[2]: Entering directory `/usr/src/linux-headers-3.3.7'
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_32
LD /usr/src/modules/broadcom-sta/built-in.o
CC [M] /usr/src/modules/broadcom-sta/src/shared/linux_osl.o
CC [M] /usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.o
CC [M] /usr/src/modules/broadcom-sta/src/wl/sys/wl_iw.o
CC [M] /usr/src/modules/broadcom-sta/src/wl/sys/wl_cfg80211.o
LD [M] /usr/src/modules/broadcom-sta/wl.o
Building modules, stage 2.
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_32
MODPOST 1 modules
CC /usr/src/modules/broadcom-sta/wl.mod.o
LD [M] /usr/src/modules/broadcom-sta/wl.ko
make[2]: Leaving directory `/usr/src/linux-headers-3.3.7'
install -D -m 0644 wl.ko debian/broadcom-sta-modules-3.3.7/lib/modules/3.3.7/kernel/drivers/net/wireless/wl.ko
dh_installdocs
dh_installchangelogs
dh_installmodules
dh_compress
dh_fixperms
dh_installdeb
dh_gencontrol -- -v5.100.82.112-7+3.3.7-10.00.Custom
dh_md5sums
dh_builddeb --destdir=/usr/src
dpkg-deb: Paket »broadcom-sta-modules-3.3.7« wird in »/usr/src/broadcom-sta-modules-3.3.7_5.100.82.112-7+3.3.7-10.00.Custom_all.deb« gebaut.
make[1]: Leaving directory `/usr/src/modules/broadcom-sta'
/usr/bin/make -f debian/rules kdist_clean
make[1]: Entering directory `/usr/src/modules/broadcom-sta'
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/3.3.7/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/3.3.7/g ;s/#KVERS#/3.3.7/g ; s/_KVERS_/3.3.7/g ; s/##KDREV##/3.3.7-10.00.Custom/g ; s/#KDREV#/3.3.7-10.00.Custom/g ; s/_KDREV_/3.3.7-10.00.Custom/g ' < $templ > ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean KBUILD=/usr/src/linux KVERS=3.3.7
Kernel architecture is X86_32
make[2]: Entering directory `/usr/src/modules/broadcom-sta'
KBUILD_NOPEDANTIC=1 make -C /lib/modules/3.3.7/build M=/usr/src/modules/broadcom-sta clean
make[3]: Entering directory `/usr/src/linux-headers-3.3.7'
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
Kernel architecture is X86_32
CLEAN /usr/src/modules/broadcom-sta/.tmp_versions
CLEAN /usr/src/modules/broadcom-sta/Module.symvers
make[3]: Leaving directory `/usr/src/linux-headers-3.3.7'
make[2]: Leaving directory `/usr/src/modules/broadcom-sta'
make[1]: Leaving directory `/usr/src/modules/broadcom-sta'
Build time: 33 seconds

Also tried to install via broadcom-sta-dkms following http://http://wiki.debian.org/wl#Wheezy - but the initial ramdisk could not be updated.

The same procedure worked fine on a Debian install.

Any hints? Cheers

[utu]

Greetings, ChriguK

Your report is important for us to fully understand. Please stay with us.

First, confirm that Knoppix 7 did not automatically install a working driver
for your Broadcom wifi.

Second, why are you trying to use the STA driver? Have you used this driver
in the past and found that it worked ok for you?

[utu]

Greetings again, ChriguK.

I think I can help you. Please refer to this confusing reference:
http://linuxwireless.org/en/users/Drivers/b43/

What it says is the Broadcom 43224 works with BOTH b43 and wl drivers.
You probably know the wl driver works for you and it's a lot easier to
get it working with wl. That was the case with Knoppix 6.7.
Knoppix 6.7 favored wl for this reason.

Knoppix 7 tries to accommodate all or most Broadcom units and
does so by eliminating the wl-driver category. We felt safe in doing
this based on the reference above. If you stare at the table long
enough I think it says there are NO cases which require wl that are
not, in principle, ok with b43, given the availability of the required
firmware.

The hitch I think you have run into is that if you insist on installing
wl yourself, said installation will blacklist the b43 driver that is
probably just fine for your hardware. Things just go downhill from
there.

I suggest you start over and see if Knoppix 7 can't install b43 and
get you going on your way. Forget what you know about wl.

Get back to us on this either way.