Re: impossible to installkernel without a compiler?

2019-05-22 Thread Warner Losh
Try setting _NO_INCLUDE_COMPILERMK=t in your environment and then doing the make install. Warner On Wed, May 22, 2019 at 2:09 AM Andriy Gapon wrote: > > Trying to update a small system with a kernel built for it on a bigger > machine I > get this: > > sh: cc: not found > make:

Re: FreeBSD Core Team Response to Controversial Social Media Posts

2019-05-19 Thread Warner Losh
On Sun, May 19, 2019 at 11:34 AM Igor Mozolevsky wrote: > On Sun, 19 May 2019 at 17:54, Warner Losh wrote: > > > > On Sun, May 19, 2019, 10:25 AM Graham Perrin wrote: > > > > > I know, it's not appropriate to find fun in a serious discussion, but > > &

Re: FreeBSD Core Team Response to Controversial Social Media Posts

2019-05-19 Thread Warner Losh
On Sun, May 19, 2019, 10:25 AM Graham Perrin wrote: > I know, it's not appropriate to find fun in a serious discussion, but > these six words did make me chuckle: > > > … freedom of expression … End of discussion. > > No offence intended. I was speed-reading (waiting for a browser to > launch)

Re: panic booting with if_tap_load="YES" in loader.conf

2019-05-18 Thread Warner Losh
On Sat, May 18, 2019, 9:48 AM Mark Johnston wrote: > On Sat, May 18, 2019 at 05:45:47PM +0300, Konstantin Belousov wrote: > > On Sat, May 18, 2019 at 05:38:15PM +0300, Konstantin Belousov wrote: > > > On Sat, May 18, 2019 at 10:24:36AM -0400, Mark Johnston wrote: > > > > On Sat, May 18, 2019 at

Re: FCP-101: obsolete driver removal planned for 2019-05-18

2019-05-12 Thread Warner Losh
On Sun, May 12, 2019, 9:28 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > Eugene Grosbein wrote: > > > 11.05.2019 22:59, Julian H. Stacey wrote: > > > > > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > > > >> > > > I've posted a review to remove obsolete 10 and 10/100

Re: FCP-101: obsolete driver removal planned for 2019-05-18

2019-05-12 Thread Warner Losh
On Sun, May 12, 2019, 12:00 PM Eugene Grosbein wrote: > 12.05.2019 8:21, Warner Losh wrote: > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet > drivers > > >> as previous approved in FCP-101. > > >> The following d

Re: FCP-101: obsolete driver removal planned for 2019-05-18

2019-05-11 Thread Warner Losh
On Sat, May 11, 2019, 12:52 PM Eugene Grosbein wrote: > 11.05.2019 21:32, Julian H. Stacey wrote: > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > >> as previous approved in FCP-101. > >> The following drivers are slated for > >> removal from FreeBSD-HEAD (to be

Re: FCP-101: obsolete driver removal planned for 2019-05-18

2019-05-11 Thread Warner Losh
On Sat, May 11, 2019, 12:03 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > > > as previous approved in FCP-101. > > > The following drivers are slated for > > > removal from FreeBSD-HEAD (to be

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-05-06 Thread Warner Losh
On Mon, May 6, 2019 at 1:16 PM Lev Serebryakov wrote: > On 01.05.2019 0:15, Warner Losh wrote: > > > I think all the features are there. You can install loader.efi as you > > used to install boot1.efi and have it work as well or better than > bo

Re: Got the same error from gptzfsboot this morning

2019-05-04 Thread Warner Losh
On Thu, May 2, 2019 at 9:12 AM Thomas Laus wrote: > Toomas: > > My laptop has been booting up flawlessly since I installed the > gptzfsboot file that you sent. It also successfully rebooted from a > cold start this morning but I received the same error message just a few > minutes ago when

Re: New vm-image size is much smaller than previos

2019-05-03 Thread Warner Losh
On Fri, May 3, 2019, 7:42 PM bob prohaska wrote: > On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote: > > -- Start of PGP signed section. > > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote: > > > > > > > > > On May 3, 2019, at 9:57 AM, Alan Somers > wrote: > > > >

Re: Mount Root fails: r347007

2019-05-02 Thread Warner Losh
On Thu, May 2, 2019 at 9:54 AM Larry Rosenman wrote: > On 05/02/2019 9:41 am, Larry Rosenman wrote: > > On 05/02/2019 9:24 am, Warner Losh wrote: > >> On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote: > >> > >>> On 05/02/2019 8:29 am, Warner Losh wrot

Re: Mount Root fails: r347007

2019-05-02 Thread Warner Losh
On Thu, May 2, 2019 at 7:40 AM Larry Rosenman wrote: > On 05/02/2019 8:29 am, Warner Losh wrote: > > On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote: > > > >> Upgraded from r346487 to r347007, and when I reboot, I get a mountroot > >> prompt. If I answer

Re: Mount Root fails: r347007

2019-05-02 Thread Warner Losh
On Wed, May 1, 2019 at 10:04 PM Larry Rosenman wrote: > Upgraded from r346487 to r347007, and when I reboot, I get a mountroot > prompt. If I answer it with the same BootFS I booted from > (zfs:zroot/ROOT/r347007) it continues to boot, and run. > > Dmesg:

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-04-30 Thread Warner Losh
On Mon, Jan 21, 2019 at 6:13 AM Lev Serebryakov wrote: > On 21.01.2019 15:59, Toomas Soome wrote: > > > Is too complicated? Boot1.efi doesn't allow that, but loader.efi > does. > loader.efi lives on ESP partition, do I understand it right? So, it > could not be damaged with "bad"

Re: r346941 boot environment in loader broken?

2019-04-30 Thread Warner Losh
Can you bisect to find the changed that broke it? Warner On Tue, Apr 30, 2019, 6:35 AM Andrey Fesenko wrote: > In loader not work change boot environment, sub menu open, change not > work, simple reset menu. > ___ > freebsd-current@freebsd.org

Re: CFT: FreeBSD Package Base

2019-04-29 Thread Warner Losh
On Mon, Apr 29, 2019 at 7:50 AM Lev Serebryakov wrote: > On 29.04.2019 16:39, k...@ixsystems.com wrote: > > > > > This should be very doable with this package base. We use it for FreeNAS > in a similar manner, where we disable a couple dozen things from base, > resulting in a much more stripped

Re: Question about 'gptzfsboot'

2019-04-28 Thread Warner Losh
On Sun, Apr 28, 2019 at 5:30 PM Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > The messages are similar. The boot process will normally proceed on the > second or third attempt.

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread Warner Losh
On Thu, Feb 28, 2019 at 12:14 PM Ian Lepore wrote: > On Thu, 2019-02-28 at 11:06 -0800, Conrad Meyer wrote: > > On Thu, Feb 28, 2019 at 10:32 AM Steve Kargl > > wrote: > > > This is interesting as well. Does this mean that amd64 is now > > > the only tier 1 platform and all other architectures

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread Warner Losh
On Thu, Feb 28, 2019 at 12:46 PM John Baldwin wrote: > On 2/28/19 11:14 AM, Cy Schubert wrote: > > On February 28, 2019 11:06:46 AM PST, Conrad Meyer > wrote: > >> On Thu, Feb 28, 2019 at 10:32 AM Steve Kargl > >> wrote: > >>> This is interesting as well. Does this mean that amd64 is now >

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-25 Thread Warner Losh
On Sun, Feb 24, 2019 at 10:58 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Sun, Feb 24, 2019 at 10:06:53AM -0700, Warner Losh wrote: > > > > > > > Maybe I missed it, but Steve, did you run the patched in a different way > > tests th

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-24 Thread Warner Losh
On Sun, Feb 24, 2019 at 2:27 AM Tijl Coosemans wrote: > On Sat, 23 Feb 2019 17:28:51 -0800 Steve Kargl > wrote: > > On Sat, Feb 23, 2019 at 12:03:58PM -0700, Warner Losh wrote: > >> On Sat, Feb 23, 2019 at 10:57 AM Steve Kargl > >> wrote: > >>> Sup

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-23 Thread Warner Losh
On Sat, Feb 23, 2019 at 10:57 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > Supposely, the laptop only has 4 GB of memory. Not sure how > it finds memory above 4 GB. > Some older chipsets had a 'hole' in memory that they mapped the PCI bus into and then remapped RAM in that range

Re: What is evdev and autoloading?

2019-02-19 Thread Warner Losh
On Tue, Feb 19, 2019 at 8:17 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > On 19 Feb 2019, at 09.15, Oleksandr Tymoshenko > wrote: > > > > > > Michael Gmelin (gre...@freebsd.org) wrote: > > >> > > >> > > On 18. Feb 2019, at 23:54, Mark Linimon > wrote: > > > >

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:50 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Mon, Feb 18, 2019 at 09:11:14AM -0700, Warner Losh wrote: > > > > You do know these constant complaints about people trying to make things > > better is demoralizing and counter

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:50 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < > > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote: > > > > > > On 2/18/19

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Sun, Feb 17, 2019 at 3:52 PM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > Anyone have insight into what evdev is? There appears to > be no manual page. When I reboot a system with custom > kernel, the system is autoloading evdev.ko, uhid.ko, and > wmt.ko. I do not need nor what

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote: > > > > On 2/18/19 12:06 PM, Stefan Blachmann wrote: > > > > > On 2/18/19, Vladimir Kondratyev wrote: > > > > >> On 2019-02-17

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 8:33 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On 2/18/19 12:06 PM, Stefan Blachmann wrote: > > > On 2/18/19, Vladimir Kondratyev wrote: > > >> On 2019-02-17 21:03, Steve Kargl wrote: > > >>> Anyone have insight into what evdev is? > > >>

Re: problem building dev/e1000

2019-02-16 Thread Warner Losh
On Sat, Feb 16, 2019 at 9:16 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > On Feb 15, 2019, at 11:47, Robert Huff wrote: > > > > > > Lev Serebryakov writes: > > > > > >>> My question would be: why? If some drivers have a new > > >>> dependency on iflib, why isn't

Re: problem building dev/e1000

2019-02-15 Thread Warner Losh
On Fri, Feb 15, 2019 at 12:54 PM Ian Lepore wrote: > On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote: > > On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote: > > > > > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > > > > [...] > &g

Re: problem building dev/e1000

2019-02-15 Thread Warner Losh
On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote: > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > > On Feb 15, 2019, at 10:46, Eric Joyner wrote: > > > > > > ifdi_if.h is a system generated interface file that network drivers > > > that depend on iflib use. It's generated from

Re: kernel build dies with "unknown option"

2019-02-13 Thread Warner Losh
On Wed, Feb 13, 2019, 4:31 PM Robert Huff > On a system running: > > FreeBSD 13.0-CURRENT r343080 16 Jan 2019 amd64 > > I updated the source tree as of midnight US Eastern time, then > ran buildworld. That completed successfully. > Then: > > huff@jerusalem> make

Re: timed restoral until deleter makes a port

2019-01-24 Thread Warner Losh
On Thu, Jan 24, 2019 at 5:03 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Thu, Jan 24, 2019 at 4:13 PM Julian H. Stacey > wrote: > > > > > Current box here is now about 10 seconds ahead, since timed was > deleted, > > > still waiting for the code vandal who removed

Re: timed restoral until deleter makes a port

2019-01-24 Thread Warner Losh
On Thu, Jan 24, 2019 at 4:13 PM Julian H. Stacey wrote: > Current box here is now about 10 seconds ahead, since timed was deleted, > still waiting for the code vandal who removed timed from src/ > without proper discussion in advance, to move timed from src/ to ports/ > > timed absence will bite

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019 at 5:09 PM Warner Losh wrote: > > > On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger >> Hi! >> >> > Well no longer needed as puc0 has found and allocated the >> > device(s) which would of shown up had you done this before >> >

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger Hi! > > > Well no longer needed as puc0 has found and allocated the > > device(s) which would of shown up had you done this before > > you fixed puc0 to find them. > > The problem is that the found 4 uarts are not 8 uarts, and they do not > seem to work

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019, 9:29 AM Lev Serebryakov Hello Rebecca, > > Sunday, January 20, 2019, 7:27:56 AM, you wrote: > > > Ultimately, UEFI doesn't care about disks and partitions: it only really > knows > > about ESPs -- FAT12/16/32 formatted partitions that contain the EFI > directory > >

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 9:32 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes < > > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > > > > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org > > >

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 2:52 AM Kurt Jaeger wrote: > Hi! > > > uart is the new thing. sio info should be ignored. > > > > Chances are good that this device doesn't have the proper entries in the > > puc driver. Do you have any pci devices that show up as unclaimed? > > In a different box, I got

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org > (mailto:l...@freebsd.org)) wrote: > > > > > I have never seen such item in BIOS Setup. I've checked two MoBos now > (one is

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 2:53 PM Kurt Jaeger wrote: > Hi! > > Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388). > After reboot, dmesg shows: > > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0 > > and /dev/ has cuau2* devices. It's unclear, which of the 8

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 2:11 PM Emmanuel Vadot wrote: > On Fri, 18 Jan 2019 22:50:31 +0300 > Lev Serebryakov wrote: > > > On 18.01.2019 22:35, Rodney W. Grimes wrote: > > > > >>> errm.. you press a key and enter device and or loader path. if it is > not working - the code is there to be fixed.

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 11:27 AM Lev Serebryakov wrote: > On 18.01.2019 21:14, Toomas Soome wrote: > > > errm.. you press a key and enter device and or loader path. if it is not > working - the code is there to be fixed. > And loader looks to "bootme" attribute and try to boot from partition >

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 8:55 AM Lev Serebryakov wrote: > On 18.01.2019 17:10, Kyle Evans wrote: > > > There's some UEFI var that's supposed to serve the same kind of > > purpose as /boot.config -- early boot parameters. I think we had > > discussed implementing this at some point, but this

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 8:27 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger > > > > Hi! > > > > > > > With a recent change I made for UEFI, we now install loader.efi onto > the > > > ESP and don???t run boot1. That means that

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger Hi! > > > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don???t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf > > Which change is that ? >

Re: UEFI, loader.efi and /boot.config

2019-01-17 Thread Warner Losh
On Thu, Jan 17, 2019, 7:33 PM Rebecca Cran > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don’t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf. > I was wondering if people will expect

Re: buildworld falure: truncated or malformed archive

2019-01-02 Thread Warner Losh
On Wed, Jan 2, 2019, 1:42 PM John Baldwin On 12/31/18 12:08 PM, Warner Losh wrote: > > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone > > >> Does this mean that it's currently impossible to build a world with > >> debug symbols? > >> > > > > Yes. Cla

Re: buildworld falure: truncated or malformed archive

2018-12-31 Thread Warner Losh
On Mon, Dec 31, 2018, 1:36 PM Ryan Stone Does this mean that it's currently impossible to build a world with > debug symbols? > Yes. Clang is simply too big until 64 bit offset support goes in. Warner > ___ freebsd-current@freebsd.org mailing list

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-28 Thread Warner Losh
On Fri, Dec 28, 2018, 5:45 AM O. Hartmann On Thu, 27 Dec 2018 08:38:20 -0700 > Warner Losh wrote: > > > On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Thu, 27

Re: buildworld falure: truncated or malformed archive

2018-12-27 Thread Warner Losh
On Thu, Dec 27, 2018, 5:29 PM Ed Maste On Thu, 27 Dec 2018 at 14:35, Ryan Stone wrote: > > > > I seem to recall something about libarchive or ar having a bug > > creating archives > 4GB, > > Indeed, FreeBSD's bespoke ar does not support the /SYM64/ format > needed for offsets >4GB. imp@ also ran

Re: buildworld falure: truncated or malformed archive

2018-12-27 Thread Warner Losh
On Thu, Dec 27, 2018, 2:36 PM Ryan Stone I'm trying to update an old (~May 2018) -head system to the latest, > but I'm getting a persistent error during buildworld: > > ld: error: /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a: > could not get the member for symbol > >

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-27 Thread Warner Losh
On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 27 Dec 2018 13:29:44 +0100 "Hartmann, O." schrieb: > Updated Fujitsu Celsius M740 to its lates UEFI firmware today. > After this update, the box won't boot FreeBSD 12-STABLE anymore! With >

Re: ctm(1) deprecation in the FreeBSD base system?

2018-12-23 Thread Warner Losh
On Sun, Dec 23, 2018 at 12:27 AM Stefan Esser wrote: > Am 23.12.18 um 02:39 schrieb Montgomery-Smith, Stephen: > > On 12/21/18 10:03 PM, Julian H. Stacey wrote: > >>> The port Makefile that I have prepared is attached below for reference. > >>> Regards, STefan > >> > >> Thanks Stefan, > >> I

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Warner Losh
On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov Mark Peek wrote: > > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wrote: > > > >> > >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > >>> > >>> Mark Peek wrote: > Thanks for the cc:. I forwarded the original report on to an internal >

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-21 Thread Warner Losh
I've been hit by this as well. At least two others on IRC have had the same issue. Warner On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > > > Hi, > > > > There's apparently a bug in VMware Workstation NAT implementation, made > >

