Return to BSD News archive
Newsgroups: comp.unix.bsd.netbsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.reston.ans.net!Germany.EU.net!Dortmund.Germany.EU.net!nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!mpifr-bonn.mpg.de!fs1.mpifr-bonn.mpg.de!souva From: souva@aibn58.astro.uni-bonn.de (Ignatios Souvatzis) Subject: Re: Help: NetBSD 1.1 finding NCR 53c810 twice! In-Reply-To: curt@cynic.portal.ca's message of 11 Feb 1996 13:01:28 -0800 Message-ID: <SOUVA.96Feb13192224@aibn58.astro.uni-bonn.de> Sender: news@mpifr-bonn.mpg.de Nntp-Posting-Host: aibn58 Reply-To: isouvatzis@astro.uni-bonn.de Organization: Radioastronomisches Institut der Universitaet Bonn, Bonn, FRG References: <311E147E.1C3C88B5@axp745.gsfc.nasa.gov> <4fllf8$dov@cynic.portal.ca> Date: Tue, 13 Feb 1996 18:22:24 GMT Lines: 50 In article <4fllf8$dov@cynic.portal.ca> curt@cynic.portal.ca (Curt Sampson) writes: In article <311E147E.1C3C88B5@axp745.gsfc.nasa.gov>, Rick Niles <niles@axp745.gsfc.nasa.gov> wrote: >I'm trying to install NetBSD 1.1 on my 486, but it seems >to have problems detecting my NCR 53c810. It finds ncr0 >and my three devices attached and then it finds ncr1 and >the same three devices. This is not a problem with the NCR chip or driver, but with the PCI code. I have the same problem with 1.1 on my PVI-486SP3. (Ironically enough, I switched from FreeBSD to NetBSD because FreeBSD used to have this problem but NetBSD 1.0 didn't.) What seems to be happening is that the driver probes devices 16-31 on the PCI bus and these, on this particular motherboard, are `reflections' of 0-15. Hm. If this is really true, this is a bug in the motherboard, not in the PCI code. ;-) But it rings a bell... while browsing through the PCI code I noticed that the IBM-PC PCI interfaces (and only IBM-PC ones) have two styles generating configuration cycles. In your particular case, the (more generic, more modern one) happens to get recognized falsely, I guess. Please try to define options PCI_CONF_MODE=2 in your kernel configuration file, config YOURKERNELFILE cd ../compile/YOURKERNELFILE rm pci_machdep.o make This will hardwire your kernel to mode 2. (If I am _very_ wrong guessing, you'll have to use options PCI_CONF_MODE=1. :-) I don't know how to fix this. I sent a message to port-i386@netbsd.org a while back about this but got no answer. Any PCI hackers out there care to enlighten me about what's going on? No PCI hacker, just read the source. ;-) Regards, Ignatios -- I think computer viruses should count as life ... I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. --S.Hawking