Bug 13361 - [i810] no X with 3.14.4 kernel
Summary: [i810] no X with 3.14.4 kernel
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-05-12 07:20 CEST by Felix Miata
Modified: 2014-05-21 22:44 CEST (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
Xorg.0.log running 3.13 (38.73 KB, text/plain)
2014-05-12 07:20 CEST, Felix Miata
Details
Xorg.0.log running 3.14 kernel (X failing) (34.24 KB, text/plain)
2014-05-12 07:21 CEST, Felix Miata
Details

Description Felix Miata 2014-05-12 07:20:41 CEST
Created attachment 5147 [details]
Xorg.0.log running 3.13

Card:Intel 810 and later: Intel Corporation|82810E DC-133 (CGC) Chipset Graphics Controller [DISPLAY_VGA] (vendor:8086 device:7125 subv:1028 subd:00b4) (rev: 03)

Booting previous kernel-desktop-3.13.10-1 KDE works normally. Booting freshly installed kernel-desktop-3.14.3-1 X won't start or crashes trying, I don't know which.
Comment 1 Felix Miata 2014-05-12 07:21:57 CEST
Created attachment 5148 [details]
Xorg.0.log running 3.14 kernel (X failing)
Felix Miata 2014-05-12 07:30:57 CEST

Summary: [i810] no X with => [i810] no X with 3.14.3 kernel

Comment 2 Felix Miata 2014-05-15 03:43:04 CEST
http://lists.freedesktop.org/archives/intel-gfx/2014-April/043917.html explains this was bisected upstream in kernel, but NAICT the fix only made it into the 3.15 kernel - this is still a problem with yesterday's 3.14.4 desktop rpm.
Manuel Hiebel 2014-05-20 00:42:48 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => tmb
Summary: [i810] no X with 3.14.3 kernel => [i810] no X with 3.14.4 kernel
Source RPM: (none) => kernel

Comment 3 Thomas Backlund 2014-05-21 22:44:24 CEST
Patch referenced in comment 2 merged in kernel-3.14.4-2.mga5 currently building

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.