Weird ABI error with Drivers v1.0.8762 AND xorg-x11 v7.0-r1

jmmf · 07-19-06, 03:02 AM

O.K., this one really has me puzzled...

I'm running current (v2006.0) Gentoo (Unstable = ~x86) Linux with normally updated S/W packages.

I installed (emerged) latest nvidia-kernel v1.0.8762-r1 AND nvidia-glx v1.0.8762, PLUS xorg-x11 v7.0-r1 (I manually "masked" v7.1 stuff, due to the ABI change).

My problem is, issuing "startx", X server dies with this error:

Code:

xauth:  creating new authority file /root/.serverauth.10925

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/AntiMinas-1.ing.puc.cl:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:UNKNOWN
Current Operating System: Linux AntiMinas-1.ing.puc.cl 2.6.15-gentoo-r8-IMM #1 SMP Thu Jun 1 18:18:26 CLT 2006 i686
Build Date: 30 June 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 19 01:23:30 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) module ABI major version (1) doesn't match the server's version (0)
(EE) Failed to load module "nv" (module requirement mismatch, 0)
(EE) module ABI minor version (6) is newer than the server's version (5)
(EE) Failed to load module "mouse" (module requirement mismatch, 0)
(EE) module ABI minor version (6) is newer than the server's version (5)
(EE) Failed to load module "kbd" (module requirement mismatch, 0)
(EE) No drivers available.

Fatal server error:
no screens found
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

¿What's going on with the ABI, if I AM KEEPING on xorg 7.0? As it appears to be by this errors, it sounds like nvidia modules already have an updated ABI version. ¿How is this possible?

This is what I've *manually* masked, so it's never being installed:

Code:

>=x11-base/xorg-x11-7.1
>=x11-base/xorg-server-1.1.0
>=x11-drivers/xf86-input-evdev-1.1.2-r1
>=x11-drivers/xf86-video-vesa-1.2.0
>=x11-drivers/xf86-input-mouse-1.1.1
>=x11-drivers/xf86-input-keyboard-1.1.0

And well, here are my (zipped) "xorg.conf" and "nvidia-bug-report.log".

Hope that someone could bring some light on this. Regards...

jmmf · 07-19-06, 03:07 AM

Please note that, THAT xorg.conf was working a while back whn I was using default nvidia modules from X drivers. TIA...

**AaronP** · 07-19-06, 12:47 PM

@jmmf,
Those errors indicate that the nv, mouse, and kbd drivers were built against X.org 7.1. You should be able to fix them by recompiling:

Code:

emerge xf86-video-nv xf86-input-mouse xf86-input-keyboard

jmmf · 07-19-06, 05:21 PM

Thank you very very much...

... In order to do as you recommended, I had to add 2 more "maskings" for "video-nv" and "video-vesa", so my /etc/portage/package.mask file looks like this:

Code:

AntiMinas-1 ~ # cat /etc/portage/package.mask 
# Obscure "InitRAMFS" generation related GenKernel problems went away with this:
<=sys-kernel/genkernel-3.3.11d-r1

# xorg 7.1 stuff that needs masking until NVidia releases a compatible driver
>=x11-base/xorg-x11-7.1
>=x11-base/xorg-server-1.1.0
>=x11-drivers/xf86-input-evdev-1.1.2-r1
>=x11-drivers/xf86-input-keyboard-1.1.0
>=x11-drivers/xf86-input-mouse-1.1.1
>=x11-drivers/xf86-video-nv-1.1.1
>=x11-drivers/xf86-video-vesa-1.1.1

AntiMinas-1 ~ #

... As it appeared I had "xf86-video-nv-1.2.0" already installed, just un un-emerge and re-emerge corrected my problems after the new masking.

Again, thank youuu very much, AaronP !!!

jmmf · 07-19-06, 05:51 PM

... Off-topic: That line just resolved that f****** genkernel problem no longer genererating a corresponding InitRAMFS when compiling new kernel, for "gentoo-sources-2.6.17-r3". (And for v2.6.17 kernels in general, I think...)

For this to work, I had to do the following, after masking genkernel v3.3.11d and previous:

1-) Get an updated "genkernel-3.3.11d-r1.ebuild" (PLEASE note the "-r1" here...) from bugs.gentoo.org (I think), and then manually copy it to /usr/portage/sys-kernel/genkernel.

2-) Issue the command:

Code:

ebuild /usr/portage/sys-kernel/genkernel/genkernel-3.3.11d-r1.ebuild digest

3-) And then:

Code:

emerge =genkernel-3.3.11d-r1

4-) As i *DESPERATELY* need dmraid at boot time, get dmraid-1.0.0.rc11-pre1.tar.bz2 (rc10 DON'T WORK with kernel 2.6.17) from: http://people.redhat.com/~heinzm/sw/dmraid/tst/old

5-) RENAME the dmraid source package, DELETING the "-pre1" segment (as that CONFUSES GENKERNEL), and then copy it to the /usr/share/genkernel/pkg directory.

6-) Edit the /etc/genkernel.conf file accordingly, to reflect dmraid's version change

7-) And finally, to allow dmraid v1.0.0.rc11-pre1 to sucessfully compile (and be included in the InitRAMFS), I had to invoke genkernel like this:

Code:

LIBS="-lselinux -lsepol" genkernel --dmraid initrd

(If you are missing SELinux libraries, just emerge them, and then, as long as you preserve "dmraid" in your genkernel cache, you can eventually un-emerge them)...

mworld · 08-28-06, 12:12 AM

This worked dude, you're a legend! I've been looking for the answer to this for many many hours and they were all along these lines but not quite there.

Quote:

Originally Posted by jmmf

... Off-topic: That line just resolved that f****** genkernel problem no longer genererating a corresponding InitRAMFS when compiling new kernel, for "gentoo-sources-2.6.17-r3". (And for v2.6.17 kernels in general, I think...)

For this to work, I had to do the following, after masking genkernel v3.3.11d and previous:

1-) Get an updated "genkernel-3.3.11d-r1.ebuild" (PLEASE note the "-r1" here...) from bugs.gentoo.org (I think), and then manually copy it to /usr/portage/sys-kernel/genkernel.

2-) Issue the command:

Code:

ebuild /usr/portage/sys-kernel/genkernel/genkernel-3.3.11d-r1.ebuild digest

3-) And then:

Code:

emerge =genkernel-3.3.11d-r1

4-) As i *DESPERATELY* need dmraid at boot time, get dmraid-1.0.0.rc11-pre1.tar.bz2 (rc10 DON'T WORK with kernel 2.6.17) from: http://people.redhat.com/~heinzm/sw/dmraid/tst/old

5-) RENAME the dmraid source package, DELETING the "-pre1" segment (as that CONFUSES GENKERNEL), and then copy it to the /usr/share/genkernel/pkg directory.

6-) Edit the /etc/genkernel.conf file accordingly, to reflect dmraid's version change

7-) And finally, to allow dmraid v1.0.0.rc11-pre1 to sucessfully compile (and be included in the InitRAMFS), I had to invoke genkernel like this:

Code:

LIBS="-lselinux -lsepol" genkernel --dmraid initrd

(If you are missing SELinux libraries, just emerge them, and then, as long as you preserve "dmraid" in your genkernel cache, you can eventually un-emerge them)...

jmmf · 08-28-06, 04:10 AM

Wow, thanks man...

... Feels REALLY good to know that post was worth the typing, being useful to someone... (I HATE typing...)

Thank you for reporting back and for letting me know. (That "investigation" I did was a bit frustrating most of the time it took.)

Best regards.

P.S.: There is a new GenKernel out now. Never tested this under it. If someone tryes it out, please report back.

07-19-06, 03:07 AM	#2
jmmf Paranoid Android... Join Date: Jul 2006 Location: Santiago, Chile Posts: 5	Re: Weird ABI error with Drivers v1.0.8762 AND xorg-x11 v7.0-r1 Please note that, THAT xorg.conf was working a while back whn I was using default nvidia modules from X drivers. TIA...

