Re: Updating build and jail manual pages to include missing or obscure information

shouldn't be used in the jail instructions. But it also has more functionality than buildworld + installworld because it has logic for optionally making pre-world and post-world targets. Options I see are:   * Declare the 'world' target deprecated only for updating, but fine for

Re: Updating build and jail manual pages to include missing or obscure information

shouldn't be used in the jail instructions. But it also has more functionality than buildworld + installworld because it has logic for optionally making pre-world and post-world targets. Options I see are:   * Declare the 'world' target deprecated only for updating, but fine for

Re: Updating build and jail manual pages to include missing or obscure information

resin-free...@g-cipher.net: > On 5/22/25 09:16, Lexi Winter wrote: > > note that 'make world' already doesn't work unless you're using DESTDIR > > (or you set a special make knob) so it shouldn't be documented as a way > > of upgrading the system in general, e.g. in build(7). > Just to share my tw

Re: Updating build and jail manual pages to include missing or obscure information

erence document, so it's there to give a complete view of the interface.  Instructions on anything other than the simplest use cases should be out of scope.  Long-form how-to articles are what the handbook is for.  A README file (i.e. UPDATING) is good as a quick start, but shouldn't be complete reference or point of truth.

Re: Updating build and jail manual pages to include missing or obscure information

ing mistakes. So a whlie back (2013 or so, from revision history), I took the instructions from UPDATING under "To rebuild everything and install it on the current system" and implemnted them as a set of (csh) aliases ... after adding a bit of local "seasoning." So now I use "_b

Re: Updating build and jail manual pages to include missing or obscure information

On Thu, May 22, 2025 at 07:56:38AM -0600, Warner Losh wrote: I object to removing these. I do agree we should document other methods, but my spidt sense is this is still in use... I object also. `make kernel` is useful if only for that by using it, one doesn't need to type `make buildkernel &&

Re: Updating build and jail manual pages to include missing or obscure information

Warner Losh: > On Thu, May 22, 2025, 7:40 AM Alexander Ziaee wrote: > > There seems to be a rough consensus that we should remove the world and > > kernel targets. > > I object to removing these. I do agree we should document other methods, > but my spidt sense is this is still in use... note th

Re: Updating build and jail manual pages to include missing or obscure information

olely > >> on the information available. After some discussion on the forum it was > >> discovered that the answer was in fact in the jail(8) manual, under the > >> Examples section. However, the make targets listed in the jail(8) > >> manual are not documen

Re: Updating build and jail manual pages to include missing or obscure information

that the answer was in fact in the jail(8) manual, under the >> Examples section.  However, the make targets listed in the jail(8) >> manual are not documented in the build(7) manual.   I'd like to open a >> discussion around updating the documentation to make the corr

Re: Updating build and jail manual pages to include missing or obscure information

argets listed in the jail(8) > manual are not documented in the build(7) manual.   I'd like to open a > discussion around updating the documentation to make the correct > information easier to find.  Specifically: > >   * Should the 'world' and 'distribution'

Re: HEADS UP: iwlwifi firmware removed from main (stable/14 to follow), run fwget before updating

On Thu, 10 Apr 2025, Bjoern A. Zeeb wrote: Hi, and the firmware is now also gone from stable/14 (which at the same time got a few bug fixes for LinuxKPI malloc and LinuxKPI 802.11). In case you run into any issues updating from a supported 14.x or 15 (younger than a year old [3]) please follow

HEADS UP: iwlwifi firmware removed from main (stable/14 to follow), run fwget before updating

On Wed, 19 Mar 2025, Bjoern A. Zeeb wrote: Hi, before updating your system please run fwget(8) or build wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you are using iwlwifi(4) or iwx(4). You can do it any time as the extra firmware files will do no harm until your next

Re: No working interface bce0 after updating to CURRENT of March 1

I've had since ages these two lines in /etc/rc.conf: ifconfig_bce0="inet 192.168.178.5 netmask 255.255.255.0" ifconfig_bce1="inet 192.168.178.6 netmask 255.255.255.0" defaultrouter="192.168.178.1" The box has two RJ-45 ports and the only used one was the first, bce0. I changed the lines now to

Re: No working interface bce0 after updating to CURRENT of March 1

I had a wild guess and plug'ed in the RJ-45 into the server's 2nd port, modified /etc/rc.conf, booted and all was fine: $ ssh 192.168.178.5 $ uname -a FreeBSD jet 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n275738-7ee310c80ea7: Sun Mar 2 01:13:00 CET 2025 guru@jet:/usr/obj/usr/src/amd64.am

Re: No working interface bce0 after updating to CURRENT of March 1

Hi You wrote : -- # netstat -rn Routing tables Internet: DestinationGatewayFlags Netif Expire default192.168.178.1 UGS*bce0* 127.0.0.1 link#3 UH lo0 192.168.178.0/24 link#2

No working interface bce0 after updating to CURRENT of March 1

Hello, Last night I updated a server from a 14.0-CURRENT amd64 1400094 #2 main-n264568-1d7ffb373c9d-dirty: Wed Sep 6 07:13:22 CEST 2023 to the CURRENT of March 1, 2025. All went fine. # git clone https://git.freebsd.org/src.git /usr/src # cd /usr/src # make -j8 buildworld ... --- buildworld

Re: pkg scripts need updating

Am 15.05.24 um 02:21 schrieb Enji Cooper: On May 14, 2024, at 7:19 AM, Michael Butler wrote: After commit aa48259f337100e79933d660fec8856371f761ed to src which removed security_daily_compat_var, I get these warnings daily.. aaron.protected-networks.net login failures: aaron.protected-ne

Re: pkg scripts need updating

> On May 14, 2024, at 7:19 AM, Michael Butler > wrote: > > After commit aa48259f337100e79933d660fec8856371f761ed to src which removed > security_daily_compat_var, I get these warnings daily.. > > aaron.protected-networks.net login failures: > > aaron.protected-networks.net refused connection

pkg scripts need updating

After commit aa48259f337100e79933d660fec8856371f761ed to src which removed security_daily_compat_var, I get these warnings daily.. aaron.protected-networks.net login failures: aaron.protected-networks.net refused connections: /usr/local/etc/periodic/security/405.pkg-base-audit: security_daily_

Re: problem updating to CURRENT from source

Gary Jennejohn asks: Did you do a clean build? This isn't mentioned in the "To rebuild everything" text, but since you're building a different branch I suspect that a clean build would be necessary. Define "clean build". The script for rebuilding world has both "make cleanworld" and

Re: problem updating to CURRENT from source

On Tue, 28 Nov 2023 12:01:47 -0500 Robert Huff wrote: > Hello: > I am trying to update a system running "14.0 CURRENT #0" to last > night's Current using source. > I read the RELNOTES; I read the directions in UPDATING under "To > rebuild everyt

problem updating to CURRENT from source

Hello: I am trying to update a system running "14.0 CURRENT #0" to last night's Current using source. I read the RELNOTES; I read the directions in UPDATING under "To rebuild everything". I built world; built kernel; installed kernel; rebooted single us

Re: Updating motherboard BIOS without MS Windows

From: Nuno Teixeira Subject: Updating motherboard BIOS without MS Windows Date: Sat, 11 Nov 2023 10:56:58 + > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? >

Re: Updating motherboard BIOS without MS Windows

s license and I'm looking for > brands that have bios-cli that work in FreeBSD. > > Thanks, > I've used a few different mainboards (Asus, Gigabyte) and I've never used Windows to update the BIOS. Most BIOSes allow updating from 1) a thumb drive with DOS (FreeDOS) installed

Re: Updating motherboard BIOS without MS Windows

Hi! > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for > brands that have bios-cli that work in FreeBSD. There's sysutils/flashrom which allows to flash some BIOS systems. Th

Re: Updating motherboard BIOS without MS Windows

Hi, > On 11 Nov 2023, at 10:56, Nuno Teixeira wrote: > > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for bra

Re: Updating motherboard BIOS without MS Windows

On Saturday, November 11th, 2023 at 11:56, Nuno Teixeira wrote: > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking

Re: Updating motherboard BIOS without MS Windows

On 11/11/23 11:56, Nuno Teixeira wrote: Hello all, Maybe not the best mailing to ask it but... How do you update BIOS without Windows since most brands only have bios software to windows? I'm about to buy a new pc without windows license and I'm looking for brands that have bios-cli that wo

Updating motherboard BIOS without MS Windows

Hello all, Maybe not the best mailing to ask it but... How do you update BIOS without Windows since most brands only have bios software to windows? I'm about to buy a new pc without windows license and I'm looking for brands that have bios-cli that work in FreeBSD. Thanks, -- Nuno Teixeira Fr

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

On Sat, Jul 22, 2023 at 1:21 AM Yasuhiro Kimura wrote: > > From: Kevin Bowling > Subject: Re: Kernel panic after updating 14-CURRENT amd64 to > main-n264268-ff4633d9f89 > Date: Fri, 21 Jul 2023 21:44:13 -0700 > > > Thanks, I have reverted for now. Can you tell me whic

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

From: Kevin Bowling Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Fri, 21 Jul 2023 21:44:13 -0700 > Thanks, I have reverted for now. Can you tell me which NIC is > implemented there? Output of `pciconf -lv` says as following. em0@pci0

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

Thanks, I have reverted for now. Can you tell me which NIC is implemented there? On Fri, Jul 21, 2023 at 12:45 PM Yasuhiro Kimura wrote: > > From: Yasuhiro Kimura > Subject: Kernel panic after updating 14-CURRENT amd64 to > main-n264268-ff4633d9f89 > Date: Sat, 22 Jul 2023 02:5

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

From: Yasuhiro Kimura Subject: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST) > After updating my 14.0-CURRENT amd64 system from > main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes > with panic as

Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

After updating my 14.0-CURRENT amd64 system from main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes with panic as following. https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-main-n264268-ff4633d9f89.20230721.panic.png --- Yasuhiro Kimura

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

> On Jul 10, 2023, at 3:27 PM, Mark Millard wrote: > > On Jul 10, 2023, at 15:03, Mark Millard > wrote: > >> On Jul 10, 2023, at 11:42, The Doctor wrote: >> >>> On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: The subject line's question was prompt

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On Jul 10, 2023, at 15:03, Mark Millard wrote: > On Jul 10, 2023, at 11:42, The Doctor wrote: > >> On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: >>> The subject line's question was prompted by >>> . . ./hazmat/bindings/_openssl.abi3.so related notices >>> in a kyua report: >>>

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On Jul 10, 2023, at 11:42, The Doctor wrote: > On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: >> The subject line's question was prompted by >> . . ./hazmat/bindings/_openssl.abi3.so related notices >> in a kyua report: >> >> # kyua report --verbose >> --results-file=usr_obj_DEST

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: > The subject line's question was prompted by > . . ./hazmat/bindings/_openssl.abi3.so related notices > in a kyua report: > > # kyua report --verbose > --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785 >

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On Jul 10, 2023, at 10:55, Mark Millard wrote: > On Jul 10, 2023, at 09:45, Mike Karels wrote: > >> On 10 Jul 2023, at 10:56, Mark Millard wrote: >> >>> The subject line's question was prompted by >>> . . ./hazmat/bindings/_openssl.abi3.so related notices >>> in a kyua report: >>> >>> # kyua

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On Jul 10, 2023, at 09:45, Mike Karels wrote: > On 10 Jul 2023, at 10:56, Mark Millard wrote: > >> The subject line's question was prompted by >> . . ./hazmat/bindings/_openssl.abi3.so related notices >> in a kyua report: >> >> # kyua report --verbose >> --results-file=usr_obj_DESTDIRs_main-CA

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

