|
Crunchbang Statler (Debian Squeeze), Liquorix, and bcm43xx
This is taken from my posts over at the crunchbang linux forums [new user link].
When I install the latest crunchbang on my laptop (fresh install, debian squeeze based), run the cb-welcome script, update everything, and install liquorix, my wireless card breaks. My wireless card is the bcm4312 card with the built in bluetooth. It works fine up until i reboot into the liquorix image. Architecture is amd64. Things I have tried:
The card works fine before the liquorix install, but not after. Even the blue LED on the wireless status indicator fails to come on; it stays orange (meaning the wireless card is off or disabled). I am positive my chipset is the bcm 4312 with integrated bluetooth. I have searched around forums for days and nothing has provided a fix. I followed the same how-to and experienced the same errors as posted on these (liquorix) forums [new user link]: I could not get the broadcom-sta package to compile at step 4: :: Quote ::
4. Build and install a broadcom-sta-modules-* package for your system, using Module-Assistant: m-a a-i broadcom-sta So instead I downloaded the 64-bit driver source myself from the broadcom site [new user link] .(version 5.100.82.38 [new user link]). Then compiled using make, and manually installed the driver by replacing wl.ko in /lib/modules/ and rebooting to no avail. My card works fine in the original amd64 kernel, but not after I compile and install the driver for the 2.6.36-3.dmz.2-liquorix-amd64 kernel. It seems that either liquorix or my limited knowledge and experience is breaking things here. Any ideas? < Edited by speckled :: Feb 25, 11, 21:39 > Back to top |
|||||
|
post the output of: lspci -nn
just so the exact hardware in your system can be accurately seen. Or: inxi -N will show a lot of it, but not as complete as lspci. always better to know what's being seen by the kernel than to assume Back to top |
|||||
|
command:
sudo lspci > lspci.txt :: Code :: 00:00.0 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller [10de:0547] (rev a2)
00:01.0 ISA bridge [0601]: nVidia Corporation MCP67 ISA Bridge [10de:0548] (rev a2) 00:01.1 SMBus [0c05]: nVidia Corporation MCP67 SMBus [10de:0542] (rev a2) 00:01.2 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller [10de:0541] (rev a2) 00:01.3 Co-processor [0b40]: nVidia Corporation MCP67 Co-processor [10de:0543] (rev a2) 00:02.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:02.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:04.0 USB Controller [0c03]: nVidia Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:04.1 USB Controller [0c03]: nVidia Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:06.0 IDE interface [0101]: nVidia Corporation MCP67 IDE Controller [10de:0560] (rev a1) 00:07.0 Audio device [0403]: nVidia Corporation MCP67 High Definition Audio [10de:055c] (rev a1) 00:08.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Bridge [10de:0561] (rev a2) 00:09.0 IDE interface [0101]: nVidia Corporation MCP67 AHCI Controller [10de:0550] (rev a2) 00:0a.0 Ethernet controller [0200]: nVidia Corporation MCP67 Ethernet [10de:054c] (rev a2) 00:0c.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0d.0 PCI bridge [0604]: nVidia Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:12.0 VGA compatible controller [0300]: nVidia Corporation C67 [GeForce 7150M / nForce 630M] [10de:0531] (rev a2) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:09.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) 01:09.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22) 01:09.2 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12) 01:09.3 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 12) 04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Back to top |
|||||
|
The broadcom 4312lp-phy (aka 4315) doesn't work with liquorix kernels on the broadcom sta (wl) drivers for whatever reason. It works with the b43 lp-phy driver though, but only in PIO-only mode. I used the info here to get mine working:
ubuntuforums.org/showthread.php?t=1266620 Here's my thread about it from a while ago: techpatterns.com/forums/about1692.html Back to top |
|||||
|
Thanks, tulan, I tried just the instructions you provided and still could not get it to work; even the LED still does not come on. The frustrating part is it works with the debian default kernel out of the box.
Back to top |
|||||
|
You said it's working on the default Debian kernel; is that with the broadcom-sta driver or the b43-lpphy driver?
The reason I ask is, it's pretty easy to get conflicting modules loaded when fighting with Broadcom drivers - b43 and the broadcom-sta driver (or 'wl', that's the name the kernel module uses) don't play well together. To check which module is loaded, you can do: :: Code :: lsmod | grep 'wl\|b43'(Do that on the Debian kernel when it's working, please.) Under normal circumstances, you would want that to return one or the other, but not both. But, as I said before, I'm pretty sure the wl driver will not work with that chip and a Liquorix kernel. I tried all manner of blacklisting, modprobing, I even tried changing a bunch of stuff in the kernel config and rebuilding my own liquorix-based kernel, all to no avail. And at that point building the module (m-a a-i broadcom-sta) completed with no errors - some more recent changes broke that apparently. So if it's working with the b43-lpphy driver on the Debian kernel but not Liquorix, I'm not sure what to say. But if you're still using the wl driver, I'd be happy to try to help you get the b43-lpphy driver working. Even if I pretty much hate the Broadcom 4315's guts. What can I say, mine's been working for months now. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||