Re: Dualhead ATI Radeon VE
On Sun, Oct 21, 2001 at 05:28:17PM +0200, Michel D?nzer wrote:
On Sun, 2001-10-21 at 05:08, Edward C. Lang wrote:
So I make that change, and now I see:
Fatal Server error:
Requested Entity already in use!
I assume that's a driver issue, and not resolvable by simple configuration
file changes?
Is the 4.1.0 driver even supposed to support dualhead on these chips?
Maybe the current CVS driver does, you may want to ask on the
Xpert@XFree86.Org list.
Well... looking at the driver source[0], I see the following comment:
/* Xinerama has sync problem with DRI, disable it for now */
if(xf86IsEntityShared(pScrn-entityList[0]))
{
info-directRenderingEnabled = FALSE;
xf86DrvMsg(scrnIndex, X_WARNING,
Direct Rendering Disabled --
Dual-head configuration is not working with DRI
at present.\nPlease use only one Device/Screen
section in your XFConfig file.\n);
}
So maybe I'll try a kernel with no DRI support. But that's going to suck in
different ways.
Regards,
Edward.
[0]
http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
--
http://www.tsumakin.net/
Re: Dualhead ATI Radeon VE
Hi, On Sat, Oct 20, 2001 at 02:51:17PM +0200, Michel D?nzer wrote: Section ServerLayout Identifier Multihead X Screen CoffeScreen Screen CentreScreen LeftOf CoffeeScreen InputDevice Generic Keyboard InputDevice Configured Mouse Option Xinerama EndSection So I make that change, and now I see: Fatal Server error: Requested Entity already in use! I assume that's a driver issue, and not resolvable by simple configuration file changes? Regards, Edward. -- http://www.tsumakin.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dualhead ATI Radeon VE
Hi, I'm having some issues with attempting to get dualhead X working on this Radeon VE. The error in /var/log/XFree86.0.log is: (==) ServerLayout Multihead X (**) |--Screen CentreScreen (0) (**) | |--Monitor Sony (**) | |--Device Radeon_VE0 (EE) Screen CoffeeScreen doesn't exist: deleting placement (**) |--Input Device Generic Keyboard (I have my coffee mug in front of my Diamondtron, which is to the right of my keyboard and mouse.) I've attached my current /etc/X11/XF86Config-4 file - are there any obvious, or not so obvious, errors in it? Any help is appreciated. Regards, Edward. -- http://www.tsumakin.net/ # XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config manual page. # (Type man XF86Config at the shell prompt.) Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section ServerFlags EndSection Section Module Loadddc LoadGLcore Loaddbe Loaddri Loadextmod Loadglx Loadpex5 Loadrecord Loadxie Loadbitmap Loadfreetype Loadspeedo Loadtype1 Loadvbe Loadint10 EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ExplorerPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section Device Identifier Radeon_VE0 Driver radeon BusID PCI:1:5:0 Screen 0 EndSection Section Device Identifier Radeon_VE1 Driver radeon BusID PCI:1:5:0 Screen 1 EndSection Section Monitor Identifier Sony HorizSync 30-107 VertRefresh 50-85 Option DPMS EndSection Section Monitor Identifier Mitsubishi HorizSync 30-92 VertRefresh 50-85 Option DPMS EndSection Section Screen Identifier CentreScreen Device Radeon_VE0 Monitor Sony DefaultDepth24 SubSection Display Depth 16 Modes 1600x1200 1280x1024 1152x864 640x480 EndSubSection SubSection Display Depth 24 Modes 1600x1200 1280x1024 1152x864 640x480 EndSubSection EndSection Section Screen Identifier CoffeeScreen Device Radeon_VE1 Monitor Mitsubishi DefaultDepth24 SubSection Display Depth 16 Modes 1280x1024 1152x864 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1152x864 640x480 EndSubSection EndSection Section ServerLayout Identifier Multihead X Screen CentreScreen LeftOf CoffeeScreen InputDevice Generic Keyboard InputDevice Configured Mouse Option Xinerama EndSection Section DRI Mode0666 EndSection # end of XF86Config
Re: Dualhead ATI Radeon VE
Hi, On Sat, Oct 20, 2001 at 02:51:17PM +0200, Michel D?nzer wrote: Section ServerLayout Identifier Multihead X Screen CoffeScreen Screen CentreScreen LeftOf CoffeeScreen InputDevice Generic Keyboard InputDevice Configured Mouse Option Xinerama EndSection So I make that change, and now I see: Fatal Server error: Requested Entity already in use! I assume that's a driver issue, and not resolvable by simple configuration file changes? Regards, Edward. -- http://www.tsumakin.net/
check_symlinks_and_bomb ()
Hi, I'm having the follow errors with check_symlinks_and_bomb () in the postints: Preparing to replace xfree86-common 4.1.0-2pre3v2 (using .../xfree86-common_4.1.0-3_all.deb) ... /var/lib/dpkg/tmp.ci/preinst: 70: Syntax error: Bad for loop variable dpkg: error processing /var/cache/apt/archives/xfree86-common_4.1.0-3_all.deb (--unpack): subprocess pre-installation script returned error exit status 2 /var/lib/dpkg/tmp.ci/postrm: 70: Syntax error: Bad for loop variable dpkg: error while cleaning up: subprocess post-removal script returned error exit status 2 Fair enough, that can be fixed. But why is that being called in the first place? This is the output of check_and_bomb.sh, a quick cut'n'paste: % ./check_and_bomb.sh 2 foo check_symlinks_and_bomb \ /usr/bin/X11 \ /usr/include/X11 \ /usr/lib/X11 \ /usr/X11R6/lib/X11/rgb.txt + cat + check_symlinks_and_bomb /usr/bin/X11 /usr/include/X11 /usr/lib/X11 /usr/X11R6/lib/X11/rgb.txt + [ -n /usr/bin/X11 /usr/include/X11 /usr/lib/X11 /usr/X11R6/lib/X11/rgb.txt ] + [ -L /usr/bin/X11 ] + maplink /usr/bin/X11 + echo ../X11R6/bin + readlink /usr/bin/X11 + [ ../X11R6/bin != ../X11R6/bin ] + [ -L /usr/include/X11 ] + maplink /usr/include/X11 + echo ../X11R6/include/X11 + readlink /usr/include/X11 + [ ../X11R6/include/X11 != ../X11R6/include/X11 ] + [ -L /usr/lib/X11 ] + maplink /usr/lib/X11 + echo ../X11R6/lib/X11 + readlink /usr/lib/X11 + [ ../X11R6/lib/X11 != ../X11R6/lib/X11 ] + [ -L /usr/X11R6/lib/X11/rgb.txt ] + maplink /usr/X11R6/lib/X11/rgb.txt + echo /etc/X11/rgb.txt + readlink /usr/X11R6/lib/X11/rgb.txt + [ /etc/X11/rgb.txt != /etc/X11/rgb.txt ] So, what conditions are necessary to cause that function to even be called? Regards, Edward. -- Edward C. Lang: [EMAIL PROTECTED] | ___ ___ _ ___ | Programmer at the Centre for Bioinformation Science | / __| _ |_) __| | Telephone: +61 2 6125 4717 | | (__| _ \ \__ \ | Postal:JCSMR, GPO Box 334 Canberra ACT 2601 | \___|___/_|___/ |
