|
Description
Yannick NGHIEM-XUAN
2009-03-12 13:33:46 UTC
Created attachment 23811 [details]
xorg.conf file
Created attachment 23812 [details]
dmesg output
Created attachment 23813 [details]
photo of the xserver started with the option "ModeDebug" "yes" added in the Device section
Interesting it detects 2 LVDS: [ 2.275796] (II) intel(0): Output LVDS is connected to pipe B [ 2.275846] (II) intel(0): Output LVDS-1 is connected to pipe A Does this machine ever worked with older driver version? This machine should be like eeebox, no LVDS, but using SDVO LVDS. Please test with 2.6.99.902, http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.6.99.902.tar.gz I tried to boot Ubuntu 8.04 (not sure what were the xserver and intel driver versions) but I got the same black screen with it. xf86-video-intel-2.6.99.902 seem to fix the bug (see the xf86-video-intel-2.6.99.902.jpg photo). The only strange behavior I could notice is a small band doubled on the right side of the screen (see the bandbug.jpg photo). The specifications of the machine tells the native resolution is 1366x768 against only 1360x768 for the closest resolution detected by the intel driver. I guess it can be the origin of this small problem. Any idea about this ? Anyway thank you very much for your help guys ! Created attachment 23879 [details]
xserver running with xf86-video-intel-2.6.99.902
Created attachment 23880 [details]
photo of the "band bug" on the right of the screen
Created attachment 23881 [details]
xorg.log file with intel-2.6.99.902
Thanks for testing. So it looks like SDVO LVDS doesn't get the right mode. cc Ma Ling who may have a patch for that. Or have you tried with a customed modeline in xorg.conf? since the original problem has been fixed, I'm removing this from 2.7 blocker. Created attachment 23894 [details]
please try the patch on your machine, then upload Xorg log file with modedebug option on, thanks.
(In reply to comment #12) > Created an attachment (id=23894) [details] > please try the patch on your machine, then upload Xorg log file with modedebug > option on, thanks. ping ~ Sorry for the delay,
I had a reject with the patch:
# cat ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c.rej*************** i830_sdvo_output_setup (xf86OutputPtr output, uint16_t flag)
*** 1542,1547 ****
/* clear up privates */
dev_priv->is_tv = FALSE;
intel_output->needs_tv_clock = FALSE;
if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1))
{
--- 1659,1665 ----
/* clear up privates */
dev_priv->is_tv = FALSE;
intel_output->needs_tv_clock = FALSE;
+ dev_priv->is_lvds = FALSE;
if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1))
{
I compiled it anyway without the rejected modification.
When I start the xserver, the screen remains black.
I attached the xorg log file.
Created attachment 24207 [details]
xorg log file with the patched i830_sdvo.c file
reject I had with the patch:
# cat ./src/i830_sdvo.c.rej
*************** i830_sdvo_output_setup (xf86OutputPtr output, uint16_t flag)
*** 1542,1547 ****
/* clear up privates */
dev_priv->is_tv = FALSE;
intel_output->needs_tv_clock = FALSE;
if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1))
{
--- 1659,1665 ----
/* clear up privates */
dev_priv->is_tv = FALSE;
intel_output->needs_tv_clock = FALSE;
+ dev_priv->is_lvds = FALSE;
if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1))
{
Created attachment 24237 [details]
please try the patch, then upload your log file with modedebug option on, thanks.
ping~ ping ~, Thanks Ma Ling (In reply to comment #16) > Created an attachment (id=24237) [details] > please try the patch, then upload your log file with modedebug option on, > thanks. > I'm afraid I have the same reject with the new patch. I downloaded xf86-video-intel-2.6.99.902.tar.gz again to be sure to have the correct source tree to apply the new patch on but same thing (see bellow): Am I doing something wrong ? is this patch supposed to be directly applied on xf86-video-intel-2.6.99.902 ? Thanks, Yannick root@asriel:/home/tnx/Documents/bug_i945# patch ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c < sdvo_lvds_debug.patch xf86-video-intel-2.6.99.902/ Xorg.0.log_03242009 root@asriel:/home/tnx/Documents/bug_i945# patch ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c < sdvo_lvds_debug.patch patching file ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c Hunk #4 succeeded at 1180 (offset -5 lines). Hunk #5 succeeded at 1213 (offset -5 lines). Hunk #6 succeeded at 1580 (offset -7 lines). Hunk #7 FAILED at 1659. Hunk #8 succeeded at 1688 (offset -11 lines). Hunk #9 succeeded at 1804 (offset -11 lines). Hunk #10 succeeded at 2104 (offset -9 lines). 1 out of 10 hunks FAILED -- saving rejects to file ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c.rej root@asriel:/home/tnx/Documents/bug_i945# cat ./xf86-video-intel-2.6.99.902/src/i830_sdvo.c.rej *************** i830_sdvo_output_setup (xf86OutputPtr output, uint16_t flag) *** 1542,1547 **** /* clear up privates */ dev_priv->is_tv = FALSE; intel_output->needs_tv_clock = FALSE; if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1)) { --- 1659,1665 ---- /* clear up privates */ dev_priv->is_tv = FALSE; intel_output->needs_tv_clock = FALSE; + dev_priv->is_lvds = FALSE; if (flag & (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1)) { Created attachment 24689 [details]
please try the debug patch on your machine, thanks.
Created attachment 25382 [details]
xserver log (libdrm-2.4.9 + xf86-video-intel-2.6.99.903 + the patch)
After a power cycle, the machine has a blank screen when Xorg starts.
Please let me know if you need more details.
Created attachment 25953 [details]
please try the debug patch on your machine,
Because no integrated lvds, please ignore it by xorg.conf, then run the patch.
Section "Device"
...
Option "monitor-LVDS" "LVDS"
...
EndSection
...
Section "Monitor"
Identifier "LVDS"
Option "Ignore" "True"
EndSection
thanks
Ma Ling
ping ~ The bug seems to be fixed with the patch id=24237. I attached the following files for your debugging purposes: - the xorg.conf I used - the xserver log file produced (debug mode activated) - a photo of the right border of the screen Thanks ! Yannick Created attachment 26230 [details]
xorg.conf file
Created attachment 26231 [details]
xorg log file
Created attachment 26232 [details]
photo of the right border of the screen
(In reply to comment #24) > The bug seems to be fixed with the patch id=24237. I attached the following > files for your debugging purposes: > - the xorg.conf I used > - the xserver log file produced (debug mode activated) > - a photo of the right border of the screen > > Thanks ! > > Yannick > Oups ! I meant patch id=25953 Created attachment 26324 [details]
please try the patch on your machine under the same environment with comments #22, thanks.
The patch is our latest version.
please ignore integrated lvds by xorg.conf, then run the patch.
Section "Device"
...
Option "monitor-LVDS" "LVDS"
...
EndSection
...
Section "Monitor"
Identifier "LVDS"
Option "Ignore" "True"
EndSection
thanks for your help
Ma Ling
Created attachment 26325 [details]
please use this patch to replace above one (26324), thanks
Hi Close the issue now, please update your driver. Thanks for your help Ma Ling commit ea0b00e675281b2914450992501566122f9affe0 Author: Ma Ling <ling.ma@intel.com> Date: Mon Jun 1 17:13:53 2009 +0800 Provide mode line from VBT to xorg. If sdvo get modes function can't find modes from EDID, transmit sdvo lvds modes from VBT to xorg. Signed-off-by: Ma Ling <ling.ma@intel.com> *** This bug has been marked as a duplicate of bug 20241 *** ok, Thanks you very much, Yannick (In reply to comment #31) > Hi > Close the issue now, please update your driver. > > Thanks for your help > Ma Ling > > commit ea0b00e675281b2914450992501566122f9affe0 > Author: Ma Ling <ling.ma@intel.com> > Date: Mon Jun 1 17:13:53 2009 +0800 > > Provide mode line from VBT to xorg. > > If sdvo get modes function can't find modes from EDID, > transmit sdvo lvds modes from VBT to xorg. > > Signed-off-by: Ma Ling <ling.ma@intel.com> > > *** This bug has been marked as a duplicate of bug 20241 *** > |
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.