Re: When will the FreeBSD (u)EFI work?

> On 3/29/20 6:11 AM, Tomoaki AOKI wrote: > > > > > 3. based solution looks good to me. > > > > IMHO, assuming /efi/bootx[64|32].efi is boot1.efi or loader.efi > > or EFI environment pointing to either one is properly used, > > > That's another thing: we should be installing loader.efi as >

Re: OpenZFS: sysctl: unknown oid 'vfs.zfs.arc_max'

> This occurs when I enable OpenZFS: > > OpenZFS: sysctl: unknown oid 'vfs.zfs.arc_max' > > Is it to be deprecated? Or is it not yet a feature of OpenZFS for FreeBSD? > > From : > > grahamperrin@momh167-gjp4-8570p:~ % sysctl vfs.zfs.arc_max > sysctl: unknown oid

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

> In message <202001261745.00qhjkuw044...@gndrsh.dnsmgr.net>, "Rodney W. > Grimes" > writes: > > > In message <20200125233116.ga49...@troutmask.apl.washington.edu>, Steve > > > Kargl w > > > rites: > > > > On Sat, Jan 25, 2020

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

> In message <20200125233116.ga49...@troutmask.apl.washington.edu>, Steve > Kargl w > rites: > > On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote: > > > On January 25, 2020 1:52:03 PM PST, Steve Kargl > > > > on.edu> wrote: > > > >On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

> Yasuhiro KIMURA yasu at utahime.org wrote on > Sat Jan 25 14:45:13 UTC 2020 : > > > I use VirtualBox to run 13-CURRENT. Host is 64bit Windows 10 1909 and > > spec of VM is as following. > > > > * 4 CPU > > * 8GB memory > > * 100GB disk > > - 92GB ZFS pool (zroot) > > - 8GB swap > > > >

Re: OpenSSL breaks factor(6)

> On Sat, Dec 28, 2019 at 10:46:52PM -0500, Garance A Drosehn wrote: > > On 27 Dec 2019, at 17:42, Steve Kargl wrote: > > > > > > This patch now includes a fix for hexadecimal conversion. It > > > simple scans the string for a hex digit in [a,...,f] and assumes > > > that a hexadecimal string has

Re: OpenSSL breaks factor(6)

> On Fri, Dec 27, 2019 at 07:00:04PM -0800, Rodney W. Grimes wrote: > > > On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > > > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > > > > The use of OpenSSL in factor(6) breaks

Re: OpenSSL breaks factor(6)

> On Fri, Dec 27, 2019 at 02:42:12PM -0800, Steve Kargl wrote: > > On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > > > The use of OpenSSL in factor(6) breaks factor(6) with respect to > > > > its documentation. > >

Re: OpenSSL breaks factor(6)

> On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > > The use of OpenSSL in factor(6) breaks factor(6) with respect to > > > its documentation. > > > > > > % man factor > > > ... > > > Numbers may be preceded by a

Re: Best way to print something from the kernel at 1s intervals?

> > I?ve been looking into the ?kernel looks to be hung at reboot? problem at > > bit. Adding a lot of printf() calls to the relevant parts it looks like it > > actually isn?t hung but busy unmounting filesystems (which we have > > thousands of), flushing disk caches, calling registered

Re: Best way to print something from the kernel at 1s intervals?

> I?ve been looking into the ?kernel looks to be hung at reboot? problem at > bit. Adding a lot of printf() calls to the relevant parts it looks like it > actually isn?t hung but busy unmounting filesystems (which we have thousands > of), flushing disk caches, calling registered callbacks and

Re: ntpd segfaults on start

> On Mon, 2019-09-09 at 09:30 -0700, Rodney W. Grimes wrote: > > > On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote: > > > > In message <20190907161749.gj2...@kib.kiev.ua>, Konstantin > > > > Belousov writes: > > > > > On

Re: ntpd segfaults on start

> On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote: > > In message <20190907161749.gj2...@kib.kiev.ua>, Konstantin Belousov writes: > > > On Sat, Sep 07, 2019 at 08:45:21AM -0700, Cy Schubert wrote: > > > > I've been able to set the memlock rlimit as low as 20 MB. The issue is > > > > letting

Re: HEADSUP: drm-current-kmod now installs sources

