Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: > > Can anyone tell me where PORTS_MODULES is documented? I don't find it in > the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I > thing) wrote it. This is a very beneficial tool. It really needs to be well > documented. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkober...@gmail.com I found it in the make.conf(5) man page. I will say, however, that the description is fairly skimpy and I wouldn't have really known how to use it to solve my nvidia driver problem w/o the help of folks here. A more complete description, preferably with a few examples, would really help to understand how it is actually used. Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
Any hope to get a bit of text on this into the Handbook? Maybe with the example in Doug B.'s e-mail announcing it. (It's in the ports archive and DuckDuckGo can find it easily.) The example in build(7) is for a single module while Doug's message show that they should be space delimited. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com On Sat, Jan 17, 2015 at 9:28 PM, David Wolfskill wrote: > On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: > > ... > > Can anyone tell me where PORTS_MODULES is documented? I don't find it in > > the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I > > thing) wrote it. This is a very beneficial tool. It really needs to be > well > > documented. > > ... > > build(7) has it. > > (I confess that I didn't recall this, nor it it just "magically occur" > to me. Rather, brute force works again: > > grep -Zwr PORTS_MODULES /usr/share/man/man* > > Ugly, perhaps, but effective. :-}) > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > Those who murder in the name of God or prophet are blasphemous cowards. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: > ... > Can anyone tell me where PORTS_MODULES is documented? I don't find it in > the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I > thing) wrote it. This is a very beneficial tool. It really needs to be well > documented. > ... build(7) has it. (I confess that I didn't recall this, nor it it just "magically occur" to me. Rather, brute force works again: grep -Zwr PORTS_MODULES /usr/share/man/man* Ugly, perhaps, but effective. :-}) Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpw45ConolGY.pgp Description: PGP signature
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 8:34 PM, Bob Willcox wrote: > On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: > > On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > > > > > > Hi, > > > > > > The nvidia-driver package needs to be recompiled with the latest > > > FreeBSD-current sources, because of changes in the callout subsystem. > > > > > > If this is not possible, we can temporarily add the > "_callout_stop_safe" > > > symbol to the kernel for some transition time. > > > ... > > > > While I'm running i386 (vs. amd64), I have not encountered the cited > > issue. > > > > Given the above, I suspect that the fact that I have the line: > > > > PORTS_MODULES=x11/nvidia-driver > > > > > > in /etc/src.conf has a fair amount of (positive) influence on that. > > > > (I track stable/10 & head -- on different slices -- daily on my laptop.) > > > > Peace, > > david > > Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my > /etc/src.conf > file and rebuilding the kernel fixed it! > > Learn something new every day! :) > Can anyone tell me where PORTS_MODULES is documented? I don't find it in the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I thing) wrote it. This is a very beneficial tool. It really needs to be well documented. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: > On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > > > > Hi, > > > > The nvidia-driver package needs to be recompiled with the latest > > FreeBSD-current sources, because of changes in the callout subsystem. > > > > If this is not possible, we can temporarily add the "_callout_stop_safe" > > symbol to the kernel for some transition time. > > ... > > While I'm running i386 (vs. amd64), I have not encountered the cited > issue. > > Given the above, I suspect that the fact that I have the line: > > PORTS_MODULES=x11/nvidia-driver > > > in /etc/src.conf has a fair amount of (positive) influence on that. > > (I track stable/10 & head -- on different slices -- daily on my laptop.) > > Peace, > david Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my /etc/src.conf file and rebuilding the kernel fixed it! Learn something new every day! :) Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 7:43 AM, Andreas Tobler wrote: > On 17.01.15 16:18, Bob Willcox wrote: > >> Yesterday when I upgraded my current box I encountered this failure when >> attempting to load the nvidia-driver (nvidia.so): >> >> link_elf_obj: symbol _callout_stop_safe undefined >> linker_load_file: Unsupported file type >> >> So, today I updtated my system again today hoping it might be fixed but >> the >> problem persists. >> >> System info: >> >> FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat >> Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN >> amd64 >> > > I think you have to rebuild the nvidia-driver against your fresh built > system. At least I had and my T510 s working again with the nvidia.ko. > > David W. really has it right. If you rebuild the kernel, any port installing a kernel module needs to be rebuilt, as well. The use of PORT_MODULES in /etc/src.conf is the best way to make sure it happens. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On 17.01.15 16:18, Bob Willcox wrote: Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 I think you have to rebuild the nvidia-driver against your fresh built system. At least I had and my T510 s working again with the nvidia.ko. Gruss, Andreas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > On 01/17/15 16:18, Bob Willcox wrote: > > Yesterday when I upgraded my current box I encountered this failure when > > attempting to load the nvidia-driver (nvidia.so): > > > > link_elf_obj: symbol _callout_stop_safe undefined > > linker_load_file: Unsupported file type > > > > So, today I updtated my system again today hoping it might be fixed but the > > problem persists. > > > > System info: > > > > FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat > > Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN > > amd64 > > > > Thanks, > > Bob > > > > Hi, > > The nvidia-driver package needs to be recompiled with the latest > FreeBSD-current sources, because of changes in the callout subsystem. > > If this is not possible, we can temporarily add the "_callout_stop_safe" > symbol to the kernel for some transition time. > ... While I'm running i386 (vs. amd64), I have not encountered the cited issue. Given the above, I suspect that the fact that I have the line: PORTS_MODULES=x11/nvidia-driver in /etc/src.conf has a fair amount of (positive) influence on that. (I track stable/10 & head -- on different slices -- daily on my laptop.) Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpu5UZEWvWbm.pgp Description: PGP signature
Re: CURRENT breaks loading of nvidia.so
On 01/17/15 16:18, Bob Willcox wrote: Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 Thanks, Bob Hi, The nvidia-driver package needs to be recompiled with the latest FreeBSD-current sources, because of changes in the callout subsystem. If this is not possible, we can temporarily add the "_callout_stop_safe" symbol to the kernel for some transition time. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
