search for: doublescan

...fresh range of 56.00-65.00 Hz (WW) NOUVEAU(0): Unable to estimate virtual size (II) NOUVEAU(0): Clock range: 12.00 to 400.00 MHz (II) NOUVEAU(0): Not using default mode "640x350" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "640x400" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "720x400" (vrefresh out of range) (II) NOUVEAU(0): Not using defau...

...MHz, 37.9 kHz, 60.3 Hz (II) S3VIRGE(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D) (II) S3VIRGE(0): Modeline "800x600" 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) S3VIRGE(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) S3VIRGE(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) S3VIRGE(0): Default mode "700x525": 72.5 MHz, 76.5 kHz, 70.1 Hz (D) (II) S3VIRGE(0): M...

...44 [ 7.165] (II) modeset(0): 30323034333031390a20000000fd0032 [ 7.165] (II) modeset(0): 4c1e5311000a202020202020000000fc [ 7.165] (II) modeset(0): 0042656e5120474c323435300a2000e5 [ 7.165] (II) modeset(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan) [ 7.165] (II) modeset(0): Printing probed modes for output DVI-I-1 [ 7.165] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 7.165] (II) modeset(0): Modeline "1920x1080"x59.9 138.50 1920 196...

...0 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 336 (II) NVIDIA(0): HSyncEnd, HTotal : 368, 416 (II) NVIDIA(0): VRes, VSyncStart : 175, 191 (II) NVIDIA(0): VSyncEnd, VTotal : 192, 222 (II) NVIDIA(0): H/V Polarity : +/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x400": (II) NVIDIA(0): 640 x 400 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVID...

...0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) NOUVEAU(0): Modeline "1152x768 at 54"x54.8 65.00 1152 1178 1314 1472 768 771 777 806 +hsync +vsync (44.2 kHz) (II) NOUVEAU(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz) (II) NOUVEAU(0): Modeline "1024x768 at 85"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz) (II) NOUVEAU(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz) (II) NOUVEAU(0): Model...

> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks

...120.6 112.7 320x240 170.4 145.6 150.0 120.1 360x200 170.1 320x200 170.5 320x175 170.5 This is a flat panel, and I'm quite sure it cannot accept modes above 85Hz, maybe even lower. Furthermore, according to the log, there are lots of doublescan modes. When anything switches to 800x600 mode, X picks a doublescan mode, which won't work. If I manually do 'xrandr -s 800x600 -r 60' the mode is good. Additionally, the included X log contains a line like the following for every mode switch: (II) NOUVEAU(0): Modeline "(null)&qu...

...z (II) NOUVEAU(0): Estimated virtual size for aspect ratio 1.5758 is 1920x1200 (II) NOUVEAU(0): Clock range: 12.00 to 400.00 MHz (II) NOUVEAU(0): Not using default mode "640x350" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "640x400" (vrefresh out of range) (II) NOUVEAU(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "720x400" (vrefresh out of range) (II) NOUVEAU(0): Not using defau...

...amma correction (1.0, 1.0, 1.0) (II) NOUVEAU(0): Monitor0: Using hsync range of 30.00-92.00 kHz (II) NOUVEAU(0): Monitor0: Using vrefresh range of 50.00-180.00 Hz (II) NOUVEAU(0): Clock range: 12.00 to 400.00 MHz (II) NOUVEAU(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) NOUVEAU(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II)...

...771 781 798 -hsync +vsync (47.7 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "1024x768"x120.1 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) [ 2068.618] (II) modesetting(G0): Modeline "960x720"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hs...

http://bugs.freedesktop.org/show_bug.cgi?id=19214 Summary: video mode change causes monitor to go out of range 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

https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...e error states: (EE) VIA(0): No valid modes found. According to the detail output, VIA seems to get loaded ok, then funs through every possible video mode and fails with the following two lines repeated for each mode: (II) VIA(0): Not using default mode "320x240" (bad mode clock/interface/doublescan) (II) VIA(0): Not using default mode "320x240" (hsync out of range) according to the output, it successfully reads a DEL Model 7004, and gives a max h-image size of horz 31, vert 23 . (it's a 15" display). I'm not sure how to track this down. Any input is appreciated.

...ankus caused a merge conflict and problems with frame-packed and interlaced 3D modes, and I found a much saner model for how the timing parameters work while I was sorting that out. Observable behavior changes from this patch should be limited to better values for m->v.blankus on interlaced non-doublescan modes and non-interlaced doublescan modes, and some sort of effect on any mode with mode->vscan set (I don't know if this case actually happens, but if it did then I would expect it to have had some sort of problem in the previous implementation anyway). Of the entire series, this first patc...

I have had my "nv" driver lock up a number of times. I downloaded the "nvidia" drivers and they did not work at 1920x1080 resolution. I am looking for an updated driver for just "nv". I found some once for a different driver that you just update commonXXX and yourdriverXXX not the whole X recompile. Where can I find those drivers? THanks, Jerry --------------

...nly supports a 555 RGB Weight in 16 bpp, the hardware does not - do 565. You must put a Weight 555 in the Display section. - - o 24/32 bpp mode is not yet supported. - -1.2 Known Bugs - - o The driver should force Weight 555 in 16 bpp mode - - o The hardware cursor doesn't work if an doublescan mode is selected. - - o Screen blanking doesn't work, nor does DPMS. - - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NV1.sgml,v 3.3 1997/03/22 09:35:30 hohndel Exp $ - - -$XFree86$

...he overlay). Some further investigation showed that the video was not only misplaced in the y direction, but also very elongated. The problem was due to CurrentLayout.mode being undefined under randr12, to mode.Flags being some random number that occasionally lead the driver to think i was using a doublescan mode. This was recently fixed in git by malc0 using currentMode->Flags. However, malc0 noted in the changelog that this may also not be correct for randr12 (It works here, but I think it may in some setups not always point to the mode on the overlay crtc). Attached patch should fix this. Danny...

..._hdisplay, omode_vdisplay; if (connector->edid_blob_ptr) edid = (struct edid *)connector->edid_blob_ptr->data; @@ -1977,12 +1978,18 @@ nv50_head_atomic_check_view(struct nv50_head_atom *armh, mode = DRM_MODE_SCALE_FULLSCREEN; } + /* For the user-specified mode, we must ignore doublescan and + * the like, but honor frame packing. + */ + umode_vdisplay = umode->vdisplay; + if ((umode->flags & DRM_MODE_FLAG_3D_MASK) == DRM_MODE_FLAG_3D_FRAME_PACKING) + umode_vdisplay += umode->vtotal; asyh->view.iW = umode->hdisplay; - asyh->view.iH = umode->vdisplay; -...

Hi, Here I post these 2 misc patches. Best regards, Maxim Levitsky

...deset=1 as module parameter) gives me black screen. No, this time, i verified that fbcon was loaded. Also, DRM thee from http://cgit.freedesktop.org/~jinghua/drm/log/?h=modesetting-gem works fine in KMS mode with my current hardware (I need to correct screen resolution, X seems to be started in doublescan mode, but after this X works ok) Logs will follow .... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.