Unable to get display running with nouveau

Jongi · #1 21st November 2009, 07:15 AM

When I boot, I met with a blank screen when kdm is meant to start up. I do not have an xorg.conf. /var/log/Xorg.0.log reports

Code:

(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 05@00:00:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib64/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
	compiled for 1.7.1, module version = 0.0.2
	ABI class: X.Org Video Driver, version 6.0
(EE) open /dev/fb0: No such file or directory
(--) NOUVEAU(0): Chipset: "NVIDIA NVA0"
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib64/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
	compiled for 1.7.1, module version = 1.0.0
	ABI class: X.Org Video Driver, version 6.0
(II) NOUVEAU(0): Initializing int10
(II) NOUVEAU(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib64/xorg/modules/extensions/libdri.so
(II) NOUVEAU(0): Loaded DRI module
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
[drm] failed to load kernel module "nouveau"
(EE) [drm] drmOpen failed.
(EE) NOUVEAU(0): [drm] error opening the drm
(EE) NOUVEAU(0): 877: 
(II) UnloadModule: "nouveau"
(II) UnloadModule: "dri"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib64/xorg/modules/libint10.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
	 at http://bodhi.fedoraproject.org/
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Full log is here - http://pastebin.com/f21887033

rpm -qa | grep nouveau

Code:

xorg-x11-drv-nouveau-0.0.15-17.20091105gite1c2efd.fc12.x86_64

rpm -qa | grep drm

Code:

libdrm-2.4.15-4.fc12.x86_64
libdrm-devel-2.4.15-4.fc12.x86_64

rpm -qa | grep nvidia reports nothing. What am I missing?

Running kernel 2.6.32-0.51.rc7.git2.fc13.x86_64 if that helps.

Edit: Here is part of the problem

Code:

# modprobe nouveau
FATAL: Module nouveau not found.

EDIT2: Using the nvidia driver (from the nvidia website)

EDIT3: Decided to install F12

STEVE555 · #2 21st November 2009, 11:57 AM

I have the same problem with the screen blank when I boot into the 2.6.32-0.51.rc7.git2.fc13 kernel.
I have no problems with the previous one,i.e the 2.6.31.5-127.fc12.i686.

The output of my xorg.log is slightly different:

Code:

(II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
(II) Module nouveau: vendor="X.Org Foundation"
	compiled for 1.7.1, module version = 0.0.10
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) NOUVEAU driver Date:   Thu Nov 5 18:30:28 2009 +0100
(II) NOUVEAU driver for NVIDIA chipset families :
	RIVA TNT    (NV04)
	RIVA TNT2   (NV05)
	GeForce 256 (NV10)
	GeForce 2   (NV11, NV15)
	GeForce 4MX (NV17, NV18)
	GeForce 3   (NV20)
	GeForce 4Ti (NV25, NV28)
	GeForce FX  (NV3x)
	GeForce 6   (NV4x)
	GeForce 7   (G7x)
	GeForce 8   (G8x)
(II) Primary Device is: PCI 01@00:00:0
(--) NOUVEAU(0): Chipset: "NVIDIA NV40"
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
	compiled for 1.7.1, module version = 1.0.0
	ABI class: X.Org Video Driver, version 6.0
(II) NOUVEAU(0): Initializing int10
(II) NOUVEAU(0): Bad V_BIOS checksum
(II) NOUVEAU(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib/xorg/modules/extensions/libdri.so
(II) NOUVEAU(0): Loaded DRI module
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "nouveau"
(EE) [drm] drmOpen failed.
(EE) NOUVEAU(0): [drm] error opening the drm
(EE) NOUVEAU(0): 864: 
(II) UnloadModule: "nouveau"
(II) UnloadModule: "dri"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/xorg/modules/libint10.so
(EE) Screen(s) found, but none have a usable configuration.

That is only a portion of the log where the error lies.The full log is here:http://fpaste.org/0sMm/
I personally compile all three components(D.R.M,linux-2.6,Mesa and Nouveau)from their respective repositories.

If you need any more logs,please let me know.
Regards,
STEVE555

lynnevan · #3 26th November 2009, 12:01 PM

My problem is very similar to the previous. I'll just highlight the errors. This happens w/ both the newest? rc7.git1 kernels, and only started w/ them:

[QUOTE](II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.

I have no clue how to do that.

(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.7.1, module version = 0.0.2
ABI class: X.Org Video Driver, version 6.0
(EE) open /dev/fb0: No such file or directory

This is true. There is no fb0 in /dev

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
[drm] failed to load kernel module "nouveau"

Likewise:# modprobe nouveau
FATAL: Module nouveau not found.

(EE) [drm] drmOpen failed.
(EE) NOUVEAU(0): [drm] error opening the drm
(EE) NOUVEAU(0): 877:
(II) UnloadModule: "nouveau"
(II) UnloadModule: "dri"
(II) UnloadModule: "int10"
(II) Unloading /usr/lib/xorg/modules/libint10.so
(EE) Screen(s) found, but none have a usable configuration.[/QUOTE]

Any kind of help or hints would be welcome.

Am using an NVIDIA graphics card but have made no attempt to install NVIDIA driver.

Thanks in advance.

STEVE555 · #4 27th November 2009, 12:12 AM

Having looking deeper into the problem,I tried to compile the linux-2.6 nouveau kernel modules against the latest 2.6.31.5-127.fc12.i686 kernel..It came up with this error:

Code:

CC [M]  /opt/linux-2.6/drivers/gpu/drm/drm_sysfs.o
/opt/linux-2.6/drivers/gpu/drm/drm_sysfs.c: In function ‘drm_sysfs_create’:
/opt/linux-2.6/drivers/gpu/drm/drm_sysfs.c:116: error: ‘struct class’ has no member named ‘nodename’
make[2]: *** [/opt/linux-2.6/drivers/gpu/drm/drm_sysfs.o] Error 1
make[1]: *** [_module_/opt/linux-2.6/drivers/gpu/drm] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.32-0.51.rc7.git2.fc13.i686'
make: *** [modules] Error 2

.

The full log is here:[URL="http://fpaste.org/73nP/"[/URL] I guess we should have to wait until the nouveau devs adjust the repository to work with the new kernel,or for fedora to bring out a new kernel?

Regards,
STEVE555

lynnevan · #5 27th November 2009, 11:39 AM

Frustrating, but I think you're right.

I couldn't do half what you did, so in my case it's going to be a matter of patience.

Thanks for the effort.

STEVE555 · #6 27th November 2009, 10:50 PM

Hi guys,
I'm happy to report that after updating with yum tonight,the latest kernel(2.6.32-0.55.rc8.git1.fc13.i686) will boot to the desktop

.I am currently compiling my source code with the new kernel.D.R.M was fine to compile,but I just tried the Linux-2.6 source code,but that failed with the same error I posted earlier.I guess I'll talk on the I.R.C channel about that

.I just have to re-compile Mesa and the Nouveau driver.I would like to to thank the Fedora developers for getting this latest kernel to get to the desktop.

Regards,
STEVE555

lynnevan · #7 28th November 2009, 01:04 AM

Good news. Got all weekend to play w/ it.

lynnevan · #8 29th November 2009, 09:11 AM

You were right. The Deskop exists!! Hurray!!
But the battle goes on.
While I am waiting for the Desktop to show up, a message flashes up in the corner that I had to film, because it passed to quickly to read. These two lines:

Quote:

FATAL: module dm_mod not found.
(drm) nouveau 0000:02:00.0 failed to evaluate _DSM: 5

I googled dm_mod, and it seemed to have to do w/ encryped partitions! Do I have my wires crossed?

Did you get drm compiled to your satisfaction? If I "vim /var/log/messages", the 2nd line quoted above shows like a red stop light.

Likewise:

Quote:

fedright nmbd[1484]: bind failed on port 137 socket_addr = 172.16.0.1.
fedright nmbd[1484]: Error = Cannot assign requested address
fedright nmbd[1484]: [2009/11/28 13:53:38, 0] nmbd/nmbd_subnetdb.c:99(make_subnet)
fedright nmbd[1484]: nmbd_subnetdb:make_subnet()
fedright nmbd[1484]: Failed to open nmb socket on interface 172.16.0.1
fedright nmbd[1484]: for port 137.
fedright nmbd[1484]: Error was Cannot assign requested address
fedright nmbd[1484]: [2009/11/28 13:53:38, 0] nmbd/nmbd.c:960(main)
fedright nmbd[1484]: ERROR: Failed when creating subnet lists. Exiting.

And, of course, nmbd won't run, period.

But that's another story and not relevant here. I would like to know if you're have any kind of similar errors w/ "drm"

thanks

STEVE555 · #9 29th November 2009, 10:33 AM

Hi lynnevan,
With dm_mod,you do have your wires crossed,I've googled that too and that has to do with the Device-Mapper in the kernel.

The main issue I'm having is trying to build the Nouveau Kernel Modules from the git repository with the latest kernel.I've talked about the error on the Nouveau I.R.C Channel,but one of them told me it wasn't a problem from Nouveau.So I said I'll wait for the next kernel for it to be fixed.

I have no trouble building the source code of D.R.M.The only issue I have with that is if install the packaged version of D.R.M,and I want to re-compile Mesa,Mesa comes up with this error:

Code:

N -DUSE_XCB -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -DHAVE_XEXTPROTO_71  nv30_state_fb.c -o nv30_state_fb.o
nv30_state_fb.c: In function ‘nv30_state_framebuffer_validate’:
nv30_state_fb.c:46: error: ‘NV34TCL_RT_FORMAT_LOG2_WIDTH_SHIFT’ undeclared (first use in this function)
nv30_state_fb.c:46: error: (Each undeclared identifier is reported only once
nv30_state_fb.c:46: error: for each function it appears in.)
nv30_state_fb.c:47: error: ‘NV34TCL_RT_FORMAT_LOG2_HEIGHT_SHIFT’ undeclared (first use in this function)
gmake[4]: *** [nv30_state_fb.o] Error 1
gmake[4]: Leaving directory `/opt/mesa/src/gallium/drivers/nv30'
gmake[3]: *** [default] Error 1
gmake[3]: Leaving directory `/opt/mesa/src/gallium/drivers'
gmake[2]: *** [default] Error 1
gmake[2]: Leaving directory `/opt/mesa/src/gallium'
gmake[1]: *** [subdirs] Error 1
gmake[1]: Leaving directory `/opt/mesa/src'
gmake: *** [default] Error 1

Then I have to re-compile the D.R.M source code for Mesa to build properly.I had brought up the issue on the Nouveau channel,but they told me it was Fedora's issue,but I hope the next packaged version of D.R.M will fix that too.

Regards,
STEVE555

lynnevan · #10 29th November 2009, 12:11 PM

Thanks for clearing that up about dm_mod. I'll have to look closer or use different key words. Wish I was more educated about compiling. Can you recommend some HOW-TOs?

thanks

STEVE555 · #11 29th November 2009, 05:24 PM

Hi lynnevan,
If you are feeling brave and want to compile this sort of stuff,have a look at this link to get you started:http://nouveau.freedesktop.org/wiki/ and then:
http://nouveau.freedesktop.org/wiki/InstallNouveau and please have a look at the warning for compiling Mesa.
http://nouveau.freedesktop.org/wiki/GalliumHowto

Any help you might need,I would suggest to start a new thread in the Rawhide section.

Regards,
STEVE555

lynnevan · #12 3rd December 2009, 04:39 AM

Being comfortable with compiling isn't really specific to rawhide, but thanks for the links. I'm sure they'll be useful generally and I might even try to fix some things like missing floppy icons in F11, or floppy icons that can't detect floppies in F13.

Again, thanks for the links.