Mailinglist Archive: opensuse-bugs (4067 mails)

< Previous Next >
[Bug 710954] New: Core i5-2500K [Sandybridge] built-in Graphics fails since kernel update to
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 8 Aug 2011 10:40:30 +0000
  • Message-id: <>

Summary: Core i5-2500K [Sandybridge] built-in Graphics fails
since kernel update to
Classification: openSUSE
Product: openSUSE 11.4
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.4
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: logicacmg@xxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---

Created an attachment (id=444681)
--> (
XOrg log file

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101

I have installed the standard security updates YaST2 Online Update has offered
me. During this update the kernel updated from to
Since then the screen gets dark immediately right after the first kernel screen
outputs (usually hidden behind splash).
Before that the system worked fine.
I found out after a while, that it is possible to start the system nonetheless.
My system is fully LUKS encrypted. The failure happens before the root system
is available!
Of course it is possible that my problem is caused by another component than
the kernel, but as there is no downgrade option to really validate this, this
is the best guess.

Reproducible: Always

Steps to Reproduce:
1. Buy a Gigabyte H67A-UDH3-B3 keyboard.
2. Buy a Intel Core i5-2500K (and install it).
3. Attach a 1920x1200 monitor via DVI-D to the mainboard.
4. Install OpenSUSE 11.4.
5. Install all patches provided until 2011-08-07 (esp. kernel
6. Boot system.

Actual Results:
Usually it shows only the splash screen and then the screen turns black (no
If splash screen is removed by boot option, there is a screen output "doing
fast boot" and very short time the next output line ("Creating device nodes
with udev" in my case), then black (no signal).

Expected Results:
System should start with 1920x1200 resolution and start X11.

Mind that the Xorg.1.log is written after the problem actually happened,
because at that time the system definitely has no access to any other file
system than /boot.

- start failsafe. System runs in 1024x768, which is not feasible for real work.
- start system with boot option
nomodeset vga=0x34B
This gives at least the opportunity to work with 1600x1200

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >