Dave,
If your Backpack reads CDRW media, then the drive mechanism has been
replaced by someone outside of Micro Solutions. The drive mechanism
originally in there was 4x and multi-read was not implemented until around
24x. I point this out because sometimes when a drive is replaced, they are
not properly jumpered. This can effect the drives response differently from
Windows to DOS to Linux. I would first make sure the drive mechanism is
jumpered as MASTER and not SLAVE or CABLE SELECT.
Also, check what is being reported from the virtual console (ALT-F3 /
ALT-F4) for additional messages.
-AL
At 02:42 PM 12/15/2003, Dr. Dave Williams P.E. wrote:
>Al:
>
>Thanks very much for your assistance.
>
>The drive does read CD-RW discs just fine (including that Debian disc)
>under Windows (95 and 2000) using standard drivers. I was actually
>surprised (and quite pleased) to see that and have never had any
>trouble at all with CD-RW discs under Windows. FIWI, the CMOS
>setting I'm using under Linux is identical to the one I use under Windows.
>
>Is it even necessary to have a disc in the drive when pcd is loaded? I have
>tried both commercial CD-ROM and CD-RW discs with equal results. In
>my quest, I've seen dmesg samples posted which seem to indicate that
>the drive itself responds to pcd with some return data, such as:
>
> > pcd0: Sharing parport0 at 0x378
> > pcd0: BACKPACK Protocol Driver V2.0.2ac
> > pcd0: Copyright 2001 by Micro Solutions, Inc., DeKalb IL.
> > pcd0: BACKPACK 2.0.2ac, Micro Solutions BACKPACK Drive at 0x378
> > pcd0: Unit: 45 Mode:1 (8-bit) Delay 0
> > pcd0: identify completion: alt=0x88 stat=0x88 err=0x188 loop=160001
> > phase=136
> > pcd0: Request sense before command: alt=0x88 stat=0x88 err=0x188
> > loop=160001 phase=136
>
>I don't get any of this. All I get is "adapter not found", "autoprobe
>failed", or
>"no CD-ROM drive found". I get the same results whether the drive is
>connected
>or not, so it seems to me like pcd isn't seeing the drive at all. I never
>get to the
>point where the drive will mount to read the disc, although I have tried.
>
>Since my last post, I got a hold of setid.exe and confirmed that the unit
>ID is
>indeed 33 as it's supposed to be based on the serial number. I was suspicious
>that this might have been changed way back when, but now I know we're using
>the correct value.
>
>Any further suggestions or ideas would be much appreciated. I suppose I
>could live with Windows on this machine, but I'd really rather not have to.
><grin>
>
>Thanks again.
>
>=Dave
>
>
>AL Crowley wrote:
>
>>
>>What type of media do you have in the Backpack? If you downloaded Debian
>>and burnt it to CDRW media, that older drive will not read CDRW's. I
>>would also verify that you can read from that Debian CD in the Backpack
>>under Windows.
>>
>>
>>
>>At 05:34 AM 12/14/2003, you wrote:
>>
>>>Greetings:
>>>
>>>I'm struggling with a particularly obstinate system:
>>>
>>>1) Toshiba T2150 Satellite notebook (port at 0x378 is
>>>running in standard bi-directional mode since the only
>>>other choice is ECP).
>>>
>>>2) Backpack CD-ROM, model 164700 (quad speed), which works
>>>under Windoze 95 (the only other OS that'll run on this
>>>little beast due to CPU and memory - 28 MB - limitations).
>>>
>>>3) Debian 3.0r1, install CD ready to go (if I could read
>>>it) since network is not yet available to the machine.
>>>
>>>Attempting a fresh install from floppies, all goes well
>>>until I try to recognize the CD-ROM drive. I load modules
>>>until I have the following according to lsmod:
>>>
>>>parport
>>>parport_pc
>>>paride
>>>bpck
>>>
>>>and then pcd will not load on matter what I've tried.
>>>I've gone through all of the parameter possibilities I
>>>can think of, centered about the ones that seem most
>>>correct:
>>>
>>> insmod pcd drive0=0x378,0,33
>>>
>>>(33 = last two digits of the drive's serial number)
>>>
>>>Every time, module installation fails and dmesg shows
>>>"adapter not found", "autoprobe failed", or "no CD-ROM
>>>drive found". Everything from no parameters, to specifying
>>>all 6 manually, to different unit numbers, to specifying
>>>no unit number, etc. all lead nowhere.
>>>
>>>Any assistance or suggestions would be gratefully
>>>appreciated. Thanks in advance.
>>>
>>>=Dave
>>>
>>>
>>>
>>>-- To unsubscribe, send mail to: linux-parport-request@torque.net --
>>>-- with the single word "unsubscribe" in the body of the message. --
>>
>>
>>
>>Thank You,
>>
>>Al Crowley, Technical Support Assistant Manager
>>Micro Solutions
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>website: http://www.micro-solutions.com
>>e-mail: alc@micro-solutions.com
>>fax: 815.756.4986
>>tech phone: 815.754.4500 (M-F 8-5 CT)
>
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Mon Dec 15 2003 - 15:59:55 EST