Bug 245741
| Summary: | Unable to get more than 800x600 screen resolution with new FC6 kernel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Cohler <mdc1> | ||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 6 | CC: | ajax | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2007-07-27 20:39: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
Mike Cohler
2007-06-26 13:02:59 UTC
Created attachment 157891 [details]
xorg log with new kernel
Created attachment 157892 [details]
xorg log with new kernel - text file
Created attachment 157893 [details]
xorg log with old kernel - text file
Created attachment 157894 [details]
/var/log/messages
This is probably the cause: -(II) I810(0): VESA VBE DDC read successfully +(II) I810(0): VESA VBE DDC read failed But why it would suddenly stop working, I don't understand. There aren't any kernel patches in there that should have caused this... You should be able to work around this by adding HorizSync 31-80 VertRefresh 56-75 to the "monitor" section of /etc/X11/xorg.conf. Created attachment 157988 [details]
xorg.conf as autogenerated by the system
There was no monitor section in xorg.conf - the xorg.conf file was
autogenerated. I have attached the original file at #6. After appending a
section containing:
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31-80
VertRefresh 56-75
EndSection
I restarted X with the original kernel running, and this now produced the same
problem with no more than 800x600 resolution that I get with the new kernel!
Maybe the xorg.conf file needs to have other changes?
I'm not an Xpert but I think it needs to have
Monitor "Monitor0"
added to the Screen section?
Can we get a copy of boot messages from the old kernel? Thanks Chuck - I am away from the machine at meetings all today but I will check the xorg.conf details tomorrow and test - and will attach copies of /var/log/messages with relevant lines tomorrow when I am back at the machine. There is no boot.log I added the Monitor line to xorg.conf, and the machine does boot and gives X with the required resolution. However the normal boot progress screen is blank apart from a message (presumably from the monitor itself) saying that the optimum resolution is 1280x1024 which is what it should choose anyway! Clearly it does not choose the correct resolution until X itself starts. I will soon be installing F7 on this machine and although this seems to be a workaround I am not sure this bug is fully resolved. I hope that once F7 is installed and updated that this problem will not recur on this machine. I have done a clean f7 install on this machine, and am fully yum updated running kernel 2.6.21-1.3228.fc7 - the problem reported in this bug does not occur with f7 on either the original kernel or the current one. If no-one else reports further after this then I guess this bug should be closed? There was at least one bug in ~FC6 where the kernel's vm86 call would clobber some registers before returning to userspace, which would confuse X horribly and usually manifest as DDC failing. The offending code appears to be gone in F7, so, hooray. |