Bug#336392: Acknowledgement (linux-image-2.6.14-1-686: 2.6.14 doesn't boot after dist-upgrade from 2.6.12)

[Olaf van der Spek <OvdSpek@LIACS.NL>]

Erik van Konijnenburg wrote:
> On Thu, Nov 10, 2005 at 11:25:43PM +0100, Olaf van der Spek wrote:
>
> > Erik van Konijnenburg wrote:
> >
> > > Could you do
> > >
> > > 	yaird --verbose --output=/tmp/pindakaas.img 2.6.14-1-686
> > > 	lspci
> >
> > debian:~# yaird --verbose --output=/tmp/pindakaas.img 2.6.14-1-686
> > yaird: goal: template, prologue (/usr/lib/yaird/conf/Default.cfg:52)
>
>
> (doing mouse and keyboard here ...)
>
>
> > yaird: goal: mountdir, / (/usr/lib/yaird/conf/Default.cfg:143)
> > yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/scsi/scsi_mod.ko {optionList=-- }
> > yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/scsi/sd_mod.ko {optionList=-- }
> > yaird: hardware: completed platform/host0/target0:0:0/0:0:0:0
> > yaird: action: mkbdev, /dev/sda {sysname=sda } {optionList=-- }
>
>
> The two modules are clear: Sda is a blockdevice on SCSI, so we mknod /dev/sda and
> we load the SCSI disk driver, which requires scsi_mod.
>
> But the SCSI host0 claims it's managed directly by the platform, without any controller

Is that a hardware or software (driver) issue?
If it's a driver issue, shouldn't this report be copied/moved to the 
kernel package?

> to manage the bus, so yaird sees no reason to load any SCSI/PCI modules.
>
> Solution: if the SCSI bus is managed by a controller that needs a driver,
> make sure the driver that manages the controller makes itself visible in /sys.
>
> Workaround: in /etc/yaird/Default.cfg, before MOUNTDIR, use the keyword 'MODULE'
> to load whatever modules your system needs.
>
> I see no manageable way to detect and repair this kind of misleading /sys directory
> automatically in a standard yaird distribution.

I'm wondering, how did it work before?
--
Olaf van der Spek
http://xccu.sf.net/