AROS ABIv11 20230430 Development

[deadwood]

Hi All,

As mentioned in development plan, I'm not moving to next release of ABIv11 based on work done in Q1 2023.

Here is reference ISO: https://axrt.org/development/aros-pc-x86_64-alpha-3.zip
Here is first ISO: https://axrt.org/development/AROS-202304XX-D1-pc-x86_64-boot-iso.zip

The following problems are known issues to be addressed:
- InstallAROS does not install Development directory
- Shutting down in VirtualBox no longer works
- Warm reboot causes crash
- When using SATA, disk names are not automatic pre-filled in InstallAROS blocking installation
- Configuring NVMe disk in VirtualBox causes booting to freeze

Please report regression compared with reference ISO on your hardware. If you have NVMe disk in your hardware, please try if installing on it works using new nvme.device.

Changelog:

Code: [Select]

AROS ABIv11 202304XX-D1 changes:

  Functionalities:
    Implemented network driver for certain nVidia chipsets (Neil)
    Synchronize Zune configuration across all builds (deadwood)
    Restore build and functioning on pc-x86_64 AROS (deadwood)
    Make native kernel more reselient in case of early error (deadwood, Kalamatee)
    Added broadcom4400.device network driver (Neil)
    Synchronize on use of ISO-8859-2 for Polish across all builds (deadwood)
    First working version of nvme.device is available (Kalamatee)
    Implemented FORMAT64 and SEEK64 commands in ahci.device (Kalamatee)
    Stabilized handling of WARM reset, implemented missing shutdown handlers (Kalamatee)
    Requesters add scroll bars if too much text is shown (Kalamatee)

  64-bit support:
    Correct size of fpos_t and ino_t C library types (deadwood)

  68k support:


  ARM support:
    muimaster.library (bugs: MUI_Request not compiling) (deadwood)
    Restore build of armhf AROS (deadwood)

  Updates:
    AROS build system (Kalamatee)
    libz 1.2.13 (Kalamatee)
    libpng 1.6.39 / png.library v53.2 (Kalamatee)
    freetype 2.13.0 / freetype2.library v6.6 (Kalamatee)
    libudis86 (Kalamatee)


  Functional fixes:
    Correctly handle __stdiowin when also using C library (deadwood)
    gl.library (bugs: race condition during initialization) (deadwood)
    hostgl.library (make it work with newer 64-bit hosts) (deadwood)
    exec.library (bugs: wrong disassembly due to wrong start address) (deadwood)
    ata.device (bugs: media insert/eject detection not working) (deadwood)
    muimaster.library (bugs: MUIA_String_Acknowledge not readable) (deadwood)
    png.datatype (bugs: 1-bit APLHA pngs not supported) (deadwood)
    fat-handler (bugs: partition check too strict) (deadwood)
    InstallAROS (bugs: not working with > 2GB RAM) (deadwood)
    dos.library (bugs: SFS not working with > 4GB RAM) (deadwood)
    C:Install-Grub2 (bugs: not working with > 4GB RAM) (deadwood)
    GCC (bugs: sometimes generates non-loadable executables) (deadwood)
    Kernel (bugs: wrong configuration of IRQ pins in IO-APIC) (deadwood)
    Area.mui (bugs: events sent when not expected to) (deadwood)
    pciusb.device (bugs: EeePC USB boot not working) (Neil)
    Register.mui (bugs: tab text cannot be formatted) (deadwood)
    String.mui, Area.mui, Cycle.mui (bugs: setting same value is causing notification) (deadwood)
    pciusb.device (bugs: too long boot delay on AspireOne ZG5) (Neil)
    ntfs-handler (bugs: accessing non existent entries) (Kalamatee)
    DiskInfo (recognize more filesystems) (Kalamatee)
    pciusb.device (workaround for MosChip MCS9990, detect addtional ports) (Kalamatee)
    Kernel (bugs: SSE registers not preserved during interrupt) (Kalamatee)
    timer.device (bugs: can issues interrupt after warm reboot) (Kalamatee)
    C:Decoration (bugs: wrong rendering of paletted pngs) (Kalamatee)

  Stability fixes:
    graphics.library (bugs: boot driver not unregistered correctly) (deadwood)
    MultiView (bugs: crash in About window when using amigaguide.datatype) (deadwood)
    exec.library (bugs: crash when showing disassembly in alert requester) (deadwood)
    Prefs/ScreenMode (bugs: crash on certain drivers) (deadwood)
    acpica.library (deadwood)



[cdimauro]

Just one question: does it support trimming?

[Amiwell]

Meanwhile thanks deadwood do some tests

[AMIGASYSTEM]

deadwood, I did some tests on VMware, ABIv11 is very fast, Wanderer is very fast, all System Applications work fine, these are the anomalies found on VMware which then are the ones already reported for the previous buil.

- Network does not work
- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)
- USB devices must be mounted later after AROS is started (if mounted earlier Wanderer crashes)

[deadwood]

- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)

Thanks for the tests. Is this happening when the video file has it's own icon or when you associate the video file via def_Icon or both?

[AMIGASYSTEM]

I created a comprehensive video where you can see what I described !

https://drive.google.com/file/d/1Uh19B3UWpTBww812pW00I9wIQC12BWgh/view?usp=share_link

[deadwood]

Ok, thanks for the video.

[miker1264]

deadwood, I did some tests on VMware, ABIv11 is very fast, Wanderer is very fast, all System Applications work fine, these are the anomalies found on VMware which then are the ones already reported for the previous buil.

- Network does not work
- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)
- USB devices must be mounted later after AROS is started (if mounted earlier Wanderer crashes)

How do you mount a USB device before AROS starts? Do you mean just attaching the device in VMWare or VirtualBox then starting AROS or trying to use it as a boot device?

I'm not having that problem when I attach the USB device after AROS starts. But I haven't tried to boot from USB.

[AMIGASYSTEM]

I am not talking about Booting from USB, that works fine !

On WMware if you mount the Pendrive on AROS and" leave it mounted", if you reboot "cold", AROS will crash before loading Wanderer

If instead you unmount the pendrive before rebooting, on reboot everything will work

[miker1264]

I am not talking about Booting from USB, that works fine !

On WMware if you mount the Pendrive on AROS and" leave it mounted", if you reboot "cold", AROS will crash before loading Wanderer

If instead you unmount the pendrive before rebooting, on reboot everything will work

Have you tried different USB devices? On VMWare I have left my Philips USB 2.0 drive attached and restarted the VM. It doesn't cause a problem. I will do some more testing to see if I can recreate the freeze you mentioned.

[AMIGASYSTEM]

Yes I have tried several different brand pendrives, even external USB HDs are not seen by AROS ABIv11 if the automount of "WMware and active

With ABIv0 this never happened, and it works regularly even now.

[ncafferkey]

I get a similar problem with USB drives if they are attached to VMware at boot. With one SFS stick (an Icaros installation which I presume 64-bit AROS doesn't try to boot from), Wanderer starts but hangs immediately after showing the desktop. With a FAT stick, Wanderer only hangs after I double-click its icon.

I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.

[AMIGASYSTEM]

I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.

I have two USB ports on the front of the PC, if I connect the Pendrive on the first USB port, the pendrive removes right away.

On the other hand, if I connect the Pendrive on the second USB port, the pendrive is removed after about thirty seconds

On both ports, once the pendrive is removed, if I reinsert it, it is no longer mounted !

[miker1264]

I get a similar problem with USB drives if they are attached to VMware at boot. With one SFS stick (an Icaros installation which I presume 64-bit AROS doesn't try to boot from), Wanderer starts but hangs immediately after showing the desktop. With a FAT stick, Wanderer only hangs after I double-click its icon.

I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.

I have noticed the second problem as well when the mounted volume icon stays on the workbench screen even after it has been removed.

Also, in some cases on ABIv11 icons that are left out on Workbench refuse to be put away. They remain on the workbench screen just like the USB disk icons.

[ncafferkey]

I did some tests with other builds regarding the USB-attached-at-boot bug:

"alpha-1": bad
"alpha-3": bad
2023-03-19 (32-bit ABIv1): good
2023-04-08 (64-bit ABIv1): bad
2023-04-08 (32-bit ABIv1): broken (doesn't boot, even without USB drives)