[opensuse] Screen Resolution
I have installed Suse 11.4 on my new laptop, an Acer Aspire 7551G. According to Acer's product description the computer has a WSXGA Display with 1600x900 pixels. My X runs well, but I have the impression that it uses a smaller resolution than 1600x900. So I have two questions: 1. How can I determine the resolution used by my X? 2. In case it is lower, how can I force X to use 1600x900 px? Thanks advance for you help and best regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/04/16 08:46 (GMT+0200) Wolfgang Mueller composed:
I have installed Suse 11.4 on my new laptop, an Acer Aspire 7551G. According to Acer's product description the computer has a WSXGA Display with 1600x900 pixels. My X runs well, but I have the impression that it uses a smaller resolution than 1600x900.
What size is that screen?
So I have two questions:
1. How can I determine the resolution used by my X?
1-Load in a web browser http://fm.no-ip.com/Auth/dpi-screen-window.html and/or 2-Open KInfoCenter -> Xserver and/or 3-'xdpyinfo | grep dime'
2. In case it is lower, how can I force X to use 1600x900 px?
Really hard to answer that without knowing the output of 'lspci | grep vga' and/or output from 'hwinfo --gfxcard'. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Apr 16, 2011 at 09:04, Felix Miata wrote:
On 2011/04/16 08:46 (GMT+0200) Wolfgang Mueller composed:
I have installed Suse 11.4 on my new laptop, an Acer Aspire 7551G. According to Acer's product description the computer has a WSXGA Display with 1600x900 pixels. My X runs well, but I have the impression that it uses a smaller resolution than 1600x900.
What size is that screen?
It's a 17.3 inch screen that has a native resolution of 1600x900.
So I have two questions:
1. How can I determine the resolution used by my X?
1-Load in a web browser http://fm.no-ip.com/Auth/dpi-screen-window.html and/or 2-Open KInfoCenter -> Xserver and/or 3-'xdpyinfo | grep dime'
2. In case it is lower, how can I force X to use 1600x900 px?
Really hard to answer that without knowing the output of 'lspci | grep vga' and/or output from 'hwinfo --gfxcard'.
Why start so complex? Can't we just start simple, and use the tools provided by the desktop manager? Or have I missed something? Open the Display configuration and look at what it's set to. In KDE4 for example go to: KMenu > Configure Desktop > Hardware > Display and Monitor > Size & Orientation What does it say there? Does it say 1600x900? If not, can you set it to the right resolution? Gnome's path is similar, and the result should be the same... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/16/11 09:19, C wrote:
On Sat, Apr 16, 2011 at 09:04, Felix Miata wrote:
On 2011/04/16 08:46 (GMT+0200) Wolfgang Mueller composed:
I have installed Suse 11.4 on my new laptop, an Acer Aspire 7551G. According to Acer's product description the computer has a WSXGA Display with 1600x900 pixels. My X runs well, but I have the impression that it uses a smaller resolution than 1600x900.
What size is that screen?
It's a 17.3 inch screen that has a native resolution of 1600x900.
That's correct.
So I have two questions:
1. How can I determine the resolution used by my X?
1-Load in a web browser http://fm.no-ip.com/Auth/dpi-screen-window.html and/or 2-Open KInfoCenter -> Xserver and/or 3-'xdpyinfo | grep dime'
2. In case it is lower, how can I force X to use 1600x900 px?
Really hard to answer that without knowing the output of 'lspci | grep vga' and/or output from 'hwinfo --gfxcard'.
Why start so complex? Can't we just start simple, and use the tools provided by the desktop manager? Or have I missed something? Open the Display configuration and look at what it's set to. In KDE4 for example go to:
KMenu> Configure Desktop> Hardware> Display and Monitor> Size& Orientation
What does it say there? Does it say 1600x900? If not, can you set it to the right resolution?
Following your advise, I found a size of 1024x768 in "Size & Orientation". The tool gives me the choice between this value and "Disabled", but 1600x900 is not available. So I selected "Disabled" (whatever that means), but that did not help. After closing the tool and recalling it, the old value of 1024x768 appeared again. Now, since SaX2 has been abolished, there is obviously no way any more to set up the correct size. Obviously, Suse is no more reliable. Perhaps, I should try a different distro. Thank you very much, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Apr 16, 2011 at 10:43, Wolfgang Mueller wrote:
Following your advise, I found a size of 1024x768 in "Size & Orientation". The tool gives me the choice between this value and "Disabled", but 1600x900 is not available. So I selected "Disabled" (whatever that means), but that did not help. After closing the tool and recalling it, the old value of 1024x768 appeared again.
Now, since SaX2 has been abolished, there is obviously no way any more to set up the correct size. Obviously, Suse is no more reliable. Perhaps, I should try a different distro.
Don't discount Felix's advice... I was just suggesting we start simple... sometimes the solution is simple. Another distro won't help you. ALL top distros will give you similar results because they all use the same autodetect for X resolutions. If it fails in openSUSE, it's quite likely to fail in the rest. You cannot claim wildly that "obviously Suse is no more reliable" because this is not an openSUSE specific issue... it's an issue with X not being detected correctly.. this is NOT something unique to openSUSE. What video card does your laptop have? What video driver are you using? Generally if you've only got 1024x768 then the install routine didn't detect something correctly Felix asked for the extra info you have to provide to take this to the next step. My guess is something went wrong in the install... that laptop should generally work fine with whatever Linux you install on it. SAX2 did a great job back when X wasn't able to detect things.. now it's generally redundant because xorg.conf is depricated.... as in it's obsolete. SAX2 was created because there was nothing at the time to set up X.. now there is.... Yes I know, there are cases where an xorg.conf is still needed, but they are uncommon. I honestly don't think a SAX2 solution is right in this case (of course I could be wrong)... I'd guess that once it's sorted, the X autodetect will do its job and your X resolutions will be what they should be. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday, April 16, 2011 03:57 C wrote:
On Sat, Apr 16, 2011 at 10:43, Wolfgang Mueller wrote:
Following your advise, I found a size of 1024x768 in "Size & Orientation". The tool gives me the choice between this value and "Disabled", but 1600x900 is not available. So I selected "Disabled" (whatever that means), but that did not help. After closing the tool and recalling it, the old value of 1024x768 appeared again.
Now, since SaX2 has been abolished, there is obviously no way any more to set up the correct size. Obviously, Suse is no more reliable. Perhaps, I should try a different distro.
<snip>
SAX2 did a great job back when X wasn't able to detect things.. now it's generally redundant because xorg.conf is depricated.... as in it's obsolete. SAX2 was created because there was nothing at the time to set up X.. now there is
You say "now there is" something that's used other than SaX2...but what is it? That's the main point of the OP's post...SaX2 could be called any time one wanted. It worked and was pretty easy to use. What took SaX2's place? Is there an actual name for the app or what? What does one call up now to do what the OP is trying to get done? -- "Properly read, the Bible is the most potent force for atheism ever conceived." -Isaac Asimov -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Apr 16, 2011 at 12:11, Insomniac wrote:
SAX2 did a great job back when X wasn't able to detect things.. now it's generally redundant because xorg.conf is depricated.... as in it's obsolete. SAX2 was created because there was nothing at the time to set up X.. now there is
You say "now there is" something that's used other than SaX2...but what is it? That's the main point of the OP's post...SaX2 could be called any time one wanted. It worked and was pretty easy to use. What took SaX2's place? Is there an actual name for the app or what? What does one call up now to do what the OP is trying to get done?
Typo on my part. The "now there is" wasn't supposed to be there... it was a bit of another train of thought I deleted... and I missed that bit. There is a GSoC that is looking into a SAX3 (I think.. I read about it, but I don't know its status), but... until it's complete, I wouldn't bank on it. As for what replaces SAX2... the autodetect in X replaces it. There is no need for an app like SAX2 in most cases. On most hardware, the display is detected correctly and all display modes are available. SAX2 is simply redundant... it was used to set up a working xorg.conf file when there was nothing else in place to do so. Yes you could call it when needed - back when X didn't autodetect your display and video hardware... back when if you didn't cobble together an xorg.conf, either by yourself, or using SAX2, you had no hope of getting a working X environment. Now xorg.conf is deprecated... so SAX2 is no longer useful... no longer maintained... and no longer included. Now before someone pops up and says yah but my monitor yadda yadda, I didn't say all... I said most. Everyone here has acknowledged that there are "corner cases" where X fails to autodetect... either because of an explicit bug - which from what I read in this thread is highly likely to be the OP's problem, or because the hardware is unusual/odd or has special case needs. These special cases are NOT the majority. These are uncommon... very uncommon. The vast majority of displays - even hardware like my Toshiba TV - are autodetected correctly, and there is nothing else to do. Where it does fail, submit a bug report... help get it fixed so that next time around it does autodetect the unusual hardware correctly. If the community sees a need for reviving SAX2, then they probably can do so. No one is stopping them. When SAX2 was discontinued, there was a call put out for maintainers, and the silence was deafening. No one was interested in maintaining it... so it was dropped. You can do some manual display tweaking using xrandr - there have been a few threads about this here on the mailing list. C. PS: just an a related aside... the autodetect in X detects and configures my older Toshiba LCD TV without any hassle (set to a native resolution of 1366x768). Windows 7 can't set it up correctly at all regardless of using the latest video card drivers or using the Windows 7 generic video drivers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
C said the following on 04/16/2011 11:39 AM:
Now before someone pops up and says yah but my monitor yadda yadda, I didn't say all... I said most. Everyone here has acknowledged that there are "corner cases" where X fails to autodetect... either because of an explicit bug - which from what I read in this thread is highly likely to be the OP's problem, or because the hardware is unusual/odd or has special case needs. These special cases are NOT the majority. These are uncommon... very uncommon.
However, like "Man Bites Dog" and other rate events .... earthquakes, tsunamis ... Royal weddings ... they are more news-worthy and hence get more face-time than boring old common place things like tornadoes in Texas or technology that does what its supposed to do. -- "...Then anyone who leaves behind him a written manual, and likewise anyone who receives it, in the belief that such writing will be clear and certain, must be exceedingly simple-minded..." -- Plato, _Phaedrus_ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/04/16 17:39 (GMT+0200) C composed:
Now before someone pops up and says yah but my monitor yadda yadda, I didn't say all... I said most. Everyone here has acknowledged that there are "corner cases" where X fails to autodetect... either because of an explicit bug - which from what I read in this thread is highly likely to be the OP's problem, or because the hardware is unusual/odd or has special case needs. These special cases are NOT the majority. These are uncommon... very uncommon.
They're more common than you seem to think. http://fm.no-ip.com/Tmp/Hardware/Display/ represents 14 displays (14 out of 16 functional in the building): 1 Vizio HDTV 1 Viewsonic 1400x1050 LCD 1 Dell shadowmask 1 Dell 1600x1200 LCD 1 Dell 1400x1050 laptop 3 Dell Trinitrons 3 IBM Trinitrons 1 Sony Trinitron 2 NEC shadowmasks 1 NEC, the laptop, and all 3 Dell Trinitrons, 5 of 14 total units, have no EDID. A few of those datasets represent additional EDID failures, but those were all corrected by a cable change. IOW, not only can a display itself have bad EDID, but a cable problem also can cause EDID failure. Not all cables with 15 pins showing have wires connecting all that need connecting. Some don't even have pins in all 15 positions. Trinitrons normally deteriorate with age, but Sony software can be used to adjust them to extend their lives. Using that software apparently can invalidate the EDID checksum. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Mueller <wm@ariannuccia.de> writes:
Following your advise, I found a size of 1024x768 in "Size & Orientation". The tool gives me the choice between this value and "Disabled", but 1600x900 is not available. So I selected "Disabled" (whatever that means), but that did not help. After closing the tool and recalling it, the old value of 1024x768 appeared again.
You have been bitten by the same KMS bug as I did. Please see this post: http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-04/msg00431.html So far the only solution I can find (tried configuring X manually) is to use xrandr to add and set the mode. Your should: 1. Run: ,---- | hwinfo --monitor | grep 1600x900@ `---- to find the Hz that that mode runs at. 2. Generate a modeline with cvt: ,---- | cvt 1600 900 <your_Hz> `---- 3. Now put this in your /etc/X11/xinit/xinitrc.common: ,---- | /usr/bin/xrandr --newmode <modeline> | /usr/bin/xrandr --addmode VGA1 <mode name> | /usr/bin/xrandr --output VGA1 --mode <mode name> `---- for example, this is what I have in mine: ,---- | /usr/bin/xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync | /usr/bin/xrandr --addmode VGA1 1680x1050_60.00 | /usr/bin/xrandr --output VGA1 --mode 1680x1050_60.00 `---- I presume that your display is vga1, if not, you can find out with: ,---- | xrandr --verbose `---- Charles -- Avoid the Gates of Hell. Use Linux (Unknown source)
On 04/16/11 12:24, Charles Philip Chan wrote:
Wolfgang Mueller<wm@ariannuccia.de> writes:
Following your advise, I found a size of 1024x768 in "Size& Orientation". The tool gives me the choice between this value and "Disabled", but 1600x900 is not available. So I selected "Disabled" (whatever that means), but that did not help. After closing the tool and recalling it, the old value of 1024x768 appeared again.
You have been bitten by the same KMS bug as I did. Please see this post:
http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-04/msg00431.html
So far the only solution I can find (tried configuring X manually) is to use xrandr to add and set the mode. Your should:
1. Run:
,---- | hwinfo --monitor | grep 1600x900@ `----
to find the Hz that that mode runs at.
2. Generate a modeline with cvt:
,---- | cvt 1600 900<your_Hz> `----
3. Now put this in your /etc/X11/xinit/xinitrc.common:
,---- | /usr/bin/xrandr --newmode<modeline> | /usr/bin/xrandr --addmode VGA1<mode name> | /usr/bin/xrandr --output VGA1 --mode<mode name> `----
for example, this is what I have in mine:
,---- | /usr/bin/xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync | /usr/bin/xrandr --addmode VGA1 1680x1050_60.00 | /usr/bin/xrandr --output VGA1 --mode 1680x1050_60.00 `----
I presume that your display is vga1, if not, you can find out with:
,---- | xrandr --verbose `----
This last statement did not give me any information on the display type, but produced the following error Message: ,---- | xrandr: Failed to get size of gamma for output default ,---- But anyway, having no different chance, I assumed VGA1 to be the correct display type. So, I invoked hwinfo and cvt, using the values produced by these programs for adding the following lines at the head of /etc/X11/xinit/xinitrc.common: ,---- | /usr/bin/xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 \ 2112 900 903 908 934 -hsync +vsync | /usr/bin/xrandr --addmode VGA1 1600x900_60.00 | /usr/bin/xrandr --output VGA1 --mode 1600x900_60.00 ,---- Then, pressing ALT CTRL F1, I went to a black screen where I dropped X by typing '/etc/init.d/xdm stop'. Then I restarted X, typing '/etc/init.d/xdm start'. After having logged in again, I noticed that nothing had changed, i.e the screen size was still 1024x768. Now, I moved the additional lines, i.e. those beginning with '/usr/bin/xrandr', to the end of /etc/X11/xinit/xinitrc.common, went to a black screen and dropped and restarted xdm. Again no effect. After these failures I replaced VGA1 by WSXGA in both versions of my /etc/X11/xinit/xinitrc.common, i.e. at the beginning and at the end and repeated the boring procedures described above: No effect again. Now, I am tired... Thanks a lot and best regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/16/11 17:10, I wrote:
On 04/16/11 12:24, Charles Philip Chan wrote:
[...]
I presume that your display is vga1, if not, you can find out with: ,---- | xrandr --verbose `----
This last statement did not give me any information on the display type, but produced the following error Message: ,---- | xrandr: Failed to get size of gamma for output default ,----
Charles, I forgot to mention that 'xrandr --verbose' does not only produce this error message, but also some interesting output: ,---- | Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 | default connected 1024x768+0+0 (0xe9) normal (normal) 0mm x 0mm | Identifier: 0xe8 | Timestamp: 33972437 | Subpixel: unknown | Clones: | CRTC: 0 | CRTCs: 0 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | 1024x768 (0xe9) 59.8MHz *current | h: width 1024 start 0 end 0 total 1024 skew 0 clock 58.4KHz | v: height 768 start 0 end 0 total 768 clock 76.0Hz | 1600x900_60.00 (0xea) 118.2MHz | h: width 1600 start 1696 end 1856 total 2112 skew 0 clock 56.0KHz | v: height 900 start 903 end 908 total 934 clock 59.9Hz `---- So, it can be seen that the 1600x900 60 Hz format is known to the system. Now, the only problem is making the system use it. Any idea? Bye, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/04/16 18:32 (GMT+0200) Wolfgang Mueller composed:
Charles, I forgot to mention that 'xrandr --verbose' does not only produce this error message, but also some interesting output:
,---- | Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 | default connected 1024x768+0+0 (0xe9) normal (normal) 0mm x 0mm | Identifier: 0xe8 | Timestamp: 33972437 | Subpixel: unknown | Clones: | CRTC: 0 | CRTCs: 0 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | 1024x768 (0xe9) 59.8MHz *current | h: width 1024 start 0 end 0 total 1024 skew 0 clock 58.4KHz | v: height 768 start 0 end 0 total 768 clock 76.0Hz | 1600x900_60.00 (0xea) 118.2MHz | h: width 1600 start 1696 end 1856 total 2112 skew 0 clock 56.0KHz | v: height 900 start 903 end 908 total 934 clock 59.9Hz
So, it can be seen that the 1600x900 60 Hz format is known to the system. Now, the only problem is making the system use it.
Your later post with Xorg.0.log points to your problem. [ 70.829] et seq X is using the VESA driver, thinking you have a Cirrus gfxchip. AFAIK, there are no widescreen modes available using the VESA driver. Could be ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] is too new to be covered by FOSS ati/radeon drivers. Maybe it's supported by the proprietary ATI driver. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Mueller <wm@ariannuccia.de> writes:
This last statement did not give me any information on the display type, but produced the following error Message: ,---- | xrandr: Failed to get size of gamma for output default ,----
Strange, you should be getting something like this: ,----[ Output of "xrandr --verbose ] | Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 | VGA1 connected 1680x1050+0+0 (0xb4) normal (normal left inverted right x axis y axis) 0mm x 0mm | Identifier: 0x41 | Timestamp: 35222446 | Subpixel: unknown | Gamma: 1.0:1.0:1.0 | Brightness: 1.0 | Clones: | CRTC: 0 | CRTCs: 0 1 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | 1024x768 (0x46) 65.0MHz -HSync -VSync | h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz | v: height 768 start 771 end 777 total 806 clock 60.0Hz | 800x600 (0x47) 40.0MHz +HSync +VSync | h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz | v: height 600 start 601 end 605 total 628 clock 60.3Hz | 800x600 (0x48) 36.0MHz +HSync +VSync | h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz | v: height 600 start 601 end 603 total 625 clock 56.2Hz | 848x480 (0x49) 33.8MHz +HSync +VSync | h: width 848 start 864 end 976 total 1088 skew 0 clock 31.0KHz | v: height 480 start 486 end 494 total 517 clock 60.0Hz | 640x480 (0x4a) 25.2MHz -HSync -VSync | h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz | v: height 480 start 489 end 492 total 525 clock 59.9Hz | 640x480 (0x4b) 25.2MHz -HSync -VSync | h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz | v: height 480 start 490 end 492 total 525 clock 59.9Hz | 1680x1050_60.00 (0xb4) 146.2MHz -HSync +VSync *current | h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.3KHz | v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz | HDMI1 disconnected (normal left inverted right x axis y axis) | Identifier: 0x42 | Timestamp: 35222446 | Subpixel: unknown | Clones: | CRTCs: 0 1 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | force_audio: 0 (0x00000000) range: (-1,1) | DP1 disconnected (normal left inverted right x axis y axis) | Identifier: 0x43 | Timestamp: 35222446 | Subpixel: unknown | Clones: | CRTCs: 0 1 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | force_audio: 0 (0x00000000) range: (-1,1) | HDMI2 disconnected (normal left inverted right x axis y axis) | Identifier: 0x44 | Timestamp: 35222446 | Subpixel: unknown | Clones: | CRTCs: 0 1 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | force_audio: 0 (0x00000000) range: (-1,1) | DP2 disconnected (normal left inverted right x axis y axis) | Identifier: 0x45 | Timestamp: 35222446 | Subpixel: unknown | Clones: | CRTCs: 0 1 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | force_audio: 0 (0x00000000) range: (-1,1) `---- What is the output of: ,---- | lspci -nn | grep VGA `---- and post your Xorg.0.log.
,---- | /usr/bin/xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync | /usr/bin/xrandr --addmode VGA1 1600x900_60.00 | /usr/bin/xrandr --output VGA1 --mode 1600x900_60.00 ,----
What errors do you see if you run the commands in an xterm? Charles -- "A word to the wise: a credentials dicksize war is usually a bad idea on the net." (David Parsons in c.o.l.development.system, about coding in C.)
On 04/16/11 22:07, Charles Philip Chan wrote:
Wolfgang Mueller<wm@ariannuccia.de> writes:
This last statement did not give me any information on the display type, but produced the following error Message: ,---- | xrandr: Failed to get size of gamma for output default ,---- Strange, you should be getting something like this:
,----[ Output of "xrandr --verbose ] | Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 | VGA1 connected 1680x1050+0+0 (0xb4) normal (normal left inverted right x axis y axis) 0mm x 0mm | Identifier: 0x41
[...] `----
Apart from the first line, which is an error message, my output of "xrandr --verbose" is similar: ,---- | xrandr: Failed to get size of gamma for output default | Screen 0: minimum 800 x 600, current 1152 x 864, maximum 1152 x 864 | default connected 1152x864+0+0 (0x10a) normal (normal) 0mm x 0mm | Identifier: 0x109 | Timestamp: 70523 | Subpixel: horizontal rgb | Clones: | CRTC: 0 | CRTCs: 0 | Transform: 1.000000 0.000000 0.000000 | 0.000000 1.000000 0.000000 | 0.000000 0.000000 1.000000 | filter: | 1152x864 (0x10a) 0.0MHz *current | h: width 1152 start 0 end 0 total 1152 skew 0 clock 0.0KHz | v: height 864 start 0 end 0 total 864 clock 0.0Hz | 1024x768 (0x10b) 0.0MHz | h: width 1024 start 0 end 0 total 1024 skew 0 clock 0.0KHz | v: height 768 start 0 end 0 total 768 clock 0.0Hz | 800x600 (0x10c) 0.0MHz | h: width 800 start 0 end 0 total 800 skew 0 clock 0.0KHz | v: height 600 start 0 end 0 total 600 clock 0.0Hz `---- Note that I had removed the Boot Option 'vga = 0x317'. This activated three sizes, 1152x864, 1024x768, and 800x600, whereas before there was only 1024x768. X now starts with 1152x864. I played a little bit with other numbers of Boot Option. When I specified a wrong number, a list appeared with a lot of different sizes and color depths, the largest of which was 1152x864/32. Some types were VGA, others VESA, But my 1600x900 did not appear. All the sizes offered had a width-to-heights ratio of 4:3, never of 16:9.
What is the output of:
,---- | lspci -nn | grep VGA `----
,---- | 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] `----
and post your Xorg.0.log.
See attachment.
,---- | /usr/bin/xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync | /usr/bin/xrandr --addmode VGA1 1600x900_60.00 | /usr/bin/xrandr --output VGA1 --mode 1600x900_60.00 ,---- What errors do you see if you run the commands in an xterm?
'/usr/bin/xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync' produces: ,---- | /usr/bin/xrandr: Failed to get size of gamma for output default `---- '/usr/bin/xrandr --addmode VGA1 1600x900_60.00' produces: ,---- | /usr/bin/xrandr: Failed to get size of gamma for output default | /usr/bin/xrandr: cannot find output "VGA1" `---- '/usr/bin/xrandr --output VGA1 --mode 1600x900_60.0' produces: ,---- | /usr/bin/xrandr: Failed to get size of gamma for output default | warning: output VGA1 not found; ignoring `---- Thanks a lot again, Wolfgang
Wolfgang Mueller <wm@ariannuccia.de> writes:
,---- | 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] `----
[ 70.848] (II) VESA(1): VESA VBE OEM Product Rev: 01.00 [ 70.865] (II) VESA(1): Creating default Display subsection in Screen section "vesa" for depth/fbbpp 24/32 [ 70.865] (==) VESA(1): Depth 24, (--) framebuffer bpp 32 [ 70.865] (==) VESA(1): RGB weight 888 [ 70.865] (==) VESA(1): Default visual is TrueColor [ 70.865] (==) VESA(1): Using gamma correction (1.0, 1.0, 1.0)
You are using the wrong driver. You should be using the radeon driver. http://wiki.x.org/wiki/radeon Try uncommenting the line in 50-device.conf (also see below). If that doesn't work you can try the package xorg-x11-driver-video-radeonhd: http://wiki.x.org/wiki/radeonhd#SupportedHardware I also found this: ,---- | Identifier "Default Device" | | #Driver "radeon" | | ## Required magic for radeon/radeonhd drivers; output name | ## (here: "DVI-0") can be figured out via 'xrandr -q' | #Option "monitor-DVI-0" "Default Monitor `---- in /etc/X11/xorg.conf.d/50-device.conf You might need to follow the instructions here. I have no experience with radeon. Charles -- The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first. (Arno Schaefer's .sig)
Charles Philip Chan <cpchan@bell.net> writes:
Wolfgang Mueller <wm@ariannuccia.de> writes:
,---- | 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] `----
Oops, looking further at the radeon page: ,---- | Driver for ATI/AMD Radeon based video chips, everything from Radeon 7000 | to Radeon HD 5890 series. | ^^^^^^^^^^^^^^ `---- you might need the radeonHD package after all. However, if doesn't seem to support KMS, so you might need to configure xorg manually after all. Charles -- "All language designers are arrogant. Goes with the territory..." (By Larry Wall)
On 04/17/11 09:48, Charles Philip Chan wrote:
Wolfgang Mueller<wm@ariannuccia.de> writes:
[...]
You are using the wrong driver. You should be using the radeon driver.
Try uncommenting the line in 50-device.conf (also see below). If that doesn't work you can try the package xorg-x11-driver-video-radeonhd:
Uncommenting '#Driver "radeon"' in 50-device.conf did not work, of course. So I went to http://wiki.x.org/wiki/radeon where I found a link to http://cgit.freedesktop.org/xorg/driver/xf86-video-ati which contains list of available drivers. I downloaded the most recent one, i.e. xf86-video-ati-6.14.1.tar.gz. After unpacking this file, I found, among other files, a script called autogen.sh which has to be executed for installation: ,---- | #! /bin/sh | srcdir=`dirname $0` | test -z "$srcdir" && srcdir=. | ORIGDIR=`pwd` | cd $srcdir | autoreconf -v --install || exit 1 | cd $ORIGDIR || exit $? | $srcdir/configure --enable-maintainer-mode "$@" `---- But execution failed because autoreconf, invoked in the third last line, is not supplied.
I also found this:
,---- | Identifier "Default Device" | | #Driver "radeon" | | ## Required magic for radeon/radeonhd drivers; output name | ## (here: "DVI-0") can be figured out via 'xrandr -q' | #Option "monitor-DVI-0" "Default Monitor `----
in /etc/X11/xorg.conf.d/50-device.conf
As already mentioned above, uncommenting '#Driver "radeon"' did produce any effect. Now, I feel I bothered you (and myself) too much. So, I decided to renounce further attempts. Being able to work very well with the resolution of 1152x864, it' no problem for me to wait for a new version of OpenSuse, 11.5 or 12.0 or whatever else it may be. Anyway, I owe you a lot of gratitude: thank you very, very much, Charles! Bye, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Mueller <wm@ariannuccia.de> writes:
After unpacking this file, I found, among other files, a script called autogen.sh which has to be executed for installation:
Oh, you are trying to compile the source.
,---- | #! /bin/sh | srcdir=`dirname $0` | test -z "$srcdir" && srcdir=. | ORIGDIR=`pwd` | cd $srcdir | autoreconf -v --install || exit 1 | cd $ORIGDIR || exit $? | $srcdir/configure --enable-maintainer-mode "$@" `----
But execution failed because autoreconf, invoked in the third last line, is not supplied.
Yes, this must be of interest to you: ,---- | bug fix for r6xx/r7xx UMS `---- autoreconf is part of the autoconf package. Which OpenSUSE are you using? 64bit or 32bit? If you are using 64bit, I can supply you an RPM right now. It only took a minute to compile.
I owe you a lot of gratitude: thank you very, very much, Charles!
No problem. Charles -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie)
On 04/17/11 13:43, Charles Philip Chan wrote:
Wolfgang Mueller<wm@ariannuccia.de> writes: [...]
Yes, this must be of interest to you:
,---- | bug fix for r6xx/r7xx UMS `----
autoreconf is part of the autoconf package. Which OpenSUSE are you using? 64bit or 32bit? If you are using 64bit, I can supply you an RPM right now. It only took a minute to compile.
Meanwhile I have installed the autoconf package from the Suse CD. But autogen.sh does not run anyway because it complains not to find aclocal: ,---- | Can't exec "aclocal": No such file or directory at \ | /usr/share/autoconf/Autom4te/FileUtils.pm line 326. `---- So I would be grateful if you sent me your 64bit RPM. But if that does not help, we should abandon definitely the attempts to reconfigure my X. Thanks in advance, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Mueller <wm@ariannuccia.de> writes:
,---- | Can't exec "aclocal": No such file or directory at \ | /usr/share/autoconf/Autom4te/FileUtils.pm line 326. `----
FYI, aclocal is in the aclocal package.
So I would be grateful if you sent me your 64bit RPM. But if that does not help, we should abandon definitely the attempts to reconfigure my X.
Please send me an email with your email address to cpchan777@gmail.com. I am reading this list through gmane. Charles -- "Besides, I think [Slackware] sounds better than 'Microsoft,' don't you?" (By Patrick Volkerding)
On 04/16/11 09:04, Felix Miata wrote:
On 2011/04/16 08:46 (GMT+0200) Wolfgang Mueller composed:
I have installed Suse 11.4 on my new laptop, an Acer Aspire 7551G. According to Acer's product description the computer has a WSXGA Display with 1600x900 pixels. My X runs well, but I have the impression that it uses a smaller resolution than 1600x900.
What size is that screen?
The size of my screen is 17.3".
So I have two questions:
1. How can I determine the resolution used by my X?
1-Load in a web browser http://fm.no-ip.com/Auth/dpi-screen-window.html and/or 2-Open KInfoCenter -> Xserver and/or 3-'xdpyinfo | grep dime'
2. In case it is lower, how can I force X to use 1600x900 px?
Really hard to answer that without knowing the output of 'lspci | grep vga' and/or output from 'hwinfo --gfxcard'.
"lspci | grep vga" produces no result, but "lspci | grep VGA" shows this line: 02:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour \ [AMD Radeon HD 6470M] And here follows the response of "hwinfo --gfxcard" "25: PCI 200.0: 0300 VGA compatible controller (VGA) [Created at pci.318] Unique ID: B35A.mAJbyLlkeA6 Parent ID: _Znp.XY83zNTsW5E SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: graphics card Model: "ATI VGA compatible controller" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x6760 SubVendor: pci 0x1025 "Acer Incorporated [ALI]" SubDevice: pci 0x0388 Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) Memory Range: 0xd0000000-0xd001ffff (rw,non-prefetchable) I/O Ports: 0x9000-0x9fff (rw) Memory Range: 0xd0040000-0xd005ffff (ro,non-prefetchable,disabled) IRQ: 5 (no events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00001002d00006760sv00001025sd00000388bc03sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #8 (PCI bridge) Primary display adapter: #25 Moreover I list the contents of /etc/X11/xorg.conf Section "Device" Identifier "vboxvideo" Driver "vboxvideo" EndSection Section "Screen" Identifier "vboxvideo" Device "vboxvideo" EndSection Section "Device" Identifier "vmware" Driver "vmware" EndSection Section "Screen" Identifier "vmware" Device "vmware" EndSection Section "Device" Identifier "cirrus" Driver "cirrus" EndSection Section "Screen" Identifier "cirrus" Device "cirrus" EndSection Section "Device" Identifier "fbdev" Driver "fbdev" EndSection Section "Screen" Identifier "fbdev" Device "fbdev" EndSection Section "Device" Identifier "vesa" Driver "vesa" EndSection Section "Screen" Identifier "vesa" Device "vesa" EndSection Section "ServerLayout" Identifier "Layout" Screen "vboxvideo" Screen "vmware" Screen "cirrus" Screen "fbdev" Screen "vesa" EndSection I hope these data are helpful. Bye, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anton Aylward -
C -
Charles Philip Chan -
Felix Miata -
Insomniac -
Wolfgang Mueller