Testing Beta 3 - Nvidia Display Driver Issue

Kbuild is on the verge of being available. The 2.6.29 kernel was released by the kernel developers as a stable kernel, and the packages has already been submitted to debian for approval and inclusion into the Sid package pool. Kbuild package for our RT kernel should be here soon... Watch the front page!

Today has been long and trying... The kernel and nVidia battle will have to wait until tomorrow. Cheers, Q

My hero. James

You could try what Dave Phillips did and install from source. It is a bit hacky at the moment with the headers that are not installable from synaptic, but doable. I will have a go at it tonight, and write up a little temporary tut to get everyone going during the testing phase.

Hi, I "think" I have tried them. I presume this involves an edit to the xorg.conf file. The samples I have used to edit it thus far have mostly been related to nvidia and/or nv drivers though. I know that Quentin has mentioned that he uses vesa drivers. I am willing to try again. Do I edit to the xorg.conf file? And, what is recommended? Thanks, James

did you try vesa drivers maybe?

Hi Dave, I have cut and pasted the basic nv xorg file into my system and still cannot get more than 800x620 resolution. I am using the Beta3 distro and really like it but the type is so big. I have an Nvidia 6150 embedded video card on my system. Thoughts? I think I have tried everything. Am I just stuck with this resolution on the beta3 for the time being? Thanks, James

Hi All, This is an xorg.conf used for 64studio 2.1 dist-upgraded to lenny. I have used grep to tweak the file, see the last 4 commented out lines. I have commented out links to unused fonts, the module "dri" because I'm using "glx" and unused mode lines in the Screen section. Composite is enabled. Most of the tweaks have been found by using grep $ grep "WW" /var/log/Xorg.0.log $ grep "EE" /var/log/Xorg.0.log $ grep "II" /var/log/Xorg.0.log Because the 2.1 lenny xorg.conf is different to the 3.0 beta xorg it will take time to create the best xorg.conf for the final released version of 3.0. It's best to change one thing at a time and always backup your backups it costs nothing and will save much grief later. Its always better to type carefully when editing xorg.conf and make sure the commented out parts have the comment in the right place. You could remove the lines instead of commenting them out. xorg.conf 2.1 lenny: Happy Hacking ;-) Cheers! Dave.

Hi, You can't install "nvidia" binary drivers without installing the kernel headers and you can't install the kernel headers without linux-kbuild-2.6.29 which doesn't exist yet. ("beta Testing"). If you're a video editor the "nvidia" binary driver will be important and this is an example of what "Testing is not for everyone" means. If you're editing audio take the time to benchmark your audio software when using the "nv" driver before you install "nvidia". You may find the "nvidia" driver will have quite an negative effect on your audio performance. Here's an xorg.conf (basic) for using the "nv" driver. Click on "Download as Text" and save the contents as a file. Back up your original xorg.conf before you edit yours. Here's the basic xorg.conf "nvidia" used after the binary driver is installed. Cheers! Dave.

@ madforthenet You should check a bit on internet about the new versions of xorg. Then you would find easily that these new versions let your /etc/X11/xorg.conf almost empty. Everything works? So there is no problem. Just add the nvidia driver in the device section when it will be possible to use it. @ SEO Honolulu You can try the .run if you want. But usually it solves the problem on short time but makes problems much later. Maybe you'll be lucky, i hope for you.

Don't know if you guys have seen this, but maybe this might help... http://meandubuntu.wordpress.com/2008/07/17/install-nvidia-17713-drivers-on-realtime-kernel/ .................................................... 1. Download the drivers (http://www.nvidia.com/object/linux_display_amd64_177.13.html) 2. Reboot into “recovery mode”, or use CTRL-ALT-F1 to drop to a terminal and kill X. 3. Run the driver script with the “-x” (extract-only) option: sudo sh NVIDIA-Linux-x86_64-177.13-pkg2.run -x (This is for the amd64 drivers, so make appropriate changes if needed, of course.) 4. Make the replacements mentioned in the nvidia linux forums post in nano: sudo nano usr/src/nc/nv-linux.h (You can use CTRL-\ for search and replace in nano.) Replace “__SEMAPHORE_INITIALIZER” with “__COMPAT_SEMAPHORE_INITIALIZER” Replace “struct semaphore” with “struct compat_semaphore” 5. Run the installer: sudo ./nvidia-installer .................................................... a possibility?

WHile I'm reading this post Is's rising a dout in my mind : My xorg.conf is right ? This is : # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "it" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" EndSection There si nothing about driver or video card , but I have the right resolution for my display 1280x1024 and I don't have any malfunfintion. If I try to reconfigure xserver from console It don't change anything . It's a positive or negative signal ? Please tell me if I do something to reconfigure xserver Bte

