Re: Removing fdisk and bsdlabel (legacy partition tools)

> On 26. Jan 2024, at 18:21, Rodney W. Grimes > wrote: > >> >> >>> On 26. Jan 2024, at 18:02, Rodney W. Grimes >>> wrote: >>> >>> -- Start of PGP signed section. Am 2024-01-25 18:49, schrieb Rodney W. Grimes: >> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: >> >>> On

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On 26. Jan 2024, at 18:02, Rodney W. Grimes > wrote: > > -- Start of PGP signed section. >> Am 2024-01-25 18:49, schrieb Rodney W. Grimes: On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes > wrote: >> >>> These will

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 16:07, Konstantin Belousov wrote: > > On Fri, Dec 22, 2023 at 11:36:24AM +0200, Toomas Soome wrote: >> >> >>> On 22. Dec 2023, at 11:09, Mark Millard wrote: >>> >>> Tomoaki AOKI wrote on >>> Date: Thu, 21 Dec 2

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 11:54, Mark Millard wrote: > > On Dec 22, 2023, at 01:36, Toomas Soome wrote: >> >> >> >>> On 22. Dec 2023, at 11:09, Mark Millard wrote: >>> >>> Tomoaki AOKI wrote on >>> Date: Thu, 21 Dec 2

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 11:09, Mark Millard wrote: > > Tomoaki AOKI wrote on > Date: Thu, 21 Dec 2023 23:21:00 UTC : > >> On Thu, 21 Dec 2023 14:22:14 +0100 >> Dimitry Andric wrote: >> >>> Yeah, my procedure is the same as yours: I first copy >>> /boot/efi/efi/freebsd/loader.efi to

Re: how to set vfs.zfs.arc.max in 15-current ?

> On 13. Oct 2023, at 09:35, void wrote: > > On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: > >> Set also vfs.zfs.arc.min to some value higher than zero. > > aha! that worked!!! :D > > root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 > vfs.zfs.arc.min: 0 -> 1073741824 >

Re: CURRRENT snapshot won't boot due missing ZFS feature

Re: WITH_BEARSSL: -8112 bytes available

> On 1. Jun 2023, at 11:30, Gary Jennejohn wrote: > > On Wed, 31 May 2023 14:41:23 -0600 > Warner Losh mailto:i...@bsdimp.com>> wrote: > >> On Wed, May 31, 2023 at 1:30?PM Gary Jennejohn wrote: >> >>> On Wed, 31 May 2023 12:15:12 -0600 >>> Warner Losh wrote: >>> >>> [SNIP irrelevant text]

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

> On 15. May 2023, at 15:22, Oleg Lelchuk wrote: > > Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned in > the previous email message... I find it a bit surprising that I only had to > make one tiny change to the source code of stand to make the graphical logo >

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

ime. rgds, toomas > On Fri, May 12, 2023, 6:55 AM Toomas Soome <mailto:tso...@me.com>> wrote: >> >> >>> On 12. May 2023, at 13:41, Oleg Lelchuk >> <mailto:oleglelc...@gmail.com>> wrote: >>> >>> There is only one monitor connec

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

re update from system vendor, that may fix the missing ConOut. rgds, toomas > > On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot <mailto:m...@bidouilliste.com>> wrote: >> On Fri, 12 May 2023 00:20:47 +0300 >> Toomas Soome mailto:tso...@me.com>> wrote: >> &g

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

le (see show console on loader prompt). rgds, toomas > > On Thu, May 11, 2023 at 6:06 PM Toomas Soome <mailto:tso...@me.com>> wrote: >> >> >>> On 12. May 2023, at 00:57, Oleg Lelchuk >> <mailto:oleglelc...@gmail.com>> wrote: >>> >&

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

/dtb;/boot/dtb/overlays" > nextboot_conf="/boot/nextboot.conf" > ram_blacklist_name="/boot/blacklist.txt" > > The efivar command shows me: > > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

> On 12. May 2023, at 00:11, Oleg Lelchuk wrote: > > Guys, there is something that I find puzzling. Why doesn't the EFI boot > loader want to display the graphical orb logo in its boot menu on an Asus > Prime 7590-P motherboard? Is there something quirky about this particular > motherboard

Re: loader.efi module path vs kernel directory

Whoops, meant cli.lua(8), of course. > On 20. Oct 2022, at 13:58, Toomas Soome wrote: > > > the problem with ‘?’ command is that it only does list commands written in C, > it does not list scripted commands. cli_lua(8) should list lua specific ones. > And at least my sta

Re: loader.efi module path vs kernel directory

be present (defined in /boot/lua/cli.lua). I am also pretty sure, Kyle did add those when 13 was current, lua version was missing those, Forth version had them first:) rgds, toomas > On 20. Oct 2022, at 13:27, Andriy Gapon wrote: > > On 20/10/2022 13:20, Toomas Soome wrote: >> Also, in

Re: loader.efi module path vs kernel directory

Also, instead of manual load, you may want to use enable-module. Sent from my iPhone > On 20. Oct 2022, at 13:08, Emmanuel Vadot wrote: > > On Thu, 20 Oct 2022 13:03:26 +0300 > Andriy Gapon wrote: > >> >> I recently needed to recover a system by manually preloading a driver. >> To a bit of

Re: kernel panic during zfs pool import

> On 18. Aug 2022, at 18:46, Santiago Martinez wrote: > > Hi everyone, > > I have a server running 13.1-stable that was powered off (gracefully) and now > is been powered on again and we have the following problem. > > The server boots almost properly, kernel load and when zfs import other

Re: 24.3. Updating Bootcode

> On 16. Aug 2022, at 15:01, Nuno Teixeira wrote: > > Hi Toomas, > > For better OS support, the UEFI specification (UEFI 2.8A Feb 14, page 499) is > suggesting to use structure like: > > /efi//… > > And to use this suggestion, it means the UEFI Boot Manager needs to be > configured (see

Re: 24.3. Updating Bootcode

> On 16. Aug 2022, at 12:49, Nuno Teixeira wrote: > > Hello all, > > With so much discussion about updating boot, I feel confused about the > correct procedure of doing it. > > Like being said there are a "24.3. Updating Bootcode" in Handbook (WIP) that > points to some important manuals.

Re: ZFS: cannot import zroot: I/O error

> On 15. Aug 2022, at 18:01, FreeBSD User wrote: > > Hello, > > I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox > 4.1.24/26 (do not know > exactly). The host is a special system based on Linux und VirtualBox and I > have no chances to > configure the VBox. > >

Re: bootstrap loader crashes, BTX halted

> On 14. Aug 2022, at 23:08, Jens Schweikhardt > wrote: > > I just installed the latest current on a gpt zfs system and it crashes early > with (manually transferred from photo taken): > > Consoles: internal video/keyboard > BIOS drive C: is disk0 > BIOS 634kB/3090148kB available memory >

Re: Updating EFI boot loader results in boot hangup

ok, yes, there is something bad happening: https://paste.ec/paste/4p6Tf7Bl#yD6QIahJs1U1SRryaKUCqOHDdf5YDUfvB-wBvwAmhV4 second pointer is supposed to be pointer to device specific format function and on last visible

Re: RES: vt newcons 3 clicks mouse paste issue FIXED

> On 4. Aug 2022, at 17:04, Ivan Quitschal wrote: > > Hi Hans > > D36042 created > How can I include more patch files in the same defect number? D36042 > https://reviews.freebsd.org/D36042 > > Its missing the vt.h.diff and vt_core.diff > Both attached > > Should i have put all three in the

Re: Problem booting current

If you boot cd/usb, zpool import -N zroot, then zpool get all, post the output. Sent from my iPhone > On 1. Jun 2022, at 16:54, Filippo Moretti wrote: > >  > I installed CURRENT with memstick of May the 27th. > I tired first UEFI and all I got was a flashing - on screen > I then tried BIOS+

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

> On 30. May 2022, at 17:06, Warner Losh wrote: > > > > On Mon, May 30, 2022 at 4:26 AM David Wolfskill <mailto:da...@catwhisker.org>> wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issu

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

> On 30. May 2022, at 04:26, David Wolfskill wrote: > > On Sun, May 29, 2022 at 06:59:34PM -0600, Warner Losh wrote: >> Sorry for top posting... >> >> Did you upgrade your boot blocks? > > Thanks for the reply! > > Hmmm Well, every time I rebuild FreeBSD head, the last step > just

Re: Zpool with latest feature com.delpfix:head_errlog can not be booted from.

