I'm already post about this but,
I just realised that this custom kerner: linux-tgk-bmq has not do nothing with any nvidia-390xx dkms because the frogging kerner supports custom patched drivers only!!! The problem is that they are not patching/maintaining any nvidia-390xx or any older drivers.
So if someone like me tries installing non-free driver with mhwd or manually from AUR, will got a big surprise because it will not working.
It was not a good idea to make tgk-bmq to default Garuda kernel. I think that not I am the only one who have older Nvidia card, it will cause many headache for people that wanna try this distro. Default kerner should be just zen kernel!!!
I run a tkg kernel of the 5.10 variety.
I also use nvidia-390xx-dkms, I don't know what's stopping you.
I also have an old nvidia card, and prior to updating to 5.10 kernel didn't had any major issues even with new tkg kernels. I think it's pretty unlikely that only because of one unsupported legacy driver main kernel will change, but in case you have issues too - you can change your kernel yourself in Garuda settings manager. Btw, I installed drivers via source packages, in my case, nvidia-390xx-dkms.
Are you using the same kernel: linux-tgk-bmq 5.9 or 5.10? Kde Dragonized?
Yapp I do it change back to Zen. It would be good to know which custom kerner compatible with which driver. Thank you for your help!
I used linux-tkg-pds-sandybridge 5.9. After updating to 5.10 everything just fell apart as it is a huge update and it seems like nvidia drivers must be rebuilt in AUR https://forum.garudalinux.org/t/chaoticaur-needs-a-rebuild-of-nvidia-390xx-for-5-10/2390?u=waterfeelix
I dont have my dkms build log, I didn't want to break my system again so I just removed immediately with mhwd.
These are from my pacman-log
╰─λ inxi -Fxxxza
System: Kernel: 5.9.14-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=0cc28cca-90c4-40ee-b717-86f6ddd393fa rw
rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM
Distro: Garuda Linux
Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 8540p v: N/A serial: <filter> Chassis:
type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 1521 v: KBC Version 32.36 serial: <filter> UEFI: Hewlett-Packard
v: 68CVD Ver. F.60 date: 11/11/2015
Battery: ID-1: BAT0 charge: 55.1 Wh condition: 55.1/55.1 Wh (100%) volts: 16.2/14.4
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Full
CPU: Info: Quad Core model: Intel Core i7 Q 840 bits: 64 type: MT MCP arch: Nehalem family: 6
model-id: 1E (30) stepping: 5 microcode: A L2 cache: 8 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 29797
Speed: 1784 MHz min/max: 1199/1867 MHz boost: disabled Core speeds (MHz): 1: 1784 2: 1845 3: 1780
4: 1768 5: 1816 6: 1757 7: 1854 8: 1472
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GF106GLM [Quadro 2000M] vendor: Hewlett-Packard driver: nouveau v: kernel
bus ID: 01:00.0 chip ID: 10de:0dda
Device-2: Chicony HP Webcam [2 MP Macro] type: USB driver: uvcvideo bus ID: 1-1.5:4
chip ID: 04f2:b15e
Display: x11 server: X.org 1.20.10 compositor: kwin_x11 driver: nouveau unloaded: modesetting
alternate: fbdev,nv,vesa resolution: <missing: xdpyinfo>
OpenGL: renderer: NVC3 v: 4.3 Mesa 20.3.1 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
Device-2: NVIDIA GF106 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:0be9
Sound Server: ALSA v: k5.9.14-zen1-1-zen
Network: Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel port: 6020
bus ID: 00:19.0 chip ID: 8086:10ea
IF: enp0s25 state: down mac: <filter>
Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 5000 bus ID: 44:00.0
chip ID: 8086:4239
IF: wlo1 state: up mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 10.84 GiB (1.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 023
Partition: ID-1: / raw size: 530.66 GiB size: 530.66 GiB (100.00%) used: 10.81 GiB (2.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%) used: 25.8 MiB (8.6%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw size: 530.66 GiB size: 530.66 GiB (100.00%) used: 10.81 GiB (2.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw size: 530.66 GiB size: 530.66 GiB (100.00%) used: 10.81 GiB (2.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw size: 530.66 GiB size: 530.66 GiB (100.00%) used: 10.81 GiB (2.0%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
Swap: Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 979.6 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
Sensors: System Temperatures: cpu: 59.0 C mobo: 0.0 C gpu: nouveau temp: 53.0 C
Fan Speeds (RPM): N/A
Info: Processes: 251 Uptime: 22m wakeups: 2 Memory: 7.65 GiB used: 2.08 GiB (27.2%) Init: systemd v: 247
Compilers: gcc: 10.2.0 clang: 11.0.0 Packages: pacman: 1099 lib: 285 Shell: fish v: 3.1.2
running in: alacritty inxi: 3.2.00
If you include terminal outputs in your post please use the proper output format in your post. Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.
Password for paste bin needed.
Do without or give password
I just find the way to solve the dkms linux-tgk-bmq issue.
The problem caused by linux-tgk makepkg base devel tools.
This is what I made:
nvidia-390xx-dkms with mhwd
sudo pacman -R nvidia-390xx-dkms
sudo pacman -Syu base-devel linux-headers
git clone https://aur.archlinux.org/nvidia-390xx.git
AUR dkms -> package actions ->download snapshot
put the the nvidia-390xx tar to the home/nvidia-390xx dir
pacman -Q | grep headers
sudo pacman -S linux-tkg-bmq-headers
If you did not use the standard DKMS install method, then perhaps you will need to rebuild your driver after kernel updates. Not 100% sure though.
I have tried all the way. With the standard method the problem is that the chaotic AUR driver 5.9 is not compatible with the latest kernel: 5.10 and headers. And after I tried to built directly from AUR with it's fixed patches for 5.10.
I got errors during the built error code was -> make: /usr/src/linux: No such file or directory!
Then I read in a forum that someone got same error and just downloaded the linux-headers and base-devel and it was the key because its replaced the makepkg dependencies and the package built got success. Also many people wrote on AUR that they can install it smoothly without errors from linux and linux-lts kernels.
I was more referring to using the standard DKMS install method (not the standard Arch or Garuda methods).
More specifically, from that page:
To build a specific module for the currently running kernel:
# dkms install -m nvidia -v 334.21
I never tried it honestly. Does it have the latest patches/fixes from AUR? I thought that all the dkms patches have different maintainer so that's why they are not releasing at the same time and thought that AUR is the latest.