Debian 9 upgrade breaks radeon triple monitor setup












4















Before last weekend, my Debian 8 setup was relatively stable; there were some quirks (like not being able to use accelerated graphics at all), but it was usable for most of what I do. I was using the fglrx driver from AMD for my setup which is the following:




  • ATI Radeon HD 5870

  • 3 identical Samsung SyncMaster SA850 monitors

  • 3 HBR2 DP cables - no dongles or adapters


This worked well, using the full resolution and proper refresh rate for the displays, but I wanted to update to Debian 9, get on the open source driver, and hopefully fix the accelerated graphics issues. I had no idea what I was in for. It was been a long weekend, especially since I am no guru at X. From my first time using it with slackware 0.97 until now, it has always seemed more like magic than anything else :)



Here is where I am now. The xserver-xorg-video-radeon driver appears to be working correctly, and identifies the card and the monitors. When I have the system booting into graphical mode, the system actually thinks that everything is fine (gdm3 is running, my applications start up, etc.), but there is nothing on the screens. The monitors complain that "Not Optimal Mode. Recommended Mode 2560x1440" which is the native resolution for the monitors, and what I had been using.



I had initially searched and saw that I could at least get the virtual consoles up and running if I added nomodeset to grub, or set modeset=0 in the kernel module options. However, that basically disables the video driver, and it gives up. Removing that, and leaving modeset enabled, I can use xrandr to change to 1280x1024 and that "works", but it is not the desired setup at all (and doesn't fix the issue with the virtual terminals). I have tried adding a modeline with cvt and xrandr with the exact specifications of the monitor, but that didn't work either. I even tried with 2560x1440 @ 30Hz, and nothing. I tried toggling DPMS. I even tried a "live" Ubuntu USB boot. Nothing.



All packages on the box are updated as of 2018-03-19T14:00Z.



As seems to be the normal practice for this type of plea for help, here are some package versions, configuration files, and logs.




  • uname: Linux ziggy 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

  • debian: 9.4

  • xserver-xorg: 1:7.7+19

  • xserver-xorg-core: 2:1.19.2-1+deb9u2

  • xserver-xorg-video-radeon: 1:7.8.0-1+b1

  • firmware-misc-nonfree: 20161130-3


xorg.conf:



Section "Monitor"
Identifier "0-DFP1"
Option "TargetRefresh" "60"
Option "Position" "0 0"
Option "DPMS" "false"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection

Section "Monitor"
Identifier "0-DFP2"
Option "TargetRefresh" "60"
Option "Position" "2560 0"
Option "DPMS" "false"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection

Section "Monitor"
Identifier "0-DFP3"
Option "TargetRefresh" "60"
Option "Position" "5120 0"
Option "DPMS" "false"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection

Section "Device"
Identifier "Card0"
Driver "radeon"
BusID "PCI:6:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 7680 1440
EndSubSection
EndSection


The Xorg.0.log is large (available here) but here are some highlights:



[    10.141] (II) RADEON(0): Output DisplayPort-0 connected
[ 10.141] (II) RADEON(0): Output DisplayPort-1 connected
[ 10.141] (II) RADEON(0): Output DisplayPort-2 connected
[ 10.141] (II) RADEON(0): Output DisplayPort-3 disconnected
[ 10.141] (II) RADEON(0): Output DisplayPort-4 disconnected
[ 10.141] (II) RADEON(0): Output DisplayPort-5 disconnected
[ 10.141] (II) RADEON(0): Using spanning desktop for initial modes
[ 10.141] (II) RADEON(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0
[ 10.141] (II) RADEON(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0
[ 10.141] (II) RADEON(0): Output DisplayPort-2 using initial mode 2560x1440 +5120+0


Which looks VERY promising, but then this is what seems to kill it:



[    10.253] (II) RADEON(0): Setting screen physical size to 2032 x 381


What!?



NOTE: there are NO "EE" lines in there at all.



I have looked at many other threads, have tried using the different 3 ports on the card, using only one monitor, etc.










share|improve this question





























    4















    Before last weekend, my Debian 8 setup was relatively stable; there were some quirks (like not being able to use accelerated graphics at all), but it was usable for most of what I do. I was using the fglrx driver from AMD for my setup which is the following:




    • ATI Radeon HD 5870

    • 3 identical Samsung SyncMaster SA850 monitors

    • 3 HBR2 DP cables - no dongles or adapters


    This worked well, using the full resolution and proper refresh rate for the displays, but I wanted to update to Debian 9, get on the open source driver, and hopefully fix the accelerated graphics issues. I had no idea what I was in for. It was been a long weekend, especially since I am no guru at X. From my first time using it with slackware 0.97 until now, it has always seemed more like magic than anything else :)



    Here is where I am now. The xserver-xorg-video-radeon driver appears to be working correctly, and identifies the card and the monitors. When I have the system booting into graphical mode, the system actually thinks that everything is fine (gdm3 is running, my applications start up, etc.), but there is nothing on the screens. The monitors complain that "Not Optimal Mode. Recommended Mode 2560x1440" which is the native resolution for the monitors, and what I had been using.



    I had initially searched and saw that I could at least get the virtual consoles up and running if I added nomodeset to grub, or set modeset=0 in the kernel module options. However, that basically disables the video driver, and it gives up. Removing that, and leaving modeset enabled, I can use xrandr to change to 1280x1024 and that "works", but it is not the desired setup at all (and doesn't fix the issue with the virtual terminals). I have tried adding a modeline with cvt and xrandr with the exact specifications of the monitor, but that didn't work either. I even tried with 2560x1440 @ 30Hz, and nothing. I tried toggling DPMS. I even tried a "live" Ubuntu USB boot. Nothing.



    All packages on the box are updated as of 2018-03-19T14:00Z.



    As seems to be the normal practice for this type of plea for help, here are some package versions, configuration files, and logs.




    • uname: Linux ziggy 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

    • debian: 9.4

    • xserver-xorg: 1:7.7+19

    • xserver-xorg-core: 2:1.19.2-1+deb9u2

    • xserver-xorg-video-radeon: 1:7.8.0-1+b1

    • firmware-misc-nonfree: 20161130-3


    xorg.conf:



    Section "Monitor"
    Identifier "0-DFP1"
    Option "TargetRefresh" "60"
    Option "Position" "0 0"
    Option "DPMS" "false"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection

    Section "Monitor"
    Identifier "0-DFP2"
    Option "TargetRefresh" "60"
    Option "Position" "2560 0"
    Option "DPMS" "false"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection

    Section "Monitor"
    Identifier "0-DFP3"
    Option "TargetRefresh" "60"
    Option "Position" "5120 0"
    Option "DPMS" "false"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection

    Section "Device"
    Identifier "Card0"
    Driver "radeon"
    BusID "PCI:6:0:0"
    EndSection

    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Virtual 7680 1440
    EndSubSection
    EndSection


    The Xorg.0.log is large (available here) but here are some highlights:



    [    10.141] (II) RADEON(0): Output DisplayPort-0 connected
    [ 10.141] (II) RADEON(0): Output DisplayPort-1 connected
    [ 10.141] (II) RADEON(0): Output DisplayPort-2 connected
    [ 10.141] (II) RADEON(0): Output DisplayPort-3 disconnected
    [ 10.141] (II) RADEON(0): Output DisplayPort-4 disconnected
    [ 10.141] (II) RADEON(0): Output DisplayPort-5 disconnected
    [ 10.141] (II) RADEON(0): Using spanning desktop for initial modes
    [ 10.141] (II) RADEON(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0
    [ 10.141] (II) RADEON(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0
    [ 10.141] (II) RADEON(0): Output DisplayPort-2 using initial mode 2560x1440 +5120+0


    Which looks VERY promising, but then this is what seems to kill it:



    [    10.253] (II) RADEON(0): Setting screen physical size to 2032 x 381


    What!?



    NOTE: there are NO "EE" lines in there at all.



    I have looked at many other threads, have tried using the different 3 ports on the card, using only one monitor, etc.










    share|improve this question



























      4












      4








      4








      Before last weekend, my Debian 8 setup was relatively stable; there were some quirks (like not being able to use accelerated graphics at all), but it was usable for most of what I do. I was using the fglrx driver from AMD for my setup which is the following:




      • ATI Radeon HD 5870

      • 3 identical Samsung SyncMaster SA850 monitors

      • 3 HBR2 DP cables - no dongles or adapters


      This worked well, using the full resolution and proper refresh rate for the displays, but I wanted to update to Debian 9, get on the open source driver, and hopefully fix the accelerated graphics issues. I had no idea what I was in for. It was been a long weekend, especially since I am no guru at X. From my first time using it with slackware 0.97 until now, it has always seemed more like magic than anything else :)



      Here is where I am now. The xserver-xorg-video-radeon driver appears to be working correctly, and identifies the card and the monitors. When I have the system booting into graphical mode, the system actually thinks that everything is fine (gdm3 is running, my applications start up, etc.), but there is nothing on the screens. The monitors complain that "Not Optimal Mode. Recommended Mode 2560x1440" which is the native resolution for the monitors, and what I had been using.



      I had initially searched and saw that I could at least get the virtual consoles up and running if I added nomodeset to grub, or set modeset=0 in the kernel module options. However, that basically disables the video driver, and it gives up. Removing that, and leaving modeset enabled, I can use xrandr to change to 1280x1024 and that "works", but it is not the desired setup at all (and doesn't fix the issue with the virtual terminals). I have tried adding a modeline with cvt and xrandr with the exact specifications of the monitor, but that didn't work either. I even tried with 2560x1440 @ 30Hz, and nothing. I tried toggling DPMS. I even tried a "live" Ubuntu USB boot. Nothing.



      All packages on the box are updated as of 2018-03-19T14:00Z.



      As seems to be the normal practice for this type of plea for help, here are some package versions, configuration files, and logs.




      • uname: Linux ziggy 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

      • debian: 9.4

      • xserver-xorg: 1:7.7+19

      • xserver-xorg-core: 2:1.19.2-1+deb9u2

      • xserver-xorg-video-radeon: 1:7.8.0-1+b1

      • firmware-misc-nonfree: 20161130-3


      xorg.conf:



      Section "Monitor"
      Identifier "0-DFP1"
      Option "TargetRefresh" "60"
      Option "Position" "0 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Monitor"
      Identifier "0-DFP2"
      Option "TargetRefresh" "60"
      Option "Position" "2560 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Monitor"
      Identifier "0-DFP3"
      Option "TargetRefresh" "60"
      Option "Position" "5120 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Device"
      Identifier "Card0"
      Driver "radeon"
      BusID "PCI:6:0:0"
      EndSection

      Section "Screen"
      Identifier "Screen0"
      Device "Card0"
      DefaultDepth 24
      SubSection "Display"
      Viewport 0 0
      Depth 24
      Virtual 7680 1440
      EndSubSection
      EndSection


      The Xorg.0.log is large (available here) but here are some highlights:



      [    10.141] (II) RADEON(0): Output DisplayPort-0 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-1 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-2 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-3 disconnected
      [ 10.141] (II) RADEON(0): Output DisplayPort-4 disconnected
      [ 10.141] (II) RADEON(0): Output DisplayPort-5 disconnected
      [ 10.141] (II) RADEON(0): Using spanning desktop for initial modes
      [ 10.141] (II) RADEON(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0
      [ 10.141] (II) RADEON(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0
      [ 10.141] (II) RADEON(0): Output DisplayPort-2 using initial mode 2560x1440 +5120+0


      Which looks VERY promising, but then this is what seems to kill it:



      [    10.253] (II) RADEON(0): Setting screen physical size to 2032 x 381


      What!?



      NOTE: there are NO "EE" lines in there at all.



      I have looked at many other threads, have tried using the different 3 ports on the card, using only one monitor, etc.










      share|improve this question
















      Before last weekend, my Debian 8 setup was relatively stable; there were some quirks (like not being able to use accelerated graphics at all), but it was usable for most of what I do. I was using the fglrx driver from AMD for my setup which is the following:




      • ATI Radeon HD 5870

      • 3 identical Samsung SyncMaster SA850 monitors

      • 3 HBR2 DP cables - no dongles or adapters


      This worked well, using the full resolution and proper refresh rate for the displays, but I wanted to update to Debian 9, get on the open source driver, and hopefully fix the accelerated graphics issues. I had no idea what I was in for. It was been a long weekend, especially since I am no guru at X. From my first time using it with slackware 0.97 until now, it has always seemed more like magic than anything else :)



      Here is where I am now. The xserver-xorg-video-radeon driver appears to be working correctly, and identifies the card and the monitors. When I have the system booting into graphical mode, the system actually thinks that everything is fine (gdm3 is running, my applications start up, etc.), but there is nothing on the screens. The monitors complain that "Not Optimal Mode. Recommended Mode 2560x1440" which is the native resolution for the monitors, and what I had been using.



      I had initially searched and saw that I could at least get the virtual consoles up and running if I added nomodeset to grub, or set modeset=0 in the kernel module options. However, that basically disables the video driver, and it gives up. Removing that, and leaving modeset enabled, I can use xrandr to change to 1280x1024 and that "works", but it is not the desired setup at all (and doesn't fix the issue with the virtual terminals). I have tried adding a modeline with cvt and xrandr with the exact specifications of the monitor, but that didn't work either. I even tried with 2560x1440 @ 30Hz, and nothing. I tried toggling DPMS. I even tried a "live" Ubuntu USB boot. Nothing.



      All packages on the box are updated as of 2018-03-19T14:00Z.



      As seems to be the normal practice for this type of plea for help, here are some package versions, configuration files, and logs.




      • uname: Linux ziggy 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

      • debian: 9.4

      • xserver-xorg: 1:7.7+19

      • xserver-xorg-core: 2:1.19.2-1+deb9u2

      • xserver-xorg-video-radeon: 1:7.8.0-1+b1

      • firmware-misc-nonfree: 20161130-3


      xorg.conf:



      Section "Monitor"
      Identifier "0-DFP1"
      Option "TargetRefresh" "60"
      Option "Position" "0 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Monitor"
      Identifier "0-DFP2"
      Option "TargetRefresh" "60"
      Option "Position" "2560 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Monitor"
      Identifier "0-DFP3"
      Option "TargetRefresh" "60"
      Option "Position" "5120 0"
      Option "DPMS" "false"
      Option "Rotate" "normal"
      Option "Disable" "false"
      EndSection

      Section "Device"
      Identifier "Card0"
      Driver "radeon"
      BusID "PCI:6:0:0"
      EndSection

      Section "Screen"
      Identifier "Screen0"
      Device "Card0"
      DefaultDepth 24
      SubSection "Display"
      Viewport 0 0
      Depth 24
      Virtual 7680 1440
      EndSubSection
      EndSection


      The Xorg.0.log is large (available here) but here are some highlights:



      [    10.141] (II) RADEON(0): Output DisplayPort-0 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-1 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-2 connected
      [ 10.141] (II) RADEON(0): Output DisplayPort-3 disconnected
      [ 10.141] (II) RADEON(0): Output DisplayPort-4 disconnected
      [ 10.141] (II) RADEON(0): Output DisplayPort-5 disconnected
      [ 10.141] (II) RADEON(0): Using spanning desktop for initial modes
      [ 10.141] (II) RADEON(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0
      [ 10.141] (II) RADEON(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0
      [ 10.141] (II) RADEON(0): Output DisplayPort-2 using initial mode 2560x1440 +5120+0


      Which looks VERY promising, but then this is what seems to kill it:



      [    10.253] (II) RADEON(0): Setting screen physical size to 2032 x 381


      What!?



      NOTE: there are NO "EE" lines in there at all.



      I have looked at many other threads, have tried using the different 3 ports on the card, using only one monitor, etc.







      debian radeon






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 hours ago









      Rui F Ribeiro

      41.5k1483140




      41.5k1483140










      asked Mar 19 '18 at 14:56









      David BenoitDavid Benoit

      212




      212






















          1 Answer
          1






          active

          oldest

          votes


















          2














          fglrx is no longer supported in Debian 9. Your post appears related to this question previously asked in that they are reporting issues with missing fglrx. I think this forum post has a solution that could work for you. I am including links to the official Debian wiki on how to install open source and proprietary drivers. I recommend you only use the open source drivers.



          Use xrandr to Correct Configuration



          Delete your old x.org configuration (rm /etc/X11/xorg.conf) and set the output with xrandr.



          xrandr -q


          If this does not help, I recommend you start from scratch.



          Start from Scratch



          To make the troubleshooting process smoother let us start by purging all old configurations and drivers. As root(sudo) run these commands:



          apt purge "fglrx.*"
          rm /etc/X11/xorg.conf
          apt install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64


          Make sure your sources.list contains the contrib and non-free repositories like so:



          deb http://ftp.us.debian.org/debian/ stable main contrib non-free 


          If you needed to add them, do not forget to update apt, simply run as root(sudo) apt update. Next if you choose to use only the open source firmware for your card you will need to run this command:



          apt-get install firmware-linux-nonfree libgl1-mesa-dri xserver-xorg-video-ati


          And reboot your computer to initialize your graphics drivers and settings.



          Conclusion



          Please comment with any issues and I can update this answer to try and best correct your issue. Do not forget to reference the wiki on how to remove and install drivers. I believe this post on multi-monitor setups for Debian could help as well. Best of Luck!






          share|improve this answer


























          • Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

            – David Benoit
            Mar 19 '18 at 18:35













          • Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

            – kemotep
            Mar 19 '18 at 19:07











          • Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

            – David Benoit
            Mar 21 '18 at 3:32











          • Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

            – Nicolas
            Apr 21 '18 at 9:54













          • @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

            – kemotep
            Apr 23 '18 at 15:48











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432106%2fdebian-9-upgrade-breaks-radeon-triple-monitor-setup%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          fglrx is no longer supported in Debian 9. Your post appears related to this question previously asked in that they are reporting issues with missing fglrx. I think this forum post has a solution that could work for you. I am including links to the official Debian wiki on how to install open source and proprietary drivers. I recommend you only use the open source drivers.



          Use xrandr to Correct Configuration



          Delete your old x.org configuration (rm /etc/X11/xorg.conf) and set the output with xrandr.



          xrandr -q


          If this does not help, I recommend you start from scratch.



          Start from Scratch



          To make the troubleshooting process smoother let us start by purging all old configurations and drivers. As root(sudo) run these commands:



          apt purge "fglrx.*"
          rm /etc/X11/xorg.conf
          apt install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64


          Make sure your sources.list contains the contrib and non-free repositories like so:



          deb http://ftp.us.debian.org/debian/ stable main contrib non-free 


          If you needed to add them, do not forget to update apt, simply run as root(sudo) apt update. Next if you choose to use only the open source firmware for your card you will need to run this command:



          apt-get install firmware-linux-nonfree libgl1-mesa-dri xserver-xorg-video-ati


          And reboot your computer to initialize your graphics drivers and settings.



          Conclusion



          Please comment with any issues and I can update this answer to try and best correct your issue. Do not forget to reference the wiki on how to remove and install drivers. I believe this post on multi-monitor setups for Debian could help as well. Best of Luck!






          share|improve this answer


























          • Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

            – David Benoit
            Mar 19 '18 at 18:35













          • Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

            – kemotep
            Mar 19 '18 at 19:07











          • Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

            – David Benoit
            Mar 21 '18 at 3:32











          • Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

            – Nicolas
            Apr 21 '18 at 9:54













          • @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

            – kemotep
            Apr 23 '18 at 15:48
















          2














          fglrx is no longer supported in Debian 9. Your post appears related to this question previously asked in that they are reporting issues with missing fglrx. I think this forum post has a solution that could work for you. I am including links to the official Debian wiki on how to install open source and proprietary drivers. I recommend you only use the open source drivers.



          Use xrandr to Correct Configuration



          Delete your old x.org configuration (rm /etc/X11/xorg.conf) and set the output with xrandr.



          xrandr -q


          If this does not help, I recommend you start from scratch.



          Start from Scratch



          To make the troubleshooting process smoother let us start by purging all old configurations and drivers. As root(sudo) run these commands:



          apt purge "fglrx.*"
          rm /etc/X11/xorg.conf
          apt install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64


          Make sure your sources.list contains the contrib and non-free repositories like so:



          deb http://ftp.us.debian.org/debian/ stable main contrib non-free 


          If you needed to add them, do not forget to update apt, simply run as root(sudo) apt update. Next if you choose to use only the open source firmware for your card you will need to run this command:



          apt-get install firmware-linux-nonfree libgl1-mesa-dri xserver-xorg-video-ati


          And reboot your computer to initialize your graphics drivers and settings.



          Conclusion



          Please comment with any issues and I can update this answer to try and best correct your issue. Do not forget to reference the wiki on how to remove and install drivers. I believe this post on multi-monitor setups for Debian could help as well. Best of Luck!






          share|improve this answer


























          • Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

            – David Benoit
            Mar 19 '18 at 18:35













          • Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

            – kemotep
            Mar 19 '18 at 19:07











          • Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

            – David Benoit
            Mar 21 '18 at 3:32











          • Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

            – Nicolas
            Apr 21 '18 at 9:54













          • @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

            – kemotep
            Apr 23 '18 at 15:48














          2












          2








          2







          fglrx is no longer supported in Debian 9. Your post appears related to this question previously asked in that they are reporting issues with missing fglrx. I think this forum post has a solution that could work for you. I am including links to the official Debian wiki on how to install open source and proprietary drivers. I recommend you only use the open source drivers.



          Use xrandr to Correct Configuration



          Delete your old x.org configuration (rm /etc/X11/xorg.conf) and set the output with xrandr.



          xrandr -q


          If this does not help, I recommend you start from scratch.



          Start from Scratch



          To make the troubleshooting process smoother let us start by purging all old configurations and drivers. As root(sudo) run these commands:



          apt purge "fglrx.*"
          rm /etc/X11/xorg.conf
          apt install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64


          Make sure your sources.list contains the contrib and non-free repositories like so:



          deb http://ftp.us.debian.org/debian/ stable main contrib non-free 


          If you needed to add them, do not forget to update apt, simply run as root(sudo) apt update. Next if you choose to use only the open source firmware for your card you will need to run this command:



          apt-get install firmware-linux-nonfree libgl1-mesa-dri xserver-xorg-video-ati


          And reboot your computer to initialize your graphics drivers and settings.



          Conclusion



          Please comment with any issues and I can update this answer to try and best correct your issue. Do not forget to reference the wiki on how to remove and install drivers. I believe this post on multi-monitor setups for Debian could help as well. Best of Luck!






          share|improve this answer















          fglrx is no longer supported in Debian 9. Your post appears related to this question previously asked in that they are reporting issues with missing fglrx. I think this forum post has a solution that could work for you. I am including links to the official Debian wiki on how to install open source and proprietary drivers. I recommend you only use the open source drivers.



          Use xrandr to Correct Configuration



          Delete your old x.org configuration (rm /etc/X11/xorg.conf) and set the output with xrandr.



          xrandr -q


          If this does not help, I recommend you start from scratch.



          Start from Scratch



          To make the troubleshooting process smoother let us start by purging all old configurations and drivers. As root(sudo) run these commands:



          apt purge "fglrx.*"
          rm /etc/X11/xorg.conf
          apt install --reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64


          Make sure your sources.list contains the contrib and non-free repositories like so:



          deb http://ftp.us.debian.org/debian/ stable main contrib non-free 


          If you needed to add them, do not forget to update apt, simply run as root(sudo) apt update. Next if you choose to use only the open source firmware for your card you will need to run this command:



          apt-get install firmware-linux-nonfree libgl1-mesa-dri xserver-xorg-video-ati


          And reboot your computer to initialize your graphics drivers and settings.



          Conclusion



          Please comment with any issues and I can update this answer to try and best correct your issue. Do not forget to reference the wiki on how to remove and install drivers. I believe this post on multi-monitor setups for Debian could help as well. Best of Luck!







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 19 '18 at 17:33

























          answered Mar 19 '18 at 17:24









          kemotepkemotep

          2,4343721




          2,4343721













          • Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

            – David Benoit
            Mar 19 '18 at 18:35













          • Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

            – kemotep
            Mar 19 '18 at 19:07











          • Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

            – David Benoit
            Mar 21 '18 at 3:32











          • Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

            – Nicolas
            Apr 21 '18 at 9:54













          • @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

            – kemotep
            Apr 23 '18 at 15:48



















          • Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

            – David Benoit
            Mar 19 '18 at 18:35













          • Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

            – kemotep
            Mar 19 '18 at 19:07











          • Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

            – David Benoit
            Mar 21 '18 at 3:32











          • Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

            – Nicolas
            Apr 21 '18 at 9:54













          • @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

            – kemotep
            Apr 23 '18 at 15:48

















          Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

          – David Benoit
          Mar 19 '18 at 18:35







          Thank you for the suggestions, but no luck. I tried both, and still have the same output in the Xorg.0.log, and the same output on the screen. I'm reading the other threads you mentioned, but I believe I had tried most of what is in there. I will keep trying though. If you have any other suggestions, please let me know. (output from xrandr -q is here: xdal.org/~benoit/xrandr.out)

          – David Benoit
          Mar 19 '18 at 18:35















          Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

          – kemotep
          Mar 19 '18 at 19:07





          Try manually creating an x config like in this guide. This is tricky if reinstalling x and your drivers did not correct the issue.

          – kemotep
          Mar 19 '18 at 19:07













          Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

          – David Benoit
          Mar 21 '18 at 3:32





          Sadly, nothing worked. I gave up and bought a new video card. I got myself a Radeon RX 570 and it pretty much worked right away (a bit of tweaking to change from radeon to amdgpu, but that was all). It still sucks that I had to spend quite a bit of money to get this to work, but at least I can work again. Thanks for all the suggestions.

          – David Benoit
          Mar 21 '18 at 3:32













          Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

          – Nicolas
          Apr 21 '18 at 9:54







          Did anyone had success on using the radeon driver module on stretch? I have a Radeon HD 4350/4550 and had no luck like David. I think, this module simply is broken....

          – Nicolas
          Apr 21 '18 at 9:54















          @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

          – kemotep
          Apr 23 '18 at 15:48





          @Nicolas, I am currently using the latest radeon drive module but for my RX 480. According to the documentation your card should be supported. what is the output of glxinfo | grep "OpenGL renderer"?

          – kemotep
          Apr 23 '18 at 15:48


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432106%2fdebian-9-upgrade-breaks-radeon-triple-monitor-setup%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          濃尾地震

          How to rewrite equation of hyperbola in standard form

          No ethernet ip address in my vocore2