All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
@ 2019-07-27  1:43 bugzilla-daemon
  2019-07-27  2:36 ` bugzilla-daemon
                   ` (9 more replies)
  0 siblings, 10 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-27  1:43 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]

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

            Bug ID: 111228
           Summary: PRIME output screen satys black on 1002:15d8 with
                    128MB VRAM
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: hhfeuer@gmx.de

So far I met the same PCI ID 1002:15d8 with 2GB VRAM which was working fine in
prime output mode with any nvidia gpu as provider. The mentioned version with
128MB VRAM doesn't work. No error messages regarding prime, just the screen
staying black.
https://devtalk.nvidia.com/default/topic/1056652/linux/amd-ryzen-7-geforce-gtx-1660-ti-laptop-gt-cannot-get-nvidia-to-be-used-as-primary-graphics/1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2442 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
@ 2019-07-27  2:36 ` bugzilla-daemon
  2019-07-27  2:37 ` bugzilla-daemon
                   ` (8 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-27  2:36 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 615 bytes --]

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

--- Comment #1 from djczaps <januszekdawid@gmail.com> ---
Created attachment 144876
  --> https://bugs.freedesktop.org/attachment.cgi?id=144876&action=edit
nvidia bug report

I'm consistentky trying to run my Nvidia gtx 1660 Ti on laptop with Ryzen 7
processor. So far unsucessfull trying to get into GUI. It might be something
related to iommu and power management when trying to open and close the laptop
lid. Laptop model Ausus TUF 505 DU. Any help will be appreciated.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1545 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
  2019-07-27  2:36 ` bugzilla-daemon
@ 2019-07-27  2:37 ` bugzilla-daemon
  2019-07-29  9:15 ` bugzilla-daemon
                   ` (7 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-27  2:37 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 361 bytes --]

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

--- Comment #2 from djczaps <januszekdawid@gmail.com> ---
https://devtalk.nvidia.com/default/topic/1056652/linux/amd-ryzen-7-geforce-gtx-1660-ti-laptop-gt-cannot-get-nvidia-to-be-used-as-primary-graphics/post/5365696/#5365696

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1347 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
  2019-07-27  2:36 ` bugzilla-daemon
  2019-07-27  2:37 ` bugzilla-daemon
@ 2019-07-29  9:15 ` bugzilla-daemon
  2019-07-29  9:26 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-29  9:15 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 719 bytes --]

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

--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
>From the attached bug report log:

*** /usr/share/X11/xorg.conf.d/10-amdgpu.conf
*** ls: -rw-r--r-- 1 root root 98 2019-07-12 20:45:36.635624123 +1000
/usr/share/X11/xorg.conf.d/10-amdgpu.conf
Section "OutputClass"
        Identifier "AMDgpu"
        MatchDriver "amdgpu"
        Driver "modesetting"
EndSection

This file originally says

        Driver "amdgpu"

not "modesetting". Who/what modified this file? Does the problem also occur
with the unmodified file, so that the Xorg amdgpu driver is used?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1584 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (2 preceding siblings ...)
  2019-07-29  9:15 ` bugzilla-daemon
@ 2019-07-29  9:26 ` bugzilla-daemon
  2019-07-29  9:37 ` [Bug 111228] PRIME output screen stays " bugzilla-daemon
                   ` (5 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-29  9:26 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]

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

--- Comment #4 from Maik Freudenberg <hhfeuer@gmx.de> ---
Both amdgpu and modesetting driver were tested, same effect.
Most notewothy in the non-prime modesetting driver case is this:
[     5.477] (EE) modeset(0): [DRI2] No driver mapping found for PCI device
0x1002 / 0x15d8
[     5.477] (EE) modeset(0): Failed to initialize the DRI2 extension.
[     5.477] (--) RandR disabled
[     5.480] (II) SELinux: Disabled on system
[     5.480] (II) AIGLX: Screen 0 is not DRI2 capable
[     5.480] (EE) AIGLX: reverting to software rendering

On those other systems mentioned with 2GB VRAM, the modesetting driver runs
fine in any case. This seems to be a different bug with the modesetting driver,
though. Non-prime+amdgpu driver runs fine.
Since the display starts to work after a suspend/resume cycle, seems to be a
kernel bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1779 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (3 preceding siblings ...)
  2019-07-29  9:26 ` bugzilla-daemon
@ 2019-07-29  9:37 ` bugzilla-daemon
  2019-08-06 10:42 ` bugzilla-daemon
                   ` (4 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-07-29  9:37 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 524 bytes --]

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

