*BSD News Article 33385


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!spool.mu.edu!torn!nott!cunews!freenet.carleton.ca!FreeNet.Carleton.CA!ab578
From: ab578@FreeNet.Carleton.CA (Bill Cheung)
Subject: FreeBSD Driver Bug? (was Re: UMC chipset works with AHP 1452CF?)
Message-ID: <CtnLFJ.G1o@freenet.carleton.ca>
Sender: news@freenet.carleton.ca (Usenet News Admin)
Reply-To: ab578@FreeNet.Carleton.CA (Bill Cheung)
Organization: The National Capital FreeNet
References: <3135kh$895@pdq.coe.montana.edu> <CtEwH5.HIF@freenet.carleton.ca>
Date: Thu, 28 Jul 1994 13:57:19 GMT
Lines: 72



In a previous article, nate@bsd.coe.montana.edu (Nate Williams) says:

>In article <CtEwH5.HIF@freenet.carleton.ca>,
>Bill Cheung <ab578@FreeNet.Carleton.CA> wrote:
>>Is there anyone who is running FreeBSD on a UMC chipset 486 motherboard? 
>
>I have been running 386BSD and then FreeBSD for years on my UMC Mboard.
>
>>Someone told me UMC chipset motherboards have problem with AHP 1452CF.
>
>I've heard that certain versions of the UMC chipset have problems, but
>not all of them do.  I've got a 1542B and have had ZERO problems due
>to the Mboard.  (A couple real silly problems I caused, but nothing
>due to hardware)
>

Well, I bought the UMC chipset motherboard a couple of days ago.  The
dealer promised me he will give me back my money if I have any problem with
it within two weeks.  I don't have much time left now. 

The problem is my ARCHIVE VIPER QIC 150 is not working, and I'm not sure if
that is a software bug or a hardware problem. 

Here is a example of what I did:

beebie# tar tv
st0(aha0:5:0): no data found, requested size: 20 (decimal)
... no data found, requested size: 20 (decimal)
... no data found, requested size: 20 (decimal)

beebie# tar tv
st0(aha0:5:0): non-media hardware failure {I'm sure the tape is in the drive}
st0: oops not queued
tar: read error on /dev/rst0: Input/Ouput error
..../386bsd : read error on /dev/rst0: Input/Ouput error
..../386bsd : read error on /dev/rst0: Input/Ouput error


I've tried removed the tape and put it back to the drive, and/or rebooting
the system.  97% of the time the drive just goes back and forth a bit and
then gives up.  2% of the time it goes fine up to a certain point and then
keeps on saying something non-stop like (this happened once at the very end
of the last file in on the tape):

(aha0:5:0): blah,....  blah info: 20 ....  
(aha0:5:0): blah,....  blah info: 20 ....  
(aha0:5:0): blah,....  blah info: 20 .... 
(aha0:5:0): blah,....  blah info: 20 ....  
(aha0:5:0): blah,....  blah info: 20 .... 
(aha0:5:0): blah,....  blah info: 20 .... 
(aha0:5:0): blah,....  blah info: 20 .... 
.....
.....

I guest that is something to do with the block size 20x512??

The remaining 1% of the time the tape drive works just fine.

Any idea what is causing the problem, anyone?

I'm running FreeBSD 1.1 on a Intel 486 DX2/66, with an AHA 1452CF, an
Archive Viper QIC 150 and a ST3550N hard-drive. 

Any suggestion will also be appreciated.

I haven't been reading this group regularly for a couple of months, if this
is a known problem, I'm sorry about that (I did check FreeBSD FAQs). 

-Bill