Re: The future of ZFS in FreeBSD

2018-12-20 Thread Warner Losh
On Thu, Dec 20, 2018 at 1:49 PM Allan Jude wrote: > I am to give a big thanks to Matt Ahrens for organizing the monthly > OpenZFS Leadership meeting, and the OpenZFS developer summit, and to > Brian Behlendorf for being so helpful, and willing to work to make > OpenZFS better for everyone. >

Re: The future of ZFS in FreeBSD

2018-12-20 Thread Warner Losh
Matt, This is a fairly comprehensive plan. Kudos for putting it together. The big question here is do you have a complete list of FreeBSD-specific changes that will be lost in the cut-over? We've heard about TRIM support and maybe NFSv4, but are there others that can be identified? Once you

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 11:14 AM Yuri Pankov wrote: > Warner Losh wrote: > > On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: > > > >> Yuri Pankov wrote: > >>> Warner Losh wrote: > >>>> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: >

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: > Yuri Pankov wrote: > > Warner Losh wrote: > >> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: > >> > >>> > >>> On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin > >>> wro

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: > > On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin > wrote: > >> On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrote: >> > Hi, >> > >> > Building disc1.iso using `make release` and having

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin wrote: > On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrote: > > Hi, > > > > Building disc1.iso using `make release` and having WITH_CTF set in > > src.conf leads to "File too big" displayed when booting the image. > > > > Would it make

Re: SCSI and dmesg

2018-11-29 Thread Warner Losh
On Thu, Nov 29, 2018 at 8:09 AM Alan Somers wrote: > On Mon, Nov 26, 2018 at 3:57 PM Warner Losh wrote: > >> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev >> wrote: >> >> > Somebody needs to make collection/submission automatic and make a port >> out

Re: SCSI and dmesg

2018-11-26 Thread Warner Losh
only when there's a material change... And I'd rather we get more nuanced data than dmesg can provide if we were to do the data collection. The admonition to submit to this site was one of expedience... Warner > -Max > > On Mon, Nov 26, 2018 at 2:08 PM Yuri Pankov wrote: > > > Yuri P

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-22 Thread Warner Losh
On Wed, Nov 21, 2018, 11:43 PM Dan Partelly wireless lagg initialization is broken in this scenario, all-right. The > init/rc system as it is now can’t cope easily with a modern asynchronous > initialization sequence. Sure you could probably find an order which works, > only to find yourself in

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-19 Thread Warner Losh
On Mon, Nov 19, 2018 at 7:48 PM Dan Partelly wrote: > Hello, > > Today I tried a simple wireless failover on a machine running free-bsd. > After reboot the system cannot complete the initialization sequence OK with > devmatcher. > The devd/devmatch(8) combo correctly identified the wireless

