SDDM/Xorg Issues

Bugattikid2012 · 2017-12-14 01:42:13

Recently purchased this laptop.

Installed Arch once again pretty much adhering to the beginner's guide (Following archives of the old guide) as I always have. I installed plasma, sddm, xorg-server, mesa, and a few other things, but I can't get sddm to successfully start up. When I try to do so, it'll pulse the screen at somewhere between 20-30 hz, and can screw up what I type into a terminal (it makes some keyboard input not register). I don't have internet on the device itself yet as it has no ethernet, and my only USB network card only seems to be picked up when I'm in a live OS from my USB. I figure I can figure out my network card(s) once I get to a desktop environment and I can use networkmanager's GUI, but if necessary I can try to figure that out before we proceed. At the moment I just use the live OS and chroot into my OS to install packages.

http://termbin.com/a79d

http://termbin.com/yu5y

I appreciate all of the help that I receive, and if you need any more commands to be run (or more information), I'm more than willing to provide them. Thanks a ton.

Trilby · 2017-12-14 02:21:30

Bugattikid2012 wrote:

Installed Arch once again pretty much adhering to the beginner's guide (Following archives of the old guide)

"pretty much" meaning not entirely? Why would you intentionally follow an outdated guide? How old? What is different in it from the current one?

The xorg log looks like you've not installed the proper video driver.

Last edited by Trilby (2017-12-14 02:21:47)

fsckd · 2017-12-14 02:58:01

The Beginners' Guide was always in flux. People were constantly changing it. Saying, "I followed the Beginners' Guide" meant nothing since its contents changed every day. This was one of the reasons why it was dropped. I strongly advise you follow the latest version of the Installation Guide.

Did you see the guide on the wiki for Xorg?

Bugattikid2012 · 2017-12-14 03:55:22

There's no material difference from the way I installed it from how it is today, and even if there was a difference, there's no reason why it shouldn't work. These guides have been followed by thousands of people over many years with the core process remaining the same. This certainly isn't the first time I've installed Arch and it certainly won't be the last. I do not believe the install process has anything to do with the issue.

I also think the driver is part of the issue, and that's why I posted this here. I can't install catalyst drivers to test it since I have to be root when using chroot without first getting my wireless connection set up. I have mesa installed but I don't see any drivers actually being put into use with lspci. I believe the Vega Mobile graphics card that I have is part of the issue, which is why I linked to it. Do either of you have any input in regards to this? Thanks.

Last edited by Bugattikid2012 (2017-12-14 04:19:08)

V1del · 2017-12-14 08:32:35

Kernel support for Vega cards has only been mainlined in 4.15 so will either want to wait, or install e.g. https://aur.archlinux.org/packages/linux-mainline to tide you over.

Bugattikid2012 · 2017-12-24 22:19:27

Is this only for Arch, or for the original Linux kernel?

Maybe I'm mistaken, but I see several sites saying 4.12 has vega support.

https://www.ubuntufree.com/linux-kernel … rovements/ Is just one of many examples.

Is this requirement of 4.15 specific to mobile Vega?

I found https://phoronix.com/scan.php?page=news … bile-Today this article which says AMDGPU-PRO can run mobile VEGA, but I haven't had any luck with this driver.

Last edited by Bugattikid2012 (2017-12-24 22:32:15)

seth · 2017-12-24 22:51:46

https://www.phoronix.com/scan.php?page= … C-Accepted
Since you're failing ati & modesetting driver and no kernel module seems loaded for the GPU(?) it's reasonable to assume that your GPU isn't supported by either the radeon nor amdgpu module - yet.

xf86-video-vesa should get you a gui, but on software rendering.

Bugattikid2012 · 2018-02-08 22:50:19

I've updated to 4.15, and I have installed the xf86-video-amdgpu driver. Upon booting this, I had a large page of errors which was solved by disabling kernal mode setting in rEFInd. Trying to launch sddm as before resulted in the same exact issue that I had before. Is there any step in regards to the display code that I'm missing?

I also read that KMS is required for AMDGPU as listed here:
https://wiki.archlinux.org/index.php/AM … _early_KMS

I plan on doing light gaming on this machine, and I would really like to have the best performance I can. It is my understanding that the AMDGPU driver preforms the best. Is there any way to get this working, or would a different driver be better? While there were many errors, the one that seemed most relevant (and led me to the conclusion of KMS causing issues) was

acer_wmi: Unsupported machine has AMWO_GUID1, unable to load

followed by many ACPI errors that went away when disabling KMS. If anyone thinks these are relevant I can try to post them as well.

What should my next step be? Thanks.

loqs · 2018-02-08 22:53:47

Please post the whole dmesg and xorg.log from a boot without modesetting disabled.

Bugattikid2012 · 2018-02-08 23:14:38

I hope this is what you wanted. I'm not sure exactly how I am supposed to run dmesg from a boot where I have KMS enabled when I can't even get to a tty session, but I was able to run dmesg it with KMS disabled. If there is something else that you had in mind I'll be happy to try that as well.

dmesg:
http://www.termbin.com/2r95

/var/log/Xorg.0.log:
http://termbin.com/9zpd

Edit: It appears as if some of the errors that I thought disappeared after disabling KMS are still there. I must've missed them before. They're near the bottom, you can see the one I mentioned earlier followed by several ACPI Errors.

Last edited by Bugattikid2012 (2018-02-08 23:24:45)

seth · 2018-02-08 23:24:33

loqs wrote:

from a boot without modesetting disabled.

Bugattikid2012 · 2018-02-08 23:29:31

seth wrote:

loqs wrote:
from a boot without modesetting disabled.

I specifically asked how I can do this in my previous post. I have specified twice already that I do not know how to do this. A quick search doesn't lead to a definite answer.

Does journalctl pull from dmesg logs, or does it take other logs into account as well?

Last edited by Bugattikid2012 (2018-02-08 23:34:28)

loqs · 2018-02-08 23:41:42

Remove nomodeset from the boot options let the system boot as far as it can then reboot using nomodeset so you get a terminal.

journalctl -b-1 -k

Will provide the kernel output from the previous boot which is equivalent to dmesg (some minor formatting differences)
Also check if Xorg.#.log.old is the log from the boot without nomodeset and if so post that as well.

Bugattikid2012 · 2018-02-08 23:44:27

Thanks, I was able to find -b, but I was unsure as to if journalctl was exactly what we were looking for. I always thought journalctl was a more general system logger.

How will I know if Xorg.0.log.old is from nomodeset or not?

Last edited by Bugattikid2012 (2018-02-08 23:56:07)

Trilby · 2018-02-08 23:48:49

