@Chris
Here it is.

Amiga pointer archive https://heckmeck.de/pointers

@kas1e

I don't think i have this issue, how do i see it?

@tao

Yes isn't that typical that the only driver is for hardware that is not working on X5000

But it isn't really the only option.

We used to have a driver for NVMe devices.
iirc the author removed his driver from os4depot because of for me unknown reasons but maybe he will change his mind later on.

@tao

The linux nerds have used more cards on the X5000 than anyone else and the Sil 3132 is the only one i ever seen beeing reported as invisible to the system, that one was reported about already in 2016.

@Kyle

Quote:

Thats strange.
I did not understand where exactly in the boot process it ends up with a gray screen, is it before or after the Aos4.1 splash screen?
I'm just asking because if it's right after amigaboot have loaded the kickstart it's generally a kickstart problem, if it's after the splash screen it's something else.


I think this might be a case when a serial cable is needed to see where it fails without guessing like crazy.

There's "never" a need to reinstall Aos unless the harddrive is broken so i'm sure we could get you going again if we figure out where it fails.

A separate thread might be needed here :)

From the "avail.doc"

"The FLUSH option is obsolete and does nothing."

If the released version is still 54.11 i guess it's this one ->
Enhancer 2 makedir bug

@jabirulo

Afaik powerprefs was only for rx cards.
I'm pretty sure i have read it from hans sometime and it would for sure not work on the radeonhd i was using before rx.
(I never upgraded to radeonhd v5)

@MazinKaesar

And what config file are you editing exactly?

I remember that it was a bit confusing to find out what file to edit for runinuae.

I cant say what file to edit as i dont have any system here to check it,

But i do remember how i found it, (instead of reading the documentation) i just added some more memory to my emulated envirment in different config files and launched wb until i had the desired amount of memory.
Then i knew i had edited the correct file.

My best guess is that you did not install some needed components for (aeon)updater.

It's good that you were carefull when installing the enhancer software as some of it should never be installed but you we're too restricted when doing so and missed some needed compoent.

There is some thread here where safe components is listed but you could also try to install this https://wiki.amiga.org/index.php/Enhancer_Software_Core

iirc it's safe components and will get updater running.

My best guess is that you did not install some needed components for (aeon)updater.

It's good that you were carefull when installing the enhancer software as some of it should never be installed but you we're too restricted when doing so and missed some needed compoent.

There is some thread here where safe components is listed but you could also try to install this https://wiki.amiga.org/index.php/Enhancer_Software_Core

iirc it's safe components and will get updater running.

55-56 degrees is what i'm usually at with my 020.
I have the old mcu firmware that made the fan go crazy already at low temperatures so i had to add extra hardware to slow the fans down.

This is how crappy the original cooler & thermal pad looks like.

The fan speed is programmed into the much and can not be changed.
The mcu will also make sure to shutdown the computer at a temp that has been programmed in.

However you can power the fan from another source to make it spin faster.

But the recommendation about replacing the thermal pad should be better.
I checked ny pad after 5 years and it was totalt worn out.

@sailor

A fresh OS4.2 iso will solve all these problems :)

There is another scenario when updated kickstart modules and kicklayouts becomes problematic.

I don't always have my kickstart folder in sys:kickstart

But having an "novice" mode and advanced mode would be better for kickstart configurations where novice mode would be used most of the time with a standard kickstart-layout that just works.

The amiga keyboard does not speak ps/2 keyboard protocol.
I don't know of any easy to find parts to convert the amiga keyboard into ps/2.
The only thing i know about is for A1200 keyboards.
The one for the infinitiv keyboards that connects directly to the keyboard membrane before any logic translates it into some serial protocol.
It might be tricky to attach it into the A2000 keyboard membrane even if the pinout probably is the same and they are probably rare.


However it's easy to convert an A2000 keyboard into usb with ready made solutions or just make one with arduino.

From there it should work with an ACTIVE usb ps/2 converter.
Most of the adaptors are passive and will not work.

If you know how to code arduino or similar it would probably be easy to extend some existing project into something that translates it directly to ps/2

@Tuvok

recommending sfs as the main filesystem on an X5000 is atm a little bit "dangerous" if the user does not have knowledge about how to prepare it's own bootmedia or has got access to a ready made bootmedia.

Thats because the enhancer package is required for the X5000 to get access to a working sfs filesystem.
When booting from the ordinary OS4.1 iso you will not be able to access SFS partitions.

Not a big problem for anyone who knows how the kickstart loading works etc but probably too much for the inexperienced user.

@SteffJay

You probably have some "fancy" keyboard that uboot does not like.

Exchange it with some cheap generic keyboard and you should be able to access uboot.

@tekmage

If you can access dropbox try download this fonts archive
Term Fonts

@tekmageQuote:

I don't have a list but about 10 years ago i tested alot of them and the one i wanted to work did not.
That was Ncomm.
I found surprisingly few alternatives that works that was not crap.

I settled with "term" in the end https://aminet.net/package/comm/term/Term

It was good but for unknown reasons for me the fonts supplied in that archive did not work with os4 and leads to a crash. (atleast 10 years ago)
Someone fixed the fonts with https://aminet.net/package/text/font/Typeface124 and gave a copy to me but it was also possible to run term if the fonts directory in the archive is renamed/deleted.(or possibly change used fonts in the prefs file)