Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Apr 1995 00:57:53 -0700 (PDT)
From:      Dave Haas <daveh@eskimo.com>
To:        bugs@FreeBSD.org
Subject:   matcd0: error during 2.0-950322-SNAP installation
Message-ID:  <Pine.SUN.3.91.950411001509.602A-100000@eskimo.com>

next in thread | raw e-mail | index | archive | help
Hi there. I'm Dave Haas of Bainbridge Island, Washington. I've been using
the 2/10 snapshot release of FreeBSD since around March 5th on another
system and love it! When I wanted to install FreeBSD onto another system,
I decided to try the 3/22 snapshot as it was said to include support for
Intel EtherExpress 16 cards and improved sound card functionality. 

I ftp'd everything except src from
ftp.cdrom.com:pub/FreeBSD/2.0-950322-SNAP, rawrote boot.flp and cpio.flp
onto freshly formatted floppies, ran through the fdisk and disklabel
procedures, and successfully proceeded until the initial boot from the
hard disk. 

Then, when wd(0,a)/kernel went probing devices, the device matcd0: would
eventually come up for probing and/or attachment, and the kernel would
declare emphatically: 

	matcd0: get_stat: after reading status byte, buss didn't go idle

This would go on forever and head off into infinity until a hard reset was
issued.  So, after resetting the computer and doing a wd(0,a)/kernel -c to
check out this problematic device. config> ls reveals: 

	matcd int0xffffffff -1   -1   0x0   0     0      0x0         yes

I tried to disable the device in the following ways: 

	config> disable matcd
	config> di matcd
	config> disable matcd0
	config> di matcd0

and was always told...

	No such device: matcd0
	Invalid command or syntax.

I also tried disabling, probing and attaching matcd0: with various
creative and unusual spellings, thinking the device might have some weird
tweak to its spelling. But always the device didn't exist. This would
explain a great deal about why the kernel falls into an infinite loop when
it tries to probe/attach to matcd0:

After the disabling fiasco, I took the SoundBlaster 16 out of this
machine, thinking that matcd0: was meant to represent the Matsushita
cd-rom which attaches to these sound cards. I went through the entire
procedure described above, and once again the same problem appeared. 

I am confused and prepared to start eating eggplant if that's what it 
takes to figure this out.

So, the system I'm working with here is an i486DX2 66Mhz system with 16mb
RAM, a 540mb Western Digital HD, a 540mb Quantum SCSI HD and a Toshiba
XM3501B cd-rom (so far unrecognizable to FreeBSD because it's on a QLogic
VLB SCSI controller card), a SoundBlaster 16 (presumably this is what's
supposed to be attached to matcd0: ???), a Diamond SpeedStar Pro w 1mb
RAM, and an Intel EtherExpress 16,

Please give me guidance here so I can avoid the unpleasantries of 
eggplant. And thanks for putting together such a great un*x system! I 
recommend it to everyone.

Dave Haas
daveh@eskimo,com
(206) 842-0679



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950411001509.602A-100000>