Re: xorg-commit messages
On Sun, Dec 28, 2008 at 12:38:40PM -0800, Jeremy Huddleston wrote: > On Dec 28, 2008, at 04:45, Daniel Stone wrote: >> On Sun, Dec 28, 2008 at 12:41:24AM -0800, Jeremy Huddleston wrote: >>> It looks like the automated messages to xorg-commit aren't getting >>> generated... is someone on that? >> >> Um, works for me: >>> Date: Sun, 28 Dec 2008 03:15:26 -0800 (PST) >>> [...] >> >> Anything in particular you're missing? > > Yeah, that's the first one I received in about 2 days. I thought I > pushed a commit yesterday, and it wasn't there... but it turns out I > committed it to "(no branch)" instead of "master" somehow... so false > alarm and it's there now... See, we're not _always_ just being shit with the lists. ;) Cheers, Daniel signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: input settings get ignored?
On Sun, Dec 28, 2008 at 09:45:12AM +, Magnus Kessler wrote: > On Sunday 28 December 2008, Bernd Steinhauser wrote: > > I was upgrading to xorg-server 1.6 Beta3 (1.5.99.3) and I have one nasty > > problem, which I'm not sure if it is me doing something wrong or if > > there is a bug. > [snip] > > In addition to that, some keys don't work or are working wrong, for > > example, when using the standard layout, the ↑ key acts as a print key. > > I guess that has something to do with the model or the rules. > > The up-arrow behaving like the print key is usually caused by using a pc10x > keyboard model with the evdev driver. actually, to be precise this is caused by any keyboard model other than evdev if the ruleset is 'base'. 'base' pulls in the xfree86 keycodes which screw the whole thing up. The evdev ruleset (part of xkeyboard-config 1.4 and later) pulls in the evdev keycodes, regardless of the model. "setxkbmap -rules evdev -model pc104 -layout us" is valid now. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: screen resolution to be fixed in gnome
Am Sun, 28 Dec 2008 12:39:36 -0500 schrieb Alex Deucher: > On Sun, Dec 28, 2008 at 11:16 AM, Bernhard Kleine wrote: >> Hallo, my first post to this list. >> >> I am using debian sid with actual, i.e. latest packages. After some >> tuning I could bring the xserver-xorg to start gnome display manager >> and its welcome screen at the desired, highest resolution 1920 x 1200 >> px. However, after logging in it takes a few seconds and than the >> resolution shifts to 1280 x 800, something I never added to any >> configuration file. >> >> I am using gnome. Do you happen to know where -- aside from xorg.conf >> -- screen resolution is to be saved or controlled? >> >> Any help appreciated. >> >> > Some versions of gnome save display related settings and switch to them > when you log in. Youhave to remove the saved gnome settings. See this > post for more info: > http://ubuntuforums.org/showthread.php?t=529791 > > Alex The link was the correct tipp. I had to delete in gnome's configuration editor all keys related to desktop->gnome->screen and after that the 1920x1200 are there. Thanks for the tip! Bernhard ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: screen resolution to be fixed in gnome
Am Sun, 28 Dec 2008 12:39:36 -0500 schrieb Alex Deucher: > On Sun, Dec 28, 2008 at 11:16 AM, Bernhard Kleine wrote: >> Hallo, my first post to this list. >> >> I am using debian sid with actual, i.e. latest packages. After some >> tuning I could bring the xserver-xorg to start gnome display manager >> and its welcome screen at the desired, highest resolution 1920 x 1200 >> px. However, after logging in it takes a few seconds and than the >> resolution shifts to 1280 x 800, something I never added to any >> configuration file. >> >> I am using gnome. Do you happen to know where -- aside from xorg.conf >> -- screen resolution is to be saved or controlled? >> >> Any help appreciated. >> >> > Some versions of gnome save display related settings and switch to them > when you log in. Youhave to remove the saved gnome settings. See this > post for more info: > http://ubuntuforums.org/showthread.php?t=529791 > > Alex The link was the correct tipp. I had to delete in gnome's configuration editor all keys related to desktop->gnome->screen and after that the 1920x1200 are there. Thanks for the tip! Bernhard ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xorg-commit messages
On Dec 28, 2008, at 04:45, Daniel Stone wrote: > On Sun, Dec 28, 2008 at 12:41:24AM -0800, Jeremy Huddleston wrote: >> It looks like the automated messages to xorg-commit aren't getting >> generated... is someone on that? > > Um, works for me: >> Date: Sun, 28 Dec 2008 03:15:26 -0800 (PST) >> [...] > > Anything in particular you're missing? Yeah, that's the first one I received in about 2 days. I thought I pushed a commit yesterday, and it wasn't there... but it turns out I committed it to "(no branch)" instead of "master" somehow... so false alarm and it's there now... ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: screen resolution to be fixed in gnome
On Sun, 2008-12-28 at 16:16 +, Bernhard Kleine wrote: > I am using debian sid with actual, i.e. latest packages. After some > tuning I could bring the xserver-xorg to start gnome display manager > and > its welcome screen at the desired, highest resolution 1920 x 1200 px. > However, after logging in it takes a few seconds and than the > resolution > shifts to 1280 x 800, something I never added to any configuration > file. > > I am using gnome. Do you happen to know where -- aside from xorg.conf > -- > screen resolution is to be saved or controlled? Hi, GNOME uses RandR to set the users preferred resolution on login. You should be able to change it by using gnome-display-properties, or failing that, xrandr. HTH, -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: screen resolution to be fixed in gnome
On Sun, Dec 28, 2008 at 11:16 AM, Bernhard Kleine wrote: > Hallo, my first post to this list. > > I am using debian sid with actual, i.e. latest packages. After some > tuning I could bring the xserver-xorg to start gnome display manager and > its welcome screen at the desired, highest resolution 1920 x 1200 px. > However, after logging in it takes a few seconds and than the resolution > shifts to 1280 x 800, something I never added to any configuration file. > > I am using gnome. Do you happen to know where -- aside from xorg.conf -- > screen resolution is to be saved or controlled? > > Any help appreciated. > Some versions of gnome save display related settings and switch to them when you log in. Youhave to remove the saved gnome settings. See this post for more info: http://ubuntuforums.org/showthread.php?t=529791 Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
On Sun, Dec 28, 2008 at 7:43 AM, Tomasz Chmielewski wrote:
> I have a radeon 9600 card, with two devices connected:
>
> - DVI: LCD monitor, capable of 1280x1024 (preferred mode)
> - VGA: LCD projector, capable of 1024x768, (800x600 preferred mode)
>
> Both devices show the same output ("clone" - of course, if the
> resolution is 1280x1024, VGA/LCD projector does not show any output, as
> this device does not support this mode).
>
> The problem is - whenever the LCD projector is powered on as computer
> boots, X starts in 800x600 resolution.
> What's worse - it's not possible to change the resolution to 1280x1024;
> xrandr will only switch the resolution up to 1024x768 (maximum supported
> by the VGA monitor).
There are two types of clone modes, one where one crtc drives two
outputs with the same timing (what you are seeing), and one where each
output is drive by a separate crtc. xrandr is not always smart enough
to do the right thing when you request different timing on two
different outputs if they are currently both being drive by the same
crtc. the following command should do what you want:
xrandr --output DVI-0 --crtc 1 --mode 1280x1024
>
>
> Is it possible to force the resolution on a device, even if it doesn't
> support it?
yes. that's what the "PreferredMode" option is for. See this page
for more on randr 1.2 xorg.conf options:
http://wiki.debian.org/XStrikeForce/HowToRandR12
Something like this should do the trick:
Section "Monitor"
Identifier "DVI-0"
DisplaySize 304 228
Modeline "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025
1028 1060 -HSync +Vsync
Option "PreferredMode" "1280x1024_60.00"
EndSection
You can also add a similar section for VGA-0.
Alex
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
gma950 + latest x11 + latest intel driver
Hi, I'm testing latest x11 from git (gentoo's x11 overlay) and latest intel driver from git (videocard: gma950). Here's some results: 0. xf86-video-intel-2.5.1 + xorg-server-1.5.3 + mesa-7.2 + kernel 2.6.28: 3D is not usable, ~3-5 fps in quake3. 2D is stable and fast 1. Latest x11 stack from git + latest xf86-video-intel from git + kernel 2.6.28 + exa (no dri2): 3D is not usable, ~5-10 fps in quake3. 2D is stable and fast 2. Latest x11 stack from git + latest xf86-video-intel from git + kernel 2.6.28 + uxa (with dri2): 3D is fast, but very unstable. I've got several X lockups: nothing interesting in Xorg.0.log or in dmesg, image freezed, system is not responding on keyboard\mouse (but sysrq works), but it's possible to login over ssh, and it's impossible to kill X :) There's also some artefacts in 2D with UXA, here's screenshots with comments: http://fenix-fen.at.tut.by/screen-3.png http://fenix-fen.at.tut.by/screen-4.png So, UXA+DRI2 is not suitable for everyday usage at the moment... Is there any way to get good 3D performance with 2.6.28 kernel and without UXA/DRI2? Regards Vasily signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
Tomasz Chmielewski schrieb: >>> I even added: >>> >>> Option "PanelSize" "1280x1024" >>> >>> but it doesn't make any difference - X starts in 1024x768. >>> >>> So - how can I start X in 1280x1024 when I use "IgnoreEDID""on" option? >> Did you keep this line? >> modeline"1280x1...@lcd" 108 1280 1326 1440 1688 1024 1025 1028 1066 > > I didn't have it - but I added it and it made no difference. > > >> AFAIK EDID tells the card about supported modes and timings. Without it you >> need >> a manual modeline. Adding Option "PreferredMode" "1280x1024" to the monitor section did the trick. -- Tomasz Chmielewski http://wpkg.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
David Greaves schrieb: > Tomasz Chmielewski wrote: >> Tomasz Chmielewski schrieb: >> >>> Right, have it in man radeon as well. >>> >>> The only side effect is that now KDE4's panel has a 1024 px width when >>> the session loads, even though the desktop starts with 1280 px width - >>> and I have to resize it each time. >>> >>> But I guess that's a question for KDE's mailing list... >> Well, it is somehow related to the X configuration... >> >> With the configuration below, X starts in 1024x768 instead of 1280x1024 >> - why (then, KDE switches to 1280x1024, but the panel stays at 1024 px)? > > Can you pastebin the full log and the full config. Full config (it's a multiseat setup): http://pastebin.com/m72c7025a Full log for this card: http://pastebin.com/m4334f96b >> I even added: >> >> Option "PanelSize" "1280x1024" >> >> but it doesn't make any difference - X starts in 1024x768. >> >> So - how can I start X in 1280x1024 when I use "IgnoreEDID""on" option? > > Did you keep this line? > modeline"1280x1...@lcd" 108 1280 1326 1440 1688 1024 1025 1028 1066 I didn't have it - but I added it and it made no difference. > AFAIK EDID tells the card about supported modes and timings. Without it you > need > a manual modeline. -- Tomasz Chmielewski http://wpkg.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
screen resolution to be fixed in gnome
Hallo, my first post to this list. I am using debian sid with actual, i.e. latest packages. After some tuning I could bring the xserver-xorg to start gnome display manager and its welcome screen at the desired, highest resolution 1920 x 1200 px. However, after logging in it takes a few seconds and than the resolution shifts to 1280 x 800, something I never added to any configuration file. I am using gnome. Do you happen to know where -- aside from xorg.conf -- screen resolution is to be saved or controlled? Any help appreciated. Bernhard xserver-xorg is Version 1:7.3+18 libgnome2-0 is Version 2.20.1.1-2 my xorg.conf Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc102" Option "XkbLayout" "de" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "ATI Technologies, Inc. Radeon RV100 QY [Radeon 7000/VE]" Driver "ati" BusID "PCI:1:0:0" VideoRam65800 EndSection Section "Monitor" Identifier "Samsung T240HD" VendorName "Arlt.com" ModelName "T240HD" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 71.0 Modeline"1920x1200" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 Option "PreferredMode" "1920x1200" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies, Inc. Radeon RV100 QY [Radeon 7000/VE]" Monitor "Samsung T240HD" DefaultDepth24 SubSection "Display" Depth 15 Modes "1920x1200" Virtual 1920 1200 EndSubSection SubSection "Display" Depth 16 Modes "1920x1200" Virtual 1920 1200 EndSubSection SubSection "Display" Depth 24 Modes "1920x1200" Virtual 1920 1200 EndSubSection EndSection #uebernommen von http://linuxwacom.sourceforge.net/index.php/howto/ inputdev Section "InputDevice" Driver"wacom" Identifier"stylus" Option"Device""/dev/input/wacom" Option"Type" "stylus" Option"USB" "on" EndSection Section "InputDevice" Driver"wacom" Identifier"eraser" Option"Device""/dev/input/wacom" Option"Type" "eraser" Option"USB" "on" EndSection Section "InputDevice" Driver"wacom" Identifier"cursor" Option"Device""/dev/input/wacom" Option"Type" "cursor" Option"USB" "on" EndSection Section "InputDevice" Driver"wacom" Identifier"pad" Option"Device""/dev/input/wacom" Option"Type" "pad" Option"USB" "on" EndSection Section "ServerLayout" Identifier "Default Layout" Screen 0"Default Screen"0 0 InputDevice "Configured Mouse" "CorePointer" InputDevice "Generic Keyboard" "CoreKeyboard" InputDevice "stylus""SendCoreEvents" InputDevice "eraser""SendCoreEvents" InputDevice "cursor""SendCoreEvents" InputDevice "pad" EndSection ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
Tomasz Chmielewski wrote: > Tomasz Chmielewski schrieb: > >> Right, have it in man radeon as well. >> >> The only side effect is that now KDE4's panel has a 1024 px width when >> the session loads, even though the desktop starts with 1280 px width - >> and I have to resize it each time. >> >> But I guess that's a question for KDE's mailing list... > > Well, it is somehow related to the X configuration... > > With the configuration below, X starts in 1024x768 instead of 1280x1024 > - why (then, KDE switches to 1280x1024, but the panel stays at 1024 px)? Can you pastebin the full log and the full config. > I even added: > > Option "PanelSize" "1280x1024" > > but it doesn't make any difference - X starts in 1024x768. > > So - how can I start X in 1280x1024 when I use "IgnoreEDID""on" option? Did you keep this line? modeline"1280x1...@lcd" 108 1280 1326 1440 1688 1024 1025 1028 1066 AFAIK EDID tells the card about supported modes and timings. Without it you need a manual modeline. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
Tomasz Chmielewski schrieb: > Right, have it in man radeon as well. > > The only side effect is that now KDE4's panel has a 1024 px width when > the session loads, even though the desktop starts with 1280 px width - > and I have to resize it each time. > > But I guess that's a question for KDE's mailing list... Well, it is somehow related to the X configuration... With the configuration below, X starts in 1024x768 instead of 1280x1024 - why (then, KDE switches to 1280x1024, but the panel stays at 1024 px)? I even added: Option "PanelSize" "1280x1024" but it doesn't make any difference - X starts in 1024x768. So - how can I start X in 1280x1024 when I use "IgnoreEDID""on" option? Part of log: (II) RADEON(0): Adding Screen mode: 1280x1024 (II) RADEON(0): Total number of valid Screen mode(s) added: 1 (II) RADEON(0): Output: DVI-0, Detected Monitor Type: 3 in RADEONProbeOutputModes (II) RADEON(0): Adding Screen mode: 1280x1024 (II) RADEON(0): Total number of valid Screen mode(s) added: 1 (II) RADEON(0): Output: S-video, Detected Monitor Type: 0 (II) RADEON(0): Output VGA-0 connected (II) RADEON(0): Output DVI-0 connected (II) RADEON(0): Output S-video disconnected (II) RADEON(0): Output VGA-0 using initial mode 1024x768 (II) RADEON(0): Output DVI-0 using initial mode 1024x768 after xf86InitialConfiguration xorg.conf: Section "Device" Identifier "device0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "ATI Radeon 9600" BusID "PCI:01:00:0" Option "AccelMethod" "EXA" Option "IgnoreEDID""on" Option "PanelSize" "1280x1024" EndSection -- Tomasz Chmielewski http://wpkg.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
David Greaves schrieb: > Tomasz Chmielewski wrote: >> Oh, yeah, that did the trick, thanks. > > NP :) > >> Where is this option documented, though? Not in my xorg.conf manual. >> >> $ man xorg.conf|grep -i edid >> $ > > > For Debian it is man radeon > > Option "IgnoreEDID" "boolean" > Do not use EDID data for mode validation, but DDC is still used > for monitor detection. This is different from NoDDC option. > The default value is off. > > Lots of good stuff in there... Right, have it in man radeon as well. The only side effect is that now KDE4's panel has a 1024 px width when the session loads, even though the desktop starts with 1280 px width - and I have to resize it each time. But I guess that's a question for KDE's mailing list... -- Tomasz Chmielewski http://wpkg.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
Tomasz Chmielewski wrote: > Oh, yeah, that did the trick, thanks. NP :) > Where is this option documented, though? Not in my xorg.conf manual. > > $ man xorg.conf|grep -i edid > $ For Debian it is man radeon Option "IgnoreEDID" "boolean" Do not use EDID data for mode validation, but DDC is still used for monitor detection. This is different from NoDDC option. The default value is off. Lots of good stuff in there... David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
David Greaves schrieb: > Tomasz Chmielewski wrote: >> I have a radeon 9600 card, with two devices connected: >> >> - DVI: LCD monitor, capable of 1280x1024 (preferred mode) >> - VGA: LCD projector, capable of 1024x768, (800x600 preferred mode) >> > > I have the same card. One of my monitors doesn't send EDID and this config > works > for me: > > Section "Monitor" > Identifier "E481" > Option "LeftOf""H481" > Option "IgnoreEDID""on" Oh, yeah, that did the trick, thanks. Where is this option documented, though? Not in my xorg.conf manual. $ man xorg.conf|grep -i edid $ -- Tomasz Chmielewski http://wpkg.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: how to ignore monitor's EDID?
Tomasz Chmielewski wrote: > I have a radeon 9600 card, with two devices connected: > > - DVI: LCD monitor, capable of 1280x1024 (preferred mode) > - VGA: LCD projector, capable of 1024x768, (800x600 preferred mode) > I have the same card. One of my monitors doesn't send EDID and this config works for me: Section "Monitor" Identifier "E481" Option "LeftOf""H481" Option "IgnoreEDID""on" Option "DPMS" modeline"1280x1...@lcd" 108 1280 1326 1440 1688 1024 1025 1028 1066 EndSection HTH David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon supported resolutions?
Felix Miata wrote: > On 2008/12/27 23:07 (GMT+0200) Nikos Chantziaras composed: > >> Felix Miata wrote: > >>> I have DVI cards and >>> displays and cables, but have never found reason to try them. > >> Better picture quality. Many people can't make out a difference though. > > Exactly. How does any normal person find an opportunity to see any > difference? Most of the internet is extreme lowfi designed for 1024x768 or > below. It's only visible to me in "extreme" cases, like a red box on white background; there's a bit of red "running in" the black (I think that's called ghosting) or the default X background (this one always made my eyes cry with my old CRT). Nothing serious though. But since my monitor *is* digital (TFT) and my graphics card is also digital, it makes more sense to use DVI-D. With VGA, the graphics card converts its digital signal to an analog VGA signal and sends it over the cable. The monitor picks it up, and since it's a TFT monitor (they need a digital signal to display) it converts the analog signal back to a digital one. With DVI-D, the signal is just sent though the cable with no conversions and cable quality doesn't matter the least since it's digital. It makes more sense to me to use it that way rather than doing a totally useless and unneeded conversion from digital to analog and then back again. If you don't have a TFT monitor but a CRT instead, then this in not an issue at all. CRTs are analog (there's a few modern digital CRTs too, but you would know if you had one). It's only an issue with TFTs. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xorg-commit messages
On Sun, Dec 28, 2008 at 12:41:24AM -0800, Jeremy Huddleston wrote: > It looks like the automated messages to xorg-commit aren't getting > generated... is someone on that? Um, works for me: > To: xorg-com...@lists.freedesktop.org > Subject: xserver: Branch 'xorg-server-1.4-apple' > Message-Id: <20081228111526.8f83510...@kemper.freedesktop.org> > Date: Sun, 28 Dec 2008 03:15:26 -0800 (PST) > From: Jeremy Huddleston > List-Id: > > hw/xquartz/bundle/X11.sh | 15 +++ > 1 file changed, 11 insertions(+), 4 deletions(-) > > New commits: > commit 6bedaddd78aa04bd303df434a4c49bb87bd7deaa > Author: Jeremy Huddleston > Date: Sun Dec 28 01:53:38 2008 -0800 > > XQuartz: Try harder to get the user's login environment > > [...] Anything in particular you're missing? Cheers, Daniel signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
how to ignore monitor's EDID?
I have a radeon 9600 card, with two devices connected:
- DVI: LCD monitor, capable of 1280x1024 (preferred mode)
- VGA: LCD projector, capable of 1024x768, (800x600 preferred mode)
Both devices show the same output ("clone" - of course, if the
resolution is 1280x1024, VGA/LCD projector does not show any output, as
this device does not support this mode).
The problem is - whenever the LCD projector is powered on as computer
boots, X starts in 800x600 resolution.
What's worse - it's not possible to change the resolution to 1280x1024;
xrandr will only switch the resolution up to 1024x768 (maximum supported
by the VGA monitor).
Is it possible to force the resolution on a device, even if it doesn't
support it?
My xorg.conf setup for this video card looks like below; "monitor0" is
the LCD monitor; I don't have any section about the VGA output / LCD
projector.
Section "Monitor"
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
Identifier "monitor0"
VendorName "Plug'n Play"
ModelName "BenQ FP937s+"
HorizSync 31.0 - 83.0
VertRefresh 59.0 - 76.0
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection
Section "Device"
Identifier "device0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "ATI Radeon 9600"
BusID "PCI:01:00:0"
Option "AccelMethod" "EXA"
EndSection
Section "Screen"
Identifier "Screen0"
Device "device0"
Monitor"monitor0"
DefaultDepth24
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768"
EndSubSection
EndSection
--
Tomasz Chmielewski
http://wpkg.org
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon supported resolutions?
On Sun, Dec 28, 2008 at 09:58:32AM +0100, Tomasz Torcz wrote: > You seem to mistake screen resolution with screen quality (sharpness). ... and screen resolution for pixel density. Cheers, Daniel signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon supported resolutions?
Twas brillig at 05:33:04 28.12.2008 UTC-05 when mrma...@ij.net did gyre and gimble: FM> Is there some FOSS tool or web site that hosts images to be used FM> for testing for ghosting or blurriness? Famous X "grid" background which used to be a default background until recently is a good test. -- pgpoRD9JFlluo.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon supported resolutions?
On 2008/12/28 09:58 (GMT+0100) Tomasz Torcz composed: > On Sat, Dec 27, 2008 at 11:13:10PM -0500, Felix Miata wrote: >> On 2008/12/27 23:07 (GMT+0200) Nikos Chantziaras composed: >> > Felix Miata wrote: >> >> I have DVI cards and >> >> displays and cables, but have never found reason to try them. >> > Better picture quality. Many people can't make out a difference though. >> Exactly. How does any normal person find an opportunity to see any >> difference? Most of the internet is extreme lowfi designed for 1024x768 or >> below. > Normal person can see when image is blurred, or high-contrast items > have “ghosts� around them. It often happens with low- and medium-quality > VGA cables, never with DVI. > You seem to mistake screen resolution with screen quality (sharpness). You seem to have ignored my question, but then maybe none of the many permanently attached VGA cables, or few removable VGA cables, I have encountered during my lifetime would seem to qualify as low quality. Is there some FOSS tool or web site that hosts images to be used for testing for ghosting or blurriness? -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: input settings get ignored?
On Sunday 28 December 2008, Bernd Steinhauser wrote: > Hi, > > I was upgrading to xorg-server 1.6 Beta3 (1.5.99.3) and I have one nasty > problem, which I'm not sure if it is me doing something wrong or if > there is a bug. [snip] > In addition to that, some keys don't work or are working wrong, for > example, when using the standard layout, the ↑ key acts as a print key. > I guess that has something to do with the model or the rules. The up-arrow behaving like the print key is usually caused by using a pc10x keyboard model with the evdev driver. Try using evdev in your 10-x11-input-keyboard.fdi file. [snip] > Regards, > Bernd Regards, Magnus signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: input settings get ignored?
Peter Hutterer wrote: > On Sun, Dec 28, 2008 at 09:16:57AM +0100, Bernd Steinhauser wrote: >> Hi, >> >> I was upgrading to xorg-server 1.6 Beta3 (1.5.99.3) and I have one nasty >> problem, which I'm not sure if it is me doing something wrong or if >> there is a bug. >> >> The problem is, that my input settings (using hal, see the attached fdi >> files) get ignored. >> The strange thing is, that the log file tells me, that the server added >> devices with these settings, but when logging in and/or starting the DE, >> the keyboard layout is "us" (default?) and not "neo" which it should be. >> (Worked just fine with xorg-server 1.5, that's why I think there isn't a >> config problem.) >> >> In addition to that, some keys don't work or are working wrong, for >> example, when using the standard layout, the ↑ key acts as a print key. >> I guess that has something to do with the model or the rules. >> >> Anyway, is this a bug or am I missing something (maybe a newer version >> of some lib/proto etc?)? >> See the attached files for more info, should be two fdi files, lshal >> output (cut out the relevant parts), the log file and the xorg.conf. >> > > This is probably > http://lists.freedesktop.org/archives/xorg/2008-December/041522.html > http://bugs.freedesktop.org/show_bug.cgi?id=19048 > > Cheers, > Peter Thanks, that fixed it, for the keyboard. The touchpad settings still get ignored. This is what hal reports: input.x11_driver = 'synaptics' (string) input.x11_options.BottomEdge = 330 (0x14a) (int) input.x11_options.GuestMouseOff = 'On' (string) input.x11_options.HorizEdgeScroll = 'Off' (string) input.x11_options.LeftEdge = 20 (0x14) (int) input.x11_options.MaxSpeed = 1 (0x1) (int) input.x11_options.MinSpeed = 1 (0x1) (int) input.x11_options.RightEdge = 500 (0x1f4) (int) input.x11_options.SHMConfig = 'On' (string) input.x11_options.TapButton1 = 1 (0x1) (int) input.x11_options.TapButton2 = 2 (0x2) (int) input.x11_options.TapButton3 = 3 (0x3) (int) input.x11_options.TopEdge = 20 (0x14) (int) input.x11_options.VertScrollDelta = 10 (0xa) (int) (That's what is in the config file, too.) This is what synclient tells me after starting X: LeftEdge= 52 RightEdge = 524 TopEdge = 49 BottomEdge = 335 FingerLow = 25 FingerHigh = 30 FingerPress = 256 MaxTapTime = 180 MaxTapMove = 26 MaxDoubleTapTime= 180 SingleTapTimeout= 180 ClickTime = 100 FastTaps= 0 EmulateMidButtonTime= 75 EmulateTwoFingerMinZ= 257 VertScrollDelta = 12 HorizScrollDelta= 12 VertEdgeScroll = 0 HorizEdgeScroll = 0 CornerCoasting = 0 VertTwoFingerScroll = 1 HorizTwoFingerScroll= 0 MinSpeed= 0.4 MaxSpeed= 0.7 AccelFactor = 0.0829187 TrackstickSpeed = 40 EdgeMotionMinZ = 30 EdgeMotionMaxZ = 160 EdgeMotionMinSpeed = 1 EdgeMotionMaxSpeed = 48 EdgeMotionUseAlways = 0 UpDownScrolling = 1 LeftRightScrolling = 1 UpDownScrollRepeat = 1 LeftRightScrollRepeat = 1 ScrollButtonRepeat = 100 TouchpadOff = 0 GuestMouseOff = 1 LockedDrags = 0 LockedDragTimeout = 5000 RTCornerButton = 0 RBCornerButton = 0 LTCornerButton = 0 LBCornerButton = 0 TapButton1 = 0 TapButton2 = 0 TapButton3 = 0 ClickFinger1= 1 ClickFinger2= 1 ClickFinger3= 1 CircularScrolling = 0 CircScrollDelta = 0.1 CircScrollTrigger = 0 CircularPad = 0 PalmDetect = 0 PalmMinWidth= 10 PalmMinZ= 200 CoastingSpeed = 0 PressureMotionMinZ = 30 PressureMotionMaxZ = 160 PressureMotionMinFactor = 1 PressureMotionMaxFactor = 1 GrabEventDevice = 1 But that might actually be a different problem related to the synaptics driver only. Regards, Bernd ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: input settings get ignored?
On Sun, Dec 28, 2008 at 09:16:57AM +0100, Bernd Steinhauser wrote: > Hi, > > I was upgrading to xorg-server 1.6 Beta3 (1.5.99.3) and I have one nasty > problem, which I'm not sure if it is me doing something wrong or if > there is a bug. > > The problem is, that my input settings (using hal, see the attached fdi > files) get ignored. > The strange thing is, that the log file tells me, that the server added > devices with these settings, but when logging in and/or starting the DE, > the keyboard layout is "us" (default?) and not "neo" which it should be. > (Worked just fine with xorg-server 1.5, that's why I think there isn't a > config problem.) > > In addition to that, some keys don't work or are working wrong, for > example, when using the standard layout, the ↑ key acts as a print key. > I guess that has something to do with the model or the rules. > > Anyway, is this a bug or am I missing something (maybe a newer version > of some lib/proto etc?)? > See the attached files for more info, should be two fdi files, lshal > output (cut out the relevant parts), the log file and the xorg.conf. > This is probably http://lists.freedesktop.org/archives/xorg/2008-December/041522.html http://bugs.freedesktop.org/show_bug.cgi?id=19048 Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon supported resolutions?
On Sat, Dec 27, 2008 at 11:13:10PM -0500, Felix Miata wrote: > On 2008/12/27 23:07 (GMT+0200) Nikos Chantziaras composed: > > > Felix Miata wrote: > > >> I have DVI cards and > >> displays and cables, but have never found reason to try them. > > > Better picture quality. Many people can't make out a difference though. > > Exactly. How does any normal person find an opportunity to see any > difference? Most of the internet is extreme lowfi designed for 1024x768 or > below. Normal person can see when image is blurred, or high-contrast items have “ghosts” around them. It often happens with low- and medium-quality VGA cables, never with DVI. You seem to mistake screen resolution with screen quality (sharpness). -- Tomasz TorczTo co nierealne -- tutaj jest normalne. zdzi...@irc.-nie.spam-.pl Ziomale na życie mają tu patenty specjalne. pgpFXY7aZCJ16.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
bump: Xorg segfaults on XOpenDisplay multi thread
Bump, adding some backtraces: Dump 1: #0 _X11TransWritev (ciptr=0x0, buf=0x21b96720, size=1) at ../../lib/xtrans/Xtrans.c:911 #1 0x20093910 in _XSendClientPrefix (dpy=, client=, auth_proto=0x0, auth_string=0x0, prefix=0x21b96784) at ConnDis.c:572 #2 0x200c4640 in XOpenDisplay (display=) at OpenDis.c:295 #3 0x40001580 in ThreadMain_OpenDisplayAndStartTest (num=0x1) at ../../thread.cpp:37 #4 0x2027d5d0 in start_thread () from /lib/libpthread.so.0 #5 0x207cb730 in __clone2 () from /lib/libc.so.6.1 Dump 2: #0 0x2070f350 in malloc_consolidate () from /lib/libc.so.6.1 #1 0x20714830 in _int_malloc () from /lib/libc.so.6.1 #2 0x20716ef0 in calloc () from /lib/libc.so.6.1 #3 0x200c4530 in XOpenDisplay (display=) at OpenDis.c:262 #4 0x40001580 in ThreadMain_OpenDisplayAndStartTest (num=0x2) at ../../thread.cpp:37 #5 0x2027d050 in start_thread () from /lib/libpthread.so.0 #6 0x207cb730 in __clone2 () from /lib/libc.so.6.1 i explored this topic for quite a while, when i debug it i see memory corruptions every time it crashes. memory corruptions doesn't always occur at the same place which makes it even harder and more confusing. i am currently trying to build the debug version with dmalloc to see it it might find some memory over runs and so forth. Machine spec: IA64 /SUSE Linux Enterprise Server/ 10 sp 2 xorg x11 6.9.0-50.58 I have a very simple test program that opens 4 threads and does XOpenDisplay(opening 4 separate display objects). i keep getting segfaults on different places in the function seems like some kind timing problem that causes memory corruption. before i start giving backtraces here any one seen this problem before? I can re-produce when working on X in debug, but couldn't re-produce it when used Electric Fence Malloc Debugger with my program (wanted to see if memory check can find any overruns) ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
xorg-commit messages
It looks like the automated messages to xorg-commit aren't getting generated... is someone on that? ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
