[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#276379 acknowledged by developer (Bug#276379: fixed in discover1-data 1.2004.11.09)

On Thu, Nov 18, 2004 at 06:03:54PM +0100, Timo Veith wrote:
> After the inital reboot, the kernel panics with "Kernel panic: Attempted 
> to kill init". A few lines before that error one can see the message 
> "bla ... megaraid.o ...init_module: No such device". This is not the 
> right module. I don't know where this gets loaded but it's wrong.

Ugh, it's because /proc/scsi/megaraid exists when meagaraid2 is loaded
and it fools initrd-tools into throwing the megaraid.o module (which
probably doesn't work) into the ramdisk. It's a problem that we've been
encountering and it's just a side effect of really poor infrastructure
for this kind of thing on the kernel side.

We can fix it in the Debian kernel, I'll throw a patch into the queue.

> What shall I do, report a new bug? I think it's got something to do with 
> the initrd being built the wrong way or not loading the megaraid2 
> module in that phase of the boot process.

Ah, yeah, you're correct.

> What is more:
> When I use "linux26" at the boot prompt,the d-i fails when it comes to 
> detecting disk drives. Not only maybe because it doesn't detect the 
> PERC Controller's PCI ID, but because there is no driver in kernel 

What image is this? megaraid.o is in the scsi-extra-modules package.
Does it want to use megaraid2? If so, I can fix that.

Joshua Kwan

Attachment: signature.asc
Description: Digital signature

Reply to: