Hi Gehrke,

> whenever I give a command to my ftape-4.02
> I get:
>  ' ftape-ctl.c (ftape_activate_drive) - known wakeup method failed
> Trying all the (four) others ....'
> in /var/log/messages.
> 
> But everything seems to work fine. 
> Whats wrong?

Do you load only ftape-internal or more drivers?
What does /var/log/messages show right after loading the
modules?

> 
> here is /var/log/messages:
> --------------------------------------------------------
> Dec  8 17:35:41 vitzlipu kernel: [021] 0       ftape-io.c (ftape_report_operatio
> n) - No acknowledge after 300 msec. (96 iter).
> Dec  8 17:35:41 vitzlipu kernel: [022] 0       ftape-io.c (ftape_report_operatio
> n) - timeout on Acknowledge.
> Dec  8 17:35:41 vitzlipu kernel: [023] 0       ftape-io.c (ftape_report_operatio
> n) - No acknowledge after 300 msec. (96 iter).
> Dec  8 17:35:41 vitzlipu kernel: [024] 0       ftape-io.c (ftape_report_operatio
> n) - timeout on Acknowledge.
> Dec  8 17:35:42 vitzlipu kernel: [025] 0       ftape-io.c (ftape_report_operatio
> n) - No acknowledge after 300 msec. (96 iter).
> Dec  8 17:35:42 vitzlipu kernel: [026] 0       ftape-io.c (ftape_report_operatio
> n) - timeout on Acknowledge.
> Dec  8 17:35:42 vitzlipu kernel: [027] 0       ftape-io.c (ftape_report_operatio
> n) - No acknowledge after 300 msec. (94 iter).
> Dec  8 17:35:42 vitzlipu kernel: [028] 0       ftape-io.c (ftape_report_operatio
> n) - timeout on Acknowledge.
> Dec  8 17:35:42 vitzlipu kernel: [029] 0      ftape-io.c (ftape_report_raw_drive
> _status) - report_operation failed after 4 trials.
> Dec  8 17:35:42 vitzlipu kernel: [030] 0     ftape-io.c (ftape_wakeup_drive) - f
> tape_report_raw_drive_status(ftape, &status) failed: -5.
> ---------------------------------------------------------
> 
> ...

Martin 


-- 
Martin Jacobs * Windsbach * [EMAIL PROTECTED]

Reply via email to