Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:8198 comp.os.386bsd.bugs:2037 Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!howland.reston.ans.net!agate!darkstar.UCSC.EDU!cats.ucsc.edu!buhrow From: buhrow@cats.ucsc.edu (Brian Buhrow) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Subject: HAVING TROUBLE WITH REBOOT ON NETBSD 0.9 AND SCSI Date: 23 Jan 1994 19:54:23 GMT Organization: University of California, Santa Cruz Lines: 58 Message-ID: <2huklf$o76@darkstar.UCSC.EDU> NNTP-Posting-Host: cobweb.ucsc.edu Summary: Boots on cold reset, but not on warm reset. Hello net world. I'm having trouble figuring out the exact solution to my problem. My problem is that I have NetBSD 0.9 on a 486dx2 with a Bustek 445S VESA SCSI board and a Western digital 80023e (or something like that) network board. If I turn the power on and bootnetbsd, it works wonderfully. However, if it reboots without resetting the cpu to its power-on state, it forgets that it has a hard drive at all. If it can't boot the floppy, it just waits for user intervention. I believe it has something to do with the initialization of the network board since it didn't display these symptoms before installing that board. So, my question is: What exactly is causing the computer to not execute the VESA SCSI bios boot code upon warm boots as opposed to working fine on cold ones? I know I have seen similar things in these groups before, but don't remember what the troubles were. Also, what should I try to isolate the problem in addition to pulling the network board? If I find it is the network board getting initialized to 16-bit operation, how can I force reset with warm boot e.g. the reboot command from the root prompt? Thank you in advance for any help you can provide. Please send mail to: buhrow@cats.ucsc.edu as I don't have time to read every message in these groups. In an effort to provide as much information as possible to help isolate the trouble, I have enclosed part of the syslog upon the boot process. It identifies the machine type, memory available, and the devices attached at the time of the trouble. -thanks Jan 22 14:29:10 freak /netbsd: NetBSD 0.9a (GENERICAHBLT) #7: Sat Jan 22 10:41:52 PST 1994 Jan 22 14:29:10 freak /netbsd: CPU: i486DX (486-class CPU) Jan 22 14:29:10 freak /netbsd: real mem = 16773120 Jan 22 14:29:10 freak /netbsd: avail mem = 14401536 Jan 22 14:29:10 freak /netbsd: using 115 buffers containing 942080 bytes of memory Jan 22 14:29:10 freak /netbsd: pc0 at 0x60-0x6f irq 1 on isa Jan 22 14:29:10 freak /netbsd: pc0: color Jan 22 14:29:10 freak /netbsd: com0 at 0x3f8-0x3ff irq 4 on isa Jan 22 14:29:10 freak /netbsd: com0: fifo Jan 22 14:29:10 freak /netbsd: com1 at 0x2f8-0x2ff irq 3 on isa Jan 22 14:29:10 freak /netbsd: com1: fifo Jan 22 14:29:10 freak /netbsd: lpa0 at 0x378-0x37f on isa Jan 22 14:29:10 freak /netbsd: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jan 22 14:29:10 freak /netbsd: fd0 at fdc0 targ 0: 1.2MB 80 cyl, 2 head, 15 sec Jan 22 14:29:10 freak /netbsd: fd1 at fdc0 targ 1: 1.44MB 80 cyl, 2 head, 18 sec Jan 22 14:29:11 freak /netbsd: bt0 at 0x330-0x337 irq 11 on isa Jan 22 14:29:11 freak /netbsd: bt0 targ 0 lun 0: type 0(direct) fixed <CONNER CP30540 545MB3.5B0BD> SCSI2 Jan 22 14:29:11 freak /netbsd: sd0 at bt0 targ 0 lun 0: 518MB 2242 cyl, 6 head, 79 sec, 512 byte/sec Jan 22 14:29:11 freak /netbsd: bt0 targ 4 lun 0: type 1(seq) removable <> SCSI1 Jan 22 14:29:11 freak /netbsd: st0 at bt0 targ 4 lun 0: 91000 blocks of 512 bytes Jan 22 14:29:11 freak /netbsd: ed0 at 0x280-0x29f irq 10 maddr 0xd0000-0xd3fff on isa Jan 22 14:29:11 freak /netbsd: ed0: address 00:00:c0:90:fb:24, type WD8013EP (16 bit) Jan 22 14:29:11 freak /netbsd: npx0 at 0xf0-0xff on isa Jan 22 14:29:11 freak /netbsd: npx0: using exception 16 Jan 22 14:29:11 freak /netbsd: biomask 840 ttymask 1a netmask 400 impmask 41a Jan 22 14:29:11 freak /netbsd: changing root device to sd0a