Re: [cbm4linux-users] driver error

[<mik...@dn...>]

Michael Klein wrote:
> On Fri, 19 Mar 2004, Mikko Kein=E4nen wrote:
>=20
>=20
>>Michael Klein wrote:
>>
>>>On Mon, 15 Mar 2004, Mikko Kein=E4nen wrote:
>>>
>>>>Any ideas why I get the following error message in every other time=
 I
>>>>issue a disk command:
>>>>
>>>>bash-2.05b$ d64copy --transfer=3Ds1 -w 8 the_pawn-disk1-sixpackB.d6=
4
>>>>[Fatal] drive 08 (1541): 99, DRIVER ERROR,00,00
>>>>
>>>>And next time it works just fine? Then it fails. After that it's ok=
 and
>>>>so on... ;)
>>>
>>>Odd. Is that the case for *all* disk commands or only d64copy (or ma=
ybe
>>>serial1-specific?). Your drive contains a normal 1541 ROM, I assume?
>>
>>Yes, I think it happens with all the commands ... just tested with
>>cbmctrl -command and it seems now that the error doesn't show up so
>>often, it seems more random:
>=20
>=20
> [occasional errors snipped]
>=20
>=20
>>>Unfortunately I have no running 2.6 kernel right now, and I wasn't a=
ble
>>>to reproduce this behaviour with 2.4.
>>
>>Maybe I should test with 2.4 kernel... I had no problems with 2.4 ker=
nel
>>some time ago when I installed cbm4linux ... the hardware setup shoul=
d
>>be the same in my computer now as it was then.
>=20
>=20
> Just copied a .d64 to and from a 1541-II using -t original with a
> freshly compiled 2.6.4 kernel without problems here (well, except for=
 a
> minor compile-time fix because parport_enumerate() seems to have gone=
) :-/
>=20
> Please check the syslog; it should tell you whether the I/O-error occ=
urs
> while reading or writing.

Hi, and thanks again.

Just unloaded and loaded again and tested some disk operations with=20
cbmctrl and here is part from my /var/log/messages:

Mar 19 22:45:21 localhost cbm_init: using passive (XM1541) cable, irq 7
Mar 19 22:45:21 localhost cbm: resetting devices
Mar 19 22:45:22 localhost cbm: sleeping 5 seconds...
Mar 19 22:46:06 localhost cbm_read: I/O error

Well, it's not a big problem anyway. Since most of the time it now seem=
s=20
to work just fine.

Regards,
Mikko.