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.
Hi,
Thanks for the reply.
Unfortunately none of the kernel parametrization suggestions worked.
I am going to try to recompile the latest kernel. Maybe that helps.
I recompiled the latest kernel. No luck.
Does anyone suspects what could be wrong?
Thank you.
T.
I'm not sure what's going on - my system locks up when I try to mount my two NTFS partitions during boot via /etc/fstab, and this only since I upgraded from kernel 2.6.15 to 2.6.22. Anyway, my "solution" is to comment out the offending lines in /etc/fstab, and mount my partitions manually after logging in. So check /etc/fstab for a possible clue to your lockups.
Whatever is making the system lockup is probably caused by either a hardware conflict or module problem.
Here is how I would approach it. Boot into your laptop's BIOS, and disable as many built-in devices as you can (AUDIO, LAN, iR, etc).
Then reboot into slack. Sure, you won't have a NIC, but see if it boots now. If it does, now go back into the BIOS, and re-enable just one device at a time, probably starting with your NIC. See if it boots. So on and so forth.
Assuming slack boots with all devices disabled, you should, by using this process, either isolate the problem to a single piece of hardware, or a combination of hardware. For instance, you might find that slack will boot with the NIC enabled, or with just the AUDIO enabled, but not both. If that's the case, take a look at the BIOS settings for Plug-n-Play OS, and "reset configuration data".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.