Re: ipfw "unknown interface name igb1" SOLVED

[Graham Menhennitt]

Thanks for replying, Sergey.

The "igb" device is no longer available as an option in the kernel 
source - I need to use "em" instead. Without "em" most things still 
work, though - just not the ipfw rules on boot. Strangely, my interfaces 
still come up as "igb".


Anyway, with "em" it all now works. Thanks!

Graham

On 23/3/19 11:55 am, Korolev Sergey wrote:

Hello!
Igb device was removed in version 12. Maybe this causes a problem. 
Maybe you should rename it to new appropriate one.


On 23 Mar 2019, at 10:49, Graham Menhennitt > wrote:


Hi all,

I recently upgraded (via source) from 11-Stable to 12-Stable on my 
router box (PC Engines APU). My firewall rules don't appear to work 
any longer during boot. I can see on the console "Line 98: unknown 
interface name igb1" when it tries to load them. The last few rules 
after the error line are not loaded. Line 98 is the "nat 1 config" line.


After boot, I run "ipfw flush;service ipfw restart" and everything 
works ok. It looks like the igb1 interface isn't fully available at 
the time when it originally tries to load.


My relevant lines (redacted) from /etc/rc.conf, /etc/ipfw.rules, and 
tail of /var/log/messages are below.


Any clues, please?

Thanks in advance,


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD Quarterly Status Report - Fourth Quarter 2018

[Edward Tomasz Napierała]

FreeBSD Project Quarterly Status Report - 4th Quarter 2018

   Since we are still on this island among many in this vast ocean of the
   Internet, we write this message in a bottle to inform you of the work
   we have finished and what lies ahead of us. These deeds that we have
   wrought with our minds and hands, they are for all to partake of - in
   the hopes that anyone of their free will, will join us in making
   improvements. In todays message the following by no means complete or
   ordered set of improvements and additions will be covered:

   i386 PAE Pagetables for up to 24GB memory support, Continuous
   Integration efforts, driver updates to ENA and graphics, ARM
   enhancements such as RochChip, Marvell 8K, and Broadcom support as well
   as more DTS files, more Capsicum possibilities, as well as pfsync
   improvements, and many more things that you can read about for
   yourselves.

   Additionally, we bring news from some islands further down stream,
   namely the nosh project, HardenedBSD, ClonOS, and the Polish BSD
   User-Group.

   We would, selfishly, encourage those of you who give us the good word
   to please send in your submissions sooner than just before the
   deadline, and also encourage anyone willing to share the good word to
   please read the section on which submissions we're also interested in
   having.

   Yours hopefully,
   Daniel Ebdrup, on behalf of the status report team.
 __

FreeBSD Team Reports

 * Continuous Integration
 * FreeBSD Core Team
 * FreeBSD Foundation
 * FreeBSD Graphics Team status report
 * FreeBSD Release Engineering Team
 * Ports Collection

Projects

 * amd64 Usermode Protection Keys
 * bhyve - Live Migration
 * bhyve - Save/Restore
 * Capsicum
 * Collection of vt(4) color schemes
 * i386 PAE Pagetables
 * Improving FreeBSD boot security
 * pfsync performance improvement
 * PWM Kernel API and userland utility

Architectures

 * Broadcom ARM64 SoC support
 * DTS Update
 * ENA FreeBSD Driver Update
 * FreeBSD on Power9 (ppc64) Parity
 * FreeBSD/RISC-V update
 * libvdsk - QCOW2 implementation
 * Marvell 8K SoC support
 * Pinebook SDCard Image
 * RockChip Support

Ports

 * FreeBSD KDE status report

Miscellaneous

 * BSD PL

Third-Party Projects

 * ClonOS: virtualization platform on top of FreeBSD Operating System
 * HardenedBSD 2018Q4 Update
 * The nosh project
 __

FreeBSD Team Reports

   Entries from the various official and semi-official teams, as found in
   the Administration Page.

Continuous Integration

   Links
   FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org
   FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org/
   FreeBSD Jenkins wiki URL: https://wiki.freebsd.org/Jenkins
   freebsd-testing Mailing List URL:
   https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing
   freebsd-ci Repository URL: https://github.com/freebsd/freebsd-ci
   Tickets related to freebsd-testing@ URL:
   https://preview.tinyurl.com/y9maauwg
   Hosted CI wiki URL: https://wiki.freebsd.org/HostedCI

   Contact: Jenkins Admin 
   Contact: Li-Wen Hsu 

   The FreeBSD CI team maintains continuous integration system and related
   tasks for the FreeBSD project. The CI system regularly checks the
   changes committed to the project's Subversion repository can be
   successfully built, and performs various tests and analysis over the
   results. The results from build jobs are archived in artifact server,
   for the further testing and debugging needs.

   The members on the CI team examine the failing builds and unstable
   tests, and work with the experts in that area to fix the code or build
   and test infrastructure, to improve the software quality of the FreeBSD
   base system. The CI team member and the FreeBSD foundation staff Li-Wen
   is the maintainer of Jenkins and Jenkins related ports.

   In this quarter, we worked on extending test executing environment to
   improve the coverage, temporarily disabling flakey test cases (and
   opening tickets to work with domain experts). Please see
   freebsd-testing@ related tickets for more information.

   In addition to that, starting from this quarter, we also work on
   collaboration with external projects to extend their CI to cover
   FreeBSD. See "HostedCI" wiki page for more information.

   Work in progress:
 * Fixing the failing test cases and builds
 * Adding drm ports building test against -CURRENT
 * Adding tests for selected project branches, e.g.: clang800-import
 * Implementing automatic tests on bare metal hardware
 * Planning the embedded testbed
 * Planning running ztest and network stack tests
 __

FreeBSD Core Team

   Contact: FreeB

Re: ifuncs check flawed?

[Ed Maste]

On Tue, 19 Mar 2019 at 16:54, Dan Allen  wrote:
>
> That is why I think the check is flawed!

The check works as intended, as suggested by the non-booting kernel
produced with the checks removed.

To help track this down can you run `make buildenv` and then in the
resulting shell collect the output of `which ld` and `ld --version`?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Nvidia driver cannot compile on FreeBSD 12.0

[Unga via freebsd-stable]

Hi all
I tried to install NVIDIA-FreeBSD-x86_64-418.56 display driver but I get 
following compilation error:
# make install===> src (install)===> src/nvidia (install)cc  -O2 -pipe 
-DNV_VERSION_STRING=\"418.56\" -D__KERNEL__ -DNVRM -Wno-unused-function 
-Wuninitialized -O2 -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -UDEBUG 
-U_DEBUG -DNDEBUG -Werror=undef  -Werror -D_KERNEL -DKLD_MODULE -nostdinc  -I. 
-I../common/inc -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include 
-fno-common  -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer    
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float  
-fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign 
-D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare 
-Wno-error-empty-body -Wno-error-parentheses-equality 
-Wno-error-unused-function -Wno-error-pointer-sign 
-Wno-error-shift-negative-value -Wno-address-of-packed-member  -mno-aes 
-mno-avx  -std=iso9899:1999 -c nvidia_acpi.c -o nvidia_acpi.oIn file included 
from nvidia_acpi.c:12:./os-interface.h:27:10: fatal error: 'stdarg.h' file not 
found#include          ^~1 error generated.

My OS:# uname -aFreeBSD unga 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  
amd64
I used to have a previous version of Nvidia driver running well on FreeBSD 11.2 
on the same machine.
Any idea?
Best regardsUnga
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

devmatch error message

[Brett Glass]

Everyone:

I've been building custom kernels for FreeBSD 12.0, and have noticed
a message on the console, during boot, that I haven't seen from prior
versions. It doesn't affect the operation of the system, but just for
the sake of cleanliness (and to make sure it doesn't cause trouble later)
I'd like to clean it up. The message is

devmatch: can't read linker hints file

Because I'm building a stripped-down kernel without klds or debugging
symbols in it, the kernel build doesn't produce a linker.hints file,
which I assume is what's causing the complaint. Is there a reason why
I should generate such a file? Or, if I don't really need to do so,
is there a way to suppress the message?

--Brett Glass
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: devmatch error message

[Warner Losh]

On Sat, Mar 23, 2019 at 6:27 PM Brett Glass  wrote:

> Everyone:
>
> I've been building custom kernels for FreeBSD 12.0, and have noticed
> a message on the console, during boot, that I haven't seen from prior
> versions. It doesn't affect the operation of the system, but just for
> the sake of cleanliness (and to make sure it doesn't cause trouble later)
> I'd like to clean it up. The message is
>
> devmatch: can't read linker hints file
>
> Because I'm building a stripped-down kernel without klds or debugging
> symbols in it, the kernel build doesn't produce a linker.hints file,
> which I assume is what's causing the complaint. Is there a reason why
> I should generate such a file? Or, if I don't really need to do so,
> is there a way to suppress the message?
>

Disable devmatch. It's useless without klds.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"