Then it must be somehow triggered by something in your hardware. I so far tested extensivelly on QEMU, VMWARE and VBox and never had an issue. Next month I might be doing more tests on real hardware - maybe one of my boards will also trigger this problem.
deadwood I don't think it's a hardware problem, I used the "z1.library" of the Hosted Linux version with Native AROS on VMware, and no Guru appeared on OWB.
Also on the same PC, same WMware, with Hosted linux, on OWB I got no Guru.
I have tested the "Z1.library" included in the Build linux-x86_64-20250214-010509, the error on the "Z1.library" has returned, the error appears just after a short while you use OWB !
deadwood, found another annoying Bug, this happens on both Linux Hosted and Native on VMware
If you unzip an LHA Archive, ZIP etc. into RAM, once you do something in the contents of the archive, a Guru appears, see attached video !
- If the LHA Archive, ZIP etc.. is unpacked on the Hardisk and the same procedure is performed no guru appears
- If the contents of the archive are instead copied to RAM also in this circumstance no Guru appears
- Basically the Guru only appears if the archive is unpacked directly into RAM!
20250206-64D11-P02:
- improved version of e1000.device that works in Qemu, VMWare and VirtualBox. Was not tested on real hardware but should work there as well.
FYI, I will be looking into vmware video driver next. It looks like it already works correctly on VMWARE 16, but fails to change resolution under VirtualBox. If you notice any other problem on either VMWARE or VirtualBox, let me know.
- DiskImage does not support ISO Images, see screenshot (this happens on 64it and 32Bit, but also happened with older builds)
- If you copy ICD0, ICD1, IDF0, IDF1,IPC0, IPC1, ISO0 from Storage/DOSDrivers to Devs/DOSDrivers, AROS will not start and show GURU, this only happens on 64Bit, see screenshot
Changes:
- vmware video driver now allows changing resolution on both VMWare and VirtualBox
- performance of vmware video driver improved to the level of VESA driver
deadwood if the resolution change on VMware is for the Mode you are referring to "Native Graphics" Mode, I cannot verify this because I get a Guru on IntelGMA at startup
Also if I try to click on the Monitor Icon I get a Guru, see screenshot
Unfortunatelly it's not possible to start a native driver once the hardware has been initialized in VESA mode.
With regards to IntelGMA - if it give you problems, then just delete it from DEVS:Monitors. I tested booting with vmware driver on both VMWARE 16 and VirtualBox and didn't experience any issues with IntelGMA.
- If in SYS:Devs/Monitors, I use only DosDriver + the icon I get a Guru on WMware, see screenshot
- If in SYS:Devs/Monitors, I use only DosDriver without the icon Wanderer I get screen a 4 Colours
On PC I use VMmare 12, for verification I will also try with 16
- I report another bug, if you rename the Volume DH0, afterwards you can no longer rename the volume (Device or Unmounted Volume)
@AMIGASYSTEM - - If in SYS:Devs/Monitors, I use only DosDriver + the icon I get a Guru on WMware, see screenshot
- If in SYS:Devs/Monitors, I use only DosDriver without the icon Wanderer I get screen a 4 Colours
I'm sorry I don't understand. The updated driver goes into DEVS:Drivers (the same path as in the patch archive). Then you select "Native" in the grub menu. As mentioned before, don't try starting the driver from icon after you booted into VESA.
Edited by amigamia on 24-02-2025 07:48, 2 months ago
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.
AMIGASYSTEMDistro Maintainer