Hi everyone, My name is Pascal Schoenhardt. I am working on a SOC project to add XRandR 1.2 support to GNOME, and I use a laptop with an Nvidia card. Therefore, I also use Nouveau. First of all, great work guys. I am extremely excited about this project, and I'm amazed by the progress you are making with such a difficult task. I am posting this message to report my success with the nouveau driver (GIT version from the 12'th of May), and to ask for support on one thing. So, here we go: Driver compiled just fine, and everything worked on the first try. The "Start X and run for cover" was not required! glxgears runs at approx. 350 fps; this is according to the console output, however the animation looks very jumpy... According to the wiki, this is the only 3D application that runs, however I am also able to use every one of the GL screensavers included in Gnome (2.20, I believe - running Feisty). They run like slideshows, but they render perfectly! Nice work. The only other GL app I've tried is Google Earth, which resulted in X crashing, but I know that advanced apps aren't meant to work yet anyways. Now for the problems: My laptop is an Asus Z71v, which has a 1680x1050 LCD panel. While I am running Feisty Fawn, which has x.org 7.2 by default, I have upgraded this to 7.3 from Burtoni's repo's, which were create with the intent of testing display hotplugging. When I first started up nouveau, I only had 1024x768. xrandr reported that screen 0 had a minimum of 640x480, a max of 1024x768, and was connected at 1024x768. My output was labeled "default" (not LVDS) and was connected at 1024x768. Trying to change the screen size with the --fb option was not successful. A bit of Googling lead me to adding: Virtual 1680 1050 to the Screen -> Display subsection in my xorg.conf. This increased the screen size to 1680x1050, however my LCD was still at 1024x768, allowing me to pan around. The strange thing was that the "default" output was registering itself to be running at 1680x1050. It seems nouveau tried changing my LCD to its native res, and thought it succeeded, when it really didn't. At this point, I could use the --fb command to lower the resolution, but not increase it. Also, changing the resolution like that caused X to crash sometimes, and some other GNOME related issues other times (nautilus crashing). My next step was to try some modelines. After 4 attempts, I found this one to work: ModeLine "1680x1050" 144.02 1680 1784 1968 2256 1050 1051 1054 1064 Now I have full resolution. The output of running 'xrandr' right now is: Screen 0: minimum 640 x 480, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 60.0* 1024x768 60.0 800x600 60.0 56.0 640x480 60.0 1280x1024 60.0 1440x900 60.0 1280x960 60.0 1280x800 60.0 1280x768 60.0 1152x768 55.0 Now, here is the real issue: My laptop has a VGA port and an svideo port. To start working on smooth multi-head support for gnome, I obviously need use of at least the VGA port. As it stands, nouveau does not detect any of these outputs. As I understand it, xrandr should be reporting something like this: Screen 0: minimum 640 x 480, current 1680 x 1050, maximum 1680 x 1050 LVDS connected 1680x1050+0+0 0mm x 0mm VGA not connected SVideo not connected ... Plugging in a monitor in the VGA port does nothing at all. I did notice that there are some other heads in the GIT repository for xrandr1.2. Do I maybe need to get a special version of nouveau? Has the randr stuff been merged into the main driver yet? If I need a special version, I would be forever grateful if someone could just post the exact git command I need to run to get what I need. :) So, I appologize for the length of this report. I hope it provides one of you developers with something useful! Cheers, Pascal
Hi Pascal, On Tue, May 15, 2007 at 11:23:50AM +0100, Pascal Schoenhardt wrote:> Now, here is the real issue: My laptop has a VGA port and an svideo > port. To start working on smooth multi-head support for gnome, I > obviously need use of at least the VGA port. As it stands, nouveau > does not detect any of these outputs. As I understand it, xrandr > should be reporting something like this:Have you tried "xrandr --auto"? It's usually required to run this command before xrandr picks up on a VGA port connection, because usually (at least, on Intel) we don't get an interrupt when a monitor is plugged in. Which brings me to a question: do we get one on nVidia? Could nouveau be able to kick off xrandr as soon as a monitor's connected? (I don't know how well Xrandr actually works on nouveau, I'm afraid.) - Chris. -- Chris Ball <cjb at laptop.org>
On Tue, 15 May 2007 11:23:50 +0100 "Pascal Schoenhardt" <stoanhart at gmail.com> wrote:> the nouveau driver (GIT version from the 12'th of May) > > Driver compiled just fine, and everything worked on the first try. The > "Start X and run for cover" was not required! glxgears runs at approx. > 350 fps; this is according to the console output, however the > animation looks very jumpy... According to the wiki, this is the only > 3D application that runs, however I am also able to use every one of > the GL screensavers included in Gnome (2.20, I believe - running > Feisty). They run like slideshows, but they render perfectly! Nice > work. The only other GL app I've tried is Google Earth, which resulted > in X crashing, but I know that advanced apps aren't meant to work yet > anyways.Yes, Mesa software rendering is nice, isn't it? ;-) I suppose you did not install Mesa from git, did you? Might be worth to check glxinfo, if you really got DRI called properly. That glxgears behaviour sounds like software rendering to me.> Now for the problems: My laptop is an Asus Z71v, which has a 1680x1050 > LCD panel. While I am running Feisty Fawn, which has x.org 7.2 by > default, I have upgraded this to 7.3 from Burtoni's repo's, which were > create with the intent of testing display hotplugging....> Now, here is the real issue: My laptop has a VGA port and an svideo > port. To start working on smooth multi-head support for gnome, I > obviously need use of at least the VGA port. As it stands, nouveau > does not detect any of these outputs. As I understand it, xrandr...> Plugging in a monitor in the VGA port does nothing at all. I did > notice that there are some other heads in the GIT repository for > xrandr1.2. Do I maybe need to get a special version of nouveau? Has > the randr stuff been merged into the main driver yet? If I need a > special version, I would be forever grateful if someone could just > post the exact git command I need to run to get what I need. :)I am not sure what the current state of Nouveau randr-1.2 is, but the following is my impression. randr-1.2 stuff is not in the master branch, but in the randr-1.2 branch only. This requires xorg-server 1.3, like master branch now does. I have the same kind of nv28 card as Airlied who works on the Nouveau randr-1.2. The last I tried I got, with one analog and one DFP, something different on both heads, but not really usable (at least DFP screen was geometrically screwed, and colors too). Some how it managed to make my mouse all weird, too, swapping and inversing x and y coordinates or something. AFAIK, trouble with basic mode setting for multiple heads. Since then, I see one or two batches of commits from Airlied to randr-1.2 branch, so things may have changed. I still do not believe randr-1.2 features are yet at a usable state. -- Pekka "PQ" Paalanen http://www.iki.fi/pq/
Apparently Analagous Threads
- SVIDEO and xrandr
- [Bug 14403] New: NV17: LVDS0 is black with Randr 1.2, works when randr 1. 2 is disabled
- [Bug 14703] New: On NV17 on laptop screen: certain resolutions are scrambled
- xrandr: Failed to get size of gamma for output default
- Re: wine don't handle hard coded resolutions & refresh rates