From owner-freebsd-x11@FreeBSD.ORG Mon Jul 7 11:07:09 2008 Return-Path: Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA2EC1065691 for ; Mon, 7 Jul 2008 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B5C878FC13 for ; Mon, 7 Jul 2008 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m67B79Yh062237 for ; Mon, 7 Jul 2008 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m67B79Mv062233 for freebsd-x11@FreeBSD.org; Mon, 7 Jul 2008 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Jul 2008 11:07:09 GMT Message-Id: <200807071107.m67B79Mv062233@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-x11@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 11:07:09 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/106370 x11 Screen corruption when using Direct Rendering on a PCI o ports/116359 x11 x11/xorg - screen blinks with PCI-E nvidia card and ve o ports/117195 x11 ix11/Xorg 7.3 dumps core at exit (sig 11) f ports/117508 x11 x11/xorg 7.2,7.3 i8i0 and intel crash system using Ble o ports/117766 x11 x11-servers/xorg-server (7.3) crashes under heavy load o ports/118950 x11 x11-drivers/xf86-video-nv - xorg xf86 nv (nvidia) driv o ports/119037 x11 x11: Can't type _ (Underscore) under X (gnome) f ports/119091 x11 x11-drivers/xf86-video-intel 2.1.1 panics system o ports/121360 x11 x11/xorg - Change default of ~/.xsession-errors to off o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/122924 x11 XCreateImage fails in most recent x11/XOrg o ports/124220 x11 [amd64] x11-servers/xorg-server - X.org server runs in o ports/124861 x11 Keyboard problems with xorg 13 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s ports/73743 x11 XOrg/XFree xauth add/startx problem o ports/93667 x11 x11/xorg-libraries: undefined symbol in libOSMesa.* is o ports/113106 x11 x11/xorg - Xorg 7.2 + Mach64 + dri produces error mess f ports/114827 x11 Xorg server crashes when starting astro/google-earth o ports/115020 x11 New port: graphics/osmesa - Mesa's off-screen renderin s ports/115536 x11 [new port] x11/xorg-base port for a minimal X.Org inst o ports/116443 x11 x11-drivers/xf86-input-keyboard patch for USB jp106 ke f ports/116603 x11 x11/xorg server 7.3 hangs up f ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) f ports/118217 x11 xorg doesnt find usb mouse when initiated with devd, w o ports/118547 x11 [patch] x11/xdm fails with pam_krb5 o ports/118645 x11 Xorg need realtime priority for mouse work nice o ports/121230 x11 [patch] ports/x11/xkeyboard-config WITHOUT_NLS support o ports/123137 x11 x11/libX11: missing ru_RU.UTF-8 locale 14 problems total. From owner-freebsd-x11@FreeBSD.ORG Mon Jul 7 18:32:05 2008 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5372E1065676 for ; Mon, 7 Jul 2008 18:32:05 +0000 (UTC) (envelope-from jochen@jochen-neumeister.de) Received: from dd6214.kasserver.com (dd6214.kasserver.com [85.13.131.7]) by mx1.freebsd.org (Postfix) with ESMTP id 78F5B8FC19 for ; Mon, 7 Jul 2008 18:32:04 +0000 (UTC) (envelope-from jochen@jochen-neumeister.de) Received: from donald.home.jochen-neumeister.de (dslb-088-078-235-148.pools.arcor-ip.net [88.78.235.148]) by dd6214.kasserver.com (Postfix) with ESMTP id 27146181D6C for ; Mon, 7 Jul 2008 20:21:01 +0200 (CEST) Message-ID: <48725F24.1080804@jochen-neumeister.de> Date: Mon, 07 Jul 2008 20:23:32 +0200 From: Jochen Neumeister User-Agent: Thunderbird 2.0.0.14 (X11/20080614) MIME-Version: 1.0 To: x11@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: xorg bug? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:32:05 -0000 Hi there, I'm not sure, that i found a bug in the new xorg. I updated my ports and read UPDATING. In my xorg.conf is the entry Driver "ati" I work in a lot of time with 2 TFT Monitors. One of this Monitor is the Virtual Desktop. The Virtual Desktop I started with an entry in my .xinitrc: xrandr --output VGA-0 --right-of DVI-0 After the xorg update the last days, my Virtual Desktop doesn't work. The problem is, the 2 Monitors are overlap, so that I see the same Desktop on both Monitors. I don`t see the virtuell Desktop. Here a my xrandr output: %xrandr Screen 0: minimum 320 x 200, current 3360 x 1050, maximum 3360 x 1050 VGA-0 connected 1680x1050+1680+0 (normal left inverted right x axis y axis) 473m m x 296mm 1680x1050 60.0*+ 1600x1000 59.9 1280x1024 75.0 59.9 1440x900 59.9 1280x960 59.9 1152x864 75.0 1152x720 60.0 1024x768 75.1 60.0 832x624 74.6 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DVI-0 connected 1680x1050+1680+0 (normal left inverted right x axis y axis) 473m m x 296mm 1680x1050 60.0*+ 1600x1000 59.9 1280x1024 75.0 59.9 1440x900 59.9 1280x960 59.9 1152x864 75.0 1152x720 60.0 1024x768 75.1 60.0 832x624 74.6 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 S-video disconnected (normal left inverted right x axis y axis) I have testing with this commands: xrandr --output DVI-0 --left-of VGA-0 xrandr --output DVI-0 --pos 0x0 but the same feature. Before I updated, xorg works with the 2 Monitors perfect. From owner-freebsd-x11@FreeBSD.ORG Sat Jul 12 13:35:43 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DE511065672 for ; Sat, 12 Jul 2008 13:35:43 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from v005705.home.net.pl (v005705.home.net.pl [212.85.118.117]) by mx1.freebsd.org (Postfix) with SMTP id 612638FC16 for ; Sat, 12 Jul 2008 13:35:42 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from 444.net.autocom.pl (HELO localhost) (zb.ispid@onet@77.236.6.157) by m022.home.net.pl with SMTP; Sat, 12 Jul 2008 13:08:57 -0000 Date: Sat, 12 Jul 2008 15:08:58 +0200 From: Zbigniew Baniewski To: freebsd-x11@freebsd.org Message-ID: <20080712130858.GA5296@sarge.my.own.domain.no-net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Subject: FreeBSD7/xorg/radeon: cannot change resolution using --<+/-> X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 13:35:43 -0000 Hallo, Since longer time I'm unable to make anything with this; perhaps somebody knows the cure: 1. It seems, that xorg totally ignores either entire `Section "Screen"' paragraph, or at least every single `SubSection "Display"' entry inside that paragaraph. In effect I'm unable to have desired resolution at desired bpp; when starting X-server, it always chooses it on its own. The second consequence is, that there's no possibility to switch resolutions using --<+ -> anymore. Below a copy of my xorg.conf. I'm using the same config under Linux (got dual-boot install) - with just slight differences (mouse, /dev/* etc. - you know; nothing screen-related) - without any problems. So, it must be a bug in FreeBSD's port of radeon driver, most probably. Does there exist any workaround? Or perhaps there's missing something FreeBSD specific? ========================================================================= # xorg.conf (Xorg X Window System server configuration file) # Transparency on Section "Extensions" Option "Composite" "Enable" EndSection Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/local/share/X11/rgb" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/webfonts/" FontPath "/usr/local/lib/X11/fonts/freefont-ttf/" FontPath "/usr/local/lib/X11/fonts/terminus-font/" FontPath "/usr/local/lib/X11/fonts/freefont/" FontPath "/usr/local/lib/X11/fonts/sharefont/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "GLcore" Load "bitmap" Load "dbe" Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "record" Load "type1" Load "vbe" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc101" Option "XkbLayout" "pl" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/sysmouse" Option "Protocol" "Auto" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Card0" Driver "radeon" VendorName "ATI" BoardName "ATI Radeon 9000 Pro" Option "AccelMethod" "XAA" Option "AGPMode" "1" Option "EnablePageFlip" "1" Option "ColorTiling" "1" BusID "PCI:1:0:0" Option "backingstore" "true" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Proview" ModelName "900 P" Option "DPMS" HorizSync 30.0 - 80.0 VertRefresh 60.0 - 85.0 EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 16 # SubSection "Display" # Viewport 0 0 # Depth 16 # Virtual 1280 1024 # EndSubSection SubSection "Display" Depth 1 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "800x600" "1024x768" "1280x1024" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "DRI" Group 0 Mode 0666 EndSection ==================================== 2. Yesterday I've replaced xorg radeon driver with the newest one, taken from ports (6.9.0), and the Xserver as well (1.4.2) - still no desired effect. 3. Since xorg has(?) ability to create kind of "template" of its config file, I've renamed my /etc/xorg.conf to /etc/xorg.conf.bak, then started X Window again, to see, what settings it'll write on its own. It didn't write anything, but... it started - for a first look - exactly, as if it had /etc/xorg.conf (although it didn't read it, as I saw in log file). I couldn't see any difference: same resolution, and same unability to change it using --. Perhaps although it was reading /etc/xorg.conf earlier - but my own settings were totally ignored? But why? Shouldn't they override any "autodetected values"? 4. No, I don't have any other xorg.conf file nowhere (made a search with "find / -name xorg*"). 5. As I've checked, I can change resolution using xrandr. But of course it's not any solution, it should be possible with --<+/->, like it's possible under every unix-like OS, with exception of FreeBSD. Looking for information, I could see, that I'm not only one, who's looking for solution: http://tinyurl.com/5p64jn - perhaps somebody found it meanwhile? If it's a bug - to whom should it be reported? -- pozdrawiam / regards Zbigniew Baniewski From owner-freebsd-x11@FreeBSD.ORG Sat Jul 12 14:39:38 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94D0A1065672 for ; Sat, 12 Jul 2008 14:39:38 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from v005705.home.net.pl (v005705.home.net.pl [212.85.118.117]) by mx1.freebsd.org (Postfix) with SMTP id 2F6C58FC14 for ; Sat, 12 Jul 2008 14:39:37 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from 444.net.autocom.pl (HELO localhost) (zb.ispid@onet@77.236.6.157) by m022.home.net.pl with SMTP; Sat, 12 Jul 2008 14:39:35 -0000 Date: Sat, 12 Jul 2008 16:39:36 +0200 From: Zbigniew Baniewski To: freebsd-x11@freebsd.org Message-ID: <20080712143936.GA5236@sarge.my.own.domain.no-net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Subject: FreeBSD7 & IceWM 1.2.35 - it doesn't read ~/.icewm/startup X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 14:39:38 -0000 And another problem: while starting IceWM, it doesn't seem to read anything from ~/.icewm/startup - although it said before: IceWM: using ~/.icewm for private configuration files (or something similar). Perhaps the support for ~/.icewm/startup has been removed - or it's a bug? Or maybe something has been changed meanwhile (different name for former "startup")? -- pozdrawiam / regards Zbigniew Baniewski From owner-freebsd-x11@FreeBSD.ORG Sat Jul 12 17:29:40 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA16F106566C for ; Sat, 12 Jul 2008 17:29:40 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from v005705.home.net.pl (v005705.home.net.pl [212.85.118.117]) by mx1.freebsd.org (Postfix) with SMTP id 383778FC16 for ; Sat, 12 Jul 2008 17:29:39 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from 444.net.autocom.pl (HELO localhost) (zb.ispid@onet@77.236.6.157) by m022.home.net.pl with SMTP; Sat, 12 Jul 2008 17:29:37 -0000 Date: Sat, 12 Jul 2008 19:29:38 +0200 From: Zbigniew Baniewski To: freebsd-x11@freebsd.org Message-ID: <20080712172938.GA5234@sarge.my.own.domain.no-net> References: <20080712143936.GA5236@sarge.my.own.domain.no-net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20080712143936.GA5236@sarge.my.own.domain.no-net> User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: FreeBSD7 & IceWM 1.2.35 - it doesn't read ~/.icewm/startup X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 17:29:41 -0000 On Sat, Jul 12, 2008 at 04:39:36PM +0200, Zbigniew Baniewski wrote: > And another problem: while starting IceWM, it doesn't seem to read anything > from ~/.icewm/startup OK, that one was rather simple: one just has to replace (in .xinitrc) a line containing: "exec icewm" with: "exec icewm-session". -- pozdrawiam / regards Zbigniew Baniewski From owner-freebsd-x11@FreeBSD.ORG Sat Jul 12 23:52:37 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA9E41065681 for ; Sat, 12 Jul 2008 23:52:37 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from v005705.home.net.pl (v005705.home.net.pl [212.85.118.117]) by mx1.freebsd.org (Postfix) with SMTP id 386178FC18 for ; Sat, 12 Jul 2008 23:52:36 +0000 (UTC) (envelope-from zb@ispid.com.pl) Received: from 444.net.autocom.pl (HELO localhost) (zb.ispid@onet@77.236.6.157) by m022.home.net.pl with SMTP; Sat, 12 Jul 2008 23:52:34 -0000 Date: Sun, 13 Jul 2008 01:52:36 +0200 From: Zbigniew Baniewski To: freebsd-x11@freebsd.org Message-ID: <20080712235235.GB5262@sarge.my.own.domain.no-net> References: <20080712130858.GA5296@sarge.my.own.domain.no-net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20080712130858.GA5296@sarge.my.own.domain.no-net> User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: FreeBSD7/xorg/radeon: cannot change resolution using --<+/-> X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 23:52:38 -0000 After a longer search I've found some clues in thread at: http://lists.freedesktop.org/archives/xorg/2008-March/034166.html #v+ > 1) What changed in 7.3 that caused this issue? The radeon driver got xrandr 1.2 support. Previous versions of the driver assumed one monitor per driver instance while with xrandr you may have several monitors. With xrandr it is much more important to get mode information about each monitor since you may have two or more monitors connected with vastly different capabilities. The previous version of the driver more or less always assumed a monitor was connected and forced whatever mode you specified. You can still do this, but as you see, the configuration has changed a bit. This page should give you a good overview: http://www.intellinuxgraphics.org/dualhead.html #v- In the effect, the configuration became difficult; f.e. one has to generate "Modelines" (instead of just write resolutions), there are problems with the real resolution "seen" by WM (if I force 800x600 - I've got very little and blurry letters), problems while trying to have virtual screen and so on. All this caused by assumption, that most users will have at least two (if not four) monitors connected to one video card. :/ -- pozdrawiam / regards Zbigniew Baniewski