On Wed, 17 May 1995, Chris Torek wrote:

> >Yeah, I seem to recall seeing a CRAZYMAP macro, with comments saying
> >things like "should see how the eeprom is set"....
> 
> Unless you have altered `sd-targets' or whatever it is, this is not
> the problem... in fact, this code worked fine in the 4.4-lite
> distribution, and still does in my system :-)
> 
> You need to match the boot path info against target and lun numbers,
> not against unix-level unit numbers.

Well, I've set sd-targets (or whatever) in the eeprom to a liner mapping, 
which worked great with my earlier kernel (from january I believe). I'm 
using a standard scsi-disk set to scsi id 0, and have tried both to 
configure the kernel to boot "generic", "sd0" and "sd0a". The 
"sd0a"-setting worked on the erlier kernel.

Would a mismatched boot path prevent L1-A from working?

Peter