View Full Version : [ubuntu] Linksys Issues
September 3rd, 2009, 01:49 AM
I think this has come up a number of times but I'm having trouble with my Linksys Wireless - B PCI adapter. Ubuntu did not recognize it automatically. I couldn't find an answer upon googling. Perhaps I'm not asking the right question. Any input would be much appreciated.
September 3rd, 2009, 06:02 AM
What are the results of the following commands?
lshw -C network
September 3rd, 2009, 05:46 PM
Here are the results. I replaced the name with "undisclosed."
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 02)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 02)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)
02:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller
02:0a.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)
02:0b.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86)
02:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
02:0c.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
02:0d.0 Communication controller: Agere Systems LT WinModem
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
undisclosed@undisclosed-desktop:~$ lshu -C network
bash: lshu: command not found
September 5th, 2009, 05:14 PM
Did I miss type the last command?
September 5th, 2009, 07:24 PM
Yes you did the correct command is:
sudo lshw -C network
You can copy the command and paste it directly in a terminal.
September 5th, 2009, 08:42 PM
Okay here's the result:
undisclosed@undisclosed-desktop:~$ sudo lshw -C network
[sudo] password for undisclosed:
description: Network controller
product: BCM4303 802.11b Wireless LAN Controller
vendor: Broadcom Corporation
physical id: a
bus info: pci@0000:02:0a.0
width: 32 bits
capabilities: pm bus_master cap_list
configuration: driver=b43-pci-bridge latency=64 module=ssb
description: Ethernet interface
product: VT6105/VT6106S [Rhine-III]
vendor: VIA Technologies, Inc.
physical id: b
bus info: pci@0000:02:0b.0
logical name: eth0
width: 32 bits
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=half latency=64 link=no maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=10MB/s
description: Wireless interface
physical id: 1
logical name: wlan0
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11b
Any further input on how to correct this would be appreciated.
September 6th, 2009, 05:47 PM
I'd really appreciate some help with this issue.
September 8th, 2009, 04:42 AM
September 13th, 2009, 04:51 PM
*BUMP* any ideas? Does anybody use a Linsys Wifi PCI card that had this issue?
September 14th, 2009, 02:27 AM
You can first check and see if you can find a Broadcom b43 option in System->Administration->Hardware Drivers. If it does not show up, you can try the following from the Terminal:
sudo apt-get install b43-fwcutterThis command does require a working internet connection because it needs to download a firmware file. The b43-fwcutter application takes some of the data from the firmware file to help make your wireless card work.
The 4303 card should be using the b43legacy module and seems to be rare in the Ubuntu community. I don't recall seeing any using Jaunty so I am not for sure what your results will be. If it still does not work, please come back again and post the results of:
lshw -C network
I am requesting the lshw -C network command again because after installing b43-fwcutter, you should have a different set of results from that command. The dmesg command will help let us know if the b43legacy module is having problems getting loaded into Ubuntu.
Hopefully installing b43-fwcutter will help solve your problem.
September 19th, 2009, 02:06 AM
hmm i can't seem to get past the first step. Here's what I got:
E: Couldn't find package b43-fwcutter
Powered by vBulletin® Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.