Re: [DNG] Update successful but video card issue
Following up on my graphics card issues, I bought an MSI Geforce GTX 1660 card, deleted a couple of files which were the X AMD drivers (very difficult to delete the packages; seemed to want to delete most of my X system), and loaded the proprietary nvidia driver from the non-free repository. Nouveau did not seem to work. Had to add contrib, but it worked like a charm in beowulf. Took maybe an hour vs the days I struggled with the older AMD card! It did not work under ascii. The newest nvidia driver there is 390, and it took 418 to make this thing work under beowulf. Works fine, 4K video flawless, and only draws 10W normally. Amazon refused to take back the AMD card because I was a couple of days beyond the 30 day limit. They said they would, but never sent me the RMA email they promised, and then were uncontactable. If I ever buy another AMD card, I'll be sure to have time to do all the configuration in two weeks so I can send it back. --Tim On Thursday, February 6, 2020, 6:20:08 PM EST, Tim Wallace via Dng wrote: Hi Roland-- I do think that you know the most about the issues with this card...but remember, when I run mpv to display 4K video at 60fps, *full screen* it works perfectly, and does not drop a single frame. I assume we're bypassing the Xorg software here. Under X, things just do not work as well. But the correct advice is to dispense with this card. It seems like a nice idea to use a workstation card for 10-bit color support and save energy, but using a gamer card shouldn't kill you power-wise if you're not gaming. Plus some of the RX 560/570 or Nvidia 1050/1060 cards seem able to drive a couple of 4K monitors, if necessary. I do have a 750W PS so no trouble there but not interested in burning much of that... --Tim On Thursday, February 6, 2020, 9:25:54 AM UTC, Roland Gebhard Sidler wrote: Hi Andreas, Tim, Didier,... @Tim: it's definitely not the radeon driver only, that causes the flickering - I tried the radeon and the amdgpu-drivers separately with the same problem appearing.B.t.w., I am working with the default kernel 4.19 in Devuan Beowulf. I guess, the W4100 as well as the WX4100 reach their limits while displaying a 4k video at 60fps... Thank you for your interest and kind answers! Sincerely Roland Am 5 Feb 2020 20:37:27 +0100 (CET) Von Tim Wallace via Dng : Hi Andreas-- I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! I've got a pile of displayport cables should I want to switch out one of those, and one other 4K monitor as well. I'm very surprised you can get the Xorg amdgpu driver to work with the amdgpu kernel module. I guess the newest I've used is 5.4.0 from backports, so conceivably 5.4.7 is different, but keep in mind this is a video card first released in 2015, so rather than newer being better, perhaps newer is less compatible as old cards are (silently?) deprecated in some way! I'm taking steps to return this thing, and considering a more typical gaming card such as an RX 560 or 570 or an Nvidia 1050 or 1060. I don't do gaming, but the video editing should be OK with one of those. The more I look into the AMD cards, the more people seem to have trouble finding drivers that work well, even on Windows. I might try them one more time. It's great to support LInux better than Nvidia does in theory, but in practice ... ? I also never quite figured out how to run the proprietary AMD drivers under Devuan. I assume that compiling a kernel which matches the Ubuntu version might do it, but that kind of defeats the purpose of buying a card well-supported in Linux! Downloading an Nvidia driver is easier than that! Thanks to everybody in DNG who gave me so much good advice, though. I'm sticking with Devuan no matter what since all my systemd issues are gone! --Tim On Wednesday, February 5, 2020, 6:20:28 PM UTC, Andreas Messer wrote: Hi Tim, On Sat, Feb 01, 2020 at 04:44:07PM +, Tim Wallace via Dng wrote: > Hi Andreas-- > lspci shows this:01:00.0 VGA compatible controller: Advanced Micro > Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the > Cape Verde but not the Southern Island. I think all Cape Verde are > that, though. Yes, Cap Verde is Southern Island generation. So we basically have the same card. > The old radeon kernel module paired with the Xorg radeon driver is the > one that gives random annoying flashes. I can almost live with them, but > under virtualbox win7 which my wife runs once a week it is unbelievably > flashy! Maybe it is something completely different: At work I had similar issues with my monitor attached to the notebook dock. From time to time, the monitor turned black for short time and immediately recovered the image. It
Re: [DNG] Update successful but video card issue
Hi Roland-- I do think that you know the most about the issues with this card...but remember, when I run mpv to display 4K video at 60fps, *full screen* it works perfectly, and does not drop a single frame. I assume we're bypassing the Xorg software here. Under X, things just do not work as well. But the correct advice is to dispense with this card. It seems like a nice idea to use a workstation card for 10-bit color support and save energy, but using a gamer card shouldn't kill you power-wise if you're not gaming. Plus some of the RX 560/570 or Nvidia 1050/1060 cards seem able to drive a couple of 4K monitors, if necessary. I do have a 750W PS so no trouble there but not interested in burning much of that... --Tim On Thursday, February 6, 2020, 9:25:54 AM UTC, Roland Gebhard Sidler wrote: Hi Andreas, Tim, Didier,... @Tim: it's definitely not the radeon driver only, that causes the flickering - I tried the radeon and the amdgpu-drivers separately with the same problem appearing.B.t.w., I am working with the default kernel 4.19 in Devuan Beowulf. I guess, the W4100 as well as the WX4100 reach their limits while displaying a 4k video at 60fps... Thank you for your interest and kind answers! Sincerely Roland Am 5 Feb 2020 20:37:27 +0100 (CET) Von Tim Wallace via Dng : Hi Andreas-- I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! I've got a pile of displayport cables should I want to switch out one of those, and one other 4K monitor as well. I'm very surprised you can get the Xorg amdgpu driver to work with the amdgpu kernel module. I guess the newest I've used is 5.4.0 from backports, so conceivably 5.4.7 is different, but keep in mind this is a video card first released in 2015, so rather than newer being better, perhaps newer is less compatible as old cards are (silently?) deprecated in some way! I'm taking steps to return this thing, and considering a more typical gaming card such as an RX 560 or 570 or an Nvidia 1050 or 1060. I don't do gaming, but the video editing should be OK with one of those. The more I look into the AMD cards, the more people seem to have trouble finding drivers that work well, even on Windows. I might try them one more time. It's great to support LInux better than Nvidia does in theory, but in practice ... ? I also never quite figured out how to run the proprietary AMD drivers under Devuan. I assume that compiling a kernel which matches the Ubuntu version might do it, but that kind of defeats the purpose of buying a card well-supported in Linux! Downloading an Nvidia driver is easier than that! Thanks to everybody in DNG who gave me so much good advice, though. I'm sticking with Devuan no matter what since all my systemd issues are gone! --Tim On Wednesday, February 5, 2020, 6:20:28 PM UTC, Andreas Messer wrote: Hi Tim, On Sat, Feb 01, 2020 at 04:44:07PM +, Tim Wallace via Dng wrote: > Hi Andreas-- > lspci shows this:01:00.0 VGA compatible controller: Advanced Micro > Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the > Cape Verde but not the Southern Island. I think all Cape Verde are > that, though. Yes, Cap Verde is Southern Island generation. So we basically have the same card. > The old radeon kernel module paired with the Xorg radeon driver is the > one that gives random annoying flashes. I can almost live with them, but > under virtualbox win7 which my wife runs once a week it is unbelievably > flashy! Maybe it is something completely different: At work I had similar issues with my monitor attached to the notebook dock. From time to time, the monitor turned black for short time and immediately recovered the image. It seemed to align with some other employees switching on or off some devices in the first place, but in the end turned out to be a loosely fitted display port plug. Could it be the cable? I also heard that in some cases a bad or insufficient display port cable led to unstable monitor operation. It could be also a DP link training issue I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! > The newer amdgpu module fails to work with the Xorg amdgpu driver. > This is with ascii, beowulf, and kernels 4.9, 4.19, and 5.4. I'm able > to get them installed, they just won't start. The Xorg amdgpu version > is 18.1, from late 2018, and a 19.1 is out, from 2019, but claims only > minor tweaks. I'm not thinking it's worth bothering to try to compile > that. Hmm strange. I was using standard beowulf Xorg package with self compiled
Re: [DNG] Update successful but video card issue
Hi Andreas, Tim, Didier,... @Tim: it's definitely not the radeon driver only, that causes the flickering - I tried the radeon and the amdgpu-drivers separately with the same problem appearing.B.t.w., I am working with the default kernel 4.19 in Devuan Beowulf. I guess, the W4100 as well as the WX4100 reach their limits while displaying a 4k video at 60fps... Thank you for your interest and kind answers! Sincerely Roland Am 5 Feb 2020 20:37:27 +0100 (CET) Von Tim Wallace via Dng : Hi Andreas-- I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! I've got a pile of displayport cables should I want to switch out one of those, and one other 4K monitor as well. I'm very surprised you can get the Xorg amdgpu driver to work with the amdgpu kernel module. I guess the newest I've used is 5.4.0 from backports, so conceivably 5.4.7 is different, but keep in mind this is a video card first released in 2015, so rather than newer being better, perhaps newer is less compatible as old cards are (silently?) deprecated in some way! I'm taking steps to return this thing, and considering a more typical gaming card such as an RX 560 or 570 or an Nvidia 1050 or 1060. I don't do gaming, but the video editing should be OK with one of those. The more I look into the AMD cards, the more people seem to have trouble finding drivers that work well, even on Windows. I might try them one more time. It's great to support LInux better than Nvidia does in theory, but in practice ... ? I also never quite figured out how to run the proprietary AMD drivers under Devuan. I assume that compiling a kernel which matches the Ubuntu version might do it, but that kind of defeats the purpose of buying a card well-supported in Linux! Downloading an Nvidia driver is easier than that! Thanks to everybody in DNG who gave me so much good advice, though. I'm sticking with Devuan no matter what since all my systemd issues are gone! --Tim On Wednesday, February 5, 2020, 6:20:28 PM UTC, Andreas Messer wrote: Hi Tim,On Sat, Feb 01, 2020 at 04:44:07PM +, Tim Wallace via Dng wrote:> Hi Andreas--> lspci shows this:01:00.0 VGA compatible controller: Advanced Micro> Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the> Cape Verde but not the Southern Island. I think all Cape Verde are> that, though.Yes, Cap Verde is Southern Island generation. So we basically have thesame card. > The old radeon kernel module paired with the Xorg radeon driver is the> one that gives random annoying flashes. I can almost live with them, but> under virtualbox win7 which my wife runs once a week it is unbelievably> flashy!Maybe it is something completely different: At work I had similar issueswith my monitor attached to the notebook dock. From time to time, themonitor turned black for short time and immediately recovered the image.It seemed to align with some other employees switching on or off somedevices in the first place, but in the end turned out to be a looselyfitted display port plug. Could it be the cable? I also heard that insome cases a bad or insufficient display port cable led to unstablemonitor operation. It could be also a DP link training issue I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! > The newer amdgpu module fails to work with the Xorg amdgpu driver. > This is with ascii, beowulf, and kernels 4.9, 4.19, and 5.4. I'm able> to get them installed, they just won't start. The Xorg amdgpu version> is 18.1, from late 2018, and a 19.1 is out, from 2019, but claims only> minor tweaks. I'm not thinking it's worth bothering to try to compile> that.Hmm strange. I was using standard beowulf Xorg package with self compiledkernel 5.4.7's amdgpu module here without any issues. cheers,Andreas -- gnuPG keyid: 8C2BAF51fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 ___Dng mailing listDng@lists.dyne.orghttps://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi Andreas-- I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! I've got a pile of displayport cables should I want to switch out one of those, and one other 4K monitor as well. I'm very surprised you can get the Xorg amdgpu driver to work with the amdgpu kernel module. I guess the newest I've used is 5.4.0 from backports, so conceivably 5.4.7 is different, but keep in mind this is a video card first released in 2015, so rather than newer being better, perhaps newer is less compatible as old cards are (silently?) deprecated in some way! I'm taking steps to return this thing, and considering a more typical gaming card such as an RX 560 or 570 or an Nvidia 1050 or 1060. I don't do gaming, but the video editing should be OK with one of those. The more I look into the AMD cards, the more people seem to have trouble finding drivers that work well, even on Windows. I might try them one more time. It's great to support LInux better than Nvidia does in theory, but in practice ... ? I also never quite figured out how to run the proprietary AMD drivers under Devuan. I assume that compiling a kernel which matches the Ubuntu version might do it, but that kind of defeats the purpose of buying a card well-supported in Linux! Downloading an Nvidia driver is easier than that! Thanks to everybody in DNG who gave me so much good advice, though. I'm sticking with Devuan no matter what since all my systemd issues are gone! --Tim On Wednesday, February 5, 2020, 6:20:28 PM UTC, Andreas Messer wrote: Hi Tim, On Sat, Feb 01, 2020 at 04:44:07PM +, Tim Wallace via Dng wrote: > Hi Andreas-- > lspci shows this:01:00.0 VGA compatible controller: Advanced Micro > Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the > Cape Verde but not the Southern Island. I think all Cape Verde are > that, though. Yes, Cap Verde is Southern Island generation. So we basically have the same card. > The old radeon kernel module paired with the Xorg radeon driver is the > one that gives random annoying flashes. I can almost live with them, but > under virtualbox win7 which my wife runs once a week it is unbelievably > flashy! Maybe it is something completely different: At work I had similar issues with my monitor attached to the notebook dock. From time to time, the monitor turned black for short time and immediately recovered the image. It seemed to align with some other employees switching on or off some devices in the first place, but in the end turned out to be a loosely fitted display port plug. Could it be the cable? I also heard that in some cases a bad or insufficient display port cable led to unstable monitor operation. It could be also a DP link training issue I do believe that it can be hardware-related, but only to the video card. I've been running this computer, the same 4K monitor, and the same displayport cable for three years without any problems, except limited graphics performance due to the built-in Intel graphics! > The newer amdgpu module fails to work with the Xorg amdgpu driver. > This is with ascii, beowulf, and kernels 4.9, 4.19, and 5.4. I'm able > to get them installed, they just won't start. The Xorg amdgpu version > is 18.1, from late 2018, and a 19.1 is out, from 2019, but claims only > minor tweaks. I'm not thinking it's worth bothering to try to compile > that. Hmm strange. I was using standard beowulf Xorg package with self compiled kernel 5.4.7's amdgpu module here without any issues. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi Tim, On Sat, Feb 01, 2020 at 04:44:07PM +, Tim Wallace via Dng wrote: > Hi Andreas-- > lspci shows this:01:00.0 VGA compatible controller: Advanced Micro > Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the > Cape Verde but not the Southern Island. I think all Cape Verde are > that, though. Yes, Cap Verde is Southern Island generation. So we basically have the same card. > The old radeon kernel module paired with the Xorg radeon driver is the > one that gives random annoying flashes. I can almost live with them, but > under virtualbox win7 which my wife runs once a week it is unbelievably > flashy! Maybe it is something completely different: At work I had similar issues with my monitor attached to the notebook dock. From time to time, the monitor turned black for short time and immediately recovered the image. It seemed to align with some other employees switching on or off some devices in the first place, but in the end turned out to be a loosely fitted display port plug. Could it be the cable? I also heard that in some cases a bad or insufficient display port cable led to unstable monitor operation. It could be also a DP link training issue > The newer amdgpu module fails to work with the Xorg amdgpu driver. > This is with ascii, beowulf, and kernels 4.9, 4.19, and 5.4. I'm able > to get them installed, they just won't start. The Xorg amdgpu version > is 18.1, from late 2018, and a 19.1 is out, from 2019, but claims only > minor tweaks. I'm not thinking it's worth bothering to try to compile > that. Hmm strange. I was using standard beowulf Xorg package with self compiled kernel 5.4.7's amdgpu module here without any issues. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Le 01/02/2020 à 15:53, g4sra via Dng a écrit : On 01/02/2020 10:11, Didier Kryn wrote: Le 31/01/2020 à 13:50, g4sra via Dng a écrit : Do not be fooled into thinking blacklisting stops a module from being loaded, ensure you rebuild the initrd\initramfs without the driver. Dunno if graphics driver modules are now part of the initrd/initramfs, but this look like crazy. Yes, and Yes. After all, everyone knows a Linux box wont boot unless you have a graphical splashscreen! (sarcasm, for non-engish natives). Grub does it one way then Linux joins in and does it another...trying to identify graphics related errors at/after boot can be a PITA. I played with these splash screens 15 years ago but found it a big effort for pure futility. These splash screens aren't by default on Debian nor Grub and I've never seen them for long. Do you mean the graphics drivers are in initrd even if you don't require a splash screen ? Even for a minimal non-graphical system? Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi Andreas-- lspci shows this:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100]which shows the Cape Verde but not the Southern Island. I think all Cape Verde are that, though. The old radeon kernel module paired with the Xorg radeon driver is the one that gives random annoying flashes. I can almost live with them, but under virtualbox win7 which my wife runs once a week it is unbelievably flashy! The newer amdgpu module fails to work with the Xorg amdgpu driver. This is with ascii, beowulf, and kernels 4.9, 4.19, and 5.4. I'm able to get them installed, they just won't start. The Xorg amdgpu version is 18.1, from late 2018, and a 19.1 is out, from 2019, but claims only minor tweaks. I'm not thinking it's worth bothering to try to compile that. I'm pretty sure Roland is the biggest expert here on this card! A hardware issue with timing could be there. Interestingly enough a similar ASRock motherboard to mine was used in online benchmarks for this card. That certainly doesn't prove that my motherboard would work with it, just that I'm not completely crazy ;) --Tim On Saturday, February 1, 2020, 4:16:53 PM UTC, Andreas Messer wrote: On Fri, Jan 31, 2020 at 11:03:24AM +, R. G. Sidler wrote: > > Hi Tim, Ludovic and Andreas. > > I installed only the amdgpu-driver. Since I always start with a naked > base install, I never care about blacklisting any drivers, because I > just don't install them Well, the drm (nvidia/amd/..) kernel modules are all installed with a single kernel package so you can only decide which to install by building your own kernel package. Blacklisting is the only way to force them not to load. But I assume you know that, since you're using Debian/Devuan already :) Maybe another thing: Since the W4100 seems to use the Cap Verde / Souther Island GPU kind (Can you confirm this, using lspci -l e.g.?) you have the option of using two different kernel drivers with a recent linux kernel: - radeon: this is the older/mature one (the default one) - amdgpu: this is the newer one which might have flaws with SI chipset You can choose them by setting some kernel module parameters (I did this, through /etc/default/grub recently to try something) And maybe a clarification: The graphics driver is divided into two parts: the kernel module and the xorg driver. The xorg driver in beowulf should be able to play with both kernel drivers, I think the amd proprietary xorg driver only works with the amdgpu kernel module. > @Andreas I decided to install a dedicated AMD workstation graphics card, > since I only do workstation stuff on my Thinkstation > > I prefer a very stable signal over high performance. Did you observe any difference? I mean, the transmission of data between graphics card and display should be digital nowadays. (I owned a FireGL2 a long while ago but remind only the negative aspects of it) cheers Andreas___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
On Fri, Jan 31, 2020 at 11:03:24AM +, R. G. Sidler wrote: > > Hi Tim, Ludovic and Andreas. > > I installed only the amdgpu-driver. Since I always start with a naked > base install, I never care about blacklisting any drivers, because I > just don't install them Well, the drm (nvidia/amd/..) kernel modules are all installed with a single kernel package so you can only decide which to install by building your own kernel package. Blacklisting is the only way to force them not to load. But I assume you know that, since you're using Debian/Devuan already :) Maybe another thing: Since the W4100 seems to use the Cap Verde / Souther Island GPU kind (Can you confirm this, using lspci -l e.g.?) you have the option of using two different kernel drivers with a recent linux kernel: - radeon: this is the older/mature one (the default one) - amdgpu: this is the newer one which might have flaws with SI chipset You can choose them by setting some kernel module parameters (I did this, through /etc/default/grub recently to try something) And maybe a clarification: The graphics driver is divided into two parts: the kernel module and the xorg driver. The xorg driver in beowulf should be able to play with both kernel drivers, I think the amd proprietary xorg driver only works with the amdgpu kernel module. > @Andreas I decided to install a dedicated AMD workstation graphics card, > since I only do workstation stuff on my Thinkstation > > I prefer a very stable signal over high performance. Did you observe any difference? I mean, the transmission of data between graphics card and display should be digital nowadays. (I owned a FireGL2 a long while ago but remind only the negative aspects of it) cheers Andreas signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
On 01/02/2020 10:11, Didier Kryn wrote: > Le 31/01/2020 à 13:50, g4sra via Dng a écrit : >> Do not be fooled into thinking blacklisting stops a module from being >> loaded, ensure you rebuild the initrd\initramfs without the driver. > > Dunno if graphics driver modules are now part of the initrd/initramfs, > but this look like crazy. Yes, and Yes. After all, everyone knows a Linux box wont boot unless you have a graphical splashscreen! (sarcasm, for non-engish natives). Grub does it one way then Linux joins in and does it another...trying to identify graphics related errors at/after boot can be a PITA. >The only purpose of initrd/initramfs is to mount the root filesytem and >ancilary filesystems /proc, /sys, /dev, /run. If only I had $1 for every time I have said that, but still the package builders insist on forcing 'depend'ancies on everything. > Therefore the only drivers needed in intrd/initramfs are those necessary to > perform these mounts. And they should better be statically linked than in the > form of modules because it consumes less memory and less cpu time. > > Didier > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Le 31/01/2020 à 13:50, g4sra via Dng a écrit : Do not be fooled into thinking blacklisting stops a module from being loaded, ensure you rebuild the initrd\initramfs without the driver. Dunno if graphics driver modules are now part of the initrd/initramfs, but this look like crazy. The only purpose of initrd/initramfs is to mount the root filesytem and ancilary filesystems /proc, /sys, /dev, /run. Therefore the only drivers needed in intrd/initramfs are those necessary to perform these mounts. And they should better be statically linked than in the form of modules because it consumes less memory and less cpu time. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
My latest adventures in AMD drivers: I tried the kernel 5.4.0 from the backports under beowulf. I forced the backports version upgrade for firmware-amd-graphics; there was no backports version of xserver-xorg-video-amdgpu. It worked, and seemed to perhaps flash a little less than previously. It loaded kernel modules amdgpu and radeon, and used radeon for the X server driver. I shut down slim, and tried Xorg --configure which called for the amdgpu driver, as expected. Starting the server with the amdgpu xorg.conf failed with the usual message about 2.50.0 being incompatible with 3.x.x, which is a radeon/amdgpu incompatibility, I believe. I blacklisted radeon, and rebooted, and indeed only the amdgpu module was loaded. Trying to run the X server with amdgpu I got another fatal message (which I have seen before): [ 34.842] (II) AMDGPU: Driver for AMD Radeon: All GPUs supported by the amdgpu kernel driver [ 34.842] (II) AMDGPU(0): [KMS] drm report modesetting isn't supported. [ 34.842] (II) AMDGPU(1): [KMS] drm report modesetting isn't supported. I don't have any trouble loading the amdgpu driver, it just doesn't work! I believe lsmod when it says that only amdgpu is loaded! Trying to track down that specific error message on the web usually just leads you to "upgrade your driver" solutions. I'm pretty sure that the AMD proprietary driver will complain about my kernel version, but after Roland's report, I am very doubtful that it would make any difference. Like Roland, I'm more interested in resolution and stability than speed. I do have a couple of 4K monitors but only one is in use right now on this system. Thanks for all the help! [If I had to run a systemd-based distribution to make this thing work I'd definitely toss it in the trash immediately ;) ] Most likely outcome is I try to send this thing back to Amazon. If that fails, a blistering review will probably follow ;) On Friday, January 31, 2020, 4:19:22 PM UTC, R. G. Sidler wrote: Ahmad, of course, I did. Sincerely Roland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Ahmad, of course, I did. Sincerely Roland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
1) Dont bin your video card, it is unlikely to help in the long run. On my (cough! yes I know but I did have valid reasons) Fedora system, I have been battling with Nvidia & Xorg drivers for years, they are certainly no better than AMD support wise. My system is currently broken, turns out the library Nvidia distribute is too old to work properly alongside the latest Mesa upgrade, so using the nouveau driver until Nvidia update it. 2) Perform each step *manually* and keep an eagle eye on the console output and the logs. When troubleshooting an issue I now always revert my configuration so that *everything* graphics related is performed manually either as root or a user from the VT command line, each step can then be validated and verified. Do not be fooled into thinking blacklisting stops a module from being loaded, ensure you rebuild the initrd\initramfs without the driver. Nine times out of ten if I can figure out what is breaking it can be fixed (e.g. I could choose to wind my Mesa library back). I used to like WFW 3.11 through to Windows Millenium for the same reason, boot to a VT prompt to sort the problem! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Anno domini 11:03:24 Fri, 31 Jan 2020 + (UTC) R. G. Sidler scripsit: > > Hi Tim, Ludovic and Andreas. > > I installed only the amdgpu-driver. Since I always start with a naked base > install, I never care about blacklisting any drivers, because I just don't > install them > > @Andreas I decided to install a dedicated AMD workstation graphics card, > since I only do workstation stuff on my Thinkstation > > I prefer a very stable signal over high performance. > > Sincerely > > > Roland > > You checked, that the firmware is present? -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi Tim, Ludovic and Andreas. I installed only the amdgpu-driver. Since I always start with a naked base install, I never care about blacklisting any drivers, because I just don't install them @Andreas I decided to install a dedicated AMD workstation graphics card, since I only do workstation stuff on my Thinkstation I prefer a very stable signal over high performance. Sincerely Roland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hello Tim, On Wed, Jan 29, 2020 at 10:05:54PM +, Tim Wallace via Dng wrote: > I have been happily running ascii but upgraded from my Intel built-in > graphics to an AMD FirePro W4100 because I do a lot of 4K video editing, > but no game-playing, and thought this 50W card would save energy and > work well with 4K. There is a nearly identical Nvidia card, but I > decided to support AMD, for easier Linux support, which has not been my > experience! > [...] > Motherboard ASRock Z97 Extreme6, i7-4790K, 16 GB, latest Bios 2.80 > [...] In the hope this won't disappoint you too much, but in my opinion you should have better invested the money into more memory or a fast SSD. The main purpose of AMD FirePro as well as the NVidia Quadro Cards are multi monitor configuration (They have lots of connectors) Do you have multiple monitors? If you compare their specs with the "gamer" cards you'll see that you get much less gpu performance for the same pricing. Their power consumption is low, because they are typically build from the lowest performance chips of a series, Often even clocked down variants. I suppose the W4100 to be something like an R7 250E card, which is actually the same as an Radeon HD7750 (Like mine, 5 years old). If have a single monitor, you'd better use a recent gamer card. You should remind, that the "Power Consumption" is the maximum value the card will take under full load. Typical GPUs have 8-15 W during Desktop use. My current favorite would be an Radeon RX550X. Its twice as fast as the W4100 but costs only about 90€. Also current cards have better Video decoding and Encoding capabilities than the old ones. I suppose the integrated GPU of the i7 can also drive a 4K Display provided the Mainboard has Display Port Connector. It should work without issues on any current linux distribution. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hello Tim, > Thanks so much for your helpful (and sobering) replies! If I had spent > $50 (instead of $260) for this card, I would have already trashed it and > just bought the Nvidia one (Quadro K1200)! Clearly AMD is not a panacea > for Linux video cards! I may still do that, or maybe try to return it.) > AMDGPU drivers usually works great on Linux, as they are the same drivers shipped by Amd minus the proprietary stuff. radeon is the old opensource project, nobody really should use it anymore unless amdgpu isn't working for them. A work around for your problem could be to remove the other drivers (xserver-xorg-video-ati and xserver-xorg-video-radeon), leaving only amdgpu to be loaded. Make sure firmware-amd-graphics is installed, backports if possible. Don't forget to install the backports of mesa, to get the latest available drivers. ASCII uses pretty old software, and in your case you really want something more recent if not the most recent. When it comes to drivers and the kernel, there is almost no reason for anybody to not use backports. > Ludovic, I don't have the card installed right now, but the family is > VERDE as seen in this old Xorg output: (--) RADEON(0): Chipset: "VERDE" > (ChipID = 0x682c) > CAPE VERDE is of the Southern Islands family. The amdgpu driver supports SI and newer families' video cards. You should be good. Ludovic signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi temp, The 5.4 kernel is also available through the backports if you're running Beowulf. Ludovic On 31/01/20 03:20, tempforever wrote: > I have no idea whether it will help your particular problem, but I can > report that I've successfully built and run run 5.4 on ascii (if that > was a question). > > Tim Wallace via Dng wrote: >> I have played with the CMDLINE stuff, and blacklisting, to no avail. >> I wonder if compiling a 5.4 kernel would solve my graphics problem, >> and work with beowulf and/or asci? > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
On Fri, Jan 31, 2020 at 02:28:09AM +, Tim Wallace via Dng wrote: > Yes it was, and thanks for that data point. I'm more likely to try it on > beowulf, but sounds like there are no major low-level subsystem > incompatibilities. > --Tim The 5.4.14 kernel compiles and runs just fine on Beowulf. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Yes it was, and thanks for that data point. I'm more likely to try it on beowulf, but sounds like there are no major low-level subsystem incompatibilities. --Tim On Friday, January 31, 2020, 2:20:41 AM UTC, tempforever wrote: I have no idea whether it will help your particular problem, but I can report that I've successfully built and run run 5.4 on ascii (if that was a question). Tim Wallace via Dng wrote: > I have played with the CMDLINE stuff, and blacklisting, to no avail. I > wonder if compiling a 5.4 kernel would solve my graphics problem, and work > with beowulf and/or asci? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
I have no idea whether it will help your particular problem, but I can report that I've successfully built and run run 5.4 on ascii (if that was a question). Tim Wallace via Dng wrote: I have played with the CMDLINE stuff, and blacklisting, to no avail. I wonder if compiling a 5.4 kernel would solve my graphics problem, and work with beowulf and/or asci? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Update successful but video card issue
Hi Ludovic and Roland-- Thanks so much for your helpful (and sobering) replies! If I had spent $50 (instead of $260) for this card, I would have already trashed it and just bought the Nvidia one (Quadro K1200)! Clearly AMD is not a panacea for Linux video cards! I may still do that, or maybe try to return it.) Roland, what kernel modules are you running (radeon, amdgpu, both?) and what X server driver? I get flashes much more often with X driver radeon, but FS video with mpv runs smoothly! Ludovic, I don't have the card installed right now, but the family is VERDE as seen in this old Xorg output: (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x682c) I'm 99% sure that the amdgpu drivers are what I need for this card, which is a 2015 card. I'm just amazed that a company that supports Linux so well would have a card this old failing this badly! I have looked at many of the links you mention, and tried to blacklist the radeon module but without success. I've tried many things, so I forget the exact symptoms of that failure. After reading your replies, I re-looked at some of my other links, and found the following interesting one at https://unix.stackexchange.com/questions/444068/how-to-switch-drivers-from-radeon-to-amdgpu Note at the bottom it states: I've been doing a lot of digging around, and seems linux kernel 4.13.0 doesn't have driver support I think for my card. So I tested kernel 4.16.0-041600-generic, which loaded the amdgpudrmfb driver along with amdgpu. Also to get x server working I had to add some device specific settings for the amdgpu in xorg.conf after doing X -showopts in console TTY1 (ctrl+alt+F1) – cryptoboy May 17 '18 at 5:24 Additionally and I'm not sure if it was already blacklisted but I noticed in /etc/modprobe.d/blacklist-framebuffer.conf that radeonfb was blacklisted. I was thinking maybe the amdgpu-pro package did that ? – cryptoboy May 17 '18 at 5:26 I figured out why it stops booting past the point of loading the amdgpudrmfb, as seen in the image I posted, due to the fact I needed to pass to the kernel the following parameters: GRUB_CMDLINE_LINUX_DEFAULT="radeon.si_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 radeon.cik_support=0" However, this goes to a blank screen, until I put in the xorg.conf configuration, which then everything loads fine. – cryptoboy May 17 '18 at 5:36 I have played with the CMDLINE stuff, and blacklisting, to no avail. I wonder if compiling a 5.4 kernel would solve my graphics problem, and work with beowulf and/or asci? I find it pretty hilarious that I picked this card over the Nvidia for minimum hassle out-of-the-box, have spent a couple of full days failing to get it working, and am now talking about compiling kernels! When you've used Linux since 1992, you expect that you can solve any problem, but it's not always true! Not sure what I'll do going forward, but thankful for the very helpful DNG list! --Tim On Thursday, January 30, 2020, 7:10:49 AM UTC, Roland Gebhard Sidler wrote: Hi Ludovic,hi Tim, actually, I do have the same issues. I am running a Thinkstation P520Cwith a Radeon Firepro W4100 with a 4K Benq PD3200U. I literally spent weeks of searching information about this problem to get rid of the flickering,but without any success. I tried several distributions (Linux Mint, Devuan and actually MXLinux) without any difference. And I also tried the proprietary drivers, which didn't change anything,installing it after the open driver and by installing it as first driver. I even tried various connections (HDMI, DP). The problem appears irregularely and more frequently whilest watching videos.There is a slight difference between watching 4k/30fps and 4k/60fps, wheras 4k/60fpsshows less flickering of the whole screen than 4k/30fps. And after having watched a 4k/60fps video for some seconds,the screen won't flicker at all for several minutes. My guess is a timing problem of the AMD Firepro W4100. Might be, using a AMD Radeon Pro WX would change that? Sincerely Roland Am 30 Jan 2020 04:07:58 +0100 (CET) Von "Ludovic Bellière" : Hello Tim, First you need to know the chipset name of your card in order to know it's family. To do that you need to run (or similar): ``` lspci | grep VGA ``` It's output on my desktop shows: ``` 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef) ``` This tells me that the chipset name of my card is Ellesmere, which is the POLARIS architecture. A quick look to [RadeonFeature][1] tells me that POLARIS is part of the [Volcanic Islands family][2]. The [gentoo wiki][3] might help too. Knowing the family is important, as it tells you how to tell the kernel to load the amdgpu driver before radeon. Because I suspect FirePro W4100 to be quite
Re: [DNG] Update successful but video card issue
Hi Ludovic,hi Tim, actually, I do have the same issues. I am running a Thinkstation P520Cwith a Radeon Firepro W4100 with a 4K Benq PD3200U. I literally spent weeks of searching information about this problem to get rid of the flickering,but without any success. I tried several distributions (Linux Mint, Devuan and actually MXLinux) without any difference. And I also tried the proprietary drivers, which didn't change anything,installing it after the open driver and by installing it as first driver. I even tried various connections (HDMI, DP). The problem appears irregularely and more frequently whilest watching videos.There is a slight difference between watching 4k/30fps and 4k/60fps, wheras 4k/60fpsshows less flickering of the whole screen than 4k/30fps. And after having watched a 4k/60fps video for some seconds,the screen won't flicker at all for several minutes. My guess is a timing problem of the AMD Firepro W4100. Might be, using a AMD Radeon Pro WX would change that? Sincerely Roland Am 30 Jan 2020 04:07:58 +0100 (CET) Von "Ludovic Bellière" : Hello Tim, First you need to know the chipset name of your card in order to knowit's family. To do that you need to run (or similar): ```lspci | grep VGA``` It's output on my desktop shows: ```01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.[AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)``` This tells me that the chipset name of my card is Ellesmere, which isthe POLARIS architecture. A quick look to [RadeonFeature][1] tells methat POLARIS is part of the [Volcanic Islands family][2]. The [gentoowiki][3] might help too. Knowing the family is important, as it tellsyou how to tell the kernel to load the amdgpu driver before radeon. Because I suspect FirePro W4100 to be quite old, the [archlinuxhowtos][4] might be helpful to you. That being said, you might prefer installing the [proprietarydrivers][5] if you plan to use a professional card. I suspect takingthat road would come with its own set of problems. I hope this helps,Ludovic [1]: https://www.x.org/wiki/RadeonFeature/[2]:https://www.x.org/wiki/RadeonFeature/#decoderringforengineeringvsmarketingnames[3]: https://wiki.gentoo.org/wiki/AMDGPU#Feature_support[4]:https://wiki.archlinux.org/index.php/AMDGPU#Enable_Southern_Islands_.28SI.29_and_Sea_Islands_.28CIK.29_support[5]:https://www.amd.com/en/support/professional-graphics/firepro/firepro-wx100-series/firepro-w4100 On 29/01/20 23:05, Tim Wallace via Dng wrote:> I have been happily running ascii but upgraded from my Intel built-in> graphics to an AMD FirePro W4100 because I do a lot of 4K video editing,> but no game-playing, and thought this 50W card would save energy and> work well with 4K. There is a nearly identical Nvidia card, but I> decided to support AMD, for easier Linux support, which has not been my> experience!> > The card booted OK under ascii but was using the Radeon Xorg driver> which gave flashing behavior from time to time, typical of a bad video> driver. I decided to try beowulf to get some newer versions of stuff.> > I installed a generic ascii on my other partition, then did the upgrade,> from an xterm, perhaps not the smartest idea but it worked. When I ran> synaptic, it added and removed hundreds of packages! Not exactly> efficient, but I was left with a working system. The only issue was> that my Samsung M.2 SSD only boots as efi, and install systems don't> seem to realize that, resulting in boot failure or boot install failure,> but I used the rEFInd program to recover everything, and all seems good> with both beowulf and ascii.> > The situation now is that I can't get the correct X video driver> working, which should be the amdgpu one, under either ascii or beowulf.> (Full screen 4K video plays great at 60 fps under mpv, with nothing> dropped and no flashes.) I did try disabling pretty much all the> acceleration options on the radeon driver, but that did not help with> the flashing.> > Details:> Motherboard ASRock Z97 Extreme6, i7-4790K, 16 GB, latest Bios 2.80> > added non-free repository, and installed firmware. On boot, both radeon> and amdgpu kernel modules are installed. When X starts, the radeon> driver is used. The xorg.conf output by Xorg -configure calls for the> amdgpu driver, but trying to run, get fatal error:> > amdgpu_device_initialize: DRM version is 2.50.0 but this kernel is only> compatible with 3.x.x> > > Under ascii, the radeon driver is called for by Xorg -configure, and the> error when forcing amdgpu is almost the same, except> > ... DRM version is 2.49.0...> > It seems that there are some incompatibilities built into both ascii and> beowulf when it comes to this card. I could compile a kernel (which I> used to do all the time in the 90's, and probably haven't done for 10> years) if that would help with the DRM version issue.> > I tried the Ubuntu version of the proprietary driver from AMD, and it> complained about the kernel version. I could compile a kernel to match> the
Re: [DNG] Update successful but video card issue
Hello Tim, First you need to know the chipset name of your card in order to know it's family. To do that you need to run (or similar): ``` lspci | grep VGA ``` It's output on my desktop shows: ``` 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef) ``` This tells me that the chipset name of my card is Ellesmere, which is the POLARIS architecture. A quick look to [RadeonFeature][1] tells me that POLARIS is part of the [Volcanic Islands family][2]. The [gentoo wiki][3] might help too. Knowing the family is important, as it tells you how to tell the kernel to load the amdgpu driver before radeon. Because I suspect FirePro W4100 to be quite old, the [archlinux howtos][4] might be helpful to you. That being said, you might prefer installing the [proprietary drivers][5] if you plan to use a professional card. I suspect taking that road would come with its own set of problems. I hope this helps, Ludovic [1]: https://www.x.org/wiki/RadeonFeature/ [2]: https://www.x.org/wiki/RadeonFeature/#decoderringforengineeringvsmarketingnames [3]: https://wiki.gentoo.org/wiki/AMDGPU#Feature_support [4]: https://wiki.archlinux.org/index.php/AMDGPU#Enable_Southern_Islands_.28SI.29_and_Sea_Islands_.28CIK.29_support [5]: https://www.amd.com/en/support/professional-graphics/firepro/firepro-wx100-series/firepro-w4100 On 29/01/20 23:05, Tim Wallace via Dng wrote: > I have been happily running ascii but upgraded from my Intel built-in > graphics to an AMD FirePro W4100 because I do a lot of 4K video editing, > but no game-playing, and thought this 50W card would save energy and > work well with 4K. There is a nearly identical Nvidia card, but I > decided to support AMD, for easier Linux support, which has not been my > experience! > > The card booted OK under ascii but was using the Radeon Xorg driver > which gave flashing behavior from time to time, typical of a bad video > driver. I decided to try beowulf to get some newer versions of stuff. > > I installed a generic ascii on my other partition, then did the upgrade, > from an xterm, perhaps not the smartest idea but it worked. When I ran > synaptic, it added and removed hundreds of packages! Not exactly > efficient, but I was left with a working system. The only issue was > that my Samsung M.2 SSD only boots as efi, and install systems don't > seem to realize that, resulting in boot failure or boot install failure, > but I used the rEFInd program to recover everything, and all seems good > with both beowulf and ascii. > > The situation now is that I can't get the correct X video driver > working, which should be the amdgpu one, under either ascii or beowulf. > (Full screen 4K video plays great at 60 fps under mpv, with nothing > dropped and no flashes.) I did try disabling pretty much all the > acceleration options on the radeon driver, but that did not help with > the flashing. > > Details: > Motherboard ASRock Z97 Extreme6, i7-4790K, 16 GB, latest Bios 2.80 > > added non-free repository, and installed firmware. On boot, both radeon > and amdgpu kernel modules are installed. When X starts, the radeon > driver is used. The xorg.conf output by Xorg -configure calls for the > amdgpu driver, but trying to run, get fatal error: > > amdgpu_device_initialize: DRM version is 2.50.0 but this kernel is only > compatible with 3.x.x > > > Under ascii, the radeon driver is called for by Xorg -configure, and the > error when forcing amdgpu is almost the same, except > > ... DRM version is 2.49.0... > > It seems that there are some incompatibilities built into both ascii and > beowulf when it comes to this card. I could compile a kernel (which I > used to do all the time in the 90's, and probably haven't done for 10 > years) if that would help with the DRM version issue. > > I tried the Ubuntu version of the proprietary driver from AMD, and it > complained about the kernel version. I could compile a kernel to match > the Ubuntu one, I suppose, and re-try the proprietary driver, if anyone > thinks that would help. I'm not looking for the fastest performance in > the world, though, just stability! > > Any advice? > > --Tim > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Update successful but video card issue
I have been happily running ascii but upgraded from my Intel built-in graphics to an AMD FirePro W4100 because I do a lot of 4K video editing, but no game-playing, and thought this 50W card would save energy and work well with 4K. There is a nearly identical Nvidia card, but I decided to support AMD, for easier Linux support, which has not been my experience! The card booted OK under ascii but was using the Radeon Xorg driver which gave flashing behavior from time to time, typical of a bad video driver. I decided to try beowulf to get some newer versions of stuff. I installed a generic ascii on my other partition, then did the upgrade, from an xterm, perhaps not the smartest idea but it worked. When I ran synaptic, it added and removed hundreds of packages! Not exactly efficient, but I was left with a working system. The only issue was that my Samsung M.2 SSD only boots as efi, and install systems don't seem to realize that, resulting in boot failure or boot install failure, but I used the rEFInd program to recover everything, and all seems good with both beowulf and ascii. The situation now is that I can't get the correct X video driver working, which should be the amdgpu one, under either ascii or beowulf. (Full screen 4K video plays great at 60 fps under mpv, with nothing dropped and no flashes.) I did try disabling pretty much all the acceleration options on the radeon driver, but that did not help with the flashing. Details: Motherboard ASRock Z97 Extreme6, i7-4790K, 16 GB, latest Bios 2.80 added non-free repository, and installed firmware. On boot, both radeon and amdgpu kernel modules are installed. When X starts, the radeon driver is used. The xorg.conf output by Xorg -configure calls for the amdgpu driver, but trying to run, get fatal error: amdgpu_device_initialize: DRM version is 2.50.0 but this kernel is only compatible with 3.x.x Under ascii, the radeon driver is called for by Xorg -configure, and the error when forcing amdgpu is almost the same, except ... DRM version is 2.49.0... It seems that there are some incompatibilities built into both ascii and beowulf when it comes to this card. I could compile a kernel (which I used to do all the time in the 90's, and probably haven't done for 10 years) if that would help with the DRM version issue. I tried the Ubuntu version of the proprietary driver from AMD, and it complained about the kernel version. I could compile a kernel to match the Ubuntu one, I suppose, and re-try the proprietary driver, if anyone thinks that would help. I'm not looking for the fastest performance in the world, though, just stability! Any advice? --Tim ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
