Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free.
I am trying to install SuSE 7.1 with no luck on a Compaq Presario with AMD 750 processor. It boots up the CD fine and goes through initializing until it tries to detect hardware. The disk drive light stays lit and just sits idle. I have been waiting for a response from SuSE for over a week now. Any help would be greatly appreciated.
1. boot from your linux CD and choose rescue mode
2. mount your linux partition and go to /etc/rc.d/rc3.d directory
3. if you'll find a link that's name starts with an 'S' and has 'kudzu' in it remove it or change to K(somethink)kudzu
the hardware detection won't run next time
if you really care about that you will need to read kudzu documentation
Thanks, nedo. It was the USB keyboard that was causing the problem. I unplugged it during the initial installation process and plugged it back in once it got to the YaST screens and it worked just fine.