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.
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 have managed to damage linux (again) I wish I could relate what I had done that caused the problem, but unfortunately, I just do not know.
When squeeze/sid is booted it gets as far as the signon panel then becomes totally non-responsive. Except that ALT+SYSREQ+R makes it possible to enter CTL+ALT+F1 to get a command prompt - which is useable. (but does not cause any other entries or key strokes to respond).
Any guidance in finding and fixing the cause of the problem would be greatly appreciated.
okay, particularly, a hardware lockup could also do it.
be very specific: is the cpu at 100%? Is the disk going regularly?
Take off anything you don't need and try a boot. Also, boot from an install cdrom.
The motherboard has a dual core processor ---- neither one ran more the 35% -- not continually, but what I would expect cpu activity to look like. Some other things I discovered: If I boot to the recovery session, I can log in as 'user' and issue a startx, and I will have my desktop displayed.
It looks like it gets hung up displaying the signon screen an before letting me input the user/password.
I appreciate your suggestions and comments -- And I plan to try the suggestions you made; But --- I thing I am going put that aside while I work on getting the current stable version of squeeze installed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.