You are not logged in.

#1 2020-01-14 04:50:20

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

[SOVLED] Only Lts Kernal Working no GUI

Hi, I'm new to this although I have run Linux before and successfully installed Arch on other machines.

I have an Acer Swift 3 SF314-41-R2GU with AMD R3-3200U and Vega 3 Graphics

The first problem was that it didn't boot after it said "Loading Linux" it would jump to a black screen and hang. I resolved this issue by installing linux-lts and now it boots fine. The problem I am now facing is no GUI is working I installed mesa,xorg-server and lxde-gtk3 but the startlxde command is returning GTK WARNING cannot open display.

Any help in diagnosing/fixing this problem would be appreciated.

EDIT (Solved):
Downgraded Linux to 5.4.6 and it seems to fix most problems see https://gitlab.freedesktop.org/drm/amd/issues/1013

Last edited by DrDestroydo (2020-01-14 09:16:14)

Offline

#2 2020-01-14 06:02:22

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

Are you trying to run 'startlxde' yourself, manually? I'm guessing this 'startlxde' command is supposed to go into your ~/.xinitrc file so that it's then started through the 'startx' command. The 'startx' command first starts the Xorg server before it then runs the ~/.xinitrc script. That could be the reason for a message like "cannot open display" because that message perhaps means that there's no Xorg server running. If you don't have a ~/.xinitrc script file right now, check out the ArchWiki article named "xinit". That article has a guide about how to create the file.

If that ~/.xinitrc stuff doesn't apply to you, the other idea I have is that the kernel in "linux-lts" might be too old for your GPU. There's always news about some sort of amdgpu driver stuff when a new kernel version is released. Your type of Vega 3 GPU regularly gets mentioned. I got the impression that Vega 3 support is still getting straightened out so an old kernel is perhaps not good to use. If that's the problem, you might then be more successful trying to battle with that hang on the newer kernel version.

Last edited by Ropid (2020-01-14 06:02:54)

Offline

#3 2020-01-14 06:13:36

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

Hi, thanks for the suggestions. Want to try moving to a different kernal but i don't know what to do since i can't get to a command line on boot with any other kernel except linux-lts, how I could go about troubleshooting the problem would be appricieted.

I tried the xinitrc thing as mentioned

this was the result of startx:

X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux Cypher 4.19.95-1-lts #1 SMP Sun, 12 Jan 2020 12:15:22 +0000 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=64cde072-0c6f-476e-a6df-ad837a0bb55c rw loglevel=3 quiet
Build Date: 04 January 2020  10:10:25AM
 
Current version of pixman: 0.38.4
	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 14 14:08:29 2020
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at [url]http://wiki.x.org[/url]
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

and this is the xorg.0.log file:

[   247.251] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[   247.251] 
X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
[   247.251] Build Operating System: Linux Arch Linux
[   247.251] Current Operating System: Linux Cypher 4.19.95-1-lts #1 SMP Sun, 12 Jan 2020 12:15:22 +0000 x86_64
[   247.251] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=64cde072-0c6f-476e-a6df-ad837a0bb55c rw loglevel=3 quiet
[   247.251] Build Date: 04 January 2020  10:10:25AM
[   247.251]  
[   247.251] Current version of pixman: 0.38.4
[   247.251] 	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
[   247.251] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   247.251] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 14 14:08:29 2020
[   247.252] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   247.252] (==) No Layout section.  Using the first Screen section.
[   247.252] (==) No screen section available. Using defaults.
[   247.252] (**) |-->Screen "Default Screen Section" (0)
[   247.252] (**) |   |-->Monitor "<default monitor>"
[   247.252] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   247.252] (==) Automatically adding devices
[   247.252] (==) Automatically enabling devices
[   247.252] (==) Automatically adding GPU devices
[   247.252] (==) Automatically binding GPU devices
[   247.252] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   247.252] (WW) The directory "/usr/share/fonts/misc" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[   247.252] 	Entry deleted from font path.
[   247.252] (==) FontPath set to:
	
[   247.252] (==) ModulePath set to "/usr/lib/xorg/modules"
[   247.252] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   247.252] (II) Module ABI versions:
[   247.252] 	X.Org ANSI C Emulation: 0.4
[   247.252] 	X.Org Video Driver: 24.0
[   247.252] 	X.Org XInput driver : 24.1
[   247.252] 	X.Org Server Extension : 10.0
[   247.253] (++) using VT number 1

