AROS ABIv0 20201110 Development

[Jeff1138]

@devlin

AMD only, really, open sourced after the nouveau was done in 2012 (thanks deadwood) but we have so few developers now that it takes time.
Have the same Dell Wyse machine, nice but slow but that does not bother me

As you have an atom based HD2 does the nouveau driver (GT218) works on this well? How does the rest of the HD2 function? Is it with a recent AROS distro?

Regards
Jeff

[deadwood]

@AMIGASYSTEM

Thanks for the link. I think I also saw AfA directly in AROS repository. Will have to investigate.

[miker1264]

@AMIGASYSTEM

Thanks for the link. I think I also saw AfA directly in AROS repository. Will have to investigate.

I took a look at the AfA OS 4.3 sources and it's very interesting. It seems to be compiled with DevCPP (.dev).

Some of it is AmiBlitz? 

Bern Roesch and the others who contributed did some good work on AfA OS.

AMIGASYSTEM

I already have a full installation of AfA OS with OS3.9 on HDF. It has already been installed and ready for WinUAE.

I'll try it out as far as themes (skins).

Also the skins are located in the lha archive from Aminet. Lots of good looking themes there.

[Devlin]

@devlin

AMD only, really, open sourced after the nouveau was done in 2012 (thanks deadwood) but we have so few developers now that it takes time.
Have the same Dell Wyse machine, nice but slow but that does not bother me

As you have an atom based HD2 does the nouveau driver (GT218) works on this well? How does the rest of the HD2 function? Is it with a recent AROS distro?

Regards
Jeff

Sound is good.
Network is functional and useable (I know there's no support for the internal wifi)
3D accel works fine (the gt218 is not particularly fast though)
My 3D test is to run OpenJK(Jedi Academy) and see how it performs as I'm familiar with it, and it constitutes for me a "real world" workload.
HD2 gets about 15-30fps(trending typically higher) in 800x600
ACPI//power control is bugged though. have to force-power off the machine when shutting down on the HD2.

I did notice on the dell/wyse machine that I couldn't get the network to start properly.
Which driver should I use for the network card? (is r8111 chip iirc)

[AMIGASYSTEM]

I already have a full installation of AfA OS with OS3.9 on HDF. It has already been installed and ready for WinUAE.

I'll try it out as far as themes (skins).

Also the skins are located in the lha archive from Aminet. Lots of good looking themes there.

Probably your AfA OS on HardFile is my AfA One that I deployed qaululche years ago, if that's the one you will find all the themes, including the ones I created, In any case some themes you can find them also here:

https://amiga-look.org/taxonomy/term/7

[Jeff1138]

@devlin

Great that the HD2 works so well, the driver for the dell is rtl8169

Regards
Jeff

[Devlin]

@devlin

Great that the HD2 works so well, the driver for the dell is rtl8169

Regards
Jeff

Network's being rude, driver appears to be loading successfully but not doing anything else after that. (it's probably dns)
Any way to get some kind of verbose logging so I know exactly wtf is happening?
Dell WYSE box would be a perfect aros candidate *if* there was an up-to-date radeon driver for it.

[Jeff1138]

@devlin

AROS usually has a few options to get output, not sure it help with networking issues though


Native debugging tools for AROS

to enable debugging at boot time entering the GRUB menu editing line (E key) and adding "debug=memory" to your boot line, then press Ctrl+X to complete booting.


Open a shell and enter the line below to run Biftek and grab the debug messages collected in RAM into a text file.

tools/debug/bifteck > ram:debug.txt

and certainly does not open a window. It is a shell tool and only dumps data located from the debug location. It is therefore important to 'catch' that debug data as soon as possible (before it gets overridden). You should invoke bifteck at the first opportunity before doing anything else. You can use the TO option to store bifteck output to a file or you can pipe it manually to a file.




Another suggestion is to do a bug() debugging. Each time bug() is executed it will be output on sashimi. You include <aros/debug.h> and place bug("something\n"); in your source code at location though which control passes.

To get the output - open an aros shell

SYS:Tools/Debug/sashimi > RAM:out.txt

Regards
Jeff

[Devlin]

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.

[ntromans]

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.

[Devlin]

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.

[ntromans]

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.

Oh, OK - unusual for ethernet not to work if there's supported hardware in the machine. It doesn't even respond to a ping? Stupid question - when setting the manual IP I presume that did include gateway and DNS?

Cheers,
Nigel.

[Jeff1138]

@devlin

Last things you could consider, what distro did you decide to use on the Z90D7 (is there a regression?) and the pull out tab should give the year of manufacturing

Tests that can be undertaken to determine correct settings and functions

 ping <router-address> e.g. 192.168.0.1 (aka inet) or 80.237.146.33 (www.amiganews.de)
 ifconfig net0
 ifconfig net0 up
sanautil -d rtl8169.device status


Lower part of IPv4 tab covers the router information

    IP Mode Get address from DHCP

or if manual settings

    Gateway (IP Address of router) = usually 192.168.0.1 or 192.168.1.1 but see router manual to make sure.
    first DNS = use 208.67.222.222 (opendns) or 212.50.160.100
    second DNS = use 208.67.220.220 (opendns) or 213.249.130.100


Sadly just ideas now, still puzzled why it is not working

Regards
Jeff

[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 !

[miker1264]

For some reason as far back as Icaros 2.2 Restart AROS worked. But for recent builds Restart AROS goes directly to shutdown. It doesn't restart automatically.

When testing themes for example it's easier to have AROS do the work by restarting than continually pushing the power button.