#37 Can't log in as "GNOME on Xorg" on Silverblue 28
Closed 8 months ago Opened 8 months ago by znmeb.

How to reproduce:

  1. Log in to Silverblue 28 with the default (GNOME - default is Wayland), it works.
  2. Log out.
  3. Try to log in with "GNOME on Xorg". The screen flashes and it goes back to the login screen.

What's happening is that X is segfaulting - see attached Xorg.0.log. Are there some packages missing?
Xorg.0.log


Yep - I installed xorg-x11-drv-amdgpu and now I can log in with GNOME on Xorg! amdgpu is the video card I have - AMD "Bonaire" ("Sea Islands" architecture).

@mclasen should this be included in the workstation comps ?

I'd say it's a must-have - the older AMD cards will work with the radeon or ati drivers but the newer ones need amdgpu.

https://www.phoronix.com/scan.php?page=search&q=AMDGPU

I'd say it's a must-have -

I don't disagree, i'm just trying to pass on the information to someone who can do something about it.

I'd also say: if you can reproduce this by installing vanilla fedora workstation (not silverblue) then we probably have a blocker bug.

hey @znmeb I talked with the hero of fedora himself:

adamw | yeah...                                                         
adamw | xorg-x11-drv-amdgpu is not in base-x indeed                     
adamw | might be a tricky vote for blocker status but i'd be FE at least

so let's go ahead and open a bug for this. Can you click this link to open a bug against the distribution component of Fedora so that we can track it as a blocker/FE for beta?

Is xorg-x11-drv-modesetting installed? Per @ajax , he would usually expect that driver to work in this case.

Edit: actually modesetting is part of xorg-x11-server-Xorg now, according to @ajax ...so it should've been available. Can we tell why it wasn't, or didn't work, at all?

do you see anything missing from this list: https://pagure.io/workstation-ostree-config/blob/master/f/fedora-common-ostree-pkgs.json#_219-233 ?

these manifests get synced with comps via a script.

do you see anything missing from this list: https://pagure.io/workstation-ostree-config/blob/master/f/fedora-common-ostree-pkgs.json#_219-233 ?
these manifests get synced with comps via a script.

That list looks fine.

I'd be a little cautious in attempting to fix this by installing amdgpu, at least in a "release blocker" sense. Existing machines where this bug doesn't appear might find themselves running amdgpu instead of modesetting; probably that's fine, but it's a larger change than you might be willing to absorb.

There's a patch in xserver master that looks relevant. Try this test build instead (without amdgpu installed):

https://koji.fedoraproject.org/koji/taskinfo?taskID=29620484

I can run tests / grab logs on this system if you want - I don't know
whether modesetting worked or not.

On Tue, Sep 11, 2018 at 12:13 PM Adam Jackson pagure@pagure.io wrote:

ajax added a new comment to an issue you are following:
``

do you see anything missing from this list:
https://pagure.io/workstation-ostree-config/blob/master/f/fedora-common-ostree-pkgs.json#_219-233
?
these manifests get synced with comps via a script.

That list looks fine.

I'd be a little cautious in attempting to fix this by installing amdgpu,
at least in a "release blocker" sense. Existing machines where this bug
doesn't appear might find themselves running amdgpu instead of modesetting;
probably that's fine, but it's a larger change than you might be willing to
absorb.

There's a patch in xserver master that looks relevant. Try this test build
instead (without amdgpu installed):

https://koji.fedoraproject.org/koji/taskinfo?taskID=29620484
``

To reply, visit the link below or just reply to this email
https://pagure.io/teamsilverblue/issue/37

--
How many people can stand on the shoulders of a giant before the giant
collapses?

@znmeb yes, please do test. Basically, what @ajax is saying is, you shouldn't need to install xorg-x11-drv-amdgpu : X should work with the 'modesetting' driver. He thinks the reason it didn't might be a bug that is fixed by https://koji.fedoraproject.org/koji/taskinfo?taskID=29620484 .

So basically we would like you to test the affected system without xorg-x11-drv-amdgpu installed, but with your system updated with the packages from that scratch build, and see if X works that way.

Thanks!

I did have Fedora 28 standard installed a couple of weeks ago but I don't remember trying it with GNOME on Xorg.

@znmeb can you do a few things for us:

  • open a bug in bugzilla for this issue: link
  • test out the above xorg-x11-server build by

to do the 2nd part:

  • First remove the xorg-x11-drv-amdgpu with rpm-ostree uninstall xorg-x11-drv-amdgpu
  • download xorg-x11-server rpms from x86_64 koji build and run rpm-ostree override replace rpm1.rpm rpm2.rpm rpm3.rpm...
  • reboot

OK ... it'll be an hour or so before I can get back to it though.

On Tue, Sep 11, 2018 at 12:43 PM Dusty Mabe pagure@pagure.io wrote:

dustymabe added a new comment to an issue you are following:
``
@znmeb can you do a few things for us:

  • open a bug in bugzilla for this issue: link
  • test out the above xorg-x11-server build by

to do the 2nd part:

  • First remove the xorg-x11-drv-amdgpu with rpm-ostree uninstall xorg-x11-drv-amdgpu
  • download xorg-x11-server rpms from x86_64 koji build and run
    rpm-ostree override replace rpm1.rpm rpm2.rpm rpm3.rpm...
    ``

To reply, visit the link below or just reply to this email
https://pagure.io/teamsilverblue/issue/37

--
How many people can stand on the shoulders of a giant before the giant
collapses?

Bugzilla done - https://bugzilla.redhat.com/show_bug.cgi?id=1627913

Is there a link to the RPMs? I didn't see it go by.

They're under https://koji.fedoraproject.org/koji/taskinfo?taskID=29620484 . Assuming you want x86_64, they're at https://koji.fedoraproject.org/koji/taskinfo?taskID=29620485 . You only need the ones that update packages you have installed, no need to install all the others too.

[znmeb@Silverblue xorg]$ rpm-ostree override replace ~/Downloads/xorg-x11-server-*.rpm
error: The connection is closed
[znmeb@Silverblue xorg]$ rpm-ostree override replace ~/Downloads/xorg-x11-server-1.19.6-10.fc28.src.rpm 
error: Importing xorg-x11-server: Unsupported path: /0001-Always-install-vbe-and-int10-sdk-headers.patch; See https://github.com/projectatomic/rpm-ostree/issues/233

How do I get a list of which ones are installed?

in a few hours I can send you the exact commands..

OK - I'll get back to this about 17:00 PST8PDT

(re installed packages) On an ostree system, I'm not sure :) You will only need the x86_64.rpm packages, though, you won't want the .src.rpm one. I'd guess probably xorg-x11-server-Xorg, xorg-x11-server-common, and xorg-x11-server-Xwayland .

any news, @znmeb ?

I have the RPMs downloaded but haven't found an rpm-ostree command to install one - I keep getting errors.

$ rpm-ostree override replace --install=xorg-x11-server ./xorg-x11-server-1.19.6-10.fc28.src.rpm 
error: Importing xorg-x11-server: Unsupported path: /0001-Always-install-vbe-and-int10-sdk-headers.patch; See https://github.com/projectatomic/rpm-ostree/issues/233

rpm-ostree override replace --help doesn't have any clues

@znmeb - i'm working on this now.. sorry I got caught up in "hurricane prep" and forgot about this.

stand by

oh wow, I totally missed the fact that this particular request was for f28 and not f29.

/me does wonder if this affects f29, if not we can stop worrying about blocker/FE

ok @znmeb, these two commands should work:

# curl -L --remote-name-all https://kojipkgs.fedoraproject.org//work/tasks/485/29620485/xorg-x11-server-{common,Xorg,Xwayland}-1.19.6-10.fc28.x86_64.rpm
#
# rpm-ostree override replace ./xorg-x11-server-{common,Xorg,Xwayland}-1.19.6-10.fc28.x86_64.rpm
  1. I don't know if it affects F29 or not. I can't even get a greeter from gdm on this machine with Silverblue 29. I'll be moving on to troubleshooting that as soon as we figure out what this one is.

  2. I got the rpm-ostree override to work but F28 still can't bring up GNOME on Xorg. I have dmesg logs and journalctl -u gdm logs with debug enabled if you need them, but I think X is still crashing.

