Yeah, I want to wait and see how this works for other people before I start making modifications.

There is meant to be a device coming soon which will convert the keyboard to a classic Amiga keyboard. Presumably this means that RAmiga will become a key that registers a Qual/Code in input.device.

In any case, as a last resort - I am thinking of opening the case up, bridge the RAmiga key with the Boing key / cut traces so that when you press the RAmiga key it is effectively the same as pressing the Boing key and then make a modification to AmigaKeyRemapper 1.3 to treat the Boing key as if it was the RAmiga key since the Boing key does actually register with input.device.

But, I want to wait an see what situations other people have.

I am just documenting my situation.

Anyone else who actually has the kb, feel free to help me and make things better.

I have mine: https://forum.hyperion-entertainment.com/viewtopic.php?t=4884

Also, you will probably need to swap Amiga and Alt keys in Prefs/Input since the Right Amiga key registers nothing in input device. I tested it out. That key does not register a qualifier code or a code. I was hoping I could extend AmigaKeyRemmapper to handle the situation for the Simulant keyboard.

This means that in order to perform a full reset which is my only option since I use an RX card then I need to use the drop down menu and cannot use the keyboard.

Other than that, it is good.

EDIT: oh, I forgot the most important thing. I had to remove bootkeyboard.usbfd from the kickstart modules, otherwise, for whatever reason, the Simulant keyboard uses that driver instead of the HID driver. If you don't do that, the keyboard does not work. Also, if you boot into UBOOT, you get the POLL issues and UBOOT is hard to use. Since we do not do that much, not too much of a problem so keep your original kb for that.

Broadblues suggestion works.

Not sure why I was doing it using Get anymore.

Thanks all.

So long as holding CNTRL works then at least there is a solution.

I am referring to an application that literally:

and uses it in the way described in the only entry for "LINECMP_GetClass()" in the SDK.

For this to work the symbol must exist somewhere or be redefined to something else. When I search in the SDK, entire, for "LINECMP_GetClass", the only thing I see is a match to a documentation file and some example files. Hence, I receive an undefined reference.

I cannot actually find this function even as far back as 53.30.

Is it external to the SDK? I also cannot find any Reaction sources on AmiNet/OS4Depot.

Thanks. I solved it now by just attaching to my X1000.


So, does this also not work if you have a RadeonRX?

Right, so I guess I will have to build with an older SDK.

Okay, now it seems to be okay. I plugged in the X1000 keyboard. That was all really weird. Thanks for the thread link. For some reason I did not provide a reason for why that "HALT" message appeared.

EDIT: I think I performed a full reinstall, actually. I should have documented that in the thread which I normally do. I think I went with SFS2 instead of NGFS.

How can I boot with no startup sequence?

I have unplugged everything. Apart from the power. Same thing. Then I attached serial, see above.

I have tried to use the emergency usb boot in the bottom row of rear USB slots, as well as the middle row. Same thing.

I have removed the SD card to see what happens, in that case the system does not come on at all which suggests that the sd card is not all that bad...

When I power the machine on with the halt message I see that the top 6 leds are on, the highest one green. The two lowest are dimly lit.

What the hell.

I guess... somehow the SD card is now corrupt? I don't have an image for the SD card.

I also cannot see a single search on the Internet with the text "Couldn't find a boot loader. Halting".

Hi, why am I seeing this message all of a sudden. I power on, see the AEON screen and then see this message on a white background.

Just before this happened, I was in uboot. I was trying to remember how to start the system without startup-sequence.

I was using uboot which was a little glitch due to the new keyboard I am using. The POLL error messages showing and a glitch menu. But before it was still usable.

I navigated to the menu option with "Boot" in the name, I think it was the second to last entry. Pressed enter. I got this message and it just hung. So, I reset the machine, now I get this message all the time. I powered off for 10 minutes and from cold it still shows itself.

___
EDIT (at time of comment #15)

See also: https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=8857
https://forum.hyperion-entertainment.com/viewtopic.php?t=4542

Neither of these have a solution. It just seems to have randomly happened and randomly stopped. Going from NGFS to SFS2 didn't really help. Will consider using a brand new SATA SSD next. As much as a doubt that it is due to badly connected SATA cables, my doubt becomes less, but that confuses me, because those cables literally do not move.

Perhaps I will try a combination of a new SARA drive and some "gold plated" (if such things exist) SATA cables, hot glued all-to-hell into the ports.

I have some code that I am trying to build and it uses the function

through the

interface.

I get an undefined reference to this function which seems to make sense since I cannot see it in my SDK at all.

...

Maybe I will have a look through the old SDKs.

You will get the RC of 5.



You will get the value 0. This is not desirable. I expected the value 5.

https://forum.hyperion-entertainment.com/viewtopic.php?t=4884

Hi. This link is not to do with KVM.

I notice the time out polling too. When the keyboard is not working I see the keyboard being driven by the boot driver, not hid.usbfd.

Do you also see this @kas1e.

What is the solution in a nutshell to save me reading... get a cheap powered USB hub, bung the USB hub into any USB port on the X5 and then bung the keyboard into the powered USB hub?

@kas1e

At the moment the way to build the SDL2+GL4ES library is to pull down SDL2 and then apply the changes to that and then build. This is all described above.

What I wanted clarity on is on:




You authored those changes. Did you do these changes or someone else?

As well, we know that modifications need to be made after these changes applied to the base SDL2 library, e.g. the active window function because they are a little out of date.

My question is: is there a better method than making a diff file of 4d504983f3876bdf714af20a8bdfed757831b1d5, applying it to the very latest SDL2 branch (currently version 2.24) and then fixing up some of the differences.

Looking at the SDK and their descriptions it looks like the (only?) way to get the kernel debug level and set it is to use exec/debug/GetDebugLevel(), check it and then - in the case that I want to set it to something, run DOS's RunCommand() as if i had typed:


?

It seems odd that there is a function to get the debug level but not set it without pretending to run a command.

===

As for KDEBUG, I would have expected

To provide the values for fields, but it does nothing. I am not sure the description for "status" is as good as it could be.

===

There was a command to run to get all of your UBOOT env variables; that, or there was a screen in some GUI tool, but I forget where that is.

===

I also managed to make KDEBUG crash when performing the following:

Right, but there is no such thing as a "soft" reboot for AmigaOne using Polaris, right?

I guess my question can be put like this:

In the event that my system freezes: whether this is a full lockup with the OS locked up or whether it is just a GFX freeze where the OS is still running in the background... whatever - just a freeze. How can I get the generated serial debugging information in such a way that it does not require an external computer?