07-19-06, 12:47 PM	#3
AaronP NVIDIA Corporation Join Date: Mar 2005 Posts: 1,925	Re: Weird ABI error with Drivers v1.0.8762 AND xorg-x11 v7.0-r1 @jmmf, Those errors indicate that the nv, mouse, and kbd drivers were built against X.org 7.1. You should be able to fix them by recompiling: Code: emerge xf86-video-nv xf86-input-mouse xf86-input-keyboard

07-19-06, 05:21 PM	#4
jmmf Paranoid Android... Join Date: Jul 2006 Location: Santiago, Chile Posts: 5	Re: Weird ABI error with Drivers v1.0.8762 AND xorg-x11 v7.0-r1 Thank you very very much... ... In order to do as you recommended, I had to add 2 more "maskings" for "video-nv" and "video-vesa", so my /etc/portage/package.mask file looks like this: Code: AntiMinas-1 ~ # cat /etc/portage/package.mask # Obscure "InitRAMFS" generation related GenKernel problems went away with this: <=sys-kernel/genkernel-3.3.11d-r1 # xorg 7.1 stuff that needs masking until NVidia releases a compatible driver >=x11-base/xorg-x11-7.1 >=x11-base/xorg-server-1.1.0 >=x11-drivers/xf86-input-evdev-1.1.2-r1 >=x11-drivers/xf86-input-keyboard-1.1.0 >=x11-drivers/xf86-input-mouse-1.1.1 >=x11-drivers/xf86-video-nv-1.1.1 >=x11-drivers/xf86-video-vesa-1.1.1 AntiMinas-1 ~ # ... As it appeared I had "xf86-video-nv-1.2.0" already installed, just un un-emerge and re-emerge corrected my problems after the new masking. Again, thank youuu very much, AaronP !!!

07-19-06, 05:51 PM	#5
jmmf Paranoid Android... Join Date: Jul 2006 Location: Santiago, Chile Posts: 5	Re: About that strange "GenKernel" part of "package.mask"... ... Off-topic: That line just resolved that f**** genkernel problem no longer genererating a corresponding InitRAMFS when compiling new kernel, for "gentoo-sources-2.6.17-r3". (And for v2.6.17 kernels in general, I think...) For this to work, I had to do the following, after masking genkernel v3.3.11d and previous: 1-) Get an updated "genkernel-3.3.11d-r1.ebuild" (PLEASE note the "-r1" here...) from bugs.gentoo.org (I think), and then manually copy it to /usr/portage/sys-kernel/genkernel. 2-) Issue the command: Code: ebuild /usr/portage/sys-kernel/genkernel/genkernel-3.3.11d-r1.ebuild digest 3-) And then: Code: emerge =genkernel-3.3.11d-r1 4-) As i DESPERATELY need dmraid at boot time, get dmraid-1.0.0.rc11-pre1.tar.bz2 (rc10 DON'T WORK with kernel 2.6.17) from: http://people.redhat.com/~heinzm/sw/dmraid/tst/old 5-) RENAME the dmraid source package, DELETING the "-pre1" segment (as that CONFUSES GENKERNEL), and then copy it to the /usr/share/genkernel/pkg directory. 6-) Edit the /etc/genkernel.conf** file accordingly, to reflect dmraid's version change 7-) And finally, to allow dmraid v1.0.0.rc11-pre1 to sucessfully compile (and be included in the InitRAMFS), I had to invoke genkernel like this: Code: LIBS="-lselinux -lsepol" genkernel --dmraid initrd (If you are missing SELinux libraries, just emerge them, and then, as long as you preserve "dmraid" in your genkernel cache, you can eventually un-emerge them)...

08-28-06, 04:10 AM	#7
jmmf Paranoid Android... Join Date: Jul 2006 Location: Santiago, Chile Posts: 5	Re: About that strange "GenKernel" part of "package.mask"... Wow, thanks man... ... Feels REALLY good to know that post was worth the typing, being useful to someone... (I HATE typing...) Thank you for reporting back and for letting me know. (That "investigation" I did was a bit frustrating most of the time it took.) Best regards. P.S.: There is a new GenKernel out now. Never tested this under it. If someone tryes it out, please report back.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)