Primary channel B?

[Reinhold J. Gerharz]

Now wait a minute. It sounds like Eugene Blanchard is referring to the
old problem of Linux scanning and assigning /dev/sdX entries from the
physical "A" bus before the physical "B" bus of the AHA-2742T,
ignoring the EISA setup parameter setting the "B" bus to be treated as
the primary bus. The last I heard about this was that it may be a SCSI
subsystem problem in Linux, rather than the AIC?xxx driver. (A search
of the mailing list archives should provide better information.)

I still have one of these cards, and hope to put it back into service
later this year. I doubt that I will set B = primary, though that is
how I used to use it, which is why I originally subscribed to this list.

At 09:12 07/31/1998 -0000, Mike Bilow wrote:
        ...
>I don't recognize the "N" suffix, but I assume it is the same as "T"
suffix?
>
>Anyway, the problem here is really in Lilo.  Until Linux is booted,
obviously
>Lilo must go through BIOS to get the kernel loaded.  Since most systems
>originally had BIOS support for only two hard drives, apparently this
got
>written into Lilo.  Older Adaptec SCSI controllers, such as the
AHA154x, did
>require that the boot device be ID 0 or 1 for this reason.
>
>If the controller ROM supports booting from an arbitrary SCSI device,
then Lilo
>should just make the necessary calls into BIOS and go with that.
Until you
>posted your message, I didn't even know that such a limitation
existed in Lilo,
>and it should be fixed in Lilo rather than in the SCSI subsystem.
Hard drives
>supported by BIOS are accessed by zero-based device number with the
high-bit
>set (0x80, 0x81, and so on) to distinguish them from floppy drives.
-- 
Reinhold J. Gerharz                        http://www.gerharz.net
PGP     Key     at      http://www.gerharz.net/pgp/public-key.asc
Need reliable, portable energy?    http://www.tst.tracor.com/tbtc
"The only good spammer is a DEAD spammer!"       -      Anonymous


To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message