[   247.255] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   247.258] (--) PCI:*(3@0:0:0) 1002:15d8:1025:1378 rev 196, Mem @ 0xb0000000/268435456, 0xc0000000/2097152, 0xc0600000/524288, I/O @ 0x00001000/256
[   247.258] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   247.258] (II) LoadModule: "glx"
[   247.258] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   247.260] (II) Module glx: vendor="X.Org Foundation"
[   247.260] 	compiled for 1.20.6, module version = 1.0.0
[   247.260] 	ABI class: X.Org Server Extension, version 10.0
[   247.260] (==) Matched ati as autoconfigured driver 0
[   247.260] (==) Matched modesetting as autoconfigured driver 1
[   247.260] (==) Matched fbdev as autoconfigured driver 2
[   247.260] (==) Matched vesa as autoconfigured driver 3
[   247.260] (==) Assigned the driver to the xf86ConfigLayout
[   247.260] (II) LoadModule: "ati"
[   247.260] (WW) Warning, couldn't open module ati
[   247.260] (EE) Failed to load module "ati" (module does not exist, 0)
[   247.260] (II) LoadModule: "modesetting"
[   247.260] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   247.261] (II) Module modesetting: vendor="X.Org Foundation"
[   247.261] 	compiled for 1.20.6, module version = 1.20.6
[   247.261] 	Module class: X.Org Video Driver
[   247.261] 	ABI class: X.Org Video Driver, version 24.0
[   247.261] (II) LoadModule: "fbdev"
[   247.261] (WW) Warning, couldn't open module fbdev
[   247.261] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   247.261] (II) LoadModule: "vesa"
[   247.261] (WW) Warning, couldn't open module vesa
[   247.261] (EE) Failed to load module "vesa" (module does not exist, 0)
[   247.261] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   247.261] (EE) open /dev/dri/card0: No such file or directory
[   247.261] (WW) Falling back to old probe method for modesetting
[   247.261] (EE) open /dev/dri/card0: No such file or directory
[   247.261] (EE) Screen 0 deleted because of no matching config section.
[   247.261] (II) UnloadModule: "modesetting"
[   247.261] (EE) Device(s) detected, but none match those in the config file.
[   247.261] (EE) 
Fatal server error:
[   247.261] (EE) no screens found(EE) 
[   247.261] (EE) 
Please consult the The X.Org Foundation support 
	 at [url]http://wiki.x.org[/url]
 for help. 
[   247.261] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   247.261] (EE) 
[   247.270] (EE) Server terminated with error (1). Closing log file.

Last edited by DrDestroydo (2020-01-14 08:53:33)

Offline

#4 2020-01-14 06:47:32

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

Can you see a device for the card in the location "/dev/dri"?

Do you have a directory "/sys/bus/pci/drivers/amdgpu"? In that location, do you see link pointing to a device if you run:

ls -l /sys/bus/pci/drivers/amdgpu

About your Xorg log, I'm guessing what it prints there means it can't find a device. The X video driver named "modesetting" seems to have loaded successfully, but then later it can't seem to open the hardware.

On that note, besides the default "modesetting", there's also a more specialized X module just for AMD GPUs. It's in the package "xf86-video-amdgpu". Maybe install that if you currently don't have it installed. This won't help fix this current problem you have, but you might want to have it already for later after you've gotten things to work.

Offline

#5 2020-01-14 06:51:17

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

There is no folder /dev/dri and there is no directory /sys/bus/pci/drivers/amdgpu.

I have the xf86-video-amdgpu package installed already.

Offline

#6 2020-01-14 06:55:55

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

I agree with you that i probably need a different kernal but I don't know how to diagnose the problem when it doesn't even make it to a command line. Are the any suggestions you can offer with methods to diagnose the kernal problem?

Offline

#7 2020-01-14 07:05:41

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

I tried finding people that report problems with similar hardware. I made a whole bunch of tries with Google and wasn't successful.

What I found out along the way is the code-name for your CPU/GPU is "Picasso", maybe that Picasso name helps in searching.

The most interesting thing I found is that people reported about the following kernel argument fixing hangs:

iommu=pt

But I think that was not like your problem, that was for people where the computer would randomly hang after some use.

About what you could currently do while you are on "linux-lts", you can take a look at the "journalctl -b" and see if there's interesting errors about your hardware. Maybe there's a way to fix linux-lts and get the graphics working.

If you want to share very long text, there's a neat package named "pastebinit" that helps. You can then run command lines like this and will get a URL for sharing the text:

journalctl -b | pastebinit
pastebinit < filename

Offline

#8 2020-01-14 07:12:07

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

After alot of restarts it randomly booted to Linux kernal 5.4, seems much slower than usual (input delay) and when I went to restart it hangs with the message:

TSC found unstable after boot, most likely due to broken BNIOS. Use 'tsc=unstable'
systemd-udevd[226]:0000:03:00.0: Worker [291] processing SEQNUM=2264 is taking a long time
systemd-shutdown[1]: Waiting for precess: systemd-devd, systemd-devd
systemd-shutdown[1]: Waiting for precess: systemd-devd
watchdog: watchdog0: watchdog did not stop!
systemd-shutdown[1]: Waiting for precess: systemd-devd
sched: RT throttling activated
i2c_designware AMDI0010:01: controller timed out
i2c_designware AMDI0010:01: timeout in disabling adapter
i2c_designware AMDI0010:01: timeout in disabling adapter
systemd-shutdown[1]: Waiting for precess: systemd-devd
sd-umoun[648]: Failed to unmount /oldroot: Device or resource busy
sd-umoun[649]: Failed to unmount /oldroot/dev: Device or resource busy
shutdown[1]: Failed to finalize  file systems, ignoring