On 10 Jul 2023, at 10:56, Mark Millard wrote: > The subject line's question was prompted by > . . ./hazmat/bindings/_openssl.abi3.so related notices > in a kyua report: > > # kyua report --verbose > --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785 > 2>&1 | grep "U

Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

The subject line's question was prompted by . . ./hazmat/bindings/_openssl.abi3.so related notices in a kyua report: # kyua report --verbose --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785 2>&1 | grep "Undefined symbol" | sort -u +ImportError: /usr/obj/DESTDIRs/

Re: Updating EFI boot loader results in boot hangup

On 8/nn/22, yet top-posted: > [snip] https://www.idallen.com/topposting.html

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Re: Updating EFI boot loader results in boot hangup Date: Tue, 16 Aug 2022 12:01:42 +0900 (JST) >>> I made regular update of my 14-CURRENT amd64 system from >>> main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated >>> EFI

Re: Updating EFI boot loader results in boot hangup

On Wed, 17 Aug 2022 07:55:32 +0900 Tomoaki AOKI wrote: > On Mon, 15 Aug 2022 21:35:52 -0600 > Warner Losh wrote: > > > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader res

Re: 24.3. Updating Bootcode

@ main-n257521-97be6fced7db Clean boot without warnings. OK. Thanks, Nuno Teixeira escreveu no dia quinta, 18/08/2022 à(s) 12:04: > Forgot to send a screenshot > for > loader.efi @ main-n257458-ef8b872301c5 > ( +Boot0007* FreeBSD-1

Re: Updating EFI boot loader results in boot hangup

On Thu, Aug 18, 2022, 12:19 AM Simon J. Gerraty wrote: > Warner Losh wrote: > > I think I broke it with my latest updates. I don't have a good ZFS > testing setup > > so I'm spending a little time enhancing the bootable image generator to > have > > one that I can easily test boot with qemu. > >

Re: 24.3. Updating Bootcode

Forgot to send a screenshot for loader.efi @ main-n257458-ef8b872301c5 ( +Boot0007* FreeBSD-14 HD(1,GPT,73acd1b2-de41-11eb-8156-002b67dfc673,0x28,0x82000)/File(\efi\freebsd\loader.efi) nvd0p1:/efi/freebsd/loader

Re: Updating EFI boot loader results in boot hangup

Warner Losh wrote: > I think I broke it with my latest updates. I don't have a good ZFS testing > setup > so I'm spending a little time enhancing the bootable image generator to have > one that I can easily test boot with qemu. FWIW bhyve is *excellent* for mucking about with EFI and loader in g

Re: 24.3. Updating Bootcode

*** and "EFI Hard Drive"(legacy /efi/boot/bootx64.efi) from BIOS. Nuno Teixeira escreveu no dia quarta, 17/08/2022 à(s) 19:14: > Hi, > > And it's done: > --- > Boot0007* FreeBSD-14 > HD(1,GPT,73acd1b2-de41-11eb-8156-002b67d

Re: 24.3. Updating Bootcode

Hi, And it's done: --- Boot0007* FreeBSD-14 HD(1,GPT,73acd1b2-de41-11eb-8156-002b67dfc673,0x28,0x82000)/File(\efi\freebsd\loader.efi) nvd0p1:/efi/freebsd/loader.efi /boot/efi//efi/freebsd/loader.efi +Boot0006* FreeBSD-14_old HD(1,GPT,73acd1b2-de41-11eb-8156-002b67dfc673,0

Re: Updating EFI boot loader results in boot hangup

Hi all, > Am 17.08.2022 um 13:48 schrieb Idwer Vollering : > > $ sudo camcontrol devlist > at scbus0 target 0 lun 0 (pass0,ada0) > at scbus1 target 0 lun 0 (pass1,ada1) > > $ gpart show ada0 ada1 > =>40 1953525088 ada0 GPT (932G) > 401024 1 f

Re: Updating EFI boot loader results in boot hangup

n, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader results in boot hangup > > > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > > > > > > > From: Yasuhiro Kimura > > &g

Re: Updating EFI boot loader results in boot hangup

On Wed, 17 Aug 2022 07:55:32 +0900, Tomoaki AOKI wrote: > On Mon, 15 Aug 2022 21:35:52 -0600 > Warner Losh wrote: > > > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader

Re: Updating EFI boot loader results in boot hangup

On Mon, 15 Aug 2022 21:35:52 -0600 Warner Losh wrote: > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > From: Yasuhiro Kimura > > Subject: Re: Updating EFI boot loader results in boot hangup > > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > &g

Re: 24.3. Updating Bootcode

On Tue, Aug 16, 2022 at 6:01 AM 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 ef

Re: 24.3. Updating Bootcode

On Tue, Aug 16, 2022 at 3:49 AM 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 p

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 ef

Re: 24.3. Updating Bootcode

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 efibootmgr(8)). > > Therefore, once you have set up OS specific setu

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

24.3. Updating Bootcode

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. There are 3 places where boot loader are: ESP (EFI System

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Mon, 15 Aug 2022 21:35:52 -0600 > Would you be able to share camcontrol devlist output? Privately if > need be. root@rolling-vm-freebsd1[1001]# camcontrol devlist at scbus0 target 0 lun 0

Re: Updating EFI boot loader results in boot hangup

On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > From: Yasuhiro Kimura > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > > > From: Yasuhiro Kimura > > Subject: Updating EFI boot loader results in boot

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Re: Updating EFI boot loader results in boot hangup Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > From: Yasuhiro Kimura > Subject: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > >> I made regul

Re: bootx64.efi; and loader.efi in the FreeBSD reserved area (was: Updating EFI boot loader results in boot hangup)

On Sun, Aug 14, 2022 at 7:52 AM Graham Perrin wrote: > On 12/08/2022 17:54, Yasuhiro Kimura wrote: > > … amd64 … (/boot/efi/efi/freebsd/loader.efi) … > > Side note: please, why the FreeBSD reserved area? > When you create a boot variable using efibootmgr, it's better to specify something that's

Re: Updating EFI boot loader results in boot hangup

Isn't better just to mount -t msdos /dev/xxxpn /mnt and cp /boot/loader.efi /mnt/efi/boot/bootx64.efi? Pete Wright escreveu no dia domingo, 14/08/2022 à(s) 22:58: > > > On 8/14/22 13:26, Graham Perrin wrote: > > On 14/08/2022 20:26, Pete Wright wrote: > > … has anyone else who has been impacted

Re: Updating EFI boot loader results in boot hangup

On 8/14/22 13:26, Graham Perrin wrote: On 14/08/2022 20:26, Pete Wright wrote: … has anyone else who has been impacted by this been able to recover? … If you have multiple boot environments: do you have a non-affected BE (prior to c32dde3166922f55927764464d13f1bc9640f5f6)? So unfortunately

Re: Updating EFI boot loader results in boot hangup

On 14/08/2022 20:26, Pete Wright wrote: … has anyone else who has been impacted by this been able to recover? … If you have multiple boot environments: do you have a non-affected BE (prior to c32dde3166922f55927764464d13f1bc9640f5f6)?

Re: Updating EFI boot loader results in boot hangup

On Sun, Aug 14, 2022 at 1:26 PM Pete Wright wrote: > On Sun, Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote: > > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: > > > Yes, Yasuhiro and I have the same error. > > > > Just a "me too", also on ZFS, on a Ryzen 3 based system. > > > > Booting the lat

Re: Updating EFI boot loader results in boot hangup

On Sun, Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote: > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: > > Yes, Yasuhiro and I have the same error. > > Just a "me too", also on ZFS, on a Ryzen 3 based system. > > Booting the latest USB snapshot image worked, but not when I copy > the whole of

bootx64.efi; and loader.efi in the FreeBSD reserved area (was: Updating EFI boot loader results in boot hangup)

On 12/08/2022 17:54, Yasuhiro Kimura wrote: … amd64 … (/boot/efi/efi/freebsd/loader.efi) … Side note: please, why the FreeBSD reserved area? I'm more familiar with /efi/boot/bootx64.efi for amd64.

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 li

Re: Updating EFI boot loader results in boot hangup

Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: Yes, Yasuhiro and I have the same error. Just a "me too", also on ZFS, on a Ryzen 3 based system. Booting the latest USB snapshot image worked, but not when I copy the whole of /boot from that USB stick to my ZFS boot partition. The system is usable

Re: Updating EFI boot loader results in boot hangup

Yes, Yasuhiro and I have the same error. On Sat, Aug 13, 2022, 10:09 PM Yasuhiro Kimura wrote: > From: Warner Losh > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 20:01:03 -0600 > > > UFS or ZFS? > > > > Warner > >

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 20:01:03 -0600 > UFS or ZFS? > > Warner ZFS in my case. --- Yasuhiro Kimura

Re: Updating EFI boot loader results in boot hangup

at precedes it > https://cgit.freebsd.org/src/commit/?id=ad759c73522efb606135e2891ac03864926b80a3 > causes a different kind of error. > > On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura wrote: > >> From: Oleg Lelchuk >> Subject: Re: Updating EFI boot loader results in bo

Re: Updating EFI boot loader results in boot hangup

b80a3 causes a different kind of error. On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura wrote: > From: Oleg Lelchuk > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 20:28:09 -0400 > > > I can

Re: Updating EFI boot loader results in boot hangup

From: Oleg Lelchuk Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 20:28:09 -0400 > I can already see that commit > > c32dde3166922f55927764464d13f1bc9640f5f6 causes breakage, but the commit that > precedes it > > f197c0bf3e075286ccea32

Re: Updating EFI boot loader results in boot hangup

et another commit caused a different kind of breakage again. On Sat, Aug 13, 2022 at 7:41 PM Yasuhiro Kimura wrote: > From: Oleg Lelchuk > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 19:32:16 -0400 > > > You can do make and make insta

Re: Updating EFI boot loader results in boot hangup

From: Oleg Lelchuk Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 19:32:16 -0400 > You can do make and make install in /usr/src/stand Thanks for letting me know. I'll try it. --- Yasuhiro Kimura

Re: Updating EFI boot loader results in boot hangup

You can do make and make install in /usr/src/stand On Sat, Aug 13, 2022 at 7:31 PM Yasuhiro Kimura wrote: > From: Warner Losh > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 16:59:55 -0600 > > > Any chance of a bisect of which revis

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 16:59:55 -0600 > Any chance of a bisect of which revision starts to fail? > > Warner I'll try it. Is it possbile to build only loader.efi without doing buildworld? I'd

Re: Updating EFI boot loader results in boot hangup

Any chance of a bisect of which revision starts to fail? Warner On Sat, Aug 13, 2022 at 4:49 PM Oleg Lelchuk wrote: > I experienced the same problem. I hope this bug will be fixed soon. > > On Sat, Aug 13, 2022 at 5:36 PM Yasuhiro Kimura wrote: > >> From: Yasuhiro Kimura &g

Re: Updating EFI boot loader results in boot hangup

I experienced the same problem. I hope this bug will be fixed soon. On Sat, Aug 13, 2022 at 5:36 PM Yasuhiro Kimura wrote: > From: Yasuhiro Kimura > Subject: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > > > I made regul

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > I made regular update of my 14-CURRENT amd64 system from > main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated > EFI boot loader (/boot/efi/ef

Re: Updating EFI boot loader results in boot hangup

On Sat, Aug 13, 2022 at 9:37 AM Nuno Teixeira wrote: > Hi Larry, > > boot off a memstick? >> > Yes, that's it. > With it we can mount efi partition and use bkp efi file by renaming it. > Yup. > I forgot that efi boot is restricted to use bootx64.efi (amd64) and my > though was looking for a co

Re: Updating EFI boot loader results in boot hangup

Hi Larry, boot off a memstick? > Yes, that's it. With it we can mount efi partition and use bkp efi file by renaming it. I forgot that efi boot is restricted to use bootx64.efi (amd64) and my though was looking for a command to load bootx64.efi.old avoiding use of a memstick (e.g.). I've tested i

Re: Updating EFI boot loader results in boot hangup

ike: > > --- > > mount -t msdosfs /dev/nvd0p1 /mnt > > cp /mnt/efi/boot/bootx64.efi /mnt/efi/boot/bootx64.old > > cp /boot/loader.efi /mnt/efi/boot/bootx64.efi > > --- > > > > I can't find the right docs to load bootx64.old. > > Could you tell me w

Re: Updating EFI boot loader results in boot hangup

From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 21:03:02 +0100 > I'm searching without success to load a bkp loader in case of boot failure. > > Upgrade process willl be like: > --- > mount -t msdosfs /dev/nvd0p1 /mn

Re: Updating EFI boot loader results in boot hangup

escreveu no dia sexta, 12/08/2022 à(s) 18:45: From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? No, you need not. The only time that I upda

Re: Updating EFI boot loader results in boot hangup

t; > Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) > 18:45: > > From: Nuno Teixeira > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Fri, 12 Aug 2022 18:26:11 +0100 > > > Hello Yasu, > > > > Does it needes to update boot loader e

updating of prebuilt packages with pkg

cking this down on a system that does have /usr/ports installed I could find in /usr/ports/UPDATING that in my example the default version of python had been upgraded, see entry 20220626: AFFECTS: users of python [...] For users of pre-build packages: # sh # for i in $(pkg query -g %n 'py3

Re: Updating EFI boot loader results in boot hangup

5: From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? No, you need not. The only time that I updated was a month ago because of zfs upgr

Re: Updating EFI boot loader results in boot hangup

ad bootx64.old. Could you tell me what you did to solve your boot? Thanks Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) 18:45: > From: Nuno Teixeira > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Fri, 12 Aug 2022 18:26:11 +0100 > > > Hello Yas

Re: Updating EFI boot loader results in boot hangup

From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 > Hello Yasu, > > Does it needes to update boot loader everytime that we upgrade current? No, you need not. > The only time that I updated was a month ago be

Re: Updating EFI boot loader results in boot hangup

Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? The only time that I updated was a month ago because of zfs upgrade and I need to practice how to boot loader bkp file :) Cheers, Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) 17:56: > Hello, > > I ma