> On Fri, 16 Aug 2019 15:40:24 -0700 > Cy Schubert wrote: > > > On August 16, 2019 2:51:22 PM PDT, "Rodney W. Grimes" > > wrote: > > >> On 8/14/19 3:40 PM, Daniel Eischen wrote: > > >> > I've lost the original thread, but would the sou

Re: HEADSUP: drm-current-kmod now installs sources

> On 8/14/19 3:40 PM, Daniel Eischen wrote: > > I've lost the original thread, but would the sources in > > /usr/local/sys/modules get built regardless of what MAKEOBJDIRPREFIX is? > > And, now that sources may be installed by a port, what is the method for > > _just_ updating the sources?

Re: Stop installing /usr/bin/clang

> On Fri, Aug 16, 2019 at 09:47:41AM +0100, David Chisnall wrote: > > On 15/08/2019 17:48, Konstantin Belousov wrote: > > > Please look at https://reviews.freebsd.org/D21060 > > > I propose to stop installing /usr/bin/clang, clang++, clang-cpp. > > > > > > It probably does not matter when all

Re: Stop installing /usr/bin/clang

> On Fri, Aug 16, 2019 at 08:57:13AM +0300, nonamel...@ukr.net wrote: > > I see the same thing with base?/usr/bin/ld and?/usr/local/bin/ld from > > binutils. > Yes but a direct ld use is very rare. When it is needed, usually the > level of hackery applied is already high enough for the user to

Re: rc script: manual stop vs system shutdown

> On Aug 1, 2019, at 08:53, Rodney W. Grimes > wrote: > > >> > >> Is it possible in an rc script to distinguish between a manual stop > >> (e.g., service foo stop) and a stop during a system shutdown (via > >> rc.shutdown) ? > >> Are

Re: rc script: manual stop vs system shutdown

> > Is it possible in an rc script to distinguish between a manual stop > (e.g., service foo stop) and a stop during a system shutdown (via > rc.shutdown) ? > Are there any marker variables for that? > Or something in the global system state? Not that I can think of, but I like this idea, I am

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

> The .iso files are for a dvd install. If you want to use a usb, download > the .img files. > > FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img > The

Re: Checking out the CSRG repository?

> On 19-06-20 05 h 59, Warner Losh wrote: > > On Wed, Jun 19, 2019 at 7:55 PM Alan Somers wrote: > > > >> On Wed, Jun 19, 2019 at 8:41 PM Warner Losh wrote: > >>> > >>> > >>> > >>> On Wed, Jun 19, 2019, 7:09 PM Alan Somers wrote: > > On Wed, Jun 19, 2019 at 5:38 PM Warner Losh

Re: Checking out the CSRG repository?

> > From: Alan Somers > > Date: Wed, 19 Jun 2019 14:12:21 -0600 > > Subject: Checking out the CSRG repository? > > To: FreeBSD CURRENT > > > > Does anybody know how to check out a local copy of the CSRG > > repository? I can view it with ViewVC, but I would really like local > > access. It

Re: error: yacc.h: No such file or directory

> In message > , Ian Le > pore writes: > > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote: > > > > On Jun 18, 2019, at 06:59, Enji Cooper > > > > wrote: > > > > > > > > > > > > > On Jun 18, 2019, at 06:53, Ian Lepore wrote: > > > > > > > > ... > > > > > > > > > Last Saturday, Bryan

Re: pkg: Cannot open /dev/null:No such file or directory

> On 04/06/2019 06:32, O. Hartmann wrote: > > As far as I know,, the package installation is performed via "chroot'ed" > > environment and somehow /dev/null is out of a sudden not accessible anymore > > while pkg tries to delegate some output to /dev/null. > > Assuming you're chroot'd to /chroot,

Re: UEFI boot broken in 13?

> Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick boots fine with in UEFI mode. Does it actually boot via a

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

> rai...@ultra-secure.de wrote: > > > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > > department who is technically responsible for the service gets around > > redoing that service. > > >From my understanding from reading the bug (though it's not entirely clear > in this

Re: FreeBSD and Coreboot

> On 5/28/19 12:46 AM, Warner Losh wrote: > > > > > > On Mon, May 27, 2019, 10:44 PM Nathan Whitehorn > > wrote: > > > > > > > > On 2019-05-27 19:14, Warner Losh wrote: > > > On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn > >

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

> 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 Ethernet drivers > > as previous approved in FCP-101. > > The following drivers are slated

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

> 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 drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> ae, bm,

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

> > 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 FreeBSD-13): > > > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > OMG ! ed !

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

