Bug 22777

Created attachment 27711 [details]
xorg.conf

Created attachment 27712 [details]
Xorg.0.log

Created attachment 27713 [details]
xrandr -q

Could you provide the G45 model or better url? We need to know what output interfaces (VGA, HDMI, TV?) exist/connected on the board.

00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e23] (rev 03)


with this Vendor/Product ID 2e22/2e23 sufficient for you to determine?

(In reply to comment #5)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller [8086:2e22] (rev 03)
> 00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller [8086:2e23] (rev 03)
> 
> 
> with this Vendor/Product ID 2e22/2e23 sufficient for you to determine?
 
No, this just tells it's G45.
I'm interested in the display interfaces available on the board.

Per the xrandr -q query it shows that is VGA and TV-2 is connected. HDMI is disconnected.

(In reply to comment #7)
> Per the xrandr -q query it shows that is VGA and TV-2 is connected. HDMI is
> disconnected.

This is a bug report, that means what xrandr report may be wrong. I don't quite believe the G45 board integrates TV, so it might be mis-reported or through a SDVO card. That's why I want you to tell the physical interfaces on the board (including any display card inserted). Can't you see the physical machine? 

No additional display cards added. the primary and secondary port is just the normal VGA port. 

Let me check out on the schematic/functional spec to see if i can get any clue.

driver is too old... this should have been fixed in the latest UMS driver. 

From the schematic

Intel G45 --> RGB/HS/VS --> CRT Primary display
Intel G45 -->SDV0-->Video DEC (chronal CH7317A)-->RGB/HS/VS --> CRT Secondary display

could you link me to where can i get the latest driver pls. thks

 Guek Wu Neo, the reason is because your sDVO device is a multi-function SDVO device which support both VGA and TV capability. It is detected as TV, that's why you see "TV-2" in the log. In current driver, this has been fixed.

For that reason, I change the summary line as well... thanks.

we don't provide package but you can get using git. See http://intellinuxgraphics.org/download.html

could you let me know the specific version?

xf86-video-intel????

2.7.99.902... or wait a couple of days for 2.8.0

SLES11GM is with xorg-server 1.5 while the patch 2.7.99.902 requires >= xorg-server 1.6.0 

i upgraded the terminal to xorg-server 1.6.0 and installed the patch
2.7.99.902.


able to see  X login screen in both pri and secondary. However the terminal
does not accept any input. keyboard...mouse does not response when pressed.
only can ssh to the terminal.

(In reply to comment #16)
> SLES11GM is with xorg-server 1.5 while the patch 2.7.99.902 requires >=
> xorg-server 1.6.0 
> 
> i upgraded the terminal to xorg-server 1.6.0 and installed the patch
> 2.7.99.902.
> 
> 
> able to see  X login screen in both pri and secondary. However the terminal
> does not accept any input. keyboard...mouse does not response when pressed.
> only can ssh to the terminal.
> 

thanks. so the problem for this should be resolved. ( display on both screen ). the next issue may not be our driver's problem, I think.

In reply to comment#17

>thanks. so the problem for this should be resolved. ( display on both >screen ). the next issue may not be our driver's problem, I think.


Although the display is now turn on with this patch, i am not able to fully verify the dual display modes due to the hang problem. 

Would it be possible to release a version that runs in xorg-server 1.5 since the current SLES11GM  does not support 16 yet?

no. 1.5 support has been discontinued... sorry.

I upgrade to X-server to 1.6.0 then build the latest xf86-video-intel(2.8.0)

linux-6i8e:/cc/qq/xf86-video-intel # make
Making all in uxa
Making all in src
Making all in xvmc
Making all in shader
Making all in mc
Making all in vld
Making all in bios_reader
Making all in ch7017
Making all in ch7xxx
Making all in ivch
Making all in sil164
Making all in tfp410
Making all in reg_dumper
Making all in render_program
  CC    i830_dri.o
i830_dri.c:66:18: error: dri2.h: No such file or directory
i830_dri.c:83: error: expected ???? ???? ???? ?鳬sm??or ?鳢_attribute__??before ?➒8                                                      30DRI2CreateBuffers??
i830_dri.c:242: error: expected declaration specifiers or ??..??before ?➍RI2BufferPtr??
i830_dri.c: In function ?➒830DRI2DestroyBuffers??
i830_dri.c:250: error: ?鴪uffers??undeclared (first use in this function)
i830_dri.c:250: error: (Each undeclared identifier is reported only once
i830_dri.c:250: error: for each function it appears in.)
i830_dri.c: At top level:
i830_dri.c:281: error: expected declaration specifiers or ??..??before ?➍RI2BufferPtr??
i830_dri.c:281: error: expected declaration specifiers or ??..??before ?➍RI2BufferPtr??
i830_dri.c: In function ?➒830DRI2CopyRegion??
i830_dri.c:283: error: ?鼈SrcBuffer??undeclared (first use in this function)
i830_dri.c:284: error: ?鼈DstBuffer??undeclared (first use in this function)
i830_dri.c:288: error: ?➍RI2BufferFrontLeft??undeclared (first use in this function)
i830_dri.c: In function ?➒830DRI2ScreenInit??
i830_dri.c:366: error: ?➍RI2InfoRec??undeclared (first use in this function)
i830_dri.c:366: error: expected ????before ?鹛nfo??
i830_dri.c:388: error: ?鹛nfo??undeclared (first use in this function)
i830_dri.c:426: error: ?➒830DRI2CreateBuffers??undeclared (first use in this function)
i830_dri.c:433: warning: implicit declaration of function ?➍RI2ScreenInit??
i830_dri.c:433: warning: nested extern declaration of ?➍RI2ScreenInit??
i830_dri.c: In function ?➒830DRI2CloseScreen??
i830_dri.c:441: warning: implicit declaration of function ?➍RI2CloseScreen??
i830_dri.c:441: warning: nested extern declaration of ?➍RI2CloseScreen??
make[3]: *** [i830_dri.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2



It seems dri2proto version is too old. I tried to build the dri2proto version
2.1 After that, it still got the same error.
Do you have any idea of this?

Hi Cindy, after building and installing the latest driproto, you need to rebuild your xorg with the newer package before compiling the video driver. 

Hi Vance/Cindy

could you discuss this offline not in this bugzilla.

comment# 20 isn't about this bug. please reopen if it still happen for you on the just released 2.8.0 driver. thanks.

Request to reopen this bug as fix does not seem to be in KMS version of 2.9.99 intel drivers.

The following three patches are required to fix this issue.

http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6ba148bbd78783f59eed3d898638c39b950dcd89

http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=51b87b9913ba164d4d5de79e558233915b37a0a5

http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3da549f5b350dd42516e5cb3576f7fefe012d95e

(In reply to comment #24)
> Request to reopen this bug as fix does not seem to be in KMS version of 2.9.99
> intel drivers.
> The following three patches are required to fix this issue.
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6ba148bbd78783f59eed3d898638c39b950dcd89
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=51b87b9913ba164d4d5de79e558233915b37a0a5
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3da549f5b350dd42516e5cb3576f7fefe012d95e

Hi, Vance
    We have the corresponding KMS version of the mentioned patch set in comment #24 and the patch set is already in upstream kernel. 

    Please try the latest upstream kernel(2.6.32) and see whether it can works for you. (Please boot the system with KMS enabled).
    
BTW: Now we don't support the UMS again. 
 
    Thanks.
   

Please try the KMS version and see whether it can works for you. If it can work for you, please open a new bug.

As we don't support UMS any more, this bug will be marked as closed.

thanks.

Already tested on a 2.6.32 kernel with KMS enabled and the issue still exist. It was would appear that the issue is still not fixed in the KMS driver. I've opened another bug to address the problem in KMS. (http://bugs.freedesktop.org/show_bug.cgi?id=25787)