ASUS TUF Gaming A17 screen goes black

[nbl]

Hi. My ASUS TUF A17 screen goes sometimes black, no sounds...sometimes screen freezes with sound tilting. There is no certain circumstances, could happen at any time, at any job. Sometimes 30 sec after boot, sometimes hours.
Did not find any similar situations on the web.
Will appreciate any help.

Code: Select all

System:
  Kernel: 5.11.0-34-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Cinnamon 5.0.5 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A17 FA706IH_FX706IH 
  v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: FA706IH v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: FA706IH.316 date: 03/12/2021 
Battery:
  ID-1: BAT1 charge: 49.4 Wh condition: 49.4/48.1 Wh (103%) 
  model: ASUS A32-K55 status: Full 
  Device-1: hidpp_battery_0 model: Logitech G603 Wireless Gaming Mouse 
  charge: 100% (should be ignored) status: Discharging 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 
  type: MT MCP arch: Zen rev: 1 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 71865 
  Speed: 1397 MHz min/max: 1400/3000 MHz Core speeds (MHz): 1: 1397 2: 1396 
  3: 1397 4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 9: 1398 10: 1397 11: 1397 
  12: 1395 
Graphics:
  Device-1: NVIDIA vendor: ASUSTeK driver: nouveau v: kernel bus ID: 01:00.0 
  Device-2: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel 
  bus ID: 05:00.0 
  Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,modesetting 
  unloaded: fbdev,vesa resolution: 1920x1080~144Hz 
  OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-34-generic LLVM 12.0.0) 
  v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio:
  Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 01:00.1 
  Device-2: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 05:00.1 
  Device-3: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
  vendor: DekTec Digital Video B.V. driver: N/A bus ID: 05:00.5 
  Device-4: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 05:00.6 
  Sound Server: ALSA v: k5.11.0-34-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter 
  vendor: AzureWave driver: rtw_8822ce v: N/A port: d000 bus ID: 03:00.0 
  IF: wlp3s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 27.73 GiB (5.8%) 
  ID-1: /dev/nvme0n1 vendor: Micron model: 2210 MTFDHBA512QFD 
  size: 476.94 GiB 
Partition:
  ID-1: / size: 91.17 GiB used: 11.04 GiB (12.1%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-2: /home size: 376.28 GiB used: 16.68 GiB (4.4%) fs: ext4 
  dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 47.2 C mobo: N/A 
  Fan Speeds (RPM): cpu: 2400 
  GPU: device: nouveau temp: 35 C device: amdgpu temp: 43 C 
Info:
  Processes: 298 Uptime: 7m Memory: 7.26 GiB used: 2.05 GiB (28.3%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38

[SMG]

Have some problems with both of them:

Please create a new thread for the Vivobook issue. These two computers have two different problems as well as having different hardware. It will be easier for others to help you if each computer has its own thread.

[SMG]

Hi. My ASUS TUF A17 screen goes sometimes black, no sounds...sometimes screen freezes with sound tilting. There is no certain circumstances, could happen at any time, at any job. Sometimes 30 sec after boot, sometimes hours.

Are you then shutting it off and restarting it using the power button? If so, we could probably check the journalctl for error messages.

I notice you have not yet installed the Nvidia driver. I suggest taking a Timeshift snapshot and then installing the recommended driver in Driver Manager. It is possible that might help even though you are currently running the computer with the AMD graphics.

[nbl]

Thanks for a reply.

Are you then shutting it off and restarting it using the power button?

Yes, it freezes completely, so the only way is to use power button.

If so, we could probably check the journalctl for error messages.

I have been messing around with this TUFF since I got it, so "journalctl -p err" gives 1000 lines, walked through and could not make any sense of the log file, where was my own bad adjustments, or where was the actual system freeze, will post log from the next freeze.

I notice you have not yet installed the Nvidia driver. I suggest taking a Timeshift snapshot and then installing the recommended driver in Driver Manager. It is possible that might help even though you are currently running the computer with the AMD graphics.

I have tried 460 & 470 drivers, but from my point of view freezes tend to happen more frequently with those drivers on, so I decided to stick with most simplest composition, till the problem is solved.

[SMG]

I have been messing around with this TUFF since I got it, so "journalctl -p err" gives 1000 lines, walked through and could not make any sense of the log file, where was my own bad adjustments, or where was the actual system freeze, will post log from the next freeze.

Let's focus on the info from one boot cycle. The next time you restart after this problem, run the following:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

[nbl]

Thank You, I will do that. As for now, I am amused, but my TUF has been running smoothly for over 24h, first time that long strike.

[nbl]

Let's focus on the info from one boot cycle. The next time you restart after this problem, run the following:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

Yep, wrote a reply and putted on a movie stream, 30 sec and tilted, I think that most of the times, if not always, it happens on media steaming.
https://termbin.com/ptgjd

[SMG]

Yep, wrote a reply and putted on a movie stream, 30 sec and tilted, I think that most of the times, if not always, it happens on media steaming.

A made a quick pass at the log and I do not notice any obvious errors. However, I will go back through it line-by-line to see if there is anything.

How are you streaming the movie? What software?

[nbl]

Thanks.
I am a student, so I stream all the time -> corona -> Moodle, Zoom, MS Teams but I do not recall any freezing with those programs.
Now, after rolling back to AMD driver system tends to freeze when I stream high resolution Youtube etc. web players.
When I used Nvidia drivers tilting happened on web-Spotify and lower resolutions video streaming, and maybe without streaming, not sure.
If You think it would help, I can install Nvidia and print logs.

[SMG]

If You think it would help, I can install Nvidia and print logs.

Let me review this log first and I will let you know what I find.

[SMG]

Yep, wrote a reply and putted on a movie stream, 30 sec and tilted, I think that most of the times, if not always, it happens on media steaming.

There is nothing but firewall blocks in the last 10 minutes of this journal.

Code: Select all

Sep 21 20:57:04 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44454 PROTO=2 
Sep 21 20:54:59 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44453 PROTO=2 
Sep 21 20:52:54 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44452 PROTO=2 
Sep 21 20:52:23 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44451 PROTO=2 
Sep 21 20:51:51 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44450 PROTO=2 
Sep 21 20:49:53 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44449 PROTO=2 
Sep 21 20:47:48 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44448 PROTO=2 
Sep 21 20:45:43 ton-ntt kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=xxx SRC=xxx DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=44447 PROTO=2 

This computer successfully went to sleep and resumed from sleep two times during this boot cycle. (It looks like one time was triggered by a lid closure and the second may have been a time-out in the power management?)

Have you checked the System Reports app to see if anything is listed under System Reports or Crash Reports?

Perhaps a newer kernel might be more stable, but without any error messages showing, that is just a total guess on my part.

Because there are no errors listed, I do not know if it would be any better or worse to use the Nvidia driver. I will let you know your computer has Secure Boot enabled which means you will need to sign the Nvidia driver so it will be trusted to load after you install it. Some computers will bring up a screen so you can enroll Nvidia in MOK. I do not know if yours will. If it does not, there is another way to enroll the keys I can pass along to you.

[nbl]

Ok, thank You for your assistance.
Loaded Nvidia, updated new kernel, hope it works out at some point.