(244906) installers for FreeBSD fail to boot HP ProBook 440 G7

[Graham Perrin]

This is now identified as FreeBSD bug 244906:


kernel booted by loader.efi on VMware Fusion crashes in EFI firmware

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

review request: loader: implement framebuffer console

[Toomas Soome]

hi!

I have been working on proper framebuffer support on FreeBSD loader and there 
is the current state: https://reviews.freebsd.org/D27420 


All feedback is welcome, and especially if you can spare some time for testing:)

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

Re: port build fails with missing sys/smr_types.h

[Chuck Tuffli]

On Thu, Dec 3, 2020 at 4:43 PM Mark Johnston  wrote:
...
> $ fetch 
> http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/13.0-CURRENT/amd64/20201126/FreeBSD-13.0-CURRENT-amd64-20201126-9e082d278b9.raw.xz
> $ unxz FreeBSD-13.0-CURRENT-amd64-20201126-9e082d278b9.raw.xz
> $ sudo mdconfig -a -f FreeBSD-13.0-CURRENT-amd64-20201126-9e082d278b9.raw
> md0
> $ sudo mount /dev/md0p4 /mnt
> $ stat /mnt/usr/include/sys/smr_types.h
> 544 241404 -r--r--r-- 1 root wheel 554933 4985 "Nov 26 03:57:51 2020" "Nov 26 
> 03:51:14 2020" "Nov 26 03:58:26 2020" "Nov 26 03:51:14 2020" 32768 16 0 
> /mnt/usr/include/sys/smr_types.h
> $
>
> So I'm not sure what's going on in your case.  smr_types.h was added a
> number of months ago.

Weird, it looks like I borked my system somehow. But thank you, that
helped immensely!

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

Re: Removing obsolete GDB 6.1.1 for FreeBSD 13

[Ed Maste]

Adding the FreeBSD-stable list to CC for more visibility.

On Wed, 2 Dec 2020 at 12:43, Ed Maste  wrote:
>
> I would like to remove GDB 6.1.1 before FreeBSD 13, and propose to
> switch the GDB knob to default to NO in the near future. If the
> crashinfo utility and related man pages do not already include
> references to installing the gdb port/package I will add those before
> making the change.

The crashinfo man page now references the gdb port/package, and
crashinfo itself emits a message that the port/package should be
installed if kgdb is not found.

GDB's proposed retirement has now been added to
https://wiki.freebsd.org/DeprecationPlan.

I expect to make GDB default to NO next week, and then remove it from
the tree a week or two later, if there is no compelling objection.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: review request: loader: implement framebuffer console

[Gordon Bergling]

Hi Toomas,

thanks for working on this. I have a build running and report back
the results from Hyper-V FreeBSD instance.

--Gordon

PS: A few months ago I had a look at all the OpenSolaris incarnations and this
feature was something I had on my TODO list for FreeBSD for a very long time. :)

On Fri, Dec 04, 2020 at 11:24:25AM +0200, Toomas Soome wrote:
> hi!
> 
> I have been working on proper framebuffer support on FreeBSD loader and there 
> is the current state: https://reviews.freebsd.org/D27420 
> 
> 
> All feedback is welcome, and especially if you can spare some time for 
> testing:)
> 
> thanks,
> toomas
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

Re: review request: loader: implement framebuffer console

[Gordon Bergling]

Tested on a recent -CURRENT, no problems seen so far.

Is there a special src.conf setting that is necessary for a
complete build / test sequence.

--Gordon

On Fri, Dec 04, 2020 at 11:24:25AM +0200, Toomas Soome wrote:
> I have been working on proper framebuffer support on FreeBSD loader and there 
> is the current state: https://reviews.freebsd.org/D27420 
> 
> 
> All feedback is welcome, and especially if you can spare some time for 
> testing:)
> 
> thanks,
> toomas
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Deprecating userland a.out support

[Ed Maste]

FreeBSD has used ELF binaries/libraries for decades, but still has
support for legacy a.out binaries. Portions of this have been retired
over time, and I propose removing the remaining pieces before FreeBSD
13. I'm not proposing making any change to kernel a.out support, but
users needing userland a.out tools would have to install them from old
FreeBSD releases.

I have opened the following reviews for three tools that still support a.out:

D27478 ldd: Retire a.out support
D27480 gprof: Retire a.out support
D27481 ldconfig: Retire a.out support

If there are no objections I plan to commit these changes before the
end of the month, along with small changes to the mtree file (removing
aout directories) etc.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: review request: loader: implement framebuffer console

[Toomas Soome]

> On 4. Dec 2020, at 23:03, Gordon Bergling  wrote:
> 
> Tested on a recent -CURRENT, no problems seen so far.
> 
> Is there a special src.conf setting that is necessary for a
> complete build / test sequence.
> 
> --Gordon

No, except that the last update did change default for bios loader to text and 
did add the knob to change that to gfx mode.

For test, the default mode should be readable and logo/brand images ok and the 
console after boot usable as well. The resolution switch (gop or vbe) should 
end up with usable screen as well, and when you enter menu, the boot menu 
should be ok.

gop get/vbe get will list current mode, show screen.font will tell font size.

Currently it is known the 8-bit depth may have issues in some systems (bios, 
UEFI only does have 32-bit depth).

thanks,
toomas

> 
> On Fri, Dec 04, 2020 at 11:24:25AM +0200, Toomas Soome wrote:
>> I have been working on proper framebuffer support on FreeBSD loader and 
>> there is the current state: https://reviews.freebsd.org/D27420 
>> 
>> 
>> All feedback is welcome, and especially if you can spare some time for 
>> testing:)
>> 
>> thanks,
>> toomas
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

How to clear the 'remove:' line from 'zpool status'

[Dustin Marquess]

So I stupidly did a 'zpool add' instead of a 'zpool attach'.  Luckily
I was able to 'zpool remove' the device thanks to the remove work done
a while back.

However, now I can't for the life of me get this part of the 'zpool
status' output to go away:

  pool: zroot
 state: ONLINE
  scan: scrub repaired 0B in 00:01:06 with 0 errors on Fri Dec  4 18:18:31 2020
remove: Removal of vdev 1 copied 104K in 0h0m, completed on Fri Dec  4
18:10:08 2020
72 memory used for removed device mappings
config:

I've tried 'zppol clear', 'zpool scrub', and rebooted.  Is there some
way to clear that 'remove' line? It's irritating my OCD :(.

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