> On Fri, May 03, 2019 at 07:39:00PM -0700, Rodney W. Grimes wrote: > > > 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

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

> 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: > > > > > >

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

-- 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: > > > > > > See r346959. Before first boot, you should expand the image up to > > > whatever size you want. growfs(8) will automatically

Re: Rotating (efi) framebuffer

> Hi > > I have a Lenovo Ideapad where the screen is rotated 90 degrees and I > can't rotate it to landscape mode until I'm in X. How many of you are in > the same situation and would like a fix? Seeing how development is going > with small (tiny) computers it will probably be more and more

Re: CFT: FreeBSD Package Base

> On Mon, Apr 29, 2019 at 10:09 AM Rodney W. Grimes < > freebsd-...@gndrsh.dnsmgr.net> wrote: > > > > > > > Correct, this is ZFS only. And it's something we're using specific to > > FreeNAS / TrueOS, which is why I didn't originally mention it as ap

Re: CFT: FreeBSD Package Base

> > Correct, this is ZFS only. And it's something we're using specific to FreeNAS > / TrueOS, which is why I didn't originally mention it as apart of our CFT. Then please it is "CFT: FreeNAS/TrueOS pkg base, ZFS only", calling this FreeBSD pkg base when it is not was wrong, and miss leading.

Re: SVN r346700 breaks build

> On Thu, Apr 25, 2019 at 3:33 PM Michael Butler > wrote: > > > > Seems that the lib32 piece (on amd64) is now broken; as follows: > > > > *sigh* > > Strike two of three for me today, it seems. Should be fixed in > r346705... sorry about that, thanks for the report! Perfection: A finely

Re: r346025: ZFS filesystems do not mount anymore

> In message <19ca3a5d-4e41-4f17-a788-b9545f104...@gmail.com>, "Enji > Cooper (yane > urabeya)" writes: > > > > > On Apr 9, 2019, at 21:51, Enji Cooper wrote: > > > > ??? > > > > > CCing crees@, the author of r346017, for context. I will file a PR soon > > > if > > one hasn???t already been

Re: lsof hangs with latest 13.0-CURRENT snapshot

> On Tue, 2019-04-09 at 12:20 -0700, Rodney W. Grimes wrote: > > > After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > > > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from > > > packages) > > > hangs. > > > > &

Re: lsof hangs with latest 13.0-CURRENT snapshot

> After upgrading from FreeBSD-13.0-CURRENT-amd64-20190328-r345620 to > FreeBSD-13.0-CURRENT-amd64-20190404-r345863, lsof (4.92 from packages) > hangs. > > This is true for bare metal installs and virtual machine installs. > > How to recreate: > > Install

Re: ZFS no longer mounted in alphanumerical order

> On 12/03/2019 11:37, Trond Endrest?l wrote: > > # Parallel mounting of ZFS filesystems leaves a chaotic listing of > > # mounted filesystems when viewed by df(1). > > df reports filesystems in the order they were mounted. > If you unmount and remount a filesystem or mount a new filesystem, you

Re: ZFS no longer mounted in alphanumerical order

> On 12/03/2019 02:12, Rodney W. Grimes wrote: > >> On 11/03/2019 23:03, Freddie Cash wrote: > >>> Wouldn't it make more sense to teach df, du, "zfs list", and other things > >>> that list the mounted filesystems to use sorted output? > >>

Re: ZFS no longer mounted in alphanumerical order

> On 11/03/2019 23:03, Freddie Cash wrote: > > Wouldn't it make more sense to teach df, du, "zfs list", and other things > > that list the mounted filesystems to use sorted output? > > | sort [desired options] Except that df and zfs list have a header that you have to deal with, which is not so

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

> 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

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

> 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 > >>> the only tier 1 platform and all other architectures

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

> On 2/28/19 10:32 AM, Steve Kargl wrote: ( ... trimmed ... ) > > The BIOS does have a enable/disable button for virtualization. > > During the great drm-legacy-kmod event of the last month, enabling > > virtualization locks up a i386 FreeBSD kernel very quickly. > > Perhaps, virtualization works

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

