I agree there is no real need for more than one NVME. From my side it is only pure interest what is possible. To have one in Amiga is really great thing!

Interesting. I've read that the SAM460 was capable of booting Linux and Amigaos4 from microSD. But I didn't know that the X5000 was capable of doing to same for at least Linux. Would be nice if it can also boot the Amigaos4 kernel with modules from microSD.

It is not possible to boot from NVMe at the moment, so the dual NVMe use case for amigaos and Linux is unclear to me.

Have this hangups before but goes away when change to internal ethernet onboard card on my X5000..
I take out my pci ethernet card from.pci slot too... So only use internal ethnet.

I used to have a slightly different WB boot problem. More often than not, my X5000 would boot into an empty grey screen with an empty screenbar.

I removed X-Dock from WBstartup but the problem persisted. In the end it turned out that, over time, I had installed a few AHI drivers for cards I don't use, and one of these seems to have been causing the hang-up. Since I removed all unnecessary drivers from DEVS:AHI and DEVS:AudioModes, I've never had such a problem.

In the WBStartup, in the Tooltypes Icon "X-Dock" have you tried to set the Priority value -126 ?

amiganuts wrote:Lets try this another way. Has anyone successfully added a backlit keyboard to their X5000? If so, what brand and model? I can just return this one I bought and get a compatible one. I was thinking of trying a Logitech or Apple. According to the compatibility list, these USBs work but it does not mention backlit.

Sorry for being lame but what is this? I have no clue...

Not all modes will work. Here is what I did. From the GUI use the Audio Mode button and try selecting vaious selections from the list that appears until you find one that works. Note that if you select one that doesn't work all the gadgets will be ghosted and you will need to restart the program. On my system non of the 16bit selections would work. I had to choose a 32bit one. It depends on the sound card you are using. Once you find a mode that works then convert it's Hex value to decimal and you should be able to use it in the tooltype setting. Note that once you set if from the tooltype you can no longer change it from the GUI because the Audio Mode button gets ghosted. Hopefully this will help you out.

There are many possibilities, I can only guess which one(s) might apply.

The input you used was either microphone or line input, either of these can be overloaded by a headphone connection. I suggest trying lower volume levels on the source device. A "best possible" solution would be to use line level outputs to the blue connector. It would be SO MUCH EASIER if we had proper "VU Meters" for AHI inputs and outputs. (note, we DO have proper VU meters for X1000 and A1222 builtin audio. I've used them extensively for about a year now. They just haven't been distributed yet)

The method itself is solid. The noise is either a level problem (most likely) or a poor connection, or possibly a noisy source. The "device level" software is doing a simple copy, it's not adding or subtracting any noise.

To record directly from a sound card input:

Copy AUDIO:SECONDS/10/TYPE/AIFC/B/16/F/44100/C/2 sample.aifc

I also wonder why my idle power consumption is so much higher compared to some of the other tests in this thread? My guess is the 2x mechanical SATA harddrives. Any thoughts on that?