Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 03:14:39PM -0700, Ngie Cooper wrote: > > > On Aug 11, 2017, at 12:34, Bob Willcox wrote: > > > >> On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: > >> On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > > On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > modules were built: > > > > ipfw.ko > > ipfw_nat.ko > > ipfw_nat64.ko > > ipfw_nptv6.ko > > ng_ipfw.ko > > > > and only this ipfw module was built: > > > > ng_ipfw.ko > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > freebsd-base-graphics branch) is failing to load ipfw so my firewall > > isn't > > starting. > > > > So, what am I missing? Is it possible that the freebsd-base-graphics > > branch > > that I'm running has an old or improper version of /etc/rc.d/ipfw? > >> > >> [...] > >> > >>> include GENERIC_DRM > >> > >> GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are > >> built. In particular, ipfw*.ko does not get built. You'll need to either > >> remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make > >> kernel builds somewhat slower), or add > >> > >> makeoptionsMODULES_OVERRIDE+= ipfw ... > >> > >> to your custom config. > > Or add "MODULES_OVERRIDE+= ipfw..." to your src.conf. > Cheers, > -Ngie Well, I added the 'makeoptions MODULES_OVERRIDE+= ipfw' to my kernel config and rebuilt my kernel and it did build ipfw.ko as expected. I haven't installed this new kernel yet since I am not at a good point here at work to do that right now...but will when I get a chance. Thanks all for the help. -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
> On Aug 11, 2017, at 12:34, Bob Willcox wrote: > >> On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: >> On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > modules were built: > > ipfw.ko > ipfw_nat.ko > ipfw_nat64.ko > ipfw_nptv6.ko > ng_ipfw.ko > > and only this ipfw module was built: > > ng_ipfw.ko > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > starting. > > So, what am I missing? Is it possible that the freebsd-base-graphics > branch > that I'm running has an old or improper version of /etc/rc.d/ipfw? >> >> [...] >> >>> include GENERIC_DRM >> >> GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are >> built. In particular, ipfw*.ko does not get built. You'll need to either >> remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make >> kernel builds somewhat slower), or add >> >> makeoptionsMODULES_OVERRIDE+= ipfw ... >> >> to your custom config. Or add "MODULES_OVERRIDE+= ipfw..." to your src.conf. Cheers, -Ngie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: > On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > > > > On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > > > > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > > > modules were built: > > > > > > > > ipfw.ko > > > > ipfw_nat.ko > > > > ipfw_nat64.ko > > > > ipfw_nptv6.ko > > > > ng_ipfw.ko > > > > > > > > and only this ipfw module was built: > > > > > > > > ng_ipfw.ko > > > > > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > > > freebsd-base-graphics branch) is failing to load ipfw so my firewall > > > > isn't > > > > starting. > > > > > > > > So, what am I missing? Is it possible that the freebsd-base-graphics > > > > branch > > > > that I'm running has an old or improper version of /etc/rc.d/ipfw? > > [...] > > > include GENERIC_DRM > > GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are > built. In particular, ipfw*.ko does not get built. You'll need to either > remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make > kernel builds somewhat slower), or add > > makeoptions MODULES_OVERRIDE+= ipfw ... > > to your custom config. > > > > > ident TAVION_DRM > > > > nooptions INVARIANTS > > nooptions INVARIANT_SUPPORT > > nooptions DEBUG_MEMGUARD > > nooptions DEBUG_REDZONE > > nooptions WITNESS > > nooptions WITNESS_ALL > > nooptions WITNESS_SKIPSPIN > > > > options TMPFS Ok, thanks for that. I'll give that a try, but probably not till next time I am ready to update this system (I use it for my day job and updating it is a pain since I need to run the drm-next mods/branch). -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > > > On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > > modules were built: > > > > > > ipfw.ko > > > ipfw_nat.ko > > > ipfw_nat64.ko > > > ipfw_nptv6.ko > > > ng_ipfw.ko > > > > > > and only this ipfw module was built: > > > > > > ng_ipfw.ko > > > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > > freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > > > starting. > > > > > > So, what am I missing? Is it possible that the freebsd-base-graphics > > > branch > > > that I'm running has an old or improper version of /etc/rc.d/ipfw? [...] > include GENERIC_DRM GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are built. In particular, ipfw*.ko does not get built. You'll need to either remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make kernel builds somewhat slower), or add makeoptions MODULES_OVERRIDE+= ipfw ... to your custom config. > > ident TAVION_DRM > > nooptions INVARIANTS > nooptions INVARIANT_SUPPORT > nooptions DEBUG_MEMGUARD > nooptions DEBUG_REDZONE > nooptions WITNESS > nooptions WITNESS_ALL > nooptions WITNESS_SKIPSPIN > > options TMPFS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 12:55:14PM -0600, Ngie Cooper wrote: > > > On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > modules were built: > > > > ipfw.ko > > ipfw_nat.ko > > ipfw_nat64.ko > > ipfw_nptv6.ko > > ng_ipfw.ko > > > > and only this ipfw module was built: > > > > ng_ipfw.ko > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > > starting. > > > > So, what am I missing? Is it possible that the freebsd-base-graphics branch > > that I'm running has an old or improper version of /etc/rc.d/ipfw? > > Hi Bob, > Can you please provide your make.conf, src.conf, and KERNCONF? > Thank you! > -Ngie Sure. BTW, I cd'd into /usr/freebsd-base-graphics/sys/modules (my drm-next src is in /usr/freebsd-base-graphics), ran make, then copied the ipfw/ipfw.ko file to /boot/kernel and was able to start ipfw after that. * make.conf * KERNCONF= TAVION ALWAYS_CHECK_MAKE= yes BATCH= yes DEFAULT_VERSIONS+= linux=c6 DEFAULT_VERSIONS+= ssl=openssl COMPAT4X= yes COMPAT5X= yes COMPAT6X= yes COMPAT7X= yes COMPAT8X= yes COMPAT9X= yes * src.conf * -- doesn't exit * KERNCONF * # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD$ include GENERIC_DRM ident TAVION_DRM nooptions INVARIANTS nooptions INVARIANT_SUPPORT nooptions DEBUG_MEMGUARD nooptions DEBUG_REDZONE nooptions WITNESS nooptions WITNESS_ALL nooptions WITNESS_SKIPSPIN options TMPFS -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
> On Aug 11, 2017, at 10:36, Bob Willcox wrote: > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel modules > were built: > > ipfw.ko > ipfw_nat.ko > ipfw_nat64.ko > ipfw_nptv6.ko > ng_ipfw.ko > > and only this ipfw module was built: > > ng_ipfw.ko > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > starting. > > So, what am I missing? Is it possible that the freebsd-base-graphics branch > that I'm running has an old or improper version of /etc/rc.d/ipfw? Hi Bob, Can you please provide your make.conf, src.conf, and KERNCONF? Thank you! -Ngie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r322076 breaks vtnet connectivity
On 08/11/17 01:48, Jung-uk Kim wrote: On 08/10/2017 21:27, Ian FREISLICH wrote: I have a host on Digital Ocean (qemu) and the change in r322076 breaks my vtnet0 interface. The interface still comes up but does not pass traffic any more. It's not obvious to my why the changes from r322075 to r322076 affect the vtnet interface. Can you please try r322323 or later? Basically, r322076 was incomplete and r322323 corrected the stupid mistake. Thanks, that fixes it. Ian -- Cape Augusta Digital Properties, LLC a Cape Augusta Company *Breach of confidentiality & accidental breach of confidentiality * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ipfw kernel module not being built
When I rebuild my kernel on Jun 13th none of the previous ipfw kernel modules were built: ipfw.ko ipfw_nat.ko ipfw_nat64.ko ipfw_nptv6.ko ng_ipfw.ko and only this ipfw module was built: ng_ipfw.ko However, the verson of /etc/rc.d/ipfw that I'm running (from the freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't starting. So, what am I missing? Is it possible that the freebsd-base-graphics branch that I'm running has an old or improper version of /etc/rc.d/ipfw? -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
clang error make buildworld
I am tying to buildworld on an ivybridge (amd64) machine and I get the following error: ===> lib/libc/tests/ssp (all) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_fgets NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_fgets ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_gets NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_gets ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_getcwd NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_getcwd ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_memcpy NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_memcpy ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_memmove NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_memmove ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_memset NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_memset ) (cd /usr/src/lib/libc/tests/ssp && DEPENDFILE=.depend.h_raw NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/ssp/Makefile _RECURSING_PROGS=t PROG=h_raw ) cc -target x86_64-unknown-freebsd12.0 --sysroot=/mnt/ObjDir/usr/src/tmp -B/mnt/ObjDir/usr/src/tmp/usr/bin -O0 -pipe -fstack-protector-all -Wstack-protector -fsanitize=bounds -g -std=gnu99 -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Qunused-arguments -o h_raw.full h_raw.o /mnt/ObjDir/usr/src/tmp/usr/lib/libgcc_s.so: undefined reference to `__gxx_personality_v0' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[7]: stopped in /usr/src/lib/libc/tests/ssp *** Error code 1 Stop. make[6]: stopped in /usr/src/lib/libc/tests/ssp *** Error code 1 Stop. make[5]: stopped in /usr/src/lib/libc/tests *** Error code 1 Stop. make[4]: stopped in /usr/src/lib/libc *** Error code 1 Stop. make[3]: stopped in /usr/src/lib *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src My /etc/make.conf contains: CPUTYPE?= ivybridge and whereas my /etc/src.conf contains: CFLAGS= -O0 -pipe COPTFLAGS= -O0 -pipe DEBUG_FLAGS=-g By the way it looks like clang is linking against gcc libraries?? How can that be possible? I thought GCC and CLANG are more like competitors in the world of compilers. Perhaps I am missing something here. Nevertheless how do I get rid of this issue? -- Best Regards, Aijaz Baig ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[mergemaster] Batch capabilities blockes by /.cshrc and sibblings
Within a NanoBSD automated installation of jails following the (outdated) instructions and templates given in chapter 14 of the handbook, I run into trouble installing the skeleton config files via "mergemaster". mergemaster always stops at this point: [...] *** There is no installed version of ./.cshrc *** Historically BSD derived systems have had a hard link from /.cshrc and /.profile to their namesakes in /root. Please indicate your preference below for bringing your installed files up to date. Use 'd' to delete the temporary ./.cshrc Use 'l' to delete the existing /pool/nanobsd/amd64/ALERICH_amd64/_.w/jails/skel/root/.cshrc and create the link Default is to leave the temporary file to deal with by hand How should I handle ./.cshrc? [Leave it to install later] [...] This si really frustrating, since I do not know how to prevent this. using option "-a" with mergemaster leaves me with uninstalled files in temproot. How can I force mergemaster to receive "d" for deletion? Kind regards, Oliver ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
