AROS ABIv0 20201110 Development

[Devlin]

Apologies if you have already tried this, bue have you tried not starting netwoork automatically at boot but starting it manually via 'startnet'? One thing you might also try - issue startnet, stopnet and then startnet again; for me this has helped with a reluctant internet connection, albeit for wifi rather than ethernet.

Cheers,
Nigel.

Tried, to no avail.

AROSTCP is not at fault here, it is, by all means, working perfectly.

I'm pretty much convinced that the driver is the culprit here. It's missing a way to bring the network card out of suspend mode when initialising it.

The fact that it works when I use PXEboot(network boot) or another OS that wakes up the network first is a big indicator of that.

If I had access to my dev environment (main PC is presently busted and laptop is *not* up to the task) I'd have a go at trying to fix it myself.

[miker1264]

Apologies if you have already tried this, bue have you tried not starting netwoork automatically at boot but starting it manually via 'startnet'? One thing you might also try - issue startnet, stopnet and then startnet again; for me this has helped with a reluctant internet connection, albeit for wifi rather than ethernet.

Cheers,
Nigel.

Tried, to no avail.

AROSTCP is not at fault here, it is, by all means, working perfectly.

I'm pretty much convinced that the driver is the culprit here. It's missing a way to bring the network card out of suspend mode when initialising it.

The fact that it works when I use PXEboot(network boot) or another OS that wakes up the network first is a big indicator of that.

If I had access to my dev environment (main PC is presently busted and laptop is *not* up to the task) I'd have a go at trying to fix it myself.

Neil recently wrote a network driver. Maybe he could give some insight into what may be the problem and how to fix it.

This was the topic if you do a search...

"AROS fully supported on NVidia based motherboard"

[Devlin]

Neil recently wrote a network driver. Maybe he could give some insight into what may be the problem and how to fix it.

This was the topic if you do a search...

"AROS fully supported on NVidia based motherboard"

I've sent a PM to Neil on the forum, hopefully he can help?

[AMIGASYSTEM]

deadwood, I tested your latest Bulit, and found that the Pointer Prefs does not work, basically it does not allow to set and save the Pointer !

The latest build tested is "pc-i386-20230702-163909.tar.gz"

With Build "AROS-20201110-2-pc-i386-boot-iso" the Pointer Prefs worked fine !

Thanks, I'll investigate.

The mentioned Pointer problem, also happens on the latest version of ABIv1 "AROS-20230710-pc-i386-boot-iso.zipper"

[deadwood]

Please check this build: https://axrt.org/development/Pointer_20230716.zip

Let me know if problems with Prefs/Pointer are solved.

[terminills]

From my tinkering it seems it's down to dhclient not managing to get an IP, failing silently and nowhere actually saying "hey this failed" and letting the user (aka me) know that it done goofed and isn't working.

To see the output for wifi, don't start networking on boot but from the shell:

execute sys:system/network/arostcp/s/startnet

c:wirelessmanager atheros5000.device verbose

(assuming wifi device is atheros).

The 'verbose' option will give lots of information on the progess (or not) with setting up the wifi connection.

By the way, if you are having trouble with wifi have you tried setting fixed IPs rather than DHCP?

Cheers,
Nigel.

Not WiFi. Ethernet, it's the built in stuff on my dell wyse - it should afaict run just fine by way of using rtl8169.device, but it never seems to get an ip address and if i set it manually it just throws packets into the void and they never go anywhere or get received by anything. Tried three known good network leads just to rule it out.

Someone can correct me if I'm wrong but the 8168.device is actually the more advanced driver as they both are based off the Linux code and the same applies.  8168 is the Realtek provided source and the 8169 would be the older out of tree driver.

[deadwood]

@AMIGASYSTEM

Were you able to validate fixes to Prefs/Pointer?

[AMIGASYSTEM]

Sorry deadwood, I had missed your post (I stay many hours at the sea in the cool wind, in my region it's hot some cities get up to 43 degrees, my city is cooler thanks to the ubiquitous Mistral sea wind

https://www.ilmeteo.it/Puglia

Tested the Fix now, the Pointer works fine, I tried to replace several of my PNG fonts and they work pefectly, see screenshot !

[deadwood]

Have you also tried setting up Busy pointer? Does that work as well?

[AMIGASYSTEM]

Sorry for the delay, yes Busy Pointer works well, question is gif anim support possible, so that you can have Pointer and Busy Pointer animated ?

[deadwood]

Thanks for confirming. I don't know about animated cursor capabilities.

[AMIGASYSTEM]

I noticed that with OWB there is suppoto on a kind of animated Busy Pointer during the "waiting" search, see screenshot !

[ntromans]

As noted over on this thread (https://ae.amigalife.org/index.php?topic=1155.msg17153#new) AROS's VNC client crashes when you attempt to connect. This both from RPi to AROS (as tested bu gkb) and also AROS to AROS (tested by myself using the AmigaOne 2.1 distro). Error message is attached.

Cheers,
Nigel.

[deadwood]

I assume this client was working at some point. What system version / distribution it was working last?

[AMIGASYSTEM]

deadwood with the same Binary, the GURU also appears with old Buid, at least this happens with Virtual Machines, with Native AROS on PC, the PC reboots !