cbm4linux-users — Any cbm4linux related discussions

Re: [cbm4linux-users] No such device

[<fo...@t-...>]

Hi!

> No error here, just a warning. Is that the complete output?
Yes, it was the complete output.

> Did you check /proc/interrupts?
Uuh, i didn't check this and this was the problem. I had to add a 
kernelparameter like "parport=0x3bc,7"
Yes, it works :-)

> > I did't use make-kpkg because it made a lot but nothing which belongs to
> > cbm4linux :-(
> Can you be more specific?
Well, usally i don't use make-kpkg and so i didn't know how to use this tool 
exactly. My computer worked like i entered "make bzImage" but in the end 
there was no cbm4linux*.deb. 

I saved my first old floppy disk and i'm very happy.

> Good luck!
Thanks a lot!

Daniel

Re: [cbm4linux-users] No such device

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

Hi Daniel!

> I'm using Debian with a 2.6.6-2 Kernel and got the cbm4linux sources by
> apt-get.
> First problem: I had no modsetver.h in /usr/src/linux/include/linux , so i
> copied it from /usr/include/linux.
> I hope this is ok.

Not sure about that. We'll see... ;-)

> After this i tried again to build a cbm module with "./debian/rules
> KSRC=/usr/src/linux build".
> I got an error message but although cbm.ko and cbm.o.
> >Output:
> > dh_testdir
> > dh_testroot
> > dh_clean
> > if [ -f debian/control.backup ]; then \
> >         mv -f debian/control.backup debian/control; \
> > fi
> > rm -f *.ko *.o cbm.mod.* build-stamp
> > dh_testdir
> > dh_testroot
> > make -C /usr/src/linux SUBDIRS=/usr/src/modules/cbm4linux modules
> > make[1]: Entering directory `/usr/src/kernel-source-2.6.6'
> >   CC [M]  /usr/src/modules/cbm4linux/cbm_module.o
> > /usr/src/modules/cbm4linux/cbm_module.c: In Funktion >>init_module<<:
> > /usr/src/modules/cbm4linux/cbm_module.c:697: Warnung: Verarbeiten des
> Argumentes 5 von >>parport_register_device<< von inkompatiblem Zeigertyp
> > /usr/src/modules/cbm4linux/cbm_module.c:663: Warnung: unused variable `i'
> >   LD [M]  /usr/src/modules/cbm4linux/cbm.o
> >   Building modules, stage 2.
> >   MODPOST
> >   CC      /usr/src/modules/cbm4linux/cbm.mod.o
> >   LD [M]  /usr/src/modules/cbm4linux/cbm.ko
> > make[1]: Leaving directory `/usr/src/kernel-source-2.6.6'
> > touch build-stamp

No error here, just a warning. Is that the complete output?

> Hoping the best i copied cbm.ko to /lib/modules/2.6.6/kernel/drivers/misc and
> edited /lib/modules/2.6.6/modules.dep.
> By the way parport_pc ist compiled into kernel und detects the port (0x3bc,
> irq7).
> from kern.log:
> > parport0: PC-style at 0x3bc (0x7bc) [PCSPP,TRISTATE]
> > parport0: irq 7 detected
> > lp0: using parport0 (polling).
> Now i got this error:
> > blackbox:/home/daywalker# modprobe cbm
> > FATAL: Error inserting cbm (/lib/modules/2.6.6/kernel/drivers/misc/cbm.ko):
> No such device
> from kern.log:
> > cbm_init: parallel port irq not configured: 0

Looks like you have to configure the IRQ explicitly. Just because the
IRQ line is detected doesn't also mean it's actually used ;-)

Did you check /proc/interrupts?

> I read old mailing articles and searched with "google" but i did'nt find any
> comparable.
> I did't use make-kpkg because it made a lot but nothing which belongs to
> cbm4linux :-(

Can you be more specific?

> Probably you see i'm a newbie and my english is sluttishly but i hope you can
> help me even though.

Good luck!

-- 
Michael

Debian is like Suse with yast turned off, just better. :)
	-- Goswin Brederlow

Re: [cbm4linux-users] Cant open source from d71

[Spiro T. <tri...@gm...>]

Hello Mats,

* On Mon, Nov 01, 2004 at 12:16:22AM +0100 Mats Johansson wrote:
 
> When i use d64copy to create a d71 image it works very well the image
> is created and works well.

Can you tell how big the image is (in bytes)?
 
> [Fatal] neither a .d64 not .d71 file: hej2.d71

This message tells us that the d64copy thinks that it is neither a D64
nor a D71 image (what else should this message tell?), and this is
determined by the size of the image in libd64copy/fs.c - open_disk().

BTW: Have you tried without specifying -2? From a brief view, it does
not seem to have any effect on this message, but to be sure... (D71
always use 2 sides, so there is no need for specfying it).

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

[cbm4linux-users] Cant open source from d71

[Mats J. <mj...@ti...>]

Hi.
I have started played around with my 1571 in 1571 mode(doubleside mode).

When i use d64copy to create a d71 image it works very well the image is
created and works well.

But then when i should write a d71 image to the drive i only get the erro=
r

d64copy  -2 image.d71  9

[Fatal] neither a .d64 not .d71 file: hej2.d71
[Fatal] can't open source


Anyone know?

/Mats

[cbm4linux-users] No such device

[Daniel F. <Dan...@ud...>]

Hi!


I'm using Debian with a 2.6.6-2 Kernel and got the cbm4linux sources by 
apt-get.
First problem: I had no modsetver.h in /usr/src/linux/include/linux , so i 
copied it from /usr/include/linux.
I hope this is ok.

After this i tried again to build a cbm module with "./debian/rules 
KSRC=/usr/src/linux build".
I got an error message but although cbm.ko and cbm.o.
>Output:
> dh_testdir
> dh_testroot
> dh_clean
> if [ -f debian/control.backup ]; then \
>         mv -f debian/control.backup debian/control; \
> fi
> rm -f *.ko *.o cbm.mod.* build-stamp
> dh_testdir
> dh_testroot
> make -C /usr/src/linux SUBDIRS=/usr/src/modules/cbm4linux modules
> make[1]: Entering directory `/usr/src/kernel-source-2.6.6'
>   CC [M]  /usr/src/modules/cbm4linux/cbm_module.o
> /usr/src/modules/cbm4linux/cbm_module.c: In Funktion >>init_module<<:
> /usr/src/modules/cbm4linux/cbm_module.c:697: Warnung: Verarbeiten des 
Argumentes 5 von >>parport_register_device<< von inkompatiblem Zeigertyp
> /usr/src/modules/cbm4linux/cbm_module.c:663: Warnung: unused variable `i'
>   LD [M]  /usr/src/modules/cbm4linux/cbm.o
>   Building modules, stage 2.
>   MODPOST
>   CC      /usr/src/modules/cbm4linux/cbm.mod.o
>   LD [M]  /usr/src/modules/cbm4linux/cbm.ko
> make[1]: Leaving directory `/usr/src/kernel-source-2.6.6'
> touch build-stamp

Hoping the best i copied cbm.ko to /lib/modules/2.6.6/kernel/drivers/misc and 
edited /lib/modules/2.6.6/modules.dep.
By the way parport_pc ist compiled into kernel und detects the port (0x3bc, 
irq7).
from kern.log:
> parport0: PC-style at 0x3bc (0x7bc) [PCSPP,TRISTATE]
> parport0: irq 7 detected
> lp0: using parport0 (polling).
Now i got this error:
> blackbox:/home/daywalker# modprobe cbm
> FATAL: Error inserting cbm (/lib/modules/2.6.6/kernel/drivers/misc/cbm.ko): 
No such device
from kern.log:
> cbm_init: parallel port irq not configured: 0

I read old mailing articles and searched with "google" but i did'nt find any 
comparable.
I did't use make-kpkg because it made a lot but nothing which belongs to 
cbm4linux :-(

Probably you see i'm a newbie and my english is sluttishly but i hope you can 
help me even though.

Thanks
Daniel

Re: [cbm4linux-users] Transfer time of a complete D64 with standard IEC protocol?

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

On Fri, 1 Oct 2004, Joe Forster/STA wrote:

>> Can anybody tell me how much time it takes to read a complete floppy
>> image (D64) using only the original IEC bus protocol?
>
> I don't think anyone would have enough time to test this... 8^) Seriously,
> when I tested it last time with The Star Commander - not cbm4linux! -, I
> managed to read a full 1541 disk in 7:50 and write it in 9:55. That was
> normal mode, the usual IEC protocol, no extras and that's what I wrote
> into the benchmark table in the docs. Bye,

cbm4linux is a bit slower. Somewhere between 10 and 12 minutes, 
depending on load and interleave.

cheers!

-- 
Michael

puffin:~ > uptime
  15:00:53 up 59 days,  7:28,  1 user,  load average: 0.31, 0.13, 0.07

Re: [cbm4linux-users] Transfer time of a complete D64 with standard IEC protocol?

[Joe Forster/S. <st...@c6...>]

Hi Spiro,

> Can anybody tell me how much time it takes to read a complete floppy
> image (D64) using only the original IEC bus protocol?

I don't think anyone would have enough time to test this... 8^) Seriously,
when I tested it last time with The Star Commander - not cbm4linux! -, I
managed to read a full 1541 disk in 7:50 and write it in 9:55. That was
normal mode, the usual IEC protocol, no extras and that's what I wrote
into the benchmark table in the docs. Bye,

Joe
--=20
KOV=C1CS Bal=E1zs alias Joe Forster/STA      st...@c6...; http://sta.c64.or=
g
Orsolya u. 5. IV/12., 1204 Budapest, Hungary; +36-1-285-3881, 6-10PM CET
(SpamAssassin protection! No HTML E-mails! No uncompressed attachments!)

[cbm4linux-users] Transfer time of a complete D64 with standard IEC protocol?

[Spiro T. <tri...@gm...>]

Hello,

just a short question: Can anybody tell me how much time it takes to
read a complete floppy image (D64) using only the original IEC bus
protocol?

As I told, all times without "enhanced" protocols, or even parallel
cables?

TIA,
   Spiro.

--
Spiro R. Trikaliotis
http://www.trikaliotis.net/

Re: [cbm4linux-users] cbmctrl open 8 15 V0 - does it do anything observable?

[Spiro T. <tri...@gm...>]

Hello,

* On Sat, Jul 10, 2004 at 02:26:37PM +0200 I wrote:
 
 
> $ cbmctrl open 8 15 V0
> 
> should let a 1571 drive perform a "validate" command, that is, do you
> hear the floppy doing something?

Please disregard this, I have found my bug.

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

[cbm4linux-users] cbmctrl open 8 15 V0 - does it do anything observable?

[Spiro T. <tri...@gm...>]

Hello,

as I currently have some problems, could somebody please tell me if the
command

$ cbmctrl open 8 15 V0

should let a 1571 drive perform a "validate" command, that is, do you
hear the floppy doing something?

Is a 

$ cbmctrl unlisten

necessary afterwards?

Thanks in advance,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

Re: [cbm4linux-users] cbm4linux problem

[Andreas <co...@c6...>]

> In particular, I think the chipset of your motherboard may not be
> compatible with the XE1541/XM1541 cables. So, you should collect the
> information listed above and send it to us... Ciao,
>
> Joe

Changing around the available BIOS settings for the parport often helps.

l8r

-- 
Count Zero/CyberpunX/SCS*TRC

http://pokefinder.org
Replay Copy Convention
28th - 31st May 2004!

Re: [cbm4linux-users] cbm4linux problem

[Joe Forster/S. <st...@c6...>]

Hi David,

I quote from the XCTest docs:

---

  If you have questions about this program, the tests or your test results
then send a detailed report to the author's E-mail address below. Your
report should contain, at least, the following information:

  1. Manufacturer and type of the motherboard of your PC.

  2. Manufacturer and type of the chipset on the I/O controller card or
     the one integrated onto the motherboard.

  3. The type of your serial cable.

  4. Manufacturer and type of your Commodore drive (if you have connected
     one).

  5. All configuration settings in the program. (In a later release,
     settings will be logged into a file automatically.)

  6. The code of the test you tried - it's in all capitals in front of the
     test description. (In a later release, input line histories will be
     logged into a file automatically.)

  7. Any other circumstances that you think to be important.

---

In particular, I think the chipset of your motherboard may not be
compatible with the XE1541/XM1541 cables. So, you should collect the
information listed above and send it to us... Ciao,

Joe
--=20
KOV=C1CS Bal=E1zs alias Joe Forster/STA      st...@c6...; http://sta.c64.or=
g
Orsolya u. 5. IV/12., 1204 Budapest, Hungary; +36-1-285-3881, 6-10PM CET
(SpamAssassin protection! No HTML E-mails! No uncompressed attachments!)

Re: [cbm4linux-users] cbm4linux problem

[<ds...@pu...>]

Hi, and thanks for the reply.

I just tried xctest, and there's definately something wrong somewhere. For
the test with the cable connected to the parallel port but not connected
to the 1541, the behavior is correct (all inputs follow their respective
outputs). However, when I plug the serial end into the 1541, the DATA line
is pulled low all the time. The weird thing is that this also happens when
the drive is off. I actually watched the data line being pulled low when I
connected the drive. All the other inputs followed their outputs as they
should.

Now I'm even more confused than before... what could cause this? The drive
works like a charm on my c64.

XCDetect just hung when I tried to start it, before printing anything to
screen. Also happened when no cable was attached, so that could be
something caused by my machine.

Any insight as to possible causes for this weird behavior would be greatly
appreciated, as I'm at a complete loss.

Thanks,
David

> Hi David,
>
> [XM1541 cable]
>> I'm starting to suspect the cable... too bad, I really can't see what's
>> wrong with it. Is there any way to test it?
>
> If you don't mind booting and using DOS for an hour or so, ;-) grab XCTest
> from http://sta.c64.org/scextprg.html#xctest and XCDetect from
> http://sta.c64.org/scextprg.html#xcdetect . Good luck,
>
> Joe
> --
> KOVÁCS Balázs alias Joe Forster/STA      st...@c6...; http://sta.c64.org
> Orsolya u. 5. IV/12., 1204 Budapest, Hungary; +36-1-285-3881, 6-10PM CET
> (SpamAssassin protection! No HTML E-mails! No uncompressed attachments!)

Re: [cbm4linux-users] cbm4linux problem

[Joe Forster/S. <st...@c6...>]

Hi David,

[XM1541 cable]
> I'm starting to suspect the cable... too bad, I really can't see what's
> wrong with it. Is there any way to test it?

If you don't mind booting and using DOS for an hour or so, ;-) grab XCTest
from http://sta.c64.org/scextprg.html#xctest and XCDetect from
http://sta.c64.org/scextprg.html#xcdetect . Good luck,

Joe
--=20
KOV=C1CS Bal=E1zs alias Joe Forster/STA      st...@c6...; http://sta.c64.or=
g
Orsolya u. 5. IV/12., 1204 Budapest, Hungary; +36-1-285-3881, 6-10PM CET
(SpamAssassin protection! No HTML E-mails! No uncompressed attachments!)

Re: [cbm4linux-users] cbm4linux problem

[<ds...@pu...>]

>> Anyone have any ideas? Hardware malfunction is quite possible, as this
>> drive does sometimes behave strangely. The cable also could be suspect -
>> it's an XM1541 I made. I've checked it several times, and can see
>> nothing
>> wrong with it, but you never know.
>
> my first guess would be the drive - is it possible for you to test with
> another? BTW, which kernel version are you running?

I'm running kernel 2.6.5 at the moment.

I just dug up my c64 and tested the drive with it, and it seems to work
like a charm. Listed the files on a few floppies, and loaded up the trusty
turbo assembler without any problems.

I'm starting to suspect the cable... too bad, I really can't see what's
wrong with it. Is there any way to test it?

Thanks.

-David

Re: [cbm4linux-users] cbm4linux problem

[Simon S. <ss...@we...>]

> Anyone have any ideas? Hardware malfunction is quite possible, as this
> drive does sometimes behave strangely. The cable also could be suspect -
> it's an XM1541 I made. I've checked it several times, and can see nothing
> wrong with it, but you never know.

my first guess would be the drive - is it possible for you to test with 
another? BTW, which kernel version are you running?

[cbm4linux-users] cbm4linux problem

[<ds...@pu...>]

Hi.

I've been trying to get my 1541 drive working with cbm4linux recently, and
I'm having a very annoying problem. What's most annoying about it is that
I have no idea what's causing it - cbm4linux, my drive or my cable.

Basically, when I boot up and load parport_pc and cbm, I get the following
output in my kernel log:
cbm_init: using passive (XM1541) cable (auto), irq 7
cbm: resetting devices
cbm: sleeping 5 seconds...

So far, so good. I then run cbmctrl detect, and it shows my 1541 as device 8.

But when I try to write to it (d64copy foo.d64 8), there's several things
that seem to happen at random. Either I get the following output:
[Fatal] could not identify device
[Warning] Unknown drive, assuming 1541
[Fatal] drive 08 (1541): 99, DRIVER ERROR,00,00

Or it starts, and gives back write errors for every sector, with the drive
not actually doing anything.

Sometimes, however, it seems to work just fine, but then after a few
sectors gives write errors.

Anyone have any ideas? Hardware malfunction is quite possible, as this
drive does sometimes behave strangely. The cable also could be suspect -
it's an XM1541 I made. I've checked it several times, and can see nothing
wrong with it, but you never know.

Any help would be greatly appreciated! Thank you.

-David

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.

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

Re: [cbm4linux-users] driver error

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

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.

Re: [cbm4linux-users] driver error

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

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.

Re: [cbm4linux-users] driver error

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

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)

[cbm4linux-users] driver error

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

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.

Re: [cbm4linux-users] a few questions

[Joe Forster/S. <st...@c6...>]

Hi Count Zero,

> Yes, using -s1   -s2 and warpmodes works just fine. Reads the very same disk
> perfectly. Reading the disk with parallel transfer several times shows the
> errors on different places ....

Okay, some testing strategy:

1. In parallel mode, is it _always the same disks_ that show you errors?

2. In serial mode, do _all disks_ transfer fine?

3. Do the same disks, with the same drive, the same cable, the same PC
   transfer fine with The Star Commander, using identical settings as
   with cbm4linux, including enabling the parallel cable?

If the answers are:

- no, yes, yes: there are some problems with the implementation of the
  parallel warp routines in cbm4linux.

- no, no, yes: there are some problems with cbm4linux on your PC.
  Perhaps, the PC is too slow or too fast, Linux is eating up too much
  CPU power etc. etc...

- no, yes, no: there is a general implementation problem with the parallel
  transfer routines (as those have been adapted from the Commander).

So, help yourself and test everything in every way you can. ;-) If you
come back with a much more detailed test suite with results then, I'm
sure, Michael will also be able to help you more... Bye,

Joe

Re: [cbm4linux-users] a few questions

[Andreas <co...@c6...>]

Again, Yo Joe, :)

> Okay, so disabling the parallel cable does help... (?) Bye,
>
> Joe

Forgot to add, that the adapter-board I am using was changed from the XEP 
Adapter it used to be to an XMP to work with linux ... :)


-- 
Count Zero/CyberpunX/SCS*TRC
http://rr.c64.org - Retro Replay home