[Xpert]Xinerama + OEM Radeom = Hard to Worky
Hy0, I accidently deleted your address, so this email is mainly directed at you. I just wanted to say I got everything working -- but it wasn't my crooked installation of X that was giving problems. After a clean install of X (the current CVS, 4.2.99.2) I was still having the same problem -- my dual head was working, but inexplicably my virtual screen size was being set to ungodly large values (1960x??? for one monitor, and 1600x1200 for the other). As you deduced, these values seem to be coming from the maximum resolution that X thought my monitors could handle -- based on the Sync values in my config file. And the solution of artificially lowering these values helped, we got 1152x768 when aiming for 1024x768 -- much more usable disparity. However, this apparantly odd behavior, of setting virtual to max capabilities instead of max requested resolution, seems to be present in this current CVS version. The 'fix' that worked best was found after re-reading the manual for the config file -- the 'virtual' directive for the screen setting manually sets the virtual screen size (wow, it was that simple! :) ). Also, Hy0, the second monitor is working fine using the current CVS driver! I have not powered off. In fact, since a recent reboot (but after trying your driver), the console is double displayed, whereas the second display used to be dead. The key to this was, at the least, leaving the monitor on during bootup. In anycase, your driver may have set something up that is still working. If you would like me to powerdown, I can, but my power switch involves a nail and screwdriver strategically place into my motherboard -- so you can imagine I don't enjoy doing that :) . I'm attaching my X config file that I am currently using to get a working 1024x768 (double wide) dual headed system. Also, I am including a log of when I was getting 1152x768 (virtual) even though my screen section was the same, except for the virtual line. (The monitor sections' Sync values were also lowered, otherwise it would be 1960x??? for one monitor and 1600x1200 for the other). -G ### BEGIN DEBCONF SECTION # 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-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/: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 "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" # Option "XkbLayout" "us" Option "XkbLayout" "dvorak" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" # Identifier "ATI Technologies, Inc. Radeon 7500 [RV200 QW]" Identifier "analog port" Driver "ati" BusID "PCI:1:0:0" Screen 0 Option "SWCursor" EndSection Section "Device" # Identifier "ATI Technologies, Inc. Radeon 7500 [RV200 QW]" Identifier "digital port" Driver "ati" BusID "PCI:1:0:0"
Re: [Xpert]Xinerama + Radeon = No error + No Worky
Just for the record, combining the current CVS, with an experimental driver, got things working, almost. So, it is possible to do dual head with -this- oem card, one more experienced than me could answer if that meant -all- oem cards. -Adam On Fri, Nov 01, 2002 at 11:01:40PM -0800, hy0 wrote: > The problem is caused by one of your monitor not being detected. If both of > your monitors were connected during boot time (if not, try it), this is > probably another instance of the monitor detection problem with some OEM > cards (the card id reported by your log file indicates you have an OEM > card). This problem started to surface recently with more and more OEM cards > hitting market. If this is the case for you, the latest CVS code won't help > too much except it'll print out a warning message. There is no workaround > and we have to rewrite the monitor detection code for these cards. I'm > planning to do this shortly but I don't have any OEM card on my hand at the > moment. If you're willing to test, I'll send you the driver when it's ready. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]change input device on the fly?
Not an expert, but have you tried to specify both devices at the same time? You may still have to restart X, but you wouldn't have to edit anything. Hope that helps a little, Adam On Thu, Nov 07, 2002 at 11:44:38AM -0500, [EMAIL PROTECTED] wrote: > Is it possible to change an input device "on the fly", or after X has > started? I have a laptop with a built-in ps2 mouse, but I also have a > USB optical mouse that I like to use. Currently, I have to shutdown X, > edit the XF86Config, then restart to use the other mouse. Is there a > better way to do this? > > Thanks in advance. > john - [EMAIL PROTECTED] > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]256 megs board fails Validation,
Well you answered my question.
Isn't three going to be the only non-two factor? (Which in my previous
email, hadn't thought possible -- I thought 24bpp was treated as 32bpp).
Anyway the better way (if still doing factoring) is to use a loop like
this:
x = mode->HDisplay
y = mode->VDisplay
z = scrp->videoRam
while ( (! (x * y & 0x01)) &&
(! (z & 0x01)) ) {
if (x & 0x01) {
y <<= 1;
} else {
x <<= 1;
}
z <<= 1;
}
if ( x*y > z )
return MODE_MEM;
// p.s. I left out the 1024, 8 and scrp->fbFormat.bitsPerPixel parts
// sorry
Anyway I would use the above only if still paranoid that a 64bit
number wouldn't work. And 64bit math by hand is not hard if it
doesn't have to be fast -- so that seems to be the best approach.
-Gryn (Adam Luter)
On Tue, Nov 05, 2002 at 03:06:09AM +0100, Alexander Stohr wrote:
> Adam Luter [mailto:luterac@;bellsouth.net] wrote:
>
> > Why not use math?
> >
> > factor = 1024 * 8 / scrp->fbFormat.bitsPerPixel;
> > if (mode->HDisplay * mode->VDisplay > scrp->videoRam * factor)
> > return MODE_MEM;
> >
> > This assumes that scrp->fbFormat.bitsPerPixel is a power of two.
> >
> > Also, really huge monochrome displays are still vunerable. In
> > other words, I would also use a 64bit number.
> >
> > -Gryn
>
> concerning your formula, I am applying
> a 24 bpp wide packed pixel format:
>
> 1024*8/24 = 341.333
>
> This case might lead to unwanted fractional loss.
> Using a special case handling for 24 bpp and similar
> would mean that any bit depth could go that way anyways.
> But then I do see no need for an "optimized" path at all.
>
> Your version further does not care about
> that HDisp and VDisp might multiply to
> a value bigger than 2 GB and therfore getting
> negatvie if input values were choosen evil minded.
>
> I considered such a division approach myself,
> but in the end this is only save if you
> can ensure limited ranges for all numbers.
>
> But we should not build up further limits
> since there were already two suggestions
> that do not need that at all
>
> One thing to discuss is the likeliness for
> 64 bit math support versus the support for
> integer division on the target platform.
>
> -Alex.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]256 megs board fails Validation,
Why not use math? factor = 1024 * 8 / scrp->fbFormat.bitsPerPixel; if (mode->HDisplay * mode->VDisplay > scrp->videoRam * factor) return MODE_MEM; This assumes that scrp->fbFormat.bitsPerPixel is a power of two. Also, really huge monochrome displays are still vunerable. In other words, I would also use a 64bit number. -Gryn On Tue, Nov 05, 2002 at 01:09:14AM +0100, Alexander Stohr wrote: > Hmm, looks like a limitation of the inital coders knowledge. > Nothing to worry about in an OpenSource project where lots > of coding youngsters did take part in. > > The below coding: > > if (mode->HDisplay * mode->VDisplay * scrp->fbFormat.bitsPerPixel > > scrp->videoRam * (1024 * 8)) > return MODE_MEM; ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xinerama + Radeon = No error + No Worky
Normally I wouldn't mind compiling, but I think it's understandable for X if I'm a little trepidious :) . However, I am anxious enough to do so this weekend or the next, if there aren't any other less adventourus suggestions! :) Thank you for the advice -- I'm sorry that I didn't find that earlier thread on my own. -Gryn (Adam) On Fri, Nov 01, 2002 at 04:50:37PM +0100, Michel Dänzer wrote: > On Fre, 2002-11-01 at 16:02, Adam Luter wrote: > > On Thu, Oct 31, 2002 at 03:22:27PM -0600, Adam Luter wrote: > > > Attached are my XF86Config-4 and XFree86.0.log files. I believe I > > > have correctly setup my XF86Config-4 file, however my second monitor > > > does not receive any signal.> > > > > This time I promise not to forget to attach the files! Sorry :) > > Your config looks fine to me, and the log looks similar to the one > someone else posted recently, i.e. everything looks fine except the > driver doesn't mention the second head at all. As I said in that other > thread after looking at the source, the driver seems to ignore the > second head under some circumstances I don't understand; maybe Hui Yu or > Kevin E. Martin would. There's also a good chance for this to work > better in current CVS. > > > -- > Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xinerama + Radeon = No error + No Worky
On Thu, Oct 31, 2002 at 03:22:27PM -0600, Adam Luter wrote: > Attached are my XF86Config-4 and XFree86.0.log files. I believe I > have correctly setup my XF86Config-4 file, however my second monitor > does not receive any signal.> This time I promise not to forget to attach the files! Sorry :) -Gryn (Adam) ### BEGIN DEBCONF SECTION # 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-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/: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 "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" # Option "XkbLayout" "us" Option "XkbLayout" "dvorak" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" # Identifier "ATI Technologies, Inc. Radeon 7500 [RV200 QW]" Identifier "analog port" Driver "ati" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" # Identifier "ATI Technologies, Inc. Radeon 7500 [RV200 QW]" Identifier "digital port" Driver "ati" BusID "PCI:1:0:0" Screen 1 Option "DigitalScreen" "true" EndSection Section "Monitor" Identifier "CTX:1705" HorizSync 30-95 VertRefresh 50-160 Option "DPMS" EndSection Section "Monitor" Identifier "MIT:17HX" HorizSync 30-82 VertRefresh 50-130 Option "DPMS" EndSection Section "Screen" Identifier "Left Screen" # Device "ATI Technologies, Inc. Radeon 7500 [RV200 QW]" Device "analog port" Monitor "CTX:1705" DefaultDepth24 SubSection "Display" Depth 24 # Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" Modes "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Right Scree
[Xpert]Xinerama + Radeon = No error + No Worky
Attached are my XF86Config-4 and XFree86.0.log files. I believe I have correctly setup my XF86Config-4 file, however my second monitor does not receive any signal. I have tried disabling various modules, I have tried swapping monitors and also I have tried various options (such as the DigitalScreen option that is enabled in the version I am sending). But no matter what I do, it seems like everything is ok, except for the part where X would actually start talking to the second head and set it up. However, there are no directly related error messages about why not :( . The newbie list had directed me here, so I thought I would try you all out. I've been trying various settings for the past month with no avail -- does anyone see what I'm doing wrong? Specs: X 4.2.1 Debian unstable/sid (pre-release X packages) CTX 17", Mitsubishi 17" (CRT/analog monitors) ATI Radeon 7500 AGP card, with a digital->analog adaptor for the second head. I appreciate any and all help, thanks very much :) . -Gryn (Adam Luter) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XFree86 and LCd
My experience with LCD monitor's (especially 17" or greater) is with the analog they have trouble keeping up. If you can decrease your overall speed you will probably decrease the "flickering". Which I think he means is a continous "fuzz" around sharp contrasts. (My two cents) -Gryn (Adam Luter) On Thu, Oct 31, 2002 at 01:00:53PM -0800, Mark Vojkovich wrote: > On Wed, 30 Oct 2002, Yongming Wei wrote: > > > My LCD is philips 150S3f. > > > > accurately, the flickering is not serious, although > > characters can be seen a little messed up, I can still > > recognize them. > > > > Now I want inscreasing DotClock to see if it is > > because the DotClock is too low. > >Flickering is generally because the refresh is too low. If > you increase the dot clock you will increase the refresh. > According to the PDF for this monitor at Philips web site > 1024x786@75Hz IS a supported mode. So it doesn't sound > like there was anything wrong with the original mode you > were using. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
