LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Gentoo
User Name
Password
Gentoo This forum is for the discussion of Gentoo Linux.

Notices


Reply
  Search this Thread
Old 02-26-2014, 01:13 PM   #1
kel_en
Member
 
Registered: Jun 2005
Location: Virginia, USA
Distribution: Slackware, Debian, MX
Posts: 125

Rep: Reputation: 17
Unable to use PCMCIA wireless card in Gentoo


I have a new install of Gentoo on an Averatec 3250 laptop. This machine has been running various Debian based Linux distributions for 8 years. I've been fighting wireless in Gentoo for several days with no success. The built-in wireless card has been hard blocked by RF-KILL since that "feature" was added to the kernel and continues to be hard blocked in Gentoo. Since the introduction of RF-KILL into the kernel, I have used a PCMCIA card, Linksys WPC54G, successfully but am unable to do so in Gentoo, so far. The card is properly identified by Gentoo as is shown in this last few lines of dmesg:

Code:
[   16.300139] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
[   16.300173] pci 0000:02:00.0: [14e4:4320] type 00 class 0x028000
[   16.300206] pci 0000:02:00.0: reg 10: [mem 0x00000000-0x00001fff]
[   16.300319] pci 0000:02:00.0: supports D1 D2
[   16.300323] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[   16.300519] pci 0000:02:00.0: BAR 0: assigned [mem 0x28000000-0x28001fff]
[   16.300538] pci 0000:02:00.0: cache line size of 32 is not supported
[   16.598210] systemd-udevd[11247]: renamed network interface eth0 to enp0s18
[   16.685486] systemd-udevd[11244]: renamed network interface lan0 to wlp0s9
[   16.743188] b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
[   16.743328] b43-pci-bridge 0000:02:00.0: setting latency timer to 64
[   16.743376] ssb: Found chip with id 0x4306, rev 0x03 and package 0x00
[   16.743385] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
[   16.743393] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
[   16.743400] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
[   16.743407] ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
[   16.743414] ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
[   16.747084] ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
[   16.867425] b43-phy1: Broadcom 4306 WLAN found (core revision 5)
[   16.920049] b43-phy1: Found PHY: Analog 2, Type 2 (G), Revision 2
[   16.980637] Broadcom 43xx driver loaded [ Features: PML ]
[   17.099583] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
I should mention that I get the same results in this Averatec laptop as I got a month ago when I converted my Thinkpad T30 to Gentoo and an identical WPC54G card. I received the same failure messages as I see in this Averatec machine. I chose to use the Thinkpad with an Ethernet cable.

This is the the error message that I get when I issue the command:
/etc/init.d/net.wlan0 start:

Code:
 * Caching service dependencies ...                                                 [ ok ]
  * Bringing up interface wlan0
  wlan0     no wireless extensions.

   *   Configuring wireless network for wlan0
   wlan0     no wireless extensions.

   Error for wireless request "Set Mode" (8B06) :
       SET failed on device wlan0 ; Operation not supported.
       Error for wireless request "Set Mode" (8B06) :
           SET failed on device wlan0 ; Operation not supported.
           Error for wireless request "Set Encode" (8B2A) :
               SET failed on device wlan0 ; Operation not supported.
               Error for wireless request "Set ESSID" (8B1A) :
                   SET failed on device wlan0 ; Operation not supported.
                    *   wlan0 does not support setting SSID to "richardlinksys"
                     *   Connecting to "richardlinksys" in managed mode (WEP Disabled) ...
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                    cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument
                     cat: /sys/class/net/wlan0/carrier: Invalid argument                                 [ !! ]
                      *   Failed to configure wireless for wlan0
                       * ERROR: net.wlan0 failed to start
This is my /etc/conf.d/net file, with the actual key and essid replaced by the terms <my-hex-key> and <my-essid> respectively:


Code:
config_enp0s18="192.168.1.68 netmask 255.255.255.0 brd 192.168.1.255"
routes_enp0s18="default via 192.168.1.2"
modules="iwconfig"
#mac_key_c0c1c0c25734="<my-hex-key>"
key_ESSID="<my-hex-key>"
config_wlan0="192.168.1.69 netmask 255.255.255.0 brd 192.168.1.255"
routes_wlan0="default via 192.168.1.2"
mode_wlan0="managed"
channel_wlan0="1"
#mac_essid_c0c1c0c25734="<my-essid>"
essid_wlan0="<my-essid>"
It is not possible to change any of the wlan0 parameters using iwconfig commands while booted into Gentoo. This was always possible in previously used distributions and is still possible with a Debian based live CD.

Since lspci indicates that my CardBus bridge is a 16-bit bridge, I followed the Gentoo WIKI instructions to create a file /etc/pcmcia/config.opts. That did not improve the situation.

I booted the machine into a recent Debian-based live CD which uses the same B43 firmware version as Gentoo and wireless worked fine. I copied the entire contents of the live CD /etc/pcmcia/ directory to the same directory in Gentoo with no improvement.

I feel like I must be missing something basic that is unique to Gentoo. I would be very grateful for any suggestions.
 
