Prometheus - Best Practices?

[jbenam]

Originally Posted by zipper

My Iso is 174 MB: https://mega.nz/file/K1dlRQIa#USkIgy...YyD8g9nmPMJSbg - game demos take 144 MB...

Great stuff, that's the one!

I wanted to start with the CD then apply the various patches next, just like Matay intended originally.

Thank you very much

[DarrenHD]

Hey everyone, does anyone have a RTL 8029 network card working in an AA3000+ - but with the updated Firestorm firmware?

I have tried two RTL 8029 cards - both working in other systems (Mediator/GREX), but on my AA3000+ with Prometheus w/Firestorm firmware, the cards will stall after a very short time. They can go online and ping, but as soon as you try to open a connection (eg. do a dir listing on FTP), or actually download a file from Aminet, the connection will stop working. Pings will suddenly stop working etc.

I am using the very latest 1.4 driver that was last available on Maytay's website. Tried the previous 1.3 driver as well. I am wondering if the Firestorm firmware is the issue.

Thanks
Darren

[jbenam]

I do have a RTL8029 I intend putting in my A4000D (I have a 10Mbit thinnet LAN in my lab) along with a non-Firestorm (not yet, at least - I have a USB Blaster, though) Prometheus.

Will report back if I get the same issues with mine - as soon as I get to fix that damned 80000004 error I get when my system tries to initialise the Prometheus...

[DarrenHD]

Originally Posted by jbenam

I do have a RTL8029 I intend putting in my A4000D (I have a 10Mbit thinnet LAN in my lab) along with a non-Firestorm (not yet, at least - I have a USB Blaster, though) Prometheus.

Will report back if I get the same issues with mine - as soon as I get to fix that damned 80000004 error I get when my system tries to initialise the Prometheus...

try putting cpu nocache before that happens, see if it helps. I had a similar problem with a Mediator once. I think the RTL 8029 should work with non firestorm firmware, but anyway let me know.

Darren

[torsti76]

Originally Posted by DarrenHD

Hey everyone, does anyone have a RTL 8029 network card working in an AA3000+ - but with the updated Firestorm firmware?

I have tried two RTL 8029 cards - both working in other systems (Mediator/GREX), but on my AA3000+ with Prometheus w/Firestorm firmware, the cards will stall after a very short time. They can go online and ping, but as soon as you try to open a connection (eg. do a dir listing on FTP), or actually download a file from Aminet, the connection will stop working. Pings will suddenly stop working etc.

I am using the very latest 1.4 driver that was last available on Maytay's website. Tried the previous 1.3 driver as well. I am wondering if the Firestorm firmware is the issue.

Thanks
Darren

This is weird! I'm seeing the same, but with a RTL8139 via OpenPCI. I (usually) can initialize it fine with Roadshow, it reserves DMA space and retrieves the DHCP settings.

But if I start sending/receiving data through the card (ping is enough to trigger it), after 3 to 10, sometimes 15 packets, the system either freezes or gives me a 8000 0004.

Sometimes it freezes right away while initializing the card. I tried prometheus.library 3.1, which seems to be the most stable, but also the newer ones from Hedeon. The effect is always similar...

Gesendet von meinem XQ-BT52 mit Tapatalk

[jbenam]

Originally Posted by DarrenHD

try putting cpu nocache before that happens, see if it helps. I had a similar problem with a Mediator once. I think the RTL 8029 should work with non firestorm firmware, but anyway let me know.

Darren

Sadly it didn't help, I still get the dreaded 80000004. I guess I will keep replacing GALs on my motherboard until something changes

[Hedeon]

I have a RTL8029 in my AA3000+ and it works fine. I used it to transfer 100s of MBs from my PC and Mac Mini during the time I had it. I did not upgrade the drivers. It were the drivers I had when my old A3000 was fitted with the old Prometheus. I just copied the whole HD over to an SD card (I use SCSI2SD now) and upgraded only the main library (and the .card and .chip but those are not related to RTL8029. They are related to RTL8139 however due do DMA being handled in the gfx drivers)

[DarrenHD]

Originally Posted by Hedeon

I have a RTL8029 in my AA3000+ and it works fine. I used it to transfer 100s of MBs from my PC and Mac Mini during the time I had it. I did not upgrade the drivers. It were the drivers I had when my old A3000 was fitted with the old Prometheus. I just copied the whole HD over to an SD card (I use SCSI2SD now) and upgraded only the main library (and the .card and .chip but those are not related to RTL8029. They are related to RTL8139 however due do DMA being handled in the gfx drivers)

Thanks Hedeon. I assume you are running Firestorm firmware on it. What version of the RTL8029 driver is it? Can you do a full version on it and post it here? Maybe email it to me?

Thanks,
Darren

[Hedeon]

Version 1.3 11.11.2002

[DarrenHD]

@Hedeon, thanks. I'm currently running 1.4 (1/29/2005) but I believe I tried 1.3 with the same result. It is perhaps something local to my network, maybe going through multiple switches is causing some issues with the driver. I am behind two small 4 port switches which are connected to each other then to a 24-port switch, which is where my router is....I may try to simplify the setup to see if that helps. Otherwise I am pretty much at a loss. May try to reinstall everything, perhaps that will help.

[Hedeon]

Mine goes from network card to switch to power socket adapter (2x) then to router-modem. Not sure what is new in 1.4?

[DarrenHD]

Originally Posted by Hedeon

Mine goes from network card to switch to power socket adapter (2x) then to router-modem. Not sure what is new in 1.4?

