AROS World Exec
Development => Development (General) => Topic started by: deadwood on March 20, 2022, 04:43:11 AM
-
Hi All,
A new release of ABIv11 x86_64 is now available, containing improvements and fixes that happened since beginning of year.
You can downloaded it from here (bottom of page): https://axrt.org/downloads-aros
Below you will find release notes. For developers, please pay special attention to changes around struct MsgPort. It is advised that you update your SDKs/build environments.
Release notes:
AROS ABIv11 20220318-1 changes:
Breaking changes:
Align size of struct MsgPort with SMP builds. (deadwood)
https://github.com/deadw00d/AROS/commit/b9bc67accce27db0e2cc0f79f554dc76e9b17a73
Note that this change impact structures that embed struct MsgPort
in them, for example struct Process. Impact on applications depend
on whether they access fields of impact structures. Test of
currently available applications indicate they are not impacted.
Functionalities:
Don't go into infinite crash loop on critical error (deadwood)
Unit test extended to allow easy compilation for AmigaOS (deadwood)
Freeze 32-bit time structures where possible (deadwood)
Design and documentation of 64-bit time support (deadwood)
Prioritize 64-bit addreess memory over 32-bit (deadwood)
64-bit support:
Fix in NList (deadwood)
Allow loading of executables compiled in small code model (deadwood)
Updates:
AROS Build System (deadwood)
Add patchelf command (deadwood)
Fixes:
C library (bugs: #52, crash at expunge) (deadwood)
muimaster.library (bugs: #51, #53, #62, ) (deadwood)
debug-handler (deadwood)
reqtools.library (bugs: #50) (deadwood)
p96gfx.hidd (bugs: switch match to gfx card mode) (deadwood)
webp.datatype (bugs: crash when using Multiview) (deadwood)
png.datatype (bugs: wrong rendering of png icons) (deadwood)
intuition.library (bugs: wrong compilation for SMP build) (deadwood)
StackSnoop (deadwood)
dos.library (bugs: #60) (deadwood)
utility.library (bugs: #63) (deadwood)
debug.library (bugs: wrong adresses in 64-bit mode) (deadwood)
-
@deadwood: may I suggest to increase the version number when backward-incompatible changes are introduced? Something like ABIv12, for example.
-
@deadwood
s this new AROS ABIv11 version only available for Linux?
On my Thread "AROS One x86 Work In Progress" I had asked if AROS can be installed in "TRI-BOOT", I was asked by a user, according to you is it possible to do it ?
-
@deadwood: may I suggest to increase the version number when backward-incompatible changes are introduced? Something like ABIv12, for example.
That's something that I want to reserve in case of changes that have a more severe and wide spread effects. The basis idea though it not to introduce such changes at all.
-
I see a link for hosted but not standalone. Am I mistaken?
btw I read this;
" This is initial release of AROS ABIv11 x86_64 bringing more than 25 years of AROS development to 64-bit environment with stable ABI."
What a fantastic milestone statement!!
-
I see a link for hosted but not standalone. Am I mistaken?
That's correct.
" This is initial release of AROS ABIv11 x86_64 bringing more than 25 years of AROS development to 64-bit environment with stable ABI."
What a fantastic milestone statement!!
Combined work of generations of AROS developers led us to this point ;)
-
Some corrections:
download link has changed into: https://axrt.org/downloads-aros
However, on that page (caption: AROS ABIv11) there you can read:Source Code: GitHub See the README for more information on installing and using AxRuntime.
Which could work confusing (especially for those not familiar with your work deadwood) as it is not axruntime rather AROS abiv11 (if not mistaken)
-
@magorium
Thanks, link above fixed. I will fix text on web page as well.
-
@deadwood: Thank you for the corrections :thumbsup:
-
Hi All,
A new release of ABIv11 x86_64 is now available, containing improvements and fixes that happened since March 2022. Among improvements is the major work done on Scalos during summer to fix multiple compatibility, stability and 64-bit problems.
You can downloaded it from here (bottom of page): https://axrt.org/downloads-aros or from GitHub: https://github.com/deadw00d/AROS/releases/tag/ABIv11_20221221-1
Below you will find release notes.
If you are interested in developing for 64-bit AROS or developing AROS itself, contact me via email: https://axrt.org/contact
Release notes:
AROS ABIv11 20221221-1 changes:
Functionalities:
Added ACTION_FH_FROM_LOCK, case ACTION_COPY_DIR_FH to cdrom-handler (deadwood)
Linux-hosted debugging of C++ code enabled (deadwood)
Shell scroll back buffer increased to 1000 lines (deadwood)
Linux-hosted starts with 256MB RAM by default now (deadwood)
Initial work on audio driver for Windows-hosted AROS (Kalamatee)
processor.resource reading CPU speed on hosted AROS (Kalamatee)
Work in interrupt handling (Kalamatee)
Continued work on nvme.device (Kalamatee)
Initial work on power/battery management (Kalamatee)
Improvements in drawing on Graph.mcc (Kalamatee)
Improvements to debug output on multi-core systems (Kalamatee)
Enable AHI-Handler (Kalamatee)
Implemented preferences program for ASL (deadwood)
Ported TinySID (Kalamatee)
Scalos brought to the same level on Amiga, i386 and 64-bit builds (deadwood)
64-bit support:
Kernel (deadwood, Kalamatee)
MUI.MiamiPanel (Kalamatee)
cgxvideo.library fixes (Kalamatee)
muimaster.library fixes (deadwood)
NList.mcc fixes (deadwood)
AmiChess fixes (deadwood)
AMP2, radium fixes (deadwood)
Scalos fixes (deadwood)
guigfx.library fixes (deadwood)
68k support:
Enable compressing executables (Kalamatee)
ARM support:
Updates:
AROS build system (deadwood, Kalamatee)
More unit tests added (deadwood)
libz 1.2.12 (Kalamatee)
acpia.library 20220331 (Kalamatee)
libjpeg 9e (Kalamatee)
freetype 2.12.1 / freetype2.library v6.5 (Kalamatee)
libglu 9.0.2 / glu.library v2.2 (Kalamatee)
Turkish catalogs update for number of applications (Mazze)
Integrated MorphOS code release for asl.library (deadwood)
libmad 0.15.1b (Kalamatee)
Functional fixes:
C library (bugs in: %lld support, isnan/isinf, %#llx/%#llX support) (deadwood)
C library (bugs in: malloc_align) (Kalamatee)
Prefs/Locale (bugs: wrong behavior on timezone tab) (deadwood)
amigaguide.datatype (bugs: hang at startup) (deadwood)
muimaster.library (bugs: List selection) (deadwood)
Prefs/Zune (bugs: damaged title) (deadwood)
x11gfx.hidd (bugs: failure under WSL) (Kalamatee)
dos.library (bugs: crash in early boot menu) (Kalamatee)
wingdi.hidd (Kalamatee)
elf2hunk (Kalamatee)
ahci.device (Kalamatee)
exec.library (Kalamatee, deadwood)
fat-handler (bugs: missing partition types) (deadwood)
Prefs/ReqTools (bugs: wrong saving of selected options) (deadwood)
asl.library (bugs: preferences not loading) (deadwood)
muimaster.library (bugs: Arexx port not enabled, wrong notification loop detection) (deadwood)
workbench.library (bugs: WBInfo not compatible) (deadwood)
png.datatype (bugs: wrong rendering of paletted icons) (deadwood)
FryingPan (crash at startup and exit) (deadwood)
TheBar.mcc (deadwood)
Scalos (bugs: multiple problems with saving and loading of preferences) (deadwood)
Scalos (bugs: wrong drawing of alpha-channel datatype bitmaps) (deadwood)
Stability fixes:
Prefs/Pointer (bugs: crash with -O2 build) (deadwood)
fd2pragma, fd2inline (Kalamatee)
WiMP (Kalamatee)
fat-handler (Kalamatee)
muimaster.library (Kalamatee)
freetype2.library (bugs: memory override) (deadwood)
Scalos (bugs: multiple different problems) (deadwood)
-
How can I give you support deadwood? Sorry I don´t know how to code for AROS!
-
thank you deadwood!
-
Great job deadwood !
-
Thanks everyone :)
-
@deadwood
Thank you for your continued efforts to improve & maintain AROS development.
Thanks to you we enjoy great software! :)
-
Thanks Deadwood. Looking forward to try it out!
-
@nikos
Good to see you here. Note that there is only a Linux-hosted version available.
-
Hi,
If you are a developer compiling programs for x86_64 ABIv11, please read:
I discovered incompatibility with C library structures. Types fpos_t and ino_t were defined as 32-bit variables, while they should be defined as 64-bit ones. This has been fixed in recent master. As an effect structures dirent and stat now have different sizes. Backwards compatibility has been maintained in crt.library and it now exposes functions operating on fixed size types as well.
If you have a local build of AROS that you use for cross-compiling your programs, it is advised that you pull latest version and rebuild the cross-compiler and AROS (to get new Development: directory with headers)
-
Hello,
I revived the native x86_64 ISO build. You can try it here if interested:
https://axrt.org/development/aros-pc-x86_64-alpha-1.zip
At the moment this ISO is provided AS-IS. I'm accepting bug reports, but I'm going to log them and not work on them at the moment.
Please limit your RAM to 2GB or less. When more RAM is present, some bugs start to manifest.
-
Thanks I try to test is the future :)
-
deadwood i tried all options on grub but it wont boot my system is a xeon hp z400 workstation
-
@deadwood
I tried the 64bit iso on my i9-13900k system and don't even get to grub.
Same experience both natively and under a VM.
Is there a RAM limitation for 64bit?
I have 128GB in my system. I tried with 64 under the VM.
-
I guess there is more work to be done.
I don't know about limitations. I have my machine set up with 512 MB RAM.
-
ok deadwood we will wait for further releases thanks anyway :)
-
@Deadwood
I tried a few more configs under a VM and got it to run.
Using what I learned there I tried it natively and it appears the problem is when using more than 16 physical cpu cores. Disabling all but 16 cores it works, and boots into AROS, but even with just 17, either native or VM and I cant even reach grub. Volume of RAM doesnt appear to be an issue.
Ive barely tested beyond that, but things seem ok from a rudimentary playing around.
-
Hi,
Booted with VB 6.1 under xubuntu but crashed with starting up InstallAROS to install to usb
Picture of crash https://postimg.cc/30X0x56j https://i.postimg.cc/SR56VmfP/Virtual-Box-AROS64bit-15-02-2023-18-48-46.png
Jeff
-
@Deadwood
I tried a few more configs under a VM and got it to run.
Using what I learned there I tried it natively and it appears the problem is when using more than 16 physical cpu cores. Disabling all but 16 cores it works, and boots into AROS, but even with just 17, either native or VM and I cant even reach grub. Volume of RAM doesnt appear to be an issue.
Ive barely tested beyond that, but things seem ok from a rudimentary playing around.
Wow, I didn't expect to see any setup with that amount of cores... Good that you were managed to solve that. What VM did you use? VMWare or VirtualBox?
-
Hi,
Booted with VB 6.1 under xubuntu but crashed with starting up InstallAROS to install to usb
Picture of crash https://postimg.cc/30X0x56j https://i.postimg.cc/SR56VmfP/Virtual-Box-AROS64bit-15-02-2023-18-48-46.png
Jeff
Thanks. Does it work for you when you install to HD without having USB volumes? Also try installing on USB without having any IDE/SATA disks attached.
-
Hi,
Thanks,
First idea, sadly same result https://postimg.cc/dLLTKwfP https://i.postimg.cc/8PbdMCB5/Virtual-Box-AROS64bit-16-02-2023-02-39-02.png
Second one, seemingly the same https://postimg.cc/jDYqkT0h https://i.postimg.cc/y8kJx6L2/Virtual-Box-AROS64bit-16-02-2023-02-36-39.png
Regards
Jeff
-
Hmm, that's weird. I was expecting at least first option to work :/
What type of disks did you configure? IDE or SATA? I tried IDE and I was able to install in VM. :/
-
Hi,
IDE as per attached VB setup picture
-
Can you post here you VM descriptor? (File with extension .vbox in VM's directory).
-
@Jeff1138
Please limit your RAM to 512 MB and check.
-
@Deadwood
When trying to install this occurs if using more than 2GB:
https://postimg.cc/PPbrCQ8m (https://postimg.cc/PPbrCQ8m)
With 2GB or less the installation works.
While it's possible to partition a drive image with more than 2GB you can't format partitions. There's no output about the error, the system just locks up.
Im using VirtualBox by the way.
-
@korban
By 2GB, you mean 2GB RAM or 2GB disk image?
-
@Deadwood.
Ah, sorry, I can see how that was unclear, especially with me mentioning partitions and whatnot in the same sentence as 2GB :)
I was talking about RAM though.
-
Indeed, crossing 2GB RAM boundary makes some 64-bit bugs starting to manifest. There are not many left and eventually they are going to be ironed out.
-
@Deadwood
I tried a few more configs under a VM and got it to run.
Using what I learned there I tried it natively and it appears the problem is when using more than 16 physical cpu cores. Disabling all but 16 cores it works, and boots into AROS, but even with just 17, either native or VM and I cant even reach grub. Volume of RAM doesnt appear to be an issue.
Ive barely tested beyond that, but things seem ok from a rudimentary playing around.
Ram isn't an issue at least up to 256GB as far as I know. :-X
-
deadwood i tried all options on grub but it wont boot my system is a xeon hp z400 workstation
Set your bios to legacy mode and grub should appear(I've had issues with EFI bios in the past).
-
New ISO,
InstallAROS should now work with setups > 2GB RAM
https://axrt.org/development/aros-pc-x86_64-alpha-2.zip
-
Don't run on real pc i have hp z400 workstation whit intel xeon six core, 8 Gb of ram, IDE emulation
-
deadwood i tried all options on grub but it wont boot my system is a xeon hp z400 workstation
Set your bios to legacy mode and grub should appear(I've had issues with EFI bios in the past).
in the bios does not appear uefi boot however I set the emulation ATA and I installed TinyAros
-
Hi,
Setting to 512mb AROSInstall now runs (tested newest iso and that runs AROSInstall) but have the same issue of now freezing while creating and formatting partitions
Jeff
-
The limit now appears to be 3GB.
I tried with 32GB to begin with, but crashes still happened when trying to format and/or use InstallAROS.
After that I tried with 4GB, which had the same result.
3GB however worked without issue whereas it didnt before the new ISO.
-
That's unexpected :/
Anyhow I confirm that with ~4GB RAM formatting now crashes VM. Well, back to debugging.
-
New version, hopefully this time installation works with 4GB RAM
https://axrt.org/development/aros-pc-x86_64-alpha-3.zip
Note: it has some debug enabled, so you will see some text scrolling. It's ok.
Note: use the default selected grub menu option
@AMIGASYSTEM
This version now prints more information in case it does not detect a correct CPU. Please make a screen shot of that on your VMs.
-
deadwood, this ISO works perfectly on VMware, I initialized and installed AROs without any problem.
The Reboot and Reboot Cold command works fine, the system reboots without closing VMware.
Reset with the "CTRL-ALT A" keys also works fine.
Do I need to test any particular application?
-
Do I need to test any particular application?
Not at this time, thanks for test.
-
@Deadwood
Not sure what happened, but at 1st I'd get the same crash when trying with to install using 32GB (although formatting drives did work), then the same with 16GB, but 8GB worked fine.
However while slowly incrementing RAM beyond 8GB by 1GB at a time I managed to reach 16GB with things still working, then again with 32GB and then 64GB (didn't try beyond this).
I still get an immediate crash of the VM when configuring the VM to more than 16 cpu cores though. Definitely doesn't hurt in practice given AROS's currently single threaded nature, but thought you might to know still.
-
@Deadwood
Not sure what happened, but at 1st I'd get the same crash when trying with to install using 32GB (although formatting drives did work), then the same with 16GB, but 8GB worked fine.
Was was the nature of this crash? Did you get any guru requester or VM just shut down? If you are able to repeat these crashes, let me know.
I still get an immediate crash of the VM when configuring the VM to more than 16 cpu cores though. Definitely doesn't hurt in practice given AROS's currently single threaded nature, but thought you might to know still.
These issues won't be solve by my in near future, so next ISOs will also have this problem.
-
@Deadwood
It was the exact same thing as the screenshot I added to reply #33 in this thread.
This time however it didn't occur until after pressing "proceed" on the part of the installer where it gives the user the option to use "work" partition, "use work partition for extras and development files". This was consistently the case while it was crashing. I dont think this was the case with previous ISOs (cant recall off the top of my head, but I think previous builds crashed earlier).
I'd planned on taking a screenshot to show you, but then things just started working again :)
Not sure any of this feedback will prove useful for you, but thought I'd let you know just incase.
I'll let you know, and take screenshots if I can replicate it again.
-
I tried to boot on PC still from problems the solution 1024x768 works but then freezes, thanks deadwood :)
-
I tried to boot on PC still from problems the solution 1024x768 works but then freezes, thanks deadwood :)
Does it display anything on the screen? If so, can you make a photo?
-
ok deadwood
-
@Amiwell
What happens when you edit grub command line and remove line 'module /Devs/Drivers/i8042.hidd' and boot?
-
works, works... :D
-
ok native mode do not work, on vesa only prefs/ahi do not work all system and tools utilities works fine :)
-
works, works... :D
Good. Does USB pen drives work for you? What keyboard/mouse do you use? USB?
-
usb pendrive works(sound.datatype error when insert)i use usb device and works fine :)
-
deadwood I tested the ISO on Pendrive the ISO "aros-pc-x86_64-alpha-3" on my old laptop "Aspire 5920", The Pendrive starts but then crashes,see screenshot !
Aspire 5920 Specifications:
Processor: Intel Core 2 Duo T7300 (2.00GHz, 4MB cache L2, FSB 800MHz)
Chipset: Intel 965PM , Intel ICH8
RAM: 4GB
Video card: NVIDIA GeForce 8600M GT 256MB dedicated memory
I add that VMWare with ISO "aros-pc-x86_64-alpha-3" does not allow to initialize and format a Pendrive, to install AROS "aros-pc-x86_64-alpha-3"
In order to install "aros-pc-x86_64-alpha-3" I had to first initialize, and format the Pendrive to AROS One, done this, the ISO "aros-pc-x86_64-alpha-3" performed installation on the pendrive without any problem
-
@AMIGASYSTEM
You should try deleting the i8042.hidd like I suggested @Amiwell.
BTW, in a way you are lucky. USB doesn't work on my real hardware.
-
Yes I already tried to delete i8042.hidd, but nothing changes, it stops at the same point.
About the Pendrive I don't think it's luck, if you try my procedure you should succeed
- Run Vipe Disk with InstallerAROS (AROS ABIv0)
- After System Reboot
- From Wanderer Quickly Format DU0
- Boot ISO "aros-pc-x86_64-alpha-3 and run InstallerAROS normall, without using Vipe Disk
This way Install AROS "pretends to format", probably skips the formatting and continues with the installation normally.
-
FYI: I'm saying USB does not work on my hardware. Not just pendrive, but all USB devices are not visible.
-
Sorry deadwood I understood that the problem was on InstallAROS.
On WMware with "aros-pc-x86_64-alpha-3, no problem with Pendrives, successfully tried all my Pendrives !
-
FYI, If you are having problems booting -alpha3 on your hardware, there are two workarounds you can try:
1) remove i8042.hidd
2) add "noacpi" switch to kernel command line in grub
-
1) remove i8042.hidd
2) add "noacpi" switch to kernel command line in grub
Using all 2 solutions at the same time, in VESA nothing changes, same error.
Using all 2 solutions at the same time, in Native it crashes on Video Card error (not supported I suppose), see screenshot:
I am booting ACER Aspire 5920 Laptop (NVIDIA GeForce 8600M) from Pendrive.
-
I tried to install it on the hard disk everything goes fine but it doesn't boot, thanks deadwood!
-
usb stick installation works fine :)
-
deadwood, is it possible to fix the problems on Zune Gadgets ? all the details can be found in THIS (https://ae.amigalife.org/index.php?topic=774.msg14863#new) post
I= Iconify (It works well)
P= Zunemenu Prefs (doesn't work on AROS, works fine on OS3)
S= Snapshot (doesn't work on AROS ?)
M= Zune Prefs GUI (Lock Wanderer)
-
Tiny Aros 64 Experimental :D
(https://i.ibb.co/HK3hLKG/2-aros-x64v11.png) (https://ibb.co/Pr0Dsr1)
-
deadwood, is it possible to fix the problems on Zune Gadgets ? all the details can be found in THIS (https://ae.amigalife.org/index.php?topic=774.msg14863#new) post
I'm not interested in doing this Zune work ATM, but maybe there are other devs who would be interested.
-
@Amiwell
Very nice, thank you. BTW, there is MPlayer and MUIBase on the archives compiled for x86_64
-
deadwood mplayer, beebase(ex muibase), dopus4, unarc, arospdf, mysticview, amitube, lunapaint, povray works fine, thanks :D
ps.text2pdf built in contrib package do not works!
-
deadwood question, but will AROS ABIv11 support the existing ABIv0 software, or is some kind of conversion planned?
Making a Distro AROS One based on ABIv11 I think is very premature ! also because it might confuse many inexperienced users
Regarding Zune, one should make the report that the Gadgets are not working as they should.
-
deadwood question, but will AROS ABIv11 support the existing ABIv0 software, or is some kind of conversion planned?
I'm thinking of adding some sort of emulation layer so that ABIv0 programs "run" on x86_64. This is however far into the future, definitely not before ABIv0 catches up with master repository codebase.
-
deadwood mplayer, beebase(ex muibase), dopus4, unarc, arospdf, mysticview, amitube, lunapaint, povray works fine, thanks :D
ps.text2pdf built in contrib package do not works!
dopus4, unarc, arospdf, mysticview, amitube, lunapaint etc..are ABIv0, they should not work on ABIv11 !
-
deadwood question, but will AROS ABIv11 support the existing ABIv0 software, or is some kind of conversion planned?
I'm thinking of adding some sort of emulation layer so that ABIv0 programs "run" on x86_64. This is however far into the future, definitely not before ABIv0 catches up with master repository codebase.
Yes at the moment it is important for ABIv0 to move forward, that way developers if it is possible will be able to convert their software.
-
deadwood question, but will AROS ABIv11 support the existing ABIv0 software, or is some kind of conversion planned?
I'm thinking of adding some sort of emulation layer so that ABIv0 programs "run" on x86_64. This is however far into the future, definitely not before ABIv0 catches up with master repository codebase.
Yes at the moment it is important for ABIv0 to move forward, that way developers if it is possible will be able to convert their software.
🤔
-
deadwood mplayer, beebase(ex muibase), dopus4, unarc, arospdf, mysticview, amitube, lunapaint, povray works fine, thanks :D
ps.text2pdf built in contrib package do not works!
dopus4, unarc, arospdf, mysticview, amitube, lunapaint etc..are ABIv0, they should not work on ABIv11 !
try it contrib package and amitube, beebase and mplayer there is a v11 version on archives
-
deadwood mplayer, beebase(ex muibase), dopus4, unarc, arospdf, mysticview, amitube, lunapaint, povray works fine, thanks :D
ps.text2pdf built in contrib package do not works!
dopus4, unarc, arospdf, mysticview, amitube, lunapaint etc..are ABIv0, they should not work on ABIv11 !
LunaPaint can be compiled for ABIv11 & Dopus4 64bit works somewhat. ZuneTools have 64bit versions as well. Also IconClone can be compiled for 64bit.
-
Thanks miker, however too little software to create a Distribution, who installs a Distribution if he does not find the software , after curiosity nothing is left and the Distro is no longer used or worse trashed.
Better to wait until everything works and the most important software is converted, reinventing the wheel is always tiring.
-
ZuneTools are not compiled for x86_64v11 only on Archives, Beebase, Mplayer, Albs Blog, AmiTube and on contrib x86_64v11 you can find other software
-
Thanks miker, however too little software to create a Distribution, who installs a Distribution if he does not find the software , after curiosity nothing is left and the Distro is no longer used or worse trashed.
Better to wait until everything works and the most important software is converted, reinventing the wheel is always tiring.
I understand you, but please remember, that the first step is always the hardest. Anybody has to do it. And yes, it is a rather thankless task… But on the contrary I would be very thankful. :)
-
I am not against it, I was just saying that to create a Distribution you have to have some software otherwise it is not palatable by likely new users.
In any case, I will always be ready and available to create AROS One x64
-
@Amigasystem
Thank you for all your efforts! I don‘t want to criticize you or your work. I appreciate what you do.
-
I use IcarosDesktop 64bit on a regular basis mostly for testing software. It is Hosted on Linux.
As far as I remember the Native version has issues booting from hard disk whether on real hardware or in VM's.
The boot from hard disk issue was fixed after several days with three or four developers working on the problems. But that was the solution for Apollo OS (AROS 68k) on V4SA. Rony Beck and others put in many hours on that issue.
Not sure if they updated the ABIv1 repository afterwards. But the changes are likely present in the Apollo OS fork.
BTW I have a zip archive of all the ZuneTools for x86-64. Maybe I will post them to AROS Archives. They were revised for 64bit & compiled by the author. It includes: StackMon, ThumbnailGenerator, VNC_Client, ZuneARC, ZuneBrot, ZuneFig, ZuneHex, ZunePaint & ZuneView.
-
Icaros Desktop a 64 bit there is not a abiv11 version but abiv1, in this thread deadwood explain the new fork based on abiv0 of x86_64 who is abiv11
-
zunetools based on abiv1 not abiv11 and do not works i try it :)
-
zunetools based on abiv1 not abiv11 and do not works i try it :)
ZuneTools is based on ZuneTools and they work just fine on x86-64. I will download the TinyAros Distro and test them. 8)
I'm using IcarosDesktop x86-64 which as far as I know is based on stable version ABIv11.
-
I'm using IcarosDesktop x86-64 which as far as I know is based on stable version ABIv11.
Was there any new release of IcarosDesktop x86_64? I remember reading about it a few years back, but ABIv11 is only available since January 2022.
-
I'm using IcarosDesktop x86-64 which as far as I know is based on stable version ABIv11.
Was there any new release of IcarosDesktop x86_64? I remember reading about it a few years back, but ABIv11 is only available since January 2022.
I'm using the older version that paolone released. I assumed it was based on ABIv11 but maybe not now that you clarified it. The IcarosDesktop I'm using is older than 2022.
-
It isn't, in fact.
-
Now I'm going to get to work and see if I can create a primordial version of AROS One 64bit ABIv11, add all available applications, if I can I'll also try to make a Pendrive Live version ;)
-
ZuneTools is based on ZuneTools and they work just fine on x86-64. I will download the TinyAros Distro and test them. 8)
do not works on build alpha of deadwood i have tested all apps, zunetools is than older from 2019 8), need to be recompiled!
-
ZuneTools is based on ZuneTools and they work just fine on x86-64. I will download the TinyAros Distro and test them. 8)
do not works on build alpha of deadwood i have tested all apps, zunetools is than older from 2019 8), need to be recompiled!
Ok. ZuneTools for x86-64 don't work. So I assume all the 64bit apps need to be recompiled for use with ABIv11 ?
-
yes miker :)
-
Now I'm going to get to work and see if I can create a primordial version of AROS One 64bit ABIv11, add all available applications, if I can I'll also try to make a Pendrive Live version ;)
That sounds great AMIGASYSTEM :)
@Deadwood..
Thank you so much for your time and fantastic work.
It is very much appreciated :)
-
@All
Thanks for good feedback and interest. Please keep in mind that I'm just adding the last 1% here - this would not be possible without "behind the scenes" work of Kalamatee and other kernel developer, so be sure to drop a donation / kind word to them as well.
As for x86_64 native version itself, my priorities lie with ABIv0, so problems that that you see in x86_64 (like non-working drivers) most likely won't be addressed at this time unless they are also present in ABIv0. That's why even though a lot of things work already, the builds are labels "alpha".
-
thanks Deadwood and all Developers :)
-
@All
As for x86_64 native version itself, my priorities lie with ABIv0, so problems that that you see in x86_64 (like non-working drivers) most likely won't be addressed at this time unless they are also present in ABIv0. That's why even though a lot of things work already, the builds are labels "alpha".
Thanks deadwood for the priority on ABIv0, ABIv11 needs to grow before a possible stable distribution, of course a thanks to all developers of any branch.
Regarding ABIv0 I am waiting for your ok before proceeding with the distribution, this is to ensure users an increasingly quality Distribution.
-
Regarding ABIv0 I am waiting for your ok before proceeding with the distribution, this is to ensure users an increasingly quality Distribution.
The list of open issues that I work on is available in ABIv0 thread. Currently I'm stuck with interrupts issues for nVidia cards and I don't know whether it will take a week or a month to resolve it. Once I address all the issues that are on the list I will make a final ISO that will close this development cycle.You need to decide whether you want to wait for that final ISO or release your distribution now and distribute a patch later.
-
Yes I wait I am not in a hurry, I don't like to spread distributions with some unresolved problem, I prefer a Distribution as stable as possible, only in this way users remain satisfied, especially those who try AROS for the first time, before making the ISO usable I must be satisfied first.
Among other things I am finishing the fourth type of icons and replacing some old system icons.
-
deadwood ahi not working properly
-
@deadwood
With AROS ABIv11 with MPlayer the file association does not work, basically if you run a Video, the GUI opens but the video is not shown, see screenshot.
I read that you are fixing GCC, I still tried to run GCC and got a GURU, if it helps I can take a screenshot.
-
@deadwood
I read that you are fixing GCC, I still tried to run GCC and got a GURU, if it helps I can take a screenshot.
I'm aware of this, fix should be available tomorrow.
-
With AROS ABIv11 with MPlayer the file association does not work, basically if you run a Video, the GUI opens but the video is not shown, see screenshot.
Bug report added: https://github.com/deadw00d/AROS/issues/92
-
I'm aware of this, fix should be available tomorrow.
Here is fixed crt.library. GCC should not longer Guru
https://axrt.org/development/crt.library-2.1-x86_64-v11.zip
-
Ok thanks deadwood, GCC works fine, no GURU, see screenshot !
I will fix the Path tonight and then try to compile something simple if I can.
-
I will fix the Path tonight and then try to compile something simple if I can.
Looking forward to it :)
-
For Path no problem, usual bug, if GCC run from Shell from Icon (System:Shell), it is not "found"
If instead you use Shell from Wanderer menu the GCC is found without moving to Bin :)
Ok tonight when I get home I will do some compilation tests !
-
deadwood one question, AROS x86 sources, to be compiled with GCC ABIv11 must first be modified to be compatible, or can they be compiled without any modification?
-
deadwood one question, AROS x86 sources, to be compiled with GCC ABIv11 must first be modified to be compatible, or can they be compiled without any modification?
If you have some source that compiled for ABIv0, then it will most likely compile without any change for ABIv11.
-
I tried to compile a small source in C "bintoiso.c", on ABIv0 the compilation was successful, in the screenshot you see Shell in Red
GCC on ABIv11 (Shell Blue) on the other hand crashed without giving any message, even the system crashes !
-
Can you make the source code available?
-
Can you make the source code available?
-
I didn't get a crash on linux-x86_64, but native have a different kernel which can cause this. Try setting the stack to 1024000 and see if that helps.
-
I used that Stack but nothing changes, now I try to copy the development folder, maybe there is something corrupted
-
Maybe the problem is caused by unpacking the "Contrib" archive, i tried unpacking again, and this time I have the error
-
Ok, that's possible. See if you have the file mentioned (cc1). Otherwise start Sashimi and see if you get some debug output on it.
-
The file "cc1" is present, allegoscreenshot report Sashimi
-
I see the problem with undefined symbols. This is something that should not be happening. I think you are right and extraction from archive somehow damaged the file.
-
You should try using a different compressor that is supported well by all platforms, perhaps RAR or ZIP would be a good solution.
-
amifox of marcus alb42 works fine :)
-
That's good development :)
-
deadwood, I would like to report that with AROS ABIv11 the Network does not work with VMware !
-
deadwood, I would like to report that with AROS ABIv11 the Network does not work with VMware !
I understand, that's possible. If VMWare has emulation of different network devices, you can try to see if all the drivers fail.
-
I have already tried the various network devices without success, but AROS Network Prefs side, should I set a Device other than PCNet32.device?
-
That's good development :)
yes is possible try to compile more application for this architecture, finally we works fine.
-
I have already tried the various network devices without success, but AROS Network Prefs side, should I set a Device other than PCNet32.device?
Well, yes. On AROS side you need to set the device that matches the virtual hardware. Try e1000.device if you have Intel PRO/1000 set on VM side.
-
With 1000.device Network Preferences crashes, the PC I use withVMware has a "Gigabit Intel(R) 82567LF-3" as the Network Card
-
currently with the alpha 3 version I have encountered problems with ahi and DiskImageGui
-
I see the problem with undefined symbols. This is something that should not be happening. I think you are right and extraction from archive somehow damaged the file.
After doing some tests, I think the problem is in the x86 Build, I installed "AROS One + ABIv11 Host Linux", and the GCC worked fine, and the source compilation also worked correctly, see screenshot.
Then I used the "same Development folder" on x86 and got the usual error
(https://ae.amigalife.org/index.php?action=dlattach;topic=881.0;attach=4578;image)
-
ok amigasystem :)
-
Then I used the "same Development folder" on x86 and got the usual error
That's quite possible. Which driver are you using in your native installation? ide.device or ahci.device?
-
My Native test was done only on VMWare ! the error happens even if you run GCC from the ISO, without the need to install it.
-
I see the problem with undefined symbols. This is something that should not be happening. I think you are right and extraction from archive somehow damaged the file.
After doing some tests, I think the problem is in the x86 Build, I installed "AROS One + ABIv11 Host Linux", and the GCC worked fine, and the source compilation also worked correctly, see screenshot.
Then I used the "same Development folder" on x86 and got the usual error
(https://ae.amigalife.org/index.php?action=dlattach;topic=881.0;attach=4578;image)
I may be completely wrong but when I look at the screenshot you compiled the binary for Bin2Iso.
Then you tried to run it with only Bin2Iso but that's the incorrect syntax. It needs a filename such a as Bin2Iso image.bin in order for it to run correctly.
At least that's what it looks like to me though there may be other issues involved as well. I wish I could test gcc also but I'm limited on hard disk space so I can't install distros. But I can install the developer tools over an existing install.
I'm new at installing gcc. Which directories do I copy?
-
I didn't test the functionality of the BinToIso binary, but just to make sure it was executable, then maybe I will try if it works, in any case the original gives the same message if run without parameters.
Pechè works the GCC as mentioned in PM, you have to copy the entire "contents of the Development Folder" (351 MB) , inside the "Development Folder" of the Build, that's all.
Then make sure that the "S" folder included in the Development folder has the "Package-Startup" File that includes the Assigns.
Important, to use GCC "do not use" the Shell run from Icon (System Folder), but use the Shell launched from Menu Wanderer. This is important otherwise the GCC command will not be found.
Remember ce the GCC v11 works only on AROS Host Linux.
-
deadwood, I found two serious oddities on the Build "aros-pc-x86_64-ABV1-alpha-3"
- If you delete the icons to the files located in the path "System/Wanderer/Tools, the respective exe files, are no longer executable, I attach comprehensive video,
Consider that on AROS One x86 I always deleted those icons because in my opinion never used by user ! and this problem does not exist
https://drive.google.com/file/d/1UYHO14InJLnBmHkEXPEdcuhj9KoHVTGy/view?usp=share_link
- The second oddity, if you replace all the system icons (which I do hundreds of times on AROS One X86), InstallAROS "does not install" the Development folder, despite there being a checkmark to enable it.
Here I ask a question, InstallAROS some "script" or "File "performs for installation, again it could be the fault of some icon
-
@AMIGASYSTEM
Bug reports added:
https://github.com/deadw00d/AROS/issues/95
https://github.com/deadw00d/AROS/issues/96
-
@Amiwell
Beware, as reported above, TinyAROS has the same problems, InstallAROS does not install the Development folder, and if you delete the icons, or change the icon type "Must be Tool icon" from "System/Wanderer/Tools", the Command "Info" does not work, see my video attached above.
---- Italiano ----
Attenzione, come segnalato sopra, TinyAROS ha gli stessi problemi, InstallAROS non installa la cartella Development, e se elimini le icone, o cambi il tipo di icona "Deve essere icona Strumento" da "System/Wanderer/Tools", il Comando "Info" non funziona, vedi il mio video allegato sopra.
-
I have no problem with icons with development tools you do not install them thaks :)
-
I have no problem with icons with development tools you do not install them thaks :)
I didn't understand, answer in Italian, on TinyAROS virtual machines "It doesn't install the Development folder"
You don't have the the icon promblem because on TinyAROS "you still have the original Build icons"
Try installing TinyAROS on VMware and you'll see that it doesn't install the Development folder, a large proportion of AROS users use VMware !
---Ita ----
Non ho capito, rispondi in italiano, su macchine virtuali TinyAROS "Non installa la cartella Development"
Non hai il problema icone perchè su TinyAROS "tu hai ancora le icone originali della Build"
Prova a installare TinyAROS su VMware e vedrai che non installa la cartella Development, gran parte degli utenti AROS usa VMware !
-
Deadwood can't worry about the native version at the moment abiv11 said that only 1% of his time will be spent
ita
ho le ken icons v2.3 e si non installa i development tools ma tanto non funzionano e deadwood al momento si sta preoccupando di altro
-
No, in that path you don't have ken icons, you didn't replace them with ken icons. see screenshot!
The Developent folder however must be able to be installed because it also serves other Development Applications.
--- Ita ---
No, in quel percorso non hai le icone ken icons, non le hai sostituite con le ken icons. guarda screenshot!
La cartella Developent comunque deve essere poter essere installata perchè serve anche ad altre Applicazioni di Sviluppo.
-
yes those I never change
-
as for the dev tools deadwood will fix the problem when he has time :)
-
Is it possible to use the cross compiler that gets built/used during during the ABIv11 build process?
I tried adding the toolchain-core-x86_64 directory (that contains x86_64-aros-gcc, etc.) to PATH but when I try to compile anything it fails to find standard header files and static libraries.
-
@salass00
Yes, it's possible :)
In order to use the cross-compiler built in step 1 for compiling your own projects (which don't use AROS builds system / mmakefile.src approach), you need to provide --sysroot parameter, for example:
$ <myprojects>/arosbuilds/toolchain-core-x86_64/x86_64-aros-gcc --sysroot=<myprojects>/arosbuilds/core-linux-x86_64-d/bin/
Taken from here: https://github.com/deadw00d/AROS/blob/master/INSTALL.md
-
amitube v1.4 again works on x64v11
-
deadwood, I made a News of AROS 20230430-1 on EAB, in order to avoid that I give some incorrect answers, possibly you could step in to give the right answers to some users, thank you
https://eab.abime.net/showthread.php?t=114416
-
@AMIGASYSTEM
Thanks, I will handle those answers.
-
@deadwood
With --sysroot I seem to be able to use the cross toolchain to compile x86_64 ABIv11 executables, but when compiling libsmb2 (for smb2fs) I get duplicate member th_off and th_x2 errors in <netinet/tcp.h>.
The reason it seems is because in this code part:
struct tcphdr {
...
#if BYTE_ORDER == LITTLE_ENDIAN
u_char th_x2:4, /* (unused) */
th_off:4; /* data offset */
#endif
#if BYTE_ORDER == BIG_ENDIAN
u_char th_off:4, /* data offset */
th_x2:4; /* (unused) */
#endif
both "BYTE_ORDER == LITTLE_ENDIAN" and "BYTE_ORDER == BIG_ENDIAN" conditions are evaluated as true by the pre-processor (most likely because the macros are undefined). If I add -D__BSD_VISIBLE to CFLAGS then I don't get these errors.
-
@salass00
I'll look into that.
Thanks for compiling your software for 64-bit. If you ran into any problem with the port, let me know :)