Cursor disappearing after suspend and wifi question
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.
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.
Cursor disappearing after suspend and wifi question
Hey all,
I have searched and searched for an answer here, Google and at the PCLOS forums. I desperately do not want to have to use XP on this laptop but the cursor issue at least is a deal breaker for me. Here the deal:
Installed PCLOS on a Dell Latitude 100L, all seemed to work well, including suspend for the first day or two, then for no apparent reason I can see when it would wake after suspend I would have no cursor. If I moved it on the touch pad or with my wireless mouse things on the screen would react as if it was there, just no pointer to be seen. I have read things that point to this being a common issue but darned if I can find any posted solutions to it. That's the deal breaker.
Now for what is probably operator error:
I bought a Dynex wireless G notebook card from Best Buy as I had read several reviews online of people saying how well it worked with Linux and how surprised they were by that. I have never configured a wireless card in Linux (or really Windows for that matter as this is my first ever laptop) So I am fairly sure this is the easier of the two to fix, I just dn't see what I have done wrong.
Like I said, I really don't wnat to have to put windows on it if I can avoid it. I have been using PCLOS on my primary PC for months now and Ubuntu for several years before that. Everything else works great with PCLOS on the laptop, it's just what's not working is a real show stopper.
If anyone can help, please do, I will be very, very grateful indeed. I have posted this at the PCLOS forums but after two days lot's of looks but no response except a bump by me.
did you set your bios to none plug n play or none windows or none os what ever you bios say when your not using windows. make sure your grub or lilo pass the command acpi=on as far as your curor in bios you have two setting one or both. yeap you can run the on board cursor or the plug ps2 or usb . set it to what ever one you want good luck .
Not sure what's up with the cursor problem, but to figure out the wireless driver, you need to know the chipset that card uses. Try running lspci and see if the card is listed. If not, it might be time to hit google and see if that info is out there.
OK, the 4318 presents a little bit of a problem. It supposedly has native linux drivers (bcm43xx on kernels earlier than 2.6.24 and b43 on 2.6.24 and later) however, it doesn't work very well with those. The alternative is ndiswrapper, which allows Windows drivers to function in Linux. To be honest, for this chipset, ndiswrapper is probably the way to go. However, make sure you don't have a 2.6.24 or later kernel as 2.6.24 broke ndiswrapper. Supposedly there is a patch out, but I haven't messed with it yet so I can't comment on how good it is. If you go the ndiswrapper route, be sure to blacklist the native linux driver (bcm43xx or b43) as having both ndiswrapper and a linux driver loaded at the same time will cause trouble. Be sure to visit the ndiswrapper wiki site as they have a lot of excellent installation instructions.
OK, the 4318 presents a little bit of a problem. It supposedly has native linux drivers (bcm43xx on kernels earlier than 2.6.24 and b43 on 2.6.24 and later) however, it doesn't work very well with those. The alternative is ndiswrapper, which allows Windows drivers to function in Linux. To be honest, for this chipset, ndiswrapper is probably the way to go. However, make sure you don't have a 2.6.24 or later kernel as 2.6.24 broke ndiswrapper. Supposedly there is a patch out, but I haven't messed with it yet so I can't comment on how good it is. If you go the ndiswrapper route, be sure to blacklist the native linux driver (bcm43xx or b43) as having both ndiswrapper and a linux driver loaded at the same time will cause trouble. Be sure to visit the ndiswrapper wiki site as they have a lot of excellent installation instructions.
Thanks. If you might be able to recommend a card that is a bit easier to get working in PCLOS, I have no problem taking this one back and buying one a little more linux friendly at all, even if it's a bit more money. If I can get this issue as well as the no cursor after suspend issue sorted I will be golden. Like I said I really DO NOT want to install XP but those two issue are deal breakers when it come to a laptop I will be doing work on. I will also hate not having Bluefish to use either- that will be a true tragedy!
If you might be able to recommend a card that is a bit easier to get working in PCLOS
Linux is a bit different in that you have to pay attention to the chipset rather than the card brand. Intel actively supports Linux driver development as does Atheros, so cards with either of those chipsets would be a good choice. But to be honest, ndiswrapper isn't hard to get going (at least not any harder than Intel or Atheros), it is just the victim of a temporary spat with the kernel development team. You'll have to do a little console work, but ndiswrapper is really pretty easy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.