Hi
So that all looks good, I would guess itās time to look at the radeon driver and options (parm)ā¦
So if you run the following command, this will show them all;
/sbin/modinfo radeon |grep "parm:"
Then run the following to see what is set;
zypper in sysfsutils
systool -vm radeon
Then itās down to researching the options to see what they can be set toā¦
https://paste.opensuse.org/89895570 ā¦many thanx so far! You mean I should āplay aroundā with parameters? Any hint where to start?
Hi
So AFAIK your card is neither SI or CIK, if so I would disable those two options, in your output they show a ā1ā (enabled) in the systool output, refer back to parm output for the options.
So in the grub boot options add;
radeon.si_support=0 radeon.cik_support=0
Reboot, check the systool output to make sure it changed, see how that goesā¦
Hi again! I donāt have the slightest idea what SI or CIK could mean, but I added these parameters to the kernel line in Yast and rebooted. Both are ā0ā now in the output of systool -vm radeon. Waitānsee
Many thanks so farā¦
Hi
Newer generation AMD cards, (GCN) Southern and Sea Island cardsā¦
ā¦no crashes here anymore! Many thanks again! 
Will the kernel parameters survive all TW zypper dups or do I have to have an eye on these lines in YasT?
Hi
No, they will survive reboots/updates fine, I doubt those parameters will be deprecated in the near futureā¦
Sorry to be back, but⦠I started a VLC player and watched an http stream for about 1 minute then the screen went black and looked like trying to restart over and over again. Not even REISUB was able to revive.
On reboot the login screen looked like on LSD, everything quite surreal and no login possible. OK, I thought, now this time the hardware is over. But booting to Win 7 (dual boot system) works perfectly (besides the first boot, which resulted in a persistent black screen (backlight on) before the login screen. But the second boot is now absolutely stable for 30 min or so. Strange.
Problems started with 4.20 kernel iirc and the notebook sitting there and doing nothing while turned for some daysā¦
On Wed 13 Feb 2019 05:06:03 PM CST, suse rasputin wrote:
Sorry to be back, but⦠I started a VLC player and watched an http
stream for about 1 minute then the screen went black and looked like
trying to restart. not even REISUB was able to revive. On reboot the
login screen looked like on LSD, everything quite surreal and no login
possible. OK, I thought, now this time the hardware is over. But booting
to Win 7 (dual boot system) works perfectly (besides the first boot,
which resulted in a persistent black screen (backlight on) before the
login screen. But the second boot is now absolutely stable for 30 min or
so. Strange. Problems started with 4.20 kernel iirc and the notebook
sitting there and doing nothing while turned for some daysā¦
Hi
Temperatures all ok, no dust bunnies in the fans⦠might be time to
replace thermal compound�
Disk and disk space ok, RAM ok (maybe run memtest?)ā¦
ā
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.28-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below⦠Thanks!
Thermal paste is relatively new, as the graphics card has been replaced some 3 years ago. Temp around 52°C for the GPU in Linux and dust removes some 3 months ago.
I started the VLC again, the effect was comparable, but not identical: After some 20 seconds the picture in the VLC screen suddenly became trapezoidal instead of rectangular (and LSD effect as described earlier) and screen went black, then cam back, but only thing to recover was REISUBā¦
As everything is normal with Windows I canāt belief itās a hardware issue. maybe I will try installing Leap 15 and see how the older kernel does play with the GPU.
Is it possible to copy the /home from TW to a fresh HDD partition and install Leap to another partition on this fresh disk? Or does Leap not play well with a TW /home partition?
Hi
Could also be VLC, lots of recent changes have upset a few of the multimedia packages⦠there will be a new staging project on packman to try and alleviate some of the breakages.
Hi again, had to reinstall the machine as TW screwd up druing udate.
Is the script here
https://forums.opensuse.org/showthread.php/528192-ATI-FirePro-M7740-went-unstable-any-ideas/page6
(third post) still valid, can I use the same procedure again to set to power mode of the GPU? 
On Fri 15 Feb 2019 09:06:05 PM CST, suse rasputin wrote:
Hi again, had to reinstall the machine as TW screwd up druing udate.
Is the script here
ATI FirePro M7740 went unstable - any ideas? - Install/Boot/Login - openSUSE Forums
(third post) still valid, can I use the same procedure again to set to
power mode of the GPU?
Hi
Yes, AFAIK all should be good, you can also just cat the variables out
to see what they are.
ā
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.28-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below⦠Thanks!
Could not install the script yet, as TW dies at the login screen every time I boot to TW. Win7 is doing fine now for hours. So nothing related to hardware. Strangeā¦
suse_rasputin, I canāt see where you ever tried the default DDX driver (Modesetting) yet. Did you? It works here on AMD/ATI cards both newer and older than yours, e.g. older:
$ rpm -qa | grep xf86-vid
xf86-video-vesa-2.4.0-1.4.x86_64
xf86-video-fbdev-0.5.0-1.4.x86_64
$ inxi -GxxS
System: Host: hpg33 Kernel: 4.20.4-1-default x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE 3.5.10 tk: Qt 3.3.8c
wm: kwin dm: startx Distro: openSUSE Tumbleweed 20190201
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV610 [Radeon HD 2400 PRO] vendor: Dell driver: radeon v: kernel
bus ID: 04:00.0 chip ID: 1002:94c3
Display: server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa alternate: ati resolution: 1920x1200~60Hz
OpenGL: renderer: AMD RV610 (DRM 2.50.0 / 4.20.4-1-default LLVM 7.0.0) v: 3.3 Mesa 18.3.1 compat-v: 3.0
direct render: Yes
Hi Mrmazda!
You mean I should remove this x86videoā¦amd thing and reboot?
Installed LEap 15, everything fine troughout installation and reboot, but after login screen: black screen with backlights on. fun fact: I can change the volume and hear the control sound, but otherwise anything is deadā¦
Win7 doing fin, TW and Lep during installation doing fin, but on login both TW and Leap turn crazyā¦
Would have to remove the AMD driver(s ?) during installation to see if it makes any differenceā¦
No. Boot with a 3 appended to cmdline so that you can then use shell login and zypper to remove unwanted/unneeded xf86-video-amdgpu and xf86-video-ati driver(s). Once removed, do startx, or do systemcl isolate graphical, or reboot.
I have a fresh installed Leap, saw the login page, changed to console and removed any xf86video except the two in your output some posts above. Reboot. At login screen I enter the password, screen turns, then it gets dark, and the background light comes back, goes away, comes back⦠HDD working hard, but no Desktop appears even after some 20 min or so.
If it wouldnāT been running absolutely flawless in Win 7 and during installing TW or LEAP I would buy the story with the hardware going south, but so I donāt really get it. Could renew thermal paste (halve a day of work, the graphics are really deep down in these Precision M6400/M6500). Or RAM test over night. But donāT think this will buy anythingā¦