Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!bcm.tmc.edu!cs.utexas.edu!howland.erols.net!newsfeed.internetmci.com!news.kei.com!news.thenet.net!frankensun.altair.com!wlbr!news.cerf.net!newsserver.sdsc.edu!usenet From: kurtm@sdsc.edu Newsgroups: comp.unix.bsd.netbsd.misc Subject: problems with AMI motherboard Date: Mon, 09 Sep 1996 17:39:07 -0700 Organization: San Diego SuperComputer Center at UCSD Lines: 33 Message-ID: <3234B8AA.4C35@sdsc.edu> Reply-To: kurtm@sdsc.edu NNTP-Posting-Host: krakatoa.sdsc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0b6 (WinNT; I) Hello, I'm hoping someone can shed light on a problem I'm having with a new machine. I've purchased an AMI Titan II dual pentium motherboard and moved my Adaptec 2940 and SCSI drive into it from my old machine. The old kernel refuses to boot properly. It seems to have problems when it tries to identify the devices on the PCI bus. On the old machine it would report "Adaptec 294x SCSI", "S3 video", etc. Now it reports: pci0 (root): configuration mode 1 pci0 bus 0 device 0: unknown vendor/product: 0x8086/0x04a3 (class: bridge, subclass: host, revision: 0x11) not configured pci0 bus 0 device 2: unknown vendor/product: 0x8086/0x0482 (class: prehistoric, subclass: miscellaneous, revision: 0x04) not configured pci0 bus 0 device 3: unknown vendor/product: 0x1095/0x0640 (class: mass storage, subclass: IDE, revision: 0x02) not configured pci0 bus 0 device 8: unknown vendor/product: 0x9004/0x8178 (class: mass storage, subclass: SCSI, revision: 0x0) not configured pci0 bus 0 device 9: unknown vendor/product: 0x5333/0x8811 (class: display, subclass: VGA, revision: 0x00) not configured Then when it tries to change the root device to sd0a, it cannot and goes into the debugger. I read in a previous message that some motherboards may have PCI bridge chips that are incompatible with NetBSD. Could this be the problem? The only other thing I could think of is that my BIOS is assigning a different IRQ to the SCSI card than my old machine did, so the kernel is looking for the root device and can't find it. I put the controller and disk in another AMI motherboard (Apollo) and had the same result -- unable to mount the root device and the same messages about unknown vendor/product at boot time for all PCI devices. Thanks for any ideas.