Strange issue on Vega 8 Mobile (HP Envy x360 Laptop)

[Min Xu]

Thanks so much! I added the two DC kernel configures and it is working now!
This so great!

Thanks again!

On Mon, Jan 29, 2018 at 12:08 PM, Bridgman, John <John.Bridgman at amd.com>
wrote:

> Yes, please file a bugzilla ticket and attach dmesg output.
>
>
>
> *From:* Min Xu [mailto:min.xu.public at gmail.com]
> *Sent:* Monday, January 29, 2018 3:04 PM
> *To:* Bridgman, John
> *Cc:* amd-gfx at lists.freedesktop.org
> *Subject:* Re: Strange issue on Vega 8 Mobile (HP Envy x360 Laptop)
>
>
>
> Thanks for explaining that firmware is not permanently loaded. Then, I
> have no ideas. Do you need my dmesg output?
>
>
>
> On Mon, Jan 29, 2018 at 12:02 PM, Min Xu <min.xu.public at gmail.com> wrote:
>
> I am running archlinux, the firmware version is very new:
>
>
>
> linux-firmware-20180119.2a713be-1
>
>
>
>
>
> On Mon, Jan 29, 2018 at 12:01 PM, Bridgman, John <John.Bridgman at amd.com>
> wrote:
>
> Microcode for the GPU hardware blocks is not permanently updated in the
> chip, but rather is loaded at power-up. Usually the files will be
> distributed via a package with a name like linux-firmware.
>
>
>
> I didn't see a mention of which distro/version you are using but along
> with new kernel you will need a relatively new version of linux-firmware.
>
>
>
> *From:* amd-gfx [mailto:amd-gfx-bounces at lists.freedesktop.org] *On Behalf
> Of *Min Xu
> *Sent:* Monday, January 29, 2018 2:57 PM
> *To:* amd-gfx at lists.freedesktop.org
> *Subject:* Strange issue on Vega 8 Mobile (HP Envy x360 Laptop)
>
>
>
> Dear AMD GFX developers,
>
>
>
> I just got a HP Envy x360 laptop and I am trying to run linux on it. I
> want to first thank you all for the great work on the amdgpu driver.
> Without it, people like me wants to run Linux would be stuck with windows.
>
>
>
> I suspect that my issue is a new issue that hasn't been reported before,
> therefore, I am writing to you to see if there indeed is a new issue and
> whether there is a workaround.
>
>
>
> I have compiled the latest kernel from the amd-staging-drm-next branch
> last night. I think the kernel "works" with my GPU. The previous two
> kernels I tried (4.14 and 4.15 final release) either doesn't support this
> card or just simply hang the system most of the time.
>
>
>
> The issue I have is that the graphic card seems to never switch to the
> high resolution mode of the monitor. The kernel would boot with the default
> 800x600 VGA graphics and then stuck. The monitor continuous to display the
> content written to the 800x600 console (some kernel booting messages) after
> amdgpu takes over. I can see from kernel dmesg the amdgpu driver found my
> card and initialized it and seems to be all happy about it. Yet, nothing
> new is displayed on the monitor. The monitor just stuck at the content of
> the 800x600 graphics.
>
>
>
> The keyboard works in this situation. Kernel is alive and I can reboot it
> by pressing <ctrl>+<alt>+<del> and I saw from the log file the system
> restarts just fine.
>
>
>
> I have tried different noobs of the amdgpu driver, like
> amdgpu.exp_hw_support=1, si_support=0, etc. Nothing seems to work. I just
> stuck with not able to switch to 1920x1080.
>
>
>
> I suspect that this is related to my firmware version. I confirmed the
> latest firmware is installed on my /usr/lib/firmware/ dir. The reason I
> suspect that it is a firmware issue is that I got the machine just 2 days
> ago and I have updated windows 10 to build 1709, which is very new. I
> suspect that windows have updated the GPU's firmware and the linux driver
> isn't working with it. If so, is there a way to force a firmware load from
> the linux side (i.e. a downgrade).
>
>
>
> Other users on the internet has report success with this particular
> machine with 4.15 kernel. Given that 4.15 doesn't work for me, the only
> thing that I could think of is the firmware version.
>
>
>
> Any other ideas?
>
>
>
>
>
> Thanks a lot,
>
> Min
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20180129/7efe0425/attachment.html>