Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!news-peer.gsl.net!news.gsl.net!news.mathworks.com!news-xfer.netaxs.com!news.structured.net!news.teleport.com!bharbour From: bharbour@teleport.com (Bob Harbour) Newsgroups: comp.unix.bsd.freebsd.misc Subject: PCI IDE adapter problems with v2.15 Date: 3 Jan 1997 04:10:47 GMT Organization: Teleport - Portland's Public Access (503) 220-1016 Lines: 37 Message-ID: <5ai0s7$j4v$1@nadine.teleport.com> References: <01bbec08$3743bbe0$0b01a8c0@fxg.usis.usemb.se> <5a9dti$huj@uriah.heep.sax.de> NNTP-Posting-Host: linda.teleport.com X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33535 J Wunsch (j@uriah.heep.sax.de) wrote: : bharbour@teleport.com (Bob Harbour) wrote: : > Either I missed the : > configuration for it or version 2.15 doesn't like a PCI IDE adapter. : I know of plenty of systems that work on a PCI IDE adapter. So unless : you've got some more datapoints to track, there's probably now chance : to ever find your source of troubles. The system shows the PCI - IDE adapter during the boot up, but doesn't attach a driver. It uses the ISA - IDE driver. The boot listing shows the PCI - IDE interface as an intel 82371 bus master IDE controller, PCI0:7:1 rev 0. I looked through the lint kernel config file and didn't see a provision for a PCI - IDE driver, just the ISA one. The disk drive is a Western Digital 2.2gb. The BIOS has a place to select modes 0-4 or so, and I tried all choices with similar results. There is also a place to select "normal" disk, large disk or LBA disk. I tried all of those as well. When I tried this configuration, the IDE drive was the only fixed disk in the system, so all partitions/slices were on it. The first partition was a 250 mb dos one, followed by a 1.2gb FreeBSD partition, with the remaining space in another dos partition. The problem appeared as kernel panic 12's with messages about returning unused pages, or pages not found and similar things related to the memory manager. It occurred when I was doing things that involved a lot of disk access like installing the OS or updating the locate database. It would usually compile the kernel successfully, but occaisionally it would have problems linking at the end. Since installing the system on a SCSI disk, I have not had any more problems. The system seems to be fine on messydos but I don't have any apps that beat the disk up that hard. It just seems a waste to have that big disk left to dos. Thanks -- Bob Harbour bharbour_AT_teleport_DOT_com