AROS 64-bit 20250418 Support Thread: AROS FORUMS

AROS 64-bit 20250418 Support Thread

Last updated on 3 hours ago

Track thread Print

deadwoodAROS Dev

Posted 4 months ago

#61

Glad it worked for you. Yes, correct - native drivers except for vmware are disabled in this initial release.

ntromansSenior Member

Posted 4 months ago

#62

Next test - HP Elitebook 8470p (i5 processor);. 64 bit boots from CD* if safe mode 2 is used, although it is possible to remove the 'nodma' and 'debug' entries and boot. I also set vesa=1024x768 to get a decent screen.

Audio works (hdaudio) as does SATA and USB. Unfortunatetly its wired ethernet is not a supported by AROS so I'm anabe to test there. Graphics are VESA under 32 bit too. Anyway, looking really good :-).

Cheers,
Nigel.

*For anyone else with this machine, it's a bit awkward to get it booting AROS from the optical drive - you need to set the bios boot options to not fastboot and drive mode IDE rater thn AHCI. To boot from hard-drive these need to go back to AHCI and can use fastboot.

ntromansSenior Member

Posted 4 months ago

#63

An observation from my HP desktop installation; I've tried changing the grub entry to vesa=1920x1080 (this is the resolution AROS 32 bit native is set to) but 64 bit refuses to give this, defaulting back to 1280x1024. Is this as expected?

Cheers,
Nigel.

P.S. dual boot 32/64 bit is working fine; the only odd thing is that 32 bit AROS cannot 'see' the sys: partitionj for 64 bit. All other partitions can be seen by both 32 and 64 bit AROS.

deadwoodAROS Dev

Posted 4 months ago

#64

ntromans wrote:

@ntromans - An observation from my HP desktop installation; I've tried changing the grub entry to vesa=1920x1080 (this is the resolution AROS 32 bit native is set to) but 64 bit refuses to give this, defaulting back to 1280x1024. Is this as expected?

No it's not expected. Try setting "standard" resolutions between 1280x1024 and 1920x1080 or resolutions like 800x600 to make sure your syntax is correct.

deadwoodAROS Dev

Posted 4 months ago

#65

@Farox, @AMIGASYSTEM

This try this update. It should:

- stop VMWare driver from crashing on your CPU's so that you can use "Default" option in Grub
- stop GL from crashing when being used (i.e. boy demo)

https://axrt.org/development/UPD20250608.zip

If you still get a crash, please post a screen shot of crash requester.

2 users reacted to this post

retrofaza, Farox

AMIGASYSTEMDistro Maintainer

Posted 4 months ago

#66

Perfect! Now WMware starts in native mode even on my Win7 64Bit, and the Boy demo works well too!
Thanks, deadwood!

AROS One All Thread
AROS One Home Site
AROS One Facebook

You do not have access to view attachments

ntromansSenior Member

Posted 4 months ago

#67

deadwood wrote:

@deadwood -
ntromans wrote:
@ntromans - An observation from my HP desktop installation; I've tried changing the grub entry to vesa=1920x1080 (this is the resolution AROS 32 bit native is set to) but 64 bit refuses to give this, defaulting back to 1280x1024. Is this as expected?

No it's not expected. Try setting "standard" resolutions between 1280x1024 and 1920x1080 or resolutions like 800x600 to make sure your syntax is correct.

The syntax is correct, I can set 800x600 but not 1440x900, 1680x1050 or 1920x1080, all avaialble from the 32 bit native driver. However, I've just tried this with 32 bit and it's VESA modes show exactly the same behaviour, i.e. nothing above 1280x1024. The graphics card is a GeForce 8400 and output is via HDMI if that's of any use.

Cheers,
Nigel.

deadwoodAROS Dev

Posted 4 months ago

#68

ntromans wrote:

@ntromans I've just tried this with 32 bit and it's VESA modes show exactly the same behaviour, i.e. nothing above 1280x1024. The graphics card is a GeForce 8400 and output is via HDMI if that's of any use.

Cheers,
Nigel.

Ok, so what you are saying is that native driver works up to 1980x but VESA in both 32-bit and 64-bit works only up to 1280x, correct?

Yes, that's possible. Basically card reports supported resolutions back to BIOS in VESA mode and it's possible that the card simply reports only up to 1280x for VESA and needs native driver for higher resolutions.

1 user reacted to this post

ntromans

deadwoodAROS Dev

Posted 4 months ago

#69

@AMIGASYSTEM

Ok, great to see that this long-standing issues has been solved for you.

FaroxMember

Posted 4 months ago

#70

Thanks a lot @deadwood now my PC start in "default" mode without problems.
But when i run Boy, the demo start fine with music but after some seconds freeze the entire system.
Tryed also on Hosted mode on the same PC with your updated files (maybe is not ideal...but i made a backup just in case), and the demo segfault ...see screen attached.

You do not have access to view attachments

deadwoodAROS Dev

Posted 4 months ago

#71

@Farox

Can you show me scren shot of the error requester under hosted or use gdb to capture segfault and show me whole backtrace after loadbt + bt?

EDIT: can you also try different OpenGL software and check it is stable for you?

Edited by deadwood on 09-06-2025 00:27, 4 months ago

AMIGASYSTEMDistro Maintainer

Posted 4 months ago

#72

deadwood wrote:

@deadwood - @AMIGASYSTEM

Ok, great to see that this long-standing issues has been solved for you.

Yes, thank you, problem solved. The “Boy” demo works well on both native VMware and VMware Hosted Linux.

AROS One All Thread
AROS One Home Site
AROS One Facebook

FaroxMember

Posted 4 months ago

#73

deadwood wrote:

@deadwood - @Farox

Can you show me scren shot of the error requester under hosted or use gdb to capture segfault and show me whole backtrace after loadbt + bt?

EDIT: can you also try different OpenGL software and check it is stable for you?

Ok sorry for late reply...just returned from work.
Here the shot of error requester under hosted...and the log from gdb..don't know if usefull (maybe we need the demo compiled with debug to have more infos).
Later i'll try another GL software.
Thanks

Edited by Farox on 09-06-2025 13:12, 4 months ago

You do not have access to view attachments

deadwoodAROS Dev

Posted 4 months ago

#74

Looks like you have two different issues. Error requester from AROS talks about null pointer access in stdlib.library while the gdb trace still shows "illegal instruction" in gallium.hidd. Are you sure update has been applied on that hosted build?

FaroxMember

Posted 4 months ago

#75

deadwood wrote:

@deadwood - Looks like you have two different issues. Error requester from AROS talks about null pointer access in stdlib.library while the gdb trace still shows "illegal instruction" in gallium.hidd. Are you sure update has been applied on that hosted build?

Ops Sorry...error requester is from Aros (64bit non debug) where i applied the update, the others shots are from Aros 64bit Debug where i forgot to apply the update..

Now the shots..nr 06 and 07 are from debug session with applied updated files.
Shots _e1 and _e2 are from non-debug session (just in case you need it).

You do not have access to view attachments

deadwoodAROS Dev

Posted 4 months ago

#76

Ok, I'd need symbols loaded. Please use 64-bit debug version with update applied. Once you get SIGSEV (shot06.png), do:

'loadbt'

once symbols are loaded (as seen on shot7.png) please do

'bt'

and take the screenshot

deadwoodAROS Dev

Posted 4 months ago

#77

@Farox

I though of two more things to check:

a) on native, double the amount of stack on the icon and check if this stops freezes
b) on hosted, be sure to add more memory then standard: ./boot/linux/AROSBootstrap -m 640

1 user reacted to this post

Farox

Amiwell79Distro Maintainer

Posted 4 months ago

#78

ntromans wrote:

@ntromans -
deadwood wrote:
@deadwood -
ntromans wrote:
@ntromans - An observation from my HP desktop installation; I've tried changing the grub entry to vesa=1920x1080 (this is the resolution AROS 32 bit native is set to) but 64 bit refuses to give this, defaulting back to 1280x1024. Is this as expected?

No it's not expected. Try setting "standard" resolutions between 1280x1024 and 1920x1080 or resolutions like 800x600 to make sure your syntax is correct.

The syntax is correct, I can set 800x600 but not 1440x900, 1680x1050 or 1920x1080, all avaialble from the 32 bit native driver. However, I've just tried this with 32 bit and it's VESA modes show exactly the same behaviour, i.e. nothing above 1280x1024. The graphics card is a GeForce 8400 and output is via HDMI if that's of any use.

Cheers,
Nigel.

try to check your available vesa resolutions with the vbeinfo command from grub

FaroxMember

Posted 4 months ago

#79

deadwood wrote:

@deadwood - @Farox

I though of two more things to check:

a) on native, double the amount of stack on the icon and check if this stops freezes
b) on hosted, be sure to add more memory then standard: ./boot/linux/AROSBootstrap -m 640

Thanks on hosted added -m 640 and it run without problems

, on native i'll have to check.
Also this is the shots on hosted debug just in case you see something else.

You do not have access to view attachments

FaroxMember

Posted 4 months ago

#80

OK tested on native and after i put a stack of 262144 i could run "Boy" "Stercus Accidit" and "Dose2".
What i miss from the 32 bit is the error message from the system that appear when the stack is too low.
Don't know if could be added.

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.

Moderator: Administrator, Moderators

Users who participated in discussion: amigamia, serk118uk, nikos, deadwood, AMIGASYSTEM, ntromans, retrofaza, Amiwell79, mattson62, akapcha, Jeff1138, Farox, ncafferkey, olivier2222

Search AROSWorld

AROS 64-bit 20250418 Support Thread