@MegaDeKay Yes, everything works with kernel 6.8 without manual intervention (tested on real hardware). Read here for more information:
https://github.com/archlinux-jerry/nvidia-340xx/issues/8
I've left the original post if someone still has a problem and copying 'drm_legacy.h' is a solution for them.
Search Criteria
Package Details: nvidia-340xx 340.108-37
Package Actions
Git Clone URL: | https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy) |
---|---|
Package Base: | nvidia-340xx |
Description: | NVIDIA drivers for linux, 340xx legacy branch |
Upstream URL: | https://www.nvidia.com/ |
Licenses: | custom |
Conflicts: | nvidia |
Submitter: | simonsmh |
Maintainer: | JerryXiao |
Last Packager: | JerryXiao |
Votes: | 72 |
Popularity: | 0.86 |
First Submitted: | 2019-06-07 10:29 (UTC) |
Last Updated: | 2024-05-10 16:52 (UTC) |
Dependencies (6)
- libgl (nvidia-340xx-utilsAUR, libglvnd-gitAUR, amdgpu-pro-oglpAUR, amdgpu-pro-oglp-legacyAUR, libglvnd)
- linux
- nvidia-340xx-utilsAUR
- linux (make)
- linux-headers (make)
- nvidia-340xx-utilsAUR (make)
Required by (5)
- bumblebee-forceunload (optional)
- bumblebee-git (optional)
- bumblebee-picasso-git (optional)
- nvfancontrol (optional)
- nvfancontrol-git (optional)
Sources (19)
- 0001-kernel-5.7.patch
- 0002-kernel-5.8.patch
- 0003-kernel-5.9.patch
- 0004-kernel-5.10.patch
- 0005-kernel-5.11.patch
- 0006-kernel-5.14.patch
- 0007-kernel-5.15.patch
- 0008-kernel-5.16.patch
- 0009-kernel-5.17.patch
- 0010-kernel-5.18.patch
- 0011-kernel-6.0.patch
- 0012-kernel-6.2.patch
- 0013-kernel-6.3.patch
- 0014-kernel-6.5.patch
- 0015-kernel-6.6.patch
- 0016-kernel-6.8.patch
- 0017-gcc-14.patch
- 20-nvidia.conf
- https://us.download.nvidia.com/XFree86/Linux-x86_64/340.108/NVIDIA-Linux-x86_64-340.108-no-compat32.run
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 58 Next › Last »
Anakievs commented on 2024-05-07 10:11 (UTC) (edited on 2024-05-07 10:15 (UTC) by Anakievs)
earlybird commented on 2024-05-07 09:14 (UTC)
is it possible to add an extra conflict package from conflicts=('nvidia') to conflicts=('nvidia' 'nvidia-dkms')
MegaDeKay commented on 2024-05-07 01:02 (UTC)
@Anakievs: To clarify, you are saying that everything works now with this driver compiled on Arch with a new 6.8 kernel, including direct rendering?
Anakievs commented on 2024-04-23 08:12 (UTC) (edited on 2024-04-23 08:14 (UTC) by Anakievs)
$ glxinfo | grep "direct rendering" direct rendering: Yes $ uname -r 6.8.7-arch1-1
holyArch commented on 2024-04-23 00:07 (UTC)
@Anakievs: What's the output if you run: glxinfo | grep "direct rendering"?
"Yes" or "No"?
Anakievs commented on 2024-04-15 19:03 (UTC)
@NSLW I don't have a black screen issue. I've thought I've made something revolutionary about the drm issue. Then I've realised that I've made nothing.
I've just compiled the driver on Debian 12. I like Arch a lot more but I look for other options.
NSLW commented on 2024-04-13 15:53 (UTC) (edited on 2024-04-13 15:54 (UTC) by NSLW)
@Anakievs did you try to add
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection
to your /etc/X11/xorg.conf to fix the black screen issue?
Anakievs commented on 2024-04-07 18:21 (UTC) (edited on 2024-04-29 11:25 (UTC) by Anakievs)
Edit:
The driver works and the steps bellow aren't requared. I've trusted the people saying there is an issue without confirming it myself.
Original:
Here is a workaround I've used (it's based on lmh69's comment).
I've extracted 'drm_legacy.h' from 'linux-headers-6.7.arch3-1-x86_64.pkg.tar.zst' to '/usr/lib/modules/6.8.4-arch1-1/build/include/drm/drm_legacy.h'. Then I've reinstalled both 'linux-headers' (to run dkms) [and 'linux' to run mkinitcpio] you can run them manually but this way was easier for me.
I've tested just a few things: vdpau, glx, Xorg.0.log and dmesg. I haven't found any issues so far.
IMPORTANT: I am still with 'nvidia-340xx-dkms 340.108-35'. I've never updated. It won't work with 'nvidia-340xx-dkms 340.108-36'.
I don't know if it's wrong but works for me:
$ uname -r 6.8.4-arch1-1 $ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 303 frames in 5.0 seconds = 60.491 FPS 300 frames in 5.0 seconds = 59.972 FPS $ mpv ... (+) Video --vid=1 (*) (h264 1280x720 25.000fps) (+) Audio --aid=1 (*) (aac 2ch 44100Hz) Using hardware decoding (vdpau). AO: [pulse] 44100Hz stereo 2ch float VO: [gpu] 1280x720 vdpau[yuv420p] Exiting... (Quit)
xbelanch commented on 2024-03-24 15:02 (UTC) (edited on 2024-03-24 15:03 (UTC) by xbelanch)
Although I have installed nvidia-340xx-dkms 340.108-36 under 6.8.1-arch1-1 kernel, every time I'm trying to launch any "opengl" application raises this:
$ kitty
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 155 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x1000009
Serial number of failed request: 241
Current serial number in output stream: 241
TheExplorer commented on 2024-03-20 12:18 (UTC)
@lmh69 @ JerryXiao Who maintains the patches? I mean who writes them? I guess someone has to help him with 'drm' thing.
Pinned Comments
JerryXiao commented on 2022-10-13 03:51 (UTC) (edited on 2022-10-14 02:44 (UTC) by JerryXiao)
For testing users, contributors: check out https://github.com/archlinux-jerry/nvidia-340xx
Warning: force push may happen to match the aur tree