Hello everbody, I recently unmasked Xorg 7.1 and upgraded my Xorg 7.0 to it. Compiling went fine but running at first not... I then found out that Xorg 7.1 needs a new Option called ReducedBlanking in the xorg.conf in order to enable Reduced Blanking (otherwise the modeline is declared invalid). Please look below for more infos in the comments! Xorg 7.0 didn't need that option. Quite a lot TFT's are using Reduced Blanking and I think maybe an einfo should be added to the xorg-server-1.1.0 ebuild that this Option is now (probably, can someone verify this? thx!) needed for Reduced Blanking, that should hopely save some users some trouble... Here is the CVS patch that introduced this behaviour to Xorg-7.1: http://lists.freedesktop.org/archives/xorg-commit/2005-December/006085.html What do you think? Thanks, Steffen Here are some infos: from my xorg.conf: Section "Monitor" Identifier "Monitor0" UseModes "Modes0" ModelName "Display" # This is the new Option that is needed under Section "Monitor": Option "ReducedBlanking" HorizSync 74 VertRefresh 60 EndSection Section "Modes" Identifier "Modes0" # Generated by Xorgautoconfig, it worked with Xorg 7.0 but Xorg 7.1 needs the ReducedBlanking Option above because otherwise it says something like "Monitor does not support Reduced Blanking => Modeline invalid! in the Xorg0.log and the screen gets No Signal... # D: 154.012 MHz, H: 74.044 kHz, V: 59.955 Hz Modeline "1920x1200" 154.012 1920 1968 2000 2080 1200 1203 1209 1235 -HSync +VSync EndSection x11-base/xorg-server-1.1.0 USE="dri nptl xorg -debug -dmx -ipv6 -kdrive -minimal -sdl -xprint" INPUT_DEVICES="keyboard mouse -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -evdev -fpit -hyperpen -jamstudio -joystick -magellan -magictouch -microtouch -mutouch -palmax -penmount -spaceorb -summa -tek4957 -ur98 -void" VIDEO_CARDS="radeon -apm -ark -chips -cirrus -cyrix -dummy -epson -fbdev -glint -i128 -i740 -i810 -imstt -mach64 -mga -neomagic -newport -nsc -nv -r128 -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb -tdfx -tga -trident -tseng -v4l -vesa -vga -via -voodoo" Portage 2.1_rc4 (default-linux/ppc/ppc32/2006.0/G4, gcc-4.1.1, glibc-2.4-r3, 2.6.16-gentoo-r9-macmini ppc) ================================================================= System uname: 2.6.16-gentoo-r9-macmini ppc 7447A, altivec supported Gentoo Base System version 1.12.0 ccache version 2.4 [enabled] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r1 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r4 ACCEPT_KEYWORDS="ppc ~ppc" AUTOCLEAN="yes" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -mtune=G4 -mcpu=G4 -maltivec -mabi=altivec -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/devel/env /usr/kde/devel/share/config /usr/kde/devel/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -mtune=G4 -mcpu=G4 -maltivec -mabi=altivec -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://pandemonium.tiscali.de/pub/gentoo" LANG="de_DE.UTF-8" LINGUAS="de en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/kde-live /usr/local/overlays/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="ppc X aac alsa altivec apache2 apm bash-completion bitmap-fonts bluetooth bonobo bzip2 cairo cdparanoia cdr cli crypt cups dri dv dvb dvd dvdr dvdread encode exif fam fastcgi fbcon ffmpeg flac foomaticdb ftp gif glitz gpm gs gtk2 gtkhtml idn ieee1394 imap isdnlog jabber jack javascript jpeg kde kdeenablefinal libg++ libwww mad matroska motif mp3 mpeg mysql ncurses nls nptl ogg opengl pam pcre pdf pdflib perl php png pppd python qt readline reflection ruby session skey sockets socks5 spell spl ssl svg tcpd theora threads tidy tiff truetype truetype-fonts type1-fonts udev unicode usb vcd vorbis wifi xcomposite xine xml xorg xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_de linguas_en userland_GNU video_cards_radeon" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I've already mentioned in e-mail that I think this warning is a good idea. Donnie, do you agree? I don't remember the reasoning (if there was any) to turn off reduced blanking by default.
(In reply to comment #1) > I've already mentioned in e-mail that I think this warning is a good idea. > Donnie, do you agree? > > I don't remember the reasoning (if there was any) to turn off reduced blanking > by default. > Maybe this helps: :) http://lists.freedesktop.org/archives/xorg/2005-December/011874.html Steffen
Probably because having less than 25% blanking generally isn't a good idea. Why do you need a modeline for your mode?
Hi and thanks for your reply! (In reply to comment #3) > Probably because having less than 25% blanking generally isn't a good idea. > > Why do you need a modeline for your mode? > Why is less that 25% blanking not a good idea? Can my current Modeline even damage something? *fear* How much blanking do I have? This comment from the Xorg list clears things up: "Currently, the mode validation code doesn't really check blanking, and thus happily accepted modes with narrow blanking. The "treeside" patch on the bugzilla adds the check for 25% (horizontal) blanking and refuses lower when no reducing blanking is used and the blanking isn't exactly 160 clocks. And then only accepts it when the ReducedBlanking option is set." Ok so this means that I'm currently using narrow blanking. The newest Xorgautoconfig generated this Modeline, I didn't change it (I only chaged some other stuff...). Is it ok to remove the HSync and VSync Options from the Modeline? Are they used with DVI? So that it looks like this: # D: 154.012 MHz, H: 74.044 kHz, V: 59.955 Hz Modeline "1920x1200" 154.012 1920 1968 2000 2080 1200 1203 1209 1235 And what would be a correct 1920x1200 CVT Reduced Blanking Modeline? The Datasheet of my Monitor says for 1920x1200 (but for Analog In, there was no DVI Chart, the Handbook says that that should happen automatically): Mode Dot Clock Sync Polarity Frequencies MHz H V H kHz V Hz VESA CVT 193.3 Nega. Posi. 74.56 59.89 1920
Hi and thanks for your reply! (In reply to comment #3) > Probably because having less than 25% blanking generally isn't a good idea. > > Why do you need a modeline for your mode? > Why is less that 25% blanking not a good idea? Can my current Modeline even damage something? *fear* How much blanking do I have? This comment from the Xorg list clears things up: "Currently, the mode validation code doesn't really check blanking, and thus happily accepted modes with narrow blanking. The "treeside" patch on the bugzilla adds the check for 25% (horizontal) blanking and refuses lower when no reducing blanking is used and the blanking isn't exactly 160 clocks. And then only accepts it when the ReducedBlanking option is set." Ok so this means that I'm currently using narrow blanking. The newest Xorgautoconfig generated this Modeline, I didn't change it (I only chaged some other stuff...). Is it ok to remove the HSync and VSync Options from the Modeline? Are they used with DVI? So that it looks like this: # D: 154.012 MHz, H: 74.044 kHz, V: 59.955 Hz Modeline "1920x1200" 154.012 1920 1968 2000 2080 1200 1203 1209 1235 And what would be a correct 1920x1200 CVT Reduced Blanking Modeline? The Datasheet of my Monitor says for 1920x1200 (but for Analog In, there was no DVI Chart, the Handbook says that that should happen automatically): Mode Dot Clock Sync Polarity Frequencies MHz H V H kHz V Hz VESA CVT 193.3 Nega. Posi. 74.56 59.89 1920 × 1200 @ 60 Hz VESA CVT RB (Reduced Blanking) 154.0 Posi. Nega. 74.04 59.96 1920 × 1200 @ 60 Hz The last Line looks a lot like the one from Xorgautoconfig, so whats wrong with it? And maybe this is important, I currently have UseFBDev "true", the Monitor then gets 1920x1200, 74 60 and is perfectly happy, but if I change UseFBDev to "false" the Monitor shows a Picture that is streched/distorted like if someone pushed the Picture with his Hands from the right and left side a bit to the middle. The Vertical part is ok, the Horizontal one is streched... The Monitor then gets: Signal 960x1200 Fh 73.5khz Fv 59.5hz Lower Resolutions work with UseFBDev false, so maybe this has to do something with reduced blanking! What do you think? Thanks for you help, Steffen
(In reply to comment #4) > Why is less that 25% blanking not a good idea? > Can my current Modeline even damage something? *fear* > How much blanking do I have? Reduced blanking could potentially damage a CRT monitor, but nobody seems to be sure. They require the option to ensure that CRT monitors won't be damaged. It's really only useful to turn it on for high-resolution LCDs. I'd recommend using the 'cvt' tool to generate a modeline, if you find that it's necessary and the Hsync/Vsync lines aren't enough. In general, you should try to just specify Hsync and Vsync rather than specifying a modeline.
Thanks for you reply, (In reply to comment #5) > (In reply to comment #4) > > Why is less that 25% blanking not a good idea? > > Can my current Modeline even damage something? *fear* > > How much blanking do I have? > > Reduced blanking could potentially damage a CRT monitor, but nobody seems to be > sure. They require the option to ensure that CRT monitors won't be damaged. > It's really only useful to turn it on for high-resolution LCDs. > > I'd recommend using the 'cvt' tool to generate a modeline, if you find that > it's necessary and the Hsync/Vsync lines aren't enough. > > In general, you should try to just specify Hsync and Vsync rather than > specifying a modeline. > so should then the Xorgautoconfig tool from JoseJX be changed? I just tried the cvt tool: cvt -v 1920 1200 # 1920x1200 59.88 Hz (CVT 2.30MA) hsync: 74.56 kHz; pclk: 193.25 MHz Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync We can clearly see that the pclk is too hight for a single link DVI-I cable... Thus I tried Reduced Blanking: cvt -v -r 1920 1200 # 1920x1200 59.95 Hz (CVT 2.30MA-R) hsync: 74.04 kHz; pclk: 154.00 MHz Modeline "1920x1200R" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync This looks almost exactly like my old Modeline from Xorgautoconfig (and the Handbook (see my other post)): # D: 154.012 MHz, H: 74.044 kHz, V: 59.955 Hz Modeline "1920x1200" 154.012 1920 1968 2000 2080 1200 1203 1209 1235 -HSync +VSync I don't think the minimal differences (74.044khz vs. 74.04 khz etc. should make any differences (right?), so what's wrong? Only the HSync and VSync Polarity are different, what do these do? Are they used with DVI? Should I change them? I will now try with DDC and EDID on, and just specifying 60hz and 74khz... What about the UseFBDev Problem, is this related to Reduced Blanking? Thanks, Steffen
Created attachment 88404 [details] Xorg.0.log section with DDC Ok, I just tried it without the Modeline and Option "DDCMode" "true" Xorg didn't start... Please have look at my attachement! Ok, so Xorg gets no DDC Data... Why? :) And of course the default Modes from Xorg aren't the right ones (WideScreen Display!)... I also tried the old Modeline without HSync and VSync Polarity, it works without any problems thus I think I don't specify them explicitly. Is this ok? Thanks for your help, I know that I'm posting a lot... *sorry* Steffen
And last but not least: I also tried the CVT RB Generated Modeline. Without Option ReducedBlanking the Mode is declared Invalid (Monitor doesn't support Reduced Blanking...) and with Option ReducedBlanking the Monitor doesn't sync and Xorg freezes up, I could not kill it, only the power button helped... This also happens whith the Xorgautoconfig Modeline if I don't specify ReducedBlanking... :( Steffen
Same problem on my machine after upgrade to 7.1 using a Dell 2405, 24''. Option "ReducedBlanking" solved it for me too. If I could, I would vote for an 'einfo'. Took me a while to get everything in place again.
Alright, I added a warning to xorg-server-1.1*.
