Xorg server not starting, gpu not supported?

Derpaphobia · December 1, 2018 at 12:42 PM

Hi! I installed the reborn remix build back at the start of october and it worked fine, however.. I recently swapped out the drives of the computer and now when I want to reinstall, it wont work.

First of all, I have to run the installer with nomodeset, which is fine, then I have to start the OS with nomodeset, which is also fine and I don't mind, but then it refuses to start Xorg server and just... tries to start it over and over again.. without booting into the OS.

Motherboard: MSI FM2-A75IA-E53

CPU: AMD A4 5300 3,4 GHz FM2

**Klojum** · December 1, 2018 at 1:34 PM Official Post

Quote from Derpaphobia

CPU: AMD A4 5300 3,4 GHz FM2

Your AMD problem caught my attention. I too have such a AMD A4-5300 apu machine, though with a different motherboard (Gigabyte F2A88XM-HD3). I've installed Milhouse's latest build #1130, and it seems to boot & work just fine...

It wasn't a clean and new install though, I had already installed LibreELEC earlier. I have a dualboot with Ubuntu 16.04 and LibreELEC. I created the two partitions for LibreELEC manually and edited the GRUB files after that.

Derpaphobia · December 1, 2018 at 2:05 PM

Yeah, so.. last time I installed Libreelec, I had Mint running on the computer before, and if I remember correclty, installing mint wasn't without problems either.. I just can't remember what fix made it possible. But it seems like the motherboard is the problem here....

**5schatten** · December 1, 2018 at 2:19 PM

Quote from Derpaphobia

Yeah, so.. last time I installed Libreelec, I had Mint running on the computer before, and if I remember correclty, installing mint wasn't without problems either.. I just can't remember what fix made it possible. But it seems like the motherboard is the problem here....

Get a recent linux Mint version & grab the dmesg output -> so we maybe can figure out what's happening behind the scenes if you can't access the log files at your LE installation

Derpaphobia · December 1, 2018 at 6:09 PM

Well.. I can access SSH if that helps somehow? I'm going to try mint, Ubuntu, then dual booting with Ubuntu just as klojum, trying to install libreelec after each

**5schatten** · December 1, 2018 at 6:40 PM

Quote from Derpaphobia

Well.. I can access SSH if that helps somehow? I'm going to try mint, Ubuntu, then dual booting with Ubuntu just as klojum, trying to install libreelec after each

does smb come up? because then you could grab the log zip in \\your-device\logfiles

Derpaphobia · December 1, 2018 at 7:00 PM

Can I set SMB as a bootcommand? I get stuck before I get into the OS but it's enough for SSH to run via the bootcommand in syslinux

**5schatten** · December 1, 2018 at 7:29 PM

Quote from Derpaphobia

Can I set SMB as a bootcommand? I get stuck before I get into the OS but it's enough for SSH to run via the bootcommand in syslinux

if you can start ssh & get the dmesg output that's probably a good start.

Derpaphobia · December 2, 2018 at 12:29 PM

Uploaded the dmesg of the reborn remix below

**5schatten** · December 2, 2018 at 1:33 PM

Quote from Derpaphobia

Uploaded the dmesg of the reborn remix below

Well you've manually set nomodeset? Because this disables your GPU drivers so you should not expect to get a working system

Code

[    0.000000] Command line: BOOT_IMAGE=/KERNEL boot=UUID=5C03-CBEE disk=UUID=b1dc2681-296e-447c-83d9-c7e8532a6718 ssh quiet nomodeset

Code

[    0.051262] You have booted with nomodeset. This means your GPU drivers are DISABLED

Code

[    1.329464] [drm] VGACON disable radeon kernel modesetting.
[    1.329469] [drm:radeon_init] *ERROR* No UMS support in radeon module!
[    1.329516] [drm:amdgpu_init] *ERROR* VGACON disables amdgpu kernel modesetting.

Derpaphobia · December 2, 2018 at 3:34 PM

Without it, I'm getting a quick black screen with a bootloop, gonna try without and see if I can get another quick dmesg off

**5schatten** · December 2, 2018 at 4:53 PM

Quote from Derpaphobia

Without it, I'm getting a quick black screen with a bootloop, gonna try without and see if I can get another quick dmesg off

Well with this nomodeset flag it's basically useless because it "covers" the root of the problem.

EDIT: well I guess your board is somewhat doomed

Anyone using an AMD APU with Ubuntu 16.04/10 (driver issues)? | Overclockers UK Forums

restart loop after fresh 16.04 installation

[ubuntu] PC will not boot; acpi core revision error

3.95.5 AMD richland A8 not booting · Issue #3093 · OpenELEC/OpenELEC.tv · GitHub

72921 – DPM Power Cycle with AMD A8-6600K & MSI FM2-A55M-E33

Maybe you can try radeon.bapm=1 or radeon.dpm=0 on the kernel command line to see if this helps?

104963 – MSI MoBo A88XM-E35 GPU Trinity A8-5600K (Aruba HD7560D) Boot loop without radeon.dpm=0

Derpaphobia · December 2, 2018 at 8:28 PM

Yeah, I've read about the stupid msi motherboards, anyhow radeon.dpm=0 seems to work! I don't know what it does but I'm in! Thank You for all the help!

**5schatten** · December 2, 2018 at 8:45 PM

Quote from Derpaphobia

Yeah, I've read about the stupid msi motherboards, anyhow radeon.dpm=0 seems to work! I don't know what it does but I'm in! Thank You for all the help!

Don't get to excited. Does radeon.bapm=1 work? Because afaik dpm=0 will disable power management for your cpu.

Derpaphobia · December 3, 2018 at 9:12 AM

Nope bapm=1 does not work

**5schatten** · December 3, 2018 at 11:00 AM

Quote from Derpaphobia

Nope bapm=1 does not work

Well okay then it's probably a dead end. This bug exists for years now and you have already the latest bios so this workaround is probably the best you can do

Derpaphobia · December 3, 2018 at 11:30 AM

Yeah I guess, oh well.. it's a really old computer anyways so this is fine by me, Thank you for all the help!

**5schatten** · December 3, 2018 at 12:53 PM

Well as long as it runs your stuff it's fine I guess.