> 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

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

> On Sat, Feb 23, 2019 at 11:19:31AM +0200, Konstantin Belousov wrote: > > On Fri, Feb 22, 2019 at 07:26:44PM -0800, Steve Kargl wrote: > > > On Thu, Feb 21, 2019 at 10:04:10PM -0800, Steve Kargl wrote: > > > > On Thu, Feb 21, 2019 at 07:39:25PM -0800, Steve Kargl wrote: > > > > > r343567 merges

Re: What is evdev and autoloading?

> > 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: > >>>> > >>>> On Mon, Feb 18, 2019 at

Re: What is evdev and autoloading?

> 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: > > &

Re: What is evdev and autoloading?

> 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 21:03, Steve Kargl wrote: > > > >>> Anyone have

Re: What is evdev and autoloading?

> 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? > >> evdev.ko is a small in-kernel library that makes all your input events > >> like keyboard presses

Re: What is evdev and autoloading?

> On Sun, Feb 17, 2019 at 03:04:41PM -0800, Mark Millard wrote: > > > > > > On 2019-Feb-17, at 10:03, Steve Kargl > > 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

Re: problem building dev/e1000

> > > 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 that expressed in sys/conf/files > >>> and handled automatically? As expressed elsewhere that gets a bit

Re: what do jails map 127.0.0.1 to?

[ Charset windows-1252 unsupported, converting... ] > Bjoern A. Zeeb wrote: > [good stuff snipped] > >Yes, could do easily but wouldn?t work for my above case, would it? I > >can help you with the code for v4 and jails if you help me with the code > >for IPv6? > Well, not quite what you

Re: drm2 removed?

> On Mon, Feb 11, 2019 at 04:33:24PM +, Johannes Lundberg wrote: > > > > On 2/11/19 4:23 PM, Niclas Zeising wrote: > > > On 2/11/19 5:20 PM, Steve Kargl wrote: > > >> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > > >>> Anyone have any idea which recent change broke the > >

Re: "Oddness" in head since around r343678 or so

> I run and track stable/11, stable/12, and head (from separate slices -- > no VMs involved) on my laptop; among other things, this permits some > degree of comparison among them. > > The laptop is configured to run xdm; while running stable/11 or > stable/12, there's a period of about 5 seconds

Re: timed restoral until deleter makes a port

> 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

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

> 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 (tested using kermit), either 8-( But

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

> Hi! > > > > It only detects four (or six?) serials... > > Are perhaps 2 of them being consumed by sio? > > See my other post, the system found 13 uarts 8-} > > > > So I think I found a 'somehow' working setup and have to add stuff to > > > sys/dev/puc/pucdata.c to match it. Thanks for the

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

> 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 this: > > none1@pci0:7:4:0: class=0x070002

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

