Suse linux wireless issues

English Network/Internet
#1

Hello All,

I have a Dell desktop computer that initially had only Windows XP on it. I wanted to challenge myself to split the OS into windows and Linux and was able to do so. Here is my problem. I have a wireless adapter (Airlink 101 AWLL6070) attached to the computer. When I log into the windows OS, I’m able to connect to the internet without any issues. However, when I log into the LINUX OS, I’m unable to connect to the internet at all. How can I get my LINUX OS to connect to the internet? Any guidance is appreciated.

Thanks.
Bagheera

#2

On 06/03/2013 09:26 PM, bagheerabirdy wrote:
>
> Hello All,
>
> I have a Dell desktop computer that initially had only Windows XP on
> it. I wanted to challenge myself to split the OS into windows and Linux
> and was able to do so. Here is my problem. I have a wireless adapter
> (Airlink 101 AWLL6070) attached to the computer. When I log into the
> windows OS, I’m able to connect to the internet without any issues.
> However, when I log into the LINUX OS, I’m unable to connect to the
> internet at all. How can I get my LINUX OS to connect to the internet?
> Any guidance is appreciated.

As we have no idea what an Airlink 101 AWLL6070 is, we cannot answer the
question. The problem might be as simple as “the firmware is missing” to as
severe as “there is no Linux driver for the device”. How do you tell us? As the
stickies in this forum (which you should read) state very clearly, the results
of “/sbin/lspci -nn” for PCI devices, or “lsusb” for USB devices contain the answer.

#3

My apologies. I read through some of the wonderful information that I found at the stickies location.

After reading through the same, I’ve obtained the system information using the collectNWData.sh script. Please see below. Hope this helps.


