Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #223956 > unrolled thread
| Started by | Dan Ritter <dsr@randomstring.org> |
|---|---|
| First post | 2020-06-24 16:30 +0200 |
| Last post | 2020-06-24 19:50 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics Dan Ritter <dsr@randomstring.org> - 2020-06-24 16:30 +0200
Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics Dan Ritter <dsr@randomstring.org> - 2020-06-24 18:20 +0200
Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics Greg Wooledge <wooledg@eeg.ccf.org> - 2020-06-24 18:40 +0200
Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics Dan Ritter <dsr@randomstring.org> - 2020-06-24 19:50 +0200
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-06-24 16:30 +0200 |
| Subject | Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics |
| Message-ID | <Alezv-4DZ-1@gated-at.bofh.it> |
Curtis Tucker1 wrote: > Hi, > > After installing firmware-bullseye + xserver-xorg-video-amdgpu + firmware-amd-graphics on an AMD Ryzen 7 Pro + Radeon Graphics platform, there is no dual monitor capability via HDMI. > > I thought the amdgpu from xorg would take care of things like xinerama or twinview. At this point, you should be able to do this with xrandr, or any of the frontend substitutes. What does xrandr |grep connect give you? From an xterm or similar, please. -dsr-
[toc] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-06-24 18:20 +0200 |
| Subject | Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics |
| Message-ID | <AlghX-5J1-5@gated-at.bofh.it> |
| In reply to | #223956 |
Curtis Tucker1 wrote: > Hi Dan, > > "xrandr | grep connect" output: > > xrandr: Failed to get size of gamma for output default > default connected primary 1920x1080+0+0 0mm x 0mm That suggests that your X server is not actually using the amdgpu driver. Here's one of mine, using amdgpu: DisplayPort-0 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 953mm x 543mm HDMI-A-0 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) Check for a very recent file called: /var/log/Xorg.0.log and start reading at the top. This should describe what happened in your most recent X session, and include items looking for your video card and eventually settling on a driver that fits it. If it isn't amdgpu, we'll need to convince your X server to use it. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-06-24 18:40 +0200 |
| Subject | Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics |
| Message-ID | <AlgBj-5Po-3@gated-at.bofh.it> |
| In reply to | #223958 |
On Wed, Jun 24, 2020 at 12:16:27PM -0400, Dan Ritter wrote: > Check for a very recent file called: > /var/log/Xorg.0.log Starting in Debian 9, the Xorg log file can be in two different places. Either there, or ~/.local/share/xorg/Xorg.0.log . Be sure to look for both, and use the one that's actually current.
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-06-24 19:50 +0200 |
| Subject | Re: [External] Re: No Dual Monitors on AMD Ryzen 7 Pro + Radeon Graphics |
| Message-ID | <AlhH3-6rP-3@gated-at.bofh.it> |
| In reply to | #223959 |
Curtis Tucker1 wrote: > No output in "~/.local", but I'll keep that in mind for future reference. I am starting to see that directory used more often, eg, fonts. > > Looking at the log in "/var/log", is loads the Radeon module, but then unloads it because it cannot find the right chipset on the board. The same for the fallback "fbdev/fbdevhw" because it could not find a framebuffer. Finally, it settles on "int10", makes a call into BIOS to initialize the GPU display as VESA with extensions VBE. Next it starts to configure other associated devices/components, ie, events, kb, touch screen, camera, etc., & hands over to udev control of HDMI/DP & HD audio/digital because it couldn't find any drivers. > > BTW: I posted this question before I discovered that there was no xorg.conf. > OK. The driver you actually want is "amdgpu", not "radeon" and definitely not VESA. Set that in xorg.conf and you should have full access to all your screens. -dsr-
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web