I stopped gdm and did X -configure to capture an error log. (attached). It looks like the amdgpu driver is still missing. The radeon kernel module is blacklisted but I don't know why X couldn't use one of the other drivers.

P.S.: This AMD card is a nightmare - the kernel modules are a rapidly moving target as are the kernel command line arguments to make it work. I may be the only one in the world that's got this issue.

@znmeb I am actually curious about something: have you ever tried running Xorg on a 'regular' (not ostree/atomic/silverblue) Fedora install on this system? Does that work? Could you try perhaps the F28 KDE live image and see if it boots OK and if so, what X driver it uses? Thanks!

Long ago (Fedora 25 or 26) I ran Fedora on it. I switched to Arch because of the card not functioning on "Clover" OpenCL. Even the AMD proprietary drivers don't work on the supposedly-AMD-supported Ubuntu 16.04. I can probably find the "Clover" bug in Bugzilla that was the impetus for the move.

GNOME 3 on Arch works on both Wayland and Xorg with these kernel arguments: (4.18 kernel at the moment): modprobe.blacklist=radeon amdgpu.cik_support=1 radeon.cik_support=0

I'll try the Live KDE if there's an F29 compose I can test with; I'd rather shake out F29 bugs than F28 bugs this close to F29 beta.

Info on f25 or Arch isn't much use, what I'm curious about is whether we have this same problem in a similar-but-not-ostree-ish Fedora image.

Here's an F29 KDE live: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180911.n.0/compose/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-29-20180911.n.0.iso

I booted the F29 i386 KDE Live (https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180911.n.0/compose/Spins/i386/iso/Fedora-KDE-Live-i386-29-20180911.n.0.iso)

It looks like the kernel is loading both the amdgpu and radeon modules, which I think isn't supposed to work on the newer cards but may be OK for this one. It didn't cause any problems.

Here's what dnf list installed | grep xorg says:

abrt-addon-xorg.i686                             2.10.10-4.fc29                      @anaconda
xorg-x11-apps.i686                               7.7-22.fc29                         @anaconda
xorg-x11-drv-ati.i686                            18.0.1-2.fc29                       @anaconda
xorg-x11-drv-evdev.i686                          2.10.6-3.fc29                       @anaconda
xorg-x11-drv-fbdev.i686                          0.5.0-2.fc29                        @anaconda
xorg-x11-drv-intel.i686                          2.99.917-39.20180618.fc29           @anaconda
xorg-x11-drv-libinput.i686                       0.28.0-2.fc29                       @anaconda
xorg-x11-drv-nouveau.i686                        1:1.0.15-6.fc29                     @anaconda
xorg-x11-drv-openchrome.i686                     0.6.0-6.fc29                        @anaconda
xorg-x11-drv-qxl.i686                            0.1.5-10.fc29                       @anaconda
xorg-x11-drv-vesa.i686                           2.4.0-4.fc29                        @anaconda
xorg-x11-drv-vmware.i686                         13.2.1-8.fc29                       @anaconda
xorg-x11-drv-wacom.i686                          0.36.1-5.fc29                       @anaconda
xorg-x11-drv-wacom-serial-support.i686           0.36.1-5.fc29                       @anaconda
xorg-x11-font-utils.i686                         1:7.5-40.fc29                       @anaconda
xorg-x11-fonts-misc.noarch                       7.5-20.fc29                         @anaconda
xorg-x11-server-Xorg.i686                        1.20.1-1.fc29                       @anaconda
xorg-x11-server-common.i686                      1.20.1-1.fc29                       @anaconda
xorg-x11-server-utils.i686                       7.7-26.fc29                         @anaconda
xorg-x11-utils.i686                              7.5-29.fc29                         @anaconda
xorg-x11-xauth.i686                              1:1.0.9-13.fc29                     @anaconda
xorg-x11-xbitmaps.noarch                         1.1.1-15.fc29                       @anaconda
xorg-x11-xinit.i686                              1.4.0-3.fc29                        @anaconda
xorg-x11-xkb-utils.i686                          7.7-27.fc29                         @anaconda

