search for: addmode

http://bugs.freedesktop.org/show_bug.cgi?id=19854 Summary: xscreensaver fails to run (regression) Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

...ed (normal left inverted right x axis y axis) DVI-D-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) I've tried a solution that has been suggested to add output to an external monitor, but it failed as shown: # xrandr --addmode HDMI-1 1920x1080 # xrandr --output HDMI-1 --mode 1920x1080 --left-of LVDS-1 xrandr: Configure crtc 1 failed I would be very thankful to get help here that can solve this confusing problem. Terje

...failed: I used gtf to calculate a 2560x1440_60 mode line Modeline "2560x1440_60.00" 311.83 2560 2744 3024 3488 1440 1441 1444 1490 -HSync +Vsync and I then used commands xrandr --newmode 2560x1440 311.83 2560 2744 3024 3488 1440 1441 1444 1490 -HSync +Vsync xrandr --addmode DP-1 2560x1440 xrandr --output DP-1 --mode 2560x1440 The result is that windows on the screen seem to increase in size slightly and flow off the screen. The system tray normally at the bottom of the screen has disappeared. More precisely, command xrandr -q reports: Screen 0: minimum 320...

Hi All, I've recently acquired a nvs280 card, which is a nv34 gpu based card with a pci-e bridge on the card, this way I can test nv3x problems without needing an agp motherboard. One thing which stands out with this card is that it drivers my dvi lcd monitor at 1680x1050 instead of its native 1920x1080. Is this due to a known limitation on the display pipeline of these cards / nv34 gpu-s.

...too low */ I assume it means the dotclock, or pixel clock (6.000 MHz) is too low for the GPU? The thing is, on X i can use xrandr to set the same mode (or with the same clock, or any clock i tried): xrandr --newmode "320x240" 6 320 328 360 400 240 243 247 253 +HSync -VSync xrandr --addmode DVI-I-1 320x240 xrandr --output DVI-I-1 --mode 320x240 Also, the kernel parameter "video=DVI-I-1:320x240M" applies the mode, but it doesn't get added. I would be grateful to know: What is the actual minimum dotclock supported by the video card? Is it defined somewhere in the drive...

...0x1440_60 mode line > > Modeline "2560x1440_60.00" 311.83 2560 2744 3024 3488 1440 1441 1444 > 1490 -HSync +Vsync > > and I then used commands > > xrandr --newmode 2560x1440 311.83 2560 2744 3024 3488 1440 1441 1444 > 1490 -HSync +Vsync > xrandr --addmode DP-1 2560x1440 > xrandr --output DP-1 --mode 2560x1440 > > The result is that windows on the screen seem to increase in size slightly > and flow off the screen. The system tray normally at the bottom of the > screen has disappeared. More precisely, command xrandr -q reports: >...

...s y axis) > DVI-D-1 disconnected (normal left inverted right x axis y axis) > HDMI-1 disconnected (normal left inverted right x axis y axis) > > > I've tried a solution that has been suggested to add output to an external > monitor, but it failed as shown: > > # xrandr --addmode HDMI-1 1920x1080 > # xrandr --output HDMI-1 --mode 1920x1080 --left-of LVDS-1 > xrandr: Configure crtc 1 failed > > > I would be very thankful to get help here that can solve this confusing > problem. > > Terje > > _______________________________________________ > N...

https://bugs.freedesktop.org/show_bug.cgi?id=52398 Bug #: 52398 Summary: nouveau: DPMS permanently turns off display when starting X.org, text console works fine Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity:

https://bugs.freedesktop.org/show_bug.cgi?id=49397 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aplattner at nvidia.com |nouveau at lists.freedesktop.o | |rg

http://bugs.freedesktop.org/show_bug.cgi?id=15949 Summary: LVDS-0 has wrapped screen with Randr1.2 Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...put from "xrandr -q" and "monitor-get-edid -v | monitor-parse-edid -v" mismatch. The latter shows that the suggested resolution is indeed 1280x1024 (60.0Hz). If I do: xrandr --newmode "1280x1024 at 60" 108 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync xrandr --addmode VGA-1 1280x1024 at 60 and then I change the monitor settings from X, I can use that resolution indeed. I'm going to attach the output of xrandr -q and monitor-*-edid. Other information about my card (POST trace, BIOS dump) can be found attached to bug #68835. -- You are receiving this mail...

https://bugs.freedesktop.org/show_bug.cgi?id=76732 Priority: medium Bug ID: 76732 Assignee: nouveau at lists.freedesktop.org Summary: Kworker using 100% CPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: patrick.clara at gmail.com

https://bugs.freedesktop.org/show_bug.cgi?id=40747 Summary: The new nouveau kernel module fails to use my monitor's native resolution Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: