Re: 14-current: unable to boot after upgrade (installworld)

> On 9. Dec 2021, at 20:54, Sergey Dyatko wrote: > > tiger@dl:~ % gpart show > > | > =>40 3907029088 da4 GPT (1.8T) > 4010241 freebsd-boot (512K) >1064 984 - free - (492K) >2048

Re: 14-current: unable to boot after upgrade (installworld)

> On 9. Dec 2021, at 20:06, Sergey Dyatko wrote: > > I was sure the installer did it when I reinstalled the system from scratch. I > can load 14-current successfully after boot via PXE and installworld with > 13-current > now I did the following: > 1) boot from HDDs FreeBSD 14.0-CURRENT #0

Re: EFI/loader show garbage in console when set to some resolution in loader.conf

> On 6. Sep 2021, at 19:44, Karel Gardas wrote: > > Hello, > > I'm attempting to set EFI console resolution in loader to 1920x1920. This is > working fine on all 3 tested* combinations when interrupting loader with '3' > key and then > issueing 'gop set 11' command and then 'boot' command.

Re: FreeBSD-13-STABLE: lib/libsecureboot/verify_file.c: error: use of undeclared identifier 'SOPEN_MAX'

> On 3. Sep 2021, at 18:59, FreeBSD User wrote: > > Hello, > > enabling > > WITH_BEARSSL > > in src.conf renders buildworld on 13-STABLE to fail, but not on > 14-CURRENT. > > > > This is the difference between the sources, obviously 14-CURRENT contains the > correct > definition of

Re: lost high resolution console with lastest snapshot

nts. >> >> >> On Tue, 6 Jul 2021 14:42:26 +0200 (CEST) >> Ronald Klop wrote: >> >>> Maybe your previous install did not use UEFI? >>> >>> Ronald. >>> >>> >>> Van: Toomas Soome via freebsd-current >>>

Re: lost high resolution console with lastest snapshot

> On 6. Jul 2021, at 14:49, Nuno Teixeira wrote: > > Hello, > > gop get says: > --- > EDID 1920x1080 > mode 0 > --- > > When I try other modes it sometimes decreases res. > > I remember that high res was working until now. > Maybe a bug? GOP set/get/list is the only interface with uefi

Re: lost high resolution console with lastest snapshot

> On 6. Jul 2021, at 14:07, Nuno Teixeira wrote: > > I forgot to say that dmesg show vt resolution: > > --- > (...) > FreeBSD clang version 12.0.1 (g...@github.com:llvm/llvm-project.git > llvmorg-12.0.1-rc2-0-ge7dac564cd0e) > WARNING: WITNESS option enabled, expect reduced performance. > ==>

Re: vt: efifb / fb+kms resolutions and fonts — how to?

> On 13. May 2021, at 17:04, Lev Serebryakov wrote: > > > Is it possible to get native 1920x1080 resoultiuon and small fond (many > lines) early on boot? > > Lenovo T540p has native resolution 1920x1080 and boots with UEFI. I've tried > two configs: > > (1) No special configuration in

Re: bectl, chroot, pkg upgrade, no record of the upgrade in /var/log/messages

BE as snapshot + clone? zpool history has that fact, but if anything else is logged (syslog or direct file write), it will be in old BE. Unless /var/log is created as shared dataset. Sent from my iPhone > On 2. May 2021, at 14:42, Graham Perrin wrote: > > This morning I created a boot

Re: [Bug 254395] bsdinstall: fail script install after BETA3

> On 20. Mar 2021, at 00:21, Yuri Pankov wrote: > > Chris wrote: >> On 2021-03-19 13:06, bugzilla-nore...@freebsd.org wrote: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395 >>> >>> Nathan Whitehorn changed: >>> >>>What|Removed |Added >>>

Re: testers needed: loader: use display pixel density for font autoselection

t;>>> On 23. Feb 2021, at 17:53, Jakob Alvermark wrote: >>>>>>> >>>>>>> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote: >>>>>>>> hi! >>>>>>>> >>>>>>>> I have do

Re: No serial console: VBE not available

> On 1. Mar 2021, at 12:34, Harry Schmalzbauer wrote: > > Am 26.02.2021 um 17:58 schrieb Toomas Soome via freebsd-current: >>> On 26. Feb 2021, at 18:54, O. Hartmann wrote: >>> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA256 >>>

