linux 2.0.0 and sony cdu31a/cdu33a problems

linux 2.0.0 and sony cdu31a/cdu33a problems

Post by Sheila Che » Wed, 23 Oct 1996 04:00:00



I apologize if this is a question that has already been asked.

I haven't been keeping up with linux at all for a while now and I've
been running 1.1.53 for over a year. Then suddenly I decided to
upgrade to 2.0. So I bought a slakware cd this weekend and upgraded.
(Off a bookstore shelf, I couldn't get anything newer.)

I haven't been able to get my cdrom (Sony cdu31a/33a) to work. I read
the howtos and stuff. I did 2 things. I built a kernel with the right
driver and iso9660 support (I'm pretty sure that's right) and I added
the line

        append="cdu31a=0x1f88,0,PAS"

to my /etc/lilo.conf and ran /sbin/lilo. The docs say that as of
1.1.60 or so, they stop auto-probing the cdu31a/33a. That is why
the append line is needed in lilo.

When I first booted up with this kernel, I get

        Unable to Identify CD ROM format

and if I try to mount -t iso9660, I get /dev/cdrom is not a device
file or some such message.

I am a little worried that this is a 2.0.0 kernel as all dot 0 things
are probably not that good yet.

Should the /dev/cdrom point to /dev/sonycd or /dev/cdu31a ? I don't
think that is my problem anyway since I tried it both ways.

The weird thing is, the boot disk that came with the cd works for me.
But I needed a new kernel for my ethernet card.  

I would aprreciate any help. Thanks.

--------------------------------------------------------------

Data Management Group   Hewlett-Packard Convex Division
"The will to win means nothing without the will to prepare."
        --Juma Ikangaa, winner NYC Marathon (1990?, 1991?)

 
 
 

linux 2.0.0 and sony cdu31a/cdu33a problems

Post by Larry Min » Fri, 25 Oct 1996 04:00:00


: I apologize if this is a question that has already been asked.

: I haven't been keeping up with linux at all for a while now and I've
: been running 1.1.53 for over a year. Then suddenly I decided to
: upgrade to 2.0. So I bought a slakware cd this weekend and upgraded.
: (Off a bookstore shelf, I couldn't get anything newer.)

: I haven't been able to get my cdrom (Sony cdu31a/33a) to work. I read
: the howtos and stuff. I did 2 things. I built a kernel with the right
: driver and iso9660 support (I'm pretty sure that's right) and I added
: the line

:       append="cdu31a=0x1f88,0,PAS"

: to my /etc/lilo.conf and ran /sbin/lilo. The docs say that as of
: 1.1.60 or so, they stop auto-probing the cdu31a/33a. That is why
: the append line is needed in lilo.

: When I first booted up with this kernel, I get

:       Unable to Identify CD ROM format

: and if I try to mount -t iso9660, I get /dev/cdrom is not a device
: file or some such message.

: I am a little worried that this is a 2.0.0 kernel as all dot 0 things
: are probably not that good yet.

: Should the /dev/cdrom point to /dev/sonycd or /dev/cdu31a ? I don't
: think that is my problem anyway since I tried it both ways.

: The weird thing is, the boot disk that came with the cd works for me.
: But I needed a new kernel for my ethernet card.  

: I would aprreciate any help. Thanks.

If you compiled the driver as a loadable module rather than in the kernel,
you need to pass the information to the driver in a different way.  You
need to create a file in /etc named conf.modules.  It should contain one
line, as follows:
options cdu31a cdu31a_port=0x340  

Change as necessary for your port address.

Larry

 
 
 

1. Problem with Sony cdu31a/cdu33a

I am having some strange problems with Linux and my cdu31a.  I am very
new to Linux, so I'm probably missing something very simple.

I am using the Trans-Ameritech April 1995 Slackware 2.2.0 (kernel
1.2.1).  At the 'boot:' prompt that the boot disk (cdu31a) gives me, I
enter 'ramdisk cdu31a=0x230,0' because my cdrom is hooked up to my
Sound Blaster 16 ASP MCD.  The cdrom mounts and unmounts fine, but
when it tries to access certain files (for installation or for even
simple directory listings) the cdrom gets stuck like a scratched
record.  All it does is flash the busy light quickly, often, and in a
regular pattern.  Linux gives me a 'CDU31A:  Read error:  0x01' error
message every few seconds.  The only way I have figured out how to fix
it is by ejecting the cd and putting it back in again.  Everything
works fine in DOS.

One thing that might have something to do with it is there is no
/dev/cdu31a.  How I had to mount my cdrom is by making a symbolic link
from /dev/sonycd to /dev/cdu31a.  When I try to mount /dev/sonycd, it
seems to work fine, but shouldn't there be a /dev/cdu31a?  I thought
that /dev/sonycd was for a different model...

At first, I thought that the cd could be scratched, but it doesn't
look like it, and the cd reads fine in DOS.

Any help would be greatly appreciated...

2. "RPM's harmful to Linux" harmful to Linux

3. sony cdu33a/cdu31a IRQ+DMA linux-1.1.28 broken

4. printing probs on Kernel2.2

5. RED HAT 5.0 CDROM MOUNT PROBELMS WITH SONY CDU31A / CDU33A

6. 4.2.1 and ppp win95 client

7. New Sony CDU31A/CDU33A driver

8. Linux on Microchannel: Please help!

9. RED HAT 5.0 CDROM MOUNT PROBELMS WITH SONY CDU31A / CDU33A DRIVE

10. RedHat Linux instalation cdu31a (cdu33a) CD-ROM Problem

11. cdu31a-cdu31a-cdu31a-cdu31a-cdu31a HELP HELP HELP please :-)

12. CDU31a/CDU33a problems

13. Linux and 386sx 4MB ram, sony cdu33a install problems.