AROS ABIv0 20201110 Development

[AMIGASYSTEM]

I installed Oracle Extensions Package, nothing has changed, I still get the same Guru Meditation

[AMIGASYSTEM]

On VirtualBox in Native Mode I get the message "Not x86-64 Compatible"

My PC is a DualCore and Windows 7 64Bit 4GB RAM

[deadwood]

That's progress - I get this error too when I set up my virtual machine as 32-bit instead of 64-bit.

[ncafferkey]

Hello,

I revived the native x86_64 ISO on ABIv11 for purpose of checking whether latest kernel fixes some of the reported issues. Please let me know if this ISO behaves better than 20201110 in terms of:

- Reboot/Shutdown (*)
- Working with Acer Aspire / EEEpc (usb boot issues)
- Working with Dell Mini

I don't think the Aspire AA1 or the original EeePC are 64-bit. The same may apply to the Dell Mini. However, the Toshiba netbook that gave me ACPI reboot/shutdown trouble apparently is 64-bit, so I'll try to test your ISO on that.

[AMIGASYSTEM]

Also tested with QEmu, when I edit Grub I get the message of incompatible CPU

[deadwood]

@AMIGASYSTEM

Can you try downloading any 64-bit Linux ISO and check if it works for you under VM?

[AMIGASYSTEM]

On VMware I had installed Mint 21 Mate, I think it is 64Bit, I attach screenshot that should confirm what I said !

My 64Bit Win7 works fine, installed by some me if without experiencing any problems.

Only strange thing, is that on VirtualBox "VT -x/AMD" is disabled.

On VMWare you can enable "VT -x/AMD", but then a request tells me that my Hardware is not supported for this works.

[deadwood]

Ok, fair enough. It looks like there is something about your computer that AROS does not like.

[miker1264]

On VMware I had installed Mint 21 Mate, I think it is 64Bit, I attach screenshot that should confirm what I said !

My 64Bit Win7 works fine, installed by some me if without experiencing any problems.

Only strange thing, is that on VirtualBox "VT -x/AMD" is disabled.

On VMWare you can enable "VT -x/AMD", but then a request tells me that my Hardware is not supported for this works.

Not sure if it helps but for AROS hosted on Linux I had problems with Linux Mint so I switched to Ubuntu. No problems after that.

[AMIGASYSTEM]

miker the problem is not Linux Mint, also because I don't use Linux for AROS, I only use it for testing.

The problem is that my PC does not support ABIv0 20201110 64Bit Virtualization, other 64 Bit virtualizations work fine, that's why I was mentioning Linux Mint

[paolone]

Hello,I revived the native x86_64 ISO on ABIv11 for purpose of checking whether latest kernel fixes some of the reported issues. Please let me know if this ISO behaves better than 20201110 in terms of:- Reboot/Shutdown (*)- Working with Acer Aspire / EEEpc (usb boot issues)- Working with Dell Minihttps://axrt.org/development/aros-pc-x86_64-alpha-1.zip(*) Warm reboot seems to crash VirtualBox, cold and shutdown and ACPI button works for me.

This under latest VMware platform:
- boots ok to Wanderer, no problems so far (good news)
- warm reboot causes a fault which lets the CPU go in shutdown state (regression), hence the VM makes a cold reboot after a VMware warning message.
- cold reboot seems to work correctly (good news)

[deadwood]

Thank paolone

The warm reboot is a known issue.

As for cold reboot and shutdown, does this mean this x86_64 ISO behave "better" in this regard than the 20201110-1 x86 ISO for you?

[deadwood]

I don't think the Aspire AA1 or the original EeePC are 64-bit. The same may apply to the Dell Mini. However, the Toshiba netbook that gave me ACPI reboot/shutdown trouble apparently is 64-bit, so I'll try to test your ISO on that.

Thanks, looking forward to results.

[ncafferkey]

I don't think the Aspire AA1 or the original EeePC are 64-bit. The same may apply to the Dell Mini. However, the Toshiba netbook that gave me ACPI reboot/shutdown trouble apparently is 64-bit, so I'll try to test your ISO on that.

Thanks, looking forward to results.

Unfortunately I can't get it to boot on any real PC. After I select any boot option in GRUB, it always immediately shows a black screen and reboots.

I then suspected the installer wasn't working to install to my USB stick properly. However, it works to install to a virtual HD in VBox. I hope I don't need to burn a CD 

Has anyone else experienced this? Can anyone report success with a real PC?

[ncafferkey]

@AMIGASYSTEM

Thanks, I already located the problem. It might be that Windows formats a bit different and you will never have this problem.

@deadwood

That's correct. Fat32 formatting can be different for each OS. Even Windows 2000 formatted Fat32 differently than more recent OS versions. There used to be a 32GB limit for Fat32 partition size then it became the 128GB limit. There are subtle differences even between Windows versions. It's very possible that Linux formats Fat32 differently. I believe it's called VFat but I'm not sure about that last part.

IIRC those differences in limits are just a choice MS made to discourage people from making huge FAT volumes that are inefficient. The term VFAT refers to the long filename capability introduced with Windows 95 I believe.