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

Bug#284961: kernel-image-2.4.27-1-smp: kernel-image-2.4.27-1-* does not detect proper SCSI Controller.



Hi Greg,

On Tue, Apr 05, 2005 at 10:17:49PM -0400, Greg Folkert wrote:
> I can arrange an account with sudo access.

> As long as we do the account info off-bug.

> On Tue, 2005-04-05 at 18:06 -0700, Steve Langasek wrote:
> > Hi Greg,
> > 
> > Apologies for the dormancy on this bug; yours is one of several RC bugs on
> > initrd-tools that have been long in the resolving, so it's not just you...
> > FWIW. :)
> > 
> > You mentioned being able to get access to this machine for debugging.  Is
> > that still a possibility?
> > 
> > Thanks,

Bad news... I can't reproduce this problem, even on your machine. :)  Can
you tell me what kernel you were running at the time you saw the problem?
Your initial report was from a machine that was running 2.4.27-1-smp, so I
assume you got this kernel working using MODULES=most in mkinitrd.conf and
then reported the bug; does that agree with what you recall of the
situation?

I suspect this problem was caused by a module name change in the kernel,
where earlier you might have been using sym53c8xx instead of sym53c8xx_2, so
the wrong driver name was detected based on which module was currently
running.  Fixing this in initrd-tools therefore probably means introducing
some special-casing to mangle this module name according to the selected
kernel version.

If you are still able to reproduce this bug on your system, please let me
know how it's manifesting, in case I'm overlooking something.

Thanks,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: