slackware boot stops

Tintapok2 · 10-04-2007, 02:24 PM

Hi folks,

I have the following problem. I installed slackware 12 on a hp pavilion dv9565.

The booting process usually stops at the phase when the kernel writes to the console the following message:

NET: Registered protocol family 2

After that I either have to press the power button, or plug the power cable out. Then the booting process continues.

Does anyone has an idea what could be wrong or what should I check?
I would appreciate any help.

Thank you, and have a nice evening, guys.

Tintapok.

adriv · 10-04-2007, 04:11 PM

I found two possible solutions:
1. http://en.opensuse.org/SDB:Installat...ol_Family_2%22 (this is about SuSE, but it may give you a lead)
2. http://www.linuxquestions.org/questi...kernel-464619/ which leads to this
http://www.nabble.com/Re:-Kernel-boo...p13000875.html

Tintapok2 · 10-05-2007, 03:14 AM

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.

T.

Tintapok2 · 10-05-2007, 05:29 PM

I recompiled the latest kernel. No luck.
Does anyone suspects what could be wrong?
Thank you.
T.

rherbert · 10-05-2007, 10:34 PM

Quote:

Originally Posted by Tintapok2

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.

Richard

WindowBreaker · 10-20-2007, 11:57 AM

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".

Post your results.