| Bug ID | 91197 |
|---|---|
| Summary | Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64 |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/Radeon |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | dennis.jansen@web.de |
I have several issues trying to connect a 4k display to the radeon card via HDMI (@30Hz). If I boot with the screen connected, when trying to take over modesetting from EFI, the internal notebook display goes black as well as the external. When I try to attach it during runtime, I can see the 3840 mode, but when I tryt to select it I get [ 97.667521] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 97.667549] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BF64 (len 962, WS 0, PS 0) @ 0xC1A1 Switching back to 1920 works fine, trying again simply causes the same error again. Tested Linux kernels 4.1.0 and 3.19. Ubuntu 15.04. I might not be able to test for long, will probably send the screen back before long if I can't get it working in full resolution at all.
Please also attach a copy of your vbios: (as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
| What | Removed | Added |
|---|---|---|
| Summary | Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck exeuting BF64 | Radeon Trinity 7400G fails with 4K UHD screen - atombios stuck executing BF64 |
Same issue in linux-drm-next and linux-daily from the Ubuntu repositories.
Created attachment 116889 [details]
dmesg 4.1+drm-next boot only
Created attachment 116890 [details]
dmesg 4.1+daily boot and vt switch and xrandr try
I've found a workaround: xrandr --newmode "3840x2160_30" 262.92 3840 3888 3920 4000 2160 2163 2168 2191 +hsync xrandr --addmode HDMI-0 "3840x2160_30" xrandr --output HDMI-0 --mode 3840x2160_30 I'm guessing the pixel clock might have been too high. Same problem with the Windows driver. The page (http://www.epanorama.net/faq/vga2rgb/calc.html) allowed me to convert the modeline with lower clock created with cru (http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU) in Windows to Linux. I was pleasantly surprised to find even vdpau working well, of course only up to FullHD video, but smooth playback on 4k resolution.
Created attachment 117226 [details]
dmesg
Same bug with Radeon HD 8370D
Created attachment 117227 [details]
vbios.rom
Same bug with Radeon HD 8370D
| What | Removed | Added |
|---|---|---|
| Attachment #117227 mime type | text/plain | application/octet-stream |
Created attachment 117228 [details]
Xorg.log
Same bug with Radeon HD 8370D
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
| What | Removed | Added |
|---|---|---|
| Resolution | FIXED | --- |
| Status | RESOLVED | REOPENED |
(In reply to NeverMind from comment #15) > Since the last update this bug no longer occur Could you clarify? What was updated? How was it fixed? Because the bug is still present for me in 4.2. If it was fixed for you, maybe you had a different bug. As this is the bug I've created, I'm reopening it.
Update: I get the BF64 error each time I switch between X and console. So it takes about 5 seconds each time. I still have to manually had modes to get 4k to work.
| What | Removed | Added |
|---|---|---|
| Status | REOPENED | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/627.