Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Broken Xorg hangs system [SOLVED kinda]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Thu Jan 14, 2021 2:03 am    Post subject: Broken Xorg hangs system [SOLVED kinda] Reply with quote

In my last thread, I ran into a problem where nouveau had been built in to xorg-drivers (I've got an AMD GPU card). I'd not properly defined my VIDEO_CARDS, and built xorg-x11, and things got weird... I have an amdgpu card, and the module is loaded. I had to add radeonsi to my VIDEO_CARDS... I rebuilt a lot of things, and then X started working. I ran glxgears, ran enlightenment, and everything looked like it was working fine. Throughout this debug session I was running fluxbox or enlightenment as root.

Today, I had some time and just wanted to see how the new machine would look running a game, installed Steam as root in enlightenment. I logged out, and back in as user, started X and set up Steam, installed Warthunder - no window manager, because I hadn't set up .xinitrc for my user, no big deal. I started Warthunder and got a popup about my video driver not being supported, to make sure I got the latest...

I logged out as my user, exited X, and ran an emerge --sync & -auv world, nothing to update, no rebuilds... I copied my root .xinitrc and .zshrc over to my user, changed ownership, and exited as root. I logged back in as user, started X and the machine hung. It hung right where Xorg says it'll start logging... so no log entry related to the hang.

I rebooted the machine, ran startx as user again, and the machine hung in the same place. Reset, log in as root, startX, no dice - machine hangs.

Right now, I'm looking at a terminal with:
Code:
X.org X Server 1.20.10
...
...
(==) Log File: "/var/log/Xorg.0.log", Time: Wed Jan 13 20:58:05 2021
(== Using system config directory "/usr/share/X11/xorg.conf.d"
_


I've looked at the cited log and it is empty. I'm a little stumped. What do I do, short of uninstalling and rebuilding X?


Last edited by whitt on Sun Jan 17, 2021 6:56 pm; edited 1 time in total
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Thu Jan 14, 2021 2:26 am    Post subject: Reply with quote

Puzzling problem indeed. There must be a reason for this. I's start with inspecting dmesg, then maybe fsck and qcheck - latter is a tool to verify integrity of installed packages. But first make sure your drive is healthy.
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2661

PostPosted: Thu Jan 14, 2021 3:53 am    Post subject: Reply with quote

Well, first of all I think you should become failure with the kill command as it is much better than pushing the power button. A single command startx; sleep 60; killall X will start the server wait 60 seconds and then kill it so you are not waiting forever (hopefully.) I should also disclaim that I haven't tried to do that for quite a while so a error is quite possible. I also believe that X -retro is still available. It is a test for the X server with no practical use whatsoever. You will need to ctr+alt+F1 back to your command line or have the kill waiting.

My guess is the user xinitrc is incomparable. audit and probably replace both .xinitrc and .zshrc. If you change something and it breaks suspect yourself as the problem.

And please don't ever startx as root. It is a very serous security problem for every single program you run.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Thu Jan 14, 2021 11:12 pm    Post subject: Reply with quote

Buffoon wrote:
Puzzling problem indeed. There must be a reason for this. I's start with inspecting dmesg, then maybe fsck and qcheck - latter is a tool to verify integrity of installed packages. But first make sure your drive is healthy.


Unfortunately there is no way for me to copy / paste from the machine, so communicating ALL of DMESG will be impractical. Is there anything I should look for? I can grep out anything you might be able to make sense of. I reviewed and it looked to me like drivers were loaded - amdgpu, and all is OK. I'm not certain what else to look for.

I can't find a package with "gcheck" in it - what needs to be emerged?
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Thu Jan 14, 2021 11:18 pm    Post subject: Reply with quote

The Doctor wrote:
Well, first of all I think you should become failure with the kill command as it is much better than pushing the power button. A single command startx; sleep 60; killall X will start the server wait 60 seconds and then kill it so you are not waiting forever (hopefully.) I should also disclaim that I haven't tried to do that for quite a while so a error is quite possible. I also believe that X -retro is still available. It is a test for the X server with no practical use whatsoever. You will need to ctr+alt+F1 back to your command line or have the kill waiting.

My guess is the user xinitrc is incomparable. audit and probably replace both .xinitrc and .zshrc. If you change something and it breaks suspect yourself as the problem.

And please don't ever startx as root. It is a very serous security problem for every single program you run.


maybe I wasn't clear - when I say the machine hangs, I don't mean X is unresponsive. If so, I'd have just gone back to another terminal and killed it. The machine stops working, period. This is a hard hang. Sleep doesn't work with the machine is hung - the OS isn't doing what it's supposed to.

There is no response to key input, so ctrl-alt term# doesn't do anything at all...

both xinitrc and zshrc are only a few lines I'd literally typed within the hour - the only concern I had with those was if I'd not handled permissions correctly, but I did... so I'm stumped. I thought maybe xord couldn't read the file run as user, but permissions are correct.

I'll post more as I have time to debug.

Or maybe now that I've gotten through the EFI boot setup once, I'll just start over with a fresh install and pay more attention this time. This machine has only been running for 5-8 hours... there isn't much on it.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Thu Jan 14, 2021 11:28 pm    Post subject: Reply with quote

The latest observation: I can boot into an earlier kernel conf, and startx.

Are there systemd changes that may have broken X's ability to start? I ran through systemd setup, enabled my wifi, ACPI, yadda yadda. I can't think of anything that'd break X, but it's about the only system level changes I made before running into the problem.

I'm still struggling to understand the nouveau issue I had, and wonder if it's related.

ANyway, taking a break for the day - don't have time for this...
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Thu Jan 14, 2021 11:35 pm    Post subject: Reply with quote

whitt,

there is always a way to do what you want in Linux. You can put dmesg into pastebin. You can redirect the output of a command into a file instead of having it printed on screen. You can put this file onto a USB stick and take it elsewhere. There are so many ways to skin this cat. Gentoo wgetpaste utility is great help, too, it has a wiki page, you should see it. Regarding dmesg, what really is interesting is if anything goes into dmesg when the computer hangs. You could also log in over ssh and run 'tail -f /your/kernel/log' (I do not know what logger you use). You could boot from an external media after crash and review logs from previous session, if you boot from external media the logs won't be overwritten. And so on. Use your creativity, you are a Gentoo user now!

qcheck is a tool from app-portage/portage-utils (not gcheck!)

Edit: I saw your latest post, if your older kernel boots then the newer kernel image may be corrupted due to filesystem corruption. Just guessing. If this is the case then reinstalling the newest kernel would help. In any case, I'd get to the bottom of this. To make sure it won't happen again.
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2661

PostPosted: Fri Jan 15, 2021 12:00 am    Post subject: Reply with quote

The tool you want is wgetpaste. Simply use it on a file or output stream and it will upload and return a link you can post here.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Fri Jan 15, 2021 12:17 am    Post subject: Reply with quote

Buffoon wrote:
whitt,

there is always a way to do what you want in Linux. You can put dmesg into pastebin. You can redirect the output of a command into a file instead of having it printed on screen. You can put this file onto a USB stick and take it elsewhere. There are so many ways to skin this cat. Gentoo wgetpaste utility is great help, too, it has a wiki page, you should see it. Regarding dmesg, what really is interesting is if anything goes into dmesg when the computer hangs. You could also log in over ssh and run 'tail -f /your/kernel/log' (I do not know what logger you use). You could boot from an external media after crash and review logs from previous session, if you boot from external media the logs won't be overwritten. And so on. Use your creativity, you are a Gentoo user now!

qcheck is a tool from app-portage/portage-utils (not gcheck!)

Edit: I saw your latest post, if your older kernel boots then the newer kernel image may be corrupted due to filesystem corruption. Just guessing. If this is the case then reinstalling the newest kernel would help. In any case, I'd get to the bottom of this. To make sure it won't happen again.


Regarding getting information off the machine after a hang, I haven't set up SSH yet or tried to boot from a live image. I'll get to it - good idea.

I have portage-utils-0.90, and no gcheck... if I were a betting person, and had to wager on the likelihood it was a drive or fs problem, or related to the confusing as all hell nouveau driver problem I ran into the same afternoon (which as far as I can tell I never found the root cause for), I'm betting on the nouveau driver issue.
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Fri Jan 15, 2021 12:34 am    Post subject: Reply with quote

Buffoon wrote:
qcheck is a tool from app-portage/portage-utils (not gcheck!)


Q not G

whitt wrote:
nouveau driver problem I ran into the same afternoon (which as far as I can tell I never found the root cause for)


As far a I remember you mentioned something about experimenting with nouveau, which made me think it got recorded in your world file. But now you have it removed and it cannot be the cause. Nothing mystical happens in Gentoo. Whatever you do can be undone (as long as you use Gentoo tools to manage it), emerge --depclean will clean out what's not needed any more. Emarge and portage are wonderful. Trust them. Reinstall is never needed, just change settings and rebuild. Indeed, if your hard drive is acting up then it's different.


Last edited by Buffoon on Fri Jan 15, 2021 12:44 am; edited 1 time in total
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Fri Jan 15, 2021 12:39 am    Post subject: Reply with quote

Set up SSH, ran dmesg to a file, ran startx from the machine and it hangs. i ran dmesg to a second file and diffed the two over ssh.

There are 67 lines from evbug: Event. Dev: input31, Type Code and Value blah blah... Nothing really of interest in there.

However /var/log/Xorg.0.log:
Code:
cat /var/log/Xorg.0.log
[   237.733]
X.Org X Server 1.20.10
X Protocol Version 11, Revision 0
[   237.733] Build Operating System: Linux 5.9.13-zen1 x86_64 Gentoo
[   237.733] Current Operating System: Linux localhost 5.9.13-zen1 #1 ZEN SMP Sun Jan 10 13:36:34 EST 2021 x86_64
[   237.733] Kernel command line: BOOT_IMAGE=/vmlinuz-5.9.13-zen1 root=UUID=1b0e9d7e-12cd-4db5-bdd4-be040fbfd300 ro
[   237.733] Build Date: 11 January 2021  06:00:08PM
[   237.733]
[   237.733] Current version of pixman: 0.40.0
[   237.733]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[   237.734] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   237.734] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 14 19:23:08 2021
[   237.735] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   237.736] (==) No Layout section.  Using the first Screen section.
[   237.736] (==) No screen section available. Using defaults.
[   237.736] (**) |-->Screen "Default Screen Section" (0)
[   237.736] (**) |   |-->Monitor "<default monitor>"
[   237.736] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[   237.736] (==) Automatically adding devices
[   237.736] (==) Automatically enabling devices
[   237.736] (==) Automatically adding GPU devices
[   237.736] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   237.738] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[   237.738] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   237.738] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[   237.738] (II) Loader magic: 0x560068767d00
[   237.738] (II) Module ABI versions:
[   237.738]    X.Org ANSI C Emulation: 0.4
[   237.738]    X.Org Video Driver: 24.1
[   237.738]    X.Org XInput driver : 24.1
[   237.738]    X.Org Server Extension : 10.0
[   237.739] (++) using VT number 1

[   237.740] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   237.741] (II) xfree86: Adding drm device (/dev/dri/card0)
[   237.741] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[   237.745] (--) PCI:*(45@0:0:0) 1002:731f:1043:05a5 rev 202, Mem @ 0xd0000000/268435456, 0xe0000000/2097152, 0xfcd00000/524288, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[   237.745] (II) LoadModule: "glx"
[   237.750] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   237.755] (II) Module glx: vendor="X.Org Foundation"
[   237.755]    compiled for 1.20.10, module version = 1.0.0
[   237.755]    ABI class: X.Org Server Extension, version 10.0
[   237.755] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
[   237.755]    loading driver: amdgpu
[   237.755] (==) Matched amdgpu as autoconfigured driver 0
[   237.755] (==) Matched ati as autoconfigured driver 1
[   237.755] (==) Matched modesetting as autoconfigured driver 2
[   237.755] (==) Matched fbdev as autoconfigured driver 3
[   237.755] (==) Matched vesa as autoconfigured driver 4
[   237.755] (==) Assigned the driver to the xf86ConfigLayout
[   237.755] (II) LoadModule: "amdgpu"
[   237.756] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
[   237.760] (II) Module amdgpu: vendor="X.Org Foundation"
[   237.760]    compiled for 1.20.10, module version = 19.1.0
[   237.760]    Module class: X.Org Video Driver
[   237.760]    ABI class: X.Org Video Driver, version 24.1
[   237.760] (II) LoadModule: "ati"
[   237.760] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[   237.760] (II) Module ati: vendor="X.Org Foundation"
[   237.760]    compiled for 1.20.10, module version = 19.1.0
[   237.760]    Module class: X.Org Video Driver
[   237.760]    ABI class: X.Org Video Driver, version 24.1
[   237.761] (II) LoadModule: "radeon"
[   237.761] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[   237.763] (II) Module radeon: vendor="X.Org Foundation"
[   237.763]    compiled for 1.20.10, module version = 19.1.0
[   237.763]    Module class: X.Org Video Driver
[   237.763]    ABI class: X.Org Video Driver, version 24.1
[   237.763] (II) LoadModule: "modesetting"
[   237.763] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   237.764] (II) Module modesetting: vendor="X.Org Foundation"
[   237.764]    compiled for 1.20.10, module version = 1.20.10
[   237.764]    Module class: X.Org Video Driver
[   237.764]    ABI class: X.Org Video Driver, version 24.1
[   237.764] (II) LoadModule: "fbdev"
[   237.764] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[   237.764] (II) Module fbdev: vendor="X.Org Foundation"
[   237.764]    compiled for 1.20.10, module version = 0.5.0
[   237.764]    Module class: X.Org Video Driver
[   237.764]    ABI class: X.Org Video Driver, version 24.1
[   237.764] (II) LoadModule: "vesa"
[   237.764] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[   237.764] (II) Module vesa: vendor="X.Org Foundation"
[   237.764]    compiled for 1.20.10, module version = 2.5.0
[   237.764]    Module class: X.Org Video Driver
[   237.764]    ABI class: X.Org Video Driver, version 24.1
[   237.764] (II) AMDGPU: Driver for AMD Radeon:
        All GPUs supported by the amdgpu kernel driver
[   237.764] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
        ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
        ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
        ATI Radeon X600 (RV380), ATI FireGL V3200 (RV380),
        ATI Radeon IGP320 (A3), ATI Radeon IGP330/340/350 (A4),
        ATI Radeon 9500, ATI Radeon 9600TX, ATI FireGL Z1, ATI Radeon 9800SE,
        ATI Radeon 9800, ATI FireGL X2, ATI Radeon 9600, ATI Radeon 9600SE,
        ATI Radeon 9600XT, ATI FireGL T2, ATI Radeon 9650, ATI FireGL RV360,
        ATI Radeon 7000 IGP (A4+), ATI Radeon 8500 AIW,
        ATI Radeon IGP320M (U1), ATI Radeon IGP330M/340M/350M (U2),
        ATI Radeon Mobility 7000 IGP, ATI Radeon 9000/PRO, ATI Radeon 9000,
        ATI Radeon X800 (R420), ATI Radeon X800PRO (R420),
        ATI Radeon X800SE (R420), ATI FireGL X3 (R420),
        ATI Radeon Mobility 9800 (M18), ATI Radeon X800 SE (R420),
        ATI Radeon X800XT (R420), ATI Radeon X800 VE (R420),
        ATI Radeon X850 (R480), ATI Radeon X850 XT (R480),
        ATI Radeon X850 SE (R480), ATI Radeon X850 PRO (R480),
        ATI Radeon X850 XT PE (R480), ATI Radeon Mobility M7,
        ATI Mobility FireGL 7800 M7, ATI Radeon Mobility M6,
        ATI FireGL Mobility 9000 (M9), ATI Radeon Mobility 9000 (M9),
        ATI Radeon 9700 Pro, ATI Radeon 9700/9500Pro, ATI FireGL X1,
        ATI Radeon 9800PRO, ATI Radeon 9800XT,
        ATI Radeon Mobility 9600/9700 (M10/M11),
        ATI Radeon Mobility 9600 (M10), ATI Radeon Mobility 9600 (M11),
        ATI FireGL Mobility T2 (M10), ATI FireGL Mobility T2e (M11),
        ATI Radeon, ATI FireGL 8700/8800, ATI Radeon 8500, ATI Radeon 9100,
        ATI Radeon 7500, ATI Radeon VE/7000, ATI ES1000,
        ATI Radeon Mobility X300 (M22), ATI Radeon Mobility X600 SE (M24C),
        ATI FireGL M22 GL, ATI Radeon X800 (R423), ATI Radeon X800PRO (R423),
        ATI Radeon X800LE (R423), ATI Radeon X800SE (R423),
        ATI Radeon X800 XTP (R430), ATI Radeon X800 XL (R430),
        ATI Radeon X800 SE (R430), ATI Radeon X800 (R430),
        ATI FireGL V7100 (R423), ATI FireGL V5100 (R423),
        ATI FireGL unknown (R423), ATI Mobility FireGL V5000 (M26),
        ATI Mobility Radeon X700 XL (M26), ATI Mobility Radeon X700 (M26),
        ATI Radeon X550XTX, ATI Radeon 9100 IGP (A5),
        ATI Radeon Mobility 9100 IGP (U3), ATI Radeon XPRESS 200,
        ATI Radeon XPRESS 200M, ATI Radeon 9250, ATI Radeon 9200,
        ATI Radeon 9200SE, ATI FireMV 2200, ATI Radeon X300 (RV370),
        ATI Radeon X600 (RV370), ATI Radeon X550 (RV370),
        ATI FireGL V3100 (RV370), ATI FireMV 2200 PCIE (RV370),
        ATI Radeon Mobility 9200 (M9+), ATI Mobility Radeon X800 XT (M28),
        ATI Mobility FireGL V5100 (M28), ATI Mobility Radeon X800 (M28),
        ATI Radeon X850, ATI unknown Radeon / FireGL (R480),
        ATI Radeon X800XT (R423), ATI FireGL V5000 (RV410),
        ATI Radeon X700 XT (RV410), ATI Radeon X700 PRO (RV410),
        ATI Radeon X700 SE (RV410), ATI Radeon X700 (RV410),
        ATI Radeon X1800, ATI Mobility Radeon X1800 XT,
        ATI Mobility Radeon X1800, ATI Mobility FireGL V7200,
        ATI FireGL V7200, ATI FireGL V5300, ATI Mobility FireGL V7100,
        ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
        ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
        ATI Mobility Radeon X1400, ATI Radeon X1550 64-bit,
        ATI Mobility Radeon X1300, ATI Radeon X1300, ATI FireGL V3300,
        ATI FireGL V3350, ATI Mobility Radeon X1450,
        ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
        ATI FireMV 2250, ATI Radeon X1650, ATI Mobility FireGL V5200,
        ATI Mobility Radeon X1600, ATI Radeon X1300 XT/X1600 Pro,
        ATI FireGL V3400, ATI Mobility FireGL V5250,
        ATI Mobility Radeon X1700, ATI Mobility Radeon X1700 XT,
        ATI FireGL V5200, ATI Radeon X2300HD, ATI Mobility Radeon HD 2300,
        ATI Radeon X1950, ATI Radeon X1900, ATI AMD Stream Processor,
        ATI RV560, ATI Mobility Radeon X1900, ATI Radeon X1950 GT, ATI RV570,
        ATI FireGL V7400, ATI Radeon 9100 PRO IGP,
        ATI Radeon Mobility 9200 IGP, ATI Radeon X1200, ATI RS740,
        ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro,
        ATI Radeon HD 2900 GT, ATI FireGL V8650, ATI FireGL V8600,
        ATI FireGL V7600, ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
        ATI Radeon HD 4850 x2, ATI FirePro V8750 (FireGL),
        ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
        ATI Mobility RADEON HD 4850 X2, ATI FirePro RV770,
        AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL),
        ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
        ATI FirePro M7750, ATI M98, ATI Mobility Radeon HD 4650,
        ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
        ATI FirePro M5750, ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
        ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
        ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
        ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
        ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
        ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI RV610,
        ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
        ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI Radeon HD 2350,
        ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400,
        ATI RADEON E2400, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
        ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
        ATI Mobility Radeon HD 3850 X2, ATI Mobility Radeon HD 3870,
        ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2,
        ATI FireGL V7700, ATI Radeon HD3690, AMD Firestream 9170,
        ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350,
        ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
        ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
        ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
        ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
        ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
        ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
        ATI FireGL V3600, ATI Radeon HD 2600 LE,
        ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
        ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
        ATI Radeon HD 3450, ATI Radeon HD 3430, ATI FirePro V3700,
        ATI FireMV 2450, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
        ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
        ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
        ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
        ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
        ATI Radeon HD 3300 Graphics, ATI Radeon 3000 Graphics, SUMO, SUMO2,
        ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
        ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
        AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
        AMD Radeon HD 6300 Series Graphics,
        AMD Radeon HD 6200 Series Graphics, PALM, CYPRESS,
        ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
        AMD Firestream 9350, ATI Radeon HD 5800 Series,
        ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
        ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
        ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
        ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series,
        REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
        ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series,
        AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
        AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
        ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
        MULLINS, KAVERI, HAWAII
[   237.765] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   237.765] (II) FBDEV: driver for framebuffer: fbdev
[   237.765] (II) VESA: driver for VESA chipsets: vesa


You guys are rapid firing at me! I only just reply to one of you when the next notice comes in... you're better than my office IT guys...

Anyway, nothing jumps out of that xorg log at me.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Fri Jan 15, 2021 12:42 am    Post subject: Reply with quote

Buffoon wrote:
Buffoon wrote:
qcheck is a tool from app-portage/portage-utils (not gcheck!)


Q not G


well then... it says all is good. a few files had permissions denied, not sure what that's about, but no errors were found.
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Fri Jan 15, 2021 12:48 am    Post subject: Reply with quote

qcheck verifies installed packages, kernel image is not the target of qcheck. Didn't you say it does not crash with different kernel? I'd copy over (replace) the suspicious kernel image from sources ( /usr/src/linux/arch/x86_64/boot/bzImage ) and boot it, still hangs? Don't forget initramfs if you have it.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Fri Jan 15, 2021 12:58 am    Post subject: Reply with quote

Buffoon wrote:
qcheck verifies installed packages, kernel image is not the target of qcheck. Didn't you say it does not crash with different kernel? I'd copy over (replace) the suspicious kernel image from sources ( /usr/src/linux/arch/x86_64/boot/bzImage ) and boot it, still hangs? Don't forget initramfs if you have it.


yup. identical behavior.
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Fri Jan 15, 2021 1:41 am    Post subject: Reply with quote

OK, lets make sure the facts are right.

This kernel was working before and now does not. Correct?
Another kernel still works. Correct?
To troubleshoot you copied the image from kernel sources into /boot/ and rebooted this replaced kernel, it still hangs. Correct?

Based on this I'd do 'make clean' followed by 'make' in kernel sources, then install and boot this freshly compiled kernel. To make sure correct image is booted check with 'uname -a'
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Fri Jan 15, 2021 5:42 pm    Post subject: Reply with quote

Buffoon wrote:
OK, lets make sure the facts are right.

This kernel was working before and now does not. Correct?
Another kernel still works. Correct?
To troubleshoot you copied the image from kernel sources into /boot/ and rebooted this replaced kernel, it still hangs. Correct?

Based on this I'd do 'make clean' followed by 'make' in kernel sources, then install and boot this freshly compiled kernel. To make sure correct image is booted check with 'uname -a'


I'm certain the correct image is booted, it's the latest ~amd64 zen kernel. My safe boot is the latest stable gentoo-sources, and I have the version from the live image but it doesn't support my wired or wireless network connections.

This kernel was built with VIDEO_CARDS="amdgpu" (missing radeonsi) - would that have had an impact? I've never heard before (admittedly I've been away for a long time) that the make.conf file would impact kernel builds... This kernel has been a champ for all of my system setup - provided I've clearly jacked a few things up w/rt make.conf, and I've monkied with USE flags, etc to get things all installed and set up. It's given me no problems, but has only been rebooted 5-6 times - I've not acid tested this thing.

The latest gentoo-sources kernel does not hang when I startx, but the resolution is low, and I don't know if it's set up optimally or not - I have done nothing other than boot it to see I can edit / alter the installation for rescue purposes. I started X only to see if it too would hang.

I copied the bzimage from usr/src/linux (pointed to my zen sources) and placed on /boot (renaming my prior zen kernel to a dot-bak copy).

I think this evening I will try a rebuild, but I'm also on the fence about a fresh / clean install. I've literally only just built this machine and am getting back into linux for the first time in forever. I was a long time home user, starting with redhat, running slack for a while, then an early adopter of gentoo.

I'm still confused and concerned about my issues with nouveau - I am not certain at all how I ran into that problem, or what may have cause it. I think you replied in that thread as well. I never found the cause, just changed VIDEO_CARDS and rebuilt a lot of random packages. FWIW, all of that work was done without rebooting the machine and just a few startx's - so it looks to me like I'd landed on a weird configuration where the kernel and xorg were happy, but xorg had been rebuilt a few times. Keep in mind I verified amdgpu was loaded, ran glxgears and everything looked good - nice rendering (for openGL) and I recall reported frame rates over 50-60 FPS.

I took that to mean the HW was correctly recognized and setup, then plowed ahead.

The only thing to change between boots was the xorg configuration change resulting from my lucking my way into getting rid of nouveau in xorg-drivers. I'm confused why we're looking at the kernel, but see why it's of interest... You know more than me, so I'll appreciate any enlightenment.

Thanks for info!
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sat Jan 16, 2021 2:37 pm    Post subject: Reply with quote

I rebuilt zen-sources-5.9.13 and caught something that may have caused a problem... I used genkernel to build my last kernel and everything (and the kitchen sink) is included when you do that. I'm not sure if some modules were incorrectly loaded...

I spent a lot of time removing all the modules and support for HW I don't have, and rebuilt last night. I could probably still remove a lot more, but it's better than it was.

I pruned down my world file, removing almost everything. I took out elightenment and fluxbox, and all xorg.

I removed all tailored use flags, and keywords except for my kernel, which remains ~amd64.

I emerged --depclean, and started building things back up.

When I emerge xorg-server, I see:
Code:
* Checking for suitable kernel configuration options...
*   CONFIG_FB_RADEON:   should not be set.  But it is.
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.


I'll try fixing that later today and then proceeding to rebuild xorg-server.

Open question - Could use of genkernel (and zero configuration or tailoring) have yielded a setup that resulted in my prior xorg-driver nouveau problem? Could that be related to the issue I'm having now?

I'm hoping the depclean and removal of my prior setup gives me a clean slate, and I get back to working xorg this evening...
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sat Jan 16, 2021 3:21 pm    Post subject: Reply with quote

Alright - so much for that... Rebuilt kernel getting rid of radeon fb, rebooted. Rebuilt xorg-server, no warning re radeon fb. Startx hangs the system.

I'm completely stumped.
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1303
Location: EU or US

PostPosted: Sat Jan 16, 2021 4:01 pm    Post subject: Reply with quote

I'm stabbing in dark now, but it definitely seems to be video hardware related. If it just started to happen after working normally then I suspect some sort of hardware failure now. One last straw, is the firmware loaded correct version with no errors at loading time (dmesg)? Maybe someone with working crystal ball can chime in, it looks like you need one of those. Oh, have you tried with some Linux liveCD which loads Xorg GUI? It this liveCD loads correct video driver, offers correct resolutions and does not hang then you know it is your Gentoo installation borked somehow. OTOH, if liveCD also hangs with Xorg then you know your hardware is kaputt.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sat Jan 16, 2021 7:00 pm    Post subject: Reply with quote

Buffoon wrote:
I'm stabbing in dark now, but it definitely seems to be video hardware related. If it just started to happen after working normally then I suspect some sort of hardware failure now. One last straw, is the firmware loaded correct version with no errors at loading time (dmesg)? Maybe someone with working crystal ball can chime in, it looks like you need one of those. Oh, have you tried with some Linux liveCD which loads Xorg GUI? It this liveCD loads correct video driver, offers correct resolutions and does not hang then you know it is your Gentoo installation borked somehow. OTOH, if liveCD also hangs with Xorg then you know your hardware is kaputt.


Join the club!

I have a hard time thinking it's hardware... but sure, it's new. who knows...

Here is a timeline, as concise as I can make it. Maybe you'll see why I suspect something is jacked up with the build of xorg...

1) Machine boots from liveusb image (whatever that kernel is) w/out easy network support
2) Installed ubuntu on small partition, used it to set up stage 3 build and grab latest ~amd64 gentoo-sources, binary kernel, zen-sources (kernels were compiled with genkernel, important NOTE - VIDEO_CARDS="amdgpu", it was not correct / complete)
3) (after struggles with EFI) booted into gentoo and started setup using zen-sources (which included compatibility for every piece of HW on earth, including nvidia HW - at that point I didn't know what nouvea was)
4) emerged xorg-server, xorg-x11, and xorg-drivers (yes, I know now some of those should have been --oneshot and should not have gotten into my world file)
5) I emerged fluxbox, glxgears, and xeyes, started X and checked it out - X worked and at least open GL looked good
6) I emerge enlightenment, stopped X and started X w/ enlightenment, all good - went through some set up and let the machine sit for a day or so
7) I wrapped up some setup, set up systemd and a few other things, created my user acct and logged out as root
8) started X as user, running enlightenment - got curious, since it's new HW, wanted to see what high res video or GPU performance would look like - installed steam per gentoo how to
9) started steam - it gave me an error about my graphics driver not being installed correctly
10) that brings me to the last thread regarding nouveau - I found that somehow, libraries were being built with nouvea support and there was a slot conflict - I think the library in question was libdrm
11) I fixed my VIDEO_CARDS line in make.conf, tried --newuse rebuilds to get rid of the library problems, but that wasn't enough. I uninstalled xorg-x11 and xorg-server and xorg-drivers, pruning them from world (NOTE: All of this was done inside the same X session, I did not shut down and restart X)
12) I rebuilt xorg-x11 - this time there was no slot conflict w/ libdrm - telling me the nouveau problem had been solved... yay.
13) I exited X and ran startx - the machine hung
14) restarted, tried startx as root - hangs - come to gentoo forums and start this thread
15) restart and select old kernel (5.8.0-36-generic) and startx - enlightenment runs at reduced resolution
16) I rebuilt zen-sources and changed kernel image on /boot - startx hangs machine
17) I recompiled kernel paying attention to all the settings, reboot, startx hangs
18) I unmerge and rebuild xorg-x11 again - this time see the warning regarding the RADEON FB config setting, go in and fix it, reboot
19) startx hangs with the new kernel again
20) boot into 5.8.0-36-generic again, startx now does not launch x, it sits for a few seconds then exits (log says no screens found)

I'm still suspecting something between the kernel and Xorg... I'm going to try just wiping the slate clean. I'll unmerge everything, go back to a vanilla kernel that supports my network (maybe not ~amd64) and start all over with no libs, no use flags, no keywords... just see what happens with everything default.

