Re: igb now em driver in FreeBSD 12.0

2019-01-31 Thread Clayton Milos
I can confirm this. Had to change kernel conf to have em instead of igb and the device is detected as igb. Matthew Macy wrote >They show up as igb. The only POLA violation is that for users of modules >there is now no if_igb.ko so configuring an igb interface doesn't >automatically

Reminder: FCP-101: pending removal of some 10/100 Ethernet drivers

2019-01-31 Thread Brooks Davis
We are currently planning to remove the following less-popular 10/100 Ethernet drivers in the March/April timeframe: ae, bm, cs, de, dme, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe All of these drivers generate warnings in FreeBSD 12 and to the best of my knowledge, none have cleared

Re: Status of libarchive/bsdtar maintainership

2019-01-31 Thread Eugene Grosbein
On 01.02.2019 11:10, Warner Losh wrote: > On Thu, Jan 31, 2019, 8:22 PM Eugene Grosbein wrote: > > Hi! > > I wonder what is status of our contrib/libarchive and bsdtar/bsdcpio etc. > in modern versions of FreeBSD > in a sense of serious bug fixing. Long

Re: Status of libarchive/bsdtar maintainership

2019-01-31 Thread Warner Losh
On Thu, Jan 31, 2019, 8:22 PM Eugene Grosbein Hi! > > I wonder what is status of our contrib/libarchive and bsdtar/bsdcpio etc. > in modern versions of FreeBSD > in a sense of serious bug fixing. Long story short: I faced a bug in the > libarchive bundled with 11.2 > that makes it impossible to

Re: Status of libarchive/bsdtar maintainership

2019-01-31 Thread Kurt Jaeger
Hi! > > Almost 3 months have passed and no response from upstream. > > Should we go ahead and fix it despite of it is part of contrib? > Do you have a fix? Can you put it up for review somewhere? It's in the PR, see https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199000 > We are no where

Status of libarchive/bsdtar maintainership

2019-01-31 Thread Eugene Grosbein
Hi! I wonder what is status of our contrib/libarchive and bsdtar/bsdcpio etc. in modern versions of FreeBSD in a sense of serious bug fixing. Long story short: I faced a bug in the libarchive bundled with 11.2 that makes it impossible to create reliable backups of live file system or its

FreeBSD CI Weekly Report 2019-01-27

2019-01-31 Thread Li-Wen Hsu
(bcc -current and -stable for more audience) FreeBSD CI Weekly Report 2019-01-27 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-01-21 to 2019-01-27. During this period, we have: * 2429 builds (91.2% pass, 7.3%

igb now em driver in FreeBSD 12.0

2019-01-31 Thread Robert Blayzor
Reading the release notes, the igb driver has been merged into the Intel em driver so that should be added to custom kernels. No problem. Question is, when the system reboots, are the NIC devices going to come up with "emX" now or will they remain "igbX" ? Kind of important to know on remote

Re: igb now em driver in FreeBSD 12.0

2019-01-31 Thread Matthew Macy
They show up as igb. The only POLA violation is that for users of modules there is now no if_igb.ko so configuring an igb interface doesn't automatically load the (em) module. On Thu, Jan 31, 2019 at 07:04 Robert Blayzor wrote: > Reading the release notes, the igb driver has been merged into

Re: X11 on Ryzen 2400G?

2019-01-31 Thread Phil Norman
On Wed, 30 Jan 2019 at 22:24, Pete Wright wrote: > > > On 1/30/19 12:10 PM, Phil Norman wrote: > [snip] > >> - after you have configured the amdgpu.ko to load on boot verify it is >> able to load the kernel module and your console display looks good. if >> you have issues loading the kernel