SlackwareThis Forum is for the discussion of Slackware Linux.
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.
My Thinkpad X200 has been running Slackware64 perfectly up until the last few boots, when it's developed the problem shown in the attachment. As suggested at the bottom of the screen, a reboot fixes it - 'til next boot. A brief websearch revealed bad RAM could be the cause, so I ran Memtest and it passed OK. Any ideas as to the cause and possible permanent fix?
Some of the RAM problems I've had on laptops were only found by running memtest for a day or two. Running memtest for only a couple of hours didn't find the problem (possibly heat related).
IF you can easily access the RAM boards and there are more than one you could try reseating the boards, booting with only 1 board at a time, or swapping the location of the two boards.
You may also experiment with booting through a USB port or replacing the disk temporarily or run smartctl to see if it may be a disk issue. You may also want to reseat the disk/SSD.
Sometimes the hardware is good but there is just a bad "connection".
I don't have a Thinkpad X200 so I don't know how easy it is to access the hardware.
IF you can easily access the RAM boards and there are more than one you could try reseating the boards...
You may also want to reseat the disk/SSD.
Sometimes the hardware is good but there is just a bad "connection".
Just tried those two options, and it booted up OK. I'll see what happens with the next two boots before I celebrate.
Thanks, both of you, for your help and suggestions.
Does the output is after setting debug boot parameter? Is it your default boot? Boot kernel with default parameters (as set in lilo.conf)? Or have you enabled additional debug level? I want to know simply, may something like this will happen to me I would try to play with debugging boot process with means given by boot parameters. For curiosity. And because it is good to know things. But, well, luckily it is not now .
I looked around. Some people refer this as battery/power issue, or video. Some report booting live system ok. So maybe to try to boot any other kernel, from usb, or CD?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.