Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!bloom-beacon.mit.edu!crl.dec.com!crl.dec.com!nntpd.lkg.dec.com!lkg.dec.com!thomas From: matt@lkg.dec.com (Matt Thomas) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: de0 fails - Can't fix iomem with UserConfig - Why? Date: 6 Jul 1995 15:53:44 GMT Organization: Digital Equipment Corporation Lines: 19 Sender: thomas@netrix.lkg.dec.com (Matt Thomas) Distribution: world Message-ID: <3th0u8$ttc@nntpd.lkg.dec.com> References: <DB87I5.MKy@ncrcae.ColumbiaSC.ATTGIS.COM> Reply-To: matt@lkg.dec.com NNTP-Posting-Host: netrix.enet.dec.com X-Newsreader: mxrn 6.18-30 cc: Jeff.McElroy@ColumbiaSC.NCR.COM In article <DB87I5.MKy@ncrcae.ColumbiaSC.ATTGIS.COM>, Jeff.McElroy@ColumbiaSC.NCR.COM (Jeff McElroy (x6065)) writes: |>My 2.0.5 Release systems boots fine until de0 fails because of a PCI |>mapping problem between the device address and the bridge address. |>Seems like I should be able to change the iomem parameter if I boot with |>-c (UserConfig) and then simply issue the iomem change. Problem is that |>the "de" device doesn't show up in "ls" under UserConfig. Any attempt to attach, |>probe, or otherwise configure "de0" is not successful. Any ideas? Is the de0 behind a PCI-PCI bridge? What happens when it fails to probe/attach? Just fails? Crashes? Hangs? What motherboard & PCI Chipset? What PCI-PCI bridge? -- Matt Thomas Internet: matt@lkg.dec.com U*X Networking WWW URL: http://ftp.dec.com/%7Ethomas/ Digital Equipment Corporation Disclaimer: This message reflects my Littleton, MA own warped views, etc.