grep -o 'Time:.*' ~/.local/share/xorg/* /var/log/Xorg*

Or perhaps a bit nicer layout:

find ~/.local/share/xorg/ /var/log/ -name 'Xorg*log' -exec stat -c "%y %n" '{}' \; | sort

Last edited by Trilby (2018-02-08 23:51:34)

loqs · 2018-02-08 23:50:13

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System:  
Current Operating System: 
Kernel command line:

The Xorg.0.log.old should start with lines like the above check the Kernel command line if nomodeset is missing from the options please post it.
Edit:
Also with the journal output again near the top should be a line starting "Command line:" the boot to post is the one without nomodeset in the options listed on that line.

Last edited by loqs (2018-02-08 23:53:44)

Bugattikid2012 · 2018-02-08 23:59:07

The Xorg logs look more or less the same from a quick glance, but here it is anyways. Didn't see the message to check time/date before rebooting to post this, but it looks like this is a nomodeset boot afterall.
https://www.termbin.com/7h1e

journalctl -b-1 -k when the previous boot (-1) is the failed boot:
https://www.termbin.com/d1an

seth · 2018-02-09 00:14:21

Still nomodeset:

Kernel command line: \\vmlinuz-linux.alreadyexistsinfilesystem rw root=UUID=7e93ef28-bfce-4b4b-b5f4-17ca67bfd726 initrd=\initramfs-linux.img nomodeset

Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: CPU:0 (17:11:0) MC20_STATUS[-|-|MiscV|-|AddrV|Deferred|-|SyndV|-|UECC]: 0x9c2030000001085b
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Error Addr: 0x00007ffcffffff00
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: IPID: 0x0000002e00000000, Syndrome: 0x000000005b240205
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Coherent Slave Extended Error Code: 1
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Coherent Slave Error: Address violation.
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: IRD, part-proc: SRC (no timeout)

Looks like https://lkml.org/lkml/2017/12/19/43

Bugattikid2012 · 2018-02-09 00:16:09

seth wrote:

Still nomodeset:

Kernel command line: \\vmlinuz-linux.alreadyexistsinfilesystem rw root=UUID=7e93ef28-bfce-4b4b-b5f4-17ca67bfd726 initrd=\initramfs-linux.img nomodeset

Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: CPU:0 (17:11:0) MC20_STATUS[-|-|MiscV|-|AddrV|Deferred|-|SyndV|-|UECC]: 0x9c2030000001085b
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Error Addr: 0x00007ffcffffff00
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: IPID: 0x0000002e00000000, Syndrome: 0x000000005b240205
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Coherent Slave Extended Error Code: 1
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: Coherent Slave Error: Address violation.
Feb 08 22:58:14 linuxlaptop kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: IRD, part-proc: SRC (no timeout)

Looks like https://lkml.org/lkml/2017/12/19/43

Yes, the Xorg log doesn't appear to show up without nomodeset. I stated that in my post. As requested however, the journalctl output is from a boot with modeset enabled.

loqs · 2018-02-09 00:23:41

Try with modesetting off adding the option amdgpu.dc=1

seth · 2018-02-09 00:31:01

Should dc not be enabled by default for Vega?

CPU0: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (family: 0x17, model: 0x11, stepping: 0x0)

Otherwise try (wild shots)

amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0

Bugattikid2012 · 2018-02-09 00:36:16

loqs wrote:

Try with modesetting off adding the option amdgpu.dc=1

I'll try that and edit this post, or post back very soon. However, I just ensured that sddm was set to launch at system startup, and maybe this journalctl with modesetting will be of more use?

http://termbin.com/ohge/

logs wrote:

Should dc not be enabled by default for Vega?

It is my understanding that it is required for Vega, but I'll give it all a go just to see. I thought the reason for needing 4.15 was the need for DC, but eh.

Edit: Neither suggestion had a different result than normal unfortunately.

Last edited by Bugattikid2012 (2018-02-09 00:50:34)

seth · 2018-02-09 07:14:22

For clarification: you still can successfully boot the multi-user.target, only starting SDDM causes trouble? Can you start "just" an X11 server (using startx, ensure to have xterm and twm installed there or adjust your xinitrc)?

Edit: did you also try "amdgpu.dc=0"?

Last edited by seth (2018-02-09 07:41:52)

Bleistift · 2018-02-22 20:49:45

Hey Bugattikid,

I see acer_wmi and you talk about Ryzen mobile, do you also have the Acer Swift 3 SF315-41 with mobile Ryzen 5?
Or any other Ryzen / Raven Ridge Laptop?

Can you suspend your mobile Ryzen system?
I cannot suspend my Acer Swift 3, it either reboots or gets stuck.....
Were you able to get working suspend to RAM?

Thanks!

Bugattikid2012 · 2018-02-22 21:19:51

Bleistift wrote:

Hey Bugattikid,
I see acer_wmi and you talk about Ryzen mobile, do you also have the Acer Swift 3 SF315-41 with mobile Ryzen 5?
Or any other Ryzen / Raven Ridge Laptop?
Can you suspend your mobile Ryzen system?
I cannot suspend my Acer Swift 3, it either reboots or gets stuck.....
Were you able to get working suspend to RAM?
Thanks!

I mentioned in the first post of this thread what laptop I have, and I have mentioned throughout this post how I haven't gotten to a desktop environment yet. I haven't been able to try to suspend.

Supposedly others have been able to setup desktop environments on this laptop, but of course they didn't post how they did it. I'm still hoping someone can help me with my issues.

Arch Linux

#1 2017-12-14 01:42:13

SDDM/Xorg Issues

#2 2017-12-14 02:21:30

Re: SDDM/Xorg Issues

#3 2017-12-14 02:58:01

Re: SDDM/Xorg Issues

#4 2017-12-14 03:55:22

Re: SDDM/Xorg Issues

#5 2017-12-14 08:32:35

Re: SDDM/Xorg Issues

#6 2017-12-24 22:19:27

Re: SDDM/Xorg Issues

#7 2017-12-24 22:51:46

Re: SDDM/Xorg Issues

#8 2018-02-08 22:50:19

Re: SDDM/Xorg Issues

#9 2018-02-08 22:53:47

Re: SDDM/Xorg Issues

#10 2018-02-08 23:14:38

Re: SDDM/Xorg Issues

#11 2018-02-08 23:24:33

Re: SDDM/Xorg Issues

#12 2018-02-08 23:29:31

Re: SDDM/Xorg Issues

#13 2018-02-08 23:41:42

Re: SDDM/Xorg Issues

#14 2018-02-08 23:44:27

Re: SDDM/Xorg Issues

#15 2018-02-08 23:48:49

Re: SDDM/Xorg Issues

#16 2018-02-08 23:50:13

Re: SDDM/Xorg Issues

#17 2018-02-08 23:59:07

Re: SDDM/Xorg Issues

#18 2018-02-09 00:14:21

Re: SDDM/Xorg Issues

#19 2018-02-09 00:16:09

Re: SDDM/Xorg Issues

#20 2018-02-09 00:23:41

Re: SDDM/Xorg Issues

#21 2018-02-09 00:31:01

Re: SDDM/Xorg Issues

#22 2018-02-09 00:36:16

Re: SDDM/Xorg Issues

#23 2018-02-09 07:14:22

Re: SDDM/Xorg Issues

#24 2018-02-22 20:49:45

Re: SDDM/Xorg Issues

#25 2018-02-22 21:19:51

Re: SDDM/Xorg Issues

Board footer