Christoph Hellwig a écrit : > On Mon, Sep 13, 2004 at 09:37:23AM +0200, Milan Kuchta wrote: > >>Package: kernel-image >>Version: 2.6.8-1-k7 >>Severity: critical [...] >>Kernel panic: Attempted to kill init! > > This looks very much like you're missing an initrd or something. How > does your lilo/grub config look like? >
Hi, I've the same issue with a custom-build of latest 2.6.8-1 tree. I think I compiled every required functions into the kernel (not as modules). So I presumed I should not need initrd. On the other hand, AFAIK, initrd is used to load modules that are required to access '/' disk (and the modules on it:)
The context:
I wanted to build my own version of kernel because my HDs (2 serial-ATA disks - Maxtor and Seagate) were handled as SCSI disks by Debian version installed by d-i.
I wanted to get the usual IDE disks management because I have currently an unexpected SERIOUS ISSUE with VERY LOW THROUGHPUT when copying files between both S-ATA drives (detected as /dev/sda and /dev/sdb).
I have asked around and heard rumored problems between Seagate disks and Silicon Image controller.
Current question I try to resolve:
Do I need SCSI management to use S-ATA disks on a 3112 Silicon Image controller ?
Cordialy, David.
