Summary: | AMD GPU pro 18.40 doesn't work with Kabylake-g | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Hai <hai.lan> | ||||
Component: | DRM/AMDgpu-pro | Assignee: | Default DRI bug account <dri-devel> | ||||
Status: | RESOLVED WONTFIX | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | CC: | cheng.zhou, kelvin.hu, xi.c.chen | ||||
Version: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Hai
2018-11-15 14:59:03 UTC
Created attachment 142477 [details]
xorg.0.log
Please use the upstream drivers for VegaM. Alex, Thanks a lot for your quick response! Hai is taking leave. I will follow up the issue when he takes leave. Could you please be more specific about the "upstream driver" mentioned in your comment? so we could have a try on our side. upstream is the open stack. Alex, We've tried the Open Stack, the OpenGL can work. From https://amdgpu-install.readthedocs.io/en/latest/install-overview.html, the Vulkan component is not in the "All-Open Stack" component list, that's reason we try Pro Stack at the beginning. Following on the "upstream drivers for VegaM", what do you mean specifically? We find that there are two open source drivers: 1) https://github.com/GPUOpen-Drivers/AMDVLK 2) https://www.mesa3d.org/ Is one of them the "upstream driver"? (In reply to Cheng from comment #5) > Following on the "upstream drivers for VegaM", what do you mean > specifically? We find that there are two open source drivers: > > 1) https://github.com/GPUOpen-Drivers/AMDVLK > 2) https://www.mesa3d.org/ > > Is one of them the "upstream driver"? Either should work. Vega-M is the integrated AMD GPU in kaby lake-g CPU. When we use mesa 18.2.2( https://www.mesa3d.org/) the GPU can work with AMD-Open driver. But it can't work with AMD-pro driver, thanks. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.