-1 pool, and no place to put another disk. > > Thanks for any help. > (If can email the replacement binary that would be wonderful). > > > On 05/20/2022 4:47 am, Toomas Soome wrote: >> I’ll see into it. It would be nice to have at least heads up message >> about such fea

Re: loader_4th.efi broke?

> On 20. May 2022, at 20:11, Bjoern A. Zeeb > wrote: > > On Fri, 20 May 2022, Toomas Soome wrote: > >>> On 20. May 2022, at 20:00, Bjoern A. Zeeb >>> wrote: >>> >>> Hi, >>> >>> something between >&

Re: loader_4th.efi broke?

> On 20. May 2022, at 20:00, Bjoern A. Zeeb > wrote: > > Hi, > > something between > 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and > 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3 > made loader_4th.efi go all > "failed to allocate staging area: 9" > > I am

Re: Zpool with latest feature com.delpfix:head_errlog can not be booted from.

I’ll see into it. It would be nice to have at least heads up message about such features, or zfs code does have means to block feature upgrade on boot pool. Rgds, Toomas > On 20. May 2022, at 11:39, Johan Hendriks wrote: > > I did upgrade my FreeBSD Current and with that i updated my

Re: "vidcontrol -i mode" shows no output except header (in search of smaller console font)

> On 28. Feb 2022, at 08:23, Michael Schuster wrote: > > Hi Toomas, > > > On Sun, Feb 27, 2022 at 10:54 PM Toomas Soome <mailto:tso...@me.com>> wrote: > > >> On 27. Feb 2022, at 23:36, Michael Schuster > <mailto:michaelspriv...@gmail.com>

Re: "vidcontrol -i mode" shows no output except header (in search of smaller console font)

> On 27. Feb 2022, at 23:36, Michael Schuster wrote: > > Hi all, > > I'm trying to get a smaller font in my text-consoles (using vt) on my Ryzen > 4700 and Vega10 Renoir - based laptop with a fresh install of FreeBSD CURRENT > from last week. > > My research led me to believe that using

Re: pxeboot binary is too big on FreeBSD (>640KBytes)

> On 21. Feb 2022, at 19:18, Simon J. Gerraty wrote: > > Toomas Soome wrote: >>> Why should pxeboot have ZFS support? >> >> Well, the feature X can be helpful for recovery purposes. The root >> cause is not the feature X itself, but the size limit. A

Re: pxeboot binary is too big on FreeBSD (>640KBytes)

> On 21. Feb 2022, at 09:43, Hans Petter Selasky wrote: > > FYI: > > After a lot of digging trying everything, I found that the pxeboot and > loader.efi was too big simply due to ZFS support. > > So I did this after buildworld: > > cd /usr/src/stand > make WITHOUT_LOADER_ZFS=YES clean >

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

Since it was booting before, does the old loader start? I see the iKVM windo does have record menu entry, can it be used to record whole incident? rgds, toomas > чт, 9 дек. 2021 г. в 18:19, Toomas Soome : > >> >> >>> On 9. Dec 2021, at 20:06, Sergey Dyatko wrote: >

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: compile failure in /usr/src/stand/libsa

> On 10. Sep 2021, at 13:53, Gary Jennejohn wrote: > > So, a new problem with buildworld in HEAD. > > Building in /usr/src/stand/libsa fails because dosfs.c, ufs.c and > geli/gelidev.c can't find disk.h. But disk.h is located in ../common. > > I had to modify all three of these files to get

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

switch to use better resolution. Toomas > > Toomas Soome escreveu no dia terça, 6/07/2021 à(s) 12:11: > >> >> >>>> On 6. Jul 2021, at 14:07, Nuno Teixeira wrote: >>> >>> I forgot to say that dmesg show vt resolution: >>> >>>

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

ive E: is disk2 > BIOS 639kB/3405336kB available memory > > FreeBSD/x86 bootstrap loader, Revision 1.1 > (Mon Feb 22 18:17:30 CET 2021 root@thor) > | > > VBE not available > > > > ... and its stuck forever ... > > What is wrong here? > > Thanks for

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

Re: boot loader blank screen

>>> >>>> On Fri, Jan 15, 2021 at 03:51:38PM +0200, Toomas Soome wrote: >>>>> Could you please check latest current now?:) >>>> Success! With main-c255999-g0bc776f3da70, I've been able to comment >> out >>>> the >>>&

Re: boot loader blank screen

> On 16. Jan 2021, at 14:40, Johan Hendriks wrote: >> > I just did an update to FreeBSD jhost002.thuis.local 13.0-ALPHA1 FreeBSD > 13.0-ALPHA1 #26 main-c256002-gfe258f23ef36: Sat Jan 16 12:25:49 CET 2021 > root@srv-01.thuis.local >

Re: boot loader blank screen

Could you please check latest current now?:) Thanks, Toomas > On 13. Jan 2021, at 20:13, Santiago Martinez wrote: > > Hi, +1 on this, i still have issue on a supermicro. > > Santi > >> On 1/8/21 8:11 PM, John Kennedy wrote: >>> On Wed, Jan 06, 2021 at 02:19:12PM -0800, John Kennedy wrote:

Re: boot loader blank screen

> On 5. Jan 2021, at 00:59, Toomas Soome wrote: > > > >> On 4. Jan 2021, at 18:30, Toomas Soome > <mailto:tso...@me.com>> wrote: >> >> >> >>> On 4. Jan 2021, at 18:22, John Kennedy >> <mailto:warl...@phouka.net>>

Re: boot loader blank screen

> On 4. Jan 2021, at 18:30, Toomas Soome wrote: > > > >> On 4. Jan 2021, at 18:22, John Kennedy wrote: >> >> This is a little weird. >> >> Somewhere between 13.0-g2ff66a915526 (Dec 30th) and -gd03fd8ede2c4 (Dec >> 29th), >> I've los

Re: boot loader blank screen

> On 4. Jan 2021, at 18:22, John Kennedy wrote: > > This is a little weird. > > Somewhere between 13.0-g2ff66a915526 (Dec 30th) and -gd03fd8ede2c4 (Dec 29th), > I've lost the screen in the boot loader. This is really weird because I > didn't update the boot loader (in quite a while,

Re: Blank ttyv0 on reboot after update from c255519-g8929690a6359 tp c255545-g82397d791966

> On 3. Jan 2021, at 14:33, David Wolfskill wrote: > > This is on my laptop. > > No clue yet -- I'll start looking at the changes once the rest of my > smoke-test is done, but it seemed to boot OK & switch to graphics mode > so I have some thing I can still use. > > Yesterday: > FreeBSD

Re: Terminal colours in current

> On 2. Jan 2021, at 07:25, Rozhuk Ivan wrote: > > Hi! > > I am tring current and found that kernel options: > options TERMINAL_NORM_ATTR = (FG_GREEN|BG_BLACK) # def to > SC_NORM_ATTR / 2 | 0x00 > options TERMINAL_KERN_ATTR = (FG_YELLOW|BG_BLACK) # def

Re: review request: loader: implement framebuffer console

der-implement-framebuffer-console.patch> (phab is also updated). thanks, toomas > On 14. Dec 2020, at 16:03, Jan Beich wrote: > > Jan Beich writes: > >> Toomas Soome writes: >> >>> hi! >>> >>> I have been working on proper framebuffer sup

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

> On 19. Dec 2020, at 23:21, Graham Perrin wrote: > > With VirtualBox on an r368589 host I installed the latest (17th December) > snapshot of 13.0-CURRENT in a guest machine. I set the guest to EFI before > installation, and chose GPT (UEFI) during installation. > > After installing KDE

Re: review request: loader: implement framebuffer console

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, Toom

review request: loader: implement framebuffer console

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

Re: uefi(8) fails to boot from ZFS with compression=zstd

Does it boot when you copy loader.efi to bootx64.efi? Toomas > On 23. Oct 2020, at 05:02, Jan Beich wrote: > > After r366657 (currently, on r366953) I've tried to boot from a > compression=zstd dataset but it failed to reach loader(8), see below. > However, switching to CSM path (boot1.efi

Re: Zpool doesn't boot anymore after FreeBSD 12.1

> On 22. Oct 2020, at 23:29, Cassiano Peixoto wrote: > > > Hi Toomas, > > Thank you for this patch. Can I know when it will be MFCed? I'd like to try. MFC will take a bit because I need to bring it together with asize updates, so we would need to do a bit of cherry-picking and testing.

Re: Zpool doesn't boot anymore after FreeBSD 12.1

Hi! Please try 366951:) I think, it should get things better for you. rgds, toomas > On 22. Oct 2020, at 20:37, Sergey V. Dyatko wrote: > > On Thu, 22 Oct 2020 16:42:16 +0300 > Andriy Gapon wrote: > >> On 22/10/2020 16:39, Cassiano Peixoto wrote: >>> Hi Andriy, >>> >>> I've just tried

Re: Zpool doesn't boot anymore after FreeBSD 12.1

> On 22. Oct 2020, at 16:42, Andriy Gapon wrote: > > On 22/10/2020 16:39, Cassiano Peixoto wrote: >> Hi Andriy, >> >> I've just tried copying my zfsloader from 11.2-STABLE (R350026) to FreeBSD >> 12.1 >> and 12.2 (STABLE) and fixed the issue. >> >> I also tried to use zfsloader of 11.3 but

Re: Zpool doesn't boot anymore after FreeBSD 12.1

There are few issues. with vmware, you should rather grow existing boot disk - just to keep setup simple. If you are adding disks, make sure they are properly partitioned. int13 error code 4 should be ’sector not found’, I have no idea why are you getting this one, but clearly there is

Re: Freeze during early boot

> On 10. Sep 2020, at 03:57, Mason Loring Bliss wrote: > > Hi, all. I'd like to see FreeBSD running on a new class of box I've got > here. Not new hardware. These are Atom chips on Micro-ITX motherboards, and > are interesting in that they are low-power and have dual gigabit NICs. > They're

Re: OpenZFS support merged

> On 25. Aug 2020, at 22:49, driesm.michi...@gmail.com wrote: > >> -Original Message- >> From: owner-freebsd...@freebsd.org On >> Behalf Of Matthew Macy >> Sent: Tuesday, 25 August 2020 04:39 >> To: freebsd-current ; freebsd-fs > f...@freebsd.org>; freebsd-hack...@freebsd.org >>

Re: OpenZFS support merged

> On 25. Aug 2020, at 19:35, Danilo Egêa Gondolfo wrote: > > On Tue, Aug 25, 2020 at 3:39 AM Matthew Macy wrote: > >> r364746 merged OpenZFS support in to HEAD. >> >> The change should be transparent unless you want to use new features. >> I caution against 'zpool upgrade' for the next few

Re: Geli encryption issue on r362779

> On 10. Jul 2020, at 18:05, Thomas Laus wrote: > >> On 2020-07-10 03:56, Toomas Soome wrote: >>> >>> ok, then next one is r363042. By nature it is an safeguard against read >>> past disk end. >>> >>> If that does not do, we really nee

Re: Boot failure on refreshed Dell Precision 7550

> On 10. Jul 2020, at 16:43, Shawn Webb wrote: > > On Fri, Jul 10, 2020 at 04:36:41PM +0300, Toomas Soome wrote: >> >> >>> On 10. Jul 2020, at 16:25, Shawn Webb wrote: >>> >>> Hey all, >>> >>> I just got in a new Dell Pr

Re: Boot failure on refreshed Dell Precision 7550

> On 10. Jul 2020, at 16:25, Shawn Webb wrote: > > Hey all, > > I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD > on it and UEFI boot failed. The screen goes black immedately when > selecting the memstick and around ten to twenty seconds later, the > system reboots. >

Re: Geli encryption issue on r362779

> On 7. Jul 2020, at 19:18, Thomas Laus wrote: > > On 2020-07-07 08:26, Toomas Soome wrote: >> Hi! >> >> I believe, 362989 should fix your issue. Please do let me know. >> > I updated to r362989. I built world and kernel after clearing out >

Re: Geli encryption issue on r362779

Hi! I believe, 362989 should fix your issue. Please do let me know. thanks, toomas > On 30. Jun 2020, at 20:19, Thomas Laus wrote: > > On 2020-06-30 11:31, Toomas Soome wrote: >> >> hi! >> >> 362431: https://svnweb.freebsd.org/base?view=revision=362431 >&

Re: Geli encryption issue on r362779

> On 30. Jun 2020, at 20:19, Thomas Laus wrote: > > On 2020-06-30 11:31, Toomas Soome wrote: >> >> hi! >> >> 362431: https://svnweb.freebsd.org/base?view=revision=362431 >> >> The majority of the code is now shared with loader (libsa/libi386),

Re: Geli encryption issue on r362779

> On 30. Jun 2020, at 15:01, Thomas Laus wrote: > > This is a repost to this list because of my submission email address did > not match the one on record. > > == > List: > > I just upgraded a couple of computers from r362220 to r362779 and have > booting

Re: Why is the console a graphic/bitmapped console, and not text/character by default

> On 12. Apr 2020, at 08:34, Chris wrote: > > On Sun, 12 Apr 2020 08:04:43 +0300 Toomas Soome tso...@me.com > <mailto:tso...@me.com> said > >> You have UEFI setup? With UEFI, there is no text mode. >> If mouse copy/paste is working is not a property of scr

Re: Why is the console a graphic/bitmapped console, and not text/character by default

You have UEFI setup? With UEFI, there is no text mode. If mouse copy/paste is working is not a property of screen mode but it if the console driver does implement it or not. Sent from my iPhone > On 12. Apr 2020, at 07:41, Chris wrote: > > Sorry for the ling title. But wasn't sure how make

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

> On 28. Mar 2020, at 05:28, Chris wrote: > > On Fri, 27 Mar 2020 18:31:50 -0700 bsd-li...@bsdforge.com > said > >> On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh i...@bsdimp.com said >> > On Fri, Mar 27, 2020 at 4:54 PM Chris wrote: >> > > > On Sat, 28 Mar

Re: head -r538966 on OrangePi+ 2ed: boot loader crashes when USB drive is present at power-on/boot: its a misaligned access by code from -r354746

I think this should fix it. We need to create copy of dos partition array, so we will get proper alignment. tsoome@freebsd-2:/usr/src % svn diff stand/common/part.c Index: stand/common/part.c === --- stand/common/part.c (revision

Re: what 3rd party boot mgr is required to boot multiple freebsd versions?

> On 17. Mar 2020, at 15:51, Matthew Seaman wrote: > > On 17/03/2020 12:58, Florian Limberger wrote: >> On 16.03.20 23:33, Chris wrote: >> >>> For the record. I'm *only* using FreeBSD in this situation. I >>> only mentioned Windows above, for the use of it's boot manager. >> >> If you only

about loader & console

Hi! I have been busy with other bits for some time, but now back to poking some bits. What we have now (on current): x86: vidconsole on BIOS systems. Text mode, the screen is managed by teken terminal emulator, we “draw” on vga text buffer. comconsole: serial port driver shared by BIOS and

Re: current does not boot on vmware fusion 11

> On 15. Feb 2020, at 22:19, Alexander V. Chernikov wrote: > > Hi folks, > > I upgraded vmware fusion to version 11 recently and noticed that my -amd64 VM > stops booting immediately after printing EFI framebuffer information. > > VM pops up a message stating that "The firmware encountered

Re: r351900 broke UEFI boot on VMware VMs

> On 14. Feb 2020, at 13:43, Yuri Pankov wrote: > > Hi Toomas, > > I was finally able to find the revision that has broken UEFI boot on VMware > VMs, that is ESXi 6.7 and Workstation 15.x, for me at least -- VM simply > powers off (sometimes with uninformative message about runtime

Re: Panic in gptzfsboot?

Fixed, sorry about the mess:) thanks, toomas > On 5. Feb 2020, at 12:30, Toomas Soome wrote: > > > >> On 5. Feb 2020, at 12:05, Stefan Eßer wrote: >> >> Am 05.02.20 um 10:14 schrieb Toomas Soome: >>>> On 5. Feb 2020, at 11:12, Stefan Eßer >>

Re: Panic in gptzfsboot?

> On 5. Feb 2020, at 12:05, Stefan Eßer wrote: > > Am 05.02.20 um 10:14 schrieb Toomas Soome: >>> On 5. Feb 2020, at 11:12, Stefan Eßer >> <mailto:s...@freebsd.org>> wrote: >>> >>> I have just re-built world and kernel and get a boot fail

Re: Panic in gptzfsboot?

> On 5. Feb 2020, at 11:12, Stefan Eßer wrote: > > I have just re-built world and kernel and get a boot failure: > > panic: free: guard2 fail @ 0x412f6c50 + 513 from unknown:0 > --> Press a key in the console to reboot <-- > > I'll try to boot from a memory stick, now, but wanted to let >

  1   2   3   >