It may be my software setup. I should try a clean install, although on the same software setup an AmigaONE PCI wireless card works with the Prism2 driver (although it's very slow - but it works fine).


I am not 100% sure what is in 1.4, just "fixes" by Neil Cafferkey I read. I should also try the card in my other AA3000 to see if it also stalls.


It's almost like it can't make some connections. Like I can browse Aminet fine using IBrowse 2.5.4, but as soon as I try to download a file it stalls. Similarly I can login to an ftp site, but as soon as I try a directory listing or to download a file it stalls. I can ping no problem.


Strange.

[DarrenHD]

So I've tried a RTL8029 network card (actually multiple cards) on two AA3000+'s and they both do the same thing: I can get a DHCP address and ping, and I can even browse aminet, but as soon as I try to download something the connection stalls, pings stop working. Similarily with command line ftp: I can login to the site but as soon as I try to do a directory listing it hangs the connection.

In the same machine a C= 2065 zorro card works fine, as does a PCI based AmigaONE wireless network card, although the wireless card is dog slow, but it works.

So either I have incompatible RTL8029 cards (I did try two different 8029 cards) or something else is going on either with the Firestorm firmware and/or RTL8029 driver. I tried two different drivers. 1.3 and 1.4.

[torsti76]

Originally Posted by DarrenHD

So I've tried a RTL8029 network card (actually multiple cards) on two AA3000+'s and they both do the same thing: I can get a DHCP address and ping, and I can even browse aminet, but as soon as I try to download something the connection stalls, pings stop working. Similarily with command line ftp: I can login to the site but as soon as I try to do a directory listing it hangs the connection.

In the same machine a C= 2065 zorro card works fine, as does a PCI based AmigaONE wireless network card, although the wireless card is dog slow, but it works.

So either I have incompatible RTL8029 cards (I did try two different 8029 cards) or something else is going on either with the Firestorm firmware and/or RTL8029 driver. I tried two different drivers. 1.3 and 1.4.

This sounds like an MTU issue. What type of internet connection do you use?

Gesendet von meinem XQ-BT52 mit Tapatalk

[DarrenHD]

Originally Posted by torsti76

This sounds like an MTU issue. What type of internet connection do you use?

Gesendet von meinem XQ-BT52 mit Tapatalk

Cable internet. I tried the RTL 8029 card in both my AA3000+'s and they both behave the same. I also tried a clean OS install and it didn't help.

[DarrenHD]

Originally Posted by torsti76

This sounds like an MTU issue. What type of internet connection do you use?

Gesendet von meinem XQ-BT52 mit Tapatalk

I tried changing the MTU in Roadshow to 1460 and also 1500. No change. Same issue. I also tried a 3rd RTL8029 card and it behaves the same. So now I have the same behaviour in two AA3000+'s, one with C= 3640 and one with a Cyberstorm MK3. I've tried different versions of the driver. I've tried Roadshow and Miami, both behave the same (by the way, Miami's MTU was 1500 to start with). I am using real 3.2 roms.

I can only conclude that there are issues with the cards that I have tested (that are all RTL8029 but different variants) and they are are not working in my machines in this combination of Prometheus/Firestorm firmware, OS/ROM, and TCP/IP Stack. I am also using a Voodoo 3 in this machine and have DMA memory allocated (but not used). I did disable that but again no change.

As to how Hedeon got his RTL8029 working....I wish I could replicate!)

Darren

[torsti76]

Can someone with a AA3000+ do me a great favour?

Please install the latest prometheus.library from the Sonnet7200 thread, take out all boards from the Firebird, and run showboards.

Then switch off the machine, take out the entire Firebird, switch the machine on again, and run showboards again.

Do you see any "ghost" PCI cards with weird IDs in either or both tests?

Thank you very much to whoever will do this for me!

[Hedeon]

Updated prometheus.library to 4.1

Fixed multi-functional PCI card recognition/set-up (e.g. NEC USB 2.0 cards)
Fixed PCI(e) bridge recognition/set-up

See http://eab.abime.net/showpost.php?p=997765&postcount=1

[spudje]

OK, so I hope I'm in the correct thread now Sorry for hijacking other threads.

Building up my AA3000+.
My setup:
AA3000+ 16 MB FastRAM 3.2.1 ROM
CSMk2 060 128 MB
External SCSI2SD v5.5
Firebird Prometheus PCI DB
Apocalypse PPC PCI
Voodoo 3 PCI
Multiple options for ethernet & USB (limited by space ) and a Terratec sound card, but that most likely will not go in due to these space limitations.

I have gathered the following:
- Latest Prometheus firmware for Firestorm (E3B)
- PrmLibs41 from Hedeon (non OpenPCI correct?)
- prm-rtl8029.device 1.3 (non OpenPCI correct?)
- openpci_8139.device 1.2b4 (OpenPCI)
- OP-FM801v0.9b (sound) (OpenPCI correct?)
- prmscan 1,6 (OpenPCI)
- DMAlist 1.2 (OpenPCI)
- ArakAttack 1.23 from Aminet (OpenPCI)

Some questions:
- Do I have latest versions of everything?
- Can I combine non OpenPCI prometheus (voodoo, PPC, rtl8029) with OpenPCI drivers (e.g. USB, sound, RTL 8139)?
- Why is an ArakAttack key needed while it is available on Aminet? Is there a newer version that requires a key? If so can anyone provide it to me?

[spudje]

OK, hopping around threads, because it's not fully clear to me which to use when.

I have my setup sort of running, but run into Warp3D issues (I think).

Fullscreen GearsPPC + Gears68k work
Windowed & small GearsPPC + Gears68k give orange guru

I used Warp3D 4.2 from aminet, installed using the installer and had to add the PPC libraries manually, since the installer didn't see I had the PCI PPC since no default WarpOS was installed.

Any pointers how to further debug?