Amibian 1.5 extended edition for pi4

Type permission into cli and update

@Gunnar Fixed. All .sh files in .amibian_scripts/ after update was with no execution bit set. Also had to change keyboard type from Nordic to UK :)

Yes. The Amiberry GUI is not 100% the same as in WinUAE, but similar in many ways. If you are familar with setting up WinUAE, you should be able to set up Amiberry as well. You can even install WB3.1 in WinUAE and then copy the hdf file and use with Amibian.

Ok thanks and yes I found an excellent PC Winuae setup tutorial on youtube

I have no experience with hstwb at all. I just googled it now to see what it was.

As far as I can tell from the hstwb.firstrealize.com website, it is a package to help you install various AmigaOS versions with some addons.

I noticed there was a separate section about Amibian. I did only read the instructions briefly, but to me it sounded easier to just set up a AmigaOS installation manually.

Anyway, I think the hstwb for Amibian is at an experimental state, judging from the threads at the github. https://github.com/henrikstengaard/hstwb-installer/wiki/HstWB-Installer-for-Amibian

The most recent issues thread is titled "Installer not working on Amibian 1.5", so I'll advice you to read there first to check the current state of the project.

Now, about your questions.

I understand that the hstwb package requires you to find your own source for the rom and OS files. The Rom files you mention does not sound like roms suitable for an emulation package. Bin files are probably files for burning your own physical ROM chips for use in a real amiga.

If youy dont have rom or OS files, the easiest way to get them legally is the Amiga Forever package.

For Picasso 96, it should not be a big problem to install that after you have got a working Workbench 3.x running.

About PAL and NTSC modes. This depends on if you have selected NTSC in the amiberry GIU, in the chipset section. I have OS3.9 installed as my main amibian setup, and normally I can select PAL or UAE screenmodes, but if I select NTSC chipset and restart, I will only see NTSC and UAE screenmodes. (the uae screenmodes will be available after you set up picasso96)

Finally, if you really want to use a hstwb installation on amibian, I think it might be easier to install it on a PC or Mac first and then copy the harddrive file (hdf) and the correct rom files to amibian later.

Entering something like this at the command line should remove the desktop for you.

sudo apt-get remove lxde

sudo apt-get autoremove

use 1234 as password if prompted

But dont expect that to remove all programs like mentioned in my previous post.

To do that you will need to enter similar commands for every other package name you want to remove.

Unless you are an experienced linux user, I think the easiest way to free space is to uninstall these bigger programs as described above, by using the desktop.

After that you can fiddle around at the command line and remove the desktop environment.

If something goes wrong, you can always flash the amibian image again and start over.

First, you do have expanded the sdcard in order to utilize all the space?

Secondly, I would strongly recommend considering getting a bigger microsd card if you are this tight of space.

For getting more space, I dont recommend uninstalling the desktop. The installed environment is LXDE, which is a lightweight desktop and I dont think it takes so much space anyway.

And, you might end up needing it later. For my installation, the usb-drive suddenly stopped showing up in Midnight Commander, so I need to use the desktop to copy to/from my drive.

What you can do, is to start the desktop and from the preferences menu, open the Add/Remove software program.

Then search or browse through and untick components that are safe to uninstall. Like the Chromium web browser (about 350MB in total), VLC (55MB), Gimp (112MB), Kodi (70MB),Qmmp (10MB), Scratch (47MB), KolourPaint (10MB), Geany (10MB).

This alone should free around 650MB, and its probably other packages that can be safely removed. You might not need all the other emulators, so some of these can be uninstalled as well.

I think first there must be a linux driver compiled for RPi that works with your hardware.

Secondly Amiberry must add support for it.

If you look at the WinUAE GUI there is a specific IO settings where you among other settings also have some Midi settings. This part is not included in the Amiberry GUI, so its most likely yet implemented.

@anbjorn.myren After doing some research I found this discussion:

https://www.raspberrypi.org/forums/viewtopic.php?t=196895

Using Alsa they were able to get the pi to talk to the Korg midi device. Now if this is relevant maybe it would help Gunnar et al. to build midi support into Amibian so AAmiga midi software could connect? Being ignorant of what this might take I would wait to hear from Gunnar or others to respond. I do appreciate the help you a have given. I think that running Amiga on the Pi and having midi control would be extremely cool! Not sure it has been done on other emulator except possibly FS-UAE.

@cabissi Same thread as those instructions you refered to.

The whole thread can be found at this link:

https://eab.abime.net/showthread.php?p=1384683

@anbjorn.myren Thank you! That was exact;y what I needed.. Minus some missteps with graphics resolution on my monitor I have it running just like your 2nd and 3rd videos. WooHoo! I will say that emulation is not for the faint of heart!😉

I have been tweaking the video settings and I have it running well. It first ran with those awful colors, but after getting resolution and colors set to 32 Google looks more normal. Still my website is weird as the image should be red and black. Very touchy frequently throwing Guru Meditation errors or locking up. Is that your experience or have you figured out a way around this? Thanks again

Chris

Fs-uae is preinstalled and available from the desktop environment. It does look like it have support for setting it up with a cyberstorm-ppc card. I have not tried it myself though. But I guess it will be quite slow. I did once set up WinUae with OS4.1, and even that was just at the limit of being usable.

I just gave it a try with fs-uae. It will start the emulator, but will complain about "error loading qemu plugin"

The qemu plugin, as found at the fs-uae website for download, does state that it works on windows, macos and linux. I suspect that means linux-x86, so that the archeive will not work on the Raspberry.

There is an old thread on amigaworld, and one user claims to have it running, but the qemu ppc plugin needs to be built by the user himself.

The thread is from 2017, I just made a post there asking about that plugin: https://amigaworld.net//modules/newbb/viewtopic.php?topic_id=42243&forum=8&2

Thank you so much for doing that much work to help me out. I found this link:

http://www.michaelminn.com/linux/notemidi/ Which says talks about a Linux driver "NOTEMIDI: whiich uses ALSA for seriaal port access. There is a lot more there but I will need quite some time if I ever understand it all.

Resolved this now. The default config path as set up in amiberry is /home/amibian/Amiga/conf/ and this is where the config files are saved.

Now I copied my autostart.uae file, as well as my default.uae file into /home/amibian/Amiga/Emulators/amiberry/conf/

After this it does autostart into workbench.

@anbjorn.myren thank you!!! This was driving me insane! <3

Make sure the paths are set correctly.

@Gunnar I have used the default paths, and these are the same dirs as I have copied the kickstart roms files to, and the conf path is also the deafult one.

I noticed that the /home/amibian/Amiga/Emulators/amiberry/controllers/ folder was missing. The retroarch.cfg file was also missing.

I just create the missing folder, and an empty retroarch.cfg file, but still no autostart.

When I start amiberry, it will start with the GUI Configuration tab open, and the default config is highlighted. But the config is not loaded.

You are right. I just tested SysInfo and compared it with the SysInfo numbers in Stephen Jones youtube video that was done with a Rpi 3. I get almost 3 times higher score on my Pi4.

Thanks, turning off overscan fixed the GUi.

I did test various configurations and the most I could get so far was 218mhz with fastest, and 291mhz with turbo.

I got mine rather quickly. I think this is done manually, and since its weekend it might take a day or two. Just be patient.

The Pi 4b arrived today, so now I can answer my own question.

Turns out there is no need to install lxde, because its already installed and configuref.

Just write startx at the commandline and you are there.