Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have Toshiba Sattelite A100 and have installed both version of Fedora 7 and 8 but could not get the wireless device activated and therefoer unable to connect to internet.I use D-Link wireless router.
I am familair with setting up wireless in windows and for Fedora also I beleive I have entered all information correctly but couldn't get the wirless device activated. By the if I enter IP information manualy, Fedora activate my wireless but can not connect to internet.
I will appreciate any suggestion to fix this problem.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
What is the wireless card chipset? Use the command ' /sbin/lspci -v '
Now post loaded modules. Use commmand ' /sbin/lsmod '
If you are actually setting up the wireless card and say not the wired nic I would do this. If you are manually configuring the nic to a Static IP, gateway, Subnet and defined the DNS values as well and if security like WEP or WPA is enabled turn it off. Turn off any security and enable dhcp. Set the nic to find its own IP. Once you can do that then you can reenable security and resolve that portion. Just one step at a time.
Wireless device is: intel Corporation PRO/wireless 3945ABG Network Connection
I disabled all securities but still could not get the wireless running. by the way I can easily connect to internet using cable but I want to have my wireless running.
I am not familiar with linux command and trying to learn. If I have to do it through command I will appreciate if you give me more detailes.
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 1820 [size=32]
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at 1840 [size=32]
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1860 [size=32]
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 1880 [size=32]
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at dc444000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) (prog-if 80 [Master])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 20
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 18b0 [size=16]
Capabilities: <access denied>
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: medium devsel, IRQ 20
I/O ports at 18c0 [size=32]
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 1820 [size=32]
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at 1840 [size=32]
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 1860 [size=32]
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 1880 [size=32]
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at dc444000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) (prog-if 80 [Master])
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 20
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 18b0 [size=16]
Capabilities: <access denied>
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
Subsystem: Toshiba America Info Systems Unknown device ff10
Flags: medium devsel, IRQ 20
I/O ports at 18c0 [size=32]
Using the 3945abg is quite different in fedora 7 to fedora 8.
It's easier to get going in Fedora 8 but with the new NetworkManager program there can be problems connecting to encrypted networks where the level of encryption is higher than basic WPA-PSK.
I have the 3945 working at present on fedora 8 and that is the route I would recommend as all the necessary driver parts are installed by default. It is usually just necessary to activate the various parts in order to get a connection.
The precise route to take is further complicated by it being different if you install from the dvd or from one of the live cd's.
Firstly, if you installed from DVD then the NetworkManager service is usually running. The command
service NetworkManager status
from a root command line will tell you if it is. Capitalisation is important by the way. If it is not running then:
system-config-services
will give you an applet to put a mark against it, start it and save the changes.
When you have NetworkManager running - and here's the second catch - although the Gnome desktop will give you a network icon top right of screen it has to be encouraged to appear in KDE. There you are looking for KNetworkManager off the System menu. Even then it won't always appear in the system tray, bottom right this time, until you have logged out and back in again. I haven't had to do it many times so you may even find that you need to totally reboot to get it to appear.
Once you have a NetworkManager icon, it should be as simple as left clicking on it and selecting your network, it was for me.
As I said, some of that may be unnecessary if you installed from the DVD. If you installed from the KDE livecd then all of it will be used as that CD is set up differently to the DVD. I can't tell you about the Gnome livecd as I haven't used it but your answers should be in the above.
Hope it works as well for you as it does for me. If you have problems, try posting back the result of the commands:
Thanks for the very helpful info bbfuller. This has helped me along with my own problems getting my Edimax EW-7128G (RaLink RT2561) to work on Fedora 8.
Now that I have successfully started up NetworkManager, it seems that Fedora is talking to my network, because if I have security enabled (WPA-PSK) it asks for a password (I have tried without security as well). Then it attempts to connect again and comes back with the same prompt.
Over on the Fedora Forum it's interesting to see that there are lots of people for whom Wireless just works and just as many who can't get a connection at all.
I was talking about a 3945 above, but I've also got a Broadcom 4318 and a Belkin F5D700 using the RT61/RT2x00 driver and they all worked without much effort. Which doesn't give me much experience to go on when things don't work.
When you try to configure a card using NetworkManager it seems fairly important that it is not set to be enabled at boot time in the Fedora Network Configuration applet.
system-config-network
issued at a root command line should get you there, then select any wireless networks and "Edit" their properties and make sure "allow users to configure is selected" but that "Start on boot" is not.
I think it will also depend on if you have tried to manually configure the wireless in any way and if any remnants of that configuring are left behind.
If you are in any doubt about that, rather than re-install it may be interesting to boot up a live cd and see if you can make a connection with that.
I'm not sure what else I can suggest, but I'll give it some more thought during the day. If you've posted back this evening I may have some other thoughts.
Over on the Fedora Forum it's interesting to see that there are lots of people for whom Wireless just works and just as many who can't get a connection at all.
I was talking about a 3945 above, but I've also got a Broadcom 4318 and a Belkin F5D700 using the RT61/RT2x00 driver and they all worked without much effort. Which doesn't give me much experience to go on when things don't work.
When you try to configure a card using NetworkManager it seems fairly important that it is not set to be enabled at boot time in the Fedora Network Configuration applet.
system-config-network
issued at a root command line should get you there, then select any wireless networks and "Edit" their properties and make sure "allow users to configure is selected" but that "Start on boot" is not.
I think it will also depend on if you have tried to manually configure the wireless in any way and if any remnants of that configuring are left behind.
If you are in any doubt about that, rather than re-install it may be interesting to boot up a live cd and see if you can make a connection with that.
I'm not sure what else I can suggest, but I'll give it some more thought during the day. If you've posted back this evening I may have some other thoughts.
Hi,
I am currently having the same problem as DDH and although i can detect the wireless network, it keeps prompting me for the WEP key over and over again. I have tried to switch off the WEP setting on my router but the result was that I can no longer even see it on fedora 8 (although it works fine on Windows Vista.
As to turning off encryption all together, there have been occasions when doing that and then adding encryption back in after getting a successful connection have worked.
If you don't see the connection after altering the encryption I would at least try rebooting you computer to see if that cures it. I've not had trouble that way before.
As to my cards reported on in post #10 my RT61/RT2x00 has recently become problematic.
If you are only using up to WEP then turning off the NetworkManager service and connecting through system-config-network may be an answer. That used to be very reliable. When I last used it, for a WEP key it was necessary to enter the hexadecimal equivalent of your WEP key and precede it with 0x. That's a zero and small x
As you can appreciate, wireless being a bit touchy in Fedora I'm not keen to mess with my settings in case I disturb something, so the above is from my recollection in Fedora 7 and may not apply in 8.
Edit: Post #27 on this thread in the Fedora Forum:
I'm struggling to get my wireless working after each kernel upgrade. I'm using fedora 8 on an intel centrino duo with a network card that uses 3945 chipset. I've found the wireless stops working after each kernel upgrade (using software updater) and after a seemingly random process, I might get it working again. I've just assumed drivers need to be reinstalled / recompiled against a new kernel if it coincides with each kernel upgrade but I've got no idea how to do this properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.