* Nvidia probem? @ 2015-06-05 17:45 Stefan Mühlinghaus 2015-06-06 6:05 ` Frankie Wild ` (2 more replies) 0 siblings, 3 replies; 14+ messages in thread From: Stefan Mühlinghaus @ 2015-06-05 17:45 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 488 bytes --] Can someone confirm if the current nvidia package is working properly? It seems that on my system the nvidia.ko and nvidia-uvm.ko modules are not beeing generated so dracut fails when trying to package them. Downgrading to the previous version has the same effect, so I assume the problem is not with the nvidia package itself. My current guess is that there is some incompatibility with the linux-headers package... or I managed to put my system in some inconsistent state. [-- Attachment #1.2: Type: text/html, Size: 499 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-05 17:45 Nvidia probem? Stefan Mühlinghaus @ 2015-06-06 6:05 ` Frankie Wild 2015-06-06 7:29 ` Juan RP 2015-06-06 9:34 ` Stefan Mühlinghaus 2015-06-06 10:01 ` Stefan Mühlinghaus 2 siblings, 1 reply; 14+ messages in thread From: Frankie Wild @ 2015-06-06 6:05 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 860 bytes --] I never managed to get my GT635M working but it might be a different issue. I am using a Thinkpad E530 with Optimus and don't have a setting in BIOS to disable the integrated graphics. From what I tried so far I always end up with 'failed to load DRM permission denied' On Friday, June 5, 2015 at 8:45:46 PM UTC+3, Stefan Mühlinghaus wrote: > > Can someone confirm if the current nvidia package is working properly? It > seems that on my system the nvidia.ko and nvidia-uvm.ko modules are not > beeing generated so dracut fails when trying to package them. Downgrading > to the previous version has the same effect, so I assume the problem is not > with the nvidia package itself. My current guess is that there is some > incompatibility with the linux-headers package... or I managed to put my > system in some inconsistent state. > [-- Attachment #1.2: Type: text/html, Size: 997 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-06 6:05 ` Frankie Wild @ 2015-06-06 7:29 ` Juan RP 0 siblings, 0 replies; 14+ messages in thread From: Juan RP @ 2015-06-06 7:29 UTC (permalink / raw) To: void..., green... [-- Attachment #1.1: Type: text/plain, Size: 551 bytes --] This is just an artifact of an incomplete /usr/sbin merge switch. Please run the following commands to have a working system and with /usr/sbin fully merged: - xbps-install -Suv - if /usr/sbin is a directory and not a symlink, remove all regular files on it, keep the symlinks. - Reboot - runit-void will then make /usr/sbin a symlink to /usr/bin, and the old /usr/sbin directory will be renamed to /usr/sbin.old - Reconfigure nvidia `xbps-reconfigure -f nvidia{,-dkms}` - Your system should be fully functional again. Cheers [-- Attachment #1.2: Type: text/html, Size: 600 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-05 17:45 Nvidia probem? Stefan Mühlinghaus 2015-06-06 6:05 ` Frankie Wild @ 2015-06-06 9:34 ` Stefan Mühlinghaus 2015-06-06 9:45 ` Juan RP 2015-06-06 10:01 ` Stefan Mühlinghaus 2 siblings, 1 reply; 14+ messages in thread From: Stefan Mühlinghaus @ 2015-06-06 9:34 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 1996 bytes --] I can confirm that the /usr/sbin transition was not complete on my system, but fixing that did not fix the original problem. Executing "xbps-reconfigure -f nvidia" still gets me: Regenerating initramfs, please wait... /usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 13: /lib/ modules/4.0.4_1//kernel/drivers/video/nvidia.ko: No such file or directory /usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 13: /lib/ modules/4.0.4_1//kernel/drivers/video/nvidia-uvm.ko: No such file or directory So I went to /usr/src/nvidia-346.72 and tried a "make": NVIDIA: calling KBUILD... make[1]: Entering directory '/usr/src/kernel-headers-4.0.4_1' make -f ./Makefile silentoldconfig make -f ./scripts/Makefile.build obj=scripts/basic rm -f .tmp_quiet_recordmcount make -f ./scripts/Makefile.build obj=scripts/kconfig silentoldconfig mkdir -p include/config include/generated scripts/kconfig/conf --silentoldconfig Kconfig make -f ./scripts/Makefile.build obj=arch/x86/syscalls all scripts/Makefile.build:44: arch/x86/syscalls/Makefile: No such file or directory make[2]: *** No rule to make target 'arch/x86/syscalls/Makefile'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make[1]: *** [archheaders] Error 2 make[1]: Leaving directory '/usr/src/kernel-headers-4.0.4_1' NVIDIA: left KBUILD. nvidia.ko failed to build! nvidia-modules-common.mk:248: recipe for target 'module' failed make: *** [module] Error 1 As is to be expected, the same happens in /usr/src/kernel-headers-4.0.4_1 directly: scripts/Makefile.build:44: arch/x86/syscalls/Makefile: No such file or directory make[1]: *** No rule to make target 'arch/x86/syscalls/Makefile'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 That "arch/x86/syscalls" directory is not part of the linux4.0-headers package. Do I need to generate it somehow? Or am I missing something else entirely? [-- Attachment #1.2: Type: text/html, Size: 21410 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-06 9:34 ` Stefan Mühlinghaus @ 2015-06-06 9:45 ` Juan RP 2015-06-10 23:09 ` John Bowles 2015-06-12 3:14 ` JD Robinson 0 siblings, 2 replies; 14+ messages in thread From: Juan RP @ 2015-06-06 9:45 UTC (permalink / raw) To: void..., master... [-- Attachment #1.1: Type: text/plain, Size: 467 bytes --] This Makefile you are mentioning about does not seem to exist. What I think happened is that the first upgrade executed dkms and this failed to build the nvidia kmods, but dkms thinks it was built and installed correctly. Do this: - dkms build -m nvidia -v 346.72 -k $(uname -r) - dkms install -m nvidia -v 346.72 -k $(uname -r) - xbps-reconfigure -f nvidia Before running xbps-reconfigure, make sure the kmods are built and installed correctly. [-- Attachment #1.2: Type: text/html, Size: 504 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-06 9:45 ` Juan RP @ 2015-06-10 23:09 ` John Bowles 2015-06-11 17:18 ` Stefan Mühlinghaus 2015-06-12 7:51 ` Stefan Mühlinghaus 2015-06-12 3:14 ` JD Robinson 1 sibling, 2 replies; 14+ messages in thread From: John Bowles @ 2015-06-10 23:09 UTC (permalink / raw) To: voidlinux; +Cc: master... [-- Attachment #1.1: Type: text/plain, Size: 256 bytes --] The proprietary Nvidia module was working fine . /usr/sbin is a symlink. the module builds OK but depmod fails with an exit status of 127 after this > - dkms install -m nvidia -v 346.72 -k $(uname -r) > > Does anyone have any further suggestions? [-- Attachment #1.2: Type: text/html, Size: 443 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-10 23:09 ` John Bowles @ 2015-06-11 17:18 ` Stefan Mühlinghaus 2015-06-11 21:22 ` John Bowles 2015-06-12 7:51 ` Stefan Mühlinghaus 1 sibling, 1 reply; 14+ messages in thread From: Stefan Mühlinghaus @ 2015-06-11 17:18 UTC (permalink / raw) To: voidlinux; +Cc: master... [-- Attachment #1.1: Type: text/plain, Size: 156 bytes --] Did you compile/install the module as root? What exactly is the error message? My guess is that the 127 is probably coming from make, not from depmod. [-- Attachment #1.2: Type: text/html, Size: 171 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-11 17:18 ` Stefan Mühlinghaus @ 2015-06-11 21:22 ` John Bowles 0 siblings, 0 replies; 14+ messages in thread From: John Bowles @ 2015-06-11 21:22 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 320 bytes --] compiled as root via sudo error msg: depmod failed (bad exit status 127) On Friday, June 12, 2015 at 5:18:24 AM UTC+12, Stefan Mühlinghaus wrote: > > Did you compile/install the module as root? What exactly is the error > message? My guess is that the 127 is probably coming from make, not from > depmod. > [-- Attachment #1.2: Type: text/html, Size: 477 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-10 23:09 ` John Bowles 2015-06-11 17:18 ` Stefan Mühlinghaus @ 2015-06-12 7:51 ` Stefan Mühlinghaus 2015-06-12 9:14 ` John Bowles 1 sibling, 1 reply; 14+ messages in thread From: Stefan Mühlinghaus @ 2015-06-12 7:51 UTC (permalink / raw) To: voidlinux; +Cc: master... [-- Attachment #1.1: Type: text/plain, Size: 78 bytes --] Do you also get an error when you run something lilke "depmod -nv" manually? [-- Attachment #1.2: Type: text/html, Size: 102 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-12 7:51 ` Stefan Mühlinghaus @ 2015-06-12 9:14 ` John Bowles 2015-06-12 14:04 ` Scott Girling 0 siblings, 1 reply; 14+ messages in thread From: John Bowles @ 2015-06-12 9:14 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 238 bytes --] 2.6meg of text? depmod -nv | grep nvidia: kernel/drivers/net/ethernet/nvidia/forcedeth.ko.gz: alias mbp_nvidia_bl apple_bl no error message in the depmod output. I'll try after cleaning /usr/src/nvidia-346.72 & dkms build etc. [-- Attachment #1.2: Type: text/html, Size: 275 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-12 9:14 ` John Bowles @ 2015-06-12 14:04 ` Scott Girling 2015-06-12 20:54 ` John Bowles 0 siblings, 1 reply; 14+ messages in thread From: Scott Girling @ 2015-06-12 14:04 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 610 bytes --] I have been having the same problem for a couple of days, but I stayed determined and I just figured out how to solve it. Check your /sbin directory and make sure the void-installer binary is removed. Reboot and reconfigure nvidia. Worked for me, I hope it works for you. On Friday, June 12, 2015 at 7:14:58 PM UTC+10, John Bowles wrote: > > 2.6meg of text? > > depmod -nv | grep nvidia: > kernel/drivers/net/ethernet/nvidia/forcedeth.ko.gz: > alias mbp_nvidia_bl apple_bl > > no error message in the depmod output. I'll try after cleaning > /usr/src/nvidia-346.72 & dkms build etc. > [-- Attachment #1.2: Type: text/html, Size: 787 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-12 14:04 ` Scott Girling @ 2015-06-12 20:54 ` John Bowles 0 siblings, 0 replies; 14+ messages in thread From: John Bowles @ 2015-06-12 20:54 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 570 bytes --] Fixed! Thanks to everyone for their help. Especially JD Robinson's lxdm hint. The problem was entirely mine. I missed the one regular file (i.e non-symlink) in /usr/sbin with the virtual terminal switching every 4 seconds so I didn't delete it. I started from scratch again, stopped lxdm and then I could see it. After rebooting and dkms remove -m nvidia -v 346.72 -k $(uname -r) dkms build -m nvidia -v 346.72 -k $(uname -r) dkms install -m nvidia -v 346.72 -k $(uname -r) modprobe -v nvidia sv start lxdm and I was back to a graphical desktop. [-- Attachment #1.2: Type: text/html, Size: 3593 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-06 9:45 ` Juan RP 2015-06-10 23:09 ` John Bowles @ 2015-06-12 3:14 ` JD Robinson 1 sibling, 0 replies; 14+ messages in thread From: JD Robinson @ 2015-06-12 3:14 UTC (permalink / raw) To: voidlinux [-- Attachment #1: Type: text/plain, Size: 158 bytes --] This also seems to have worked for me. I had a difficult time logging in because lxdm was respawning. sv stop lxdm For anyone having a similar issue. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Nvidia probem? 2015-06-05 17:45 Nvidia probem? Stefan Mühlinghaus 2015-06-06 6:05 ` Frankie Wild 2015-06-06 9:34 ` Stefan Mühlinghaus @ 2015-06-06 10:01 ` Stefan Mühlinghaus 2 siblings, 0 replies; 14+ messages in thread From: Stefan Mühlinghaus @ 2015-06-06 10:01 UTC (permalink / raw) To: voidlinux [-- Attachment #1.1: Type: text/plain, Size: 83 bytes --] Yes, that did it. All working correctly now. Thank you very much for your help! [-- Attachment #1.2: Type: text/html, Size: 100 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2015-06-12 20:54 UTC | newest] Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-06-05 17:45 Nvidia probem? Stefan Mühlinghaus 2015-06-06 6:05 ` Frankie Wild 2015-06-06 7:29 ` Juan RP 2015-06-06 9:34 ` Stefan Mühlinghaus 2015-06-06 9:45 ` Juan RP 2015-06-10 23:09 ` John Bowles 2015-06-11 17:18 ` Stefan Mühlinghaus 2015-06-11 21:22 ` John Bowles 2015-06-12 7:51 ` Stefan Mühlinghaus 2015-06-12 9:14 ` John Bowles 2015-06-12 14:04 ` Scott Girling 2015-06-12 20:54 ` John Bowles 2015-06-12 3:14 ` JD Robinson 2015-06-06 10:01 ` Stefan Mühlinghaus
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).