AROS ABIv0 20201110 Development

[AMIGASYSTEM]

Thanks Contrib now everything is unpacked and correctly.

I integrated D14 on AROS One, provisionally just to be able to work, I replaced the "png.datatypes" with that of D10 to display DualPNG Icons correctly, then I anco replaced "Screenmode" with that of D7.

I couldn't figure out why Amistart doesn't work, I think it's something about some important library

I forgot, now with D14 on Wanderer you can move files and delete "orphan" icons of files and folders

I modified the Descriptor of webp.datatype, now "webp" image files will be recognized even without extension.

[ncafferkey]

@ncafferkey

If I can reproduce these USB problems on hardware I have, there is a change they will be fixed. Can you tell me what kind of USB 1.1 these are? OHCI or UHCI?

They are both Intel EHCI/UHCI. The one that doesn't recognise drives at all has an ICH6 chipset, while the one that just has a delay in seeing drives is ICH7M.

[AMIGASYSTEM]

ncafferkey, I don't know if I understood correctly, on my AROS One z5 I don't have this problem, after the black screen Wnderer starts, without appearing "cat eyes".

Maybe otre could depend that I have the internal SD "dead", or by type of Pendrive, i used one 4GB and one 8GB

Tested D4, D7 and D10, the second Pendrive inserted on Wandere also appears quickly, and is quickly ejected

[cavemann]

I'm still having problems with a division by zero error in screenmode when I go native with my nvidia 9500.
Also my nvidia 8400 is recognized  as  vga 4-bit. I945 boots normal.  Any suggestions? Do have to replace
screenmode?

[ncafferkey]

ncafferkey, I don't know if I understood correctly, on my AROS One z5 I don't have this problem, after the black screen Wnderer starts, without appearing "cat eyes".

Maybe otre could depend that I have the internal SD "dead", or by type of Pendrive, i used one 4GB and one 8GB

Tested D4, D7 and D10, the second Pendrive inserted on Wandere also appears quickly, and is quickly ejected

I did try two different types of USB stick, in case that was the problem. Just now I also wrote the 2019-01-21 ABIv0 nightly build to the same stick I've been using for Deadwood's recent builds, and the problem went away, so I don't think the model of stick I'm using is the problem.

Could you try with the option ATA=nopci,nolegacy? I need to use that option to avoid booting from my SSD.

[AMIGASYSTEM]

I did the test with Acer One z5, D14 and the option ATA=nopci,nolegacy

- Native mode, cat eyes appear and then wanderer starts up
- VESA mode, it starts wanderer directly

[ncafferkey]

I did the test with Acer One z5, D14 and the option ATA=nopci,nolegacy

- Native mode, cat eyes appear and then wanderer starts up
- VESA mode, it starts wanderer directly

Thanks, very interesting. Maybe without that option AROS is kept busy poking around at your broken SSD and by the time it gives up, the USB stick is visible.

I don't know why the graphics driver would make a difference though. If you have time, could you try these tests three times each to see if the behaviour is consistent?

[AMIGASYSTEM]

Tried several times, on all 3 USB ports, and the result does not change, cat's eyes appear only in native mode.

I assume with VESA it doesn't happen because I don't have to search or initialize the Video Card.

[AMIGASYSTEM]

Discovered something interesting, in default "multiboot /Arch/pc/bootstrap.gz ATA=32bit", if a Wireless USB Mouse and also connected on ACER One z5, the cat eyes appear both n native and VESA mode.

On your Acer is anything else connected on a USB port ?

[deadwood]

I'm still having problems with a division by zero error in screenmode when I go native with my nvidia 9500.
Also my nvidia 8400 is recognized  as  vga 4-bit. I945 boots normal.  Any suggestions? Do have to replace
screenmode?

Prefs/ScreenMode will be fixed in one of next builds.

You nVidia card: did it work with the reference release or any previous Dx builds?

[paolone]

Also, ACPI reboot? I know this could be tricky if some machines or VMs have always behaved badly with ACPI reboot/shutdown (although I don't think this is known definitively yet), but it could become a common complaint (e.g. from new AROS users), especially if popular VMs like VMWare have this problem.

While the ACPI reboot issue is being fixed, wouldn't be possible to turn back to "traditional" reset routine for cold reboot? Unless there are some filesystem related safety reasons involved, at least it worked fine.

[deadwood]

Also, ACPI reboot? I know this could be tricky if some machines or VMs have always behaved badly with ACPI reboot/shutdown (although I don't think this is known definitively yet), but it could become a common complaint (e.g. from new AROS users), especially if popular VMs like VMWare have this problem.

While the ACPI reboot issue is being fixed, wouldn't be possible to turn back to "traditional" reset routine for cold reboot? Unless there are some filesystem related safety reasons involved, at least it worked fine.

When I understand how these things work, I might be able to suggest a workaround. For the time being the only thing that comes to my mind is trying how things work with 'noacpi' boot parameter.

[ncafferkey]

Discovered something interesting, in default "multiboot /Arch/pc/bootstrap.gz ATA=32bit", if a Wireless USB Mouse and also connected on ACER One z5, the cat eyes appear both n native and VESA mode.

On your Acer is anything else connected on a USB port ?

No external devices, but I think the built-in webcam is on USB. I sometimes get messages after boot has completed about the webcam being disconnected, so the connection may be intermittent.

Does your webcam appear in the device list in Trident?

[AMIGASYSTEM]

Yes Trident sees the WebCam, see screenshot, I however have never had any messages, of course I only use AROS on PenDrive or External USB Hardisk.

[cavemann]

I'm still having problems with a division by zero error in screenmode when I go native with my nvidia 9500.
Also my nvidia 8400 is recognized  as  vga 4-bit. I945 boots normal.  Any suggestions? Do have to replace
screenmode?

Prefs/ScreenMode will be fixed in one of next builds.

You nVidia card: did it work with the reference release or any previous Dx builds?

gforce9500 worked with D7'
gforce8400 boots as vga for some reason, (used to run very good years ago)
.
thanx