aros + raspberry 3+ and AROS-20201229-raspi-armhf-system.tar.bz2 (

meteos · 905

meteos

  • Newbie
  • *
    • Posts: 5
    • Karma: +0/-0
Hello to all

I am brand new on AROS

I downloaded the file AROS-20201229-raspi-armhf-system.tar.bz2 on Nightly Build Downloads (ABI-v1)

The native version for ARMv6 based Raspberry Pi computers. Contains all files needed to boot from a FAT formatted sd-card.

I copied the files from the archive to the 1st partition of the sd-card (in vfat)
when I start up, I get the multicoloured screen and then the black screen.

what more do I have to do to get access to the system?

thank you for your advice
Yours sincerely



magorium

  • Senior Member
  • ****
    • Posts: 253
    • Karma: +7/-0
  • Convicted non contributor
Hi and welcome meteos.


Man you're quick  :)

The build for the pi started working just yesterday (or the day before, i'm a bit hazy there), so it's bound to have some issues and i doubt that anyone had the chance to test it (thoroughly) yet.

Feel free to create bug-report @ github, or ask about it on slack. It might be the developer(s) are aware there are (still) some issues, in which case it will take some time to address (otherwise it would have been done already).



meteos

  • Newbie
  • *
    • Posts: 5
    • Karma: +0/-0
good morning,
thank you for its details
if it's brand new ... and as I'm not a developer, I don't see what I could bring to the developers in a bug report except that it doesn't boot on rapsberry pi 3 & pi400.

I'm a former amigaiste (1985) and wanted to see if on raspberry (pi 400) I could find the nostalgia of the amiga 500.
so i will wait and read forum

thank you again



magorium

  • Senior Member
  • ****
    • Posts: 253
    • Karma: +7/-0
  • Convicted non contributor
thank you for its details
You're most welcome.

In case you do have some basic knowledge on software development then you can perhaps take a peek at the commit history on github here https://github.com/aros-development-team/AROS/commits/master

If you look closely you can see that for example the raspi just had some commits being made less than a day ago (i am assuming to try to fix some issues that presented itself during the build/testing or because it was already anticipated to address certain issues).

Quote
if it's brand new ...
It is not entirely brand new (see also my answer later), the raspi branch exist for a couple of years now.

What is new however, is that since the transition to a new updated abi (abiv1) it became clear that a) there still need to be done a lot of work on the raspi port and b) the AROS build-system in general needed an overhaul as well. Especially the latter required (and still requires) a lot of work.

Besides that, there was also a transition from svn to git(hub) and support for a new build-software (azure) was added as well.

In all that development violence and changes the raspi branch simply was left a bit behind the other branches (as the main branch is x86_64).

Quote
and as I'm not a developer, I don't see what I could bring to the developers in a bug report except that it doesn't boot on rapsberry pi 3 & pi400.
And, with all due respect, that is where you are a bit wrong  :)

Developers rely on reports, just as you just did. They simply do not have the time to check each and every branch on a daily base and that is where us users come in and can help a bit.

The only "crime" you committed is that the build for the raspi branch just started working again, and as such developers keep an (closer) eye on things for a bit when such things happen. For detailed reports they really rely on the user-base.

So in case you can be bothered i would advise to keep an eye open on the progress and try for example once a week/month or so.

Even though you are perhaps not a developer, it is perfectly valid to ask such a question (on github or otherwise) how many more work is needed to be able to test the raspi branch or how long that would approximately take (i have currently no idea what needs to be done). If you have an github account then that would be the easiest way, otherwise you could use the developers slack-channel. Sometimes developers can also be found on the #aros irc channel at freenode.

afaik they do not have an account here or in case they do, do not react (often) in public threads here.



In case you do not wish to wait for the progress on the raspi branch, then there are alternatives as well.

For example, it is possible to run AROS hosted on your pi, see http://www.aros.org/nightly.php (linux-armhf-system and linux-armhf-contrib) or in case you have a "powerful" enough computer which runs linux/windows you can use virtualization software like vmware/virtualbox (there are others as well) and run or install AROS there.

The latter isn't exactly the same experience as running AROS native but you can configure most (if not all) virtualization software in such a way that it integrates seamlessly with your OS. I had AROS running on virtualbox on my windows machine for years and am now doing the same on a linux machine. For development i use the hosted version of AROS because that works better for my personal work-flow.

As a sidenote, if you truly seek the a500 experience then you are probably better off using an emulator like fs-uae/winuae because they can emulate the Amiga to (almost) perfection. AROS is more geared towards users that like the experience of the operating system. AROS itself does not have any support for integration of running original Amiga software, but Icaros desktop does come with an emulator named janus-UAE and paolone tried to make that experience as seamless as he was able to make it (with support from the developer of Janus-UAE as well) but janus-UAE is showing its age  :-\

regards,




meteos

  • Newbie
  • *
    • Posts: 5
    • Karma: +0/-0
Hello, and happy new year to all

today I tested AROS-20210104-raspi-armhf-system.tar.bz2

result : still black screen (well rather a gradation from black to midnight blue from left to right) after the raspberry's multicolor screen

request for improvement
Would it be possible in the Raspberry version manufacturing process to provide an image of the sdcard to be tested instead of the files.
it takes more time to copy more than 6000 files than to "write the sdcard image".

in advance thank you



Fafa

  • Newbie
  • *
    • Posts: 1
    • Karma: +0/-0
Happy New Year to everyone.

I have tested AROS-20210107-raspi-armhf-system on Raspi 3+ and Raspi 2

Raspi 3+: the same result as Meteos, a gradation from black to midnight blue from left to right.

Raspi 2: No signal video, after the multicolor screen

Thanks to everyone who makes Aros possible.



magorium

  • Senior Member
  • ****
    • Posts: 253
    • Karma: +7/-0
  • Convicted non contributor
request for improvement
Would it be possible in the Raspberry version manufacturing process to provide an image of the sdcard to be tested instead of the files.
it takes more time to copy more than 6000 files than to "write the sdcard image".
I can't remember which target exactly but it could be the raspi that was distributed in the past as .img file that could be dd'd to an sd-card.

Everything is possible  :P , so also your request but i have no idea if that is planned by the development team.

For the status see also my reply to Fafa. Thank you for testing.


magorium

  • Senior Member
  • ****
    • Posts: 253
    • Karma: +7/-0
  • Convicted non contributor
Happy New Year to everyone.
Happy newyear to you as well.


Thank you for testing and reporting your issues.


The testing is really appreciated but still a bit early  :)

Most of the commits made the last couple of weeks are related to fixing/improving the build-system in general. This is still an ongoing process (last coupe of days with regards to the darwin target for example) and one that might take quite some time (months rather than weeks, but that is a guesstimate from myself based on what i've seen so far)

Besides the obvious advantages of improving the build-system, there is some special care needed for the raspi as well, that in order to even have a change to try to compile the open-source hardware video driver (vulkan) there are some (other) requirements that have to be met as well (updated compiler/dependencies f.e.)

Be prepared to watch the build-system fail a couple of times before things get more (and more) stable, at that point there might be some time for the development team to dive into things, but keep in mind that x86_64 has priority (don't ask me why, as raspi is much more sexy and important, not ?  :P )

If you want to make sure your issues is not forgotten then i do emphasis reporting your issue(s) on github (if that hasn't been done already)

Happy AROS'ing


meteos

  • Newbie
  • *
    • Posts: 5
    • Karma: +0/-0
hello,
I modified a script to create the image of the sdcard for the raspberry.
The goal is to burn the image rather than copy the files to the sd.

I block on the copy in the image because it takes the source directory as path and not just the content.

if anyone has an idea?



magorium

  • Senior Member
  • ****
    • Posts: 253
    • Karma: +7/-0
  • Convicted non contributor
I block on the copy in the image because it takes the source directory as path and not just the content.
If you have successfully created an empty image, and added a filesystem to it then you can mount the image to your system by making use of a so-called loopback.

That allows you to access the 'inside' of the image as it was a regular floppy disk or hd, and as such are able to copy files 'inside' the image. Once you are done copying files into the image you can then dd the image to f.e. an sd-card or any other drive (be very careful when using dd as it can wipe out an perfect working system-drive in a blink of an eye when writing to the wrong device)

If your image is not to big in size (restricted by how much memory your machine has) then it is possible to locate the image file inside a ramdisk, which will work blazingly fast. Of course you can also place the image file on a HD or sd-card/usb-pendrive in which case that will work just as slow/fast as using a regular HD sd-card/pendrive. The upside is that you only have to do it once (write once, copy many) :)

Here are some (english) instructions from someone who is attempting something similar as what you are currently trying to accomplish and who is using ubuntu: https://midnightprogrammer.net/post/create-mount-and-unmount-img-files-in-ubuntu/

Quote
if anyone has an idea?
Hopefully those instructions are enough to get you going...