collectNWData.sh V0.6.11 (Rev: 1.368, Build: 2013/05/19 17:41:39 UTC)
--- Which type of your network connection should be tested?
--- (1) Wireless connection (WLAN)
--- What's the type of networktopology?
--- (2) WLAN HW router <---> LinuxClient
--- On which host is the script executed?
--- (1) LinuxClient
--- WLAN SSID to connect to: §§§§§§§§1
--- NWEliza is analyzing the system for common network configuration errors ...
!!! CND0550W: Unable to detect USB network card for the selected connection type
!!! CND0400W: Alternate modules detected for interface
!!! CND0230W: IPV6 enabled
!!! CND0240E: networkmanager for network configuration enabled but a YAST network card configuration for eth0 exist
--- Go to http://www.linux-tips-and-tricks.de/CND#English to get more detailed instructions 
--- about the error/warning messages and how to fix the problems on your own.
--- If you are unsuccessful then place the contents of file in the net
--- (see http://www.linux-tips-and-tricks.de/CND_UPL#English for links) 
--- and then paste the nopaste link on your favorite Linux forum.
==================================================================================================================
===== cat /etc/*-_]release || cat /etc/*-_]version =============================================================
/etc/SuSE-release
openSUSE 11.1 (i586)
VERSION = 11.1
===== uname -a ===================================================================================================
Linux linux-1oxp 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux
===== cat /etc/sysconfig/network/ifcfg-[earwd]* | grep -v "=''" ==================================================
--- /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='dhcp'
STARTMODE='onboot'
===== ping tests =================================================================================================
Ping of 173.194.35.180 failed
ping: unknown host [www.google.com](http://www.google.com)
Ping of [www.google.com](http://www.google.com) failed
===== cat /etc/resolv | grep -i "nameserver" =====================================================================
===== cat /etc/hosts =============================================================================================
127.0.0.1       localhost
127.0.0.2       linux-1oxp.site linux-1oxp
===== (route -n && route -A inet6 -n) | egrep "(eth|ath|ra|wlan|dsl|ppp)" ========================================
===== ifconfig (filtered for eth|wlan|ra|ath|dsl|ppp) ============================================================
eth0      Link encap:Ethernet  HWaddr ##:##:##:##:##:#1  
          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)
===== lspci ======================================================================================================
02:08.0 Ethernet controller [0200]: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller [8086:1039] (rev 81)
 Kernel driver in use: e100
 Kernel modules: e100, eepro100
===== lsusb | grep -v "root hub" =================================================================================
Bus 004 Device 006: ID 1058:1100 Western Digital Technologies, Inc. 
Bus 001 Device 004: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
===== hwinfo (filtered) ==========================================================================================
24: PCI 208.0: 0200 Ethernet controller
  Model: "Intel 82801DB PRO/100 VE (LOM) Ethernet Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x1039 "82801DB PRO/100 VE (LOM) Ethernet Controller"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x0142 
  Driver: "e100"
  Driver Modules: "e100"
  Device File: eth0
  Link detected: no
    Driver Status: e100 is active
    Driver Activation Cmd: "modprobe e100"
    Driver Status: eepro100 is not active
    Driver Activation Cmd: "modprobe eepro100"
===== lsmod (filtered) ===========================================================================================
| ac97_bus        | af_packet       | ata_piix        | binfmt_misc     | dcdbas           |
| dock            | drm             | e100            | ehci_hcd        | emu10k1_gp       |
| ff_memless      | hid             | hwmon           | i2c_core        | i2c_i801         |
| ip_tables       | ipv6            | jbd             | libata          | lp               |
| mbcache         | mii             | pci_hotplug     | ppdev           | r128             |
| scsi_mod        | sd_mod          | sg              | shpchp          | sr_mod           |
| st              | uhci_hcd        | usb_storage     |
===== iwconfig ===================================================================================================
eth0      no wireless extensions.
===== ls /lib/firmware/*.{fw,ucode,bin} ==========================================================================
| BCM2033-FW.bin          | aic94xx-seq.fw          | aica_firmware.bin       | atmel_at76c502-wpa.bin   |
| atmel_at76c502.bin      | atmel_at76c502_3com-wpa.bin| atmel_at76c502_3com.bin | atmel_at76c502d-wpa.bin  |
| atmel_at76c502d.bin     | atmel_at76c502e-wpa.bin | atmel_at76c502e.bin     | atmel_at76c503-i3861.bin |
| atmel_at76c503-i3863.bin| atmel_at76c503-rfmd-0.90.2-140.bin| atmel_at76c503-rfmd-acc.bin| atmel_at76c503-rfmd.bin  |
| atmel_at76c504.bin      | atmel_at76c504_2958-wpa.bin| atmel_at76c504a_2958-wpa.bin| atmel_at76c504c-wpa.bin  |
| atmel_at76c505-rfmd.bin | atmel_at76c505-rfmd2958.bin| atmel_at76c505a-rfmd2958.bin| atmel_at76c506-wpa.bin   |
| atmel_at76c506.bin      | digiface_firmware.bin   | digiface_firmware_rev11.bin| dvb-ttpci-01.fw          |
| ipw-2.2-boot.fw         | ipw-2.2-bss.fw          | ipw-2.2-bss_ucode.fw    | ipw-2.2-ibss.fw          |
| ipw-2.2-ibss_ucode.fw   | ipw-2.3-boot.fw         | ipw-2.3-bss.fw          | ipw-2.3-bss_ucode.fw     |
| ipw-2.3-ibss.fw         | ipw-2.3-ibss_ucode.fw   | ipw-2.3-sniffer.fw      | ipw-2.3-sniffer_ucode.fw |
| ipw-2.4-boot.fw         | ipw-2.4-bss.fw          | ipw-2.4-bss_ucode.fw    | ipw-2.4-ibss.fw          |
| ipw-2.4-ibss_ucode.fw   | ipw-2.4-sniffer.fw      | ipw-2.4-sniffer_ucode.fw| ipw2100-1.3-i.fw         |
| ipw2100-1.3-p.fw        | ipw2100-1.3.fw          | ipw2200-bss.fw          | ipw2200-ibss.fw          |
| ipw2200-sniffer.fw      | iwlwifi-3945-1.ucode    | iwlwifi-4965-1.ucode    | iwlwifi-4965-2.ucode     |
| iwlwifi-5000-1.ucode    | multiface_firmware.bin  | multiface_firmware_rev11.bin| ql2100_fw.bin            |
| ql2200_fw.bin           | ql2300_fw.bin           | ql2322_fw.bin           | ql2400_fw.bin            |
| ql2500_fw.bin           | rt2561.bin              | rt2561s.bin             | rt2661.bin               |
| rt73.bin                |
===== iwlist scanning (filtered) =================================================================================
No WLANs found
===== ndiswrapper -l =============================================================================================
No ndiswrapper module loaded
===== Active processes ===========================================================================================
wpa_supplicant:YES networkmanager:YES nm-applet:NO
===== ===== egrep -i "^^#].*(persistent|networkmanager)" /etc/sysconfig/network/config ==========================
===== rfkill list wifi ===========================================================================================
Can't open RFKILL control device: No such file or directory
===== Actual date for bias of following greps ====================================================================
20:41:10 2013-06-03
===== grep -i radio /var/log/messages* | tail -n 5 ===============================================================
===== dmesg | grep -i radio | tail -n 5 ==========================================================================
===== tail -n 300 /var/log/messages* | /usr/bin/grep -i firmware | tail -n 10 ====================================
===== egrep 'eth|ath|wlan|ra|ppp' /etc/udev/rules.d/*net_persistent* /etc/udev/rules.d/*persistent-net* ==========
/etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="##:##:##:##:##:#1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
===== egrep -r 'eth[0-10]|ath[0-10]|wlan[0-10]|ra[0-10]' /etc/modprobe.*|egrep -v -i '#|blacklist' ===============
/etc/modprobe.conf:install eth0             /bin/true
/etc/modprobe.conf:install eth1             /bin/true
==================================================================================================================
*** NWElizaStates V0.6.11
IF:eth0 IM:2 DI:1 AP:0 FALON:2 NI:1 cNI:1 NDIS:0 CM:2 IP6:1 KM:1 WLW:0 RTDT:SuSE GUI:0 UID:0
#4

On 06/03/2013 11:06 PM, bagheerabirdy wrote:
>
> My apologies. I read through some of the wonderful information that I
> found at the stickies location.
>
> Here is the lsusb & also lspci info from my system:
>
>
> Code:
> --------------------
> linux-1oxp:/home # lsusb
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 003: ID 09a6:8001 Poinchips Mass Storage Device
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 003: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> linux-1oxp:/home # sudo /sbin/lspci
> 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
> 00:01.0 PCI bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 01)
> 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
> 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
> 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
> 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
> 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
> 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
> 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
> 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF
> 02:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax/Voice/Spkp Modem (rev 01)
> 02:02.0 Multimedia audio controller: Creative Labs [SB Live! Value] EMU10k1X
> 02:02.1 Input device controller: Creative Labs [SB Live! Value] Input device controller
> 02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 81)
>
> --------------------
>
>
> Hope this gives some insight. Please let me know if any additional info
> is required.
>
> I will also work on getting the output from the collectNWData.sh script
> that has been mentioned in one of those stickies.

There are no wireless devices in either the lspci or lsusb output. If your
device is USB, was it plugged in? Note, a driver is not needed to provide this
info. In fact, this info is what the kernel uses to determine which driver is
needed.

BTW, you need the -nn switch for the lspci command to output the PCI IDs.

#5

The USB wireless device has been plugged in. That is what is very confusing to me. When I restart the machine and log into the windows session, this wireless device is being recognized and I’m able to connect to the internet but when I restart and log back into the Linux session, the device is not even being recognized. Here is a link to the wireless device on the manufacturers website Adapters – AWLL6070.

The lspci -nn gave me the same output as before.

#6

hi,

its possible, kernel 2.6.27.7-9-default is to old for the detection of the usb stick

have you tried a newer kernel?

kernel 3.7 should identify it as a wired connection

later kernels should identify it as a Mobile Broadband device

the above is based on experience connecting up with a Hauwei E3551 device
(this device can be connected via a usb port or via wireless)

#7

On 06/04/2013 05:56 PM, keellambert wrote:

> its possible, kernel 2.6.27.7-9-default is to old for the detection of
> the usb stick

ah! the OP’s second post reveals s/he is running openSUSE 11.1 which
sailed past its end of life and support on January 14th 2011 (cite:
http://en.opensuse.org/Lifetime) and has received no
security patches since…

so, it is probably good that the wireless does not work (as the box
is not secure, and if i were mine i would never bare connect it to
the internet)

suggest it move to a currently supported version (today those are
12.2 and 12.3)

doing that will introduce a modern kernel which (as @keellambert
points out) will probably work lots better…

–
dd
http://tinyurl.com/DD-Caveat

#8

On 06/04/2013 07:56 AM, bagheerabirdy wrote:
>
> The USB wireless device has been plugged in. That is what is very
> confusing to me. When I restart the machine and log into the windows
> session, this wireless device is being recognized and I’m able to
> connect to the internet but when I restart and log back into the Linux
> session, the device is not even being recognized. Here is a link to the
> wireless device on the manufacturers website ‘Adapters – AWLL6070’
> (http://www.airlink101.com/products/awll6070.php).
>
> The lspci -nn gave me the same output as before.

No it did not. On my system, “lspci” yields the following for one device:


0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE
802.11b/g/n WiFi Adapter (rev 01)

The “lspci -nn” output for the same device is:


0e:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE
802.11b/g/n WiFi Adapter [10ec:8178] (rev 01)

To you, that may look the same; however that “[10ec:8178]” found in the second
example is critical to knowing what driver is needed.

For you, the lspci output is immaterial as you have now told us you have a USB
device. From that, I deduce that the device is indicated by


Bus 003 Device 003: ID 09a6:8001 Poinchips Mass Storage Device

The device is one of those dual-mode devices that presents itself as a storage
device that contains the driver, but can be switched to become a wireless
device. The friendliest versions of these are permanently switched after the
driver is installed, but this one has to be switched after every boot. According
to the inf file in the Windows driver, the wireless chip may be an RaLink 2870
with USB IDs [148f:2870] and it will work under Linux as soon as the
kernel-firmware is installed and you figure out the modeswitch command
necessary. The latter part is the problem.

The first step will be to ensure that the usb_modeswitch and usb_modeswitch_data
packages are installed. Unfortunately, the standard set of modeswitch data files
does not include one for the 09a6:8001 device. It can be captured from what
Windows writes when the system starts, but setting that part up is difficult. I
have not done a Windows USB capture for about 6 years, and I do not remember
exactly what it took, but I know it was not easy. In addition, there is nothing
on the Internet about the Airplay device.

I hate to recommend that you spend more money, but I think your best approach
would be to buy an inexpensive USB adapter on E-bay. I have had good success
with a TP-Link TL-WN722N such as found at
http://www.ebay.com/itm/TP-LINK-TL-WN722N-Wireless-N150-High-Gain-USB-Adapter-150Mbps-w-4-dBi-Hig-/380649558150?pt=US_USB_Wi_Fi_Adapters_Dongles&hash=item58a07b5086
for $15.99 US with free shipping. If you want a smaller unit, something like
http://www.ebay.com/itm/Dreambox-VU-Wifi-11-54-150-300-Mbps-MiniStick-USB-Chipset-Ralink-RT2870-RT3070-/121056745729?pt=US_Satellite_TV_Receivers&hash=item1c2f8b5901
should be OK. It is $30 with free shipping.

#9

Thank you all for the suggestions. I will first try to move to the latest version 12.3. However, I read elsewhere in the forum that I cannot directly move from Suse 11.1 to 12.3. I may have to move up in increments of say 11.3, etc. Any suggestions on that will be great.

Also if you could please refer me to the link that provides a step by step instruction on how to upgrade, that will be just awesome.

#10

On 06/04/2013 09:46 PM, bagheerabirdy wrote:
> Any suggestions on that will be great.

totally abandon your 11.1 install it is SO different from the current
offering that there is nothing there to bring forward but whatever
data you might have collected in its few days of use.

really! do not try to use your /home it will contain configs unlikely
to be useful, and pretty likely to be troublesome…

instead: save off the data (music, photos, movies, email, doctoral
thesis, etc etc you collected therein) and then full format and
install 12.2 or 12.3

you might find some reading prior to install will make your
experience less daunting:

http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-startup/

http://en.opensuse.org/SDB:Download_help

http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/new-user-how-faq-read-only/

buy a big measure of Patience.

–
dd
http://tinyurl.com/DD-Caveat

#11

Trying to encourage my grandson to use Linux on his Inspiron E1705. Loaded OpenSuse 12.3 with KDE 4.10.5, dual boot. Everything is great and he really likes it, but the WiFi doesn’t work.

The WiFi hardware was loaded with the default broadcom driver but Network manager did not add it to the network interfaces. In the hardware probe the card is listed as a 1390 WLAN minicard

: PCI c00.0: 0280 Network controller
[Created at pci.319]
Unique ID: zb5c.AUabv0M9SM3
Parent ID: qTvu.KxZ2I+vnJeF
SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
SysFS BusID: 0000:0c:00.0
Hardware Class: network
Model: “Dell Wireless 1390 WLAN Mini-Card”
Vendor: pci 0x14e4 “Broadcom”
Device: pci 0x4311 “BCM4311 802.11b/g WLAN”
SubVendor: pci 0x1028 “Dell”
SubDevice: pci 0x0007 “Wireless 1390 WLAN Mini-Card”
Revision: 0x01
Driver: “b43-pci-bridge”
Driver Modules: “ssb”
Memory Range: 0xefcfc000-0xefcfffff (rw,non-prefetchable)
IRQ: 17 (13396 events)
Module Alias: “pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00”
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd: “modprobe ssb”
Driver Info #1:
Driver Status: wl is active
Driver Activation Cmd: “modprobe wl”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (PCI bridge)

I can’t make the card active because when I try to setup a wireless in Configure desktop, the wireless tab is not available. Tried to insert a kernel specific driver (“desktop”) - still no joy.

I hope you can help.

My grandson will be monitoring this - his first trouble report - so be nice to him. And Thanks. **** that kid loves his Minecraft.

#12

On 08/03/2013 04:46 PM, masonbell09 wrote:
>
> Trying to encourage my grandson to use Linux on his Inspiron E1705.
> Loaded OpenSuse 12.3 with KDE 4.10.5, dual boot. Everything is great
> and he really likes it, but the WiFi doesn’t work.
>
> The WiFi hardware was loaded with the default broadcom driver but
> Network manager did not add it to the network interfaces. In the
> hardware probe the card is listed as a 1390 WLAN minicard
>
> : PCI c00.0: 0280 Network controller
> [Created at pci.319]
> Unique ID: zb5c.AUabv0M9SM3
> Parent ID: qTvu.KxZ2I+vnJeF
> SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
> SysFS BusID: 0000:0c:00.0
> Hardware Class: network
> Model: “Dell Wireless 1390 WLAN Mini-Card”
> Vendor: pci 0x14e4 “Broadcom”
> Device: pci 0x4311 “BCM4311 802.11b/g WLAN”
> SubVendor: pci 0x1028 “Dell”
> SubDevice: pci 0x0007 “Wireless 1390 WLAN Mini-Card”
> Revision: 0x01
> Driver: “b43-pci-bridge”
> Driver Modules: “ssb”
> Memory Range: 0xefcfc000-0xefcfffff (rw,non-prefetchable)
> IRQ: 17 (13396 events)
> Module Alias: “pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00”
> Driver Info #0:
> Driver Status: ssb is active
> Driver Activation Cmd: “modprobe ssb”
> Driver Info #1:
> Driver Status: wl is active
> Driver Activation Cmd: “modprobe wl”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
> Attached to: #18 (PCI bridge)
>
> I can’t make the card active because when I try to setup a wireless in
> Configure desktop, the wireless tab is not available. Tried to insert a
> kernel specific driver (“desktop”) - still no joy.
>
> I hope you can help.
>
> My grandson will be monitoring this - his first trouble report - so be
> nice to him. And Thanks. **** that kid loves his Minecraft.

Both my grandsons also enjoy Minecraft a lot.

If you look at the output of the dmesg command, you will see that the firmware
is missing. The Broadcom devices are funny in that they refuse to allow anyone
to redistribute their firmware, thus we have prepared a script that downloads a
foreign driver and extracts the firmware. You perform this action with


sudo /usr/sbin/install_bcm43xx_firmware

The 1434:4311 devices work quite well with driver b43.

#13

Thanks for your response.

Ran in the b43 firmware, but still have the previous condition. H/W is below, still can not configure wireless in network manager.
PCI c00.0: 0280 Network controller
[Created at pci.319]
Unique ID: zb5c.AUabv0M9SM3
Parent ID: qTvu.KxZ2I+vnJeF
SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
SysFS BusID: 0000:0c:00.0
Hardware Class: network
Model: “Dell Wireless 1390 WLAN Mini-Card”
Vendor: pci 0x14e4 “Broadcom”
Device: pci 0x4311 “BCM4311 802.11b/g WLAN”
SubVendor: pci 0x1028 “Dell”
SubDevice: pci 0x0007 “Wireless 1390 WLAN Mini-Card”
Revision: 0x01
Driver: “b43-pci-bridge”
Driver Modules: “ssb”
Memory Range: 0xefcfc000-0xefcfffff (rw,non-prefetchable)
IRQ: 17 (13396 events)
Module Alias: “pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00”
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd: “modprobe ssb”
Driver Info #1:
Driver Status: wl is active
Driver Activation Cmd: “modprobe wl”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (PCI bridge)

Thanks again.

#14

On 08/03/2013 07:26 PM, masonbell09 wrote:
>
> lwfinger;2576682 Wrote:
>> On 08/03/2013 04:46 PM, masonbell09 wrote:
>>>
>>> Trying to encourage my grandson to use Linux on his Inspiron E1705.
>>> Loaded OpenSuse 12.3 with KDE 4.10.5, dual boot. Everything is great
>>> and he really likes it, but the WiFi doesn’t work.
>>>
>>> The WiFi hardware was loaded with the default broadcom driver but
>>> Network manager did not add it to the network interfaces. In the
>>> hardware probe the card is listed as a 1390 WLAN minicard
>>>
>>> : PCI c00.0: 0280 Network controller
>>> [Created at pci.319]
>>> Unique ID: zb5c.AUabv0M9SM3
>>> Parent ID: qTvu.KxZ2I+vnJeF
>>> SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
>>> SysFS BusID: 0000:0c:00.0
>>> Hardware Class: network
>>> Model: “Dell Wireless 1390 WLAN Mini-Card”
>>> Vendor: pci 0x14e4 “Broadcom”
>>> Device: pci 0x4311 “BCM4311 802.11b/g WLAN”
>>> SubVendor: pci 0x1028 “Dell”
>>> SubDevice: pci 0x0007 “Wireless 1390 WLAN Mini-Card”
>>> Revision: 0x01
>>> Driver: “b43-pci-bridge”
>>> Driver Modules: “ssb”
>>> Memory Range: 0xefcfc000-0xefcfffff (rw,non-prefetchable)
>>> IRQ: 17 (13396 events)
>>> Module Alias: “pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00”
>>> Driver Info #0:
>>> Driver Status: ssb is active
>>> Driver Activation Cmd: “modprobe ssb”
>>> Driver Info #1:
>>> Driver Status: wl is active
>>> Driver Activation Cmd: “modprobe wl”
>>> Config Status: cfg=no, avail=yes, need=no, active=unknown
>>> Attached to: #18 (PCI bridge)
>>>
>>> I can’t make the card active because when I try to setup a wireless
>> in
>>> Configure desktop, the wireless tab is not available. Tried to
>> insert a
>>> kernel specific driver (“desktop”) - still no joy.
>>>
>>> I hope you can help.
>>>
>>> My grandson will be monitoring this - his first trouble report - so
>> be
>>> nice to him. And Thanks. **** that kid loves his Minecraft.
>>
>> Both my grandsons also enjoy Minecraft a lot.
>>
>> If you look at the output of the dmesg command, you will see that the
>> firmware
>> is missing. The Broadcom devices are funny in that they refuse to allow
>> anyone
>> to redistribute their firmware, thus we have prepared a script that
>> downloads a
>> foreign driver and extracts the firmware. You perform this action with
>>
>>>
> Code:
> --------------------
> > >
> > sudo /usr/sbin/install_bcm43xx_firmware
> >
> --------------------
>>>
>>
>> The 1434:4311 devices work quite well with driver b43.
>
> Thanks for your response.
>
> Ran in the b43 firmware, but still have the previous condition. H/W is
> below, still can not configure wireless in network manager.
> PCI c00.0: 0280 Network controller
> [Created at pci.319]
> Unique ID: zb5c.AUabv0M9SM3
> Parent ID: qTvu.KxZ2I+vnJeF
> SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:0c:00.0
> SysFS BusID: 0000:0c:00.0
> Hardware Class: network
> Model: “Dell Wireless 1390 WLAN Mini-Card”
> Vendor: pci 0x14e4 “Broadcom”
> Device: pci 0x4311 “BCM4311 802.11b/g WLAN”
> SubVendor: pci 0x1028 “Dell”
> SubDevice: pci 0x0007 “Wireless 1390 WLAN Mini-Card”
> Revision: 0x01
> Driver: “b43-pci-bridge”
> Driver Modules: “ssb”
> Memory Range: 0xefcfc000-0xefcfffff (rw,non-prefetchable)
> IRQ: 17 (13396 events)
> Module Alias: “pci:v000014E4d00004311sv00001028sd00000007bc02sc80i00”
> Driver Info #0:
> Driver Status: ssb is active
> Driver Activation Cmd: “modprobe ssb”
> Driver Info #1:
> Driver Status: wl is active

You have installed wl. Part of the installation process blacklists ssb and b43.
You need to find the file in /etc/modprobe.d/ that does this blacklisting and
delete those lines.

#15

It worked, thanks. I’ve yet to get a connection to an AP, but that is a different matter. Looks like the WiFi is seeing the network and is active. Again, thanks