Lubuntu- Wireless works fine in LXDE, but not icewm or openbox
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Lubuntu- Wireless works fine in LXDE, but not icewm or openbox
I have an older laptop (P4 Compaq Presario 2110; 512mb RAM) on which I installed Lubuntu 10.10. I am using a Buffalo wireless G PCMCIA card (Broadcom 43xx chip set) on the LXDE side which works perfectly. Out of curiosity I installed 'icewm' and 'openbox.' My wireless card shows when I check lspci as "UP." Using wicd, I can see networks, but my router will not resolve an IP address. NetworkManager does nothing.
I have tried using both ifconfig and iwconfig commands with no love.
Is this something inherent with lighter WMs and desktops? Is there a means to allow my router assign an IP and why would it be different for a different WM? Should the IP address be assigned to the computer?
I dont think you can have wicd and Networkmanager at the same time. Did you install wicd using either apt-get or synaptic? Also, I am not sure how your network is layed out; however, its very easy to set it to the wrong encryption type. You could always try to connect and then watch your logs while the laptop tries to authenticate. It might lead you to what is causing your issue. Also, could you post the output of iwconfig and ifconfig? I have a feeling your problem may be something simple. If you have an older laptop ( maybe your wireless card is older aswell) you might be dealing with a b/g card trying to connect to N. Any way, hope this gets you pointed in the right direction.
8)
wlan0 IEEE 802.11bg ESSID: off/any
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr: off Fragment thr: off
Power Management: off
Perhaps you misread my post? I am not using wicd and NetworkManager at the same time. I normally use NetworkManager, but since I could not resolve an IP address, tried wicd. The problem is not my configuration, as I am posting this on the laptop in question. When I switch to icewm, everything starts as normal, but I cannot resolve an IP address... I'll ask again; is there something missing from a window manager that is standard in a desktop environment? Are there files or programs that I need to launch manually that I am overlooking?
Last edited by FunkyPenguin; 01-16-2011 at 11:11 AM.
O, I did misread. I am sorry. However, wicd should work irregardless of the WM your using. I say this because you can run it with out X. I apologize for wasting your time.
Me too. I cant see what a WM would have to do with networking issues. NetworkManager is gtk and wicd has ncurses. I really dont understand why wicd would fail to work for you. Have you tried loading the WM that DOES allow you to connect, then killing it? You could then try stareting up the problem WM and see if it causes the connection to drop. Might help you debug it. Also, your logs will show the authentication process with the router. Perhaps check the log and see if the connection process is even making it that far. Good luck.
Thinking out loud, if I were to manually assign the IP that I am able to get automatically when on LXDE I should be able to connect, right? It is a legitimated IP lease assigned by my router...
No and Yes. The IP is assigned by your router. You need to think of what TCP/IP is. IP is actually like a whole protocol onto itself. So, if you assign a static IP of 192.168.1.1 to the desktop, then try and connect to you router at 192.168.1.2 with out a route your request will fail.
If you are not authenticated with the router you will be unable to do anything. once you authenticate you will be able to get a route to send traffic over. Tht is why I was telling you to watch your logs while trying to log into the router / LAN.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.