SANA2 (uaenet.device) / SLIRP / A2065 (was: WinUAE SANA driver usable?)

[amigafreak68k]

Hi Frode,

just one question:

Is the WinUAE builtin SANAII driver usable in FS-UAE? In WinUAE it is the config option "sana2=true". I tried with "uae_sana2 = true" but can't get it to work in FS-UAE...

best regards

[FrodeSolheim]

No, but with the recent addition of slirp support in WinUAE, I can check if making sana2+ethernet+slirp work in FS-UAE too is relatively painless...

[FrodeSolheim]

Well, I have now made necessary changes to make FS-UAE compile with the slirp mode feature:
https://github.com/FrodeSolheim/fs-u...f7002bccb27540

I've not even tested it yet, but the code is there on github if someone wants to try

[amigafreak68k]

Great!

What's to write in the config to use this feature?

[FrodeSolheim]

Hmm, well, it would be the same as for WinUAE (prefixed for uae_*), haven't checked yet

[amigafreak68k]

Originally Posted by FrodeSolheim

• Added slirp support (not tested yet, not enabled by default).

I'd tested this in the newest beta build, but can't get it to start...

I'd tried it in WinUAE with the same config options. ShowConfig had list the network card but in FS-UAE it doesn't.

I used the config options

uae_a2065 = slirp_inbound
uae_sana2 = true


in FS-UAE. I searched for the FS-UAE.log to attach here but can't find it

[FrodeSolheim]

Originally Posted by amigafreak68k

ShowConfig had list the network card but in FS-UAE it doesn't. I used the config options:
uae_a2065 = slirp_inbound
uae_sana2 = true

Hi, the slirp code didn't compile for 64-bit targets, so the a2065/slirp/uaenet.device features were completely disabled in 2.5.6dev.

I have since then updated the slirp code to work for 64-bit builds too (code will be pushed to git soon), and re-enabled those features by default.

However, it still does not seem to work properly, in fact, uaenet.device currently crashes FS-UAE when it is used...

[amigafreak68k]

I thought the Mac-build would be 32bit?

[FrodeSolheim]

Originally Posted by amigafreak68k

I thought the Mac-build would be 32bit?

And indeed it is -But it was quicker to disable it generally for 2.5.6dev so 64-bit builds didn't fail, rather than enabling it depending on platform. After all, I planned to update the slirp code anyway.

Anyway, it is re-enabled now by the following commits:
https://github.com/FrodeSolheim/fs-u...c563e136387f6e
https://github.com/FrodeSolheim/fs-u...2c0930ba94d6ff

I still need to dig into the code and figure out why it crashes (well, actually I know why it crashes, it is a null pointer dereference, but I need to study the code to figure out if/why it works in WinUAE )

[FrodeSolheim]

There has been some progress; A2065 works partially (MiamiInit, DNS lookup seems to work, something wrong with TCP connections though).

[amigafreak68k]

Yes! I get the same results on Mac OS X.

The emulated Amiga should visible in the network devices list of my Internet router but doesn't. Maybe FS-UAE not really takling to the router...

I use Genesis from Amiga OS 3.9

[FrodeSolheim]

The Amiga wouldn't show up on your Internet router anyway when using slirp mode, because it is NATed through FS-UAE / the host.

I have sniffed the traffic (on the host computer) using wireshark, and I can see the DNS lookup going through and back, and a TCP connection initiated using AmiIRC. Welcome message from IRC server is received on the host, but does not reach AmiIRC. I haven't found the issue yet (and I'm not looking right now :-/).

[amigafreak68k]

Maybe Toni Wilen have a solution on this?

[FrodeSolheim]

Originally Posted by amigafreak68k

Maybe Toni Wilen have a solution on this?

No, I'm afraid not. Toni cannot know what I have (potentially) done with the source code. For all he know I have just messed up (that could actually be true anyway).

It is possible the problem is related to the patch I borrowed from QEmu for 64-bit support (i.e. the code wasn't compatible enough before applying the patch). So the first order of business is to revert that and try exclusively with a 32-bit build. If that works, there's probably something with the 64-bit patch.

(Other options include get WinUAE compiling in a virtual machine and compare WinUAE and FS-UAE with a debugger while using slirp, and another option is to try to get FS-UAE working with fully updated slirp code from Qemu).

[amigafreak68k]

Oh my god, what a outlay! In this case this feature (for me) isn't that important! Don't spend time on this until it will be more important for others (or you)

[FrodeSolheim]

Test for amigafreak68k

OS X version of FS-UAE with QEMU-UAE slirp support: http://fs-uae.net/devel/2.5.17slirp/
Requires special version of QEMU-UAE plugin: http://fs-uae.net/devel/plugins/qemu...osx-x86.tar.gz

To enable, for now use:

uae_a2065 = slirp

This enables A2065 emulation - which works

There's also SANA2 (uaenet), but last I checked this crashed:

uae_sana2 = true

[amigafreak68k]

....downloading right now!

[amigafreak68k]

First Test with my AmigaOS 4.1 setup = Emulation (PPC) crashes -> light green screen. (See log)

Now testing with AmigaOS 3.9...

Edit:

In AmigaOS 3.9 with activated slirp option there doesn't run anymore any "ReAction"-Application. Also Wallpapers aren't loaded. With normal 2.1.17 no problem!

[FrodeSolheim]

@amigafreak68k thanks for testing. I have only tested the feature briefly myself due to limited time available. I have only tested A2065 / slirp by itself (WB 3.1 + Miami + AmiIRC), and also checked that the AmigaOS 4.1 installer still boots with the new QEMU-UAE version.

When you say you tested with your AmigaOS 4.1 setup and that it crashes, do you mean that stuff that worked before stopped working now? Or that it crashes when you try to use A2065 in AmigaOS 4.1?

[amigafreak68k]

No. AmigaOS 4.1 setup doesn't boot. After Rainbow Colours -> Pink screen -> green screen -> HALT

This isn't, if I disabel slirp option