Subject: Re: kernel news, sorry for the mess.
To: Tim Kelly <hockey@dialectronics.com>
From: Riccardo Mottola <rollei@tiscalinet.it>
List: port-macppc
Date: 12/08/2004 22:16:01
Hey,

> At 9:15 PM +0100 12/8/04, Riccardo Mottola wrote:
> >NetBSD 2.99.11 (RICCARDO) #21: Tue Dec  7 18:06:59 EST 2004
> >        ml@Macallan:/data/src/sys/arch/macppc/compile/RICCARDO
> >total memory = 176 MB
> >avail memory = 164 MB
> >
> >autoconf.c bootpath: scsi-int/sd@1/netbsd
> >autoconf.c OF_canon result: /bandit@F2000000/gc@10/mesh@18000/sd@0,0
> >autoconf.c cbootpath: /bandit@F2000000/gc@10/mesh@18000/sd@1
> 
> This stuff is from an upcoming patch of mine. It fixes the problem where
> the root boot device will not be properly identified when it comes from a
> SCSI disk other than SCSI ID 0. It is debug information that shows the
> condition that otherwise would have had this problem - Riccardo is booting
> from a disk at ID 1, but going through OF to canonicalize the path with
> either canon or instance to path drops the node. This patch is taking me a
> bit longer to prepare and in the meantime Brian, Michael and I have
> identified another bug related to ofb so my attention has been elsewhere.
> 
> If you have a SCSI based install and you keep getting boot device:
> <unknown>, please let me know and I'll send you a patch for testing.

the box has two disks
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
probe(mesh0:0:0:0): max sync rate 10.00Mb/s
sd0 at scsibus1 target 0 lun 0: <QUANTUM, FIREBALL SE4.3S, PJ0A> disk
fixed
sd0: 4110 MB, 7637 cyl, 4 head, 275 sec, 512 bytes/sect x 8418816
sectors
probe(mesh0:0:1:0): max sync rate 10.00Mb/s
sd1 at scsibus1 target 1 lun 0: <IBM OEM, DFHSS4F, 4141> disk fixed
(bootpath member) 
sd1: drive offline
probe(mesh0:0:3:0): max sync rate 5.00Mb/s
cd0 at scsibus1 target 3 lun 0: <MATSHITA, CD-ROM CR-8005A, 4.0i> cdrom
removabl
boot device: sd1

the netbsd disk is indeed ID1.

apropos SCSI id's and 'internal' numbers (sd0 etc).. Could the internal
bus have priority? I think if someone has internal disks they should
retain their ID and so always boot correctly.

I noticed this when I tried to test my externalboot disk I tried on the
9600 on the 9500: the boot disk get shifted because of the external
disk. This seems stupid to me. "external is external".

Also I noticed however that on the 9500 the kernel identifies the
external hard disk! on the 9600 not... strange..

-R