Hi, I've been running slackware for about a year, but just recently had started to get random kernel panics. I had been screwing around so I decided to do a new install of 9.1 to try fixing the problem, but am now unable to get to the setup program. When I try booting off the CD I get only so far loading the barei.i image until it hangs after these lines:

1 ramdisk: compressed image found at block 0
2 crc error<6> Freeing initrd memory: 2500k freed
3 VFS: Mounted root (ext 2 filesystem)
4 Freeing unused kernel memory: 116k freed

Occaisonly these extra lines are output before it hangs:

5 ext2-fs error(device ramdisk(1.0); ext2_check_page: bad entry in directory #11 2: unaligned directory entry- offset ignored
6 <basically the same as 5>
7 <basically the same as 5>
8 <basically the same as 5>
9 <basically the same as 5>
10 kernel panic: no init found. try passing init=option to kernel


Can anyone tell me what is wrong?

Umm, have you checked you iso after the download?

Edit: Do you have a not common hardware setup? (SCSI, S-ATA, or something in that direction)

I had a similar problem, when trying to boot from Slack 9.1 CD, i get allways a kernel panic, until i find out that it dosent like any USB devices pluged...
If you got any USB device, just unplug it, boot from the CD, after the kernel is loaded, plug in the USB devices again...
It worked for me, and it wasn´t a bad ISO problem...
Good luck.

The SIN Raven

Misel: No I haven't checked the ISO, how can I do that? Also, the hardware setup is normal, slackware used to install fine.

Raven: I tried connecting my keyboard with a USB->PS2 converter on and it still didn't work. I also tried it with the 9.0 CD which used to work and got the same results (with slightly different error messages.)

I'm thinking this might have something to do with hardware, but from the error messages I'm not sure what...

Yes it might be hardware.
It was only a trie, with Slack 9.0, i get no errors, but with 9.1 i get them.
The only thing better them gessing it´s for you to trie to thake out hardware step by step until you find what it´s giving you the error.
This is what i did, but not need to go far...
Unless anyone has a more usefull opinion, i dont seam other way to do it...
For the messages that you receided, i´m betting in you hard disks...
Or they have bad sectors, or the partitions became corrupted...
Why not start from there?
Sorry if i can help you more.

The SIN Raven