Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

golden_boyy · 2017-03-13 04:40:56

I recently installed Arch Linux again on a separate HDD on my desktop. Everything installs fine when there is no display/window manager involved. Every time I install a display manager/window manager, Arch only ever gets to the login screen then goes to a black screen. I installed both the vesa default drivers and the AMD drivers. My video card is a Radeon R9 390. So far, I've reinstalled Arch many times trying different display and windows managers, I've permanently set "no mode set" in the /etc/default/grub file. I've reinstall xorg and even tried the proprietary AMD drivers. Lastly, I've tried swapping from HDMI to DVI and VGA but to no avail. I'm very unsure as to why Arch crashes/black screens every login attempt. Since I am unable to login to the system, I'm not sure how I would be able to get to the command line to enable print screen of error messages. If anyone has a potential solution for that as well I would really appreciate it.Thank you very much for your assistance, and if I need to post more info please let me know.

Last edited by golden_boyy (2017-04-23 23:50:16)

jasonwryan · 2017-03-13 04:45:30

Forget a DM: just get X working. See the .xinitrc page on the wiki. Post your logs and .xinitrc if it fails.

Not an Installation issue, moving to NC...

golden_boyy · 2017-03-20 03:10:19

Startx works. When I am in the terminal and type "startx" it shows 3 green terminals and a clock. If you would like to still see specific logs please let me know. Thank you in advance!

Lone_Wolf · 2017-03-20 14:02:42

Good, so basic X functionality works.

Does it work for both root and a normal user ?

If yes, configure ~/.xinitrc to start a windowmanager like openbox and test.

R00KIE · 2017-03-20 14:23:50

Please post the output of 'lspci -nnk'.

golden_boyy · 2017-04-01 20:25:29

Sorry for the late response. @Lone_Wolf startx works from both the root user and the non root user. I've downloaded LXDE and enabled it to start from startx. Using startx allows the LXDE desktop to show, but when I click on items within the screen such as "monitor settings" it freezes. Currently, I only have the VESA drivers installed.

@R00KIE Here is the output of the 'lspci -nnk' command

https://pastebin.com/QWKePBDE

Lone_Wolf · 2017-04-03 12:41:57

The lspci output makes clear you have a hybrid graphics setup.

An integrated intel HD 530 using i915 kernel module and a radeon Hawaii Pro card that uses the radeon kernel module.

post xorg log please.

golden_boyy · 2017-04-09 07:25:14

Attached is the most recent (I believe) Xorg log. If you would like any other logs that would assist in this issue please do not hesitate to let me know! Thank you.

https://pastebin.com/ZaxTNM0T

R00KIE · 2017-04-09 11:43:13

Do you have any custom xorg.conf files? If you have try to rename/delete them and start X again and see if it makes any difference.

Lone_Wolf · 2017-04-09 12:21:56

Xorg log doesn't show any *.conf files used, but it does make clear you have set the 390x as primary card.

Try installing xf86-video-ati .

I've permanently set "no mode set" in the /etc/default/grub file

revert that ,and add radeon to the modules= line in mkinitcpio.conf .
then recreate the intramfs and reboot to command prompt.

post dmesg and journalctl -b .

stay logged in as root in one tty, open a new tty as user and try startx from that tty.

Even if X hangs, ctrl+alt+Fx (x being the number of the tty you are logged in as root) should allow you to check logs .

golden_boyy · 2017-04-09 23:04:53

Steps I've taken:

1) Installed xf86-video-ati
2) Reverted "no mode set" the /etc/default/grub file
3) Added "radeon" to the modules= line in mkinitcpio.conf
4) Recreated intramfs using "mkinitcpio -p linux" command
5) dmesg after boot https://pastebin.com/RbABCw8k
6) Journalctl -b after boot https://pastebin.com/Vndx3CrY
7) Updated Xorg log https://pastebin.com/KcRu9U2K
8) Startx when using the "sudo startx -- :1 vt5" command opens the startx default green windows with black space everywhere else.
9) I changed the ~/.xinitrc file to enable LXDE execution using startx by adding "exec startlxde" to the file.
10) From that startx session, I envoked the "startx" command which then takes me to the LXDE desktop
11) LXDE crashes when interacting with the desktop.
12) Journalctl -b after crash https://pastebin.com/NCQ25kcX (while logged in as root in other tty)
13) dmesg after crash https://pastebin.com/VakC4NqE (while logged in as root in other tty)

If you would like anything else to better assist please let me know. Thank you!

Lone_Wolf · 2017-04-10 12:34:15

Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-render-util.so is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-ewmh.so.2.0.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-keysyms.so.1 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-icccm.so is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-icccm.so.4.0.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-render-util.so.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-image.so is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-render-util.so.0.0.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-ewmh.so is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-image.so.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-keysyms.so is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-keysyms.so.1.0.0 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-ewmh.so.2 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-icccm.so.4 is empty, not checked.
Apr 09 08:11:00 Rubix ldconfig[368]: /sbin/ldconfig: File /usr/lib/libxcb-image.so.0.0.0 is empty, not checked

Something went wrong with updating.

use pacman -Qo to figure out the packages those files belong to, then re-install those packages.

After you have handled all of them, run pacman -Qkk . check the output carefully for other problems .

Once all package related issues have been dealt with, run pacman -Syu intel-ucode .

Configure intel microcode updating, https://wiki.archlinux.org/index.php/Microcode .
reboot and repeat steps 5 and further from #11 .

golden_boyy · 2017-04-17 01:07:45

All of the files that were having issues have been updated and/or removed. I've installed "intel-ucode", but the issue now seems to be grub not recognizing and not enabling me to mount a specific partition within the filesystem.
The dmesg output: https://pastebin.com\TjCrzzjq
I've tried to mount "sda2" to /data using "sudo mount -t ext4 /dev/sda2 /data" but produces the following error: "VFS: Can't find ext4 filesystem".
lsblk output: https://pastebin/GLXqXPCK
journalctl -b output: https://pastebin\nuG8KyNd

Last edited by golden_boyy (2017-04-17 01:48:43)

loqs · 2017-04-17 01:14:51

The three links in post #13 are not valid. Please also post the output of

# blkid

golden_boyy · 2017-04-17 01:55:44

blkid output: https://pastebin.com/7CpzgUHq

I believe I've corrected the issue by removing os-prober and then running the "grub-mkconfig -o /boot/grub/grub.cfg" command. I also removed /dev/sda2 from the "fstab" file. Recompiling grub gave no issues after that, and logs appear to be fine. The original issue still persists unfortunately. Whenever I login to the desktop and interact with the screen (i.e. dragging items, clicking, etc) the screen will begin to fuzz; the more I interact with the screen the worse it fuzzes until it freezes and blackscreens.

Xorg logs: https://pastebin.com/FnDaNwg5

loqs · 2017-04-17 15:30:15

The three links in post #13 are still invalid. From the blkid output whatever filesystem was on /dev/sda2 is corrupted beyond detection if any of it remains.
The corruption of /dev/sda2 seems to be a separate to the graphical corruption so please start a new thread about it.

golden_boyy · 2017-04-23 23:49:52

I found the issue. Enabling the intel microcode and, after trying different display managers, using the correct display manager it ended up working. Thank you all for your help. Marked as solved.

Arch Linux

#1 2017-03-13 04:40:56

Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#2 2017-03-13 04:45:30

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#3 2017-03-20 03:10:19

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#4 2017-03-20 14:02:42

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#5 2017-03-20 14:23:50

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#6 2017-04-01 20:25:29

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#7 2017-04-03 12:41:57

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#8 2017-04-09 07:25:14

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#9 2017-04-09 11:43:13

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#10 2017-04-09 12:21:56

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#11 2017-04-09 23:04:53

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#12 2017-04-10 12:34:15

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#13 2017-04-17 01:07:45

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#14 2017-04-17 01:14:51

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#15 2017-04-17 01:55:44

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#16 2017-04-17 15:30:15

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

#17 2017-04-23 23:49:52

Re: Arch Linux freezes upon login (R9 390 GPU)[SOLVED]

Board footer