View previous topic :: View next topic |
Author |
Message |
ddvlad n00b

Joined: 25 Nov 2006 Posts: 58
|
Posted: Sun Feb 11, 2007 2:52 pm Post subject: First time kernel compiler experiencing some problems |
|
|
Hello,
after a couple of failed attempts some time ago, I actually ended up
with a kernel that boots (based on gentoo-sources). However, I am
experiencing some problems whichI think are at least in part due to
my perhaps incomplete kernel configuration.
First of all, my console is still in 80x24 mode, although I pass
video=vesafb:1024x768-32@72 to the kernel. I have compiled vesafb-tng
into the kernel, so specifying the vga mode is not needed, right? If I
add vga=0x318, the kernel complains about an unsupported mode and makes
me choose another. However, I know from my previous (genkernel-created)
kernel that these paramters work for my hardware setup.
Secondly, I installed nvidia-drivers, but the X server refuses to load
glx. I can't check for the exact error now, but it's something about an
unrecognised/unsupported format. If I set opengl to xorg-x11, X starts
(but I suppose it's not by far the same thing).
Could this be linked to the fact that my detected X settings are a bit
strange? For instance, the monitor VendorName and ModelName are just
generic strings and the subsections for the Screen section only contain
"ViewPort 0 0" in addition to Depth, which varies (correctly as far as I
can tell) from 1 to 24.
Other than that, and a bit offtopic, too, today has been both very fun
and incredibly educational (but a bit sore on the eyes). But after about
13 hours, I might not make much sense. Apologies beforehand if that is
the case.
Vlad |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55459 Location: 56N 3W
|
Posted: Sun Feb 11, 2007 5:48 pm Post subject: |
|
|
ddvlad,
Welcome to Gentoo. It sounds like you are climbing the learning curve.
If you post some specific questions, with error messages, it will be much easier to help you.
The kernel contains two classes of console drivers, frambuffer, which gives you a tux image per cpu/core at the top of the screen during boot and the older VGA text only console. You may build any combination into your kernel. Be advised that leaving them both out is normally a BadThing.
Since you want to use the nvidia driver for Xorg, you must only choose vesa or vesa-tng for a framebuffer driver.
As you say, you need not specify both vga and vesa.
There are a limited number of depth settings available. Depth sets the number of bits used for each pixel. Valid values are
1,4,8,15,16 and 24. Most modern drivers only support 16 and 24. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
wynn Advocate


Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Sun Feb 11, 2007 5:52 pm Post subject: |
|
|
Although 0x318 is in the table in Using framebuffer devices on Intel platforms "5.3 What VESA modes are available to me?", 0x317 works OK here.
The settings under "Graphics support" here are Code: | [*] Enable firmware EDID
<*> Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
(1280x1024@75) VESA default mode | and nothing else.
To get any further with your nvidia/glx problem will probably need your xorg.conf â please use Code: | sed -r "/^[[:space:]]*([#;].*)*$/d" /etc/X11/xorg.conf | (JoeUser's confcat) to remove blank lines and comments to get the version for posting.
/var/log/Xorg.0.log will also be helpful. _________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
 |
ddvlad n00b

Joined: 25 Nov 2006 Posts: 58
|
Posted: Sun Feb 11, 2007 6:59 pm Post subject: |
|
|
Hi guys,
Sorry about not being specific enough in my previous post. I managed to make the framebuffer work the way I hoped to, though I don't exactly know how. I'll settle with that for now -- I'll fiddle with it until I understand *after* I get nvidia-drivers working.
I tried reinstalling nvidia-drivers a few times, all to no avail. I looked in the log file, but it seems that the following bit is the only problem, so I'll only post it instead of the whole log (it's what I get at stdout when running X):
Code: | dlopen: /usr/lib/xorg/modules/extensions/libglx.so: cannot handle TLS data
(EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so
(EE) Failed to load module "glx" (loader failed, 7)
(EE) Failed to load module "wfb" (module does not exist, 0)
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
(EE) NVIDIA(0): you continue to encounter problems, Please try
(EE) NVIDIA(0): reinstalling the NVIDIA driver.
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc105)+us" };
xkb_geometry { include "pc(pc105)" };
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing. |
X then starts up okay (and the opengl driver is set to nvidia), but: Code: | $ glxinfo
glxinfo: error while loading shared libraries: libGL.so.1: cannot handle TLS data |
Here is the contents of my xorg.conf file: Code: | Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
Load "record"
Load "xtrap"
Load "glx"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV31 [GeForce FX 5600]"
BusID "PCI:1:0:0"
VideoRam 262143
Option "NoLogo" "true"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768"
EndSubSection
EndSection |
|
|
Back to top |
|
 |
wynn Advocate


Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Sun Feb 11, 2007 7:16 pm Post subject: |
|
|
It looks as though you haven't run Code: | eselect opengl set nvidia | as Xorg is failing to load libglx.so from /usr/lib/xorg/modules/extensions which should be Code: | lrwxrwxrwx 1 root root 43 Feb 6 11:50 /usr/lib/xorg/modules/extensions/libglx.so -> /usr/lib/opengl/nvidia/extensions/libglx.so | with Code: | (II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.9746
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) Loading extension GLX | showing it's the NVidia one. _________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55459 Location: 56N 3W
|
Posted: Sun Feb 11, 2007 7:18 pm Post subject: |
|
|
ddvlad,
Code: | (EE) Failed to load module "glx" (loader failed, 7)
(EE) Failed to load module "wfb" (module does not exist, 0) |
Suggests you have some missing files. What usually happens is that they are not in the place were Xorg looks.
Thats the ModulePath listed close to the top of the log.
The fix is to add further ModulePath statements to xorg.con in the Section Files or make some symbolic links.
You need to find the files first though. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
ddvlad n00b

Joined: 25 Nov 2006 Posts: 58
|
Posted: Sun Feb 11, 2007 7:43 pm Post subject: |
|
|
After running eselect opengl set nvidia, the symlink is correct, but I end up with a blank screen -- I can't switch consoles or restart X, but thankfully I can reboot with Ctrl-Alt-Delete.
I also added a ModulesPath directive to /usr/lib/xorg/modules/extensions; wtb gets loaded (or at least doesn't get complained about), but I get the same error with glx: Code: | dlopen: /usr/lib/xorg/modules/extensions/libglx.so: cannot handle TLS data |
Funny thing is that, even with the xorg-x11 opengl driver, I still get the error, and (after removing a line in xorg.conf) the fancy nvidia splash screen.
PS: I double-checked and my kernel does not contain nvidia framebuffer support, so this cannot be the problem. |
|
Back to top |
|
 |
ddvlad n00b

Joined: 25 Nov 2006 Posts: 58
|
Posted: Sun Feb 11, 2007 10:07 pm Post subject: |
|
|
Thanks for all your help guys, I learned quite a few things from this whole mess. I've solved the problem by installing an older version of the drivers and compiling xorg-server without dri. I found instructions here http://www.nvnews.net/vbulletin/showthread.php?t=82947&page=4 and I hope others will find them helpful; I also hope that linking off-site isn't frowned upon.
All the best,
Vlad |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55459 Location: 56N 3W
|
Posted: Sun Feb 11, 2007 10:45 pm Post subject: |
|
|
ddvlad,
We are not keen on off site links that use non portage ways of doing things but since those instructions are for Gentoo, I won't remove the link. (Someone else may)
If you read the fine print in the guide, it tells you to comment out Load dri and the entire Section DRI, in xorg.conf
You may not need the legacy drivers. That depends on your nVidia graphics chip. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
ddvlad n00b

Joined: 25 Nov 2006 Posts: 58
|
Posted: Sun Feb 11, 2007 11:37 pm Post subject: |
|
|
A few remarks are in order:
- the final post of the thread (up until now) lists how to solve the problem using portage -- no other hacks are required.
- I had commented out dri loading from the very beginning -- I am not sure why the solution worked for me
- I didn't mean legacy drivers -- just an older, stable version of the regular ones.
Vlad |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|