X found the radeon driver but not the amdgpu driver. I'm guessing if I switch my kernel arguments around and don't blacklist the radeon kernel module X will come up in Silverblue 28 too.

You should probably test on a newer AMD card - one that requires the amdgpu kernel module - to see what happens. I can't help you there; this will be the last AMD GPU I ever buy. ;-)

Info on f25 or Arch isn't much use, what I'm curious about is whether we have this same problem in a similar-but-not-ostree-ish Fedora image.
Here's an F29 KDE live: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180911.n.0/compose/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-29-20180911.n.0.iso

I tried the KDE F29 i386 live compose - see https://pagure.io/teamsilverblue/issue/37#comment-530952

It looks like F29 is OK on this old AMD card - it works with either the radeon or amdgpu kernel module. But you'll need to test on a newer AMD card - I think some of them require the amdgpu kernel module.

or I guess you could try the Workstation live:
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180911.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-29-20180911.n.0.iso
log out of the Shell after it boots, then try logging into the X session...

Fedora-Workstation-Live-x86_64-29-20180911.n.0.iso booted successfully. I had to set a password for the live user to get the logout and login on Xorg to work, but it did come up on Xorg as well as Wayland. Both the amdgpu and radeon kernel modules were loaded.

@znmeb maybe we should wait for f29 beta to come out and then have you try f29 silverblue beta to see if you have this issue or not

@znmeb maybe we should wait for f29 beta to come out and then have you try f29 silverblue beta to see if you have this issue or not

That's my plan ... I am on the mailing lists so I should see the Go-No Go meetings. I'm planning to do the Silverblue test day on the 20th. Meanwhile I'll be wringing out the OpenCL stuff on Silverblue 28 as much as possible.

@znmeb maybe we should wait for f29 beta to come out and then have you try f29 silverblue beta to see if you have this issue or not

That's my plan ... I am on the mailing lists so I should see the Go-No Go meetings. I'm planning to do the Silverblue test day on the 20th. Meanwhile I'll be wringing out the OpenCL stuff on Silverblue 28 as much as possible.

It looks like there is a Silverblue 29 Beta - I managed to get a rebase to work.

$ rpm-ostree status
State: idle
AutomaticUpdates: disabled
Deployments:
‚óŹ ostree://fedora-workstation:fedora/28/x86_64/workstation
                   Version: 28.20180911.0 (2018-09-11 15:06:50)
                BaseCommit: acfb4afdebf0731ce0b9134adf434173472a970328d75ece68d5015af27b33e4
              GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
           LayeredPackages: chrome-gnome-shell cockpit docker-compose f28-backgrounds-extras-gnome git git-lfs
                            kernel-tools mediawriter powertop python3-speedtest-cli vim-enhanced xorg-x11-drv-amdgpu

  ostree://fedora-workstation:fedora/29/x86_64/silverblue
                   Version: 29_Beta.1.1 (2018-09-12 11:43:54)
                BaseCommit: 478cb224043d9f5175ba282ffc787350a9c6e1ff46411e0f19f262d60df97e93
              GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
           LayeredPackages: chrome-gnome-shell cockpit docker-compose f28-backgrounds-extras-gnome git git-lfs
                            kernel-tools mediawriter powertop python3-speedtest-cli vim-enhanced xorg-x11-drv-amdgpu

I'll do some more testing tonight now that I have an F29 workstation live USB stick to test with.

Fedora 29 Workstation update: I installed Fedora 29 Workstation using the "everything" net install disk. I can log in on either Wayland or Xorg without any problems other than slowness from a known SELinux issue with a fixed version in the pipeline.

Silverblue 29 Beta 1.3 is installed. All the screen things work now. I have no plan to drop back to F28 Silverblue any more now that 29 is viable.

Metadata Update from @dustymabe:
- Issue status updated to: Closed (was: Open)

8 months ago

Login to comment on this ticket.

Metadata
Attachments 2
Attached 8 months ago View Comment
Attached 8 months ago View Comment