I'd love some help on this, and some of you may be interested as I'm
using the new binary "backpack.o" from the MicroSolutions web site.
I went back to the "2.2.12-20" kernel source distribution from RedHat
and recompiled (just to keep the module happy, I don't know if that
Now if I do the following:
% modprobe backpack
% ln -sf /dev/pcd0 /dev/cdrom
My CDs play like a charm. Here are the messages:
Feb 19 21:57:19 www kernel: paride: version 1.04 installed
Feb 19 21:57:19 www kernel: BACKPACK Protocol Driver V1.0.0
Feb 19 21:57:19 www kernel: Copyright 1999 by Micro Solutions, Inc., DeKalb IL.
Feb 19 21:57:19 www kernel: paride: backpack registered as protocol 0
Feb 19 21:57:43 www kernel: pcd: pcd version 1.07, major 46, nice 0
Feb 19 21:57:43 www kernel: parport0: PC-style at 0x378 [SPP,ECP,ECPEPP,ECPPS2]
Feb 19 21:57:43 www kernel: parport0: detected irq 7; use procfs to enable interrupt-driven operation.
Feb 19 21:57:43 www kernel: backpack: LPT 0378, Mfg WinBond
Feb 19 21:57:43 www kernel: backpack: ID 66, Tx EPP (Dword)
Feb 19 21:57:43 www kernel: pcd0: Sharing parport0 at 0x378
Feb 19 21:57:43 www kernel: pcd0: Master: CR-4804TE
Feb 19 21:57:43 www kernel: Uniform CDROM driver Revision: 2.56
Now the problem is, before I use cdrecord to write anything, I want to
try to use cdparanoia to rip a few tracks (please note that I have
never done any of this before).
So I try:
% cdparanoia -B
and I get:
cdparanoia III release 9.7 (December 13, 1999)
(C) 1999 Monty <email@example.com> and Xiphophorus
Report bugs to firstname.lastname@example.org
/dev/cdrom exists but isn't accessible. By default,
cdparanoia stops searching for an accessible drive here.
Consider using -s to force a more complete autosense
of the machine.
More information about /dev/cdrom:
Checking /dev/cdrom for cdrom...
Testing /dev/cdrom for cooked ioctl() interface
/dev/pcd0 is not a cooked ioctl CDROM.
Testing /dev/cdrom for SCSI interface
/dev/cdrom is not a SCSI device
I've tried "modprobe ide-scsi" and linking /dev/cdrom to all sorts of
combinations of pg0, scd0, sr0, sdc, and so on. I still get
essentially the same message from cdparanoia.
I realise this may be a cdparanoia-specific problem, but does anyone
have an idea what I should be doing? All the info I've found says
cdparanoia is "the" ripper programme, but I'm willing to try
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Mon Feb 21 2000 - 19:23:44 EST