Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Wed, Jun 4, 2008 at 10:44 AM, Paul Johnson [EMAIL PROTECTED] wrote: 2008/5/29 Robert Cahn [EMAIL PROTECTED]: I have updated my desktop using the 64-bit desktop of F9 from F7. My wireless is described by: 00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Netgear MA311 802.11b wireless adapter Flags: bus master, medium devsel, latency 32, IRQ 18 Memory at e9005000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci Under F7 the wireless connected without any issues. Turn off the service network Turn on the service NetworkManager run the applet nm-applet to control your wireless logins. Do not try to make system-config-network work together with NM. pj -- Paul E. Johnson Professor, Political Science 1541 Lilac Lane, Room 504 University of Kansas -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Hi Paul, Let me see if I understand. I should go into the service configuration and disable network and enable network manager and I should be OK? -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
2008/5/29 Robert Cahn [EMAIL PROTECTED]: I have updated my desktop using the 64-bit desktop of F9 from F7. My wireless is described by: 00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Netgear MA311 802.11b wireless adapter Flags: bus master, medium devsel, latency 32, IRQ 18 Memory at e9005000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci Under F7 the wireless connected without any issues. Turn off the service network Turn on the service NetworkManager run the applet nm-applet to control your wireless logins. Do not try to make system-config-network work together with NM. pj -- Paul E. Johnson Professor, Political Science 1541 Lilac Lane, Room 504 University of Kansas -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Fri, May 30, 2008 at 3:09 PM, Patrick O'Callaghan [EMAIL PROTECTED] wrote: On Fri, 2008-05-30 at 13:46 +0100, Timothy Murphy wrote: The NM developers suffer from the delusion that NM always works. Of course it always works. Says so right here in the man page :-) poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Latest update on mine is that it still doesn't work. I did post in the Fedora forums and someone posted this link. http://live.gnome.org/NetworkManagerHardware It looks like there are two drivers possibly conflicting. My only problem is I don't know how to verify which drivers are being used and how to disable or uninstall a driver. Can you point me in the right direction? Thanks. -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
Marc Ferguson wrote: I did the iwlist scan and I noticed it did scans for: lo, eth1, wifi0, eth0, irda0, and pan0. My wireless device, according to Network Configuration is eth0. I find that weird; in prior distros wireless devices where labeled wlan0, wlan1, etc. The scan did pick up something for wifi0 and eth0. What is something? Did it pick up the AP you are hoping to use? If so, it seems to me that NM _is_ working. Do you know what kind of encryption the AP is using? Did you try clicking on the NM applet in the panel? IMHO, NM is very, very bad at telling you where the connection is breaking down if it does not connect cleanly. The NM developers suffer from the delusion that NM always works. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting (F8-Live works)
As A test I downloaded Fedora-8-Live-x86_64 iso. When I boot from this disk all the wireless problems go away. It connects immediately. In F9 the services have been changed. There is a Network Manager but no NetworkManagerDispatcher. That would seem to indicate a major rewrite. This test seems to show that for some of us wireless support is broken. Bob Cahn -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Fri, 2008-05-30 at 13:46 +0100, Timothy Murphy wrote: The NM developers suffer from the delusion that NM always works. Of course it always works. Says so right here in the man page :-) poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Wed, 2008-05-28 at 23:00 -0430, Patrick O'Callaghan wrote: On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote: Hi, The PATH variable seems to already have a value in it: PATH=$PATH:$HOME/bin I should hope so. $PATH is where the Shell looks for commands to execute. It's a list of directories to look in. lspci and friends are in /sbin (or sometimes in /usr/sbin). /sbin/lspci etc. will run them. Or do this in .bash_profile: PATH=/sbin:/usr/sbin:$PATH Better is PATH=$PATH:/sbin:/usr/sbin There are some programs with the same name in both /bin and /sbin and /usr/bin and /usr/sbin that behave differently. If you are a regular user, you want the /bin and /usr/bin ones, not the /sbin and /usr/sbim ones. poc -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Wed, 2008-05-28 at 21:09 -0400, Marc Ferguson wrote: I tried the lspci command, but it says command not found. I'm logged in as root, in the terminal. Also; ifconfig, iwconfig are not found either? How do I get these back. How did you log in? I'm guessing you used su rather than su -. -- [EMAIL PROTECTED] ~]$ uname -ipr 2.6.23.15-80.fc7 i686 i386 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
Yes I did log in using su, what's the difference with the - option? Well I did get the lspci command to work. I exported it to a text file. As soon as I get to work I'll post the result. Thanks for the detailed help. VI is a very cool application, but hard to figure out at first. I spent a couple minutes in man and vim :help. On 5/29/08, Tim [EMAIL PROTECTED] wrote: On Wed, 2008-05-28 at 21:09 -0400, Marc Ferguson wrote: I tried the lspci command, but it says command not found. I'm logged in as root, in the terminal. Also; ifconfig, iwconfig are not found either? How do I get these back. How did you log in? I'm guessing you used su rather than su -. -- [EMAIL PROTECTED] ~]$ uname -ipr 2.6.23.15-80.fc7 i686 i386 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- Sent from Gmail for mobile | mobile.google.com Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
Hi, The PATH variable seems to already have a value in it: PATH=$PATH:$HOME/bin Add the actual path after what's there, i.e. PATH=$PATH:$HOME/bin:/search/path/1:/search/path/2 As for the locate command I got this error: locate: can not open '/var/lib/mlocate/mlocate.db' : No such file or directory As root, run updatedb which will then generate the mlocate.db. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
Yes I did log in using su, what's the difference with the - option? Well I did get the lspci command to work. I exported it to a text file. As soon as I get to work I'll post the result. Thanks for the detailed help. VI is a very cool application, but hard to figure out at first. I spent a couple minutes in man and vim :help. A simple su gives you root privileges with *your* shell environment, while su - gives you the full root shell, as if you had logged in at the console as root. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Thu, May 29, 2008 at 9:53 AM, Mike Burger [EMAIL PROTECTED] wrote: Yes I did log in using su, what's the difference with the - option? Well I did get the lspci command to work. I exported it to a text file. As soon as I get to work I'll post the result. Thanks for the detailed help. VI is a very cool application, but hard to figure out at first. I spent a couple minutes in man and vim :help. A simple su gives you root privileges with *your* shell environment, while su - gives you the full root shell, as if you had logged in at the console as root. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Excellent, thanks for that info. Here is the result of lspci: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Actiontec Electronics Inc Unknown device 2406 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f800 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci What can I learn from this info? Based on all the threads I'm guessing my wireless card isn't completely compatible with Fedora 9. The funny thing is everything works except for making the actual connection to a wireless network though. -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Thu, May 29, 2008 at 12:58 PM, Patrick O'Callaghan [EMAIL PROTECTED] wrote: On Thu, 2008-05-29 at 12:22 -0400, Matthew Saltzman wrote: On Thu, 2008-05-29 at 08:18 -0430, Patrick O'Callaghan wrote: On Thu, 2008-05-29 at 05:15 -0400, Matthew Saltzman wrote: On Wed, 2008-05-28 at 23:00 -0430, Patrick O'Callaghan wrote: On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote: Hi, The PATH variable seems to already have a value in it: PATH=$PATH:$HOME/bin I should hope so. $PATH is where the Shell looks for commands to execute. It's a list of directories to look in. lspci and friends are in /sbin (or sometimes in /usr/sbin). /sbin/lspci etc. will run them. Or do this in .bash_profile: PATH=/sbin:/usr/sbin:$PATH Better is PATH=$PATH:/sbin:/usr/sbin There are some programs with the same name in both /bin and /sbin and /usr/bin and /usr/sbin that behave differently. If you are a regular user, you want the /bin and /usr/bin ones, not the /sbin and /usr/sbim ones. Yes, but in the context of the question I'm assuming he's root, when you want it the other way round. Fair enough, but if he really is *logged in* as root (in a login shell), these should be in his path already. That's set in /etc/profile. If he su'd to root without the - (--login) option that would explain his problem. Correct. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Yes I did log into root without the hyphen. Once I logged in using: su - I am able to use ifconfig, iwconfig, lspci, etc. I did post the results of lspci, but I'm unclear what to do with the information in it. It doesn't look like an error occurred, but then again, I don't know what I'm looking at. Thanks. -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Thu, 2008-05-29 at 10:20 -0400, Marc Ferguson wrote: Excellent, thanks for that info. Here is the result of lspci: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Actiontec Electronics Inc Unknown device 2406 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f800 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci What can I learn from this info? Based on all the threads I'm guessing my wireless card isn't completely compatible with Fedora 9. The funny thing is everything works except for making the actual connection to a wireless network though. You have a Wavelan chipset, which should work using the Orinoco driver (already detected and loaded by the kernel). Now try 'iwlist scan' (again, as root). If the card works physically you should see a list of nearby access points. That means there is a strong chance of being able to get it to work, you just have to configure it correctly :-) Also, make sure the radio is physically turned on! On some laptops (e.g. Toshibas) there's a small switch to turn it on and off. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Thu, May 29, 2008 at 2:41 PM, Patrick O'Callaghan [EMAIL PROTECTED] wrote: On Thu, 2008-05-29 at 10:20 -0400, Marc Ferguson wrote: Excellent, thanks for that info. Here is the result of lspci: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Actiontec Electronics Inc Unknown device 2406 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f800 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci What can I learn from this info? Based on all the threads I'm guessing my wireless card isn't completely compatible with Fedora 9. The funny thing is everything works except for making the actual connection to a wireless network though. You have a Wavelan chipset, which should work using the Orinoco driver (already detected and loaded by the kernel). Now try 'iwlist scan' (again, as root). If the card works physically you should see a list of nearby access points. That means there is a strong chance of being able to get it to work, you just have to configure it correctly :-) Also, make sure the radio is physically turned on! On some laptops (e.g. Toshibas) there's a small switch to turn it on and off. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Hi, I did the iwlist scan and I noticed it did scans for: lo, eth1, wifi0, eth0, irda0, and pan0. My wireless device, according to Network Configuration is eth0. I find that weird; in prior distros wireless devices where labeled wlan0, wlan1, etc. The scan did pick up something for wifi0 and eth0. Does that mean that they are conflicting in some way? Overall; it looks like NetworkManager isn't playing nice with my wireless card and I'll have to do manual scans and configuring in order to get it to work? -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
I have updated my desktop using the 64-bit desktop of F9 from F7. My wireless is described by: 00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Netgear MA311 802.11b wireless adapter Flags: bus master, medium devsel, latency 32, IRQ 18 Memory at e9005000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Kernel driver in use: hostap_pci Kernel modules: orinoco_pci, hostap_pci Under F7 the wireless connected without any issues. The I'm using plain old WEP on the access point. When I attempt to connect the first NM pip turns green immediately but the second pip never does. Eventually I'm asked for the WEP key. Entering it again does no good. I've used system-config-network to statically enter the WEP key and specify the SSID. Nothing works. I've never been able to connect under F9. I notice that I'm never asked to unlock the keyring as I was under F5 and F7. Are there any other suggestions as to what I can try? /Bob Cahn -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Thu, 2008-05-29 at 14:56 -0400, Marc Ferguson wrote: The scan did pick up something for wifi0 and eth0. Does that mean that they are conflicting in some way? I don't think so. AFAIK the wifi0 is effectively a pseudo-interface on top of eth0. Something to do with how the kernel drivers are implemented, but don't take my word for it. Anyone who knows more about this is welcome to jump in at this point :-) poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
What wireless card do you have in your laptop? Olusola *I would like to know if anyone is having problems getting their wireless connection to actually connect in Fedora 9 using Network Manager?* I just installed Fedora 9 on my laptop (Thinkpad R40). I did not do the 76 updates yet, but out-of-the-box, my wireless won't connect. The LAN connects just fine, but not wireless. It's great that network manager does an auto broadcast, now. I put in my WEP information, which I triple-checked, but it says the connection has disconnected. I even tried it on WEPless access points and the same thing happens. -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
I have, based on my system-config-network, an Intersil Corporation Pri. To be honest - I'm not too clear what I have. On 5/28/08, Olusola Fadero [EMAIL PROTECTED] wrote: What wireless card do you have in your laptop? Olusola *I would like to know if anyone is having problems getting their wireless connection to actually connect in Fedora 9 using Network Manager?* I just installed Fedora 9 on my laptop (Thinkpad R40). I did not do the 76 updates yet, but out-of-the-box, my wireless won't connect. The LAN connects just fine, but not wireless. It's great that network manager does an auto broadcast, now. I put in my WEP information, which I triple-checked, but it says the connection has disconnected. I even tried it on WEPless access points and the same thing happens. -- Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- Sent from Gmail for mobile | mobile.google.com Marc F. ..Grace to you and peace from Him who is and who was and who is to come.. -Rev1:4 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + Network Manager = Wireless NOT Connecting
On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote: Hi, The PATH variable seems to already have a value in it: PATH=$PATH:$HOME/bin I should hope so. $PATH is where the Shell looks for commands to execute. It's a list of directories to look in. lspci and friends are in /sbin (or sometimes in /usr/sbin). /sbin/lspci etc. will run them. Or do this in .bash_profile: PATH=/sbin:/usr/sbin:$PATH poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
