Thread: [cbm4linux-users] driver error
Brought to you by:
cbm4linux
Menu
▾
▴
cbm4linux-users
|
From: <mik...@dn...> - 2004-03-15 19:41:23
|
Hi!
Any ideas why I get the following error message in every other time I=20
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=
=20
so on... ;)
I'm using 2.6 kernel (in Gentoo Linux). My cable is XM1541.
I'm using the following options with cbm-module:
options cbm lp=3D0 cable=3D0 reset=3D1
And following options with parport_pc module:
options parport_pc io=3D0x378 irq=3D7
Here is my kernel configuration:
<M> Parallel port support
<M> PC-style hardware=20
< > Multi-IO cards (parallel and serial)=20
[*] Use FIFO/DMA if available=20
(EXPERIMENTAL) [ ] SuperIO=20
chipset support (EXPERIMENTAL)=20
[ ] Support foreign hardware=20
[*] IEEE 1284 transfer modes
Has anyone had similar problems?
Thanks & best regards,
Mikko Kein=E4nen.
|
|
From: Michael K. <mic...@pu...> - 2004-03-19 10:09:02
|
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? > I'm using 2.6 kernel (in Gentoo Linux). My cable is XM1541. Unfortunately I have no running 2.6 kernel right now, and I wasn't able to reproduce this behaviour with 2.4. > I'm using the following options with cbm-module: > > options cbm lp=3D0 cable=3D0 reset=3D1 > > And following options with parport_pc module: > > options parport_pc io=3D0x378 irq=3D7 > > Here is my kernel configuration: > > <M> Parallel port support > =09<M> PC-style hardware > =09< > Multi-IO cards (parallel and serial) > =09[*] Use FIFO/DMA if available > (EXPERIMENTAL Options are IMO o.k. (somehow your mail got truncated here, although it's completely visible in the archive) Cheers, --=20 Michael message composed with VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Nov 9 2003 21:24:11) |
|
From: <mik...@dn...> - 2004-03-19 10:32:53
|
Hi! Thanks for your aswer! Michael Klein wrote: > On Mon, 15 Mar 2004, Mikko Kein=E4nen wrote: >=20 >=20 >>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 a= nd >>so on... ;) >=20 >=20 > Odd. Is that the case for *all* disk commands or only d64copy (or may= be > serial1-specific?). Your drive contains a normal 1541 ROM, I assume? Yes, I think it happens with all the commands ... just tested with=20 cbmctrl -command and it seems now that the error doesn't show up so=20 often, it seems more random: --- bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 99, driver error,00,00 cbmctrl: dir: Input/output error bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 99, driver error,00,00 cbmctrl: dir: Input/output error bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 99, driver error,00,00 cbmctrl: dir: Input/output error bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 bash-2.05b$ cbmctrl dir 8 0 ."6pack " 05 2a 664 blocks free. 00, ok,00,00 --- Well, its better this way. Still I'm a bit confused. But I'm really=20 happy to have cbm4linux! :) >>I'm using 2.6 kernel (in Gentoo Linux). My cable is XM1541. >=20 >=20 > Unfortunately I have no running 2.6 kernel right now, and I wasn't ab= le > to reproduce this behaviour with 2.4. Maybe I should test with 2.4 kernel... I had no problems with 2.4 kerne= l=20 some time ago when I installed cbm4linux ... the hardware setup should=20 be the same in my computer now as it was then. >>I'm using the following options with cbm-module: >> >>options cbm lp=3D0 cable=3D0 reset=3D1 >> >>And following options with parport_pc module: >> >>options parport_pc io=3D0x378 irq=3D7 >> >>Here is my kernel configuration: >> >> <M> Parallel port support >> <M> PC-style hardware >> < > Multi-IO cards (parallel and serial) >> [*] Use FIFO/DMA if available >>(EXPERIMENTAL >=20 >=20 > Options are IMO o.k. >=20 > (somehow your mail got truncated here, although it's completely visib= le > in the archive) >=20 > Cheers, >=20 Best regards, Mikko. |
|
From: Michael K. <mic...@pu...> - 2004-03-19 20:12:09
|
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 |
|
From: <mik...@dn...> - 2004-03-19 20:53:34
|
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. |
|
From: <mik...@dn...> - 2004-03-19 10:39:51
|
Michael Klein wrote: > 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? Oh, yes it should be normal 1541 ROM. - Mikko. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X