Bug 726143
| Summary: | [RV730] KMS failure in EFI mode (iMac11,2 1.0 with ATI "9488" (HD 4670?)) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> |
| Component: | xorg-x11-drv-ati | Assignee: | Mads Kiilerich <mads> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | gansalmon, itamar, jglisse, jonathan, kernel-maint, madhu.chinakonda, mzdunek, the.ridikulus.rat, xgl-maint |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | [cat:modesetting] | ||
| Fixed In Version: | kernel-3.3.4-4.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-18 13:36:10 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
Mads Kiilerich
2011-07-27 16:38:10 UTC
Created attachment 515558 [details]
Xorg.0.log with nomodeset and fbdev
please attach kernel log (dmesg) + Xorg log when booting without the nomodeset option I already attached dmesg without nomodeset - and with drm.debug=14. Isn't that good enough? KMS fails completely and blanks the screen and gives no output at all. AFAICT because it can't find a suitable connector (=display/modesetting?). AFAIK X in KMS mode thus doesn't have chance - and the X log didn't show anything interesting because it bailed out early. Do you want it anyway? Ok - I will get it tomorrow. Created attachment 515670 [details]
dmesg without debug
Created attachment 515671 [details]
/var/log/Xorg.0.log
First dmesg line that indicates an error is: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver Created attachment 515672 [details]
/var/log/Xorg.0.log
Likely display port issue with kms. Please attach your video bios: cd /sys/bus/pci/devices/0000:01:00.0 sudo sh -c "echo 1 > rom" sudo sh -c "cat rom > ~/bios.rom" Created attachment 515724 [details]
bios.rom
See also Bug 726337 for similar issue in BIOS mode. mjg59 points out that http://www.spinics.net/lists/dri-devel/msg13435.html should fix this issue. Created attachment 522363 [details]
dmesg from 3.1.0-0.rc5.git0.0.fc16.x86_64
kernel-3.1.0-0.rc5.git0.0.fc16.x86_64 seems to work slightly better - but still nothing on the display:
[ 3.903413] [drm] Initialized drm 1.1.0 20060810
[ 3.922150] [drm] radeon defaulting to kernel modesetting.
[ 3.922153] [drm] radeon kernel modesetting enabled.
[ 3.922559] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.922568] radeon 0000:01:00.0: setting latency timer to 64
[ 3.933585] [drm] initializing kernel modesetting (RV730 0x1002:0x9488 0x106B:0x00B6).
[ 3.933695] [drm] register mmio base: 0xD0420000
[ 3.933697] [drm] register mmio size: 65536
[ 5.079055] [drm] GPU not posted. posting now...
[ 5.082537] radeon 0000:01:00.0: VRAM: 256M 0x0000000000000000 - 0x000000000FFFFFFF (256M used)
[ 5.082544] radeon 0000:01:00.0: GTT: 512M 0x0000000010000000 - 0x000000002FFFFFFF
[ 5.083891] [drm] Detected VRAM RAM=256M, BAR=256M
[ 5.083894] [drm] RAM width 128bits DDR
[ 5.085470] [TTM] Zone kernel: Available graphics memory: 4072156 kiB.
[ 5.085475] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
[ 5.085479] [TTM] Initializing pool allocator.
[ 5.087042] [drm] radeon: 256M of VRAM memory ready
[ 5.087074] [drm] radeon: 512M of GTT memory ready.
[ 5.088012] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 5.088017] [drm] Driver supports precise vblank timestamp query.
[ 5.088293] radeon 0000:01:00.0: irq 42 for MSI/MSI-X
[ 5.088309] radeon 0000:01:00.0: radeon: using MSI.
[ 5.088918] [drm] radeon: irq initialized.
[ 5.088976] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 5.090957] [drm] Loading RV730 Microcode
[ 5.151297] radeon 0000:01:00.0: WB enabled
[ 5.202022] [drm] ring test succeeded in 0 usecs
[ 5.204997] [drm] radeon: ib pool ready.
[ 5.208190] [drm] ib test succeeded in 0 usecs
[ 5.221938] [drm] Radeon Display Connectors
[ 5.221942] [drm] Connector 0:
[ 5.221943] [drm] DisplayPort
[ 5.221945] [drm] HPD1
[ 5.221948] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 5.221950] [drm] Encoders:
[ 5.221952] [drm] DFP1: INTERNAL_UNIPHY
[ 5.221954] [drm] Connector 1:
[ 5.221956] [drm] eDP
[ 5.221958] [drm] HPD2
[ 5.221960] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 5.221962] [drm] Encoders:
[ 5.221964] [drm] LCD1: INTERNAL_UNIPHY
[ 5.221966] [drm] Connector 2:
[ 5.221967] [drm] VGA
[ 5.221970] [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c
[ 5.221971] [drm] Encoders:
[ 5.221973] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 5.341604] [drm] Radeon display connector DP-1: No monitor connected or invalid EDID
[ 5.461337] [drm] Radeon display connector eDP-1: No monitor connected or invalid EDID
[ 5.471082] [drm] Radeon display connector VGA-1: No monitor connected or invalid EDID
[ 5.471102] [drm] Special thermal controller config
[ 5.471275] [drm] radeon: power management initialized
[ 5.559034] [drm] fb mappable at 0xC0142000
[ 5.559036] [drm] vram apper at 0xC0000000
[ 5.559038] [drm] size 8294400
[ 5.559039] [drm] fb depth is 24
[ 5.559040] [drm] pitch is 7680
[ 5.978739] Console: switching to colour frame buffer device 240x67
[ 5.993191] fb0: radeondrmfb frame buffer device
[ 5.993196] drm: registered panic notifier
[ 5.993311] [drm] Initialized radeon 2.11.0 20080528 for 0000:01:00.0 on minor 0
X show plenty of invalids:
[ 27.905] (==) FBDEV(0): Backing store disabled
[ 27.909] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 27.909] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
Created attachment 522364 [details]
Xorg.0.log from 3.1.0-0.rc5.git0.0.fc16.x86_64
Same behaviour with 3.1.0-7.fc16.x86_64, but a couple of new messages: [drm:radeon_dp_i2c_aux_ch] *ERROR* aux i2c too many retries, giving up [drm:radeon_dp_i2c_aux_ch] *ERROR* aux i2c too many retries, giving up Still failing with F16 with 3.2.9-1.fc16.x86_64. When you test make sure to disable fbdev in Xorg conf and also attach newer dmesg with drm.debug=14 Created attachment 581356 [details]
smolt, dmesg and X log with 3.3.2-6.fc16.x86_64 drm.debug=14
Attaching smolt, dmesg and X log with 3.3.2-6.fc16.x86_64 drm.debug=14, captured blindly using a custom live USB booted with grub2 2.0 beta4.
(grub2 do not have any font and do not explicitly set gfxmode or gfxpayload and not use gfxterm ... could soemthing in that area make a difference?)
kernel-3.3.4-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.3.4-4.fc17 Package kernel-3.3.4-4.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.3.4-4.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7362/kernel-3.3.4-4.fc17 then log in and leave karma (feedback). kernel-3.3.4-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Do you have any plans to backport it to f16? I can't test a f17 kernel at the moment. Created attachment 592944 [details]
smolt info, dmesg and X log with 3.4.2-1.fc16.x86_64
I don't know the nature of the fix, but I would expect that it also should make it work with the 3.4 kernel in f16 ... but it doesn't do that for me.
Logs from custom live usb with EFI and grub2beta6 are attached.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |