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.
I recently installed SuSE 8.2 on a Gateway Solo 5300
For the most part the entire install went smoothly, but there is one hard-ware related issue that is really driving me nuts!
It seems that whenever there is any type of "hardware detection"? The keyboard locks up.
Literally, this will not occur at all during normal use, but if I need to re-configure any hardware device - the keyboard will lockup during the split second stage of "hardware detection". For some strange reason, it will also happen if I need to make changes to software.. so again, once yast loads the "install software" module - the keyboard is gone. The keyboard is locked up in -both- kde and the console mode... so I assume this is some type of irq conflict??
I use a USB mouse, so I noticed when I am sometimes able to get it to work again, if I create a new session using "Start New Session" under the main kde menu... Most of the time if I do this, the keyboard will start working again, so Im not sure if this is an issue that sometimes will fix when the X server resets...
I have seen other posts related to this, but they involve APM or a set amount of time... This -just- happens when there is some type of hardware detection. I can work for 15 hours straight without a hitch until I need to go and fetch some software, or change any settings to hardware.
My hardware attached to the laptop:
USB Logitech Mouse
USB CDMA modem for cell phone
Anyone know what I can try to prevent from happening?
I have a similar problem. I have a Gateway 5300 with a Logitech USB Mouse and I have been unable to fully loaded Suse 8.0 or 8.2 because the keyboard always locks up. I have loaded and ran Red Hat, Mandrake and Debian with no problem. Suse has no answer for the problem. I bought 8.0 and registered it but the tech support, which sucks by the way, had no idea what to do. If you ever get an answer and a fix for this problem please post it here. I check back every now and then to see if anyone finds a fix.
hi, i have a solo5300 too, but i dont have the original cdrom drive, i have a floppy and a dvd/cdrom drive, i cant get it to boot from the cd and im sure i have the bios configured properly, i need to install an operating system.
if this makes any sense to you, and you can help me out that would be awesome!
also, one more thing, have you found a battery made by someone besides gateway?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.