Do a full backup with LibreELEC's Back/Restore tool, just in case.
Swapping out the HDD/SSD from the AMD to the Intel is an option. The Intel UEFI should (still) have a 'legacy' boot option AFAIK.
Otherwise, do a fresh install (v9.2.0) on the Intel and restore the previously made backup.
Some little trouble.
Go get your support from wherever you get your illegal add-ons.
This is not the forum where you will find any sympathy for your add-on problems.
I myself use Ubuntu's Disk Image Writer for LibreELEC images. I never used anything over 16GB for LibreELEC though. It's possible that a 128 Gig SD card has never been tested with LE's own tool, although size shouldn't matter when writing a disk image.
You sure you are using the correct image file for the RPi 4 ? (just asking..)
Have you tried a different tool to whatever it is you're trying to do?
Hello. Question on the same topic.
Why are you putting your text in a code tag..?
I bought a laptop Dell PRECISION M4800.
That is a laptop with a NVIDIA Quadro® graphics card. And possibly not supported by the regular Nvidia graphics drivers.
And also, it's not very polite to "hijack" someone else's forum thread for your own problem computer. Next time simply create your own forum topic.
LibreELEC has a "Wait for network" option. Has that been enabled?
If the network is not up yet (because LibreELEC may have booted too quickly), then the database connection will also likely fail.
The RPi2 has 512MB internal memory, of which Kodi takes up roughly half. So I don't think a swap file will help, also because a SDcard will be painfully slow handling a swap file.
Ethernet drop outs I saw once or twice on my RPi4-4GB with Raspbian running the Kodi application doing some 4K video. This happened with Kodi's internal NFS mounts which is usually okay. You could try to create system mounts in LibreELEC instead, and point Kodi to those mounts for your source(s).
probably caused by your "massive" DB being loaded into a mere 1G RAM.
I don't think that an entire database is ever loaded into internal memory.
Loading a humongous number of movies or music artists into a Kodi listing might take its toll though.
How do I start from here?
2019-04-11 12:28:42.297 T:1937336768 NOTICE: Disabled debug logging due to GUI setting. Level 0.
It's always good to enable debugging so the Kodi log is more detailed. Do so, restart Kodi, and reproduce the error(s) for a new log file.
I'm pretty sure that of all RPi users, not many of them will attach a corded USB keyboard. But if that works for you, that's fine of course.
As we have no crystal ball here, yes we would like to see the full, debug-enabled, kodi.log file.
Instructions:
Really, a poll..?
If you want a debug log, you can also SSH into the RPi4 and upload the log file(s) from the command line. No need to directly connect your keyboard to the RPi4.
Use pastebinit ~/.kodi/temp/kodi.log to beam up your log file.
Quote from floraoliviaWant to also...
Thanks for it...
It's really great men...
Why are you on this forum? So far, you have made 3 posts which are pretty much useless.
Please don't waste our attention with replies which have no sense or meaning.
Raspbian is a full-blown OS, while LibreELEC has only those things that are "on a need-to-have" basis. But perhaps that Buster has received a number of updates that are making certain things smoother. Or perhaps you are using a quicker SD card for Buster?
"Please use a normal user account"...
Then it's too bad that LibreELEC only has one user: root.
A v18.6 release is very much possible, although no ETA date is known.
The onboard gigabit ethernet should be more than fine. Using wifi with any HTPC device should be banned in my opinion. 
You can change the CEC port number in the CEC settings of the Input Device in the Kodi GUI menu. Reboot and try again. Not sure if this works.
It's really great men...
Great men? Tall people?
We have no need for useless comments.