Hi, The first method is to edit & configure xorg.conf yourself. See 1/3rd down the thread. 64 Studio 3.0 alpha ISO (post) xorg & nv driver The second method I haven't tried yet. See the first post. 64studio 3.0 observations Alex wrote: (First Post) I used Envy to install the opensource NV driver for graphics, and it all just works. (26" monitor.) Cheers! Dave

Wow, I haven't checked back on this thread in a bit.. looks like it was busy huh :p Quick question about the nv driver... I got a fresh install of beta 3 as you know... so exactly what am I pulling down from synaptic to get the nv driver in place? When I look at my xorg.conf, it's not even listing any kind of driver.. think it said something to the effect of "selected device" for both my monitor and vid card. Suggestions?

Hi skullnotions I appreciate your answer , but I'm a neewbie in Computer Audio Music so I'm not a really tester like you and other members. I just come to explore this world and I want to do by Linux cause the very expensive cost of windows programs and also cause I'm a Linux User since Debian 3 and first release of Ubuntu then I want to continue explore this world expecially in audio to start learn how to recording instrument and also to "compose" and play computer music not necessary electronic. Bye

Hi madforthenet, I have been experimenting with "nv" & "nvidia" for quite a while now. The binary "nvidia" driver can really mess with audio performance, sometimes an older driver will work much better with audio than the newest one. Even though my nvidia card works with a new driver I have found downloading and using an older version is the best for me. You have to try different drivers until you find the best one for your system. Take the time to make notes using "nv" first and then compare the results when you install "nvidia". This testing time where "nvidia" can't be installed is a great opportunity to test your audio in depth. I don't think I'll be installing "nvidia" on my working studio. "nv" does all I need. Cheers! Dave.

Hi skullnotions please be patience with me really mean that " The "nvidia" driver will influence your Audio performance, only by running the "nv" driver will you know by how much" bye

Hi tb, It will be worth the wait if it insures that we don't have big issues with the final release. Sure is a great distro and you are a valued member of this awesome community ;-) I too am looking forward to installing the 3.0 final. In the meantime I'm looking forward to reading your posts\reports with the testing versions. As soon as the final is released, I will be preparing to test for the next release. I love testing, and love to see users satisfied with the version they use. Peace Dave ;-)

My bad with the language. I'll try to keep it in check in the future. Thanks everyone for responding. I know that beta testing requires lots of patience. This is a great product and worth the wait for sure. I just was hoping someone out there would have a guess for how long we're going to have to wait. It would be really helpful if we knew whether we're talking days vs months. Anyway, I'll be checking back daily until this problem is resolved. peace tb

QH the sensor has struck again... You are welcome to drop me a mail if you see something that might have the exact same meaning, slightly edited ;-) This is a forum for everyone. Please keep it clean and to the point, and remember that children have open access to 64 Studio like the rest of us. There will be an announcement on the front page when kbuild is sorted out... This will be newsworthy enough! Cheers, Quentin

Hi, This testing time where "nvidia" can't be installed is a great opportunity to test your audio in depth. Testing takes patience and as I've said many times on the forum "Testing is not for everyone". The "nvidia" driver will influence your Audio performance, only by running the "nv" driver will you know by how much. Getting the 64studio base and kernel stable are vital to future releases. It doesn't matter how long it takes. It will be worth the wait. Happy Testing :-) Cheers! Dave.

Hi SEO Honolulu I have an Asus 8600 GT silent on my pc and with 64studio 3 alpha 3 I use nv driver without many problem . In effect to use 3D acceleration you must have nvidia driver , but it' not possible with kernel 2.6.29-1-multimedia-686 , it's possible to compile and use original nvidia driver up to 2.6.26-1-multimedia-686 If 3D acceleratio is necessary fot you maybe you could instal the stable version 2.1 We all aspect with patience the availability of kbuild packet for headers for actual kernel to compile nvidia driver. bye

I am also currently stuck using the "nv" driver. Not too bad for me, but not running at the peak of my card's performance. We unfortunately have no control over it. Patience grasshopper...

Does anyone know how long we should expect to wait for this? It's really ***** bad ****** for everyone. I'm a noob so I'm not sure what to expect. It's already been a couple of weeks though so I'm starting to worry that we're going to be in this situation for a while. skullnotions/quentin Do you have any guesses on how long we're going to have to wait? thanks tb

Hi, Until we get kbuild-2.6.29 built use the "nv" driver. You need kbuild-2.6.29 to install the kernel headers. Cheers! Dave.

oh man, that formatted all wrong.. if you go to the link I mentioned, it lays out those steps in a readable format...