Here's the output for 'mt -f /dev/qft0 status' after recompiling
ftape-io.c/verbosity changes:
stdout:
qic-117 drive type = 0x00047
File number=-1, block number=-1.
mt_resid: 0, mt_erreg: 0x1b1f
mt_dsreg: 0x22d865, mt_gstat: 0x41000000
General status bits on (41000000):
BOT ONLINE
/var/log/messages:
I don't know if it's improper to send attachments but the log output
kind of makes the mail unreadable. I set the MCONFIG trace flag on hi
and left in the conf* options line you gave me but when I searched for
'track' nothing came up.
Incidentally, I've wondered about this before but when I 'make install'
ftape asks if it can overwrite some items in /dev - is it necessary to
allow it to do so? And is there a reason zftape appears as such:
-rwxrwxrwx 1 root 0 May 13 16:55 /dev/zftape
Everything else tape-related in /dev appears to be links or 'c'.
The format output will be along shortly.
Thank you for your time and help.
Mike
Nostradamus foresaw that on Jul 22, Claus-Justus Heine would write:
->Mike Hardy <[EMAIL PROTECTED]> writes:
->
->> ftape: 4.03
->> ftape-tools: 1.08
->> kernel: 2.2.5
->> Pent 200, 80M RAM, Colorado Jumbo 250, FC-20 controller
->>
->> /etc/conf.modules entries:
->>
->> alias char-major-27 zftape
->> options ftape ft_probe_fc10=1
->> options ftape ft_fdc_driver=ftape-internal,none,none,none
->> options ftape-internal ft_fdc_base=0x180 ft_fdc_irq=9 ft_fdc_dma=2
->>
->> Description:
->>
->> Using the newest ftape and ftape-tools (although I've had this error
->> before this newest rev), any time I try to format a 307' QIC-80 tape in
->> a Colorado Jumbo 250 I get right to the very end of formatting (when
->> it's verifying) and it craps out with:
->>
->> ftape-io.c (ftape_seek_head_to_track) - track out of bounds.
->
->Ups. Can you please load the driver with the following option:
->
->options ftape ft_fdc_driver=ftape-internal,none,none,none ft_tracings=4,4,4,4,4
->
->This will increase the verbosity level of the driver. Then try to
->access the tape, e.g. with "mt status". Afterwards there should be line like
->
->ftape-read.c (ftape_decode_header_segment) - (fmt/spt/tpc/fhm/ftm/fsm) = ...
->
->in you syslog. The interesting part is that were I have inserted the
->three dots. Especially the third value (tpc == tracks per cartridge)
->will be interesting.
->
->Regards
->
->Claus
->
->--
-> Claus-Justus Heine
-> [EMAIL PROTECTED]
-> http://www.instmath.rwth-aachen.de/~heine/
->
-> Ftape - the Linux Floppy Tape Project
-> Home Page : http://www.instmath.rwth-aachen.de/~heine/ftape/
-> Mailing-list: [EMAIL PROTECTED]
->
---------------------
Mike Hardy
[EMAIL PROTECTED]
Aunty Em: Hate you, hate Kansas, took the dog - Dorothy
ftape log output
