You are not logged in.

#1 2018-05-20 17:09:42

julesm
Member
Registered: 2014-07-29
Posts: 70

[SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

I see threads about xorg 1.20 and nvidia, but I'm having an issue with xorg 1.20 and nouveau. Since upgrading to xorg 1.20.0-2 and nouveau 1.0.15-3, x fails to start. There are messages about fatal error 11 - resource temporarily unavailable. In the xorg log file, I see a segfault:

[    84.372] (EE) Segmentation fault at address 0x8
[    84.372] (EE) 
Fatal server error:
[    84.372] (EE) Caught signal 11 (Segmentation fault). Server aborting

If I downgrade xorg-server, xorg-server-common and xf86-video-nouveau, then it all works like it should.

I wanted to highlight that the issue with xorg 1.20 seems wider than just a nvidia driver issue; nouveau is also affected.

Fingers crossed for a resolution soon!

Cheers,
Jules

Last edited by julesm (2018-05-21 06:58:52)

Offline

#2 2018-05-20 18:20:14

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,797

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

Remove xf86-video-nouveau to make xorg use the modesetting driver, it appears the xf86-video-nouveau driver has not been properly updated yet

Offline

#3 2018-05-20 20:37:34

julesm
Member
Registered: 2014-07-29
Posts: 70

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

Thanks - I will try that. But nouveau updated on the same day xorg 1.20 updated and nouveau 1.0.15-3 is dependent on xorg 1.20.

From pacman log: xf86-video-nouveau (1.0.15-2 -> 1.0.15-3)

But wouldn't this be a temporary measure?

Is it that nouveau is no longer necessary?

Offline

#4 2018-05-20 20:57:45

seth
Member
Registered: 2012-09-03
Posts: 12,933

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

xf86-video-nouveau was only recompiled against the new ABI, but 1.0.15 was released a year ago, so nobody vetted this version agains the new xorg server.
xf86-video-* are not "necessary" for quite some time because there's the modesetting driver - they might still work better for some GPUs, though, but at least eg. xf86-video-intel is more or less abandoned in favor or the modesetting driver.

Offline

#5 2018-05-21 06:58:35

julesm
Member
Registered: 2014-07-29
Posts: 70

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

Many thanks - removed nouveau - updated and all is well!

Cheers,
Jules

Offline

#6 2018-05-23 19:35:52

dwillar
Member
Registered: 2012-08-10
Posts: 10

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

I also removed nouveau and recovered my xfce4 GUI. When xscreensaver tried to run noof without nouveau installed the result was pitiful to say the least. Does someone have an alternative to nouveau. Perhaps I have missed something here. This does not appear to be in anyway solved at this time as far as I can see. If the idea is to get rid of the xf86 series of drivers then it seems to me that xorg-server has a way to go to be able to handle the job. Please get the nouveau driver fixed or provide an alternative solution!

Offline

#7 2018-05-23 19:36:52

seth
Member
Registered: 2012-09-03
Posts: 12,933

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

read comment #4

Offline

#8 2018-05-24 09:39:12

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,797

Re: [SOLVED] Xorg 1.20.0-2 with nouveau fails to start - segfaults

In general afaik the glamor accel used by the modesetting driver isn't as fast for pure 2D operations, but if you base your definition of unusable on whether a 20 year old demo screen saver using old API still works fluently, then you might have other problems in the future.

That said, for the OP this is considered solved, if you really want this discussed further, open up a thread post details about your setup, at least a xorg log would be nice, so we could at least confirm that the modesetting driver works as expected. And if it doesn't,  you might want to actively gather information on why nouveau doesn't work correctly, so that a proper bug report can be made, from what I'm seeing, no one has done that yet for the problem described here

Offline

Board footer

Powered by FluxBB