Wangster (wangster@sprint.ca)
Thu, 2 Sep 1999 20:40:57 -0500
Ok, power cycled the whole system. Checked the EPP setting in BIOS.
It's set to EPP1.9 (the other choice for EPP is EPP1.7).
Loaded the modules and used the verbose option on the pt module. Here is the
dmesg output:
--- start ---
paride: version 1.04 installed
paride: epat registered as protocol 0
pt: pt version 1.04, major 96
pt0: epat: port 0x3bc, mode 0, ccr ff, test=(255,255,510)
pt0: epat: port 0x3bc, mode 1, ccr ff, test=(255,255,510)
pt0: epat: port 0x3bc, mode 2, ccr ff, test=(255,255,510)
pt0: 0x378 is parport0
pt0: epat: port 0x378, mode 0, ccr 0, test=(192,192,384)
pt0: epat: port 0x378, mode 1, ccr 40, test=(240,240,480)
pt0: epat: port 0x378, mode 2, ccr 0, test=(0,0,0)
pt0: epat: port 0x378, mode 3, ccr 0, test=(0,0,0)
pt0: epat: port 0x378, mode 4, ccr 0, test=(0,0,0)
pt0: epat: port 0x378, mode 5, ccr 0, test=(0,0,0)
pt0: Sharing parport0 at 0x378
pt0: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 5 (EPP-32), delay 1
pt0: Reset (7) signature = 1 1 1 14 eb
pt0: HP COLORADO 5GBe, master, blocksize 512, 2458 MB
------- end -----
I tared some files to the drive and then read the list of files back in. I
started small and worked my way up to backing up my entire system. It all
worked flawlessly until I tried the entire system. I could hear the drive
working for a very long time and I thought it was going to work, but then it
died saying this:
----- start ---
tar -cf /dev/pt0 /
tar: Removing leading `/' from absolute path names in the archive
tar: Cannot write to /dev/pt0: I/O error
tar: Error is not recoverable: exiting now
---- end ---
And in dmesg for the same command:
--- start ---
pt0: write DSC timeout
pt0: Sense key: 0, ASC: 0, ASQ: 0
pt0: write filemark DSC timeout
pt0: Request sense before command: alt=0xc0 stat=0xc0 err=0x1c0 loop=600001
phase=192
pt0: rewind before command: alt=0xc0 stat=0xc0 err=0x1c0 loop=600001
phase=192
pt0: Request sense before command: alt=0xc0 stat=0xc0 err=0x1c0 loop=600001
phase=192
--- end ---
Unless this is being caused by my lame-o mother board and its EPC1.9 mode, I
think the modules might be buggy. The only other thing that I'm concerned
about is that message about sharing the parport.. Shared with what? I have
nothing else on the port or using it. Did I maybe compile something into the
kernel that I shouldn't have? I included things that referred to the
parallel port because I assumed I needed at least some basic port functions
to get started. Was I wrong?
John Lange
-- 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 Thu 02 Sep 1999 - 21:45:24 EDT