View Full Version : Unable to connect to wireless networks - and unable to configure network
elasticsoul
27th July 2010, 07:19 PM
Hi All,
I just switched from Ubuntu to Fedora 13 because I was unable to get Ubuntu to connect to wireless networks. I tried everything suggested in help and forums, and kept getting "Bad Password" with WICD and Network Manager. Now, with Fedora...I still can't connect. :confused:
Problem #1: The help guide says to "...make sure that the relevant wireless interface (usually eth0 or eth1) is controlled by NetworkManager," and that I do this via: System>Administration>Network
However, there is no Network option under System>Administration.
Problem #2: I open Network Manager, which displays a list of networks. I click on mine, configure it with WPA and the right password, and it fails to connect: "The network connection has been disconnected."
Help?
glennzo
27th July 2010, 08:08 PM
Post the type of wireless and Ethernet hardware you have so that others will have a better idea as to how to help you.
lspci
Cut and paste the relevant info please.
elasticsoul
27th July 2010, 08:16 PM
My apologies. Here it is:
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:01.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:03.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
nimnull22
27th July 2010, 09:07 PM
Wireless - means interface should be "wlan".
What kind of wireless adapter do you use? Is it a usb dongle? Your "lspci" output said nothing about wireless devices, only about ethernet.
So please, give us more explanation.
glennzo
27th July 2010, 09:09 PM
My apologies. Here it is:
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:01.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:03.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
I only see Ethernet, in red.
elasticsoul
27th July 2010, 09:52 PM
Weird, no? I am far from an expert at this, but when I booted into Setup, I noticed that one of the PCI's is set to wireless.
From the Dell marketing materials (http://www.dell.com/downloads/us/products/latit/c640_spec.pdf):
"An internal MiniPCI slot is designed to exclusively support 802.11 wireless2 technology."
"Dell True MobileTM 1150 Wireless Mini PCI Card . . . . . . . . . . . . . . . . .IEEE 802.11b2 industry standard; Wi-FiTM compatible"
Does this help?
---------- Post added at 12:52 PM CDT ---------- Previous post was at 12:25 PM CDT ----------
More info; when I type lshw:
*-network
description: Wireless interface
physical id: 1
logical name: eth1
serial: 00:02:2d:34:dc:3a
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Lucent/Agere 6.16 multicast=yes wireless=IEEE 802.11b
nimnull22
27th July 2010, 09:53 PM
Take a look:
http://blogs.linux.ie/fuzzbucket/2006/03/24/dell-latitude-c640-wireless-and-gnulinux/
Is it about your laptop?
elasticsoul
27th July 2010, 09:58 PM
nimnull22 -yes it is! However, I must have a wireless card installed, because the machine detects wireless networks. My most recent post suggests an Orinoco driver, but I have no idea what the hardware is.
nimnull22
27th July 2010, 10:31 PM
Ok, please on root console type and post here outputs of:
ifconfig -a
iwconfig
elasticsoul
27th July 2010, 10:40 PM
Here you go. After the two you requested, I also posted the results of lshw, as this seems to indicate a wireless card of some sort with orinoco driver, in case it helps.
Thanks for your patience and help!
ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:74:95:78:6D
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:11 Base address:0xc00
eth1 Link encap:Ethernet HWaddr 00:02:2D:34:DC:3A
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:5 Base address:0xe100
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:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1664 (1.6 KiB) TX bytes:1664 (1.6 KiB)
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b Mode:Managed Frequency:2.457 GHz
Access Point: None Bit Rate:11 Mb/s Sensitivity:1/0
Retry limit:8 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-122 dBm Noise level=-122 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lshw:
*-network
description: Wireless interface
physical id: 1
logical name: eth1
serial: 00:02:2d:34:dc:3a
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Lucent/Agere 6.16 multicast=yes wireless=IEEE 802.11b
JEO
27th July 2010, 10:48 PM
Hi All,
I just switched from Ubuntu to Fedora 13 because I was unable to get Ubuntu to connect to wireless networks. I tried everything suggested in help and forums, and kept getting "Bad Password" with WICD and Network Manager. Now, with Fedora...I still can't connect. :confused:
Problem #1: The help guide says to "...make sure that the relevant wireless interface (usually eth0 or eth1) is controlled by NetworkManager," and that I do this via: System>Administration>Network
However, there is no Network option under System>Administration.
Problem #2: I open Network Manager, which displays a list of networks. I click on mine, configure it with WPA and the right password, and it fails to connect: "The network connection has been disconnected."
Help?
From what I recall about such old hardware, it may not work with WPA only WEP unless you have a new enough firmware in the card. Such cards can work with WPA in Windows because the windows driver puts the updated firmware in the card's RAM memory each time it loads, but the Linux driver requires that the firmware be flashed. It is most likely an intersil prism 2.5 based card.
elasticsoul
27th July 2010, 10:54 PM
From what I recall about such old hardware, it may not work with WPA only WEP unless you have a new enough firmware in the card. Such cards can work with WPA in Windows because the windows driver puts the updated firmware in the card's RAM memory each time it loads, but the Linux driver requires that the firmware be flashed. It is most likely an intersil prism 2.5 based card.
It did connect when XP was installed. However, it did not connect after I installed Ubuntu on my home network, which still has WEP. I got the same error: "Bad password."
I could take a look at the card; I'll try and dig up some tools and remove some covers.
JEO
27th July 2010, 11:02 PM
Have a look here it describes what firmware version you need for WPA:
http://junsun.net/linux/intersil-prism/
If you review /var/log/messages at the time the wireless driver loads orinico driver or the newer hostap driver, it will usually print the firmware version.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.