[gentoo-user] nvidia-drivers problem on xorg 1.6.3.901-r2
Arnau Bria
I've rebuild my xorg-server with no hal support, I've upgraded my kernel
to 2.6.30-r8 and rebuild "all" xf86 drivers/libs/proto packages:
# eix xf86|grep "^\[I\]"
[I] x11-apps/xf86dga
[I] x11-drivers/xf86-input-evdev
[I] x11-drivers/xf86-input-keyboard
[I] x11-drivers/xf86-input-mouse
[I] x11-drivers/xf86-video-nv
[I] x11-drivers/xf86-video-vesa
[I] x11-libs/libXxf86dga
[I] x11-libs/libXxf86misc
[I] x11-libs/libXxf86vm
[I] x11-proto/xf86bigfontproto
[I] x11-proto/xf86dgaproto
[I] x11-proto/xf86driproto
[I] x11-proto/xf86miscproto
[I] x11-proto/xf86rushproto
[I] x11-proto/xf86vidmodeproto
Then, I use nvidia-xconf for geenrating my xorg.conf file and looks
like:
Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "extmod"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "My Monitor"
HorizSync 70.0 - 84.0
VertRefresh 60.0 - 85.0
EndSection
Section "Device"
Identifier "VGA"
Driver "vesa"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "VGA"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
and when I start X, system goes really slow and I see some
errors/warnings in X log file:
# grep EE Xorg.0.log
to load module "freetype" (module does not exist, 0)
to load module "dri" (module does not exist, 0)
to load module "dri2" (module does not exist, 0)
# grep WW Xorg.0.log
nConsole: setpgid failed: Operation not permitt
nConsole: setsid failed: Operation not permitte
, couldn't open module freetype
, couldn't open module dri
, couldn't open module dri2
0): WAIT (0, 6, 0x8000, 0x0000987c, 0x0000987c)
0): WAIT (2, 6, 0x8000, 0x0000d478, 0x000002e4)
0): WAIT (1, 6, 0x8000, 0x0000d478, 0x000002e4)
and a tail:
tail Xorg.0.log
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Mouse1: ps2EnableDataReporting: succeeded
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Initialized AGP GART.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Mouse1: ps2EnableDataReporting: succeeded
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x0000d478, 0x000002e4)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x0000d478, 0x000002e4)
(II) NVIDIA(0): Initialized AGP GART
So i have to switch to vesa driver...
Anyone faced similar problem? how may I debug this problem deeply?
TIA,
--
Arnau Bria
http://blog.emergetux.net
Bombing for peace is like fucking for virginity
Alex Schuster
> I've rebuild my xorg-server with no hal support, I've upgraded my
> kernel to 2.6.30-r8 and rebuild "all" xf86 drivers/libs/proto
> packages:
[...]
> Then, I use nvidia-xconf for geenrating my xorg.conf file and looks
> like:
[...]
> Section "Device"
> Identifier "VGA"
> Driver "vesa"
> VendorName "Unknown"
> BoardName "Unknown"
> EndSection
>
> and when I start X, system goes really slow and I see some
> errors/warnings in X log file:
I would expect vesa to be quite slow. I don't know about nvidia-xconf and
where it comes from, probably because I do not have a nvidia card any
more. Does it really place "vesa" into the config?
What happens when you replace the "vesa" driver with "nvidia"? emerge
nvidia-drivers if not already done. If this fails, try "nv" instead, this
is the slower open source driver, which should be okay for 2D acceleration
at least.
> # grep EE Xorg.0.log
> to load module "freetype" (module does not exist, 0)
> to load module "dri" (module does not exist, 0)
> to load module "dri2" (module does not exist, 0)
I read something here about dri and dri2 some days ago, but don't
remember. I think they are not needed with nvidia-drivers or something
like that.
There is also X -configure which creates a new xorg.conf, but that
segfaults for some years on my machine.
And you could try with hal and no xorg.conf.
Wonko
Alan McKinnon
> Hi all,
>
> I've rebuild my xorg-server with no hal support, I've upgraded my kernel
> to 2.6.30-r8 and rebuild "all" xf86 drivers/libs/proto packages:
>
> # eix xf86|grep "^\[I\]"
> [I] x11-apps/xf86dga
> [I] x11-drivers/xf86-input-evdev
> [I] x11-drivers/xf86-input-keyboard
> [I] x11-drivers/xf86-input-mouse
> [I] x11-drivers/xf86-video-nv
> [I] x11-drivers/xf86-video-vesa
> [I] x11-libs/libXxf86dga
> [I] x11-libs/libXxf86misc
> [I] x11-libs/libXxf86vm
> [I] x11-proto/xf86bigfontproto
> [I] x11-proto/xf86dgaproto
> [I] x11-proto/xf86driproto
> [I] x11-proto/xf86miscproto
> [I] x11-proto/xf86rushproto
> [I] x11-proto/xf86vidmodeproto
According to this, you did not rebuild nvidia-drivers. Either
emerge nvidia-drivers
module-rebuild rebuild
--
alan dot mckinnon at gmail dot com
Alan McKinnon
> > # grep EE Xorg.0.log
> > to load module "freetype" (module does not exist, 0)
> > to load module "dri" (module does not exist, 0)
> > to load module "dri2" (module does not exist, 0)
>
> I read something here about dri and dri2 some days ago, but don't
> remember. I think they are not needed with nvidia-drivers or something
> like that.
>
Yes, dri and dri2 are not used by nvidia-drivers, they implement them itself.
But X will still try and look for them.
Best way to set up nvidia drivers from scratch is to install and run nvidia-
settings
Arnau Bria
Alex Schuster wrote:
> Arnau Bria writes:
[...]
> > Section "Device"
> > Identifier "VGA"
> > Driver "nvidia"
> > VendorName "Unknown"
> > BoardName "Unknown"
> > EndSection
> I would expect vesa to be quite slow. I don't know about nvidia-xconf
> and where it comes from, probably because I do not have a nvidia card
> any more. Does it really place "vesa" into the config?
no, no...
there's an error in my xorg.conf, it's not vesa but
nvidia, (as I need X for sending mail I had to use vesa driver for
starting X and did not remeber to change it in xorg.conf when sending
mail... ) :-S
> What happens when you replace the "vesa" driver with "nvidia"? emerge
> nvidia-drivers if not already done. If this fails, try "nv" instead,
> this is the slower open source driver, which should be okay for 2D
> acceleration at least.
when I use nvidia driver system goes really, really slow. about a
minute to change between worksapces, or open an aplication.
nv completly freezes my sytem.
nvidia-drivers are rebuild after kernel upgrade.
> > # grep EE Xorg.0.log
> > to load module "freetype" (module does not exist, 0)
> > to load module "dri" (module does not exist, 0)
> > to load module "dri2" (module does not exist, 0)
>
> I read something here about dri and dri2 some days ago, but don't
> remember. I think they are not needed with nvidia-drivers or
> something like that.
seem that, but if nvidia-xconfig don't try to load it, why X does?
lx-arnau ~ # nvidia-xconfig
Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'
lx-arnau ~ # grep dri /etc/X11/xorg.conf
## Load "dri"
> There is also X -configure which creates a new xorg.conf, but that
> segfaults for some years on my machine.
that's what I'm using.
> And you could try with hal and no xorg.conf.
no, few days ago I explained my hal problems :-) trying with no hal now.
> Wonko
Thanks for your reply,
Arnau Bria
yes, but if nvidia driver make X unoperative, how may I going to be
able to run nvidia-settings? isn't it a xorg-sevrer/nvidia driver
relaetd problem? I'm a bit confused...
Thansk for your reply,
Alan McKinnon
> On Thu, 12 Nov 2009 14:57:28 +0200
>
> Alan McKinnon wrote:
> > On Thursday 12 November 2009 14:33:22 Alex Schuster wrote:
> > > > # grep EE Xorg.0.log
> > > > to load module "freetype" (module does not exist, 0)
> > > > to load module "dri" (module does not exist, 0)
> > > > to load module "dri2" (module does not exist, 0)
> > >
> > > I read something here about dri and dri2 some days ago, but don't
> > > remember. I think they are not needed with nvidia-drivers or
> > > something like that.
> >
> > Yes, dri and dri2 are not used by nvidia-drivers, they implement them
> > itself.
> >
> > But X will still try and look for them.
> >
> > Best way to set up nvidia drivers from scratch is to install and run
> > nvidia- settings
>
> yes, but if nvidia driver make X unoperative, how may I going to be
> able to run nvidia-settings? isn't it a xorg-sevrer/nvidia driver
> relaetd problem? I'm a bit confused...
The ebuild outputs this elog:
echo
elog "You must be in the video group to use the NVIDIA device"
elog "For more info, read the docs at"
elog "http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6"
elog
Is the user in the video group?
Arnau Bria
Alan McKinnon wrote:
> According to this, you did not rebuild nvidia-drivers. Either
I did, but did not mention... sorry.
> emerge nvidia-drivers
> module-rebuild rebuild
it only rebuilds nvidia-driver:
x11-drivers/nvidia-drivers-180.60
Cheers,
Arnau Bria
Alan McKinnon wrote:
[...]
> The ebuild outputs this elog:
>
> echo
> elog "You must be in the video group to use the NVIDIA device"
> elog "For more info, read the docs at"
> elog
> "http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6" elog
>
>
> Is the user in the video group?
sure.
$ id
uid=1000(arnau) gid=1000(arnau) groups=10(wheel),16(cron),18(audio),19(cdrom),27(video),35(games),1000(arnau),1007(plugdev),1014(vboxusers)
it worked fine until xorg 1.6 and nvidia-driver upgrade. As I used hal,
and did not work fine for me, I first thought it was hal related, but
now seems other issue...
will read guide again, maybe I missed some step..
thanks for your reply,
Arnau Bria
Arnau Bria wrote:
[...]
> will read guide again, maybe I missed some step..
nop, no missed steps. :-(
Iain Buchanan
> On Thu, 12 Nov 2009 15:44:48 +0100
> Arnau Bria wrote:
>
> [...]
> > will read guide again, maybe I missed some step..
> nop, no missed steps. :-(
>
In my experience, various nvidia-drivers just seem to "not work" with my
system, no matter how many times I rebuild and recheck things. I have a
whole bunch of versions masked. Looking back, I never seemed to have a
problem with 180.60 - I ran it for about 4-6 weeks.
You could try adding this to /etc/portage/package.mask:
=x11-drivers/nvidia-drivers-180.60
Then decide whether you want to downgrade to the previous stable, or
upgrade to the latest unstable. I'm running unstable 190.42-r2 and so
far it's quite "stable", but as we've seen, every system is different!
(I'm on ~x86, so quite a bit of my system will differ from yours).
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
Man's reach must exceed his grasp, for why else the heavens?
Arnau Bria
Iain Buchanan wrote:
Hi,
> In my experience, various nvidia-drivers just seem to "not work" with
> my system, no matter how many times I rebuild and recheck things. I
> have a whole bunch of versions masked. Looking back, I never seemed
> to have a problem with 180.60 - I ran it for about 4-6 weeks.
>
> You could try adding this to /etc/portage/package.mask:
> =x11-drivers/nvidia-drivers-180.60
I did upgrade...
> Then decide whether you want to downgrade to the previous stable, or
> upgrade to the latest unstable. I'm running unstable 190.42-r2 and so
> far it's quite "stable", but as we've seen, every system is different!
> (I'm on ~x86, so quite a bit of my system will differ from yours).
here I'm... same version as you but diff revision .
[I] x11-drivers/nvidia-drivers
Installed versions: 190.42-r3!s(12:51:20 PM 11/16/2009)(acpi gtk kernel_li
X starts fine (I see NVidia logo for only half second) I can change
between workspaces fine, but when I open an application it hangs... I'm
lucky cause I can change to virtual console with Ctrl+Alt+F1 and no
reboot needed, but I'm really tired about this issue...
nv does not work neither and I don't know what else I can try... Vesa
sucks (well, at least I can see things in my screen if I take off my
glasses).... and I see no other people with same problem.
> HTH,
Thanks for your reply,