(II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "928圆96" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "896圆72" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "800圆00" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1600x1200" (hsync out of range) (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1280x1024" (hsync out of range) (II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1280x960" (hsync out of range) (II) intel(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1152x864" (hsync out of range) (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1024x768" (hsync out of range) (II) intel(0): Not using default mode "512x384i" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "1024x768i" (unknown reason)
(II) intel(0): Not using default mode "800圆00" (hsync out of range) (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "640x480" (hsync out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "720x400" (vrefresh out of range) (II) intel(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "640x400" (vrefresh out of range) (II) intel(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) intel(0): Not using default mode "640x350" (vrefresh out of range) (WW) intel(0): Unable to estimate virtual size (II) intel(0): : Using default vrefresh range of 50.00-70.00 Hz (II) intel(0): : Using default hsync range of 31.50-37.90 kHz (=) intel(0): Will alloc AGP framebuffer: 24576 kByte (II) intel(0): I810CheckAvailableMemory: 435196k available (II) intel(0): Kernel reported 108800 total, 1 used (-) intel(0): IO registers at addr 0xFF000000 (-) intel(0): Linear framebuffer at 0xF8000000 (II) intel(0): VESA VBE DDC transfer in appr. Last edited by sonoran 6th October 2010 at 08:03 PM.
#Samsung display monitor driver driver#
This doesn't seem to be working in your case, but there may be a clue there as to why not.Īfter that LoadModule: line, the driver should report back all the EDID info it reads from the monitor. Look for "LoadModule: "i2c"", which is where the X server will try to use the driver to get information directly from your monitor. You might want to look at /var/log/Xorg.0.log (or Xorg.1.log) to see what is going on. Get the recommended native resolution of the monitor from its docs, or google the monitor for that info, and put it in a file according to the nf man page. When the Xorg server isn't reading the monitor's specifications properly you can create an nf file.
To determine the number to use, see this page: One simple thing to try is adding "vga=xxx" to your kernel parameters in nf. What make and model graphics card are you using? Does its driver have any way to set the resolution?
0 kommentar(er)
