Tiny Aros Experimental x86_64 v11

[terminills]

The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.

Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift 

With VMWare AROS we are talking about many years ago, when there were many more developers on AROS, I will definitely continue to test as always for ABIv11 as well, but right now as deadwood said, the priorities reside in ABIv0

This is the exact attitude that ran off a few of the most active developers.   

[miker1264]

I fixed the iso await further developments by deadwood

Thanks for your efforts in setting up Tiny AROS x86. It is much appreciated.

It also gives me a good starting point to setup a testing environment. I don't especially like to use the default layout filled with Gorilla Icons and no applications other than system apps. Sometimes those extra utilities are needed.

And besides I like the concept of Tiny AROS. Quick & easy!

PS - I will refresh my ABIv11 Build System this weekend then I can compile some existing software for ABIv11.
(this time for real  ).

[Amiwell]

ok miker thanks so much

[miker1264]

The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.

Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift 

With VMWare AROS we are talking about many years ago, when there were many more developers on AROS, I will definitely continue to test as always for ABIv11 as well, but right now as deadwood said, the priorities reside in ABIv0

The problem is that we must take the first steps in the direction of ABIv11 in order to make future distros possible.

The other problem is that deadwood is only one person and he has to focus on the most important tasks first. But if there are situations where changes benefit both ABIv11 & ABIv0 then that's good. That's beneficial for everyone.

Until we can attract more active developers to AROS this situation probably won't change. But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.

That's how I see it but others may see it differently.

[deadwood]

The problem is that we must take the first steps in the direction of ABIv11 in order to make future distros possible.

The other problem is that deadwood is only one person and he has to focus on the most important tasks first. But if there are situations where changes benefit both ABIv11 & ABIv0 then that's good. That's beneficial for everyone.

Until we can attract more active developers to AROS this situation probably won't change. But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.

That's how I see it but others may see it differently.

+1

[AMIGASYSTEM]

 But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.

That's how I see it but others may see it differently.

If I have to be honest, I find AROS x86 ABIv0 more functional than AROS 68k, I use both, on AROS 68k I have not seen anything more than AROS x86 ABIv0.

AROS 68k in my opinion is a hybrid system, which does not have any native software, and that much of the Amiga software does not work or works poorly, I say this given my extensive Amiga experience for almost 40 years, this is why I decided not to distribute AROS One 68k, despite having had so many requests, an example on these link:

https://eab.abime.net/showthread.php?t=98062

http://eab.abime.net/showthread.php?t=97987

http://eab.abime.net/showthread.php?t=106295

[miker1264]

Amiwell

Instead of TinyAros it is becoming a discussion about ABIv11.

AMIGASYSTEM
You misunderstood. I wasn't talking only about AROS 68k.

The code base that AROS 68k uses was ABIv1 but that may be ABIv11 now. But deadwood can explain it better.

The Apollo Team has made changes to their branch (should we call it ABIv10 or ABIv12 ?). These changes can be brought into ABIv11 which in some way is also the basis for ABIv0. I know I'm not explaining it correctly. It's complicated.

For various reasons we haven't worked directly with Apollo Team for a long time now. Rony Beck and a few others have gained some experience dealing with the boot from hard disk issue for the V4 Standalone (real hardware for 68k).

There were several problems preventing boot from hard disk such as with the current ABIv11. I believe the two problems are the same. It was mostly a timing issue if I remember correctly. Scsi.device was waiting indefinitely for a signal that never arrived. But all that was fixed a few years ago. That's just one example of how we can co-operate.

But more importantly we must also consider development with ABIv11 in mind in order to improve it to move forward. Once ABIv11 can boot from hard disk either on real hardware or in a virtual machine it makes testing easier.

@Amiwell
Does TinyAros work in Native Mode or just Hosted Mode?

[miker1264]

Of course it's necessary to focus on development for ABIv0 because that's what the majority of the people use daily.

But it's also important to have distros like TinyAros x86-64 so we can compile software as needed or when it becomes available so we can test it. That's necessary to move forward with development.

Whether anyone else chooses to support ABIv11 that's up to them. But I'm certainly in favor of x86-64 flavors of AROS.

[AMIGASYSTEM]

Ok miker, sorry I just wanted to point out that I always updated AROS 68k with the Nightly Builds ispreviously taken from HERE, I don't know if it is produced by Apollo, for sure in these years the compatibility with Amiga software and its functionality has never changed, so for for me, at the moment it doesn't make any sense to Distribute a new version of AROS One 68k.

About ABIv11, at the moment I believe it is not worthwhile to make a Distribution, since many things are unfinished, testing for the moment is better to do it with deadwood's reference Build.

When deadwood says ABIv11 is ready to be used for a Distribution, I will be happy to upgrade my AROS One ABIv11, which I have already announced here:

https://ae.amigalife.org/index.php?topic=1087.0

[magorium]

The code base that AROS 68k uses was ABIv1 but that may be ABIv11 now. But deadwood can explain it better.

It still is ABIv1 for 68k and it will not change.

The Apollo Team has made changes to their branch (should we call it ABIv10 or ABIv12 ?). These changes can be brought into ABIv11 which in some way is also the basis for ABIv0. I know I'm not explaining it correctly. It's complicated.

afaik Apollo forked AROS so if you need specific information on that topic then you should ask the Apollo developers 

What I do know is that some of their work/fixes is/are incorporated back into  the official AROS source-tree.

[deadwood]

But more importantly we must also consider development with ABIv11 in mind in order to improve it to move forward. Once ABIv11 can boot from hard disk either on real hardware or in a virtual machine it makes testing easier.

@Amiwell
Does TinyAros work in Native Mode or just Hosted Mode?

You should really try TinyAros x86_64 and see for yourself

[deadwood]

@miker1264

If you try TinyAros x86_64 in VirtualBox you will get not keyboard nor mouse, because PS/2 driver is removed.

Add this to grub module list

Code: [Select]

    module /Devs/Drivers/i8042.hidd

Also when you try running GCC you will get a crash in C library. I will fix this over weekend.

[Amiwell]

Miker this distribution is native installs on USB stick and preset to work only in vesa mode at the moment

[Amiwell]

@miker1264

If you try TinyAros x86_64 in VirtualBox you will get not keyboard nor mouse, because PS/2 driver is removed.

Add this to grub module list

Code: [Select]

    module /Devs/Drivers/i8042.hidd


Also when you try running GCC you will get a crash in C library. I will fix this over weekend.

Thanks

[miker1264]

I'm trying to boot the ISO in VirtualBox but in Vesa Mode the screen is black. What configuration do I need. Will it boot from the ISO ?