Hi, I'm running RedHat 6.0 on an old '486. I've compiled run the 2.2.10 kernel. I've compiled and installed the ftape-4.x-1999_06_02 and ftape-tools-1999_03_17. I install the ftape, zftape, and ftape-internal modules. But my Colorado 250 MB will not work. I put a formatted 307 foot Qic 80 tape in the drive. Here is the /var/log/messages that result from "ftmt -f /dev/qft0 status": Jul 23 21:28:16 apu kernel: [015] 0 ftape-ctl.c (ftape_get_drive_status_R6560845c) - status: new cartridge. Jul 23 21:28:17 apu kernel: [016] 0 ftape-ctl.c (ftape_init_drive) - post QIC-117B drive @ 500 Kbps. Jul 23 21:28:17 apu kernel: [017] 0 ftape-ctl.c (ftape_calibrate_data_rate_R0c794da2) - Highest FDC supported data rate: 500 Kbps. Jul 23 21:28:18 apu kernel: [018] 0 ftape-ctl.c (ftape_init_drive) - 307 ft. QIC-40 tape. Jul 23 21:28:19 apu kernel: [019] 0 ftape-io.c (ftape_seek_head_to_track) - track out of bounds. The command stalls and I have to CTL-C to exit the command. Then more lines show up in the message log: Jul 23 21:29:14 apu kernel: [020] 0 ftape-rw.c (seek_forward) - read_id failed completely. Jul 23 21:29:15 apu kernel: [021] 0 ftape-rw.c (seek_forward) - read_id failed completely. Jul 23 21:29:15 apu kernel: [022] 0 ftape-rw.c (ftape_start_tape) - failed to reposition. Jul 23 21:29:15 apu kernel: [023] 0 ftape-read.c (ftape_read_segment_Rf3a45c52) - Error: segment 0 unreachable. Jul 23 21:29:15 apu kernel: [024] 0 ftape-read.c (ftape_read_header_segment_R87b6964d) - header segment damaged, trying backup. Jul 23 21:29:15 apu kernel: [025] 0 ftape-read.c (ftape_read_segment_Rf3a45c52) - interrupted by non-blockable signal. Jul 23 21:29:15 apu kernel: [026] 0 ftape-read.c (ftape_read_header_segment_R87b6964d) - no readable header segment found. Jul 23 21:29:15 apu kernel: [027] 0 zftape-read.c (zft_read_header_segments) - ftape_read_header_segment_R87b6964d(zftape->ftape, zftape->hseg_buf) failed: -4. Jul 23 21:30:00 apu kernel: [028] 0 ftape-ctl.c (ftape_print_history) - == Non-fatal errors this run: ==. It is all down hill from there. Have any of you seen the same problem? What can I do to get past the failure? -- L A Wilkins [EMAIL PROTECTED]
