Bug 967206 - Intel Graphic module fails to load
Summary: Intel Graphic module fails to load
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-25 13:37 UTC by monts
Modified: 2013-05-25 18:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-25 18:10:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
dmesg_old (61.57 KB, text/plain)
2013-05-25 15:18 UTC, monts 		montosh.bisht: review+
Details
dmesg_new (22.27 KB, text/plain)
2013-05-25 15:21 UTC, monts 		no flags Details
View All

Description monts 2013-05-25 13:37:12 UTC 
Description of problem:3.10.0-0.rc2.git1.2.fc20.x86_64 fails to load Intel Graphic module 


Version-Release number of selected component (if applicable):
3.10.0-0.rc2.git1.2.fc20.x86_64

How reproducible:testing Rawhide via fedora-rawhide-kernel-nodebug 


Steps to Reproduce:
1.yum update to 3.10.0-0.rc2.git1.2.fc20.x86_64
2.reboot
3.fails to load Intel Graphic module falls back to vga resolution

Actual results:fails to load Intel Graphic module


Expected results:Should load the Intel Graphic module and normal screen resolution.


Additional info:trying to fix with manually installing
kernel-3.10.0-0.rc2.git3.1.fc20.x86_64.rpm via koji .. lets see .. careful out there those of you are testing Rawhide via fedora-rawhide-kernel-nodebug
Comment 1 Josh Boyer 2013-05-25 14:06:22 UTC 
Please provide the dmesg from your kernel boot.
Comment 2 monts 2013-05-25 15:18:47 UTC 
Created attachment 753115 [details]
dmesg_old

dmesg_old with 3.10.0-0.rc2.git1.2.fc20.x86_64
Comment 3 monts 2013-05-25 15:21:09 UTC 
Created attachment 753116 [details]
dmesg_new

dmesg_new with 3.10.0-0.rc2.git3.1.fc20.x86_64 
module gets loaded and works
Comment 4 Josh Boyer 2013-05-25 18:10:24 UTC 
This was probably related to an error that removed modules.builtin and modules.order.  It has since been fixed.  If you see this again with a newer kernel, please let us know.
Note You need to log in before you can comment on or make changes to this bug.