laptop wireless won't connect in KDE but works in Gnome (Fedora 13)
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
laptop wireless won't connect in KDE but works in Gnome (Fedora 13)
After searching/googling for information related to the topic, I haven't been able to get this working in KDE.
Background: I have a Dell Studio 1745 with builtin Intel 5100bg wireless card. It connects to my Linksys WRT54G router just fine in openSUSE 11.2 & 11.3 using either KDE or Gnome. In Fedora 13 it only connects under Gnome, not KDE. Those are using NetworkManager. Using traditional ifup only works in Fedora under Gnome, i.e. nothing works under KDE in Fedora.
Error org.freedesktop.NetworkManagerSettings.InternalError: unable to get the connection D-Bus path
Error org.freedesktop.NetworkManagerSettings.InternalError: unable to get the connection D-Bus path
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.
Determining IP information for wlan0... failed; no link present. Check cable?
Steps taken so far:
1) completely deleted NetworkManager (and depends) with yum remove.
2) Removed all wireless related files in /etc/sysconfig/.
3) Re-installed wireless network in System > Admin > Network
No matter what I have done, the wireless refuses to work in KDE on Fedora. I've temporarily resorted to having my wife string a 50ft patch cord from the router in the basement to my laptop (I'm disabled, can't climb stairs).
Does anyone have a suggestion of what else I might try?
Since the wired network works, it may be that the network manager is the problem. When you reinstalled the network manager, did you reinstall the Gnome network manager?
If so, I can say I have found it to be unreliable except under the Gnome interface. For what it's worth, here's my experience.
I have a netbook running Ubuntu 8.04 (factory installed Ubuntu that does not automatically update versions--maybe it's a netbook thing; it works and I'm not going to mess with it). The Gnome network manager will connect to my wireless when I start the computer (from a restart or powered off condition) in Gnome, but not when I start it in Fluxbox. If I start it in Fluxbox, the Gnome network manager icon just rotates making pretty circles.
If I start it, go into Gnome, make the network connection, leave Gnome, then start Fluxbox, the connection works fine until I actually reboot or power off (I did an "uptime" before I powered it off the last time--it had been up for over 9 days, during which time I had commmonly logged out over-night.
In contrast, I have a laptop running Ubuntu current (it started with factory installed 8.04 but has lived through all the version updates). Early on, I replaced Gnome network manager with wicd. That box connects flawlessly to any wireless network, regardless of the window manager I use after powering up or rebooting.
In my experience, Gnome network manager does not play well with anything but Gnome on boot. YMMV.
Since the wired network works, it may be that the network manager is the problem. When you reinstalled the network manager, did you reinstall the Gnome network manager?
As stated in my original post, I did NOT reinstall NetworkManager.
Quote:
If so, I can say I have found it to be unreliable except under the Gnome interface. For what it's worth, here's my experience.
I have a netbook running Ubuntu 8.04 (factory installed Ubuntu that does not automatically update versions--maybe it's a netbook thing; it works and I'm not going to mess with it). The Gnome network manager will connect to my wireless when I start the computer (from a restart or powered off condition) in Gnome, but not when I start it in Fluxbox. If I start it in Fluxbox, the Gnome network manager icon just rotates making pretty circles.
If I start it, go into Gnome, make the network connection, leave Gnome, then start Fluxbox, the connection works fine until I actually reboot or power off (I did an "uptime" before I powered it off the last time--it had been up for over 9 days, during which time I had commmonly logged out over-night.
In contrast, I have a laptop running Ubuntu current (it started with factory installed 8.04 but has lived through all the version updates). Early on, I replaced Gnome network manager with wicd. That box connects flawlessly to any wireless network, regardless of the window manager I use after powering up or rebooting.
In my experience, Gnome network manager does not play well with anything but Gnome on boot. YMMV.
I'll have to give that a try if wicd (which I'll download tonight) doesn't work. Right now I've been able to get wired eth0 working by ifup method which it wasn't doing in KDE previously under F13. Oh, and I also re-installed F13 from DVD without NetworkManager.
I kicked myself this afternoon for not suggesting another possible test would be to try connecting by editing the wireless configuration file. It's not an ideal way for day-to-day use--something like wicd or some other network manager frontend is a lot easier to work with, but it might be a good test.
In Slackware, it's /etc/rc.d/rc.wireless. But, frankly, I don't know whether Fedora has an rc.wireless or equivalent--a search was not very comforting; my Ubuntu machine appears not to have one.
Distribution: Mepis and Fedora, also Mandrake and SuSE PC-BSD Mint Solaris 11 express
Posts: 385
Rep:
I had the same problem. I installed wlassistant while in Gnome (which does get Internet when KDE doesn't) After that, I restarted in KDE and ran wlassistant. My hidden WPA-Personal network showed up and I got on. Weirdly enough, it let me configure the wireless but not use it.
The solution has been posted elsewhere in LQ, but is worth repeating.
The solution has been posted elsewhere in LQ, but is worth repeating.
Would you mind posting a link?
Thanks, OP, for starting an interesting discussion -- I'm hoping for insight in getting wifi working on my MEPIS 8.0 (KDE 3.5.12) secondary install on my Eee PC 8G.
Distribution: Mepis and Fedora, also Mandrake and SuSE PC-BSD Mint Solaris 11 express
Posts: 385
Rep:
Quote:
Originally Posted by archtoad6
Would you mind posting a link?
Thanks, OP, for starting an interesting discussion -- I'm hoping for insight in getting wifi working on my MEPIS 8.0 (KDE 3.5.12) secondary install on my Eee PC 8G.
Actually, the solution is pretty simple. Using Gnome Xfce or whatever other desktop does get wireless, install wlassistant. I used yum, but there is no reason why yumex or kpackagekit wouldn't also work. If there is no wireless to be had, then use a wired connection, somewhere you can get Ethernet or a wireless Ethernet bridge (WET-54g)
Configure your connection like normal using KDE's tools. The tools will allow you to set up the connection, just not activate it. Wlassistant did allow me to get online in KDE. Of course, the other solution is to just give up and use Xfce or Gnome instead.
------------
Mepis...
After you install Mepis, try to restart the machine and run synaptic for updates. You may have to use wired Ethernet for the first update, another words plugging your netbook directly into your modem or router. Run updates for everything. Then use Synaptic to search for a wireless driver for your NIC, if it hasn't already done so itself. Of course, using a Wireless Ethernet bridge on an open network will also work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.