Bug 496335
| Summary: | [kms] native resolution not used when kms is enabled (i915) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
| Component: | kernel | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | ajax, a.steffan, awilliam, itamar, kernel-maint, kevin, lsof |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-12 16:36:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Need Real Name
2009-04-17 21:24:30 UTC
Oh and suspend resume is broken now too. > Oh and suspend resume is broken now too.
Actually it's worse, switching VTs is broken. If I am lucky I get a terminal by continuously trying new VTs, but then everything freezes. If I keep trying more, I might see a _ cursor flashing ridiculously fast, so fast it's almost not flashing. Ctrl+Alt+Del does not response.
Upping severity since this is now a crash bug.
Is this report against 2.6.29.1-85? Can you try -97 from koji? This is a report against everything after 46.fc11.x86_64, up to and including kernel-2.6.29.1-70.fc11.x86_64. I will try 97 now. I booted into 97, and got the wrong resolution again, same as above (i.e. correct at one point during boot). Tried switching vts - freeze. No escape. Reboot 1 - Freeze when X starts. Reboot 2 - Freeze when X starts. Gone back to 46 for now. My screen's native resolution is 1680x1050. Setting xorg.conf to this shows "no mode of this name". Perhaps relevant? Still broken in kernel-2.6.29.1-100.fc11.x86_64. Do you need logs or anything? I realise you're busy, but I'm sitting here with a pretty much broken Fedora install and I've not heard anything. Do you expect the i915 will work before Fedora 11 reaches final? It seems strange that I can switch vts, but not run ctrl+alt+del or even use the vts. -46 doesn't crash my system, but the resolution is stretched making it awkward for anything graphical. No looking at photos, etc. kernel-2.6.29.1-111.fc11.x86_64 is also broken. How about attaching your /var/log/Xorg.0.log and dmesg from the 111 case? I have a eee900 here with i915 thats working fine. Sure, it's in the first comment: https://bugzilla.redhat.com/attachment.cgi?id=339892 For the -111 kernel and xorg-x11-drv-intel-2.7.0-2.fc11 case? That seems to be the -70 kernel and 2.6.99 intel driver. (In reply to comment #12) > For the -111 kernel and xorg-x11-drv-intel-2.7.0-2.fc11 case? > That seems to be the -70 kernel and 2.6.99 intel driver. Yes that's for an older kernel. I'll upload two new xorg log files. Created attachment 342351 [details]
the xorg log for with a normal boot (modesetting). I hold the power button when the machine does not respond.
Created attachment 342352 [details]
the xorg log with nomodeset as a kernel boot parameter.
This at least doesn't crash the box, but I get the wrong 1280x1024 resolution in X, despite configuring 1400x1050. Colour depth is 16 if that helps.
Created attachment 342353 [details]
lspci output
Created attachment 342354 [details]
my xorg.conf file
Initially generated by s-c-d, but amended to use 16 colours to see if that helped.
I notice "driver vesa". Will try changing to intel.
Changing "driver vesa" to "driver intel" gives me native resolution! But only if I boot with nomodeset. If I boot normally, I get X in 1024 x 768 despite the framebuffer using the native resolution. So, from that I assume you have a /etc/X11/xorg.conf? does it work if you move/remove that file and boot without it? nomodeset + xorg.conf file = X native resolution modeset + xorg.conf file = X low resolution and if I remember correctly (I can retest if you want): nomodeset + no xorg.conf = X low resoltuion modeset + no xorg.conf = crash Correction:
> nomodeset + no xorg.conf = X low resoltuion
nomodeset + no xorg.conf = X native resolution
This is new. Good.
To re-summarise: nomodeset + xorg.conf file = X native resolution modeset + xorg.conf file = X low resolution nomodeset + no xorg.conf file = X native resolution modeset + no xorg.conf file = X low resolution It looks like the intel driver is skipping over my screen's resolution: (II) intel(0): Printing probed modes for output DVI1 (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz) (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) I am confused. In both of the logs you posted, the driver in use is vesa, not intel. In this case no modesetting would be used, there's no modesetting for the vesa driver (AFAIK). Can you provide Xorg.0.logs from the case with no xorg.conf file? Created attachment 342361 [details]
xorg log with modesetting
Created attachment 342362 [details]
xorg log with no modesetting
Here are the logs with no xorg.conf file. looks like enough information there for kristian to figure out what's wrong. thanks. correcting summary. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping WFM I'm assuming comment #30 means "it works now". Closing on that basis, please reopen if I'm wrong. |