Old 02-26-2014, 05:02 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
I'm a long time out of practise on this, but IIRC You need a few things

1. A card bus driver(kernel module) to bring up the control chip.
2. A driver for the card.
3. Firmware as required (depends on driver).
4. Usually, there some config file needed in /etc/something.opts which describes this card. The pcmcia bus is not as advanced as pci in terms of configuration.

The card bus you will find with lspci. Does that have a driver in the logs? start that way. Also greop logs for 'firmware' and look for not found errors.
 
Old 02-27-2014, 02:21 AM   #3
i92guboj
Gentoo support team
 
Registered: May 2008
Location: Lucena, Córdoba (Spain)
Distribution: Gentoo
Posts: 4,083

Rep: Reputation: 405Reputation: 405Reputation: 405Reputation: 405Reputation: 405
Which firmware are you using? Most of the problems with broadcom cards are related to choosing the right firmware. I am using a similar chip and have installed sys-firmware/b43-firmware, which seems to work fine.

So, after those dmesg messages that you posted, you should be able to see some others related to the firmware loading process.

Code:
# dmesg|grep b43
[    5.057594] b43-pci-bridge 0000:0b:03.0: enabling device (0000 -> 0002)
[    5.385730] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[    5.392126] b43-phy0: Found PHY: Analog 2, Type 2 (G), Revision 2
[   15.826041] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   25.449045] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   25.923029] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Other than that, the card is correctly detected, so, if you get to the point where the firmware loads and still can't configure it properly, it could be something to do with the idiotic changes in the network naming scheme or something.
 
Old 02-27-2014, 06:58 AM   #4
kel_en
Member
 
Registered: Jun 2005
Location: Virginia, USA
Distribution: Slackware, Debian, MX
Posts: 125

Original Poster
Rep: Reputation: 17
Unable to use PCMCIA wireless card in Gentoo

I am using the b43 driver and have for years in various distributions. This is the relevant portion of dmesg from Gentoo when wireless fails:

Code:
grep b43 dmesg
[   16.848561] b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
[   16.848697] b43-pci-bridge 0000:02:00.0: setting latency timer to 64
[   16.915733] b43-phy1: Broadcom 4306 WLAN found (core revision 5)
[   16.970485] b43-phy1: Found PHY: Analog 2, Type 2 (G), Revision 2
[  196.830088] b43-phy1: Loading firmware version 666.2 (2011-02-23 01:15:07)
This is the same code from the live Debian-based CD run on the same day, when wireless works:
Code:
grep b43 dmesg
[   22.307935] b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
[   22.308013] b43-pci-bridge 0000:02:00.0: setting latency timer to 64
[   23.328822] b43-phy1: Broadcom 4306 WLAN found (core revision 5)
[   23.352245] b43-phy1: Found PHY: Analog 2, Type 2 (G), Revision 2
[   23.725470] Registered led device: b43-phy1::tx
[   23.725528] Registered led device: b43-phy1::rx
[   23.725585] Registered led device: b43-phy1::radio
[ 1128.902114] b43-phy2: Broadcom 4306 WLAN found (core revision 5)
[ 1128.924197] b43-phy2: Found PHY: Analog 2, Type 2 (G), Revision 2
[ 1128.959458] Registered led device: b43-phy2::tx
[ 1128.959651] Registered led device: b43-phy2::rx
[ 1128.959829] Registered led device: b43-phy2::radio
[ 1751.528143] b43-phy2: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1751.642905] b43 ssb0:0 wlan1: disabling HT/VHT due to WEP/TKIP use
Note that the firmware in both cases is the same verion. As can be seen, the live CD finds the device as both b43-phy1 and b43-phy2 and and registers both versions as led devices for tx, rx and radio which Gentoo does not.

Thanks for the reply.
 
Old 02-28-2014, 03:24 AM   #5
i92guboj
Gentoo support team
 
Registered: May 2008
Location: Lucena, Córdoba (Spain)
Distribution: Gentoo
Posts: 4,083

Rep: Reputation: 405Reputation: 405Reputation: 405Reputation: 405Reputation: 405
Yes, it's the same version. At this point, the only thing I can suggest is that you compare the config files for both kernels and see if you can deduct something from there.
 
Old 03-01-2014, 12:44 PM   #6
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
The B43 driver does not do WEP. It only does WPA encryption. WEP was past it when B43 was baing written.

I have one myself and ran into this before. You will not get through on WEP. Set your router to WPA and you should get going.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to connect Wireless WG511 pcmcia card toold Linux - Newbie 10 10-24-2010 02:20 PM
Unable to start up PCMCIA wireless card remcon Slackware 5 04-30-2009 04:16 AM
Gentoo Linux pcmcia wireless network ryudo Linux - Wireless Networking 3 03-09-2007 10:01 PM
Gentoo Install PCMCIA Xircom 2 Card Issues HayGuyyys Linux - Newbie 3 01-30-2007 11:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Gentoo

All times are GMT -5. The time now is 08:33 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration