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 /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 what you did to solve your boot? > > Thanks I use VirturalBox to run 14-CURRENT system. UEFI BIOS of VirtualBox provides a way to select loader file and boot from it. So I take following steps when updating loader file. 1. cd /boot/efi/efi/freebsd 2. mv loader.efi loader.backup.efi 3. cp -a /boot/loader.efi . And when boot from new loader file fails, I enter UEFI BIOS, select loader.backup.efi and boot from it. As you can see, above way depends on the feature of VirturalBox. So it depends on your hardware whether or not you can adopt it. As Larry pointed out, surest way is to boot from install media such as memstick or cdrom. --- Yasuhiro Kimura
Re: Updating EFI boot loader results in boot hangup
boot off a memstick? On 08/12/2022 3:25 pm, Nuno Teixeira wrote: The problem is if boot is failing, how to mount and rename it? I'm looking for a way, if possible, to boot directly bkp boot64x in case of failure. I was hoping to find it in loader(8) or uefi(8)... Larry Rosenman escreveu no dia sexta, 12/08/2022 à(s) 21:09: I would assume just rename the bootx64.old to bootx64.efi and/or put it in a different directory that EFI can see On 08/12/2022 3:03 pm, Nuno Teixeira wrote: 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 /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 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 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 upgrade and I need to practice how to boot loader bkp file :) I update boot loader everytime because I'd like to do it :-). And sometimes problem hits upon me like this time and I contribute to debugging base system :-):-). --- Yasuhiro Kimura -- Nuno Teixeira FreeBSD Committer (ports) -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 -- Nuno Teixeira FreeBSD Committer (ports) -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
Re: Updating EFI boot loader results in boot hangup
The problem is if boot is failing, how to mount and rename it? I'm looking for a way, if possible, to boot directly bkp boot64x in case of failure. I was hoping to find it in loader(8) or uefi(8)... Larry Rosenman escreveu no dia sexta, 12/08/2022 à(s) 21:09: > I would assume just rename the bootx64.old to bootx64.efi > > and/or put it in a different directory that EFI can see > > > On 08/12/2022 3:03 pm, Nuno Teixeira wrote: > > 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 /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 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 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 upgrade and > I need to practice how to boot > > loader bkp file :) > > I update boot loader everytime because I'd like to do it :-). > And sometimes problem hits upon me like this time and I contribute to > debugging base system :-):-). > > --- > Yasuhiro Kimura > > > > -- > Nuno Teixeira > FreeBSD Committer (ports) > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: l...@lerctr.org > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > -- Nuno Teixeira FreeBSD Committer (ports)
updating of prebuilt packages with pkg
I am not sure if this issue is more for -stable or -ports, so I start
here. The visible problem was that after 'pkg upgrade' certbot stopped
working.
I am running systems that after initial install do binary-only upgrades
for both core and ports with freebsd-update(8) and pkg(8). I do not have
the /usr/src/ or /usr/ports/ trees installed in order to save space. For
policy reasons these use pre-built packages and I will never compile
anything from source on these systems. This one is on 12.3-RELEASE .
Recently I encountered that the usual cadence of
pkg update
pkg upgraade
pkg autoremove
pkg clean
left me with several packages in state "?".
$ pkg version |grep \?
[...]
py38-acme-1.22.0,1 ?
py38-certbot-1.22.0,1 ?
[...]
ruby27-bdb-0.6.6_8 ?
which tells me that these have been superseded by something else.
Tracking 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 'py38-*'); do pkg set -yn ${i}:py39-${i#py38-};
done
# pkg upgrade
[...]
How would a user of pre-built packages find out about the need to run the
'pkg set' command? The dependency and integrity solver in pkg did not show
any notices about it. An example would be p7zip.
I believe a similar issue exists if a port gets removed entirely, in which
case a previously installed package shows in state "?". No notification
is given by pkg about the fact that is was deprecated.
Using the instructions above I was able to get back to a working certbot.
In the case of ruby27 the pkg commands above handled this gracefully
on its own, see /usr/ports/UPDATING entry from 20220421
"ruby: 2.7.x -> 3.0.4_2,1".
Thanks, andreas
--
andr...@naund.org
Re: Updating EFI boot loader results in boot hangup
I would assume just rename the bootx64.old to bootx64.efi and/or put it in a different directory that EFI can see On 08/12/2022 3:03 pm, Nuno Teixeira wrote: 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 /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 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 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 upgrade and I need to practice how to boot loader bkp file :) I update boot loader everytime because I'd like to do it :-). And sometimes problem hits upon me like this time and I contribute to debugging base system :-):-). --- Yasuhiro Kimura -- Nuno Teixeira FreeBSD Committer (ports) -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
Re: Updating EFI boot loader results in boot hangup
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 /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 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 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 upgrade and > I need to practice how to boot > > loader bkp file :) > > I update boot loader everytime because I'd like to do it :-). > And sometimes problem hits upon me like this time and I contribute to > debugging base system :-):-). > > --- > Yasuhiro Kimura > > -- Nuno Teixeira FreeBSD Committer (ports)
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 because of zfs upgrade and I > need to practice how to boot > loader bkp file :) I update boot loader everytime because I'd like to do it :-). And sometimes problem hits upon me like this time and I contribute to debugging base system :-):-). --- Yasuhiro Kimura
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 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-boot-hangup.png > > If I restore previous loader file (that is, loader.efi of > main-n257134-a69c0964625 and kernel of main-n257316-9d16275c65b), then > system boots successfully. > > Best Regards. > > --- > Yasuhiro Kimura > > -- Nuno Teixeira FreeBSD Committer (ports)
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-boot-hangup.png If I restore previous loader file (that is, loader.efi of main-n257134-a69c0964625 and kernel of main-n257316-9d16275c65b), then system boots successfully. Best Regards. --- Yasuhiro Kimura
Re: [iwlwifi] ipv6 connection problem
Hi Merek, If you are connecting to IPv6 only WLAN than you can probably either > disable DHCP (if the RDNSS is provided for this network): > ifconfig_wlan0="WPA up" > or install dhcp client capable of acquiring DHCPv6 lease and use it > instead of standard dhclient(8) from the base which doesn't support DHCPv6. I've tried ifconfig_wlan0="WPA up" and it crashes os. You saying that base dhcp doesn't support ipv6 but it works fine with ehternet: --- ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" rtsold_enable="YES" --- Any clues? Thanks
Re: [iwlwifi] ipv6 connection problem
W dniu 11.08.2022 o 17:53, Nuno Teixeira pisze:
Hello Bjoern!
/etc/rc.conf:
---
wlans_iwlwifi0="wlan0"
create_args_wlan0="wlanmode sta regdomain ETSI country PT"
ifconfig_wlan0_ipv6="inet6 accept_rtadv"
ifconfig_wlan0="WPA SYNCDHCP"
rtsold_enable="YES"
---
If you are connecting to IPv6 only WLAN than you can probably either
disable DHCP (if the RDNSS is provided for this network):
ifconfig_wlan0="WPA up"
or install dhcp client capable of acquiring DHCPv6 lease and use it
instead of standard dhclient(8) from the base which doesn't support DHCPv6.
`ifconfig wlan0`:
---
wlan0: flags=8c43 metric
0 mtu 1500
ether 6c:6a:77:df:09:21
inet6 fe80::6e6a:77ff:fedf:921%wlan0 prefixlen 64 scopeid 0x3
groups: wlan
ssid "" channel 6 (2437 MHz 11g)
regdomain ETSI country PT authmode WPA1+WPA2/802.11i privacy MIXED
deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS wme
roaming MANUAL bintval 0
parent interface: iwlwifi0
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
nd6 options=23
---
(a) this is unlikely related to IPv6? The only thing that would do
is pass down more multicast addresses than with just IPv4 (and that's
after assoc normally). I run some on IPv6-only.
Let me ask you anyway, so we can be sure. If you remove the IPv6
config,
does wpa_supplicant associate fine? (could also be a different
tooling issue).
With ipv4 wireless work ok and wpa_supplicant associate ok.
(b) does `ifconfig wlan0 list scan` show your AP when it doesn't?
If it doesn't that is more likely the problem. And that remains a
problem
for some conditions I am also facing. More on 11a than 11g.
`ifconfig wlan0 list scan`:
---
SSID/MESH ID BSSID CHAN RATE S:N
INT CAPS
MEO-3637C0 00:06:91:36:37:c0 11 54M -53:-96
100 EP RSN BSSLOAD HTCAP WPS WME
MEO-WiFi 00:06:91:36:37:c2 11 54M -53:-96
100 E BSSLOAD HTCAP WME
MEO-3637C0 00:06:91:36:37:c1 60 54M -61:-96
100 EP RSN BSSLOAD HTCAP VHTCAP VHTOPMODE VHTPWRENV WPS WME
MEO-WiFi 00:06:91:36:37:c6 60 54M -60:-96
100 E BSSLOAD HTCAP VHTCAP VHTOPMODE VHTPWRENV WME
---
(c) Then the question is if wpa_supplicant blacklists the network;
`wpa_cli blacklist` would show. If it does try the following sequence
to make it try more often:
CMD=wpa_cli
SSID=
${CMD} blacklist clear
${CMD} disable ${SSID}
${CMD} enable ${SSID}
${CMD} list_networks
`wpa_cli blacklist`:
---
Failed to connect to non-global ctrl_ifname: (nil) error: Inappropriate
ioctl for device
---
(d) given you didn't say, what does `freebsd-version -r -u`
say, just to rule out you are missing the latest wpa fixes.
`freebsd-version -r -u`:
---
14.0-CURRENT
14.0-CURRENT
---
@1ffd352bc25b
(e) what you can do is enable more wpa_supplicant logging; I often use
wpa_supplicant_flags="-sdd" in /etc/rc.conf which will log to
syslog instead
of the debug file but it'll increase debugging a lot (and warning, it
may also log keying material).
Ok.
Cheers,
--
Nuno Teixeira
FreeBSD Committer (ports)
--
Marek Zarychta
OpenPGP_signature
Description: OpenPGP digital signature
