Summary: | No apropiate resolution | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | erasmo <erasmorg> | ||||||||||
Component: | Driver/intel | Assignee: | ykzhao <yakui.zhao> | ||||||||||
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
Severity: | major | ||||||||||||
Priority: | medium | Keywords: | NEEDINFO | ||||||||||
Version: | 6.8.1 | ||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
erasmo
2010-02-06 12:40:28 UTC
Created attachment 33132 [details]
xorg, xrandr info system
(In reply to comment #0) > What more info do you need ? full Xorg log (as text, not pdf). # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # Note that some configuration settings that could be done previously # in this file, now are automatically configured by the server and settings # here are ignored. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" EndSection erasmo@erasmo-desktop:~$ xrandr Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096 VGA1 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 800x600 60.3* 640x480 59.9 Created attachment 33186 [details]
XORG.0.LOG
(In reply to comment #4) > Created an attachment (id=33186) [details] > XORG.0.LOG > Will you please try the latest kernel(2.6.33-rc7) and add the boot option of "drm.debug=0x04"? After the system is booted, please attach the output of dmesg. thanks. Yakui (In reply to comment #5) > (In reply to comment #4) > > Created an attachment (id=33186) [details] [details] > > XORG.0.LOG > > > > Will you please try the latest kernel(2.6.33-rc7) and add the boot option of > "drm.debug=0x04"? After the system is booted, please attach the output of > dmesg. > > thanks. > Yakui > Dear Yakui.. My system is update and the lastest kernel for me is 2.6.31.19, how I get the lastest kernel.. I am not an advanced user.. How I add the boot option ? Where I can find the file dmesg ? > My system is update and the lastest kernel for me is 2.6.31.19, how I get the > lastest kernel.. > I am not an advanced user.. You can download the kernel from www.kernel.org and then compile it by yourself. The linux-2.6.32.8 stable kernel is also ok. > How I add the boot option ? You can edit the file of /boot/grub/grub.conf and add the boot option of "drm.debug=0x04" to it. Of course on some boxes the file name is /etc/grub/menu.lst. > Where I can find the file dmesg ? After the system is booted, use the command of "dmesg >dmesg_after" to get the corresponding dmesg log. thanks. > Created attachment 33510 [details]
dmesg log
Just I added the dmesg log, is correct according to your directions ? (In reply to comment #7) > > My system is update and the lastest kernel for me is 2.6.31.19, how I get the > > lastest kernel.. > > I am not an advanced user.. > > You can download the kernel from www.kernel.org and then compile it by > yourself. The linux-2.6.32.8 stable kernel is also ok. > > > How I add the boot option ? > > You can edit the file of /boot/grub/grub.conf and add the boot option of > "drm.debug=0x04" to it. Of course on some boxes the file name is > /etc/grub/menu.lst. > > > Where I can find the file dmesg ? > > After the system is booted, use the command of "dmesg >dmesg_after" to get the > corresponding dmesg log. > > thanks. > > > (In reply to comment #9) Sorry for the late response. You attach the correct dmesg. But from the dmesg log it seems that it complains the following messages: >EDID checksum is invalid, remainder is 244 In such case the EDID is discarded and i915 driver won't parse the display mode from it. Do you have an opportunity to try this monitor on another box and see whether the proper resolution is selected?(1280x1024) Do you have an opportunity to try antoher monitor on this box and see whether the proper resolution is selected? Thanks. Ok, sorry for the delay, it because just I needed to get other computer and other monitor, The other computer with my monitor the resolution is 800 x 600 (wrong) My computer with the other monitor load OK in resolution.. What it means ??? (In reply to comment #10) > (In reply to comment #9) > Sorry for the late response. You attach the correct dmesg. But from the dmesg > log it seems that it complains the following messages: > >EDID checksum is invalid, remainder is 244 > > In such case the EDID is discarded and i915 driver won't parse the display > mode from it. > > Do you have an opportunity to try this monitor on another box and see whether > the proper resolution is selected?(1280x1024) > > Do you have an opportunity to try antoher monitor on this box and see whether > the proper resolution is selected? > > Thanks. > (In reply to comment #11) > Ok, sorry for the delay, it because just I needed to get other computer and > other monitor, > > The other computer with my monitor the resolution is 800 x 600 (wrong) > My computer with the other monitor load OK in resolution.. Thanks for the response. It seems that the system can work well if another monitor is used. But there is no appropriate resolution when your monitor is used. Now it is very clear that the issue is related with the incorrect EDID on your monitor. As the incorrect is discarded, the driver won't parse the display mode contained in EDID any more. Instead it will add some default modes(for example: 800x600, 1024x768). In such case no appropriate resolution is selected for your monitor. If this issue is very important to you, you can report this issue to the monitor vendor. As the issue is related with the incorrect EDID on this monitor, IMO this bug should be rejected and marked as "NOTOURBUG". Thanks. > > What it means ??? > Created attachment 34335 [details]
Dmesg file with Kernel 2.6.28.16
Dear Yakui.
You have closed this bug report, but I would like to comment it.
If I use the Kernel 2.6.28.16, my system detect the resolution, In fact if I go to
System> Preferences> Screen I can choose the next resolutions:
1360 x 768 (16:9) 1152 x 864 (4:3) It is used by the system and is OK, 1024 x 7068 (4:3) 800 x 600 (4:3) 640x480(4:3)
Buth with this kernel I do not have sound. The kernels after it, no appropiate resolution.
Also, in recent kernels, the signal level (inalambric web icon) showed in panel ussually appears a second speaker icon in spite of this icon. In this kernel, apperas the inalambric icon & speaker icon always)
I am attaching the dmesg log using kernel 2.6.28.16
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.