Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!purdue!mozo.cc.purdue.edu!staff.cc.purdue.edu!bj From: bj@staff.cc.purdue.edu (Ben Jackson) Newsgroups: comp.os.386bsd.development Subject: FreeBSD 1.1.5 on PCI (was: NetBSD-1.0 - WHEN?) Date: 22 Sep 1994 01:23:11 GMT Organization: Purdue University Lines: 25 Message-ID: <35qm9v$gkq@mozo.cc.purdue.edu> References: <199408172054.PAA07862@MindBender.HeadCandy.com> <1994Sep20.134745.15198@ccc.amdahl.com> <35ncc9$34dv@yuma.acns.colostate.edu> <35p0vb$7tp@agate.berkeley.edu> NNTP-Posting-Host: staff.cc.purdue.edu In article <35p0vb$7tp@agate.berkeley.edu>, Jordan K. Hubbard <jkh@violet.berkeley.edu> wrote: >In article <35ncc9$34dv@yuma.acns.colostate.edu>, >Sandy Lam <sandylam@lamar.ColoState.EDU> wrote: >> this would be a lot cooler if the BINARIES of the install were available >> somehwere. I can't install FreeBSD on my disk because most of my >> machines are PCI, which won't work on FreebSD (i've tried). > >Not to start any flame wars, but this is strange. I have 6 PCI machines >here and all of them run FreeBSD. wcarchive.cdrom.com is a PCI machine >running 1.1.5.1 - it works fine! You must have a very odd PCI machine, >I guess! :-) Not that odd... FreeBSD 1.1.5 doesn't run on my PCI box either. I can run 1.1 for weeks on end with no troubles, but 1.1.5 panics as soon as I start swapping/paging. At the moment I'm running a kernel with some of the 1.1.5 features I needed hacked into 1.1. I'm hoping the VM problem is cured in 2.0, but the last -current I got didn't compile. John Dyson offered to come by and see this in person, but unfortunately it was during the week I was moving from one appartment to another. Oh, in case you want to rate oddity: Zeos 486DX2/66 PCI w/16M. -- Ben Jackson