Date: Sat, 14 Dec 1996 08:10:37 -0600 From: Raul Zighelboim <mango@staff.communique.net> To: "'lada@ws2301.gud.siemens.co.at'" <lada@ws2301.gud.siemens.co.at>, "'yergeau@gloworm.Stanford.EDU'" <yergeau@gloworm.Stanford.EDU>, "'Bruce Evans'" <bde@zeta.org.au> Cc: "'hackers@freebsd.org'" <hackers@freebsd.org> Subject: RE: 2.1.5-R kernel root on sd0 fails Message-ID: <c=US%a=_%p=Communique._Inc.%l=KAORI-961214141037Z-1371@kaori.communique.net>
next in thread | raw e-mail | index | archive | help
This is what I set on my kernel to able to boot from sd when wd: config kernel root on sd1 controller scbus0 at aic0 device sd1 at scbus0 target 0 unit 0 hope this helps. >---------- >From: Bruce Evans[SMTP:bde@zeta.org.au] >Sent: Friday, December 13, 1996 11:07 PM >To: lada@ws2301.gud.siemens.co.at; yergeau@gloworm.Stanford.EDU >Cc: hackers@freebsd.org >Subject: Re: 2.1.5-R kernel root on sd0 fails > >>>I had a happy installation with one SCSI disk and then had to add >>>a wd0--don't ask why. >>> >>>Subsequently I went to generate a new kernel in order to be able to >>>boot from sd0 without manual keyboard intervention every time. >> >>There doesn't appear to be a way to convince the biosboot to pass >>the "correct" information to the kernel (after all, both are bios >>drives). Just putting "root on sd0" in the kernel config does not >>appear to work (the kernel still tries what it got from biosboot, >>sd1), but the following worked for me. > >Three ways: >1. manual keyboard intervention every time. Type something like > 1:sd(0,a)kernel >2. configure the boot blocks with the BOOT_HD_BIAS option. Something > like CFLAGS += -DBOOT_HD_BIAS=1. >3. configure the boot boot blocks with the NAMEBLOCK option and put > the string in (1) in the nameblock using nextboot(8). I haven't > tried this. > >>Put "root on sd1" and wire the SCSI drive to be sd1 (e.g. "disk sd1 >>at scbus0 target 0"). You may also need to wire scbus0 to a >>particular controller (e.g. "controller scbus0 at ahc0"). See the >>LINT kernel config if you need more information on how to wire disk >>and controller targets. > >This might be necessary if there are more drives and the BIOS drive >order is different than the FreeBSD drive order. > >Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c=US%a=_%p=Communique._Inc.%l=KAORI-961214141037Z-1371>