You are not logged in.
As already mentioned in the linux-ck thread (https://bbs.archlinux.org/viewtopic.php?id=111715), the kernel version 4.9 breaks the system boot in combination with nvidia driver.
After booting, the system hangs with an error message "driver nvidia is already registered".
This problem is known for weeks, so why do the Arch Linux kernel maintainers push the kernel and nvidia driver from TESTING to STABLE branch?!
Affected versions:
core/linux 4.9.6-1 (base)
extra/nvidia-304xx 304.134-4
Offline
Maybe ur system is a little unique...
i just met a watchdog problem..
Offline
Build the nvidia-304xx driver applying the patch that the 340xx package uses to see if that is the problem. I do not have the hardware to test this on. Alternatively open a bug report against 304xx.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
or you Can just disable your nvidia card in BIOS ?
Offline
https://bugs.archlinux.org/task/52734 (opened today)
edit:
@indianahorst see also https://lists.archlinux.org/pipermail/a … 28538.html
Last edited by loqs (2017-01-27 17:51:46)
Offline
@loqs - Thank you for the references. I updated nvidia-304xx-ck with this patch.
@indiana - Please try it and report back.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I had the same issue and can confirm the patch is working for 4.9.6. I recompiled nvidia-304xx. All you need to do is modify the PKGBUILD to include a second patch file (I called it legacy.patch) and copied the debian patch into my custom patch file. Updated the source line, ran updpkgsums, makepkg -csi and reboot.
Last edited by slytux (2017-01-27 22:53:38)
Offline
@loqs - Thank you for the references. I updated nvidia-304xx-ck with this patch.
@indiana - Please try it and report back.
Graysky, I have now tried aur/nvidia-304xx-ck 304.134-4 in conjunction with repo-ck/linux-ck 4.9.6-1 (ck-generic) and the bug seems fixed! No error while booting, no error messages in dmesg.
It would be glad if you would patch also repo-ck/nvidia-304xx-ck-kx 304.134-3. Thanks a lot!
Offline
I had the same issue and can confirm the patch is working for 4.9.6. I recompiled nvidia-304xx. All you need to do is modify the PKGBUILD to include a second patch file (I called it legacy.patch) and copied the debian patch into my custom patch file. Updated the source line, ran updpkgsums, makepkg -csi and reboot.
I would like to try this but have never used a patch in a pkgbuild before. I would feel ok doing a single patch but don't see anything in the wiki about multiple patches, so I'm a bit leery of winging it. Could you explain your custom patch file, and/or share it?
I've already tried downgrading the kernel and nvidia drivers with no joy. Any wisdom would be much appreciated.
edit: I have the patch already, just not sure how to apply it along with the existing patch.
Last edited by akovia (2017-01-29 16:29:50)
Offline
https://aur.archlinux.org/packages/nvidia-304xx-ck/ see the PKGBUILD that applies both needed patches.
Offline
https://aur.archlinux.org/packages/nvidia-304xx-ck/ see the PKGBUILD that applies both needed patches.
Thank you for that.
Thought I was out of the woods, but now I'm getting a conflict when it's trying to install.
nvidia-304xx and nvidia-304xx-dkms are in conflict
Do I need to downgrade first?
Offline
Pacman should prompt you to remove nvidia-304xx-dkms when you try to install nvidia-304xx just accept the prompt to remove it.
If you want to keep the dkms version make sure the patch was applied to that then upgrade the dkms version.
Offline
Remove the dkms package then install the non-dkms package. Never understood wtf anyone would use dkms.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline