Andreas Rohrbacher (arohrbacher@metrolaserinc.com)
Fri, 31 Jul 1998 07:38:22 -0700
Hello Grant,
thanks for the quick reply. Here is the information you
requested to track down my problem. Please note that I am running
the most recent version of paride (I downloaded the patch against 2.0.34
from the linux-parport web site and compiled the sources as loadable
modules. That's also what I did when I used paride v. 0.94 which gave
identical results).
I am running linux 2.0.30 on an Intel 486DX2 66MHz laptop with a
bidirectional printer port (a DOS utility once described it as a PS/2
compatible port).
Here is what I do:
# rmmod lp
# insmod paride
paride: version 1.02 installed
# insmod epat
paride: epat registered as protocol 0
# insmod pcd verbose=1
pcd: pcd version 1.03s, major 46, nice 0
pcd0: epat: port 0x3bc, mode 0, ccr 77, test=(255,255,510)
pcd0: epat: port 0x3bc, mode 1, ccr ef, test=(255,255,510)
pcd0: epat: port 0x3bc, mode 2, ccr 7f, test=(255,255,510)
pcd0: epat: port 0x378, mode 0, ccr 80, test=(0,256,0)
pcd0: epat: port 0x378, mode 1, ccr 40, test=(224,256,448)
pcd0: epat: port 0x378, mode 2, ccr 80, test=(0,256,0)
pcd0: epat: port 0x378, mode 3, ccr ff, test=(255,255,510)
pcd0: epat: port 0x378, mode 4, ccr ff, test=(255,255,510)
pcd0: epat: port 0x378, mode 5, ccr ff, test=(255,255,510)
pcd0: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 2 (8-bit), delay 1
pcd0: Reset (1) signature = 1 1 1 14 eb
pcd0: Master: CD-ROM !B
# mount /dev/pcd0 /cdrom
mount: block device /dev/pcd0 is write-protected, mounting read-only
# cp /cdrom/acroread.tar.gz ~
pcd0: read block before command: alt=0x58 stat=0x58 err=0x100 loop=160001
phase=2
end_request: I/O error, dev 2e:00, sector 304144
pcd0: read block before command: alt=0x58 stat=0x58 err=0x100 loop=160001
phase=2
end_request: I/O error, dev 2e:00, sector 304146
pcd0: read block: command phase error
end_request: I/O error, dev 2e:00, sector 304148
...... (a lot more of these same error messages, but with different sector
numbers)
pcd0: read block: command phase error
end_request: I/O error, dev 2e:00, sector 304150
cp: acroread.tar.gz: I/O error
I had to switch the cdrom drive off to get access to the console again.
The end result: only part of the file acroread.tar.gz was copied.
Then I did:
# umount /cdrom/
pcd0: unlock door completion: alt=0x51 stat=0x51 err=0x60 loop=0 phase=3
pcd0: unlock door data done: alt=0x51 stat=0x51 err=0x60 loop=0 phase=3
pcd0: Sense key: 6, ASC: 29, ASQ: 0
I also tried to use other modes and delays, but that didn't help at all.
Andreas
----------
> From: grant@torque.net
> To: Andreas Rohrbacher <arohrbacher@metrolaserinc.com>
> Cc: linux-parport@torque.net
> Subject: Re: [PARPORT] problems w/ paride driver for Shuttle EPAT adapter
> Date: Thursday, July 30, 1998 4:57 PM
>
> > I have some problems with the paride device driver for linux. I want to
> > access a
> > CDROM drive (IBM, model-no. CRMC-FX001DE) connected via the Shuttle
EPAT
> > adapter to my bidirectional printer port on my laptop. I used insmod
> > [module] to load paride.o, epat.o and pcd.o
> > Everything works fine, also mounting a cdrom (after creating the
> > appropriate device files in /dev/). I can even copy or read smaller
files,
> > but when I try to copy a larger file of many smaller files the system
> > hangs: sometimes the only remedy is to switch my linux-box off (!),
because
> > the console is locked up. I am running Slackware 3.5, kernel 2.0.30,
the
> > version of paride I am using is 0.94.
>
> The latest version of PARIDE can be found in 2.0.35, but I don't think
this
> is something that upgrading is likely to address.
>
> I suspect that you are getting I/O errors for one reason or another.
Usually,
> these errors cause a message to be displayed to your console, however, if
> you are running X you won't see then.
>
> Also, I'd like to know what mode the epat driver is using for your port.
> It is possible, especially with some older unidirectional ports that you
> need to increase the port delay setting.
>
> So, please let me know what sort of computer it is (processor & speed),
> whether you can set the parallel port mode, what mode it is in, and the
> kernel log messages when you load the pcd driver. You can retrieve those
> messages using the dmesg command, or possibly from your system's kernel
> log file.
>
> Then, please reproduce the problem you are having, and send me the first
> two or three messages that appear on your console, once the problem sets
> in.
>
> If it is not too much work, doing all this with the current version of
> PARIDE would be appreciated.
>
>
--------------------------------------------------------------------------
> Grant R. Guenther
grant@torque.net
>
--------------------------------------------------------------------------
-- 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 2.0b3 on Wed 30 Dec 1998 - 10:18:05 EST