search for: v3900

Well, I got my user back to being able to use his system, but I've still got one issue: it's running on the VESA driver - there is *no* Catalyst build for this monitor, for CentOS 7. From a lot of googling, nothing's been done since the summer of '14 (lspci reports it as a FirePro V3900). Any thoughts, or pointers, as to if/how I can get X - he's running KDE - to see the full width of the monitor, not just about 4" less, or is that not possible with the VESA driver? mark

...to being able to use his system, but I've still >> got one issue: it's running on the VESA driver - there is*no* Catalyst >> build for this monitor, for CentOS 7. From a lot of googling, nothing's >> been done since the summer of '14 (lspci reports it as a FirePro V3900). >> >> Any thoughts, or pointers, as to if/how I can get X - he's running KDE - >> to see the full width of the monitor, not just about 4" less, or is that >> not possible with the VESA driver? > > did you try these? > http://support.amd.com/en-us/download...

...to >> change it back to not recognizing the full width of the screen via the >> control ctr, because when it did, everything was distorted - circles >> were ovals, etc. I suppose I'll get around to writing him a xorg.conf >> at some time. > > Mark, with the FirePro V3900 the 'radeon' driver should be loading, not > the VESA one. Is xorg-x11-drv-ati installed? I am running a FirePro Yup: rpm -qa | grep drv-ati xorg-x11-drv-ati-7.4.0-1.20140918git56c7fb8.el7.x86_64 Note that, as I said earlier, it is over a year old. > M7820 in my Dell Precision M6...

...link). Then he had to > change it back to not recognizing the full width of the screen via the > control ctr, because when it did, everything was distorted - circles > were ovals, etc. I suppose I'll get around to writing him a xorg.conf > at some time. Mark, with the FirePro V3900 the 'radeon' driver should be loading, not the VESA one. Is xorg-x11-drv-ati installed? I am running a FirePro M7820 in my Dell Precision M6500, and everything 'Just Works' with the xorg-x11-drv-ati package (and its dependencies) installed. I even get triple monitor support a...

...> >>> still got one issue: it's running on the VESA driver - there is > >>> *no* Catalyst build for this monitor, for CentOS 7. From a lot of > >>> googling, nothing's been done since the summer of '14 (lspci > >>> reports it as a FirePro V3900). > >>> > >>> Any thoughts, or pointers, as to if/how I can get X - he's running KDE > >>> - to see the full width of the monitor, not just about 4" less, or is > >>> that not possible with the VESA driver? <SNIP> > Btw, I spoke to D...

...y user back to being able to use his system, but I've still > got one issue: it's running on the VESA driver - there is*no* Catalyst > build for this monitor, for CentOS 7. From a lot of googling, nothing's > been done since the summer of '14 (lspci reports it as a FirePro V3900). > > Any thoughts, or pointers, as to if/how I can get X - he's running KDE - > to see the full width of the monitor, not just about 4" less, or is that > not possible with the VESA driver? did you try these? http://support.amd.com/en-us/download/desktop?os=Linux+x86 -- j...

...system, but I've >>> still got one issue: it's running on the VESA driver - there is >>> *no* Catalyst build for this monitor, for CentOS 7. From a lot of >>> googling, nothing's been done since the summer of '14 (lspci >>> reports it as a FirePro V3900). >>> >>> Any thoughts, or pointers, as to if/how I can get X - he's running KDE >>> - to see the full width of the monitor, not just about 4" less, or is >>> that not possible with the VESA driver? >> >> did you try these? >> http://su...

...t;> still got one issue: it's running on the VESA driver - there is >> >>> *no* Catalyst build for this monitor, for CentOS 7. From a lot of >> >>> googling, nothing's been done since the summer of '14 (lspci >> >>> reports it as a FirePro V3900). >> >>> >> >>> Any thoughts, or pointers, as to if/how I can get X - he's running >> >>> KDE - to see the full width of the monitor, not just about 4" less, >> >>> or is that not possible with the VESA driver? > <SNIP> &...