GPU/Grub issues

General system Newbie
41

I am reaching the limits of my knowledge. At this point, I wonder if your GPU is having issues. I am thinking one of two things.

First, I would add a kernel parameter and seeing if that helps.

You can do this by:

  1. Press “E” on the grub screen and find the line with the “quiet” parameter.

  2. Replace the word “quiet” with acpi_osi='Windows 2018' you need.

  3. Press F-10 to boot your computer.

Notice that the quotation marks around Windows 2018 are single ticks.

The second thing I would try is removing any nVidia config files, remove any blacklisting, turning your PC off, removing your nVidia GPU and doing a reboot.

1 Like
42

Maybe try just disconnect everything from GPU and it from motherboard, then connect again, just in case…

Oven though… :fire: :laughing:

@Oziach sorry, missed it

1 Like
43

Nope, booted into this rn, same thing, except the performance of the whole system is abysmal.

@keybreak I did mention I tried reseating. I do have the time right now to completely take apart and put together the whole system – would do it good to replace the thermal paste on the CPU, as it has been roughly a year for it.

1 Like
44

I do not understand. Did you boot into the system without the nVidia GPU installed? Despite the performance being low, was it stable? What did inxi -G say? I am trying to see if it is the nVidia GPU.

It could not hurt, but I do not think thermal paste is your issue.

Well, I am sorry. At this point we are out of my knowledge zone.

1 Like
45

Sorry, with the acpi_osi='Windows 2018' is what I meant and that inxi -G says the same exact thing.

I know it’s not, but I’m just trying to hype myself up to do it. :laughing:

46

Can you return inxi -Fxxxza --no-host?

1 Like
47 
$ inxi -Fxxxza --no-host
System:
  Kernel: 5.9.12-arch1-1 x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-linux 
  root=UUID=db231805-d44a-4176-9e12-2531ea10f116 rw "acpi_osi=Windows 2018" 
  loglevel=3 nowatchdog 
  Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm 
  dm: GDM 3.38.2, LightDM 1.30.0 Distro: EndeavourOS 
Machine:
  Type: Desktop Mobo: ASRock model: AB350M Pro4 serial: <filter> 
  UEFI: American Megatrends v: P4.90 date: 07/06/2018 
CPU:
  Info: Quad Core model: AMD Ryzen 3 2200G with Radeon Vega Graphics 
  bits: 64 type: MCP arch: Zen family: 17 (23) model-id: 11 (17) 
  stepping: N/A microcode: 810100B L2 cache: 2048 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 27956 
  Speed: 1515 MHz min/max: 1600/3500 MHz boost: enabled Core speeds (MHz): 
  1: 2205 2: 1680 3: 1492 4: 1530 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. 
  driver: nvidia v: 455.45.01 alternate: nouveau,nvidia_drm bus ID: 10:00.0 
  chip ID: 10de:1c03 
  Display: x11 server: X.org 1.20.10 compositor: budgie-wm 
  driver: modesetting FAILED: nvidia resolution: <missing: xdpyinfo> 
  OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.3.0 
  compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: NVIDIA GP106 High Definition Audio vendor: eVga.com. 
  driver: snd_hda_intel v: kernel bus ID: 10:00.1 chip ID: 10de:10f1 
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel 
  v: kernel bus ID: 38:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.9.12-arch1-1 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASRock driver: r8169 v: kernel modules: r8168 port: e000 
  bus ID: 1f:00.0 chip ID: 10ec:8168 
  IF: enp31s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 2.27 TiB used: 8.26 GiB (0.4%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T2B0C-00PXH0 
  size: 931.51 GiB block size: physical: 512 B logical: 512 B 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 211070WD scheme: GPT 
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 3B6Q scheme: GPT 
  ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-08WN4A0 
  size: 931.51 GiB block size: physical: 4096 B logical: 512 B 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A02 scheme: GPT 
Partition:
  ID-1: / raw size: 465.21 GiB size: 456.91 GiB (98.22%) 
  used: 8.26 GiB (1.8%) fs: ext4 dev: /dev/sda2 
Swap:
  Alert: No Swap data was found. 
Sensors:
  System Temperatures: cpu: 55.9 C mobo: N/A gpu: nvidia temp: 54 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 9% 
Info:
  Processes: 210 Uptime: 15m wakeups: 0 Memory: 15.63 GiB 
  used: 2.02 GiB (12.9%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  Packages: pacman: 975 lib: 285 Shell: Bash v: 5.0.18 
  running in: gnome-terminal inxi: 3.1.09

I did it in Grub exactly like posted though.

48

**This is disabled in BIOS yes? I have a feeling your integrated GPU is not playing nice with the Nvidia card.

2 Likes
49

No The acpi parameter should look like acpi_='Windows 2018' Single ticks not quotation marks.

1 Like
50

Yes, that’s what I did. Not sure why it went to quotation marks.

@anon53396576 It was playing nice for ages though. Let me figure out how to disable it and boot into that.

51

Double check. It is highlighted in red because it is not being applied. the single ticks are only around the Windows 2018.

1 Like
52

Yes, that is exactly how I did it. acpi_osi='Windows 2018'

1 Like
53

Little off-topic, but still since it was asked about UEFI i have re-read some stuff…Jeez :man_facepalming:

1 Like
54

Shameless of me to tag my post as a solution, but I can summarize the topic. Every person in this thread was a big help!!!

GPU:

It WAS set to Disabled.

http://forum.asrock.com/forum_posts.asp?TID=8503&title=disabling-integrated-graphics-card

^^^ Followed the instructions on this thread:

BIOS Path: Advanced > AMD CBS > NBIO Common Options > GFX Configuration
1. Set the Integrated Graphics Controller to Forces.
2. Set the UMA Mode to UMA_SPECIFIED.
3. Set the UMA Frame Buffer Size to 64M.
4. Press [F10] save and exit.

These BIOS parameters for my specific motherboard fixed the drivers issue I was having.

$ inxi -G
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 455.45.01 
  Device-2: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
  driver: amdgpu v: kernel 
  Display: x11 server: X.org 1.20.10 driver: nvidia 
  resolution: <missing: xdpyinfo> 
  OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01

Grub:

I’m just a dingdong and messed something up down the road of me using the system. Manual partitioning on a empty drive fixes the issue flawlessly.

3 Likes
55

I was just making sure.

It looks like it is now using the Geforce card. How is the performance?

1 Like
56

I don’t know, I’m going to attempt to boot into my main system and play a game.

1 Like
57

Better than it has been in months, wtf :rofl:

Let me reboot like 10 times to see if it persists.

$ inxi -G
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 455.45.01
           Device-2: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
           driver: amdgpu v: kernel
           Display: x11 server: X.Org 1.20.10 driver: modesetting,nvidia
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01

btw

1 Like
58

So what exactly have you done in the end to fix?

1 Like
59

Now

Before

1 Like
60

What @anon53396576 suggested, just backwards. Essentially, reenabled the iGPU, which was disabled for many many months for whatever reason.

It could’ve gotten disabled by default, or got disabled when I was reflashing my BIOS many times. I’m honestly not sure.

2 Likes