[Bug 63935] TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=63935

--- Comment #9 from Dave Witbrodt <dawitbro at sbcglobal.net> ---
Noting Benjamin's experience with EFI in comment 8, I took a look at my 3
machines on which I am trying the UVD support.  I have a laptop, a desktop, and
another (inexpensive) desktop which I use as a file server.


Desktop:  JUNIPER, no EFI support (several years old)
CONFIG_EXTRA_FIRMWARE="radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin
radeon/JUNIPER_rlc.bin radeon/CYPRESS_uvd.bin ..."
Boot results:
[    0.816646] [drm] UVD initialized successfully.


Laptop:  SUMO, no EFI support (not old, but not new enough for EFI)
CONFIG_EXTRA_FIRMWARE="radeon/SUMO_rlc.bin radeon/SUMO_me.bin
radeon/SUMO_pfp.bin radeon/SUMO_uvd.bin ..."
Boot results:
[    1.650383] [drm] UVD initialized successfully.


"fileserver":  SUMO2, EFI support (newest motherboard of the 3)
CONFIG_EXTRA_FIRMWARE="radeon/SUMO_rlc.bin radeon/SUMO2_me.bin
radeon/SUMO2_pfp.bin radeon/SUMO_uvd.bin"
Boot results:
[   11.575783] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).
See comment 6 above.


This looks like further evidence of EFI involvement with the problem.  I cannot
see any BIOS settings that would allow me to alter EFI support on my
"fileserver" motherboard.  The only option I could find had to do with PCI ROM
support ("legacy" vs "EFI"), but this had defaulted to "legacy" when I
installed the motherboard and I never touched it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130509/19e08833/attachment.html>