Arch Linux User Repository

For testing users, contributors: check out https://github.com/archlinux-jerry/nvidia-340xx
Warning: force push may happen to match the aur tree

Cannot install nvidia-340xx-dkms : First need to run it as " IGNORE_CC_MISMATCH=1 dkms install --no-depmod nvidia/340.108 -k 5.18.13-arch1-1 " Because of comparison btw GCC and CC (same versions) Next, into /var/lib/dkms/nvidia/340.108/source/ need to patch os-interface.h and nv.h to modify include of stdarg.h to linux/stdarg.h Then I figure out that patches are not applied into this directory (or I do not understand why they are here ^^) so I had a lot of errors. I stopped here, build nvidia-340xx, call manually dkms install to ignore CC mismatch, and it's installed properly. Now I have to reboot... Hope it works ! EDIT : finally forcing re-install of nvidia-340xx (it said installed but keep -dkms in place, maybe a mistake of I), works fine :)

Hi,

Doesn't work on my PC using mobo Gigabyte GA-E7AUM-DS2H (IGPU 9400), when I start gdm it generates watchdog soft lockup cpu stuck

@JerryXiao well, kernel says "PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug" on boot, yes. It is laptop, so no cables - direct connection, triple checked, cleansed by alcohol etc. On heavy drive access like "pacman -Qs nvidia" it starts to print "broken inode" if nvidia driver installed.

@sebalis I believe user should have the freedom to choose their own C compiler in makepkg.conf. I wouldn't override their preference unless it has to be done. Fixing the warning is a good thing, but we should try fixing the compiler version comparison code instead.
Also structleak_plugin of gcc would have blocked the compilation in case of a compiler version mismatch, so that check seems redundant. Maybe we can remove it entirely.

@JerryXiao When I build the package, I get the following message twice:

warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (GCC) 12.1.0
You are using: cc (GCC) 12.1.0

This occurs shortly after the lines

make[1]: Entering directory '/usr/lib/modules/5.18.3-arch1-1/build'

and

make[1]: Entering directory '/usr/lib/modules/5.18.3-arch1-1/build'

The only lines before the warning are echos of commands that are about to be executed.

At one point in the past there was a subsequent message during the installation process that a command had returned a non-zero exit status. I couldn’t reproduce that command when I tried just now.

However, it would still be a good thing in my view to remove this warning as it might cause uncertainty. Also I’m wondering if the issue could be more serious for users that might have an alternative C compilers installed.

@sebalis I don't see any issue with the current PKGBUILD. Tested on real hardware.
@dmanlfc no log, so no solution.
@alexzk ACPI bug? ACPI is working fine on my hardware. TBH how could an acpi bug corrupt your SSD? Do you have a bad sata cable or have you undervolted your CPU?

I installed this package on 5.18.1 and haven’t had issues since. My kernel is now 5.18.3 and I have just successfully built the package again (but didn’t bother to install it). Conincidentally, I did find I still had to add CC=gcc to the two calls to “make” and would appreciate an opinion from the maintainers about their reasons not to include that change. Do they not see this issue?

Doesn't build against the 5.18.2 kernel - is there a compilation patch by any chance?

I installed new SSD into old HP CQ 50 with GTX 8600M card. Installed fresh new arch. Once this driver 340xx boots (gui login) it breaks file system on SSD. Rolled back to nouveau and things work now.