Re: HEADS-UP: PIE enabled by default on main

> On 28. Feb 2021, at 13:27, dmilith . wrote: > > First of all - ALSR is designed as mitigation for external attacks, > not internal ones (logged in user). > Second - Linux and FreeBSD both have weak implementations in > comparison to PAX-driven ones. Try attacking the system with > Grsecurity

Re: No serial console: VBE not available

> On 26. Feb 2021, at 18:54, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > hello, > > running a FreeBSD appliance on top of a PCengines APU2C4 with the latest > seabios > (apu2_v4.13.0.3.rom). The PCengines boot image layout is based on > pmbr/gptboot (GPT

Re: testers needed: loader: use display pixel density for font autoselection

> On 26. Feb 2021, at 17:56, Rodney W. Grimes > wrote: > >>> On 26. Feb 2021, at 05:42, Rodney W. Grimes >>> wrote: >>> >>>>> On 23. Feb 2021, at 17:53, Jakob Alvermark wrote: >>>>> >>>>> On 2/23/21 12:27

Re: testers needed: loader: use display pixel density for font autoselection

> On 26. Feb 2021, at 05:42, Rodney W. Grimes wrote: > >>> On 23. Feb 2021, at 17:53, Jakob Alvermark wrote: >>> >>> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote: >>>> hi! >>>> >>>> I have done some work to

Re: testers needed: loader: use display pixel density for font autoselection

> On 23. Feb 2021, at 17:53, Jakob Alvermark wrote: > > On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote: >> hi! >> >> I have done some work to make font pickup a bit smarter (hopefully better;), >> but my own ability to test is limited to

testers needed: loader: use display pixel density for font autoselection

hi! I have done some work to make font pickup a bit smarter (hopefully better;), but my own ability to test is limited to one bugged supermicro and one MBP with retina display… The phab link is https://reviews.freebsd.org/D28849 I have built loader

Re: loader/boot fonts are painfully small (again)

> On 11. Feb 2021, at 23:21, Yuri Pankov wrote: > > Lenovo P51 laptop, 15'' 4k (3840x2160) display. > > Booting from the latest available current snapshot (20210107), fonts > were at least readable; updating to the latest bits (manually installing > new loader as well) made them really small

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

> On 1. Feb 2021, at 05:35, Yasuhiro Kimura wrote: > > From: Yasuhiro Kimura mailto:y...@utahime.org>> > Subject: Setting for displaying utf8 characters on all vt consoles results in > panic on 14-CURRENT and 13.0-ALPHA3 > Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST) > >> To display utf8

Re: vidcontrol < /dev/console -i active ioctl error

> On 28. Jan 2021, at 01:35, Jesper Schmitz Mouridsen wrote: > > FreeBSD build.freebsd.lan 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #0 > main-c255938-g7ae27c2d6c4: Thu Jan 14 06:29:55 UTC 2021 > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > jesper@build:~ $ su >

Re: DRM and Radeon

> On 26. Jan 2021, at 10:18, Marek Zarychta > wrote: > > W dniu 26.01.2021 o 08:58, Graham Perrin pisze: >> On 26/01/2021 07:02, Alexey Dokuchaev wrote: >> > Re: loading drm crashes system >> > … There are known issues with Radeon cards, they were quite well >> > supported a year ago, then

Re: ZFS feature compatibility?

> On 26. Jan 2021, at 00:23, John Kennedy wrote: > >> Thanks, I am new to the EFI world. Does the name now have to be >> BOOTx64.efi ? >> >> root@zoo2:/boot # ls -l /mnt/EFI/freebsd/ >> total 824 >> -rwxr-xr-x 1 root wheel 843776 Nov 21 10:50 loader.efi >> root@zoo2:/boot # > if there

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 23:08, Allan Jude wrote: > > On 2021-01-25 16:03, Toomas Soome via freebsd-current wrote: >> >> >>> On 25. Jan 2021, at 22:15, mike tancsa wrote: >>> >>> On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 22:15, mike tancsa wrote: > > On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: >> >>> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current >>> wrote: >>> >>> I have a few machines on which I'

Re: ZFS feature compatibility?

> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current > wrote: > > I have a few machines on which I've been hesitant to run 'zpool upgrade' as > I'm not sure of the (boot?) implications. They report like this .. > > imb@toshi:/home/imb> uname -a > FreeBSD