Mediator + LAN + EasyNet

[D00kie]

Hi kreciu,

   I have got fastethernet.device working completely stable for a few years here. Is it Realtek 8139 compatible card? I have a Realtek 8139D, Voodoo3 3000, and a SB128 card all working together. If it seems like a hardware fault, you could try re-ordering the cards or run c:pciinfo to make sure no two cards have the same IRQ. Check elbox.com to make sure you have the latest fastethernet.device. I use my old Miami TCP stack, but it also worked in the RoadShow demo as well.

   If you have any other questions I'm happy to pop upstairs and crack the 1200T open and have a look for ya!

[D00kie]

Hi,
   I have a really early Mediator 1200 - the one where I had to pull and replace the U2 chips after a few months because of a design problem. It was difficult to stabilise, so I blame any card problems on that usually. If memory serves, you also need a really recent pci.device to work with fastethernet.

   TCP stacks on Amiga are not easy. I would say roadshow is easiest. To change anything in roadshow, you have to edit config files by hand, but the demo installed and got running really easily. And it does DHCP so that makes things way easier. With Miami I've gotta put a DHCP address reservation in the router because you can only have a static address.

[D00kie]

Here is some information about my Mediator setup:
Slot 1 is the sound card
Slot 2 fast ethernet
Slot 3 empty
Slot 4 Video card
-----------------------------------------------
New Shell process 4
4.Workbench:> version libs:pci.library
pci.library 9.11
4.Workbench:> version devs:networks/fastethernet.device
FastEthernet.device 1.25
4.Workbench:> pciinfo

Pci Device 1:
   VendorID: $1274
   VendorName: Ensoniq
   DeviceID: $5880
   DeviceName: 5880 AudioPCI
   ClassCode: $40100
   RevisionID: $2
   InterruptPin: 1
   SubsystemVendorID: $1274
   SubsystemID: $2000
   IOSpace0: $ed6000 - $ed603f

Pci Device 2:
   VendorID: $10ec
   VendorName: Realtek Semiconductor
   DeviceID: $8139
   DeviceName: RT8139A/B/C Fast Ethernet Adapter
   ClassCode: $20000
   RevisionID: $10
   InterruptPin: 2
   SubsystemVendorID: $10ec
   SubsystemID: $8139
   IOSpace0: $ed6400 - $ed64ff
   MemSpace1: $80000000 - $800000ff
   RomSpace: $80020000 - $8003ffff

Pci Device 3:
   VendorID: $121a
   VendorName: 3dfx Interactive Inc
   DeviceID: $5
   DeviceName: Voodoo3 All Voodoo3 chips, 3000
   ClassCode: $30000
   RevisionID: $1
   InterruptPin: 4
   SubsystemVendorID: $121a
   SubsystemID: $57
   MemSpace0: $82000000 - $83ffffff
   MemSpace1: $84000000 - $85ffffff
   IOSpace2: $ed6800 - $ed68ff
   RomSpace: $80010000 - $8001ffff

[D00kie]

When you see a yellow box like the red Guru, that is classed as "recoverable error" and it usually means that, although the system can continue, it's about time to save all of your work and prepare for the eventual collapse of the OS that is coming. I think there is still a driver problem - either fastehternet.device or incompatibility between fastethernet and pci.device. If the system is stable when not connected to the Internet then it's probably that. AmigaKit.com shows a RealTek card in the photograph so I assume it's supported by the Mediator.

I'd encourage you to run the PCIinfo and make sure the card is not sharing an interrupt with another card. Some cards can share interrupts but I would try to avoid it...

[D00kie]

I've been using the Netsurf Beta 3.8 from Arti for a few months. I seem to remember another person doing an entirely different port (was his name Chris?) that I liked a bit less.

When the whole screen is a solid yellow, it's usually a memory problem. I've had this twice - one cause was actually faulty RAM. The other is when the machine crashes and the remapped ROM image gets corrupted by a crashing program. I also see a yellow screen when booting with an incompatible turbo-board mapper. For instance I was using the MMULib maprom and fastzero, when I should have been using Remapollo because the latter was designed specifically for my Apollo board.

Hope this helps!