(sorry if there are typos above couldnt copy-paste so wrote out the error)

Last edited by DrDestroydo (2020-01-14 08:52:58)

Offline

#9 2020-01-14 07:25:32

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

It booted to Linux 5.4.11 again after a long wait at a black screen here is the journalctl -b:

https://pastebin.com/nuuPm8Jg

I don't know what to look for when it comes to diagnossing an error.

btw thankyou so much for your help it has been invaluable

Offline

#10 2020-01-14 07:41:27

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

These here are perhaps the interesting messages:

Jan 14 15:21:56 Cypher kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
Jan 14 15:21:57 Cypher kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing A4A6 (len 84, WS 0, PS 0) @ 0xA4DC
Jan 14 15:21:58 Cypher kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing CF70 (len 525, WS 0, PS 0) @ 0xCFC1

Those kinds of lines show up in several places in the log.

Looking around online I can find people with all kinds of AMD cards having that problem, but I can't really find anyone with an integrated GPU. I also can't really find out how the people solved the issue.

Maybe those lines aren't exactly the problem, maybe something in a different place is going wrong, and this graphics driver problem is just a symptom but not the cause.

Offline

#11 2020-01-14 07:45:37

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

I found this here in your log:

Jan 14 15:21:44 Cypher kernel: iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x1c79a1630]
Jan 14 15:21:44 Cypher kernel: iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x1c79a1670]
Jan 14 15:21:45 Cypher kernel: iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=03:00.0 address=0x1c79a1690]

Those are the kinds of lines that are supposed to get fixed by using "iommu=pt" on the kernel command line.

Offline

#12 2020-01-14 07:53:04

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

I found someone writing that this here on the kernel command line helps:

idle=nomwait

I found that here in post #7:

https://forum.mxlinux.org/viewtopic.php?f=92&t=52920

Offline

#13 2020-01-14 07:53:59

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

Double checked kernal parameters iommu=pt is definitely there.

Offline

#14 2020-01-14 08:03:27

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

It is now more reliably booting into linux kernal 5.4.11.

startx is now saying:

waiting for X server to begin accepting connections
..
..
..
..

then the dots repeat forever?

the command line also feels quite sluggish when in the linux kernal, but seems fine when booting to linux-lts

Last edited by DrDestroydo (2020-01-14 08:52:35)

Offline

#15 2020-01-14 08:13:06

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

You've added that "idle=nomwait", and that seemed to make it more reliable with regards to booting the "linux" package kernel? Can you share another "journalctl -b" log of that?

Offline

#16 2020-01-14 08:14:11

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

Offline

#17 2020-01-14 08:23:10

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

I think I'd try installing the last 5.3 kernel version of the "linux" package as an experiment, maybe there's a terrible problem with the 5.4 kernel.

There's an AUR package named "downgrade" that has a script to help with that. Using that script you'd run "downgrade linux" and follow instructions on the screen.

Another way is, run this command line here:

sudo pacman -U 'https://archive.archlinux.org/packages/l/linux/linux-5.3.13.1-1-x86_64.pkg.tar.xz'

Pacman should start downloading from that server and install that file.

Offline

#18 2020-01-14 08:30:57

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

In that log you shared last, there's interesting messages at the very end but I can't find anything about that online, at least nothing that seems related to your system.

Offline

#19 2020-01-14 08:35:27

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,783
Website

Re: [SOVLED] Only Lts Kernal Working no GUI

DrDestroydo, please use code tags for terminal output, not quote tags: https://wiki.archlinux.org/index.php/Co … s_and_code


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#20 2020-01-14 08:50:26

DrDestroydo
Member
Registered: 2020-01-14
Posts: 10

Re: [SOVLED] Only Lts Kernal Working no GUI

Downgraded to linux 5.3 and lightdm and lxde3 started up fine,

THANK YOU SO MUCH.

Have no idea how that fixed the problem but it works so thank you.

Offline

#21 2020-01-14 09:01:14

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: [SOVLED] Only Lts Kernal Working no GUI

What you can do now is stop pacman from upgrading "linux" when you update the system. You do that in /etc/pacman.conf with a line like this:

IgnorePkg = linux

Look around a bit in the file, the "IgnorePkg" line is already prepared somewhere in there.

When you then run "sudo pacman -Syu", pacman will print a message that there's a newer linux package available but it won't download it.

Hopefully version 5.5 of the kernel will work well again.

EDIT:

I found a bug report about your problem. It says that the problem only showed up in kernel 5.4.7 and that it was fine with kernel 5.4.6. Here's a link to it:

https://gitlab.freedesktop.org/drm/amd/issues/1013

Last edited by Ropid (2020-01-14 09:05:01)

Offline

Board footer

Powered by FluxBB