> Hi! > > > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0 > > Ah, that is a false lead. > > I compared it to a second, similar hardware and there I found the same uart2, > even if no card was installed 8-( > > So it seems the card is not detected at all 8-( Need to find out

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

> 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

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

> 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: > > > > > > >

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

> > 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 > > Supermicro X9something and other is brand-new Goldmont-based Chinese MiniPC > > like Intel

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

> > On 18 Jan 2019, at 21:33, Rodney W. Grimes > > wrote: > > > >> > >> > >>> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote: > >>> > >>> On 18.01.2019 20:13, Warner Losh wrote: > >>> > >>

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

> 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 > which has one, even if it is loaded from other

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

> > > > On 18 Jan 2019, at 19:57, Lev Serebryakov wrote: > > > > On 18.01.2019 20:13, Warner Losh wrote: > > > >>> Also, there are same problems with GPT/BIOS setup (which uses GPT but > >>> legacy boot) :-( > >>> > >> > >> What same problems? I don't think we've touched how gptboot has

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

> 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

Re: openssl 1.1.1 utils mkerr.pl

> Hi! > > > Did you try to use the openssl port? > > cd security/openssl111 > $ grep mkerr pkg-plist > $ cd secuirty/openssl111 make extract find work | grep mkerr > does not have it, either. > -- Rod Grimes rgri...@freebsd.org

Re: building release images broken?

> On 11/17/18 5:35 PM, Michael Butler wrote: > > Any clues as to what's broken here? I'm trying to build a CD and/or DVD > > image. > > > > My tree is at SVN r340525. > > > > -- > Kernel build for GENERIC completed on Sat Nov 17

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

> On Wed, Nov 14, 2018 at 3:49 PM Kyle Evans wrote: > > > Good, good, so the loader <-> kernel transition would appear to be > > intact and information appears good at first blush. If you don't have > > time to dig into this, I'll try poking at it this weekend, but it > > looks to be either

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

> On Tue, Nov 13, 2018 at 5:15 PM Subbsd wrote: > > > > Hi, > > > > > > > > On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes > > wrote: > > > > > > Uh oh, ok, thats not what I was thinking of then. I do not have any >

Re: 12.0-beta3 base.txz missing complete dir tree

[ Charset UTF-8 unsupported, converting... ] > > > On 11/8/18 12:25 PM, Ernie Luzar wrote: > > ftp.freebsd.org/pub/FreeBSD/releases/amd/amd/12.0-BETA3/base.txz > > > > /usr/local empty > > /var/log? empty > > > > This is really making testing imposable! > > shouldn't both of those directories

Re: 12.0-BETA1 vnet with pf firewall

> On 30 Oct 2018, at 14:14, Rodney W. Grimes wrote: > > >> On 30 Oct 2018, at 14:29, Bjoern A. Zeeb wrote: > >>> On 30 Oct 2018, at 12:23, Kristof Provost wrote: > >>>> I?m not too familiar with this part of the vnet code, but it looks > >

Re: 12.0-BETA1 vnet with pf firewall

> On 30 Oct 2018, at 14:29, Bjoern A. Zeeb wrote: > > On 30 Oct 2018, at 12:23, Kristof Provost wrote: > >> I?m not too familiar with this part of the vnet code, but it looks > >> to me like we?ve got more per-vnet variables that was originally > >> anticipated, so we may need to just increase

Re: 12.0-BETA1 vnet with pf firewall

> Bjoern A. Zeeb wrote: > > On 28 Oct 2018, at 15:31, Ernie Luzar wrote: > > > >> Tested with host running ipfilter and vnet running pf. Tried loading > >> pf from host console or from vnet console using kldload pf.ko command > >> and get this error message; > >> > >> linker_load_file:

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

> 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 remove

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

> > 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. > If you have seen one it may be an issue to removing it, > especially if this is on a "new AMD" system.

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

> 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. If you have seen one it may be an issue to removing it, especially if this is on a "new AMD" system. > > It looks

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

> 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 libs etc) > - FreeBSD would shrink 0.028 % of the size of src/ > cd

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

> 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 port. If not, I can muddle my way > > through it. But

Re: careless commits disrupt

> Am 22.10.18 um 23:09 schrieb Julian H. Stacey: > > Hi, Reference: > >> From: Stefan Esser > >> Date: Fri, 12 Oct 2018 11:44:59 +0200 > > > > Stefan Esser wrote: > >> I might have mentioned, that I always preserve old shared libraries in > >> /usr/lib/compat before

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

> "Rodney W. Grimes" wrote: > > > The ctm(1) client remains in the FreeBSD base system, although > > > FreeBSD-hosted ctm infrastructure was shut down some time ago. I > > > suspect it is time to remove it from the base system (perhaps making a > > &g

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

> > In message > > , Warner Losh writes: > > >> > I think Julian Stacy is still running CTM generation ? > >> > >> Ah, yes, that brought back enough brain cells, > >> confirmed that is who I saw with ctm usage. > > > >Do we need it in base? Or can we make it a port? > > Absolutely

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

> > 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 in the last 14 days of a user who was infact > >using ctm though I can not associate a username/email

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

> The ctm(1) client remains in the FreeBSD base system, although > FreeBSD-hosted ctm infrastructure was shut down some time ago. I > suspect it is time to remove it from the base system (perhaps making a > port). > > How much use does ctm have these days? I do not know that other than I do know

Re: A new stable/12 poudriere jail is inferior to its stable/12 host

-- Start of PGP signed section. > On Sun, Oct 21, 2018 at 02:14:16PM +0100, Graham Perrin wrote: > > On 21/10/2018 13:31, David Wolfskill wrote: > > > On Sun, Oct 21, 2018 at 09:41:46AM +0100, Graham Perrin wrote: > > >> With the host already at r339438, > > >> creation of a jail (method: svn

Re: Not sure if this is an important bug...

> I tried running 12.0-BETA8 under bhyve on a Phenom-II+11.2 box and > it explodes because of an unemulated instruction: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232081 > > I have no idea what importance this has in relation to releasing 12.0 Can you try an earlier alpha for

Re: Not sure if this is an important bug...

> On Mon, Oct 08, 2018 at 07:12:59PM +, Poul-Henning Kamp wrote: > > I tried running 12.0-BETA8 under bhyve on a Phenom-II+11.2 box and > > it explodes because of an unemulated instruction: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232081 > > > > I have no idea what

Re: Sound issues with Dell Latitude 7490 (kabylake)

> On 10/2/18 6:27 PM, Rodney W. Grimes wrote: > >> On 10/1/18 6:43 PM, Rodney W. Grimes wrote: > >>>> Hi > >>>> > >>>> While sound work out of the box (with headphone switching) on the 1-2 > >>>> year > >>>>

Re: Sound issues with Dell Latitude 7490 (kabylake)

> On 10/1/18 6:43 PM, Rodney W. Grimes wrote: > >> Hi > >> > >> While sound work out of the box (with headphone switching) on the 1-2 year > >> older Latitude 7270, it does not on my new machine. > >> > >> The internal speaker works fine.

Re: Sound issues with Dell Latitude 7490 (kabylake)

> Hi > > While sound work out of the box (with headphone switching) on the 1-2 year > older Latitude 7270, it does not on my new machine. > > The internal speaker works fine. If I plug in external speakers in the > headphone jack, sound still goes to the internal speaker while a very load > buzz

Re: devmatch sideeffec: No sound

> HW: Thinkpad T480 with T3 Dock. > > SW: -current, r338952 > > With devmatch enabled in /etc/rc.conf (the default0, snd_uaudio > gets loaded automatically and finds the audio stuff in the dock, > which is connected to a screen output(s) I do not use. > > Firefox ends up with /dev/dsp2.0 which

Re: LLVM breaks buildworld

> > On Thu, Sep 27, 2018 at 12:39:07PM -0700, Steve Kargl wrote: > > > On Thu, Sep 27, 2018 at 12:34:39PM -0700, Steve Kargl wrote: > > > > cd /usr/obj > > > > rm -f usr > > > > cd /usr/src > > > > svn update > > > > make buildworld > > > > (wait a long time) > > > > > > > > ===>

Re: LLVM breaks buildworld

> On Thu, Sep 27, 2018 at 12:39:07PM -0700, Steve Kargl wrote: > > On Thu, Sep 27, 2018 at 12:34:39PM -0700, Steve Kargl wrote: > > > cd /usr/obj > > > rm -f usr > > > cd /usr/src > > > svn update > > > make buildworld > > > (wait a long time) > > > > > > ===> lib/clang/libllvm (all) > > >

Re: Enabling the WITH_REPRODUCIBLE_BUILD knob for 12.0-REL

> On 27 September 2018 at 06:46, tech-lists wrote: > > > > So, I want to know where and when each system was compiled. > > Why lose this information by default? > > This comes down to the simple fact that our build / release process > does not currently distinguish between building a world or

Re: FreeBSD EFI projects

> On 9/19/18 3:53 AM, Greg V wrote: > > > > > Yes, of course it was 64-bit. > > > > I don't think I ever downloaded the 32-bit one... > > > And are you sure it was booted via EFI and not the BIOS emulation CSM > (Compatibility Support Module)? I'm fairly sure we _don't_ support > booting a

Re: FreeBSD EFI projects

> > On 9/19/18 9:06 AM, Rodney W. Grimes wrote: > > Yes, that is one of the catagories of rare, a EFI-32 bit system that > > was originally shipped with a 32 bit only CPU, that later got upgraded > > in the field with a 64 bit CPU, that still runs a EFI-32 bios. > >

Re: FreeBSD EFI projects

> On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes > wrote: > >> On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes > >> wrote: > >> >> On 9/18/18 4:11 AM, Greg V wrote: > >> >> > >> >> > > >> >> &g

<    1   2   3   4   5   >