Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!zaphod.mps.ohio-state.edu!darwin.sura.net!haven.umd.edu!uunet!mcsun!Germany.EU.net!hcshh!hm From: hm@hcshh.hcs.de (Hellmuth Michaelis) Newsgroups: comp.os.386bsd.bugs Subject: Re: Julian's SCSI driver: no bootdrive found on reboot (SOLVED!) Message-ID: <2067@hcshh.hcs.de> Date: 20 Mar 93 15:50:36 GMT References: <2066@hcshh.hcs.de> <CGD.93Mar19220437@eden.CS.Berkeley.EDU> Organization: HCS GmbH, Hamburg, Europe Lines: 54 In <CGD.93Mar19220437@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <2066@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes: >=>I have installed it on a EISA machine with a 1742 and yesterday on a ISA >=>machine using a 1542 and both Machines show the same behaviour: >=>after a reboot, no bootdrive is found by the bios, i have to press reset, >=>after that the scsi drives are identified and all is ok - otherwise >=>the driver performs very well, without any other problems. >i just got a new machine (and EISA, with a 1742) and had the exact >same problem. >one of my network cards was configured wrong, and the driver was >garbaging *something* so that (i guess) the card got into some weird >state on reboot... That was the right hint! I removed the config-entries for the network cards and generated a new kernel on both machines - success, no reboot problems anymore on both. Then i put them in on both machines again, made new kernels, same problems again on both machines. On both machines, i am using SMC Elite16 8013 EPC (Cheapernet/ThinEthernet) network cards HARD configured to use ioaddr 0x300, irq 10 and memaddr 0xcc000 (because they are not recognized on a reboot if soft-configured ....) and (and that was it!!!) i'm using the "option WD8013" in both config files. On the EISA machine a 1742 is used and on the ISA machine a 1542B is used, both in the recommended default configurations. After removing the "option WD8013" from the config files, executing "make clean", "make depend" and "make" the problem was solved! I returned to the original /sys/i386/i386/vm_machdep.c with the original cpu_reset() code for the EISA machine, NO problems anymore rebooting both machines! The BIOS on both machines now found the boot drives - everything ok now! Conclusion for me: avoid under all circumstances "option WD8013" in the config file!!! I rememberd (and posted that to c.u.b a while ago) that i locked up a machine using an "old" WD 8013 (jumper configurable) board completely (could not boot from an IDE drive anymore !) - because i was using "option WD8013" - i spent a lot time on that. Something MUST be going completely wrong when using that option, i had a look at the National Semiconductor data sheet, but could not find the register which is used to switch to 16 bit xfers - it might be in the SMC/WD docs (which i don't have). hellmuth -- hellmuth michaelis HCS Hanseatischer Computerservice GmbH hamburg, europe hm@hcshh.hcs.de tel: +49/40/55903-170 fax: +49/40/5591486 [ the opinions expressed above are my own and not the opinion of anybody else ]