Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Thu, 25 Aug 2011 10:37:31 +0200 Polytropon wrote: > On Tue, 16 Aug 2011 14:15:03 -0500, Conrad J. Sabatier wrote: > > > > Yes, the driver performs quite admirably. :-) No more gnashing my > > teeth in envy of others with true hardware-accelerated drivers. > > I'm currently using that driver, and everything seems to > work as intended. The only problem I have is that the > driver has different DPI opinions as the previous ones. > This makes some fonts unreadable. I found that I can > easily change the Gtk+ base font by a ~/.gtkrc-2.0 > with something like ``gtk-font-name="Tahoma 12"'' in > it, but this of course doesn't apply everywhere. Yes, I noticed this, too, as soon as I switched to using this driver. Fonts shrank all over the place. :-) I hadn't considered adjusting the DPI. That sounds like an interesting possibility. > There seems to be a solution to handle DPI settings in > X directly, so I put "DisplaySize 410 305" in the monitor > section of xorg.conf. The monitor is an Eizo FlexScan F980 > 21" CRT with BNC cabling, so no autodetect magic. But some > things still are wrong, maybe I should try ``Option "DPI" > "96 x 96"'' in the device section - I'm not sure which > values should be used, 72 or 75 or 96 or 115... > > Additionally, the gv program has a problem (but it already > had that on _each_ of the three drivers): The keys for > selecting pages are squished. > > This is how they should look like: > > http://t16web.lanl.gov/Kawano/gnuplot/intro/plotcalc7.png > > They are like this: > > +-+ +-+ +-+ +-+ > |* ===| | ===| | ===| | ===| > | ===| |* ===| | ===| | ===| > |* ===| | ===| |* ===| | ===| > | ===| |* ===| | ===| | ===| > +-+ +-+ +-+ +-+ > > SHOULD like. Currently, they look like this: > > +-+ +-+ +-+ +-+ > |#| |#| |#| |#| > +-+ +-+ +-+ +-+ > > You can't tell which is which. > > The gv program uses Xaw3d for the display elements. Maybe nVidia > is not compatible with that? Or it's also a "wrong DPI" effect? > Everything else in gv works as intended. Hmm, sorry, I don't know about that. You may find the following link helpful: http://www.retrevo.com/support/Eizo-F980-Monitors-manual/id/1360bh645/t/2/ > On the other hand, mplayer can now change brightness and contrast > again; I have put "vo=gl" in ~/.mplayer/config and it works. :-) Cool, I'll have to try that. > > > I'd like to point out that the nvidia driver comes with > > > nice documentation: /usr/local/share/doc/NVIDIA_GLX-1.0/README > > > contains lots of great stuff. > > > > The html version is even nicer to work with: > > > > file:///usr/local/share/doc/NVIDIA_GLX-1.0/html/index.html > > Thanks for the pointer, yes, that's really informative. During > the near future, I'm interested in getting Twinview + Xinerama > working (as I actually have _two_ 21" CRTs of the same type) > and TV out working. There's almost too much documentation for this driver. So much to look at and tinker with. Great fun it is, though. :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Tue, 16 Aug 2011 14:15:03 -0500, Conrad J. Sabatier wrote: > On Sun, 14 Aug 2011 05:49:42 +0200 > Polytropon wrote: > > > Meanwhile, I got the "nvidia" driver compiled, installed > > and running. Tests like > > > > % xlock -nolock -mode lament > > > > or > > > > % xlock -nolock -mode fire > > > > show the FPS rate I've expected (no comparison to the 3 > > fps I got with "nv"). In "gears" there are > 5000 FPS, > > that's _magnitudes_ better than with "nv". > > Yes, the driver performs quite admirably. :-) No more gnashing my > teeth in envy of others with true hardware-accelerated drivers. I'm currently using that driver, and everything seems to work as intended. The only problem I have is that the driver has different DPI opinions as the previous ones. This makes some fonts unreadable. I found that I can easily change the Gtk+ base font by a ~/.gtkrc-2.0 with something like ``gtk-font-name="Tahoma 12"'' in it, but this of course doesn't apply everywhere. There seems to be a solution to handle DPI settings in X directly, so I put "DisplaySize 410 305" in the monitor section of xorg.conf. The monitor is an Eizo FlexScan F980 21" CRT with BNC cabling, so no autodetect magic. But some things still are wrong, maybe I should try ``Option "DPI" "96 x 96"'' in the device section - I'm not sure which values should be used, 72 or 75 or 96 or 115... Additionally, the gv program has a problem (but it already had that on _each_ of the three drivers): The keys for selecting pages are squished. This is how they should look like: http://t16web.lanl.gov/Kawano/gnuplot/intro/plotcalc7.png They are like this: +-+ +-+ +-+ +-+ |* ===| | ===| | ===| | ===| | ===| |* ===| | ===| | ===| |* ===| | ===| |* ===| | ===| | ===| |* ===| | ===| | ===| +-+ +-+ +-+ +-+ SHOULD like. Currently, they look like this: +-+ +-+ +-+ +-+ |#| |#| |#| |#| +-+ +-+ +-+ +-+ You can't tell which is which. The gv program uses Xaw3d for the display elements. Maybe nVidia is not compatible with that? Or it's also a "wrong DPI" effect? Everything else in gv works as intended. On the other hand, mplayer can now change brightness and contrast again; I have put "vo=gl" in ~/.mplayer/config and it works. :-) > > I'd like to point out that the nvidia driver comes with > > nice documentation: /usr/local/share/doc/NVIDIA_GLX-1.0/README > > contains lots of great stuff. > > The html version is even nicer to work with: > > file:///usr/local/share/doc/NVIDIA_GLX-1.0/html/index.html Thanks for the pointer, yes, that's really informative. During the near future, I'm interested in getting Twinview + Xinerama working (as I actually have _two_ 21" CRTs of the same type) and TV out working. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, 14 Aug 2011 05:49:42 +0200 Polytropon wrote: > Meanwhile, I got the "nvidia" driver compiled, installed > and running. Tests like > > % xlock -nolock -mode lament > > or > > % xlock -nolock -mode fire > > show the FPS rate I've expected (no comparison to the 3 > fps I got with "nv"). In "gears" there are > 5000 FPS, > that's _magnitudes_ better than with "nv". Yes, the driver performs quite admirably. :-) No more gnashing my teeth in envy of others with true hardware-accelerated drivers. > But my text font in Sylpheed as well as the one used in > intclock is not a bit damaged (just chose a different one > in Sylpheed so I can see what I'm currently typing). > > The next thing I have to try is triggering the system > freeze by using any Gtk+ application. :-) > > I'd like to point out that the nvidia driver comes with > nice documentation: /usr/local/share/doc/NVIDIA_GLX-1.0/README > contains lots of great stuff. The html version is even nicer to work with: file:///usr/local/share/doc/NVIDIA_GLX-1.0/html/index.html -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, 14 Aug 2011, Polytropon wrote: And just in case I have to replace it (PCIe required), what brand of GPU should I buy instead? Again nVidia, or better ATI, or Intel? It's a hard decision because I don't want to get from one trouble into the next one... Radeon HD4650 has worked well for me for some time. The only problem I've seen is Firefox occasionally corrupts window borders. That might be Firefox or GTK or the radeon driver, but has been minor enough that I haven't pursued it. Some people report lockup problems with other versions of Radeon on the forums, cause unknown so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, Aug 13, 2011 at 11:01 PM, Polytropon wrote: > > What I don't understand is how a port that's more than > one year old can require a X server version that's not > reached yet _today_... :-) > Not exactly related to your point here, but you should also be aware of the WITHOUT_NOUVEAU macro. When set, nouveau will not work, but it does allow for much newer versions of some graphics subsystems which should give you better performance and possibly stability. As I said earlier, nouveau is to be avoided on FreeBSD. Newer versions of nouveau require KMS AKAIK, so it might be better to revisit that port when support is added to the kernel. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, Aug 14, 2011 at 10:21 AM, Gurpreet Singh wrote: > > > ---Start-- > Installing it should be as simple as below procedure provided you have > base sources in /usr/src. > > > # cd /usr/src/sys > # fetch http://people.freebsd.org/~rnoland/drm-nouveau-062309.patch > # patch -sp0 -i drm-nouveau-062309.patch > # cd modules/drm > # make depend all install > ---End-- > I should mention that before following these steps I installed xf86-video-nouveau package using "make install". It was then that I was showing the above message. Regards, Gurpreet -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, Aug 14, 2011 at 6:52 AM, Polytropon wrote: > > Has anyone got the "nouveau" driver working, and if, > how precisely has he done so? > I am using nouveau driver on FreeBSD 8.2 Release with resolution 1280x1024. I have Nvidia GeForce 7025 card embedded in my Asus Mobo. CPU: AMD Phenom(tm) II X2 545 Processor (3013.73-MHz K8-class CPU) I am able to run nouveau driver by simply following the instructions given in package xf86-video-nouveau's pkg-message file: These are those instructions: ---Start-- Installing it should be as simple as below procedure provided you have base sources in /usr/src. # cd /usr/src/sys # fetch http://people.freebsd.org/~rnoland/drm-nouveau-062309.patch # patch -sp0 -i drm-nouveau-062309.patch # cd modules/drm # make depend all install ---End-- Here is my Xorg's version: ---Start- X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-RELEASE amd64 Current Operating System: FreeBSD amnesiac 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 11 August 2011 11:06:01PM ---End-- And I didn't changed anything in my xorg.conf generate by Xorg -configure except changing Driver nv to nouveau in Device section. Here it is: --Start-- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "extmod" Load "record" Load "dbe" Load "glx" Load "dri" Load "dri2" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option"Protocol" "auto" Option"Device" "/dev/sysmouse" Option"ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "SWcursor" # [] #Option "HWcursor" # [] #Option "NoAccel"# [] #Option "ShadowFB" # [] #Option "UseFBDev" # [] #Option "Rotate" # [] #Option "VideoKey" # #Option "FlatPanel" # [] #Option "FPDither" # [] #Option "CrtcNumber" # #Option "FPScale"# [] #Option "FPTweak"# #Option "DualHead" # [] Identifier "Card0" Driver "nouveau" VendorName "nVidia Corporation" BoardName "C61 [GeForce 7025 / nForce 630a]" BusID "PCI:0:13:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" 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 EndSubSection EndSection ---End > Is there an explaination of the lockups (always only > in relation to Gtk+ triggering it)? Does it indicate > a defective driver or a defective hardware? What do > you think? > I once experienced such mysterious lockup since I started using FreeBSD 1 month ago. It left no traces which I could find. If I can recall correctly I was using Firefox that time and 2/3 Eterms were open. WM was Fluxbox. Regards, Gurpreet -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, 13 Aug 2011 23:15:52 -0500, Antonio Olivares wrote: > I just > # cd /ports/x11-drivers/xf86-drivers-nouveau/ > # make install clean > > # Xorg -configure > tested the screen, then ran > # cp /root/xorg.conf.net /etc/X11/xorg.conf > # sed -i "" 's|nv|nouveau|g' /etc/X11/xorg.conf > > restarted machine and I have nouveau working fine. Nothing more? I mean kernel modules & stuff? > I had a problem when playing a movie with mplayer, the movie did not > fill the entire screen when I typed 'f' or used -fs options. I > corrected this by adding to > ~/.mplayer/config > > zoom="YES" > > and it worked :) An important feature, thanks for the clue! > I was going to try and get the kernel sources to > successfully install nvidia, but why go through that hassle if it is > now working like I wanted it to work. Mayvbe you can check the 3D abilities with the commands I mentioned. Meanwhile, I was a brave man and launched Firefox. Three seconds later the system froze. Furthermore, I've lost my ~/.sylpheed/accountrc and folderlist.xml which I had to restore manually. Lost: Indications which messages I already had replied to. So again, Gtk+ triggers the system freeze, independent of the driver used. Now can I say that the GPU must be faulty? And just in case I have to replace it (PCIe required), what brand of GPU should I buy instead? Again nVidia, or better ATI, or Intel? It's a hard decision because I don't want to get from one trouble into the next one... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, Aug 13, 2011 at 11:01 PM, Polytropon wrote: > On Sat, 13 Aug 2011 22:12:26 -0500, Antonio Olivares wrote: >> I have nouveau working but for another card: >> >> vgapci0@pci0:1:0:0: class=0x03 card=0x82781043 chip=0x06e410de >> rev=0xa1 hdr=0x00 >> vendor = 'NVIDIA Corporation' >> device = 'NVIDIA GeForce 8400 GS (G98)' >> class = display >> subclass = VGA >> >> [olivares@quadcore ~]$ cat /var/log/Xorg.0.log | grep 'nouveau' >> (II) LoadModule: "nouveau" >> (II) Loading /usr/local/lib/xorg/modules/drivers/nouveau_drv.so >> (II) Module nouveau: vendor="X.Org Foundation" >> [drm] failed to load kernel module "nouveau" > > Do you still have the commands that successfully > brought you there? I just # cd /ports/x11-drivers/xf86-drivers-nouveau/ # make install clean # Xorg -configure tested the screen, then ran # cp /root/xorg.conf.net /etc/X11/xorg.conf # sed -i "" 's|nv|nouveau|g' /etc/X11/xorg.conf restarted machine and I have nouveau working fine. Sometimes screen flickers, but I consider that normal behavior, given that Fedora 14 & Fedora 15, porteus 64 bit also flicker and they have newer xorg packages and newer nouveau drivers too and it is no loss :( I can go back to nv, but nouveau is working fine :) I had a problem when playing a movie with mplayer, the movie did not fill the entire screen when I typed 'f' or used -fs options. I corrected this by adding to ~/.mplayer/config zoom="YES" and it worked :) I was going to try and get the kernel sources to successfully install nvidia, but why go through that hassle if it is now working like I wanted it to work. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, 13 Aug 2011 22:12:26 -0500, Antonio Olivares wrote: > I have nouveau working but for another card: > > vgapci0@pci0:1:0:0: class=0x03 card=0x82781043 chip=0x06e410de > rev=0xa1 hdr=0x00 > vendor = 'NVIDIA Corporation' > device = 'NVIDIA GeForce 8400 GS (G98)' > class = display > subclass = VGA > > [olivares@quadcore ~]$ cat /var/log/Xorg.0.log | grep 'nouveau' > (II) LoadModule: "nouveau" > (II) Loading /usr/local/lib/xorg/modules/drivers/nouveau_drv.so > (II) Module nouveau: vendor="X.Org Foundation" > [drm] failed to load kernel module "nouveau" Do you still have the commands that successfully brought you there? > > It complains about xorg-server must be >= 1.8, but > > only 1.7.7 is in latest ports (right now). This is > > step 4 on the list. Note that it's "./autogen.sh", > > not "./autogen" as in the article. > > This would explain it :( The xorg-server is at 1.7.7, I questioned > myself why xf86-driver-nouveau is from 2009 :(, and in Fedora it is > just old and these guys keep churning and churning new & updated > drivers :( What I don't understand is how a port that's more than one year old can require a X server version that's not reached yet _today_... :-) > The folks recommended me to get nvidia driver, but I get: > > quadcore# pwd > /usr/ports/x11/nvidia-driver > quadcore# make install clean > ===> Building for nvidia-driver-270.41.19 > ===> src (all) > "/usr/share/mk/bsd.kmod.mk", line 12: "can't find kernel source tree" > *** Error code 1 > > Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-270.41.19. > *** Error code 1 > > Stop in /usr/ports/x11/nvidia-driver. > *** Error code 1 > > Stop in /usr/ports/x11/nvidia-driver. Just tried, and it compiled quick and nice. It also seems to run very good, and 3D is also at a sufficient rate (see my other reply to the list). In your case - it seems that you don't have the kernel sources installed? Populate your /usr/src tree via CVS (csup) or from the installation media in case you're using a -RELEASE system. The subtree for the kernel is /usr/src/sys. > The folks recommend it to me because of some additional things, lower > CPU usage, better 3D stuff & other good things I'm looking forward to be able to play my (today "old fashioned") Linux and wine-powered 3D games. :-) Next thing will be dual screen. I have to try that in order to form an opinion if this is just silly nonsense or helpful for my individual productivity. > Some folks say that it is the recommended thing to do, is to install > nvidia drivers. As I have (hopefully correctly) understood from the documentation of the "nv" driver, this one is only for 2D. With the present incorporation of 3D stuff into "simple" desktop applications this might be worth considering. PS. Ctrl+Alt+Backspace now works. I'm always "impressed" how much work it takes to _transform_ functionality that one takes for granted with all the old software into their "modern" continuations... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, 13 Aug 2011 21:38:59 -0600 (MDT), Warren Block wrote: > On Sun, 14 Aug 2011, Polytropon wrote: > > > PS. Looking at your xorg.conf, maybe the reason why I > >can't do Ctrl+Alt+Backspace anymore is that DontZap > >belongs to ServerLayout, not to ServerFlags - I'll > >quickly check that. > > xorg.conf(5) says about ServerFlags: > >Options specified in this section (with the exception of the >"Default-ServerLayout" Option) may be overridden by Options specified >in the active ServerLayout section. > > In general, ServerFlags is unnecessary. Just put the options in > ServerLayout. Done that, but Ctrl+Alt+Backspace still doesn't work. > DontZap defaults to off now, but the key sequence has to be set, like > setxkbmap -option terminate:ctrl_alt_bksp > > or > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > Option "XkbOptions" "terminate:ctrl_alt_bksp" > EndSection I'll try on next X startup. Meanwhile, I got the "nvidia" driver compiled, installed and running. Tests like % xlock -nolock -mode lament or % xlock -nolock -mode fire show the FPS rate I've expected (no comparison to the 3 fps I got with "nv"). In "gears" there are > 5000 FPS, that's _magnitudes_ better than with "nv". But my text font in Sylpheed as well as the one used in intclock is not a bit damaged (just chose a different one in Sylpheed so I can see what I'm currently typing). The next thing I have to try is triggering the system freeze by using any Gtk+ application. :-) I'd like to point out that the nvidia driver comes with nice documentation: /usr/local/share/doc/NVIDIA_GLX-1.0/README contains lots of great stuff. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, 14 Aug 2011, Polytropon wrote: PS. Looking at your xorg.conf, maybe the reason why I can't do Ctrl+Alt+Backspace anymore is that DontZap belongs to ServerLayout, not to ServerFlags - I'll quickly check that. xorg.conf(5) says about ServerFlags: Options specified in this section (with the exception of the "Default-ServerLayout" Option) may be overridden by Options specified in the active ServerLayout section. In general, ServerFlags is unnecessary. Just put the options in ServerLayout. DontZap defaults to off now, but the key sequence has to be set, like setxkbmap -option terminate:ctrl_alt_bksp or Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, 14 Aug 2011 03:55:20 +0100, Frank Shute wrote: > On Sun, Aug 14, 2011 at 03:22:06AM +0200, Polytropon wrote: > > Has anyone got the "nouveau" driver working, and if, > > how precisely has he done so? > > Yes. I got it working once by following the package instructions but > on a subsequent system upgrade it stopped working and all my efforts > to get it working again have been unsuccessful. The instructions in the pkg-message seem to be incomplete (in comparison to what I read in the article. > > Is there an explaination of the lockups (always only > > in relation to Gtk+ triggering it)? Does it indicate > > a defective driver or a defective hardware? What do > > you think? > > It doesn't seem to make sense. Have you got something missing/added to > xorg.conf that's causing it? My xorg.conf looks quite like yours. I am not using HAL (compiled X without that). Monitor attached is a 21" CRT. The xorg.conf has been autogenerated and then trimmed. Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Mouse0""CorePointer" InputDevice "Keyboard0" "CoreKeyboard" # Option "SingleCard""true" EndSection Section "ServerFlags" Option "DontVTSwitch" "false" Option "DontZap" "false" Option "DontZoom" "false" # Option "Xinerama" "false" # Option "AIGLX" "true" EndSection Section "Files" ModulePath "/usr/local/lib/xorg/modules" FontPath"/usr/local/lib/X11/fonts/misc/" FontPath"/usr/local/lib/X11/fonts/TTF/" FontPath"/usr/local/lib/X11/fonts/OTF" FontPath"/usr/local/lib/X11/fonts/Type1/" FontPath"/usr/local/lib/X11/fonts/100dpi/" FontPath"/usr/local/lib/X11/fonts/75dpi/" FontPath"/usr/local/share/ghostscript/fonts/" # FontPath"/usr/local/share/fonts/amspsfont/type1/" # FontPath"/usr/local/share/fonts/cmpsfont/type1/" # FontPath"/usr/local/lib/X11/fonts/truetype/" EndSection Section "Module" Load"extmod" Load"record" Load"dbe" Load"glx" Load"dri" Load"dri2" Load"freetype" Load"type1" EndSection Section "DRI" Mode0666 EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "de" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device""/dev/sysmouse" Option "Emulate3Buttons" "true" Option "EmulateWheel" "true" Option "EmulateWheelButton""2" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Eizo" ModelName "FlexScan F980" HorizSync 30.0 - 137.0 VertRefresh 50.0 - 160.0 Option "DPMS" "false" Option "PreferredMode" "1152x864" EndSection Section "Device" Identifier "Card0" # Driver "nouveau" Driver "nv" VendorName "nVidia Corporation" BoardName "G73 [GeForce 7600 GS]" BusID "PCI:2:0:0" Screen 0 EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth24 Option "Accel" SubSection "Display" Viewport0 0 Depth 24 Visual "TrueColor" Modes "1400x1050" "1152x864" "1024x768" "800x600" "640x480" "320x240" EndSubSection EndSection > I don't have any ideas but I wish the nouveau driver port would get > some love and attention. I sould like that too - especially as the "nv" driver seems (at least according to the documentation) no 3D functionality which would be a real waste of money and power. Aligning it a bit more with the ports infrastructure to allow a "quite immediate" use would be nice. > Downloading and applying patches etc. should be automatic shouldn't > it? It seems rather "brittle" too. Installing git to get the other stuff (as described in the article) was a real horror to me. :-) But as I said: The symptom is _SPECIFIC_ (!!!) to the use of Gtk+ based programs. Everything else seems to be norm
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
> It complains about xorg-server must be >= 1.8, but > only 1.7.7 is in latest ports (right now). This is > step 4 on the list. Note that it's "./autogen.sh", > not "./autogen" as in the article. > > The steps explained are: > > 1. Uninstall any nvidia driver > # pkg_delete nvidia-driver-\* > # vi /boot/loader.conf # Remove the line 'nvidia_load="YES"' > > 2. Patch your kernel (Update your system if you are not running 8.0-CURRENT > or a recent 7.1-STABLE / 7.2-PRERELEASE): > # cd /usr/src/sys > # fetch http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch > # mkdir modules/drm/nouveau > # patch > drm-nouveau-032109.patch > # cd /usr/src && make kernel > # reboot > > 3. Install libdrm from git: > % git clone git://anongit.freedesktop.org/git/mesa/drm > % cd drm > % ./autogen --enable-nouveau-experimental-api > % gmake > % sudo gmake install > > 4. Install xf86-video-nouveau from git: > % git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau > % cd xf86-video-nouveau > % ./autogen > % gmake > % sudo gmake install > > 5. Update /usr/local/etc/X11/xorg.conf. > > As I said, I have problems doing so because of > > nouveau_dri2.c:374: warning: implicit declaration of function > 'DRI2BlockClient' > nouveau_dri2.c: In function 'nouveau_dri2_init': > nouveau_dri2.c:445: error: 'DRI2InfoRec' has no member named 'ScheduleSwap' > nouveau_dri2.c:446: error: 'DRI2InfoRec' has no member named 'ScheduleWaitMSC' > nouveau_dri2.c:447: error: 'DRI2InfoRec' has no member named 'GetMSC' > gmake[2]: *** [nouveau_dri2.lo] Error 1 > gmake[2]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau/src' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau' > gmake: *** [all] Error 2 > > and so on. > > > > So my questions are: > > Has anyone got the "nouveau" driver working, and if, > how precisely has he done so? I have nouveau working but for another card: vgapci0@pci0:1:0:0: class=0x03 card=0x82781043 chip=0x06e410de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'NVIDIA GeForce 8400 GS (G98)' class = display subclass = VGA [olivares@quadcore ~]$ cat /var/log/Xorg.0.log | grep 'nouveau' (II) LoadModule: "nouveau" (II) Loading /usr/local/lib/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" [drm] failed to load kernel module "nouveau" In mplayer's mailing list, some folks recommended me to get the nvidia driver directly, but I have run into trouble compiling the nvidia driver from ports. I need the source and I did not want to get into trouble :( > > Is there an explaination of the lockups (always only > in relation to Gtk+ triggering it)? Does it indicate > a defective driver or a defective hardware? What do > you think? > > I have _never_ encountered such kind of problems yet, > so I'm almost out of ideas. Sadly I can't check with > my (wonderfully working) ATI card because this one > is AGP, but the mainboard only has PCIe. > > Any ideas and instructions, as well as diagnosis-guessing > is very welcome. :-) > It complains about xorg-server must be >= 1.8, but > only 1.7.7 is in latest ports (right now). This is > step 4 on the list. Note that it's "./autogen.sh", > not "./autogen" as in the article. This would explain it :( The xorg-server is at 1.7.7, I questioned myself why xf86-driver-nouveau is from 2009 :(, and in Fedora it is just old and these guys keep churning and churning new & updated drivers :( The folks recommended me to get nvidia driver, but I get: quadcore# pwd /usr/ports/x11/nvidia-driver quadcore# make install clean ===> Building for nvidia-driver-270.41.19 ===> src (all) "/usr/share/mk/bsd.kmod.mk", line 12: "can't find kernel source tree" *** Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-270.41.19. *** Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** Error code 1 Stop in /usr/ports/x11/nvidia-driver. Maybe this would be the route to go in your case Polytropon? The folks recommend it to me because of some additional things, lower CPU usage, better 3D stuff & other good things http://freebsd.1045724.n5.nabble.com/Nvidia-driver-td4078051.html Some folks say that it is the recommended thing to do, is to install nvidia drivers. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sat, Aug 13, 2011 at 8:22 PM, Polytropon wrote: > Has anyone got the "nouveau" driver working, and if, > how precisely has he done so? > I used to have it working, but I think for various reasons it's being abandoned by FreeBSD x11 team. Not sure of exact current state but it's not worth pursuing. > > Is there an explaination of the lockups (always only > in relation to Gtk+ triggering it)? Does it indicate > a defective driver or a defective hardware? What do > you think? > Too soon to say. I always use the proprietary nvidia driver, and I've never had major issue from one installed from ports: /usr/ports/x11/nvidia-driver -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
On Sun, Aug 14, 2011 at 03:22:06AM +0200, Polytropon wrote: > > I'm using FreeBSD/amd64 on an Intel Core 2 4300 (1.8GHz) > on a VIA-equipped mainboard. The whole machine is a quite > cheap one from a discounter (mainly food). > > OS is 8.2-STABLE (July 2011). I have xorg-7.5.1 installed > with xorg-server-1.7.7_1,1, using xf86-video-nv-2.1.18 > configured in xorg.conf. The GPU I'm using is a nVidia > GeForce 7600 (G73) which is being supported by the "nv" > driver (as well as by "nouveau", see later on) according > to the documentation. My setup is about the same but with a GeForce 7300. I use nv without problems. > > When in X and _only_ in conjunction with programs using > the Gtk2 (Gtk+) toolkit, I encounter _total_ system > lockups (freezes): no disk activity, no console I/O, > nothing. It even happens during drawing operations. > A hard reset is required, which means power-cycling > as the cheap PC doesn't have a RESET button. A fsck > is required on next booting. > > I could trigger this problem with Sylpheed, Claws > Mail and Firefox. > > I am only able to do email because I downgraded > Sylpheed from 3.1.1_1 to 1.0.6_9 which does use > the classic Gtk (which I find more accessible > anyway). This old version that _works_ is about > to be removed from the ports tree!!! > > The machine has successfully been compiling the system, > X and OpenOffice, so I may assume that it's not > defective RAM or broken CPU. The hard disk is new. > > When the system does not lock up, frame rates for > 3D (tested with "glxgears" and xlock -mode fire") > is _very_ bad - much worse than on my old P4 with > ATI graphics. > > I read that the "nv" driver does not support 3D, so > I tried to install the "nouveau" driver. > > I did install xf86-video-nouveau-0.0.10.20090728_3 > from ports and replaced "nv" by "nouveau" in xorg.conf. > Result: > > (EE) [drm] drmOpen failed. > (EE) NOUVEAU(0): [drm] error opening the drm > Segmentation fault: 11 at address 0x0 > Fatal server error: > Caught signal 11 (Segmentation fault: 11). Server aborting > > There is no /dev/dri available. > > /usr/ports/x11-drivers/xf86-video-nouveau/pkg-message: > # cd /usr/src/sys > # fetch http://people.freebsd.org/~rnoland/drm-nouveau-062309.patch > # patch -sp0 -i drm-nouveau-062309.patch > # cd modules/drm > # make depend all install > > I've done this, installed & rebooted, same result. > > % startx > drmOpenDevice: node name is /dev/dri/card0 > Failed to change owner or group for file > /dev/dri! 2: No such file or directory > Failed to change owner or group for file > /dev/dri/card0! 2: No such file or directory > [drm] failed to load kernel module "nouveau" > > (EE) [drm] drmOpen failed. > (EE) NOUVEAU(0): [drm] error opening the drm > Segmentation fault: 11 at address 0x0 > Fatal server error: > Caught signal 11 (Segmentation fault: 11). Server aborting > > The kernel loggs the following messages: > > link_elf_obj: symbol DRM_MEM_TTM undefined > linker_load_file: Unsupported file type > > I tried some searching and found "We can haz Nouveau > on FreeBSD!" of March 2009. According to this instruction: > > http://romain.blogreen.org/blog/2009/03/we-can-haz-nouveau-on-freebsd/ > > It complains about xorg-server must be >= 1.8, but > only 1.7.7 is in latest ports (right now). This is > step 4 on the list. Note that it's "./autogen.sh", > not "./autogen" as in the article. > > The steps explained are: > > 1. Uninstall any nvidia driver > # pkg_delete nvidia-driver-\* > # vi /boot/loader.conf # Remove the line 'nvidia_load="YES"' > > 2. Patch your kernel (Update your system if you are not running 8.0-CURRENT > or a recent 7.1-STABLE / 7.2-PRERELEASE): > # cd /usr/src/sys > # fetch http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch > # mkdir modules/drm/nouveau > # patch > drm-nouveau-032109.patch > # cd /usr/src && make kernel > # reboot > > 3. Install libdrm from git: > % git clone git://anongit.freedesktop.org/git/mesa/drm > % cd drm > % ./autogen --enable-nouveau-experimental-api > % gmake > % sudo gmake install > > 4. Install xf86-video-nouveau from git: > % git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau > % cd xf86-video-nouveau > % ./autogen > % gmake > % sudo gmake install > > 5. Update /usr/local/etc/X11/xorg.conf. > > As I said, I have problems doing so because of > > nouveau_dri2.c:374: warning: implicit declaration of function > 'DRI2BlockClient' > nouveau_dri2.c: In function 'nouveau_dri2_init': > nouveau_dri2.c:445: error: 'DRI2InfoRec' has no member named 'ScheduleSwap' > nouveau_dri2.c:446: error: 'DRI2InfoRec' has no member named 'ScheduleWaitMSC' > nouveau_dri2.c:447: error: 'DRI2InfoRec' has no member named 'GetMSC' > gmake[2]: *** [nouveau_dri2.lo] Error 1 > gmake[2]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau/src' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau' > g
System lockups in X with nVidia GeForce 7600 GS (G73) and Gtk+
I'm using FreeBSD/amd64 on an Intel Core 2 4300 (1.8GHz) on a VIA-equipped mainboard. The whole machine is a quite cheap one from a discounter (mainly food). OS is 8.2-STABLE (July 2011). I have xorg-7.5.1 installed with xorg-server-1.7.7_1,1, using xf86-video-nv-2.1.18 configured in xorg.conf. The GPU I'm using is a nVidia GeForce 7600 (G73) which is being supported by the "nv" driver (as well as by "nouveau", see later on) according to the documentation. When in X and _only_ in conjunction with programs using the Gtk2 (Gtk+) toolkit, I encounter _total_ system lockups (freezes): no disk activity, no console I/O, nothing. It even happens during drawing operations. A hard reset is required, which means power-cycling as the cheap PC doesn't have a RESET button. A fsck is required on next booting. I could trigger this problem with Sylpheed, Claws Mail and Firefox. I am only able to do email because I downgraded Sylpheed from 3.1.1_1 to 1.0.6_9 which does use the classic Gtk (which I find more accessible anyway). This old version that _works_ is about to be removed from the ports tree!!! The machine has successfully been compiling the system, X and OpenOffice, so I may assume that it's not defective RAM or broken CPU. The hard disk is new. When the system does not lock up, frame rates for 3D (tested with "glxgears" and xlock -mode fire") is _very_ bad - much worse than on my old P4 with ATI graphics. I read that the "nv" driver does not support 3D, so I tried to install the "nouveau" driver. I did install xf86-video-nouveau-0.0.10.20090728_3 from ports and replaced "nv" by "nouveau" in xorg.conf. Result: (EE) [drm] drmOpen failed. (EE) NOUVEAU(0): [drm] error opening the drm Segmentation fault: 11 at address 0x0 Fatal server error: Caught signal 11 (Segmentation fault: 11). Server aborting There is no /dev/dri available. /usr/ports/x11-drivers/xf86-video-nouveau/pkg-message: # cd /usr/src/sys # fetch http://people.freebsd.org/~rnoland/drm-nouveau-062309.patch # patch -sp0 -i drm-nouveau-062309.patch # cd modules/drm # make depend all install I've done this, installed & rebooted, same result. % startx drmOpenDevice: node name is /dev/dri/card0 Failed to change owner or group for file /dev/dri! 2: No such file or directory Failed to change owner or group for file /dev/dri/card0! 2: No such file or directory [drm] failed to load kernel module "nouveau" (EE) [drm] drmOpen failed. (EE) NOUVEAU(0): [drm] error opening the drm Segmentation fault: 11 at address 0x0 Fatal server error: Caught signal 11 (Segmentation fault: 11). Server aborting The kernel loggs the following messages: link_elf_obj: symbol DRM_MEM_TTM undefined linker_load_file: Unsupported file type I tried some searching and found "We can haz Nouveau on FreeBSD!" of March 2009. According to this instruction: http://romain.blogreen.org/blog/2009/03/we-can-haz-nouveau-on-freebsd/ It complains about xorg-server must be >= 1.8, but only 1.7.7 is in latest ports (right now). This is step 4 on the list. Note that it's "./autogen.sh", not "./autogen" as in the article. The steps explained are: 1. Uninstall any nvidia driver # pkg_delete nvidia-driver-\* # vi /boot/loader.conf # Remove the line 'nvidia_load="YES"' 2. Patch your kernel (Update your system if you are not running 8.0-CURRENT or a recent 7.1-STABLE / 7.2-PRERELEASE): # cd /usr/src/sys # fetch http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch # mkdir modules/drm/nouveau # patch > drm-nouveau-032109.patch # cd /usr/src && make kernel # reboot 3. Install libdrm from git: % git clone git://anongit.freedesktop.org/git/mesa/drm % cd drm % ./autogen --enable-nouveau-experimental-api % gmake % sudo gmake install 4. Install xf86-video-nouveau from git: % git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau % cd xf86-video-nouveau % ./autogen % gmake % sudo gmake install 5. Update /usr/local/etc/X11/xorg.conf. As I said, I have problems doing so because of nouveau_dri2.c:374: warning: implicit declaration of function 'DRI2BlockClient' nouveau_dri2.c: In function 'nouveau_dri2_init': nouveau_dri2.c:445: error: 'DRI2InfoRec' has no member named 'ScheduleSwap' nouveau_dri2.c:446: error: 'DRI2InfoRec' has no member named 'ScheduleWaitMSC' nouveau_dri2.c:447: error: 'DRI2InfoRec' has no member named 'GetMSC' gmake[2]: *** [nouveau_dri2.lo] Error 1 gmake[2]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/src/sys/drm/xf86-video-nouveau' gmake: *** [all] Error 2 and so on. So my questions are: Has anyone got the "nouveau" driver working, and if, how precisely has he done so? Is there an explaination of the lockups (always only in relation to Gtk+ triggering it)? Does it indicate a defective driver or a defective hardware? What do you think? I have _never_ encountered such kind of problems yet, so I'm almost out of ideas. Sadly I can
