Date: Fri, 14 May 1999 23:03:07 +0100 From: Paul Civati <paul@xciv.org> To: freebsd-hardware@freebsd.org Subject: Need help diagnosing hardware problem Message-ID: <E10iQ2u-00078m-00@mailhost.xciv.org>
next in thread | raw e-mail | index | archive | help
I have a 486DX4-100, which ran FreeBSD 2.1.0-R fine for about a year, it was then left unused for a while when I upgraded to a new machine. I've now replaced the IDE disk with a (brand new) <Adaptec 2940A Ultra SCSI host adapter> and IBM DDRS-34560 disk. The machine has installed 2.2.8-R fine, and built a new kernel, but I have problems doing things like (with large files): # gzip -dc linux-2.0.36.tar.gz > test gzip: linux-2.0.36.tar.gz: invalid compressed data--crc error # ls -l test -rw-r--r-- 1 root wheel 30228603 May 14 22:24 test # gzip -l linux-2.0.36.tar.gz compressed uncompr. ratio uncompressed_name 7269221 30228480 75.9% linux-2.0.36.tar # gzip -dc fbsd227-srcsys.tar.gz > test gzip: fbsd227-srcsys.tar.gz: invalid compressed data--crc error # ls -l test -rw-r--r-- 1 root wheel 51681603 May 14 22:50 test # gzip -l fbsd227-srcsys.tar.gz compressed uncompr. ratio uncompressed_name 11012524 51681280 78.6% fbsd227-srcsys.tar (I have used md5 to verify the tar files havn't been corrupted, they extract fine on another machine, and there is plenty of free disk space to extract them). I don't *think* it's a memory problem, as I'm not getting any sig11 errors when compiling, and I've tried running with each 16M SIMM separately. (I also don't think it's an o/s problem, a test linux install exhibited the same problem with the above test). Parity is enabled on both controller and disk, and the disk is terminated (it's the only device). There are a few PCI related options in the system BIOS, but the (Gigabyte 486-AM) m/b manual doesn't give any useful info other than 'enable to enable this feature, disable to disable this feature' for a lot of them. :/ I'm thinking it's either a SCSI problem or one of the BIOS options that didn't effect the system when it was IDE based. Anyone have any tips on what the problem might be? -Paul- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E10iQ2u-00078m-00>