Updating EFI boot loader results in boot hangup

Hello, I made regular update of my 14-CURRENT amd64 system from main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated EFI boot loader (/boot/efi/efi/freebsd/loader.efi) but it results in boot hangup as following. https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-20220813-bo

Re: After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

On 2021-Oct-12, at 01:43, Hans Petter Selasky wrote: > On 10/12/21 3:11 AM, Mark Millard via freebsd-arm wrote: >> There is this "mixer" oddity for each boot: >> Feeding entropy: . >> mixer: 75:75: no such device >> mixer: 75:75: no such device >> mixer: 75:75: no such device >> mixer: 25:25:

Re: After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

On 10/12/21 3:11 AM, Mark Millard via freebsd-arm wrote: There is this "mixer" oddity for each boot: Feeding entropy: . mixer: 75:75: no such device mixer: 75:75: no such device mixer: 75:75: no such device mixer: 25:25: no such device mixer: 75:75: no such device mixer: 75:75: no such device mi

After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

I did not even get a chance to finish typing a command after login for the fist boot after updating: Fatal kernel mode data abort: 'Translation Fault (L2)' on read trapframe: 0xe18d6998 FSR=0007, FAR=fff4, spsr=a013 r0 =0001, r1 =, r2 =, r3 = r4

  1   2   3   4   5   6   7   >