Christoph Wasshuber (wasshub@spdc.ti.com)
Mon, 30 Nov 1998 07:38:06 -0600
Thanx for the tips concerning backup software. Before
I can think of possibly looking into implementing mtops
I would like get my tape drive working. Here are the
problems I encountered.
I upgraded to 2.0.36 kernel and built paride, pt, and epat
drivers into the kernel. With dmesg I get:
lp1 at 0x0378 (polling)
paride: epat registered as protocol 0
pt: pt version 1.04s, major 96
pt0: Autoprobe failed
pt: No ATAPI tape drive detected
First question: is the lp1 the reason why Autoprobe failed?
Then I recompiled the kernel and built paride,pt,epat as modules
and also made parallel printer support as module.
After loading everything with insmod paride, insmod epat and,
insmode pt I get with dmesg:
paride: version 1.02 installed
paride: epat registered as protocol 0
pt: pt version 1.04s, major 96
...
pt0: epat 1.01, Shuttle EPAT chip C6 at 0x378, mode 0 (4 bit), delay 1
pt0: Reset (7) signature = 1 1 1 14 eb
pt0: HP Colorado 5 GBe, master, blocksize 512, 2458MB
So far it seems good. Then I created the devices using the script on
the PARIDE webpage. But how can I now access the tape? I tried:
fdisk /dev/pt0
I get the error "unable to read /dev/pt0".
I tried:
mount /dev/pt0 /mnt/tape
I get the error "mount: /dev/pt0 is not a block device"
In the case of the fdisk command I hear the tape spinning for
a while. So it seems to do something. What could be the problem?
How can I proceed?
regards
Chris....
-- 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:48 EST