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 have suse10 installed on my Compaq Presario M2000 laptop, both 32 and 64 bit versions.
The 32 bit install won't shut down/reboot properly. It makes it until the message:
'The system is rebooting, please stand by..' but then it freezes with funny colorful patterns stuck to the screen and I manually have to hard-reset.
Any ideas?
It's hard to say. Check for logs for starters. Then examine /et/rc.d/rc.0 or the equivilant shutdown file that SuSe provides and see which program might be causing it to hang.
Unfortunately I don't really understand much of what's going on in those files but halting the computer goes fine, only the reboot freezes. After the message:
'Sending all processes the KILL signal'
there are 3 blank lines, for two of them the status is 'done' but the middle one says 'missing'.
Is there a way to find out what exactly is going on during reboot/halt?
Also during bootup there is an error message that says:
<3>udev[2057]: run_program: open /dev/null failed
<3>udev[2057]: run_program: exec of program '/sbin/modprobe' failed
There is no accessible dev/null directory on the system and trying to manually create it the system says it already exists.
I guess that might have to do something with the reboot issue.
Unfortunately I can't really use Slackware since I don't have a distro specific driver for the conexant modem. Are you using your modem by any chance?
alma
I would be worried about those udev messages. I have similar reboot issues with my Compaq Armada 100s. It just didn't not work. If I recall correctly, I was once able to fix the problem by changing APM parameters in Kernel Configuration.
Anyway, those reboot lockups should not damge your system if Linux halted in a controlled manner before the lockup occurs.
I figured that it's not a big issue alone, i only have to shutdown and manually restart. I just tend to think that it might have to do something with other bugs I have.
Anyway, thanks for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.