Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!fu-berlin.de!news.belwue.de!News.Uni-Marburg.DE!news.th-darmstadt.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail From: j@bonnie.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Not supported message - Please interpret! Date: 24 Jul 1995 11:35:10 +0200 Organization: Private U**x site, Dresden. Lines: 28 Message-ID: <3uvpge$a7s@bonnie.tcd-dresden.de> References: <9507211537252076@rio.muc.de> Reply-To: joerg_wunsch@uriah.heep.sax.de NNTP-Posting-Host: 192.109.108.139 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Thomas Schreiber <ts@rio.muc.de> wrote: > >When starting INSTALL.BAT I get the following message: > > Probing for devices on the pci0 bus: > configuration mode 1 allows 32 devices > pci0:1: vendor=0x1083, device=0x613, class=bridge [not supported] > ^^^^^^^^^^^^^^ > >What device is this? A PCI-PCI bridge. The message has been changed recently, since the ``not supported'' can be misinterpreted as ``not functional''. Actually, it will be functional since it's been initialized by the BIOS and FreeBSD has no need to handle it specially. >Is it possible, that this is the reason for >the massive problems I have with installing FreeBSD 2.0.5? >(I get a lot of header checksum errors (cpio) and invalid format >errors (gunzip) - Have tried different things to get rid of that but >without success) This smells like memory timing and/or cache coherency problems. -- cheers, J"org private: joerg_wunsch@uriah.heep.sax.de http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)