I may use genkernel, then go in and remove all the nvidia settings to make sure I avoid the nouveau *thing* I ran into. It'll take a while, so any ideas welcomed...
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sun Jan 17, 2021 6:30 pm    Post subject: Reply with quote

so... prior to X breaking, I'd updated my user account zshrc and xinitrc. I'd just made them and checked them out as root, after setting up zsh and all the plugins (completions, syntax highlighting, etc). All was good inside X. Everything died after closing X and restarting.

I followed the gentoo guide for changing your shell here:
https://wiki.gentoo.org/wiki/Shell

APparently I fell victim to a bug discussed here:
https://forums.gentoo.org/viewtopic-t-1089552-start-0.html

Now, apparently, eselect sh just doesn't work. Or that's all I can gather.

I nuked my rescue ubuntu install, and built a brand new gentoo install. I went through the exact same flow - verified X was working with amdgpu, and all was good. I set up my shell, logged out, and X hung.

If your shell is completely jacked, nothing knows what to do with what's in your xinitrc. So X just sits there waiting for exec fluxbox and nothing happens.

I changed back to bash, X works. I use oldschool chsh to change to zsh, and X works.

Jesus H...

At least now I have a brand new, shiny installation, and have only lost about 10 hours of my life watching text scroll rapidly up my screen.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47626
Location: 56N 3W

PostPosted: Sun Jan 17, 2021 6:52 pm    Post subject: Reply with quote

whitt,

Lets start at the very beginning and try some analysis.

Boot however you like, it need not be Gentoo.
Put the output of
Code:
lspci -nnk
onto a pastebin.
Get into your chroot and put the output of
Code:
emerge --info
onto a pastebin.
Put your Gentoo kernel .config file onto a pastebin. That's usually at /usr/srcl/linux/.config but need not be.

Boot your Gentoo to the console and pastebin the output of
Code:
dmesg

Don't filter anything. We are looking for both what is but shouldn't be and what isn't there but should be.
This will tell us your hardware and your global Gentoo configuration.
We can match that aginist you kernel .config in case that's breaking something.
dmesg will show what the kernel does when your system starts.

Long shot sanity test.
Move your ~/.xinitrc out of the way. A rename is good.
Code:
emerge -1av xterm xclock twm

startx should now draw three xterms and an analogue clock, all wrapped up in twm.

If that works, Xorg is fine.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sun Jan 17, 2021 6:56 pm    Post subject: Reply with quote

In case my post wasn't clear - the problem is solved. The problem had nothing to do with hardware, xorg, or the kernel.

eselect sh doesn't update the shell to point to zsh - though I'll point out it is listed in the gentoo wiki regarding changing shell. I used chsh, and now X starts exactly as it should.

I just had to rebuild the entire system to find the problem...
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 16707

PostPosted: Sun Jan 17, 2021 8:28 pm    Post subject: Reply with quote

eselect sh is described as managing the /bin/sh symlink. chsh changes the shell spawned for the user on successful login. If eselect sh sets the system shell to zsh, then every script that starts #!/bin/sh will use zsh as its interpreter. If zsh interprets such a script differently from how bash or dash would do it, then you may get bad results.

If you want to narrow down how this failed, examine relevant scripts looking to see which ones use #!/bin/sh. For each of those in turn, try explicitly using #!/bin/zsh, and see if the script still works.
Back to top
View user's profile Send private message
whitt
n00b
n00b


Joined: 28 Dec 2020
Posts: 51

PostPosted: Sun Jan 17, 2021 8:50 pm    Post subject: Reply with quote

Hu wrote:
eselect sh is described as managing the /bin/sh symlink. chsh changes the shell spawned for the user on successful login. If eselect sh sets the system shell to zsh, then every script that starts #!/bin/sh will use zsh as its interpreter. If zsh interprets such a script differently from how bash or dash would do it, then you may get bad results.

If you want to narrow down how this failed, examine relevant scripts looking to see which ones use #!/bin/sh. For each of those in turn, try explicitly using #!/bin/zsh, and see if the script still works.


that's what I thought too, but it doesn't seem to be... I haven't done any further digging, but if you read the bug report linked in the forum post i copied above, you'll see that because zsh isn't fully POSIX compliant, it isn't (at least fully) supported by eselect sh. I'm not sure what goes wrong, and have a little too much to sort through right now to bother figuring it out.

end of the day, use chsh, I don't see what you get from select sh anyway.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum