Bug 187794

Could you attach /etc/X11/xorg.conf and /var/log/Xorg.0.log? Thanks.

Created attachment 91524 [details]
/etc/X11/xorg.conf

Created attachment 91526 [details]
/var/log/Xorg.0.log

The graphical login screen was displayed with the described symptoms, then when I switched back to console mode, the log file had 1886 lines. When I switched back to VT7, I did not get the image back

Nothing obvious I can see in the config/logfile. Could you also try "i810xorg71" driver. Simply replace "i810" with "i810xorg71" in your config file.

Created attachment 91531 [details]
/etc/X11/xorg.conf driver modified to i810xorg71

Ok. Does it help? I suggest to reboot before testing the Xserver again.

Created attachment 91532 [details]
/var/log/Xorg.0.log for driver i810xorg71

the driver i810xorg71 was not found.
But I see a message in the first logfile which seems worth to be analysed, perhaps the driver cannot set the display modes in the graphics adapter:
(II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs.
and
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
        the saved state
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method.

Sorry, the i810xorg71 driver has been integrated after 10.1 release. I'll attach it.

Created attachment 91533 [details]
i810xorg71.tar.bz2

I tried the driver i810xorg71 : At first it seems to work, but if switch to a text console and then back to VT7, the display shows "power saving mode" or "input signal out of range" (in a green box, generated inside the monitor).
After retrying several times, it seems to me it works just after a fresh boot, afterwards the screen gets the garbling when going from init 3 to init 5, and "power saving mode" when switching VTs.
I suspect that the original i810 driver has the same behaviour.
I then tried selecting the exact definition for my monitor (IBM 6737). Here, I'll get "input signal out of range" message at the first switch to VT7 after rebooting. I'am attaching xorg.conf and Xorg.O.log for this last test case.

Created attachment 91541 [details]
/var/log/Xorg.0.log for driver i810xorg71 and IBM6737

Created attachment 91542 [details]
/etc/X11/xorg.conf driver i810xorg71 and IBM6737

Ok. Does adding (with using i810xorg71)

  Option "Noaccel"
  Option "SWcursor"

to the section "Device" of your config file help? Does the signal also get lost during logout of a user session (when a new xserver is started)?

Created attachment 91545 [details]
/var/log/boot.msg

Just an other idea, in boot.log there is a message about a patch:
Patching video bios 855resolution version 0.4, by Alain Poirier

Chipset: 845G (id=0x25608086)
VBIOS type: 3
VBIOS Version: 2603

** Patch mode 3c to resolution 1024x768 complete
done

Sure, this is for broken BIOSes, which do not support higher resolutions. If you think this might be a problem set VIDEOBIOS_PATCH to "no" in /etc/sysconfig/videobios.

Options "Noaccel" and "SWcursor" did not fix the problem.

But setting VIDEOBIOS_PATCH to "no" was the solution.

Wow! You've been the first with a problem with 855resolution. So do you still need the i810xorg71 driver with 855resolution disabled?

No, if 855resolution is disabled, i810 is working fine.

I made some checks to get a better monitor definition from YaST, but everytime I changed something 855resolution was reenabled in /etc/sysconfig/videobios and I had to disable it, then reboot to check the result.

Now, I have a working config with i810 at 1024x768 / 107Hz

Yes, that's a problem. SaX2 always reenables this. The easiest fix/workaround for you is to uninstall the 855resolution package. Setting to NORMAL since you've a fix/workaround for now.

Marcus, here's another one for the 855resolution blacklist.

yes indeed. The information from the command

   dmidecode

is needed here to build up the blacklist. This problem
will be tracked in bug: #201338

Thanks

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