Bug 105573 - AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu
Summary: AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-17 19:01 UTC by CthUlhUzzz
Modified: 2019-11-19 08:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (22.95 KB, text/plain)
2018-03-17 19:01 UTC, CthUlhUzzz
no flags Details

Description CthUlhUzzz 2018-03-17 19:01:51 UTC
Created attachment 138173 [details]
Xorg log

Failed to start X Server on amdgpu driver stack
OS: Ubuntu 18.04b1
Kernel: 4.15.0

I have hybrid AMD graphics in notebook. If I use "radeon" stack X works perfectly.
But when I enable "amdgpu" stack X fails
Comment 1 CthUlhUzzz 2018-03-19 02:29:16 UTC
I found the errors reason. A discrete graphics card dynamically turns off as unnecessary by driver, then the server can not initialize it. If you pass the parameter radeon/amdgpu.runpm=0 to the driver module, the server starts normally. Does X support dynamic power switching for GPUs?

This state works:
phoenix@phoenix-laptop:~$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:01.0
1:DIS: :Pwr:0000:01:00.0

This state doesn't works:
phoenix@phoenix-laptop:~$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:01.0
1:DIS: :DynOff:0000:01:00.0
Comment 2 Martin Peres 2019-11-19 08:01:55 UTC
-- 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/xorg/driver/xf86-video-ati/issues/181.


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.