Re: [cbm4linux-users] driver error

[Michael K. <mic...@pu...>]

On Fri, 19 Mar 2004, Mikko Kein=E4nen wrote:

> 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.d64
> >>[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 maybe
> > 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:

[occasional errors snipped]

> > Unfortunately I have no running 2.6 kernel right now, and I wasn't able
> > to reproduce this behaviour with 2.4.
>
> Maybe I should test with 2.4 kernel... I had no problems with 2.4 kernel
> some time ago when I installed cbm4linux ... the hardware setup should
> be the same in my computer now as it was then.

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) :-/

Please check the syslog; it should tell you whether the I/O-error occurs
while reading or writing.

Cheers!

--=20
Michael

"I may have invented Ctrl-Alt-Del, but Microsoft made it popular."
  - David Bradley, one of the designers of the original IBM PC