Created attachment 20175 [details]
xorg.conf

Created attachment 20176 [details]
hwinfo

Guek is using the following driver related software

- xorg-server 1.5.2
- xf86-video-intel 2.5.0
- libdrm 2.4.1
- Mesa 7.2_intel-2008-q3_46921a5 (Intel-2008-Q3-RC5)
- Kernel 2.6.27.1

Sounds like a blocker to me. The only workaround for now is using vesa/fbdev driver.

[...]
(II) intel(0): Output VGA disconnected
(WW) intel(0): No outputs definitely connected, trying again...
(II) intel(0): Output VGA disconnected
(WW) intel(0): Unable to find initial modes
(EE) intel(0): No valid modes.

would you please submit a log with "ModeDebug" option turns on?

Does this hardware ever worked with previous intel driver 2.x? 

Created attachment 20202 [details]
Xorg.0.log collected after adding Option ModeDebug on

Created attachment 20203 [details]
xorg.conf with Option ModeDebug on

(In reply to comment #7)
> Does this hardware ever worked with previous intel driver 2.x? 

I doubt that this hardware has ever been tested with an earlier intel 2.x release. I assume that it worked with i810 driver before though.

855GM should at least have LVDS. What's your machine type? maybe we have wrong quirks?

Classic mode works fine on my R50e.

Yes it has LVDS. This is a point of sales with 15" IR touch screen from Elo Technology. hwinfo in previous attached. 

(In reply to comment #10)
> (In reply to comment #7)
> > Does this hardware ever worked with previous intel driver 2.x? 
> 
> I doubt that this hardware has ever been tested with an earlier intel 2.x
> release. I assume that it worked with i810 driver before though.
> 

If so, I don't think it's blocker.

Sounds like Intel is not interested into supporting hardware, which has been supported before by i810 driver. A driver which is no longer available for X.Org 7.4 (missing support for libpciaccess).

Does this machine have a VBIOS you can attach to this bug?

# cd /sys/devices/pci0000\:00/0000\:00\:02.0/
# echo 1 > rom
# cat rom > /tmp/rom.bin
# echo 0 > rom

It may also be that you could use the LVDSFixedMode option for this device; if it's a special purpose platform that may be the expected usage.

Created attachment 20292 [details]
rom.bin

Just notified that our driver now has a lvds quirk on this board alike...could you try to remove following line from src/i830_quirk.c and try again?

    /* Cappuccino SlimPRO SP625F, bz #11368 */
    { PCI_CHIP_I855_GM, 0x8086, 0x3582, quirk_ignore_lvds },

i did not locate the 'i830_quirk.c' in the sles11beta4 and sled11beta5 terminal that i have..

Guek, you would need to recompile the xf86-video-intel driver from source. I'm not sure if Intel provides a HOWTO for this. From my mind:

 git-clone git://anongit.freedesktop.org/git/driver/xf86-video-intel
 cd xf86-video-intel
 ./autogen.sh
 make
 make install

You need to install git and gcc package (+dependancies) before. Hope this are tools, which are available on SLES/SLED Beta.

Guek, just to double check. The vesa driver does work on this machine, right?

yes. they work with vesa 

would you please attach your xorg.log using vesa or directfb? thanks.

Created attachment 20535 [details]
Xorg.0.log when vesa driver used

(In reply to comment #17)
> Just notified that our driver now has a lvds quirk on this board alike...could
> you try to remove following line from src/i830_quirk.c and try again?
> 
>     /* Cappuccino SlimPRO SP625F, bz #11368 */
>     { PCI_CHIP_I855_GM, 0x8086, 0x3582, quirk_ignore_lvds },
> 

Guek, please also tell us the test result if you remove this from the source code... xorg.log file with ModeDebug turns on... thanks.

In reply to comment#24,  Pls see my reply in comment#18.

there is not 'i830_quirk.c' file in the sles11beta4 and sled11beta5 terminal
that i have..

(In reply to comment #25)
> In reply to comment#24,  Pls see my reply in comment#18.
> 
> there is not 'i830_quirk.c' file in the sles11beta4 and sled11beta5 terminal
> that i have..
> 

there should be source code from sles release, isn't it? maybe you need to install the -dev package?  Stefan Dirsch should know...

To move this bug on, we have to rely on  you to do the testing since we don't have this device...

thanks.

Stefan?

Guek, Michael, please see my comment #19.

Hi Stefan, I tried compiling the driver source but encountered some errors. Perhaps you can advise on this.

Upon running the script, I get the following error.

sles11beta4135:/tmp/xf86-video-intel # ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
configure.ac:273: error: must install xorg-macros 1.1.3 or later before running autoconf/autogen
configure.ac:273: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1

Vance, please install xorg-x11-proto-devel and xorg-x11-devel, e.g. by using

  zypper install xorg-x11-proto-devel xorg-x11-devel

Stefan,

did not locate the xorg-x11-proto-devel and xorg-x11-devel 3dvds of Sles11beta6. git is not  in either.
where can we get them from? 

(In reply to comment #31)
> did not locate the xorg-x11-proto-devel and xorg-x11-devel 3dvds of
> Sles11beta6. git is not  in either.
> where can we get them from?

Sigh. Seems we don't publish developer packages for our enterprise betas.
You can get the packages from openSUSE 11.1 from

  http://download.opensuse.org/factory/repo/oss/suse/i586/

, they are compatible.

managed to download and install the xorg-x11-proto-devel and xorg-x11-devel and their dependencies from the link. Thanks Stefan.

run './autogen.sh', move further. 

Stefan could you advise on  this error message.

./configure: line 12603: syntax error near unexpected token `XINERAMA,'
./configure: line 12603: `XORG_DRIVER_CHECK_EXT(XINERAMA, xineramaproto)'

Created attachment 20802 [details]
this is output messages upon running ./autogen.sh

Looks sles missed xineramaproto in xorg devel package. 

(In reply to comment #35)
> Looks sles missed xineramaproto in xorg devel package. 

You have to install xorg-x11-proto-devel. However, that should been a dependency of xorg-x11-devel.

The actual package should be xorg-x11-server-sdk.
try this if you still can not solve the build issue

Created attachment 20828 [details]
Xorg.0.log and xorg.conf 

by the way, i only managed to locate i830_quirks.c (With a 's')

thanks QianXian able to compile after installing the xorg-x11-server-sdk and its dependencies.

this is what i did:

(1) removed the following from  xf86-video-intel/src/i830_quirks.c
/* Cappuccino SlimPRO SP625F, bz #11368 */
    { PCI_CHIP_I855_GM, 0x8086, 0x3582, quirk_ignore_lvds 

(2)cd xf86-video-intel
 ./autogen.sh
 make
 make install

(3) edit the xorg.conf to use intel driver and with ModeDebug on.

(4) reboot and till do not able to see display when startX

I think you have wrong build or install of changed driver. Log should at least say LVDS ddc i2c initialization.
Try ./autogen.sh --prefix=/usr; make ; make install.

Created attachment 20931 [details]
i830.quirks.c, dmesg, messages, Xorg.0.log and xorg.conf

this is what i did:

(1) removed the following from  xf86-video-intel/src/i830_quirks.c
/* Cappuccino SlimPRO SP625F, bz #11368 */
    { PCI_CHIP_I855_GM, 0x8086, 0x3582, quirk_ignore_lvds 

(2) Try ./autogen.sh --prefix=/usr; make ; make install.


(3) edit /etc/X11/xorg.conf to use intel video driver

(4) it works:-)

Guek, thanks for verify this! I have removed origin quirk and added LVDS output detect patch into git master. Could you help to test if current git master works for you? This helps me to verify the LVDS detect logic. Thanks.

The commit should be 
1-0fe61b0b7e3bbe8ced1b0ad2be72c438d200c64b
2-4d7a95959d8223aec41550eb19f60b3edd7210a1

I attached the diff file for this, Guek, please patch this into you 2d driver and try this.

Novell, if it works, please add this patch into the SLE11 release.

Thanks for Zhenyu's great support

Created attachment 20938 [details]
new lvds detect patch from upstream 

commit
4d7a95959d8223aec41550eb19f60b3edd7210a1
0fe61b0b7e3bbe8ced1b0ad2be72c438d200c64b

ZhenYu,

hv you completed the uploading of the package?
could you give me the link pls. thank you.

The attachment is uploaded.

See the last attachment file.

do i need to rename the file? 
which folder  should i place the file to?
do i need to recompile the package?

i am waiting for further helping instruction from Intel on how to install the patch to try out.

(In reply to comment #46)
> do i need to rename the file? 
No
> which folder  should i place the file to?
cd xf86-video-intel/; patch -p1 <$patch_file 
> do i need to recompile the package?
> 
Yes,
./autogen.sh --prefix=/usr
make -j4 install

Reboot xserver. (ctrl-alt-backspace or telinit 3 and then telinit 5)

Created attachment 20991 [details]
Xorg.0.log i830_quirks.c and i830_lvds.c

Not able to start X using the intel driver after applying the patch.

Error message:Not able to start X with error message " maximum number of X
display failures reached.

Could you paste the output of 'ls /proc/acpi/button'? Is there 'lid' directory under /proc/acpi/button directory?

there is only a 'power' directory under '/proc/acpi/button'.

Do not see 'lid' directory under '/proc/acpi/button'

Created attachment 21002 [details] [review]
Be LID_UNKNOWN when no lid acpi object found

Thanks. Could you help to apply and test with this patch? 

And there's a debug utility under xf86-video-intel source, src/bios_reader/swf_dumper, could you paste output from running this tool?

Created attachment 21003 [details] [review]
Be LID_UNKNOWN when no lid acpi object found

Thanks. Could you help to apply and test with this patch? 

And there's a debug utility under xf86-video-intel source, src/bios_reader/swf_dumper, could you paste output from running this tool?

Created attachment 21004 [details] [review]
Be LID_UNKNOWN when no lid acpi object found

Thanks. Could you help to apply and test with this patch? 

And there's a debug utility under xf86-video-intel source, src/bios_reader/swf_dumper, could you paste output from running this tool?

Created attachment 21035 [details]
xorg.0.log swfdump xorg.conf 

display works with the patch from comment#52 using intel driver in xorg.conf

Guek, thanks for your testing! I've pushed the patch to upstream.

commit 80e2d90139dd99f50beb4f9353599608624b777d
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Thu Dec 11 13:45:17 2008 +0800

    Let lid status be unknown if no acpi lid object found

commit 4d7a95959d8223aec41550eb19f60b3edd7210a1
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Tue Dec 9 19:48:11 2008 +0800

    Try to add LVDS detect support
    
    This one trys to use lid status for LVDS detect,
    which works when internal panel is not used as primary
    display alone, or there's no internal panel at all.
    ACPI button driver's lid state interface is preferred,
    and SWF state is also checked if ACPI method failed.

commit 0fe61b0b7e3bbe8ced1b0ad2be72c438d200c64b
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Tue Dec 9 19:19:58 2008 +0800

    Remove Cappuccino SlimPRO SP625F 855GM LVDS quirk
    
    It breaks bug #18462 on IBM 855GM with same subdevice ids.

Guek, patches are now applied to our xorg-x11-driver-video package for SLE11, so next RC should include the fix.

Noted. Will lookout in RC2 and feedback. Thank you.

(In reply to comment #56)
> Guek, thanks for your testing! I've pushed the patch to upstream.
> 
> commit 80e2d90139dd99f50beb4f9353599608624b777d
> Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
> Date:   Thu Dec 11 13:45:17 2008 +0800
> 
>     Let lid status be unknown if no acpi lid object found
> 
> commit 4d7a95959d8223aec41550eb19f60b3edd7210a1
> Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
> Date:   Tue Dec 9 19:48:11 2008 +0800
> 
>     Try to add LVDS detect support
> 
>     This one trys to use lid status for LVDS detect,
>     which works when internal panel is not used as primary
>     display alone, or there's no internal panel at all.
>     ACPI button driver's lid state interface is preferred,
>     and SWF state is also checked if ACPI method failed.
> 
> commit 0fe61b0b7e3bbe8ced1b0ad2be72c438d200c64b
> Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
> Date:   Tue Dec 9 19:19:58 2008 +0800
> 
>     Remove Cappuccino SlimPRO SP625F 855GM LVDS quirk
> 
>     It breaks bug #18462 on IBM 855GM with same subdevice ids.

Unfortunately applying these patches caused severe regressions for a large part of our user base. The result for them is that no output is detected any longer,
so Xserver no longer comes up at all. Thus I'm afraid I need to reopen this one
and disable this patch for now. See

  https://bugzilla.novell.com/show_bug.cgi?id=486643 

for more details.

Bug 486643 - intel: No outputs detected after xorg-x11-driver-video update (855GM/915GM)

Could you help to get X log with ModeDebug on?

I will and let you know, once such a logfile is available.

Created attachment 24239 [details]
Xorg.0_7.4-19.5.1.log

Xorg.0.log with ModeDebug on.

(II) intel(0): LID switch detect closed with ACPI button

ok, so driver trys to know lid status through acpi button lid object, and that reported closed. 

We have seen this kind of hw with broken acpi, it's fixed through custom dsdt or driver has a BROKEN_ACPI_LID quirk if this hw's acpi can't be fixed with dsdt.

Could you ask user to attach acpidump? our acpi guy would like to see it.

Created attachment 24250 [details]
Xorg.0.log with ModeDebug on.

Created attachment 24251 [details]
Output of acpidump

I am suffering with the same behavior. 
Attached requested files.

*** This bug has been marked as a duplicate of bug 20826 ***

with the package mentioned in Bug #20826, what is the plan to have the fixed that we have verified to be working in this bug back in place for our terminal to function.

Why? Does this patch break anything?

Bug #20826 mentioned "disabled LVDS detect". Where else the package in this Bug#18462 comment#56  is with "LVDS detect".

Thus will the change in Bug#20826. Will it affect IBM terminal that is verfied to be working with package from Bug#18462 comment#56?

Wang should know. Anyway, we saw so many regressions, that we currently don't have a choice anyway. And Luc, we're talking about patches, not about packages.
Patches are changes to the source code. 

  http://en.wikipedia.org/wiki/Patch_(computing)

Packages is something different ...

Intel

could you respond on the query in comment#69

for your case ( 855GM with LVDS panel attached ), the revert of the change won't impact you, i.e. it by default assume any mobile chpset will come with a LVDS panel. So, even the patch is reverted , your case should still work.

Your problem is introduced by the patch of adding quirk for Cappuccino SlimPRO SP625F 855GM, which use exactly same board as you use but did _not_ come with a LVDS panel, commit 0fe61b0b7e3bbe8ced1b0ad2be72c438d200c64b get rid of this quirk. So it breaks another guy, but not you...