[back]

[index]

[next]

VII.a. Riebl Card Questions & Answers


[book picture] What are all those jumpers used for? (4)
Martin-Eric Racine <q-funk@pp.fishpool.com>

Answer from Leo Weppelman <leo@ahisinfr.xs4all.nl> :

There is some info about the jumpers in the NetBSD/Atari FAQ. Checkout :
     http://www.netbsd.org/Ports/atari/faq.html


Answer from Kerstin Hoef-Emden <aeb25@uni-koeln.de> :

Next draing explaines the settings of the Jumpers on the Riebl card


     +-------------------------------------+
    +|  AAAAAA                             |-+
AUI ||          D                          | |
    +|                           C         | |
     |                           C         | | VME
BNC =|                           C         | |
     |                               BBB   |-+
     +-------------------------------------+

The A and D jumpers are for addressing AUI or BNC. They have to be put altogether either to the "top" or the "bottom" of the card. They should be on top for AUI.
For a TT all C jumpers have to be set, for a MegaSTe none. As far as I remember, this is as well the setting for my Riebl.
B jumpers are not explained but are described as set/not set/set.


Answer from Ronald van der Kamp <atarist@xs4all.nl> :

Jumpers Riebl card in a TT :

  • J1-6 (Jumper array A)
    all together : BNC is to bottom and AUI is to top
  • J7 (Jumper D)
    J7 to top BNC other AUI - Some say : no jumper. What is it?
  • J8-J10 (Jumper array B)
    unknown works if closed/open/closed in TT
  • J17-23 (Jumper array C)
    all closed = TT - all open = megaSTE


[book picture] How do I update the address in the card's memory? (4)
Martin-Eric Racine <q-funk@pp.fishpool.com>

Answer from Leo Weppelman <leo@ahisinfr.xs4all.nl> :

There is a test-utility from Riebl that allows you to change the MAC-address. However, when you have only one Riebl card it doesn't really matter what the MAC-address is as long as you don't connect it to another Riebl card with an empty battery ;-)


Answer from Kerstin Hoef-Emden <aeb25@uni-koeln.de> :

The battery of the Riebl is soldered on the board.
After installing the card with correct jumper settings, it is important to initialise it, which means it is told its unique hardware address. The battery supplies the card with the power to keep this setting. A card with empty battery switches back to a default hardware address, which is not unique. While the STinG/MagiC combo doesnīt seem to be interested, Linux will complain during bootup, if the Riebl comes with default address and empty battery.

But there is a trick how to prevent the complaint in Linux. The cardīs battery may be empty, but despite this the card can have a valid hardware address. Some lines are added to one of the init scripts. These lines handle over the hardware address to the Riebl during Linux bootup prior to the installation of the Riebl driver. In this case you donīt need a battery.

[book picture] Any hint about using one with MiNTnet? (4)
Martin-Eric Racine <q-funk@pp.fishpool.com>

Answer from Ronald Andersson <dlanor@oden.se> :

Nope, except that I've seen a rumour that it should be possible.

Well, I just remembered that a Riebl card was exactly what Peter Rottengatter used, and for which he wrote the ETHER.STX which is part of the STinG 1.20 distribution package...

So for STinG, this card should be more or less 'plug-n-play' :-) (Except for possible hardware strap needs.) And if there is any problem, we do have access to the full source code as well, as this was sent out to the beta list quite some time ago.

I now it may be useless to even mention this to the NMD developer, but you could try it at least, as there is no conflict in using MiNT and STinG 'side-by-side' as long as they use separate ports.

In fact it should even be possible to write a combo of STX and XDD files that act as a local gateway from STinG to MintNet and vice versa, though I know far too little about XDD construction to do that job. (It is certainly possible at the STinG end though.)


Answer from Jo Even Skarstein <joska@nvg.ntnu.no> :

You're not the first one to think of this ;-) I have been thinking of writing packet-drivers for STiNG and MiNT-net (XIF, not XDD) that use a block of shared memory to exchange packets, mostly to be able to use STiNG's IP-masquerading. However, with the recent development of IP-masq. in MiNT-Net I no longer have any need for this.

As for the Riebl-card, there are drivers for it (inc. source) in the MiNT-Net distribtion, so it shouldn't be hard to set it up. The problem is (as M-E indicated) the Riebl's hardware-address which might be lost. I'm afraid I can't be of any assistance in this case, as I don't have a Riebl myself.


We already have GlueSTiK that patches STiK calls into MiNTnet, but indeed a low-level interface might be even better. The problem is, STinG is currently known not to work on AES 4.1 and MiNT.

[book picture] Software for the Riebl Card 4 (4)

Answer from Kerstin Hoef-Emden <aeb25@uni-koeln.de> :

The Atari Disks coming with the card contain a program to initialise the card. This includes asking for the hardware address. This program doesn't run under MagiC. It's necessary to boot up Single-TOS for it.

There is a driver for STinG as well. It is still concidered to be beta, but it works perfectly for me. But you anyway need the initialisation program for the hardware address, the one from the STinG beta release didn't work neither under MagiC, nor under Single TOS.


Answer from Karl Samyn <saka@village.uunet.be> :

ANS also has drivers for the Riebl Card. Following the installation instructions I got it working on a set of 2 Mega ST computers. It even works fine from a floppy disk.
My Riebl Card also works fine with the STinG drivers. The hardware address can't be set here, but it just works fine.




(4) : Site Update of 27 August 2000, © by Karl Samyn