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,
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
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:
> >
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
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
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
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
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.
> > >
> >
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
Greetings
a few weeks ago I pointed people to the nycbug dmesg service. I said I was
looking at data to drive SCSI retirement. I've gatherd some preliminary
data, which I've uploaded to
https://github.com/bsdimp/device-data/blob/master/cam.md along with some
preliminary notions of disposition for
At Netflix we have our OCA firmware based on FreeBSD -current (we take a
snapshot every 5 weeks or so). We've been booting thousands of machines off
nda for over a year... It absolutely works and is one of the things that
lets us deliver the content we do...
I have some patches in my queue
On Mon, Oct 8, 2018 at 7:32 AM Hans Petter Selasky wrote:
> On 10/8/18 3:06 PM, Warner Losh wrote:
> > You need "/boot/kernel/amdgpu.ko" here
> >
> > Warner
>
> Or did you mean:
>
> /boot/modules/amdgpu.ko
>
Doh! You're right. You need the one ins
On Mon, Oct 8, 2018 at 1:37 AM Thomas Mueller wrote:
> I just submitted /var/run/dmesg.boot from my current NetBSD and from
> FreeBSD 11.1-STABLE.
>
> I was surprised to see some other BSD OSes listed, including 5 dmesg
> reports from Bitrig and 3 from RetroBSD.
>
> I had been tracking three
On Mon, Oct 8, 2018 at 6:47 AM tech-lists wrote:
> Hi,
>
> context: 12-alpha8, amd64, xorg, AMD rx580 card
>
> As per /usr/ports/UPDATING, I have installed graphics/drm-kmod which has
> installed drm-next-kmod-4.11.g20180822
>
> As per pkg message, it's loaded with this line in /etc/rc.conf:
>
>
On Sun, Oct 7, 2018 at 3:49 AM Konstantin Belousov
wrote:
> On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote:
> >
> > > Greetings,
> > >
> > > As you can tell, the project is looking to c
On Sun, Oct 7, 2018 at 2:16 AM Dhananjay Balan wrote:
> On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote:
> >
> > > Greetings,
> > >
> > > As you can tell, the project is looking to c
On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote:
> Greetings,
>
> As you can tell, the project is looking to clear some of the deadwood from
> its driver lists. One problem is that we have to guess what's in used based
> on our personal experience. This has proven to be les
Greetings,
As you can tell, the project is looking to clear some of the deadwood from
its driver lists. One problem is that we have to guess what's in used based
on our personal experience. This has proven to be less reliable than hoped
in the 10/100 discussions that are going on now.
So, to
On Sat, Oct 6, 2018 at 10:22 AM Kevin Oberman wrote:
> Due to lack of space on /var, I am unable to get a dump. (I'll get that
> fixed soon, but shuffling partitions take more time than I have right now.
>
You can run savecore after you boot the system and direct its output to
another
On Thu, Oct 4, 2018 at 10:37 AM Allan Jude wrote:
> On 2018-10-04 12:29, Zaphod Beeblebrox wrote:
> > Are there any plans to support AMD RAID?
> >
> > AMD RAID is _like_ Intel RAID, but has a number of differences. One is
> > that it requires UEFI (without UEFI it does not boot, at least). It
swell if there were a cheap to obtain box that exhibits this problem.
Warner
On Sat, Sep 29, 2018 at 6:14 PM Warner Losh wrote:
> Sadly both of these bugs are thin on detail beyond it doesn't work. Makes
> it hard to even look into it.
>
> Warner
>
> On Sat, Sep 29, 2018, 6
Sadly both of these bugs are thin on detail beyond it doesn't work. Makes
it hard to even look into it.
Warner
On Sat, Sep 29, 2018, 6:00 PM Yuri wrote:
> See:
>
> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230090
>
> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957
>
>
>
On Fri, Sep 28, 2018 at 2:02 PM Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Fri, Sep 28, 2018 at 02:47:39PM -0500, Matthew D. Fuller wrote:
> > On Fri, Sep 28, 2018 at 11:00:02AM -0700 I heard the voice of
> > Steve Kargl, and lo! it spake thus:
> > >
> > > I have a radeon HD
On Fri, Sep 28, 2018 at 12:01 PM Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
>
> At the risk of raising the ire of others, but with the pending
> branching for FreeBSD 12, I respectfully request that drm2
> remain in head after the branch.
The current plans, which are still being
On Sun, Sep 23, 2018, 6:11 AM Graham Perrin wrote:
> No problem with Plasma here with
> FreeBSD 12.0-ALPHA7 r338892 GENERIC-NODEBUG
> built and installed a few hours ago.
>
> Prior to that I used an alpha from … probably mid-August. No problem with
> networking after startup, and no post-startup
On Fri, Sep 21, 2018 at 9:59 PM Rebecca Cran wrote:
> On 9/21/18 9:57 PM, Warner Losh wrote:
>
> > Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say?
> >
> > They look good for me, but the only way you get this error is if they
> > are wrong
s from
the host as well, even though we rebuild them...
Warner
On Fri, Sep 21, 2018 at 9:38 PM Rebecca Cran wrote:
> On 9/21/18 9:35 PM, Warner Losh wrote:
> >
> > I meant to add, can you give a few lines before the error is spewed
> > here in email? My IRC computer died before
On Fri, Sep 21, 2018 at 9:34 PM Warner Losh wrote:
>
>
> On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote:
>
>> On 9/21/18 9:09 PM, Warner Losh wrote:
>>
>> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
>> > freebsd-toolch
On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote:
> On 9/21/18 9:09 PM, Warner Losh wrote:
>
> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
> > freebsd-toolch...@freebsd.org> wrote:
> >
> >> On 9/21/18 4:06 PM, Mark Johnston w
On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
freebsd-toolch...@freebsd.org> wrote:
> On 9/21/18 4:06 PM, Mark Johnston wrote:
> >
> > https://reviews.freebsd.org/D17279 for anyone else that would like to
> > review.
>
>
> Is that possibly related to the error I'm getting
On Wed, Sep 19, 2018 at 4:33 PM Rebecca Cran wrote:
> Oh, that's a really good point - thanks! I happen to have a Minnowboard
> Turbot currently sitting unused.
>
One other idea, unrelated to the 32-bit UEFI to boot 64-bit kernel, is to
see about mining tsoome@'s port of FreeBSD boot loader to
On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote:
> On 9/16/18 9:32 PM, Warner Losh wrote:
>
> >
> > What did you have in mind working on? I have a few things that are in
> > various stages of completeness around this issue that I've not had
> > time to polish o
On Sun, Sep 16, 2018 at 4:31 PM Rebecca Cran wrote:
> I'm just getting back into FreeBSD development, and I'm trying to focus
> on (U)EFI work.
>
> It seems there are various things that people would like to have done,
> some of which are listed on
>
On Mon, Sep 10, 2018 at 8:58 AM Ed Maste wrote:
> The FreeBSD base system is a reproducible build[1] with a minor
> exception: the build metadata (timestamps, user, hostname, etc.)
> included in the kernel and loader.
>
> With the default, non-reproducible build the kernel ident looks like:
>
>
On Thu, Sep 6, 2018, 5:49 PM Ed Maste wrote:
> On 4 September 2018 at 06:53, Kurt Jaeger wrote:
> >
> > The github repo isn't official, because there are still some
> > consistency issues. The consistency problem is: If an repo-copy
> > from svn to git is done, how can that repo-copy be done a
For those wondering at what's going on with this, I've shared the following
with the developers@ mailing list. I thought I'd share it here to fight the
misinformation that's swirling about. We don't have all the answers yet,
and I'm working on it with others in the community to get the best
On Sat, Aug 25, 2018, 12:17 PM Pete Wright wrote:
>
>
> On 8/25/18 11:10 AM, Yuri Pankov wrote:
> > Pete Wright wrote:
> >> howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
> >> that my usb mouse is not being detected. i made sure to do a proper
> >> mergemaster after
On Fri, Aug 24, 2018 at 4:20 PM Niclas Zeising wrote:
> On 08/24/18 17:20, Warner Losh wrote:
> > This would allow the graphics port to have a rc script that sets
> > this up so when X11 goes to automatically load the module, the right one
> > gets loaded.
> >
&
On Fri, Aug 24, 2018 at 4:20 PM Matthew Macy wrote:
> On Fri, Aug 24, 2018 at 14:53 Ali wrote:
>
> > On Tue, Aug 21, 2018 at 06:54:54PM -0700, Matthew Macy wrote:
> > > Just in case anyone misses the change to UPDATING:
> > >
> > > 20180821:
> > > drm and drm2 have been removed. Users
On Fri, Aug 24, 2018 at 9:27 AM Johannes Lundberg
wrote:
> There's some tricks we can do here.
>>
>> First, I talked to Kyle yesterday about augmenting the Lua loader to have
>> a X_loadflag option. Some background. We look at a lot of X_ flags for
>> loading modules. X_load=yes being the
On Fri, Aug 24, 2018 at 8:13 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Fri, Aug 24, 2018 at 3:22 AM Johannes Lundberg
> wrote:
> > >
> > > On Fri, Aug 24, 2018 at 10:12 AM Matthew Macy
> wrote:
> > >
> > > > No we're not. x86 and PPC will be disconnected from the
On Fri, Aug 24, 2018 at 2:14 AM Matthew Macy wrote:
> No we're not. x86 and PPC will be disconnected from the build in a
> subsequent commit during the freeze. Warner was simply too tired to
> communicate this adequately and still meet the timeline that RE wanted.
>
We're still trying to figure
On Tue, Aug 21, 2018 at 8:16 AM, Warner Losh wrote:
> There's a half a dozen special targets, however. clean comes to mind...
>
>
> However, this test is needlessly restrictive:
>
> .if !empty(CFLAGS:M*${SRCTOP}/sys*:N*${SRCTOP}/sys/cddl/compat*:
> N*${SRCTOP}/sys/crypto*)
129 fixed the issue. Seems like the problem is that
> bsd.crunchgen.mk iterates over all directories to do a make obj when
> it does the bootstrap-tools phase.
> On Tue, 21 Aug 2018 at 14:49, Warner Losh wrote:
> >
> >
> >
> > On Tue, Aug 21, 2018 at 12:38 AM, John Baldw
On Tue, Aug 21, 2018 at 7:49 AM, Warner Losh wrote:
>
>
> On Tue, Aug 21, 2018 at 12:38 AM, John Baldwin wrote:
>
>> On 8/20/18 9:00 PM, O. Hartmann wrote:
>> > -BEGIN PGP SIGNED MESSAGE-
>> > Hash: SHA512
>> >
>> > Am Mon,
On Tue, Aug 21, 2018 at 12:38 AM, John Baldwin wrote:
> On 8/20/18 9:00 PM, O. Hartmann wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Am Mon, 20 Aug 2018 21:24:21 +0200
> > "O. Hartmann" schrieb:
> >
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA512
> >>
> >>
On Mon, Aug 20, 2018 at 5:24 PM, Brett
wrote:
> On 8/20/2018 7:09 PM, Warner Losh wrote:
>
>> On Mon, Aug 20, 2018 at 4:50 PM, Brett
>> wrote:
>>
>> Hi Kevin,
>>>
>>> Thanks for your help.
>>>
>>> Should I be doing "make
On Mon, Aug 20, 2018 at 4:50 PM, Brett
wrote:
> Hi Kevin,
>
> Thanks for your help.
>
> Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
> LOADER_DEFAULT_INTERP=4th installkernel"?
>
Nope. Kernel has nothing to do with it. That won't work.
I had also previously tried "
On Mon, Aug 20, 2018 at 9:55 AM, Kyle Evans wrote:
> On Mon, Aug 20, 2018 at 10:39 AM, Manfred Antar
> wrote:
> > Hi
> > How do i get the menu back after switching to LUA loader?
> > I’m using a comconsole. Before the switch to LUA I had a menu and a
> little devil with pitchfork:)
> > Now just
On Sun, Aug 19, 2018 at 11:10 AM, Warner Losh wrote:
>
> I think including both loaders in userboot is probably a no-start
>> based on the current interface.
>>
>
> Yea, it would be a challenge... Sadly, we have POLA violations either way
> we jump here.
>
Just to
On Sun, Aug 19, 2018 at 11:03 AM, Kyle Evans wrote:
> On Sun, Aug 19, 2018 at 11:58 AM, John Baldwin wrote:
> > On 8/19/18 5:28 PM, Kyle Evans wrote:
> >> On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote:
> >>> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman
On Sun, Aug 19, 2018 at 11:04 AM, Larry Rosenman wrote:
> so it still looks forth'ish, but it's using lua.
>
It will always look forthish becuase it's unused in loader_lua.
Warner
___
freebsd-current@freebsd.org mailing list
On Sun, Aug 19, 2018 at 10:58 AM, John Baldwin wrote:
> On 8/19/18 5:28 PM, Kyle Evans wrote:
> > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote:
> >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman
> wrote:
> >>
> >>> On Sun, Aug 19, 2
On Sun, Aug 19, 2018 at 10:05 AM, Larry Rosenman wrote:
> On Sun, Aug 19, 2018 at 11:54:51AM -0400, Joe Maloney wrote:
> > I ran into this as well months ago. To workaround it I extracted
> > userboot.so for the VM's, and launched bhyve with the alternate
> > userboot.so. You can use a flag as
On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote:
> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote:
> > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote:
> >
> > > With today's change to LUA as the loader, I seem to have an issue with
> >
On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote:
> With today's change to LUA as the loader, I seem to have an issue with
> bhyhve:
>
> Consoles: userboot
>
> FreeBSD/amd64 User boot, Revision 1.1
> (Thu Nov 16 15:04:02 CST 2017 r...@borg.lerctr.org)
> Startup error in
On Wed, Aug 15, 2018 at 7:00 AM, Kyle Evans wrote:
> On Wed, Aug 15, 2018 at 7:53 AM, Kyle Evans wrote:
> > On Wed, Aug 15, 2018 at 7:40 AM, David Wolfskill
> wrote:
> >> I'm tracking head/amd64 daily twice on each of two machines: my "build
> >> machine" ("freebeast") and my laptop, each
I never have /usr/src on my system (other than the directory that mtree
creates). So when I run mergemaster it's always failing until I remember to
add the -m . (or was it -t ., I sometimes forget).
Given the recent ntpd stuff, I was annoyed enough with this default
behavior to create a fix for
On Sun, Aug 12, 2018, 4:27 PM Matthew Macy wrote:
>
>
> On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote:
>
>>
>>
>> On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote:
>>
>>> Sorry guys, last time I touched ZFS I tried to push to make it an optio
On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote:
> Sorry guys, last time I touched ZFS I tried to push to make it an option to
> statically link and was actually told that it wasn't something anyone else
> wanted. The issue comes from ZFS not being in NOTES and thus not in LINT.
>
LINT is
On Fri, Aug 10, 2018 at 5:30 PM, Erich Dollansky <
freebsd.ed.li...@sumeritec.com> wrote:
> Hi,
>
> On Fri, 10 Aug 2018 07:53:19 -0600
> Warner Losh wrote:
>
> > On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
> > freebsd.ed.li...@sumeritec.com> wrote:
On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
freebsd.ed.li...@sumeritec.com> wrote:
> Hi,
>
> On Fri, 10 Aug 2018 12:40:48 +0800
> blubee blubeeme wrote:
>
> > On Fri, Aug 10, 2018 at 8:28 AM Erich Dollansky <
> > freebsd.ed.li...@sumeritec.com> wrote:
> >
> > > Hi,
> > >
> > > On Fri, 10
On Wed, Aug 8, 2018 at 6:03 PM, Allan Jude wrote:
> On 2018-08-08 19:21, Sean Bruno wrote:
> >
> >
> > On 08/08/18 17:13, Warner Losh wrote:
> >>
> >>
> >> On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno >> <mailto:sbr...@freebsd.org>>
On Wed, Aug 8, 2018 at 5:21 PM, Sean Bruno wrote:
>
>
> On 08/08/18 17:13, Warner Losh wrote:
> >
> >
> > On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno > <mailto:sbr...@freebsd.org>> wrote:
> >
> > tl;dr pxeboot new x86 host, ip
On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno wrote:
> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after multiuser.
>
> The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am having
> the hardest time with the IPMI SOL interface.
>
> I have configured "COM2" as the IPMI SOL
On Wed, Aug 8, 2018 at 6:19 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Wed, Aug 08, 2018 at 06:14:19PM +0100, Warner Losh wrote:
> > On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > >
On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> Just build a new world and kernel. Upon doing "make installkernel",
> I see at the end of the process
>
> kldxref /boot/kernel
> kldxref: unhandled relocation type 2
> kldxref: unhandled relocation type 2
>
On Sat, Aug 4, 2018, 8:21 PM Emmanuel Vadot wrote:
> On Sat, 04 Aug 2018 09:47:11 -0600
> Ian Lepore wrote:
>
> > On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote:
> > > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote:
> > > >
> > > > On Sat, 2018-08-04 at 18:22 +0300,
On Fri, Aug 3, 2018, 10:17 PM Tommi Pernila wrote:
>
>
> On Fri, 3 Aug 2018 at 20.17, Warner Losh wrote:
>
>> On Fri, Aug 3, 2018, 5:58 PM Ian Lepore wrote:
>>
>> > On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote:
>> > > On
On Fri, Aug 3, 2018, 5:58 PM Ian Lepore wrote:
> On Fri, 2018-08-03 at 19:54 +0300, Tommi Pernila wrote:
> > On Tue, 10 Jul 2018 at 1.05, Warner Losh wrote:
> >
> > >
> > > I have this in my tree already...
> > >
> > > Warner
> > >
On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk wrote:
> On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote:
> > On 08/01/2018 09:02, Warner Losh wrote:
> > >
> > >
> > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle > > <mailto:e...@metr
fore?
> >
> > > - --
> > > O. Hartmann
> [...]
>
> >
> > Roman Bogorodskiy
>
> I'm glad to be of help. But it was a "wild guess", not experience or
> decend knowledge.
> Maybe there is an issue with recent UEFI/boot/stand implementa
On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle wrote:
> Hi folks,
>
> I'm wondering what's the status of OpenSSL 1.1.1 integration into base?
> More specifically, is there a repo or a branch that's started the
> integration? I'm aware of the wiki page and the list of port build
> issues, but that
On Sat, Jul 28, 2018 at 1:50 PM, Emmanuel Vadot
wrote:
> On Sat, 28 Jul 2018 13:27:08 -0600
> Warner Losh wrote:
>
> > Let me know the rev... all my fixes are in the tree...
> >
> > Warner
>
> Fixed by r336837
>
Yea, I thought I'd pushed all my in-flight
Let me know the rev... all my fixes are in the tree...
Warner
On Sat, Jul 28, 2018, 12:52 PM Emmanuel Vadot wrote:
> On Sat, 28 Jul 2018 20:34:31 +0200
> Emmanuel Vadot wrote:
>
> > On Sat, 28 Jul 2018 20:28:30 +0200
> > Emmanuel Vadot wrote:
> >
> > > On Sat, 28 Jul 2018 13:17:45 -0400
> >
On Sat, Jul 28, 2018, 12:08 PM Mark Johnston wrote:
> On Sat, Jul 28, 2018 at 01:17:45PM -0400, Shawn Webb wrote:
> > It appears with the latest 12-CURRENT/arm64, booting is broken. The
> > boot process gets stuck after the "Using DTB provided by..." message.
> >
> > This is on my SoftIron
[[ context trimmed ]]
On Fri, Jul 27, 2018 at 12:03 PM, Warner Losh wrote:
>
>
> On Fri, Jul 27, 2018 at 11:05 AM, O. Hartmann
> wrote:
>
>>
>> Just to add another success on ASRock Z77-Pro4 (800k ESP, FAT12) and
>> ASRock Z77-Pro4M
>> (300mb ESP, FAT32).
On Fri, Jul 27, 2018 at 11:05 AM, O. Hartmann
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Fri, 27 Jul 2018 13:59:44 +0300
> Toomas Soome schrieb:
>
> > > On 27 Jul 2018, at 13:02, O. Hartmann wrote:
> > >
> > > On Fri, 27 Jul 2018 08:54:48 +0300
> > > Toomas Soome wrote:
go-to
> person.
>
> ---
> Sent using a tiny phone keyboard.
> Apologies for any typos and autocorrect.
> Also, this old phone only supports top post. Apologies.
>
> Cy Schubert
> or
> The need of the many outweighs the greed of the few.
> ---
>
--
> From: Ian Lepore
> Sent: 15/07/2018 11:08
> To: Warner Losh; K. Macy
> Cc: Steve Kargl; FreeBSD Current
> Subject: Re: [PATCH] Recent libm additions
>
> On Sun, 2018-07-15 at 11:55 -0600, Warner Losh wrote:
> > On Sun, Jul 15, 2018, 11:23 AM K. Macy wrote:
>
On Sun, Jul 15, 2018, 11:23 AM K. Macy wrote:
> >
> > Well, actually, the functions in polevll.c should have been copied
> > into ld80/e_powl.c, and polevall.c should never have been committed.
> > Unfortunately, the code was not reviewed for correctness.
>
> That is not correct. Please stop
These changes look perfect to me.
Warner
On Sun, Jul 15, 2018, 9:08 AM Steve Kargl
wrote:
> Apparently, the recents additions to libm were not
> subject to any code review. The following patch
> does two things. First, it works around
>
> https://bugs.llvm.org/show_bug.cgi?id=8532
>
>
I don't know enough about efi myself to update the script
> > to make it assemble images the new way Warner envisions.
> >
> > -- Ian
> >
> >>>
> >>> I'm in the middle of moving to a new apartment right now. It's
> >>> going to
> >>
Yea, there's a stray space in that string.
r336114 should fix that.
Warner
On Sun, Jul 8, 2018 at 4:50 PM, Mark Millard wrote:
> https://ci.freebsd.org/job/FreeBSD-head-amd64-build/9386/consoleText
> shows:
>
> ===> zlib (install)
> install -T release -o root -g wheel -m 555 zlib.ko
>
On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
> >
> > > [ Charset UTF-8 unsupported, converting... ]
> > >> On 5 Jul 2018, at 17:19, Warner Losh wrote:
&
On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin wrote:
> On 7/5/18 12:36 PM, Konstantin Belousov wrote:
> > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote:
> >> On 07/05/18 20:59, Hans Petter Selasky wrote:
> >>> On 07/05/18 19:48, Pete Wright wrote:
>
>
> On
On Thu, Jul 5, 2018 at 3:31 PM, Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote:
>
> [ Charset UTF-8 unsupported, converting... ]
>>
>>> On 5 Jul 2018, at 17:19, Warner Losh wrote:
>>>
>>&g
I think I know what is going on... I may have some changes that fixes this.
Warner
On Thu, Jul 5, 2018, 9:12 AM Linus Sundqvist
wrote:
> I have no idea how to do that or where to begin, but if anyone would like
> to assist with those steps I'll gladly run commands or a test ISO on one of
> our
On Thu, Jul 5, 2018, 12:55 PM Bjoern A. Zeeb
wrote:
> On 5 Jul 2018, at 17:19, Warner Losh wrote:
>
> > FAT12 isn't good for UEFI. Use FAT16 or FAT32.
>
> We use it for the default image we built and the wiki suggests it as
> well at https://wiki.freebsd.org/UEFI#CD.2FDVD_
FAT12 isn't good for UEFI. Use FAT16 or FAT32.
Warner
On Thu, Jul 5, 2018, 9:32 AM Bjoern A. Zeeb
wrote:
> Hi,
>
> while I can boot memstick images just fine (which are created using
> makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I
> am not able to get anything that
On Wed, Jul 4, 2018, 2:13 PM Kevin Oberman wrote:
> On Wed, Jul 4, 2018 at 11:49 AM, Yuri wrote:
>
> > On 07/04/18 07:27, Rodney W. Grimes wrote:
> >
> >> Devd/devmatch is one of the largest changes recently,
> >> it could be something in that code path.
> >>
> >> Do you get the if_run.ko
On Wed, Jun 27, 2018, 7:27 PM Mark Millard wrote:
> These are the gcc/g++ 4.2.1 based targets.
>
> For example . . .
>
> https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/6261/consoleText
>
> --- all_subdir_sbin/devd ---
> /usr/src/sbin/devd/devd.cc: In member function 'std::string
>
On Mon, Jun 25, 2018 at 11:40 AM, tech-lists wrote:
> On 25/06/2018 16:37, Warner Losh wrote:
>
>> While the compat stuff generally works, there are edge cases where it
>> will fail when you have a mixed environment. You're best bet is to
>> reinstall all ports. If you d
On Mon, Jun 25, 2018 at 6:40 AM, tech-lists wrote:
> Hello,
>
> When upgrading an old-ish 12-current (r317212), as per:
>
> 20170523:
>> The "ino64" 64-bit inode project has been committed, which extends
>> a number of types to 64 bits. In order to upgrade, carefully
>> follow
There were some issues with legacy geely booting recently. What version?
UEFI or legacy BIOS booting?
Warner
On Fri, Jun 22, 2018, 10:26 PM Ben Woods wrote:
> On 23 June 2018 at 12:08, Allan Jude wrote:
>
> > If you just press shift a bunch of times, does it print the Mount root
> > prompt?
>
On Tue, Jun 19, 2018 at 5:11 AM, Rick Macklem wrote:
> Steve Wills wrote:
> On 06/18/18 17:42, Rick Macklem wrote:
> >> Steve Wills wrote:
> >>> Would it be possible or reasonable to use the client ID to log a
> message
> >>> telling the admin to enable a sysctl to enable the hacks?
> >> Yes.
My thoughts on this are mixed.
You need certain workarounds, but they sound like they need to be on a
per-client-type basis.
On the one hand, you don't want to chat with different clients differently,
but on the other you want it to work.
I'd suggest a two-tiered approach.
First, have a sysctl
On Mon, Jun 18, 2018, 3:01 AM Olivier Cochard-Labbé
wrote:
> On Sun, Jun 17, 2018 at 10:01 AM O. Hartmann
> wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Running CURRENT as routing and firewalling appliance on a PCengines APU
> > 2C4 with the
> > latest (official)
On Thu, Jun 14, 2018 at 2:15 PM, Rick Macklem wrote:
> Hi,
>
> I have three new utilities that are mainly useful for managing the pNFS
> server
> committed as r335130.
>
> In the projects tree, I have them in /usr/bin and man section 1. However,
> since they are mostly useful to a sysadmin
On Wed, Jun 6, 2018 at 12:55 AM, O. Hartmann
wrote:
> Hello,
>
> my desperate call for help is according to PR 225291,
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291.
>
> On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core
> CPU)
> I face the inability to burn
601 - 700 of 3044 matches
Mail list logo
