nouveau broken with kernel 3.5.2-1 (from testing)

lynix · 2012-08-17 11:02:42

Nouveau is currently broken for me as of linux-3.5.2-1.

Booting normally (early KMS) my screens go to standby right after GRUB loads the initramfs and the system does not boot.

Booting with nomodeset in kernel cmdline the system comes up to runlevel 3 but refuses to start Xorg.

/var/log/Xorg.0.log:

(...)
[   178.637] drmOpenDevice: node name is /dev/dri/card0
[   178.643] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[   178.643] drmOpenDevice: node name is /dev/dri/card0
[   178.646] drmOpenByBusid: drmOpenMinor returns -1
[   178.646] drmOpenDevice: node name is /dev/dri/card1
[   178.650] drmOpenByBusid: drmOpenMinor returns -1
[   178.650] drmOpenDevice: node name is /dev/dri/card2
[   178.654] drmOpenByBusid: drmOpenMinor returns -1
[   178.654] drmOpenDevice: node name is /dev/dri/card3
[   178.658] drmOpenByBusid: drmOpenMinor returns -1
[   178.658] drmOpenDevice: node name is /dev/dri/card4
[   178.662] drmOpenByBusid: drmOpenMinor returns -1
[   178.662] drmOpenDevice: node name is /dev/dri/card5
[   178.665] drmOpenByBusid: drmOpenMinor returns -1
[   178.665] drmOpenDevice: node name is /dev/dri/card6
[   178.669] drmOpenByBusid: drmOpenMinor returns -1
[   178.669] drmOpenDevice: node name is /dev/dri/card7
[   178.673] drmOpenByBusid: drmOpenMinor returns -1
[   178.673] drmOpenDevice: node name is /dev/dri/card8
[   178.677] drmOpenByBusid: drmOpenMinor returns -1
[   178.677] drmOpenDevice: node name is /dev/dri/card9
[   178.680] drmOpenByBusid: drmOpenMinor returns -1
[   178.680] drmOpenDevice: node name is /dev/dri/card10
[   178.684] drmOpenByBusid: drmOpenMinor returns -1
[   178.684] drmOpenDevice: node name is /dev/dri/card11
[   178.688] drmOpenByBusid: drmOpenMinor returns -1
[   178.688] drmOpenDevice: node name is /dev/dri/card12
[   178.692] drmOpenByBusid: drmOpenMinor returns -1
[   178.692] drmOpenDevice: node name is /dev/dri/card13
[   178.696] drmOpenByBusid: drmOpenMinor returns -1
[   178.696] drmOpenDevice: node name is /dev/dri/card14
[   178.699] drmOpenByBusid: drmOpenMinor returns -1
[   178.699] drmOpenDevice: node name is /dev/dri/card15
[   178.703] drmOpenByBusid: drmOpenMinor returns -1
[   178.703] drmOpenDevice: node name is /dev/dri/card0
[   178.708] drmOpenDevice: node name is /dev/dri/card0
[   178.712] drmOpenDevice: node name is /dev/dri/card1
[   178.716] drmOpenDevice: node name is /dev/dri/card2
[   178.720] drmOpenDevice: node name is /dev/dri/card3
[   178.723] drmOpenDevice: node name is /dev/dri/card4
[   178.727] drmOpenDevice: node name is /dev/dri/card5
[   178.731] drmOpenDevice: node name is /dev/dri/card6
[   178.735] drmOpenDevice: node name is /dev/dri/card7
[   178.738] drmOpenDevice: node name is /dev/dri/card8
[   178.742] drmOpenDevice: node name is /dev/dri/card9
[   178.746] drmOpenDevice: node name is /dev/dri/card10
[   178.750] drmOpenDevice: node name is /dev/dri/card11
[   178.754] drmOpenDevice: node name is /dev/dri/card12
[   178.757] drmOpenDevice: node name is /dev/dri/card13
[   178.761] drmOpenDevice: node name is /dev/dri/card14
[   178.765] drmOpenDevice: node name is /dev/dri/card15
[   178.769] (EE) [drm] failed to open device
[   178.769] (EE) No devices detected.
[   178.769] 
Fatal server error:
[   178.769] no screens found
[   178.769]

linux-3.4.9 from the core repo works fine.

Anyone else having issues with nouveau on 3.5.2?

Regards

lynix

EDIT: fixed topic title: not related to -ck patchset

Last edited by lynix (2012-08-18 09:19:47)

graysky · 2012-08-17 18:52:44

I'm guessing the problem is unreleated to the ck patchset and is related to 3.5.x series. You have several options to test this hypothesis:

1) Install 3.5.2-1-ARCH from [testing]
2) Download and build 3.4.9-1-ck from the archived PKG section of repo-ck.com

Option 1 is faster

Last edited by graysky (2012-08-17 18:56:58)

lynix · 2012-08-18 09:17:08

I found the time to do the testing. You're right: It is indeed a problem with 3.5.x, not related to the ck patchset.

I'm really thinking about going back to the nvidia proprietary drivers... (freezes when enabling 2D acceleration, and now this one *sigh* )

graysky · 2012-08-18 10:48:37

Another reason to use the proprietary drivers is superior power management. Nouveau cannot do the GPU equivalent of speedstep to manage the GPU clock rate. It is always full blast.

lynix · 2012-08-18 10:56:05

I know, but my hardware is watercooled 8)

I wanted to have KMS which is the only thing the nvidia drivers do not provide. But maybe I should sacrifice KMS to get rid of all these problems... ^^

Gusar · 2012-08-18 11:04:49

graysky wrote:

Nouveau cannot do the GPU equivalent of speedstep to manage the GPU clock rate. It is always full blast.

Actually, Nvidia hardware tends to start out at the lowest performance level, giving you crappy performance. Though nouveau still uses more power than when using the blob. Reclocking and power management, while related, are not one and the same. It takes more to manage the hardware than just changing the clocks.

@lynix: Do you really spend so much time at the console that having a high-res one matters? Considering you're starting X, it doesn't appear to be so.

graysky · 2012-08-18 11:05:35

Watercooling will not reduce power consumption You can use uvesafb to give yourself more resolutions, but for 16:9 or 16:10 the best you can do is 1280x800. You cannot get 1920x1080 or whatever.

lynix · 2012-08-18 11:14:10

Gusar wrote:

@lynix: Do you really spend so much time at the console that having a high-res one matters? Considering you're starting X, it doesn't appear to be so.

Not really But I wanted to get rid of this evil proprietary stuff that taints my kernel and go with the shiny-all-new, all-opensource drivers

graysky wrote:

You can use uvesafb to give yourself more resolutions, but for 16:9 or 16:10 the best you can do is 1280x800

Thanks for the hint, thats what I had before I switched over to nouveau.

You're both right, I guess I'll switch back to the proprietary drivers - although I still like the idea of using only opensource drivers...

laithor · 2012-08-24 16:33:11

I am having similar problems on my old Dell laptop. It has an old nvidia card. Booting normally with KMS leads to a black screen half way through boot up. If I pass the "nomodeset" command in my syslinux boot parameter I can at least get to the linux shell. But I Xorg doesn't work. I looked through my dmesg log and I couldn't even find where nouveau was loading.

I used to use the nvidia 96xx driver until Xorg dropped support for it. I then switched to nouveau which worked pretty well until the recent updates.

Do I have to go with another generic driver like vesa since it seems that nouveau is problematic with the new kernel?

thanks!

Gusar · 2012-08-24 16:40:33

If you use nomodeset, then of course nouveau won't load. Have you tried linux-lts? That kinda the easiest solution if the current kernel give you issues.

laithor · 2012-08-24 22:55:07

I haven't tried linux-lts. Is it just an older kernel that will work with older hardware? I guess I could just downgrade kernels using pacman and see if that works. I just don't want to break packages going forward. Is it problematic to use an older kernel like 3.4.1 while the rest of my system continues to upgrade on the rolling release cycle?

zenlord · 2012-08-25 08:12:18

No it's not. It's probably safer to use 'linux-lts' and update it as the updates come in than to exclude 'linux' from updating.

laithor · 2012-08-27 15:44:12

After trying various fixes over the weekend I finally got things to work using the linux-lts kernel. My old hardware just doesn't seem to play well with the newer kernels. thanks to everyone for your help!

Arch Linux

#1 2012-08-17 11:02:42

nouveau broken with kernel 3.5.2-1 (from testing)

#2 2012-08-17 18:52:44

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#3 2012-08-18 09:17:08

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#4 2012-08-18 10:48:37

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#5 2012-08-18 10:56:05

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#6 2012-08-18 11:04:49

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#7 2012-08-18 11:05:35

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#8 2012-08-18 11:14:10

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#9 2012-08-24 16:33:11

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#10 2012-08-24 16:40:33

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#11 2012-08-24 22:55:07

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#12 2012-08-25 08:12:18

Re: nouveau broken with kernel 3.5.2-1 (from testing)

#13 2012-08-27 15:44:12

Re: nouveau broken with kernel 3.5.2-1 (from testing)

Board footer