Skip to Content.
Sympa Menu

baslinux - Re: [BL] BL3 and SCSI

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: baslinux AT lists.ibiblio.org
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] BL3 and SCSI
  • Date: Sun, 27 Jul 2008 13:38:45 +0000 (UTC)



Sindi Keesan wrote

Message from Steven
===================
Sindi wrote:

CONFIG_SCSI_AIC7XXX=y
PCI card.
All my scsi cards and even onboard scsi
controllers have used this driver.
insmod aic7xxx (if that is your controller)
after booting with the 'big' kernel.

The problem is: the root filesystem resides
on a SCSI HD. The kernel must be able to mount
the root filesystem before anything else can
happen (i.e. insmod). Therefore, the correct
SCSI driver must be compiled into the kernel
(not a module). Otherwise, it will not be able
to identify the HD that holds the root filesystem.

That's why I suggested the Slackware scsi.s kernel,
which has all possible scsi drivers compiled into
the kernel. The scsi.s kernel should be able to
identify the SCSI drive, mount the root filesystem
and then start BL3.

Cheers,
Steven

You could also use DSL or another live CD to see which scsi controller module got loaded, then compile a kernel with that driver (probably aic7xxx).

If your big kernel does not have a controller driver, why answer Y instead of M to the other scsi driver questions? It makes the kernel much larger and you still cannot use it to boot from scsi drive.





Archive powered by MHonArc 2.6.24.

Top of Page