Bug 845722 - kernel-3.5.0-2.fc17.x86_64 only framebuffer with Intel graphics adapter
Summary: kernel-3.5.0-2.fc17.x86_64 only framebuffer with Intel graphics adapter
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-04 08:25 UTC by Daniel T. Rainers
Modified: 2013-07-31 17:49 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-31 17:49:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg.0.log after fallback to Vesa/framebuffer mode (28.89 KB, text/x-log)
2012-08-30 07:38 UTC, Daniel T. Rainers
no flags Details
relevant parts of dmesg dealing with vesafb and intelfb (1.38 KB, application/octet-stream)
2012-08-30 07:38 UTC, Daniel T. Rainers
no flags Details

Description Daniel T. Rainers 2012-08-04 08:25:30 UTC
Description of problem:

After upgrading to kernel-3.5.0-2.fc17.x86_64 my screen resolution will only be 1024x768. Console fonts are larger than normal and /var/log/Xorg.0.log indicates that X is running using the framebuffer drivers.

My graphics card according to lspci is:
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)

Normally this works fine with xorg-x11-drv-intel


Additional info:

After reverting back to kernel 3.4.6-2.fc17.x86_64 everything works fine, even with the latest xorg-x11-drv-intel (version 2.20.1-1.fc17.x86_64).

Comment 1 Daniel T. Rainers 2012-08-13 14:50:08 UTC
Wow, two weeks without any response. That's helpful...

Comment 2 Nick Turenkov 2012-08-22 13:48:15 UTC
I have the same problem. I just updated to 3.5.2 and after reboot got only 1024x768 as max resolution. I have looked into Xorg.0.log and saw that default vesa or so driver is used. Actually somehow X cannot determine display.

In addition:
Old kernel 3.3.4 works fine
3.5.0 - also did not work for me

Comment 3 Adam Jackson 2012-08-29 17:51:22 UTC
Please attach the X log from the failed configuration.

Comment 4 Daniel T. Rainers 2012-08-30 07:38:03 UTC
Created attachment 608063 [details]
Xorg.0.log after fallback to Vesa/framebuffer mode

Please note: Configuration of Xorg as found in /etc/X11/ or /etc/X11/xorg.conf.d has not been modified manually and only contains the default configuration of Fedora.

Comment 5 Daniel T. Rainers 2012-08-30 07:38:54 UTC
Created attachment 608064 [details]
relevant parts of dmesg dealing with vesafb and intelfb

Comment 6 Daniel T. Rainers 2012-09-19 10:21:29 UTC
The problem still exists. Also, I must add that manually selecting xorg-intel or intelfb in the specific configuration will not work.

Comment 7 Daniel T. Rainers 2012-10-19 07:19:45 UTC
Even today this problem persists. The last working kernel is 3.4.6-2 - EVERY NEWER kernel version has the problem described here. 

Why is there not even the slightest reply after I've submitted the required log files? That was almost TWO months ago...

Comment 8 Fedora End Of Life 2013-07-03 19:24:30 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2013-07-31 17:49:31 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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