Re: UEFI GOP: screen goes blank during boot after loader is finished

2018-11-15 Thread Warner Losh
On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran wrote: > On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: > > > What is the ConOut evifar look like? We set serial when the UEFI env says > > to do so. > > Booting with: > > sudo bhyve -A -P -c 2 -H -m 4G

Re: UEFI GOP: screen goes blank during boot after loader is finished

2018-11-14 Thread Warner Losh
On Wed, Nov 14, 2018 at 4:00 PM Kyle Evans wrote: > On Wed, Nov 14, 2018 at 4:55 PM Subbsd wrote: > > > > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans wrote: > > > > > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans wrote: > > > > > > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd wrote: > > > > > >

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Warner Losh
On Tue, Nov 13, 2018 at 3:52 PM Conrad Meyer wrote: > Geom devices have the DIOCGDELETE ioctl, which translates into > BIO_DELETE (which is TRIM, as I understand it). > Correct. TRIM is both the catch-all term people use, as well as the name of a specific DSM (data set management) command in

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Warner Losh
On Tue, Nov 13, 2018 at 3:10 PM Alan Somers wrote: > Hole-punching has been discussed on these lists before[1]. It basically > means to turn a dense file into a sparse file by deallocating storage for > some of the blocks in the middle. There's no standard API for it. Linux > uses

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
On Mon, Nov 5, 2018 at 10:23 AM Robert Huff wrote: > > Warner Losh writes: > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > >

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
On Sun, Nov 4, 2018 at 10:52 PM Kevin Oberman wrote: > On Sun, Nov 4, 2018 at 12:15 PM Niclas Zeising > wrote: > > > On 11/4/18 8:29 PM, Robert Huff wrote: > > > > > > I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300 > > > gpu) which will be updated from 11. to 12.0 once

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 4:10 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > > > I think that's a really really bad idea. We should *NEVER* create them by > > default. We are only sliding by on the coat-tails of compatibility by > using &

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:27 PM Allan Jude wrote: > On 2018-11-04 16:20, Rebecca Cran wrote: > > I'm currently working on creating and updating the ESP (EFI System > Partition) > > for UEFI booting during installation and installworld. > > > > During installation, with my changes it gets mounted

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:43 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > > > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi > is > > hard one of course. But then again, it is problem only when we can not > > setup EFI

Re: armv7 BETA3 panics when usb-disk inserted

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 12:55 AM Poul-Henning Kamp wrote: > With the 12.0-BETA3 BEAGLEBONE image, I very often see this panic > when I plug a USB attached SSD disk in. > ... >umass0 on uhub0 > umass0: > on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x8100 >

Re: UEFI boot hangs after loader

2018-10-28 Thread Warner Losh
On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > Jung-uk Kim wrote: > > On 18. 10. 24., Warner Losh wrote: > >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> > >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >>> 00

Re: UEFI boot hangs after loader

2018-10-26 Thread Warner Losh
I've recreated something like this in efivar as well... I need to study the code for how to improve it to have sanity limits... I hope to have a patch soon... Thanks for this data point. I think I'm on the right track. Warner On Fri, Oct 26, 2018 at 3:47 PM Harry Newton wrote: > So patching

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:46 AM Warner Losh wrote: > > > On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran > wrote: > >> On 10/25/18 10:20 AM, Rebecca Cran wrote: >> >> > >> > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 >> >

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran wrote: > On 10/25/18 10:20 AM, Rebecca Cran wrote: > > > > > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 > > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 > > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 >

Re: pkg problem on FreeBSD 13.0-CURRENT

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:17 AM Kurt Jaeger wrote: > Hi! > > > On 10/25/18 5:19 PM, Sean Bruno wrote: > > > pkg-static install -f pkg > > > > It works better now, but there are some complaints. > > If it's only the certificate issue, try this: > > cd /usr/local/etc > cp pkg.conf.sample pkg.conf

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:16 AM Rebecca Cran wrote: > On 10/25/18 10:00 AM, Warner Losh wrote: > > > > > I suspect you can just lose those hints in the hints file and be fine. > The > > uart should attach via acpi. The keyboard won't, however, since it isn't > &

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 9:35 AM Rebecca Cran wrote: > On 10/25/18 5:02 AM, Rodney W. Grimes wrote: > > > Can you please reply with the specific device. > > If you have seen one it may be an issue to removing it, > > especially if this is on a "new AMD" system. > > > This is a new Ryzen system.

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen wrote: > On 10/25/18 6:57 AM, Rodney W. Grimes wrote: > >>> I noticed a warning on a new AMD system running 12-BETA1: > >>> > >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > >> Can you please reply with the specific device. > >>

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 11:47 AM Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > > > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
00 30 00 31 00 2e 00 30 00 30 00 00 00 > 00e0: 7f ff 04 00 00 00 42 4f > gryphon# > Perfect. I'll decode this and see if I can figure out where we're going AFU. Warner > On 24 October 2018 at 15:09, Warner Losh wrote: > >> >> >> On Wed, Oct 24, 2018 at 7:05 A

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 9:36 AM Toomas Soome wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS > >

Re: build is broken

2018-10-23 Thread Warner Losh
Konstantin fixed it a few minutes ago. Warner On Tue, Oct 23, 2018, 6:09 PM Martin Wilke wrote: > as of rev: 339671 > > build fails > > https://dpaste.de/NCeV/raw > > - Miwi > -- > +-oOO--(_)--OOo-+ > With best Regards, > Martin Wilke

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 2:13 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > A cost(=time)/benefit look on moving ctm from src/ to ports/ : > > - No tangible architecture benefit (its not like purging an old driver > > to makes kernel support simpler, or avoiding clashing

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018, 12:18 PM Stefan Esser wrote: > Am 23.10.18 um 19:06 schrieb Warner Losh: > > > > > > On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser > <mailto:s...@freebsd.org>> wrote: > > > > Am 23.10.18 um 17:27 schrieb Montgomery-Smith,

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser wrote: > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > I have no problem turning ctm into a port. But I would appreciate > > advice on whether there is a standard or easy process for converting > > software from the FreeBSD base to a

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > >

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-22 Thread Warner Losh
On Mon, Oct 22, 2018 at 2:40 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > In message <201810221957.w9mjvdxx012...@pdx.rh.cn85.dnsmgr.net>, > "Rodney W. Gri > > mes" writes: > > > > >I do not know that other than I do know that I have seen > > >one data point

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-22 Thread Warner Losh
On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote: > On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > > > On 22 Oct 2018, at 13:58, Mark Millard wrote: > >> > >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: > >>> > >>>> On 22 Oct

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < > freebsd-sta...@freebsd.org> wrote: > >> [I built based on WITHOUT_ZFS= for other reasons. But, >> after installing the build, H

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < freebsd-sta...@freebsd.org> wrote: > [I built based on WITHOUT_ZFS= for other reasons. But, > after installing the build, Hyper-V based boots are > working.] > > On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > > > On

Re: DRM: radeonkms … can not be unloaded (kernel panic)) …

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018, 2:29 AM Kevin Oberman wrote: > On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky > wrote: > > > On 10/20/18 3:10 AM, Graham Perrin wrote: > > > On 20/10/2018 00:01, Graham Perrin wrote: > > > > > >> kldunload radeonkms > > >> > > >> – results in a kernel panic. > > > > >

Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ -r336532 broke it ]

2018-10-21 Thread Warner Losh
On Sat, Oct 20, 2018 at 11:04 PM Mark Millard wrote: > [I found what change lead to the 1950X boot crashing > with BTX halted.] > > On 2018-Oct-20, at 12:44 PM, Mark Millard wrote: > > > [Adding some vintage information for a loader > > that allowed a native boot.] > > > > On 2018-Oct-20, at

  1   2   3   4   5   6   7   8   9   10   >