I'm trying to install amibian 1.4 on my raspberry pi 4B, it seems this is not compatible with eachother. Or am i doing something wrong?
0
crossconnect4u
Oct 8, 2019 · Edited: Oct 8, 2019
1.4 is not compatible with Pi 4 or Pi 3A+. 1.4 works fine on a Pi 3. 1.5 final will be and is still in development. 1.5 beta no pi 4 either. But did at one point have uaegfx working on beta. Make sure to get good cooling as it is reported to cause the Pi4 to run warm so far. You can install FS-UAE on Raspbian desktop in the mean time as I have done.
marcel_smeding
Oct 9, 2019
thanks for the reply, i just have to be patient i guess... :0)
Dave
Mar 30
Hi sorry to jump on with a different question it's just that I noticed you said you were running fs uae, I am on my pi 4 but I can not run in full screen without display refresh speed and input lag, have you got round this. I also emulate the ST and was able to resolve it on there so I am hopeful. Apologies again I'm struggling to find info.
crossconnect4u
Mar 30
Amibian 1.5EE is out. Supports Pi4 and uses FSUAE (custom build I believe) Click flag to change keyboard layout. I have noticed lag on Pi4 with v1.4 when running 4 instances of FS UAE at the same time with Compiz cube, but up to 3 I have been fine. Full screen fine. I enabled OpenGL (in raspiconfig I think) you can also use a Linux shell command called ps (process) or the GUI program “monitor” to look at cpu consumption. Overheating CPU will slow everything down 4 sure. Make sure to use a fan With your Pi4. Even a desk fan. There is a temp monitor applet you can add to your menu to monitor temp graphically. I found out my errors and corruption were due to a failing hard drive on my tower I used for making SD images.
crossconnect4u
Oct 9, 2019
Me too... chomping at the bit to get mine. But I have a Pi 4, 3 Pi 3’s, a Pi 2 68k Apple ( My “Apple Pie” ) and other devices, and plenty of things to develop in the mean time... including faq related stuff in the forums and figuring out what is causing all these damn write errors corrupting my files!!! I have had to reload emulations 4 or more times. Even DietPi/Amiberry had issues. Do not recall having many issues with Raspbian. I back up frequently and am making an image library for rapid scratch installs and hdf repository so I can reburn image instead of re-install - with images already intact and pre-configured, and quickly add internet and music files and adf’s and WHDload games. I expect others to have better reliability than me. I think I have something going on locally.
cbm.amiga1955
Oct 12, 2019
Could it be due to improper shut-downs?
crossconnect4u
Oct 12, 2019 · Edited: Oct 12, 2019
There is that possibility... but even the emulator itself has been corrupted not just the hard files. I power off after shutting down script. I do sometimes reset when I change hard files in the config.
P.S. the more i think about it, i may have done both ways...i should try watching my behaviors more closely to see for sure...
crossconnect4u
Oct 12, 2019 · Edited: Oct 12, 2019
The only thing I expected to get lost is directory cache on the Amiga images. This possibility has occurred to me though, thanks. Have already started to pay a bit more attention to this as well. I have also done write-read tests on a PC and found cards bad, as well as successful tests and then fails in operation... I will confess however to not shutting down the emulation between reboots, changing hardfiles or profiles ( I do Amiga Reset ) etc...
stanond55
Mar 6
I downloaded and am using the beta version 1.5 and so far so good. I entered Ambian desktop and the key board is off. I could not change it to US where shift 2 gets me the at sign. Even after using sudo dpkg-reconfigure keyboard-configuration and sudo dpkg-reconfigure keyboard-configuration. Suggestions please. My hyphen key is ö. Icelandic keyboard maybe
crossconnect4u
Mar 30
Clicking on the flag will change between 3 preset keyboards. Icelandic Nordic and US I think - something like that... I have not been able to make it stay on a US keyboard yet. It keeps resetting. My suspicion is Gunnar put it in there with a script configured that way to maintain sanity while developing Amibian 1.5ee and forgot to take it out. Not sure.
cabissi
Apr 4
This bug is mentioned In menu help screen. The fix is explained as well. I moved the microSD card over to my PC and used notepad++ to fix it (All 3 options are US now). The fix can be done on the RP as well. Good luck.
1.4 is not compatible with Pi 4 or Pi 3A+. 1.4 works fine on a Pi 3. 1.5 final will be and is still in development. 1.5 beta no pi 4 either. But did at one point have uaegfx working on beta. Make sure to get good cooling as it is reported to cause the Pi4 to run warm so far. You can install FS-UAE on Raspbian desktop in the mean time as I have done.
thanks for the reply, i just have to be patient i guess... :0)
Hi sorry to jump on with a different question it's just that I noticed you said you were running fs uae, I am on my pi 4 but I can not run in full screen without display refresh speed and input lag, have you got round this. I also emulate the ST and was able to resolve it on there so I am hopeful. Apologies again I'm struggling to find info.
Amibian 1.5EE is out. Supports Pi4 and uses FSUAE (custom build I believe) Click flag to change keyboard layout. I have noticed lag on Pi4 with v1.4 when running 4 instances of FS UAE at the same time with Compiz cube, but up to 3 I have been fine. Full screen fine. I enabled OpenGL (in raspiconfig I think) you can also use a Linux shell command called ps (process) or the GUI program “monitor” to look at cpu consumption. Overheating CPU will slow everything down 4 sure. Make sure to use a fan With your Pi4. Even a desk fan. There is a temp monitor applet you can add to your menu to monitor temp graphically. I found out my errors and corruption were due to a failing hard drive on my tower I used for making SD images.
Me too... chomping at the bit to get mine. But I have a Pi 4, 3 Pi 3’s, a Pi 2 68k Apple ( My “Apple Pie” ) and other devices, and plenty of things to develop in the mean time... including faq related stuff in the forums and figuring out what is causing all these damn write errors corrupting my files!!! I have had to reload emulations 4 or more times. Even DietPi/Amiberry had issues. Do not recall having many issues with Raspbian. I back up frequently and am making an image library for rapid scratch installs and hdf repository so I can reburn image instead of re-install - with images already intact and pre-configured, and quickly add internet and music files and adf’s and WHDload games. I expect others to have better reliability than me. I think I have something going on locally.
Could it be due to improper shut-downs?
There is that possibility... but even the emulator itself has been corrupted not just the hard files. I power off after shutting down script. I do sometimes reset when I change hard files in the config. P.S. the more i think about it, i may have done both ways...i should try watching my behaviors more closely to see for sure...
The only thing I expected to get lost is directory cache on the Amiga images. This possibility has occurred to me though, thanks. Have already started to pay a bit more attention to this as well. I have also done write-read tests on a PC and found cards bad, as well as successful tests and then fails in operation... I will confess however to not shutting down the emulation between reboots, changing hardfiles or profiles ( I do Amiga Reset ) etc...
I downloaded and am using the beta version 1.5 and so far so good. I entered Ambian desktop and the key board is off. I could not change it to US where shift 2 gets me the at sign. Even after using sudo dpkg-reconfigure keyboard-configuration and sudo dpkg-reconfigure keyboard-configuration. Suggestions please. My hyphen key is ö. Icelandic keyboard maybe
Clicking on the flag will change between 3 preset keyboards. Icelandic Nordic and US I think - something like that... I have not been able to make it stay on a US keyboard yet. It keeps resetting. My suspicion is Gunnar put it in there with a script configured that way to maintain sanity while developing Amibian 1.5ee and forgot to take it out. Not sure.
This bug is mentioned In menu help screen. The fix is explained as well. I moved the microSD card over to my PC and used notepad++ to fix it (All 3 options are US now). The fix can be done on the RP as well. Good luck.