Slackware 10.2 hangs

hylke · 09-29-2005, 09:13 AM

Hello,
I've updated Slackware 10.1 to Slackware 10.2, but it hangs after it says:

Quote:

hdd: ...

I first found that problem when I forgot to run lilo after upgrading my packages, I wanted to rerun lilo by mounting my harddisk, but it didn't wanted to start(same error as I have now).
So I ended up using an old version SLAX and installed lilo.
But now I have that error.
Any idea how to fix it?
Thanx in advance,
Hylke

hylke · 09-29-2005, 12:29 PM

I think this is a kernel problem, but i'm not sure about that.
Btw, my dvd reader/writer(hdd) is a HL-DT-ST gcc-* thing.
It worked fine with 10.1 and down.

dracolich · 09-29-2005, 03:18 PM

What kernel are you using and what does your lilo.conf file look like?

Haiyadragon · 09-29-2005, 04:05 PM

If it's a Lilo problem try using Grub. Once you're use to the config file it's so much more robust. Especially because it won't barf everytime you forget to run lilo.

hylke · 09-30-2005, 01:50 AM

Quote:

Originally posted by dracolich
What kernel are you using and what does your lilo.conf file look like?

I gues the one that I installed with Slackware 10.2(although i'm not sure, since I only upgraded the packages).
My lilo configuration looks like this:

Quote:

boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
change-rules
reset
vga = normal
menu-title = "Hylke's computer"

image = /boot/vmlinuz
root = /dev/hda1
append = "max_scsi_luns=7"
label = "desktop"
read-only

image = /boot/vmlinuz
root = /dev/hda5
label = livecd
read-only

Quote:

If it's a Lilo problem try using Grub. Once you're use to the config file it's so much more robust. Especially because it won't barf everytime you forget to run lilo.

I gues your right, cus my other OS(which used to work fine), has the same problem.But i'm not planning to change to grub.

dracolich · 09-30-2005, 07:12 AM

If you're using just the kernel that came with 10.2 it's 2.4.31. You might want to go to the source directory in /usr/src/linux-2.4.31 and run make menuconfig to make sure it has correct settings for your system. There might be things missing and other things installed that you don't need. Or if you still have your old kernel image you can adjust lilo.conf to boot it instead. In the meantime try changing that append line to read

append = "ide-scsi"

and see if that helps. That's the only append required to enable burning. I've never used a max_scsi_luns parameter before and never had problems. Whenever you change lilo.conf don't forget to run the lilo command to enable the changes.

hylke · 09-30-2005, 07:52 AM

max_scsi_luns was to make my cardreader work.
And I think i'm still using the same kernel, because I only upgraded and installed new slackware packages, and if i'm right, the kernels are in a special directory.
replacing max_scsi_luns to ide-scsi did not help at all, the problem remains.
Btw, it also gives the warning:

Quote:

/proc/partitions doesn't exist, hd scan bypassed.

hylke · 10-01-2005, 02:50 AM

And is there someway to deupgrade all the packages so it will work again?
Thanx, Hylke

hylke · 10-02-2005, 04:21 AM

I've tried installing the older version of lilo that came with Slackware 10.1, but for so far as I can see, that did not make any difference at al.
So maybe it's not the problem of lilo after all.

dracolich · 10-02-2005, 01:08 PM

According to your posted lilo.conf your kernel is called, vmlinuz - the same name as the one Slackware provides with the install discs. So if you upgraded packages without skipping that one it overwrote your original.
A missing /proc/partitions makes me think the pseudofilesystem support is not loaded. My suggestion is to change the kernel. Either run make menuconfig and fix the one that's there (2.4.31), or download the source of a new one and build it (www.kernel.org).
When you do get your kernel working edit the filename a bit, something descriptive like vmlinux-2.4.31, edit your lilo.conf accordingly and rerun lilo. That way if you upgrade again for the next release it won't overwrite your working kernel. It also allows you to have multiple kernels to choose for booting.

hylke · 10-04-2005, 09:14 AM

Quote:

Originally posted by dracolich
According to your posted lilo.conf your kernel is called, vmlinuz - the same name as the one Slackware provides with the install discs. So if you upgraded packages without skipping that one it overwrote your original.

What do you mean with the last sentence?

Quote:

A missing /proc/partitions makes me think the pseudofilesystem support is not loaded. My suggestion is to change the kernel. Either run make menuconfig and fix the one that's there (2.4.31), or download the source of a new one and build it (www.kernel.org).
When you do get your kernel working edit the filename a bit, something descriptive like vmlinux-2.4.31, edit your lilo.conf accordingly and rerun lilo. That way if you upgrade again for the next release it won't overwrite your working kernel. It also allows you to have multiple kernels to choose for booting.

So, is the only thing I need to change in my current kernel the pseudofilesystem support?
And should it be compiled as a module or in the kernel?
Thanx in advance,
Hylke

hylke · 10-06-2005, 11:33 AM

I finally managed to fix it.
What I did was, I installed the kernel sources that came with 10.1, and compiled a new kernel.
After that my sound still wouldn't work, so I installed alsa that came with 10.2, but that didn't seem to work either, installing the version that came with 10.1 did the trick.
Greetz Hylke

dracolich · 10-06-2005, 12:02 PM

Sorry for taking so long to answer your question. Glad you found a solution. Anyway...

Quote:

According to your posted lilo.conf your kernel is called, vmlinuz - the same name as the one Slackware provides with the install discs. So if you upgraded packages without skipping that one it overwrote your original.

Uprading the packages doesn't prompt before it overwrites files. And it doesn't make backups of old files except configs in /etc and scripts in /etc/rc.d. So if you had a the kernel-2.4.29 package from 10.1 installed this created the vmlinuz file in /boot. If that name doesn't change and you run upgradepkg on the kernel-2.4.31 package with 10.2 then the existing vmlinuz file will be replaced with the new one without asking. That's why I finetune my kernels and then rename them something descriptive such as vmlinuz-2.4.31 or bzImage-2.6.13.2. That way the old file won't be replaced during an upgrade because the filenames aren't the same.