Re: [DNG] [FLASH] THE UNITED STATES CONGRESS HAS FALLEN

[Roland Gebhard Sidler]

Please ban such persons immediately instead of even thinking about
commenting their elaborates

Am 07.01.21 um 00:18 schrieb Linux O'Beardly via Dng:
> I don't really think this is the forum to discuss such things. In my
> opinion, politics don't belong here.  I can assure you none of you
> want to hear my politics. 
>
> On Wed, Jan 6, 2021 at 5:26 PM Bruce Perens via Dng
> mailto:dng@lists.dyne.org>> wrote:
>
> They'll get up again. What we are seeing is the last hurrah of
> white supremacists who aren't getting their way. 
>
> On Wed, Jan 6, 2021 at 11:55 AM Se7en  wrote:
>
> The Congress of the United States has fallen. This is NOT A
> JOKE. The
> United States Congress has fallen.
>
> -- 
> |-/                   | Se7en
>      /  The One and Only! | se7en@cock.email
>     /                     | 0x0F83F93882CF6116
>    /                      | https://se7en-site.neocities.org
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org 
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 
>
>
>
> -- 
> Bruce Perens - CEO at stealth startup. I'll tell you what it is
> eventually :-)
> ___
> Dng mailing list
> Dng@lists.dyne.org 
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 
>
>
>
> -- 
> Linux O'Beardly
> @LinuxOBeardly
> http://o.beard.ly 
> linux.obear...@gmail.com 
>
> ___
> 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] [FLASH] THE UNITED STATES CONGRESS HAS FALLEN

[Roland Gebhard Sidler]

Please ban such persons immediately instead of even thinking about
commenting their elaborates

Am 06.01.21 um 23:26 schrieb Bruce Perens via Dng:
> They'll get up again. What we are seeing is the last hurrah of white
> supremacists who aren't getting their way. 
>
> On Wed, Jan 6, 2021 at 11:55 AM Se7en  wrote:
>
> The Congress of the United States has fallen. This is NOT A JOKE. The
> United States Congress has fallen.
>
> -- 
> |-/                   | Se7en
>      /  The One and Only! | se7en@cock.email
>     /                     | 0x0F83F93882CF6116
>    /                      | https://se7en-site.neocities.org
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org 
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 
>
>
>
> -- 
> Bruce Perens - CEO at stealth startup. I'll tell you what it is
> eventually :-)
>
> ___
> 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

[Roland Gebhard Sidler]

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

[Roland Gebhard Sidler]

 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