topic title: Problems with nouveau driver: func 07 lookup failed
Posts: 10
marko
Joined: 11 Jun 2015
#1
Hello,

every time on bootup the nouveau driver complains:

Code: Select all

    nouveau E[ DISPLAY][0000:01:00.0][0x00000000] 01:0130: func 07 lookup failed, -2
The system starts anyway and runs rather stable. Exept for the hardware video acceleration. E.g. Chromium freezes and has to be killed, glxgears freezes after drawing one frame.
From time to time (ca. 1 in 10) nouveau complains

Code: Select all

    nouveau E[     DRM] GPU lockup - switching to software fbcon
and the system freezes completely.

Deactivating the hw acceleration via the xorg.conf (Option noaccel and nofbaccel) had no effect. The nvidia driver seems to be working (at least nearly: some programs windows need a couple of seconds for redrawing on tabbing/maximizing), but I had to choose the debian kernel from smxi. I couldn't install it on the antix kernel. On the 4.2.1-gnu-antix kernel it is allways the second error and the system allways freezes.

My card

Code: Select all

inxi -G
Graphics:  Card: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300]
           Display Server: X.Org 1.16.4 driver: nouveau
           Resolution: 1280x800@59.91hz
           GLX Renderer: Gallium 0.4 on NV46 GLX Version: 2.1 Mesa 10.3.2
worked fine with antix 13.2 (hw acceleration with nouveau, but same issues with nvidia).

Preferably I would like to have the nouveau driver working. But if alternatively the delay on the redraw on the nvidia driver can be helped i would be glad too.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#2
What are outputs of

Code: Select all

harry@biker:~
$ xvidtune -show
"1366x768"     72.14   1366 1414 1446 1522    768  770  775  790 +hsync -vsync

harry@biker:~
$ glxinfo | grep -i"direct rendering"
direct rendering: Yes
harry@biker:~
$ cat /var/log/Xorg.0.log | grep -i"dri" | grep -v -i"driver"
[     6.562] (II) xfree86: Adding drm device (/dev/dri/card0)
[     6.627] (II) Loading sub module"dri2"
[     6.627] (II) LoadModule:"dri2"
[     6.627] (II) Module"dri2" already built-in
[     6.629] (II) intel(0): [DRI2] Setup complete
[     6.645] (II) intel(0): direct rendering: DRI2 Enabled
[     6.692] (II) GLX: Initialized DRI2 GL provider for screen 0
Posts: 10
marko
Joined: 11 Jun 2015
#3

Code: Select all

xvidtune -show
"1280x800"     71.00   1280 1328 1360 1440    800  803  809  823 -hsync -vsync

Code: Select all

glxinfo | grep -i"direct rendering"
direct rendering: Yes

Code: Select all

cat /var/log/Xorg.0.log | grep -i"dri" | grep -v -i"driver"
[    22.424] (II) xfree86: Adding drm device (/dev/dri/card0)
[    22.941] (II) Loading sub module"dri2"
[    22.941] (II) LoadModule:"dri2"
[    22.942] (II) Module"dri2" already built-in
[    23.436] (II) NOUVEAU(0): [DRI2] Setup complete
[    26.090] (II) GLX: Initialized DRI2 GL provider for screen 0
Posts: 10
marko
Joined: 11 Jun 2015
#4
I made a little testrun installing other kernels via apt-get:

3.7.10-antix.7-pae
3.6.11-antix.1-486-smp
- boots ok
- glxgears runs, chromium runs hardware accelerated

3.11.5-antix.1-486-smp
3.9.5-antix.1-486-smp
- boots only to command line, but without these errors
- Xorg.log:
[ 23.841] (EE) [drm] KMS not enabled
[ 23.841] (EE) No devices detected.
[ 23.841] (EE) no screens found(EE)

3.12.6-antix.1-486-smp
- like 3.7.10, but at shutdown now -r there are endless messages scrolling

3.13.3-antix.1-486-smp
- boots into gui
- glxgears and hw accellerated chromium not working
- no func 07 lookup error in dmesg

3.14.4-antix.3-486
- like 3.13, but at shutdown now -r there are endless messages scrolling

3.15.2-antix.3-486
4.0.5-antix.1-486-smp
4.2.1-antix.3-686-pae
- boots into gui
- glxgears and hw accellerated chromium not working
- func 07 lookup failed

Since the old 3.7 kernel seems to be working, i will stay with it. Or are there any critical bugs in it?

Some questions that came up during the tests:
- Sometimes during the bootup messages alsa (alsactl) complains, but I didn't find any entry under /var/log/. Does Alsa has an own log elsewhere? Sound seems to be running though.
- Installing the linux-image* over apt-get creates two entries in the grub menu: one extra with (sysvinit) appendix. Why?
Posts: 10
marko
Joined: 11 Jun 2015
#5
No insights from anyone?
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#6
- Installing the linux-image* over apt-get creates two entries in the grub menu: one extra with (sysvinit) appendix. Why?
In case you want to cli boot to run smxi.

No insights from anyone?
Some of us are busy alpha testing MX-15 presently. So things are quiet around here because of that.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#7
irc #nouveau channel might be your best source for help.

a web search didn't 't provide a definitive answer


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau&date=2014-06-18"
linktext was:"http://people.freedesktop.org/~cbrill/d ... 2014-06-18"
====================================



========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bugzilla.redhat.com/show_bug.cgi?id=918732"
linktext was:"https://bugzilla.redhat.com/show_bug.cgi?id=918732"
====================================


but, from what I read, proprietary nvidia driver is less problematic than noveau for the 7300 series cards
Posts: 10
marko
Joined: 11 Jun 2015
#8
rokytnji wrote:
- Installing the linux-image* over apt-get creates two entries in the grub menu: one extra with (sysvinit) appendix. Why?
In case you want to cli boot to run smxi.
That could explain the boot to cli in my kernel tests. Is sysvinit the same as init 3?
skidoo wrote:but, from what I read, proprietary nvidia driver is less problematic than noveau for the 7300 series cards
It is at least the most upcoming answer. But there's that window switching delay thingy. Also installing them is quite a pain in the neck. Over smxi i only could install with the debian kernel. And with
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.debian.org/NvidiaGraphicsDrivers#Version_304.125_.28legacy_GPUs.29"
linktext was:"https://wiki.debian.org/NvidiaGraphicsD ... cy_GPUs.29"
====================================
i only resulted in cli boots.