The EDID is probed fine:

(II) intel(0): Supported VESA Video Modes:
(II) intel(0): 720x400@70Hz
(II) intel(0): 640x480@60Hz
(II) intel(0): 640x480@72Hz
(II) intel(0): 640x480@75Hz
(II) intel(0): 800x600@60Hz
(II) intel(0): 800x600@75Hz
(II) intel(0): 1024x768@60Hz
(II) intel(0): 1024x768@70Hz
(II) intel(0): 1024x768@75Hz
(II) intel(0): 1280x1024@75Hz
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported Future Video Modes:
(II) intel(0): #0: hsize: 1280  vsize 960  refresh: 75  vid: 20353
(II) intel(0): #1: hsize: 1024  vsize 768  refresh: 75  vid: 20321
(II) intel(0): #2: hsize: 800  vsize 600  refresh: 75  vid: 20293
(II) intel(0): #3: hsize: 640  vsize 480  refresh: 75  vid: 20273
(II) intel(0): #4: hsize: 1280  vsize 1024  refresh: 75  vid: 36737
(II) intel(0): #5: hsize: 1024  vsize 819  refresh: 75  vid: 36705
(II) intel(0): #6: hsize: 800  vsize 640  refresh: 75  vid: 36677

(II) intel(0): EDID (in hex):
(II) intel(0): 	00ffffffffffff0036696264cc22da03
(II) intel(0): 	2311010381251ea4e8fbb4a1554b9724
(II) intel(0): 	10484cad4f00814f614f454f314f818f
(II) intel(0): 	618f458f0101c31e0020410020301060
(II) intel(0): 	1300782d1100001e000000fd0032551e
(II) intel(0): 	520b000a202020202020000000fc0043
(II) intel(0): 	72797374616c0a0a0a0a0a0a000000ff
(II) intel(0): 	003030303030310a20202020202000e3

But you've got a broken config file that's cutting out all the useful modes, in particular the preferred one.

Section "Monitor"
  HorizSync    31-38
  Identifier   "Monitor[0]"
  ModelName    "800X600@60HZ"
  Option       "DPMS"
  VendorName   "--> VESA"
  VertRefresh  50-60
  UseModes     "Modes[0]"
EndSection

(II) intel(0): Not using mode "1280x960" (vrefresh out of range)

Delete the horizsync and vertrefresh, and probably everything else in there, and try again.

As I said is working in VESA mode so I think you missunderstood me. The
VESA config works as expected - the VESA logs are only for diagnose and
comparison.
The intel driver does not work and in my opinion the xorg.conf is correct !

I also tried all modelines generated by all modern linux distributions
during install or with their tools. None are working !

Played with manually generated modelines - ALL yields the same results -
no output on LVDS.

Adrian



Sincerely
Adrian

> http://bugs.freedesktop.org/show_bug.cgi?id=16517
>
>
> Eric Anholt <eric@anholt.net> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |INVALID
>
>
>
>
> --- Comment #1 from Eric Anholt <eric@anholt.net>  2008-06-26 21:07:26 PST
> ---
> The EDID is probed fine:
>
> (II) intel(0): Supported VESA Video Modes:
> (II) intel(0): 720x400@70Hz
> (II) intel(0): 640x480@60Hz
> (II) intel(0): 640x480@72Hz
> (II) intel(0): 640x480@75Hz
> (II) intel(0): 800x600@60Hz
> (II) intel(0): 800x600@75Hz
> (II) intel(0): 1024x768@60Hz
> (II) intel(0): 1024x768@70Hz
> (II) intel(0): 1024x768@75Hz
> (II) intel(0): 1280x1024@75Hz
> (II) intel(0): Manufacturer's mask: 0
> (II) intel(0): Supported Future Video Modes:
> (II) intel(0): #0: hsize: 1280  vsize 960  refresh: 75  vid: 20353
> (II) intel(0): #1: hsize: 1024  vsize 768  refresh: 75  vid: 20321
> (II) intel(0): #2: hsize: 800  vsize 600  refresh: 75  vid: 20293
> (II) intel(0): #3: hsize: 640  vsize 480  refresh: 75  vid: 20273
> (II) intel(0): #4: hsize: 1280  vsize 1024  refresh: 75  vid: 36737
> (II) intel(0): #5: hsize: 1024  vsize 819  refresh: 75  vid: 36705
> (II) intel(0): #6: hsize: 800  vsize 640  refresh: 75  vid: 36677
>
> (II) intel(0): EDID (in hex):
> (II) intel(0):  00ffffffffffff0036696264cc22da03
> (II) intel(0):  2311010381251ea4e8fbb4a1554b9724
> (II) intel(0):  10484cad4f00814f614f454f314f818f
> (II) intel(0):  618f458f0101c31e0020410020301060
> (II) intel(0):  1300782d1100001e000000fd0032551e
> (II) intel(0):  520b000a202020202020000000fc0043
> (II) intel(0):  72797374616c0a0a0a0a0a0a000000ff
> (II) intel(0):  003030303030310a20202020202000e3
>
> But you've got a broken config file that's cutting out all the useful
> modes, in
> particular the preferred one.
>
> Section "Monitor"
>   HorizSync    31-38
>   Identifier   "Monitor[0]"
>   ModelName    "800X600@60HZ"
>   Option       "DPMS"
>   VendorName   "--> VESA"
>   VertRefresh  50-60
>   UseModes     "Modes[0]"
> EndSection
>
> (II) intel(0): Not using mode "1280x960" (vrefresh out of range)
>
> Delete the horizsync and vertrefresh, and probably everything else in
> there,
> and try again.
>
>
> --
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>

I don't know how do you mark the bug as solved as it my card with the given LCD screen - connected trough SDVOC doesn't work - AT ALL !


Did you take a look at the following in the VESA and Intel logs ?
From vesa log :
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read failed
(II) VESA(0): Searching for matching VESA mode(s):

NO DDC reading !!!!! (sorry for multiple "!"s)

And from the Intel log - the same corresponding section:
(==) intel(0): Using EXA for acceleration
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module already built-in
(II) intel(0): Output VGA using monitor section Monitor[0]
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): I2C bus "SDVOB DDC Bus" initialized.
(II) intel(0): Output TMDS-1 using monitor section Monitor[0]
(II) intel(0): SDVOB: device VID/DID: 02:3C.06, clock range 25.0MHz - 200.0MHz
(II) intel(0): SDVOB: 1 input channel
(II) intel(0): SDVOB: TMDS0 output reported
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
(II) intel(0): I2C bus "SDVOC DDC Bus" initialized.
(II) intel(0): Output TMDS-2 has no monitor section
(II) intel(0): SDVOC: device VID/DID: 02:47.02, clock range 25.0MHz - 165.0MHz
(II) intel(0): SDVOC: 1 input channel
(II) intel(0): SDVOC: TMDS0 output reported
(II) intel(0): Current clock rate multiplier: 8
(II) intel(0): Current clock rate multiplier: 1
(II) intel(0): Output VGA disconnected
(II) intel(0): EDID for output VGA
(II) intel(0): Output TMDS-1 connected
(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" removed.
(II) intel(0): EDID for output TMDS-1
(II) intel(0): Manufacturer: MSI  Model: 6462  Serial#: 64627404
(II) intel(0): Year: 2007  Week: 35
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): DFP 1.x compatible TMDS
(II) intel(0): Max H-Image Size [cm]: horiz.: 37  vert.: 30
(II) intel(0): Gamma: 2.64
(II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) intel(0): First detailed timing not preferred mode in violation of standard!(II) intel(0): redX: 0.632 redY: 0.335   greenX: 0.295 greenY: 0.593
(II) intel(0): blueX: 0.143 blueY: 0.065   whiteX: 0.282 whiteY: 0.297
(II) intel(0): Supported VESA Video Modes:
(II) intel(0): 720x400@70Hz
(II) intel(0): 640x480@60Hz
(II) intel(0): 640x480@72Hz
(II) intel(0): 640x480@75Hz
(II) intel(0): 800x600@60Hz
(II) intel(0): 800x600@75Hz
(II) intel(0): 1024x768@60Hz
(II) intel(0): 1024x768@70Hz
(II) intel(0): 1024x768@75Hz
(II) intel(0): 1280x1024@75Hz
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported Future Video Modes:
(II) intel(0): #0: hsize: 1280  vsize 960  refresh: 75  vid: 20353
(II) intel(0): #1: hsize: 1024  vsize 768  refresh: 75  vid: 20321
(II) intel(0): #2: hsize: 800  vsize 600  refresh: 75  vid: 20293
(II) intel(0): #3: hsize: 640  vsize 480  refresh: 75  vid: 20273
(II) intel(0): #4: hsize: 1280  vsize 1024  refresh: 75  vid: 36737
(II) intel(0): #5: hsize: 1024  vsize 819  refresh: 75  vid: 36705
(II) intel(0): #6: hsize: 800  vsize 640  refresh: 75  vid: 36677
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 78.8 MHz   Image Size:  376 x 301 mm
(II) intel(0): h_active: 1024  h_sync: 1040  h_sync_end 1136 h_blank_end 1312 h_border: 0
(II) intel(0): v_active: 768  v_sync: 769  v_sync_end 772 v_blanking: 800 v_border: 0
(II) intel(0): Ranges: V min: 50  V max: 85 Hz, H min: 30  H max: 82 kHz, PixClock max 110 MHz
(II) intel(0): Monitor name: Crystal
(II) intel(0): Serial No: 000001
(II) intel(0): EDID (in hex):
(II) intel(0): 	00ffffffffffff0036696264cc22da03
(II) intel(0): 	2311010381251ea4e8fbb4a1554b9724
(II) intel(0): 	10484cad4f00814f614f454f314f818f
(II) intel(0): 	618f458f0101c31e0020410020301060
(II) intel(0): 	1300782d1100001e000000fd0032551e
(II) intel(0): 	520b000a202020202020000000fc0043
(II) intel(0): 	72797374616c0a0a0a0a0a0a000000ff
(II) intel(0): 	003030303030310a20202020202000e3
(II) intel(0): EDID vendor "MSI", prod id 25698
(II) intel(0): Not using mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using mode "640x480" (vrefresh out of range)
(II) intel(0): Not using mode "640x480" (vrefresh out of range)
(II) intel(0): Not using mode "720x400" (vrefresh out of range)
(II) intel(0): Not using mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using mode "1024x768" (hsync out of range)
(II) intel(0): Not using mode "800x600" (vrefresh out of range)
(II) intel(0): Not using mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using mode "800x600" (vrefresh out of range)
(II) intel(0): Not using mode "640x480" (vrefresh out of range)
(II) intel(0): Not using mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using mode "1024x819" (vrefresh out of range)
(II) intel(0): Not using mode "800x640" (vrefresh out of range)
(II) intel(0): Not using default mode "640x350" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "720x400" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1152x864" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "832x624" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1152x768" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1600x1024" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) intel(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) intel(0): Printing probed modes for output TMDS-1
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x60.0   38.34  800 832 928 1024  600 604 608 624 -hsync -vsync (37.4 kHz)
(II) intel(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Output TMDS-2 disconnected
(II) intel(0): EDID for output TMDS-2
(II) intel(0): Output VGA disconnected
(II) intel(0): Output TMDS-1 connected
(II) intel(0): Output TMDS-2 disconnected
(II) intel(0): Output TMDS-1 using initial mode 800x600
<b>(EE) intel(0): First SDVOC output reported failure to sync</b>

So basically the SDVOC where the LCD is connected will never sync.
I've tried everithing in the screen frequency - I cannot get image whatever modelines I put in.

I szaw similar cases on Internet forums where people were saying that if the intel driver will not get properly the EDID data it will just shut off that output connection - which is my case. 
Reference: http://lists.freedesktop.org/archives/xorg/2007-February/022010.html
for the description.

I am exactly in this case.

Sincerely,
Adrian

DVI trough SDVO ?!?!?!? maybe

Could this be the famous problem of DVI trough SDVO not working ?
on "more on the bug EDID !?!?!? BUG"
Maybe is just that the DVI connection using the intel driver simply doesn't work like suggested by others here:
http://lists.freedesktop.org/archives/xorg/2008-January/032293.html

Quote:
Alexander E. Patrakov wrote:
> 2008/1/23, Alexander E. Patrakov <patrakov at gmail.com>:
>> 2008/1/22, Sergio Monteiro Basto <sergio at sergiomb.no-ip.org>:
>>> On Tue, 2008-01-22 at 12:57 +0500, Alexander E. Patrakov wrote:
>>>> Also in this configuration it fails to restore the VGA mode (gives
>>>> blank screen)
>>>> when I zap the X server with Ctrl+Alt+Backspace.
>>> I think, not guaranty ,   I saw this problem when I had xerver 1.3.0,
>>> and correct by upgrade to xserver 1.4+
>> With my LFS hat on, now I say that the "blank screen" bug (which, BTW,
>> can be reproduced with Ctrl+Alt+F1, too) still exists on my computer
>> with the following software versions:
>>
>> Mesa 557b0d9
>> xorg-server b6d4cdf
>> xf86-video-intel c35ab31
>>
>> However, while doing some GL testing, I did something that made this
>> bug go away. Here are the errors from Xorg log:
>
> Update: I did nothing. The following sequence of events is 100% reproducible.
>
> startx              # gives a nice desktop
> press Ctrl+Alt+F1   # gives blank screen
> press Ctrl+Alt+F7   # back to desktop
> press Ctrl+Alt+F1   # gives text console, as it should
> press Ctrl+Alt+F7   # back to desktop
>

Using current git (just intel and drm, everything else is Fedora 8), as
of today I cannot switch to the console at all. I
have an X3500 chip to a LCD display over VGA. I would use DVI, but that
doesn't work at all with the intel driver, but does with VESA.

Kevin

New status:
If I connect an external monitor DVI to SDVOB and restart X then the internal monitor SDVOC - LVDS also goes on and displays correctly.
At this point if I disconnect the display SDVOB display - the LDVS stays on.
If I reboot the computer without the SDVOB -DVI again I have the old behvaior - i.e the internal display will just go blank (black- off)

Adrian

POssible solution (hardware)

If I connect an external monitor DVI to SDVOB and restart X then the internal monitor SDVOC - LVDS also goes on and displays correctly.

At this point if I disconnect the display the LDVS stays on.

If I reboot the computer without the SDVOB -DVI again I have the old behvaior - i.e the internal display will just go blank (black- off). 

So – i draw the following conclusions

1)       The SDVOC (internal display) is the second connector on DVI that is looked upon
2)       The SDVOB (external DVI) when connected swirches on both SDVOC and SDVOB displays as SDVOB is correclty detected.

Switching the LVDS DVI cable with the external DVI cable might eventually solve the problem – is this possible ? 
(i.e. switch the outputs so that the internal LVDS becomes SDVOB and external DVI becomes SDVOC) ?

For intel driver developers - are you sure the SDVO outputs are handled correctly ? i.e. when nothing is connected on SDVOB but the internal display is connected on the "lower precedence" SDVOC output ?!?!? 

Adrian

I never even looked at the vesa logs.

In order to debug anything further, I think I need you to replace your xorg.conf with just the following content:

Section "Device"
        Identifier "my device"
        Driver "intel"
        Option "ModeDebug" "YES"
EndSection

Then start X with the external monitor disconnected, and attach your log.  Then, I'll know that it was nothing with your previous config file, won't get confused with the external monitor, and most importantly will have the register debug information to see what's going on.

Created attachment 17471 [details]
Conf and LOG for minimal Configuration

Hello,
 I tested with a minimal conf file as suggested and with MOdeDebug YES in teh config. I had to add a Screen device - or otherwise X wouldn't parse the conf file but there is no other additional information or settings.

I also confirm that I've tried the minimal config with the external monitor (DVI -SDVOB)connected - and the SDVOC - DVI (internal) correclty displays in this case.

Without the externel display as ALWAYS nothing gets displayed. I tend to believe that there is a problem with SDVO handling. i.e. the fact that there is nothing on SDVOB also disables SDVOC ?!? 

Adrian

Created attachment 17480 [details]
Chipset graphical schema

Additional Hardware Information

Here some additional hardware config information on the chipset connection:
I quote from the manufacturer:

"In the IONEGX31 system, the G31 chipset /BIOS detects two SDVO to DVI channels: 
SDVOB for the external DVI port.
SDVOC for the internal SDVO—DVI—LVDS port"

So the grahical adapter (not that this will change a lot I hope) as it was in my first log file (lspci) is G31 - on an Intel Chipset G33
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)


Adrian

Changed priority and severity. It seams to me that not being able to display anything is rather blocking if you want to use the Intel driver and have 3D acceleration.

We've bought more than 200 machines that we cannot use at present. Willing to help with anything - but I don't get much interaction here.

Adrian

re-assign

(In reply to comment #8)
> Created an attachment (id=17471) [details]
> Conf and LOG for minimal Configuration
> 
> Hello,
>  I tested with a minimal conf file as suggested and with MOdeDebug YES in teh
> config. I had to add a Screen device - or otherwise X wouldn't parse the conf
> file but there is no other additional information or settings.
> 
> I also confirm that I've tried the minimal config with the external monitor
> (DVI -SDVOB)connected - and the SDVOC - DVI (internal) correclty displays in
> this case.
> 
> Without the externel display as ALWAYS nothing gets displayed. I tend to
> believe that there is a problem with SDVO handling. i.e. the fact that there is
> nothing on SDVOB also disables SDVOC ?!? 
> 
> Adrian
> 

Andrian,

Is this log you got when you connect the external montior or not? If not, could you please also attach the log (with modedebug on ) when you connect external monitor, i.e. internal Lcd also works?

as Eric said, this is not an EDID issue, bug title apparently wrong..

Created attachment 17631 [details]
Confg MODEDEBUG and Xorg.0.log for 2 displays (both working in this case)

> Andrian,
> Is this log you got when you connect the external montior or not? If not, could
> you please also attach the log (with modedebug on ) when you connect external
> monitor, i.e. internal Lcd also works?
> as Eric said, this is not an EDID issue, bug title apparently wrong..

Yes you're right it seems more of a SDVO problem (thx for changing the desc) - but at the begining when I filed the bug I was lead to thinking is an EDID problem (seeing a few aother posts on the net). Aftwerwards (as seen in my message history) I correlated the SDVO error messages with some other informations people posted on the net and finally came to a conclusion when I conected 2 displays and noticed that in fact that is not an EDID but, to my knowledge an SDVO problem.

Here is the minimal conf with MODEDEBUG and with the external SDVOB DVI display connected. Both displays (internal LCD and external DVI) are working in this case ! (in the attachement list)

Hello,

    Have you got any new good news ?
Should I DHL you a computer with this chipset to be able to test ?
If you think that will help just give some address and I will get back the machine where you are done with it ?

Adrian

Have you tried with a lower mode? like 1024x768 60hz, what I suspect is mode from EDID has something wrong.

(In reply to comment #15)
> Have you tried with a lower mode? like 1024x768 60hz, what I suspect is mode
> from EDID has something wrong.
> 

I've tried 800x600 and 1024x768 - both not working.
On the other hand when an external monitor is connected all resolutions work correctly.

Guys I can send you a machine with this chipset for testing - wouldn't be this more effective ? If acceptable -could you post an address where I can send the unit ?

I've taken a look in the driver source code to see what happends with the SDVOs but I haven't really found a good point where I could start investigating....

It takes already a good deal of time - and we are seriously thinking into dropping intel cards.

Adrian

Created attachment 17979 [details]
xorg.log with modedebug on, both display work

Created attachment 17980 [details]
xorg.conf with modedebug on, both display work

Created attachment 17981 [details]
Xorg.log with modedebug on, minimum configuration

Created attachment 17982 [details]
xorg.conf with modedebug on, minimum configuration

Created attachment 17984 [details] [review]
write sdvo reg correctly

Please try with this patch, which apply to current git master.

oops, wrong patch.

Adrian, could you try current git master or 2.4.0 first?

Adrian, something you may try is to increase sdvo reg write time.

In src/i830_sdvo.c, i830_sdvo_write_sdvox(), try to increase that for cycle times to see if it helps.

Ok - I  was out for holidays most part of the august. I will try now the latest git and then if still not working the modifications suggested "sdvo four cycle times" 

Adrian

SOLVED - at least partially.
Ok it seems that with the 2.4.2 stable version the 2D part of the driver is working better. I am able to get display for some of the resolutions supported by the screen. I will have to install a Windows in parallel to check all available resolutions - but now at least I can get image. I will test the full driver with the 3D part - but those things normally shouldn't be influenced by this issue.

Cannot autogen.sh however the latest git version of the driver. I have an error for some undefined variable 

Adrian

Nice to hear that! ;)
If there're no other display problem, you may close this.

Assume no other display issue for this, so close.

Per Adrian's request to keep this until all testings would be done.

Ok the thing is not fully corrected at all.
From time to time I still get (driver version 2.4.2)
(II) Module "ddc" already built-in
(II) Module "i2c" already built-in
(II) Module "ramdac" already built-in
(EE) intel(0): First SDVOB output reported failure to sync


and from that point on 
1) either I get a messed up X screen and I have to kill the X server and restart it
2) or killing the X server doesn;t suffice - I have to reboot the machine. 

Rebooting always suffice !

Whatever you did guys it doesn't seem to be enough.

Now I find this happening after launching and exiting an application directly on X. It never occured to me on boot but maybe I did not manage to get the "correct timing" for that to happen.

Before jumping on me about launching an application and terminating it (as being the cause) I mention that the behaviour is the same for about any X application (xvinfo, xlsclients, xlsatoms, v4l-info, etc).
I mostly use vl4-info and xvinfo but then tested with other applications and it does the same. The bug no however is not systematic - i.e. can't give you the correct steps to reproduce it as it happens now and then 5-20 times /day.

Adrian

Created attachment 18783 [details]
Log of the 2.4.2 driver when everything is ok

Created attachment 18784 [details]
Log of the 2.4.2 driver when everything is ok

X log when X launches - no error

(In reply to comment #29)
> Per Adrian's request to keep this until all testings would be done.

We should really close this as the original reported issue has been fixed.

Andrian, please open a new bug for your new issue. Please understand reading through so long history comments until seeing a real issue in comment#30 is pain. Thanks.

Ok I will close this one and open a new one for the rest of the problems.

Thanks guys.

Adrian