View Full Version : Wireless in Fedora 9 BETA
JKoder
15th April 2008, 08:35 PM
Hello all.
I dont know exactly if this is a bug, but whenever i connect to my wireles router, it stays connected for 1 minute maximum and then it disconnects.Sometimes it's stay conected longer and siconnects randomly.
What could be the reason ?
I must confes i choosed Fedora over Ubuntu, but this is quite anoying
bbfuller
15th April 2008, 08:49 PM
Hello JKoder
Fedora 9 beta is exactly that and you shouldn't expect the same performance in that as in finished versions of Fedora.
In the event though, my broadcom 4306 card which is in my Fedora 9 beta machine connects perfectly for as long as I care to leave it. If you want any guesses as to what is happening you will get more reasoned response if you specify what your wireless card is and what software you are using with it.
ghost_ryder35
15th April 2008, 09:25 PM
go to terminal and issue:
lspci
then post the results here
ShivaS
18th April 2008, 08:32 AM
Has anyone tried F9 with an Intel 3945 wireless chipset? On F8 I was unable to configure it from the console and it was very frustrating ...
AntMan
18th April 2008, 06:20 PM
Has anyone tried F9 with an Intel 3945 wireless chipset? On F8 I was unable to configure it from the console and it was very frustrating ...
Yes, both F8 and F9 worked fine with my intel 3945 wifi using network manager. Actually, F9 is actually better since it suspends and resumes the wifi without a hiccup when going in and out of standby mode. :D
Iron_Mike
19th April 2008, 02:15 AM
Hello all.
I dont know exactly if this is a bug, but whenever i connect to my wireles router, it stays connected for 1 minute maximum and then it disconnects.Sometimes it's stay conected longer and siconnects randomly.
What could be the reason ?
I must confes i choosed Fedora over Ubuntu, but this is quite anoying
You failed to mention which what model/brand wireless your using?
JKoder
19th April 2008, 07:44 AM
You failed to mention which what model/brand wireless your using?
Sorry about that.
My wifi card is Atheros, one thing i noticed is, after a few disconnects, it does not disconnect anymore, but just after a few disconnects .
Right now i am not on fedora so i cannot give you lspci output.
ghost_ryder35
20th April 2008, 02:05 PM
Sorry about that.
My wifi card is Atheros, one thing i noticed is, after a few disconnects, it does not disconnect anymore, but just after a few disconnects .
Right now i am not on fedora so i cannot give you lspci output.
lspci out would be releveant to solving your problem. if network manager is managing your connection I would check to see what channel it is setup with and compare to your wireless router. mine was setup for channel 1 and my router channel 7. syncing them solved my frequent disconencts.
ShivaS
21st April 2008, 09:30 AM
Yes, both F8 and F9 worked fine with my intel 3945 wifi using network manager. Actually, F9 is actually better since it suspends and resumes the wifi without a hiccup when going in and out of standby mode. :D
Indeed, wireless worked in F8 using NetworkManager and that annoying PAM-keyring screen :mad:
I truly hope that WPA2 support was improved in F9 ...I think I'll find that tonight... :D
Droz
27th April 2008, 05:25 PM
I have this same problem, and I believe that it is something to do with the fact that my atheros driver in the f9 preview is different to the one in f8. ath5k_pci instead of ath_pci or something.
Also, i've noticed when fc9 wireless connection drops out, all the computers on the wireless network drop out too - ie, all the XP computers.
drop outs happen randomly, but almost every time i do something like use yumex...
ideas?
Droz
28th April 2008, 06:33 AM
... Also, i'd like to add that it never happens if the wireless network is unsecured - at my local library, i'm connected all day, but at home, with wpa2, fc9 beta/preview causes the whole network to crash...
ShivaS
28th April 2008, 03:21 PM
I just installed Fedora9_x64 and, as expected, no wireless, even with NetworkManager started.
The error states "ADDRCONF(NETDEV_UP): wlan0: link is not ready"
Apr 28 16:47:26 dev NetworkManager: <info> Bringing up device wlan0
Apr 28 16:47:26 dev kernel: ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Apr 28 16:47:26 dev kernel: Registered led device: iwl-phy0:radio
Apr 28 16:47:26 dev kernel: Registered led device: iwl-phy0:assoc
Apr 28 16:47:26 dev kernel: Registered led device: iwl-phy0:RX
Apr 28 16:47:26 dev kernel: Registered led device: iwl-phy0:TX
Apr 28 16:47:26 dev kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 28 16:47:26 dev NetworkManager: <info> Deactivating device wlan0.
Apr 28 16:47:26 dev NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1).
Apr 28 16:49:53 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Apr 28 16:49:57 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 28 16:50:05 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 28 16:50:13 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 28 16:50:21 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Apr 28 16:50:35 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Apr 28 16:50:50 dev dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Apr 28 16:50:54 dev dhclient: No DHCPOFFERS received.
Apr 28 16:50:54 dev dhclient: No working leases in persistent database - sleeping.
My wireless card is a Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) and my wireless network is configured to use WPA2PSK.
ShivaS
29th April 2008, 08:29 AM
Finally, a F9 reinstall fixed everything.
I don't know if this is a feature or a bug, but when the wired connection is activated, the wireless card is hardware disabled (the wireless LED turns off ).
rstory
30th April 2008, 02:50 PM
did you have to do anything special? my 3945 isn't working (f9)...
ShivaS
30th April 2008, 03:02 PM
did you have to do anything special? my 3945 isn't working (f9)...
The NetworkManager-gnome package must be installed.
Run rpm -qa|grep NetworkManager to see if it is installed.
The funny thing is that it does not appear in the F9 DVD repo., so either you check the package on F9 install or wire yourself to internet (somehow ) and yum install it.
The second time I installed F9, I also unchecked the rest of the wireless drivers, such as Intel 2200. Seems like NetworkManager GUI has been improved since F8: it saves the wireless network auth. key and the annoying pam-keyring screen is gone.
rstory
30th April 2008, 03:23 PM
# rpm -qa|grep NetworkManager
NetworkManager-glib-0.7.0-0.9.2.svn3566.fc9.i386
NetworkManager-0.7.0-0.9.2.svn3566.fc9.i386
NetworkManager-gnome-0.7.0-0.9.2.svn3566.fc9.i386
# service NetworkManager status
NetworkManager (pid 2367) is running...
# service NetworkManagerDispatcher status
NetworkManagerDispatcher (pid 2554) is running...
I F9 installed from a local yum repo, and it was installed and enabled by default...
ShivaS
30th April 2008, 03:30 PM
OFF:I'm usually making a custom install from DVD ...and break things in the process ... :D
ON:
1. Check if you have a wireless device installed. If not, make one and edit it's properties to be managed by NetworkManager
2. Restart NetworkManagerDispatcher and NetworkManager services
3. Check if nm-applet is present in the taskbar, if it is, double click it and create a new wireless connection.
AntMan
30th April 2008, 10:29 PM
Just a FYI that the F8 and F9 LiveCD's have NetworkManager setup as default. So when I installed it onto my laptops, wifi was working out of the box.
norrisg
1st May 2008, 03:09 AM
Just a FYI that the F8 and F9 LiveCD's have NetworkManager setup as default. So when I installed it onto my laptops, wifi was working out of the box.
This is also the case (well, the setup as default is anyway - working is another matter), for a normal DVD install of F9.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.