Bug 1410338
Summary: | Atom E3940 (Apollo Lake) Intel HD Graphics 500 graphical resolution only up to 800x600 on RHEL 7.3 x86_64 UEFI mode but legacy mode up to 1024x768 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | smc_cert | ||||||
Component: | xorg-x11-drv-intel | Assignee: | Lyude <lyude> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 7.3 | CC: | desktop-qa-list, hwcert-reviewers, lyude, smc_cert, tpelka | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2017-03-03 17:45:54 UTC | Type: | Bug | ||||||
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
smc_cert
2017-01-05 07:58:16 UTC
Created attachment 1237537 [details]
Xorg.0.log on RHEL 7.3 x86_64 uEFI
Hello, Any update for this symptom? Thanks, Jass / Supermicro Hello, Any update for this symptom? Thanks, Jass / Supermicro Would you be willing to lend us some of this hardware? I don't think we have any available. As well, can you also do me a favor: add the parameter "drm.debug=0x6" to your kernel commandline, boot in UEFI mode and get me the output of dmesg (just dmesg is required, I don't need any of the other logs just yet) Created attachment 1256056 [details]
dmesg add parameter drm.debug=0x6.log
(In reply to Lyude from comment #5) > Would you be willing to lend us some of this hardware? I don't think we have > any available. > > As well, can you also do me a favor: add the parameter "drm.debug=0x6" to > your kernel commandline, boot in UEFI mode and get me the output of > > dmesg Lyude, Good Day! Please find attached log "dmesg add parameter drm.debug=0x6.log" and is it ok that we setup the SUT which no support IPMI KVM console for you debugging remotely?? Thanks, Jass / Supermicro > > (just dmesg is required, I don't need any of the other logs just yet) (In reply to smc_cert from comment #7) > (In reply to Lyude from comment #5) > > Would you be willing to lend us some of this hardware? I don't think we have > > any available. > > > > As well, can you also do me a favor: add the parameter "drm.debug=0x6" to > > your kernel commandline, boot in UEFI mode and get me the output of > > > > dmesg > > Lyude, > Good Day! > Please find attached log "dmesg add parameter drm.debug=0x6.log" and is it > ok that we setup the SUT which no support IPMI KVM console for you debugging > remotely?? > > Thanks, > Jass / Supermicro > > > > > (just dmesg is required, I don't need any of the other logs just yet) This would be just fine. This being said though it looks like this problem might not require any debugging to solve: the chipset this machine uses is apparently broxton, which I believe was (at the time of RHEL7.3) preliminary hardware. As confirmed by your dmesg: [ 3.641027] [drm] This hardware requires preliminary hardware support. See CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT, and/or modparam preliminary_hw_support This means that i915 won't enable itself on that chipset unless you add i915.preliminary_hw_support=1 to the kernel commandline. Can you check if things work somewhat better when you do that? As for the difference in resolution: I think that's just the firmware having different default resolutions for UEFI vs. BIOS. The resolution just never updates to what it should be after booting since i915 disables itself. I've also given a few more details regarding this to your partner manager. (In reply to Lyude from comment #8) > (In reply to smc_cert from comment #7) > > (In reply to Lyude from comment #5) > > > Would you be willing to lend us some of this hardware? I don't think we have > > > any available. > > > > > > As well, can you also do me a favor: add the parameter "drm.debug=0x6" to > > > your kernel commandline, boot in UEFI mode and get me the output of > > > > > > dmesg > > > > Lyude, > > Good Day! > > Please find attached log "dmesg add parameter drm.debug=0x6.log" and is it > > ok that we setup the SUT which no support IPMI KVM console for you debugging > > remotely?? > > > > Thanks, > > Jass / Supermicro > > > > > > > > (just dmesg is required, I don't need any of the other logs just yet) > > This would be just fine. This being said though it looks like this problem > might not require any debugging to solve: the chipset this machine uses is > apparently broxton, which I believe was (at the time of RHEL7.3) preliminary > hardware. As confirmed by your dmesg: > > [ 3.641027] [drm] This hardware requires preliminary hardware support. > See CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT, and/or modparam > preliminary_hw_support > > This means that i915 won't enable itself on that chipset unless you add > i915.preliminary_hw_support=1 to the kernel commandline. Can you check if > things work somewhat better when you do that? > > As for the difference in resolution: I think that's just the firmware having > different default resolutions for UEFI vs. BIOS. The resolution just never > updates to what it should be after booting since i915 disables itself. Lyude, Good Day! "add i915.preliminary_hw_support=1 to the kernel commandline" works for us and no more concern on my side, please close this case. Thanks for support. Thanks, Jass / Supermicro |