Bug report submitted (was: Re: xf86-video-intel 2.4.1: Problems with 915GM and Asus VW222S)
Dear list, Am Mittwoch, den 03.09.2008, 22:21 +0200 schrieb Paul Menzel: > Am Dienstag, den 02.09.2008, 16:05 +0200 schrieb Paul Menzel: > > > I am the owner of an ASUS EeePC 701 4G and am not able to get the ASUS > > VW222S [2] as an external display going at a resolution of 1680 * 1050 > > over VGA, which is the only port available. > > I forgot to mention. > > 1. The ASUS EeePC 701 4G has an Intel 910 GML Express chipset. > 2. The monitor is working on my desktop PC with the openchrome driver. > > > PS: Please CC me, as I am not subscribed to the list. > > 3. I am subcsribed to the list ;) > > > Any ideas or hints where I could look? Do those > > (EE) intel(0): underrun on pipe A! > > have to do with this? I filed a bug report under [3]. Thanks, Paul PS: I would be interested, what I did wrong (subject, form, …) so I did not get any answer, so that I will not make this mistake next time. A link to a webpage with the rules would also suffice. > > [1] http://en.wikipedia.org/wiki/EeePC > > [2] > > http://www.asus.com/products.aspx?l1=10&l2=89&l3=362&l4=0&model=1741&modelmenu=1 [3] https://bugs.freedesktop.org/show_bug.cgi?id=17629 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Bug report submitted
Dear list, Am Donnerstag, den 18.09.2008, 09:41 +0100 schrieb Colin Guthrie: > Paul Menzel wrote: > > PS: I would be interested, what I did wrong (subject, form, …) so I did > > not get any answer, so that I will not make this mistake next time. A > > link to a webpage with the rules would also suffice. > > I don't think you did anything specifically wrong. > > I notice you don't have any monitor glue or modelines avaialble in your > xorg.conf. Ok, I will dig into those words on the WWW. > You should have a look at that. > http://www.intellinuxgraphics.org/dualhead.html Thanks, I will do this. Bests, Paul > > Col > > > -- > > Colin Guthrie > gmane(at)colin.guthr.ie > http://colin.guthr.ie/ > > Day Job: >Tribalogic Limited [http://www.tribalogic.net/] > Open Source: >Mandriva Linux Contributor [http://www.mandriva.com/] >PulseAudio Hacker [http://www.pulseaudio.org/] >Trac Hacker [http://trac.edgewall.org/] > > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Samsung Syncmaster 741MP problem
Dear Mattias, Am Samstag, den 13.12.2008, 19:03 +0100 schrieb Mattias: > I have a problem with my Linux Box (Mint 5) regarding the screen monitor > (so I thought it is a problem of the XOrg Video). When i try to use full > screen applications, such as games, my screen gets black and says > (Resolution not optimal. Suggested: 1280x1024 60Hz). I am using the > NVIDIA Binary drivers (should be 177.xx). I think you will not get any answers on this list, because you are using the NVIDIA proprietary drivers, which cannot be supported because no source code is available. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Maximum Screen Size for intel driver
Dear Greg,
Am Samstag, den 20.12.2008, 20:38 + schrieb Greg Stark:
>
>
> On Sat, Dec 20, 2008 at 6:58 PM, Greg Stark wrote:
> I'm running into this intel driver limit on a i945GM card:
>
> xrandr: screen cannot be larger than 1280x1824 (desired size
> 1920x1824)
>
> I've recompiled from source from
> git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel
> but it seems at
> least the master branch still has this problem. Are there
> plans to work around
> this problem? Is there a branch containing fixes for it?
>
> I know it's possible because in Windows this card happily
> drives this monitor
> at 1920x1200 for a total desktop size of 3200x1200.
>
>
> I'm not sure if this is related but I see the following code in
> i830_driver.c:
>
> /* See i830_exa.c comments for why we limit the framebuffer size
> like this.
> */
> if (IS_I965G(pI830)) {
> max_width = 8192;
> max_height = 8192;
> } else {
> max_width = 2048;
> max_height = 2048;
> }
> xf86CrtcSetSizeRange (pScrn, 320, 200, max_width, max_height);
>
> There is no such related comments in i830_exa.c as the comment here
> claims. (In fact there are hardly any comments in i830_exa.c at all).
> Is this code just obsolete? What will happen if I just put a more
> reasonable set of values here?
I heard, there are some technical limitations to it in the
implementation.
I think [1] is the way to go. (Look for Virtual.)
Thanks,
Paul
[1]
http://wiki.debian.org/DebianEeePC/HowTo/Configure#head-5002c433e6ebf8a0a8fae6ae545cc32789bdae3f
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problem with xorg and intel g43
Dear Fabio, where is your first message you are referring to. Could you please post a link. Am Mittwoch, den 04.03.2009, 12:00 +0100 schrieb Fabio: […] > Does anybody have some hint? I also had problems getting the ASUS VW222S to work. Take a look at [1] for the hints I got to solve this. I can not comment on the freezes. Thanks, Paul [1] https://bugs.freedesktop.org/show_bug.cgi?id=17629 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problem with xorg and intel g43
Am Mittwoch, den 04.03.2009, 20:26 +0100 schrieb Fabio: > > where is your first message you are referring to. Could you please post > > a link. > > > > It is a thread of two months ago; here is the link > > http://lists.freedesktop.org/archives/xorg/2009-January/042176.html > > >> Does anybody have some hint? > > > > I also had problems getting the ASUS VW222S to work. Take a look at [1] > > for the hints I got to solve this. > > > > I can not comment on the freezes. > > > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=17629 > > > > Thank you very much for this link. I see that, quite likely, there is an > issue with this family of monitors and the intel driver but it seems > quite hard to find it and fix it. > > If you read the old thread, you will discover that I got a working > modeline using powerstrip under windows. I didn't know about > cvt -v -r 1680 1050 > which I discovered reading your link: I tried it and it gives me a > different modeline with respect to the one I found. Namely, mine is > Modeline "1680x1050" 147.600 1680 1784 1968 2256 1050 1051 1054 1087 -hsync > +vsync > whereas cvt gives > Modeline "1680x1050R" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 > +hsync -vsync > I will give it a try: maybe this will fix the crash...! I doubt that it will help with the crash, because the graphics card should not know if the monitor cannot display the image. But who knows. Anyway, if it does not work, you should definitely file a bug report. Only then my problem was dealt with by the intel engineer. And I do not know if such problems need to be send to a specific intel list to get help. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Problem with xorg and intel g43
Dear Fabio, sorry for the late reply. Am Donnerstag, den 05.03.2009, 11:47 +0100 schrieb Fabio: > >> If you read the old thread, you will discover that I got a working > >> modeline using powerstrip under windows. I didn't know about > >> cvt -v -r 1680 1050 > >> which I discovered reading your link: I tried it and it gives me a > >> different modeline with respect to the one I found. Namely, mine is > >> Modeline "1680x1050" 147.600 1680 1784 1968 2256 1050 1051 1054 > 1087 -hsync +vsync > >> whereas cvt gives > >> Modeline "1680x1050R" 119.00 1680 1728 1760 1840 1050 1053 1059 > 1080 +hsync -vsync > >> I will give it a try: maybe this will fix the crash...! > > > > I doubt that it will help with the crash, because the graphics card > > should not know if the monitor cannot display the image. But who > knows. > > I made some tests and the result is that, at least, it looks more > stable, > which is an improvement... ;-) > To be sure, I need more time since the crash I experience is not > deterministic: sometime it happens at boot time, just when gdm > starts, > sometimes it happens when changing user, sometime it doesn't happen > at > all! > > > > Anyway, if it does not work, you should definitely file a bug > report. > > Only then my problem was dealt with by the intel engineer. And I do > not > > know if such problems need to be send to a specific intel list to > get > > help. > > I will think about that, but it is diffucult to describe it since the > resolution works fine, once manually defined, whereas the crashes, as > I > said, are quite randoms. Maybe the developers will know more option and tools to be useful for debugging. Did you enable the debug option of the intel driver? > There is also another issue: as I wrote in a previous mail, the intel > device is not autorecognized by knoppix. This fact is quite strange. > May I ask you which device is yours? It is an ASUS Eee PC 701 4G [1]. > Mine is a G43, on integrate on the mother board Asus P5QL-EM. > In case, can you try to boot knoppix? If you also experience the same > problem, maybe this also could be signaled as a bug. Sorry, I do not have an external CD/DVD drive, so I cannot test. Thanks, Paul [1] http://en.wikipedia.org/wiki/Asus_Eee_PC signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[PATCH] Fix example for rotate in manual.
As can be read some lines above. Rotation can be one of 'normal', 'left', 'right' or 'inverted'. This causes the output contents to be rotated in the specified direction. 'right' specifies a clockwise rotation of the picture and 'left' specifies a counter-clockwise rotation. Signed-off-by: Paul Menzel --- xrandr.man |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/xrandr.man b/xrandr.man index e3d7daf..c7396ba 100644 --- a/xrandr.man +++ b/xrandr.man @@ -284,7 +284,7 @@ Reflect across the X axis. Reflect across the Y axis. .SH EXAMPLES Sets an output called LVDS to its preferred mode, and on its right put an -output called VGA to preferred mode of a screen which has been physically rotated clockwise: +output called VGA to preferred mode of a screen which has been physically rotated counter-clockwise: .RS xrandr --output LVDS --auto --rotate normal --pos 0x0 --output VGA --auto --rotate left --right-of LVDS .RE -- 1.6.2 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Debian Sid with NVidia card : Xorg cannot start...
Dear David, Am Montag, den 13.04.2009, 10:22 +0200 schrieb David BERCOT: > I'm new on this list and this is my first message. > I hope it's not a "classical" error but I had a (quick) look in the > archives and I did not found any solution... > > First of all, I use Debian Sid with a 2.6.29 kernel. I've tried to > install the non-free NVidia drivers but it seems that there is a > bug with the 2.6.29 kernel. So, I have to use the free drivers > (expecting for the bug to be resolved soon ;-))). > > So, I've tried to install Lenny. Everything was OK (but the resolution > that Xorg uses is 1600x1200 instead of the real resolution of > 1680x1050 !!!). Then, I've tried Squeeze and it was ok too (same Xorg > version : 1:7.3+18). And, last, I've tried with Sid and Xorg can't > start !!! Now, the Xorg version is 1:7.4+1. My Xorg.conf is empty (not > really, but there are no information about my card, the driver to use, > etc...). The error is : > > X.Org X Server 1.6.0 > Release Date: 2009-2-25 > X Protocol Version 11, Revision 0 > Build Operating System: Linux 2.6;29-1-amd64 x86_64 Debian > [...] > (EE) No devices detected. > Fatal server error: > no screens found > > Do you have any idea ? I guess it does not have to do anything with the video module. Maybe take a look at [1]. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515214 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
What is the correct list to discuss and send patches for xf86-video-intel?
Dear everyone, is this list the correct one? Or is there a special list for this? I did not find this exact information on [1]. It says, For questions regarding the use of this driver or questions about the development of this driver, please use the xorg@lists.freedesktop.org mailing list. so I am not a hundred percent sure. Thanks, Paul [1] http://intellinuxgraphics.org/feedback.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[OT] Git, Debian and development against xserver (intel driver)
Dear everyone (probably more Debian developers), I am not posting this to the Git mailing list, because I think the question does more deal with the workflow of the Debian sources(?). I have some patches against xf86-video-intel 2.3.2, which is the version in Debian Lenny. Ultimately these should be integrated upstream, so probably in version 2.7.0. The developer of the patch is using Debian Lenny and therefore it would be convenient to be able to build always a Debian package to be able to test the patches. My question is: “How is your repository setup?” or “How do you do this?”. The Debian Git repository is available [1] and of course the xorg one too [2]. 1. One suggestion I got was to do the following. git init git remote add xorg git://anongit.freedesktop.org/xorg/driver/xf86-video-intel git remote add debian git://git.debian.org/git/pkg-xorg/driver/xserver-xorg-video-intel git fetch debian ; git fetch --tags debian git fetch xorg ; git fetch --tags xorg # there are some minor discrepancies between the tags git br frc-patch xorg/master git br frc-debian-lenny debian/debian-lenny # publish the branches on a server Then develop against one branch (probably debian-lenny the patches are based on) and cherry-pick them into master. 2. One other way is to only use the Debian Git repository because it tracks the xorg branches. git clone git://git.debian.org/git/pkg-xorg/driver/xserver-xorg-video-intel git checkout --track origin/upstream-lenny # apply patches against upstream-lenny git checkout --track origin/debian-lenny git merge upstream-lenny # rebase does not work # adapt a Debian specific patch # publish the branches on a server 3. Or would it be better to directly develop against debian-lenny? Debian developers, is debian-lenny based on upstream-lenny and how to update debian-lenny. Using rebase, merge or cherry-pick? Sorry for this kind of post. But I am no Git expert, so any advice is much appreciated. Thanks, Paul [1] http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-intel.git [2] http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
start Xserver with disconnected display
Dear list, if I understand it correctly the Xserver does not start, if it finds no connected display. At least it is this way for the intel driver I think¹. Is there an option to disable this autodetection and start up nevertheless if the parameters for the display are provided via xorg.conf? Would such an option have to be implemented for the Xserver or each video driver seperately? Thanks, Paul ¹ It gets checked for example in i830_crt.c static xf86OutputStatus i830_crt_detect(xf86OutputPtr output) and returns XF86OutputStatusConnected or XF86OutputStatusDisconnected. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: After an update I get error message "no screens found"
Dear Marco, Am Montag, den 27.04.2009, 13:02 +0200 schrieb rosenrei...@arcor.de: > I updated my system and after a reboot the Xserver failed to start. I got the > message: > > (EE) Screen(s) found, but none have a usable configuration. > Fatal server error: > no screens found > > I tried the new unmodified xorg.conf and my old working xorg.conf (attached) > configuration and I got the same error (logfile attached). > > What's wrong? > > My system is debian lenny-testing, 2.6.26-1-sparc64, X.Org X Server 1.4.2 […] > Section "Device" > Identifier "ATI Technologies 3D Rage Pro or similar (ATY,GT-C)" > Driver "ati" > BusID "PCI:1:2:0" > Option "UseFBDev" "true" > EndSection […] > (II) Setting vga for screen 0. > (**) MACH64(0): Depth 24, (--) framebuffer bpp 32 > (==) MACH64(0): Using XAA acceleration architecture > (WW) MACH64: Mach64 in slot 1:2:0 could not be detected! Could this be the problem. Is the BusID still the same after the upgrade? > (II) UnloadModule: "mach64" > (EE) Screen(s) found, but none have a usable configuration. > > Fatal server error: > no screens found Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: AllowEmptyInput and HAL
Am Dienstag, den 28.04.2009, 22:01 +0100 schrieb Phil Endecott: > Hello again, > > My efforts to recover from a dead computer continue. I have > resurrected the old disk in a new box, but the new box has a different > graphics chip and installing the (Debian packaged) driver for that has > brought in new bits of everything, and it has all gone bad. > > Specifically, when X started I had no keyboard or mouse. After > power-cycling [no other way to escape!] I found a message in the log > saying that "AllowEmptyInput" was enabled and that my keyboard and > mouse configuration was being ignored. Having looked this up in man > xorg.conf I see that this mode is the default. I'll try to be polite: > This does not seem like the most useful behaviour. > > Having set AutoAddDevices to false in order to disable the unhelpful > AllowEmptyInput, I now have a functioning mouse. But I have a keyboard > where every alternate keystroke produces the right letter and the > others produce garbage (maybe top-bit-set characters?). > > I also noticed some messages in the log where "config/hal" complained > that "NewInputDeviceRequest failed". Presumably this is because of my > AutoAddDevices. I had noticed that Debian installed "hal"; I had not > previously heard of it. It looks like something that sits on top of udev. > > So I've now spent most of three days on this. I just want a computer > that works, preferably as well as the old one did, and while I don't > have one I can't do much work [I'm self-employed]. So could someone > please suggest what I should do: > > - Is there some simple set of xorg.conf settings that will make it just > work like it did before, without any AllowEmptyInput and HAL stuff and > with a functional keyboard? > > - Or would I be better off trying to learn how this HAL thing works? > > X is something that I only have to understand once every few years when > I have some new hardware. By the next time I need to understand it, > either I have forgotten something vital or it has all changed What Debian release do you use and what X.org version? If you run unstable with xserver-xorg 1:7.4+1 you should be able to just delete your xorg.conf file and everything should work out of the box. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: AllowEmptyInput and HAL
Am Dienstag, den 05.05.2009, 18:58 +0100 schrieb Phil Endecott: > Still battling with this. Help! Some new details below. I do not have a clue. So I just shoot into the dark. Did you already try using a LiveCD or a fresh installation? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Setting resolution of external monitor
Dear Oliver, Am Samstag, den 23.05.2009, 14:24 +0200 schrieb Oliver Block: > On Thu, May 21, 2009 at 12:43:54PM +0200, Éric Piel wrote: […] > > Otherwise, have you tried forcing the mode of the VGA_1 output? > > Something like: > > xrandr --newmode "1920x1080n" 148.50 1920 2008 2052 2200 1080 1084 > > 1089 1125 +hsync +vsync > > xrandr --addmode VGA_1 "1920x1080n" > > xrandr --output VGA_1 --mode "1920x1080n" > I tried this. This first command (newmode) works, but the second fails. > > $ xrandr --addmode VGA_1 "1920x1080n" > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 155 (RANDR) > Minor opcode of failed request: 18 () > Serial number of failed request: 17 > Current serial number in output stream: 18 I guess that your output device is named differently. Do $ xrandr and look what how your VGA device is named and change the parameter. You can also search in the manual for for example addmode like $ man xrandr /addmod # return and `n` for the next match Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [PATCH 1/2] kdrive: add protocol mouse option
Am Dienstag, den 26.05.2009, 15:30 +0200 schrieb Olivier Blin: > kdrive probes a lot of PS/2 protocols for the mouse device, which > makes the mouse unusable for some seconds after X startup. > This new "protocol" option allows forcing the mouse protocol. > It can be used this way: > Xfbdev -mouse mouse,,protocol=ps/2 -keybd keyboard > > Signed-off-by: Olivier Blin > --- > hw/kdrive/linux/mouse.c |4 +++- > hw/kdrive/src/kdrive.h |1 + > hw/kdrive/src/kinput.c |3 +++ > 3 files changed, 7 insertions(+), 1 deletions(-) I have no clue, but should this new option be documented in the help output or manpage? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[cgit] No repositories found
Dear list, from [1] I click on 2009-02-26 Intel video driver patch [2] and get the following message. No repositories found Is that behavior correct? Thanks, Paul [1] http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/src/i810_driver.c [2] http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=f53bdad1412f841075232455837578f00709c6ef signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[synaptics] [PATCH] Fix typo. s/tough/though/
Signed-off-by: Paul Menzel --- man/synaptics.man |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/man/synaptics.man b/man/synaptics.man index d990304..8f7812c 100644 --- a/man/synaptics.man +++ b/man/synaptics.man @@ -16,7 +16,7 @@ synaptics \- Synaptics touchpad input driver .SH DESCRIPTION .B synaptics is an __xservername__ input driver for the touchpads from Synaptics -Incorporated. Even tough these touchpads (by default, operating in a +Incorporated. Even though these touchpads (by default, operating in a compatibility mode emulating a standard mouse) can be handled by the normal evdev or mouse drivers, this driver allows more advanced features of the touchpad to become available. Some benefits would be: -- 1.6.3.1 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: RFC: Xv field order
Dear Krzysztof, Am Montag, den 22.06.2009, 21:56 +0200 schrieb Krzysztof Halasa: […] > I'm at a point with all needed hardware info to implement interlaced > mode (mainly for perfect Xvideo playback) in intel driver. Now there is > another question: how should an Xv client interface with it? Do we have > any interlaced field-aware Xv interface? I am no expert and do not know if it has anything to do with your “problem”, but have you heard of the FRC patches [1] yet? I put Thomas, the author of the patches, to receivers of this message. […] Bests, Paul [1] http://frc.easy-vdr.de/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: F11: Why is Xorg with Intel 945 failing to allow 1600x1200 resolutions?
Dear Daniel, Am Montag, den 24.08.2009, 10:35 -0700 schrieb Daniel B. Thurman: > On Fedora 8/9, I was able to drop in my xorg.conf > file into /etc/X11 directory and was able to get > the X display to recognize the Monitor type and > I get 1600x1200 resolution, but for some reason, > I am not able to do this with Fedora 11. > > My monitor is a Hitachi CM715, and my onboard > video chip is an Intel 82945G/GZ Integrated graphics > controller. > > I have tried system-config-display & it seems > to limit my resolution to 1280x1024. I note with > this tool, there is no possible way to change the > vertical refresh rate. Maybe this is GNOME or Fedora specific? > I know that F8/9, Ubuntu 8/9, and Debian 5 works with > 1600x1200 mode, I haven't tried Fedora 10, and Fedora > 11 is limited to 1280x1024. > > It seems to me that xorg on F11 is a version that does > not support 1600x1200 mode. > > I have supplied an attachment for Xorg.0.log with this post. > > How can I resolve this problem? It looks like the EDID information advertise the 1600x1200 resolution. Could you post your xorg.conf file? Could you test to just move the file somewhere else and see what happens to start X without a configuration file? Could you post the version of the Intel driver in each distribution? The next would probably compare the output of /var/log/Xorg.0.log. If this does not help and the version in Fedora 11 is the newest of all, than you could try the Git version. If this does not give any clues the best thing would be to open a ticket in Bugzilla for the Intel driver and the developers will help you there. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: S-video detection on Radeon 8500LE
Dear Martin, Am Samstag, den 29.08.2009, 11:18 +0200 schrieb Martin Doucha: > Dave Airlie napsal(a): > > These cards have an off-chip tv-out that we don't support in the driver > > yet. > > How can I help with getting it supported then? Is anybody working on it > at the moment or should I start coding on my own? I do not know if you need documentation for tho off-chip tv-out and if you will get access to it. If not, there is an alternative by using a VGA2SCART-cable. If you are lucky you will also be able to use frame rate control [1] which other say has superior quality to S-Video. Bests, Paul [1] http://frc.easy-vdr.de/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: start Xserver with disconnected display
Dear list, Am Mittwoch, den 22.04.2009, 11:38 +0200 schrieb Paul Menzel: > if I understand it correctly the Xserver does not start, if it finds no > connected display. At least it is this way for the intel driver I > think¹. > > Is there an option to disable this autodetection and start up > nevertheless if the parameters for the display are provided via > xorg.conf? > > Would such an option have to be implemented for the Xserver or each > video driver seperately? Due to this message on intel-gfx [1] I found out, that there is a feature request open in Bugzilla and a patch for it attached [2]. How do we get this applied? > ¹ It gets checked for example in i830_crt.c > > static xf86OutputStatus i830_crt_detect(xf86OutputPtr output) > > and returns XF86OutputStatusConnected or XF86OutputStatusDisconnected. Thanks, Paul [1] http://lists.freedesktop.org/archives/intel-gfx/2009-September/004048.html [2] https://bugs.freedesktop.org/show_bug.cgi?id=14611 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [intel-gfx 2.9.1] intel driver resolution problem
Dear Joerg, Am Dienstag, den 29.12.2009, 17:22 +0100 schrieb Joerg Dorchain: > with my setup, the intel driver does not find out my preferred resolution > by itself. For some reason, I am stuck with 800x600. Adding a modeline in > the xorg.conf helps, but that is exactly copied from the Xorg.log, so IMHO > the driver should be able to figure out this by itself. > > Is there a better way than to give the modeline explicitly? Did you try with no `xorg.conf` at all? > Below are my xorg.onf and the Xorg.log, with and without modeline. So you are using the latest released intel driver (2.9.1). To get more help I suggest to directly contact the list for the driver [1][2] (taken from [3]) or—which is preferred—open a bug report [4] and report the bug number/URL back here. Thanks, Paul [1] intel-...@lists.freedesktop.org [2] http://lists.freedesktop.org/mailman/listinfo/intel-gfx [3] http://intellinuxgraphics.org/ [4] http://intellinuxgraphics.org/how_to_report_bug.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [intel-gfx 2.9.1] intel driver resolution problem
Am Mittwoch, den 30.12.2009, 15:47 +0100 schrieb Joerg Dorchain: > On Wed, Dec 30, 2009 at 12:31:25PM +0100, Paul Menzel wrote: > > Am Dienstag, den 29.12.2009, 17:22 +0100 schrieb Joerg Dorchain: > > > with my setup, the intel driver does not find out my preferred resolution > > > by itself. For some reason, I am stuck with 800x600. Adding a modeline in > > > the xorg.conf helps, but that is exactly copied from the Xorg.log, so IMH= > > O > > > the driver should be able to figure out this by itself. > > >=20 > > > Is there a better way than to give the modeline explicitly? > > > > Did you try with no `xorg.conf` at all? > > Yes. But without > Section "ServerFlags" > Option "AllowEmptyInput" "Off" # No HAL on this machine > EndSection > I do not get any input devices at all. But did you experience the same problem with the resolution? > > So you are using the latest released intel driver (2.9.1). To get more > > help I suggest to directly contact the list for the driver [1][2] (taken > > from [3]) or=E2=80=94which is preferred=E2=80=94open a bug report [4] and r= > > eport the bug > > number/URL back here. > > I'll try the mailing list first. Maybe it is simple. This is [1] for those who want to follow up. Thanks, Paul [1] http://lists.freedesktop.org/archives/intel-gfx/2009-December/005255.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: i915 driver
Dear Neil, Am Mittwoch, den 30.12.2009, 16:59 -0500 schrieb Neil Sikka: > Hello. I am trying to get the different display modes working with my > portege M400 laptop. Im running 2.6.32 with the toshiba_acpi module. > the problem is that when i do: > > echo "lcd_out:0;crt_out:1" > /proc/acpi/toshiba/video > cat /proc/acpi/toshiba/video > > i get: > lcd_out: 1 > crt_out: 0 > tv_out: 0 > > I am following the guide at > http://memebeam.org/toys/ToshibaAcpiDriver. Why does the state of the > crt_out variable not change? the kernel file where this is handled is: > kernel/drivers/portability/ > x86/toshiba_acpi.c. I have the same problem as these guys here: > > http://osdir.com/ml/linux.hardware.toshiba/2003-04/msg00216.html > > I tried doing what was suggested at that link, but that did not work > either. Is there a known bug where the state of the driver (as seen by > cat /proc/acpi/toshiba/video) is not updated by writing to it(echo > "lcd_out:0;crt_out:1" > /proc/acpi/toshiba/video)? It seems that the > state written to this file is not persistant. I have posted my problem > in full detail here > (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/tvout-from-toshiba-portege-m400-777822/). > thanks. is not that problem related to the toshiba acpi driver and belongs to a different mailing list. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
list for Toshiba Laptop ACPI Extras driver for Linux (was: i915 driver)
Dear Neil, [Please always reply to the list, so that everybody can profit and answer, and please do not top post. (I adapted it manually.] Am Montag, den 04.01.2010, 17:48 -0500 schrieb Neil Sikka: > On Thu, Dec 31, 2009 at 6:03 AM, Paul Menzel > wrote: > > Am Mittwoch, den 30.12.2009, 16:59 -0500 schrieb Neil Sikka: > >> Hello. I am trying to get the different display modes working with my > >> portege M400 laptop. Im running 2.6.32 with the toshiba_acpi module. > >> the problem is that when i do: > >> > >> echo "lcd_out:0;crt_out:1" > /proc/acpi/toshiba/video > >> cat /proc/acpi/toshiba/video > >> > >> i get: > >> lcd_out: 1 > >> crt_out: 0 > >> tv_out: 0 > >> > >> I am following the guide at > >> http://memebeam.org/toys/ToshibaAcpiDriver. Why does the state of the > >> crt_out variable not change? the kernel file where this is handled is: > >> kernel/drivers/portability/ > >> x86/toshiba_acpi.c. I have the same problem as these guys here: > >> > >> http://osdir.com/ml/linux.hardware.toshiba/2003-04/msg00216.html > >> > >> I tried doing what was suggested at that link, but that did not work > >> either. Is there a known bug where the state of the driver (as seen by > >> cat /proc/acpi/toshiba/video) is not updated by writing to it(echo > >> "lcd_out:0;crt_out:1" > /proc/acpi/toshiba/video)? It seems that the > >> state written to this file is not persistant. I have posted my problem > >> in full detail here > >> (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/tvout-from-toshiba-portege-m400-777822/). > >> thanks. > > > > is not that problem related to the toshiba acpi driver and belongs to a > > different mailing list. Do you know which mailing list i should mail about this issue? Reading the [1] I would try the following. 1. »Adding questions [to the page] is also helpful.« Edit [1] and put your question there. 2. If that does not help. Mail the auther directly. 3. Ask on the list of Linux ACPI [2]. Thanks, Paul [1] http://memebeam.org/toys/ToshibaAcpiDriver [2] http://www.lesswatts.org/projects/acpi/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel, xrandr and performance.
Am Sonntag, den 10.01.2010, 20:03 +0100 schrieb Łukasz Maśko: > My laptop has an Intel 945GM graphics chip. Right now I'm using Intel driver > 2.9.1. It works pretty well, but... > > If I turn on my secondary display with xrandr (it is an LCD screen connected > via DVI, I'm setting it as a cloned display), graphics performs much slower. > It concerns video and OpenGL (desktop effects inder KDE4). About a month > ago, before I switched to KDE4, under KDE3 everything was working OK using > the same hardware configuration. > > Is it just a general case, or I have something not correctly configured? I have no clue. But does KDE 4 use more desktop effects? Reading your message I would suggest that the KDE upgrade is at fault here. Or did you also upgrade the Intel graphics driver? Install a different DE or try with KDE 3 again to test the video and OpenGL stuff. Depending of your findings you should either contact the KDE guys or the Intel [1] guys afterward and leave the corresponding URL in a reply to this thread. Thanks, Paul [1] http://intellinuxgraphics.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Standard timing/modeline for 720p50 1280x...@50 Hz 50Hz
Am Donnerstag, den 21.01.2010, 18:38 +0100 schrieb t...@cs.fau.de: > On Thu, Jan 21, 2010 at 05:50:38PM +0100, Roland Scheidegger wrote: > > FWIW, after a bit of fiddling around these are the modelines I use (but > > I don't remember how I came up with them...), for a PT-AX200E. EDID > > looked poor to me too, aren't there still some unparsed (by Xorg) blocks? > > Modeline "1280x720_60" 74.50 1280 1404 1532 1664 720 723 728 748 > > -hsync +vsync > > Modeline "1280x720_50" 74.25 1280 1724 1800 1984 720 723 728 748 > > -hsync +vsync > > Thanks a lot, will try those. Just for the record. Did you get your projector working and what modeline did you use? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Getting key codes of remote controls handled in X just using evdev and not LIRC
Dear X.org folks, »In X you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys may generate keycodes that X doesn't recognize at all and the device does not support keymaps, or this would be easy to fix.« [1] Do you know if there exist a solution already for this problem? Most of the keys of the remote control (for example play, pause) do not generate an event in `xev` on my system. I read [2] and searched the Web for more information but did not find a solution not involving LIRC. At the and you will find the generated key codes by evdev.(?) Do you know of a way to just create a keymap(?) file to map those key codes to X events(?)? I am sorry to ask you, but the input system (scan codes, key codes, X mapping(?)) is still very complicated for me to understand. Thanks, Paul [1] http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_DT_USB_XS_Diversity#Using_evdev [2] http://lwn.net/Articles/364515/ $ /lib/udev/keymap -i /dev/input/event11 Press ESC to finish scan code: 0x00 key code: up scan code: 0x00 key code: right scan code: 0x00 key code: down scan code: 0x00 key code: left scan code: 0x00 key code: ok scan code: 0x00 key code: tv scan code: 0x00 key code: dvd scan code: 0x00 key code: video scan code: 0x00 key code: audio scan code: 0x00 key code: screen scan code: 0x00 key code: menu scan code: 0x00 key code: subtitle scan code: 0x00 key code: text scan code: 0x00 key code: delete scan code: 0x00 key code: 1 scan code: 0x00 key code: 2 scan code: 0x00 key code: 3 scan code: 0x00 key code: home scan code: 0x00 key code: 4 scan code: 0x00 key code: 5 scan code: 0x00 key code: 6 scan code: 0x00 key code: 7 scan code: 0x00 key code: 8 scan code: 0x00 key code: 9 scan code: 0x00 key code: refresh scan code: 0x00 key code: video scan code: 0x00 key code: 0 scan code: 0x00 key code: epg scan code: 0x00 key code: info scan code: 0x00 key code: back scan code: 0x00 key code: channelup scan code: 0x00 key code: channeldown scan code: 0x00 key code: play scan code: 0x00 key code: mute scan code: 0x00 key code: volumeup scan code: 0x00 key code: volumedown scan code: 0x00 key code: red scan code: 0x00 key code: green scan code: 0x00 key code: yellow scan code: 0x00 key code: blue scan code: 0x00 key code: record scan code: 0x00 key code: stop scan code: 0x00 key code: pause scan code: 0x00 key code: previous scan code: 0x00 key code: rewind scan code: 0x00 key code: fastforward scan code: 0x00 key code: next scan code: 0x00 key code: pause signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Getting key codes of remote controls handled in X just using evdev and not LIRC
Am Mittwoch, den 07.04.2010, 16:11 +1000 schrieb Peter Hutterer: […] > play and pause should work though, to name the two examples. they certainly > work well enough on my multimedia keyboards, so I don't see why the remote > should be much different. > For this issue, it's probably best to file a bug with all logs attached so > we can have a look at what's going wrong. Thank you for your reply. Is there a list of what logs are needed to debug such issues. • /var/log/Xorg.log … Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Getting key codes of remote controls handled in X just using evdev and not LIRC
Am Donnerstag, den 08.04.2010, 09:59 +1000 schrieb Peter Hutterer: > On Thu, Apr 08, 2010 at 01:51:28AM +0200, Paul Menzel wrote: > > Am Mittwoch, den 07.04.2010, 16:11 +1000 schrieb Peter Hutterer: > > > > […] > > > > > play and pause should work though, to name the two examples. they > > > certainly > > > work well enough on my multimedia keyboards, so I don't see why the remote > > > should be much different. > > > For this issue, it's probably best to file a bug with all logs attached so > > > we can have a look at what's going wrong. > > > > Thank you for your reply. Is there a list of what logs are needed to > > debug such issues. > > > > • /var/log/Xorg.log > > that's the most important one, xorg.conf is helpful if you have one and for > servers up to including 1.7 the output of lshal can be required too > (depending on the issue, not in your case). > Keyboard issues often need the keymap too (xkbcomp -xkb $DISPLAY -) > Finally, the output of evtest against the device file when you hit the keys > in question. I created a new report in Bugzilla as bug 27532 [1]. Please change the component or another field as you see fit. Thanks, Paul [1] https://bugs.freedesktop.org/show_bug.cgi?id=27532 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Re: multiple monitors configuration without proprietary driver
[Please do not top post or full quote.] Dear Alberto, Am Montag, den 12.04.2010, 11:28 +0100 schrieb Luis Alberto Padrón Hernández: […] > Here it is my last doubt. I would like one monitor to act like the main one > (with the gnome panels, and the login screen and so on) because it has more > qualitiy (the DVI one), but it just happen to be the other one which behaves > like this. I have tried to change orders in xorg.conf but nothing. Do you > know > how to change that? you can try to play with `xrandr`. Look for »primary« in `man xrandr`. That is just a guess though. I hope it will work. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Nvidia: Xorg displaying 50 Hz but uses 60 Hz
Dear X.org folks, there seems to be a bug where the wrong refresh rate is displayed to the one which is used [1][2]. Despite setting VertRefresh50.0 60 Hz is used when not setting an explicit modeline. Am Donnerstag, den 26.08.2010, 16:16 +0200 schrieb Thomas Hilber: > On Thu, Aug 26, 2010 at 03:06:51PM +0100, Tony Houghton wrote: > > Are you aware of the interaction between DynamicTwinView and XRandR? The > > no. But if Xorg.0.log tells me (in the bad case): > > (II) NVIDIA(0): Validating Mode "1920x1080": > (II) NVIDIA(0): 1920 x 1080 @ 50 Hz > (II) NVIDIA(0): For use as DFP backend. > (II) NVIDIA(0): Mode Source: EDID > (II) NVIDIA(0): Pixel Clock : 148.50 MHz > (II) NVIDIA(0): HRes, HSyncStart : 1920, 2448 > (II) NVIDIA(0): HSyncEnd, HTotal : 2492, 2640 > (II) NVIDIA(0): VRes, VSyncStart : 1080, 1084 > (II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125 > (II) NVIDIA(0): H/V Polarity : +/+ > (II) NVIDIA(0): Mode is valid. > [...] > (II) NVIDIA(0): "1920x1080_50" : 1920 x 1080 @ 50.0 Hz (from: EDID) > [...] > (II) NVIDIA(0): Config Options in the README. > (II) NVIDIA(0): Setting mode "1920x1080_50" > > and it uses a 60Hz modeline though this is clearly a Xserver bug for me. Is that a bug in the X server or of the Nvidia proprietary driver? Thanks, Paul [1] http://linuxtv.org/pipermail/vdr/2010-August/023448.html [2] http://linuxtv.org/pipermail/vdr/2010-August/023455.html signature.asc Description: This is a digitally signed message part ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