Maik Freudenberg <hhfeuer@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|PRIME output screen satys   |PRIME output screen stays
                   |black on 1002:15d8 with     |black on 1002:15d8 with
                   |128MB VRAM                  |128MB VRAM

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1180 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (4 preceding siblings ...)
  2019-07-29  9:37 ` [Bug 111228] PRIME output screen stays " bugzilla-daemon
@ 2019-08-06 10:42 ` bugzilla-daemon
  2019-08-06 10:45 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-08-06 10:42 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 318 bytes --]

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

--- Comment #5 from djczaps <januszekdawid@gmail.com> ---
Created attachment 144955
  --> https://bugs.freedesktop.org/attachment.cgi?id=144955&action=edit
nvidia bug report Ubuntu

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (5 preceding siblings ...)
  2019-08-06 10:42 ` bugzilla-daemon
@ 2019-08-06 10:45 ` bugzilla-daemon
  2019-10-02  7:44 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-08-06 10:45 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]

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

--- Comment #6 from djczaps <januszekdawid@gmail.com> ---
Similar situation --> if not exactly the same. Except I don't need to do any
nvidia-blacklist as a backup. Nvidia is just blacklisted itself. Also strange
power management when You pres the switch off button most often the system
doesn't shutdown. Need to press the power button manually to make it happen.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1310 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (6 preceding siblings ...)
  2019-08-06 10:45 ` bugzilla-daemon
@ 2019-10-02  7:44 ` bugzilla-daemon
  2019-10-02  8:08 ` bugzilla-daemon
  2019-11-19  9:37 ` bugzilla-daemon
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-10-02  7:44 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 1378 bytes --]

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

--- Comment #7 from Maik Freudenberg <hhfeuer@gmx.de> ---
Updating with info from other users with the same amd gpu with 128MB VRAM:
- one user was able to switch to VT and start a second Xserver which then
worked fine.
- another user found out that connecting an external monitor would work, was
able to log into gnome and in the monitor manager, the internal display showed
as disabled. So he could simply enable it and started working.

So this seems to be failing on xrandr --auto, not correctly adding the internal
display to the config. Looking what Ubuntu does:
# Pass provider or sink and source
xrandr --setprovideroutputsource "$sink" "$src"

# Make sure xrandr sees all the outputs
xrandr --auto

# Do not move up. Only now xrandr shows the outputs
lvds=$(xrandr | grep -i -e "lvds" -e "edp" | head -n1 |cut -d " " -f 1)
xrandr --output "$lvds" --off
xrandr --output "$lvds" --auto

So it already disables and enables the internal display as a workaround for
something but this still isn't enough in this case.
Maybe this is some timing problem so that adding a "sleep 2" either before or
after xrandr --auto would make that work?

Doesn't explain why this is only happening on this specific model, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (7 preceding siblings ...)
  2019-10-02  7:44 ` bugzilla-daemon
@ 2019-10-02  8:08 ` bugzilla-daemon
  2019-11-19  9:37 ` bugzilla-daemon
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-10-02  8:08 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 476 bytes --]

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

--- Comment #8 from Maik Freudenberg <hhfeuer@gmx.de> ---
A note on amdgpu the amount of VRAM amdgpu is reporting:
This is the amount of system memory dedicated to the iGPU. Strange enough, this
doesn't seem to be bios configurable, which would be an easy workaround. It
seems to be hardcoded, some machines set to 128 MB, others to 2GB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1280 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

* [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
  2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
                   ` (8 preceding siblings ...)
  2019-10-02  8:08 ` bugzilla-daemon
@ 2019-11-19  9:37 ` bugzilla-daemon
  9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2019-11-19  9:37 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]

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

Martin Peres <martin.peres@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |MOVED

--- Comment #9 from Martin Peres <martin.peres@free.fr> ---
-- 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/877.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2404 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2019-11-19  9:37 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-27  1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
2019-07-27  2:36 ` bugzilla-daemon
2019-07-27  2:37 ` bugzilla-daemon
2019-07-29  9:15 ` bugzilla-daemon
2019-07-29  9:26 ` bugzilla-daemon
2019-07-29  9:37 ` [Bug 111228] PRIME output screen stays " bugzilla-daemon
2019-08-06 10:42 ` bugzilla-daemon
2019-08-06 10:45 ` bugzilla-daemon
2019-10-02  7:44 ` bugzilla-daemon
2019-10-02  8:08 ` bugzilla-daemon
2019-11-19  9:37 ` bugzilla-daemon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.