Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 01 Jan 1998 22:56:41 -0500
From:      James Higgins <jamesh@bnoc.net>
To:        Doug White <dwhite@resnet.uoregon.edu>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Panasonic CR-563 CD-ROM Drives.
Message-ID:  <34AC6579.2DF5C14@bnoc.net>
References:  <Pine.BSF.3.96.980101142340.22261M-100000@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote:
> 
> On Thu, 1 Jan 1998, James Higgins wrote:
> 
> > Ok,
> >
> > I change the I/O address to 0x630. Windows 95 shows the device at 0x630
> > and linux also detects the drive at 0x630.  Kernel parameter in linux is
> > "sbpcd=0x630,LaserMate" if that means anything to anyone.  Then I save
> > the userconfig parameters and continue booting.
> 
> Did you set the interrupt?
> 

There is no way to specify an interrupt as far as I can tell.

> > The drive light flashes like the drive is read, but when I select it as
> > my installation media I get the now infamous "No CDROM devices found....
> > blah blah blah" error.  I can switch to virtual console 2 and see the
> > line: "DEBUG:  Try at matcdc0 retruns errno 2".
> 
> Hit scroll lock at the main install menu, then use the arrow keys to
> scroll back and see the boot prompt.  See if matcd0 found anything.


I went ahead and installed off an MSDOS partition since I had he space
and I thought maybe I could make some sense out of it if I saw the
kernel configuration.

It does not detect a drive while installing or if I compile a kernel
with the following line in the configuration.

controller matcd0 at isa ? port 0x630 bio

I also read in the mailing list archive that someone else had a problem
if the ID jumper on the drive was not one.  I also changed that from 3
to one.  The drive still works in DOS/Windows and nothing in FreeBSD.

I also tried setting the port to -1 and having the driver probe.  No
luck.  In the file /usr/src/sys/i386/isa/matcd/options.h it is stated
that you there are additional I/O ports that can be autoprobed but are
not by default since the are usually the addresses of network or SCSI
cards.  Considering I have netither I enabled the additional I/O ports,
recompiled and still no drive detected.  

The strangest part off all this mess is that the drive activity light
comes on like it is being read during the boot sequence.

Hmmmmm ponderous.

Any further suggestions?

James Higgins




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34AC6579.2DF5C14>