FreeBSD 14.0-BETA5 Now Available

2023-10-06 Thread Glen Barber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The fifth BETA build of the 14.0-RELEASE release cycle is now available.

Installation images are available for:

o 14.0-BETA5 amd64 GENERIC
o 14.0-BETA5 i386 GENERIC
o 14.0-BETA5 powerpc GENERIC
o 14.0-BETA5 powerpc64 GENERIC64
o 14.0-BETA5 powerpc64le GENERIC64LE
o 14.0-BETA5 powerpcspe MPC85XXSPE
o 14.0-BETA5 armv7 GENERICSD
o 14.0-BETA5 aarch64 GENERIC
o 14.0-BETA5 aarch64 RPI
o 14.0-BETA5 aarch64 PINE64
o 14.0-BETA5 aarch64 PINE64-LTS
o 14.0-BETA5 aarch64 PINEBOOK
o 14.0-BETA5 aarch64 ROCK64
o 14.0-BETA5 aarch64 ROCKPRO64
o 14.0-BETA5 riscv64 GENERIC
o 14.0-BETA5 riscv64 GENERICSD

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

https://download.freebsd.org/releases/ISO-IMAGES/14.0/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use Git to do a source based update of an existing
system, use the "releng/14.0" branch.

A summary of changes since 14.0-BETA4 includes:

o An issue preventing binary upgrades using freebsd-update on earlier
  supported releases had been fixed.

o Several networking-related bug fixes had been addressed.

o Experimental support for Amazon EC2 cloud-init AMIs had been added.

o Several additional miscellaneous bug fixes and enhancements.

A list of changes since 13.2-RELEASE is available in the releng/14.0
release notes:

https://www.freebsd.org/releases/14.0R/relnotes/

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 14.0-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

https://download.freebsd.org/releases/VM-IMAGES/14.0-BETA5/

BASIC-CI images can be found at:

https://download.freebsd.org/releases/CI-IMAGES/14.0-BETA5/

The partition layout is:

~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
-bios QEMU_EFI.fd -serial telnet::,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager
Parameter Store in each region using the keys:

/aws/service/freebsd/amd64/base/ufs/14.0/BETA5
/aws/service/freebsd/amd64/base/zfs/14.0/BETA5
/aws/service/freebsd/amd64/cloud-init/ufs/14.0/BETA5
/aws/service/freebsd/amd64/cloud-init/zfs/14.0/BETA5

FreeBSD/aarch64 EC2 AMI IDs can be retrieved from the Systems Manager
Parameter Store in each region using the keys:

/aws/service/freebsd/aarch64/base/ufs/14.0/BETA5
/aws/service/freebsd/aarch64/base/zfs/14.0/BETA5
/aws/service/freebsd/aarch64/cloud-init/ufs/14.0/BETA5
/aws/service/freebsd/aarch64/cloud-init/zfs/14.0/BETA5

=== Vagrant Images ===

FreeBSD/amd64 images are not available for this build.

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64, i386,
and aarch64 systems running earlier FreeBSD releases.  Systems running
earlier FreeBSD releases can upgrade as follows:

# freebsd-update upgrade -r 14.0-BETA5

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install

It is recommended to 

Re: Thinkpad X1 Carbon gen11 - suspend not work

2023-10-06 Thread Oleksandr Kryvulia

05.10.23 11:06, Li-Wen Hsu:
On Thu, Oct 5, 2023 at 4:00 PM Oleksandr Kryvulia 
 wrote:


Hi,
I have Thinkpad X1 Carbon gen11 where s3 is not available:

# sysctl hw.acpi.supported_sleep_state
hw.acpi.supported_sleep_state: S4 S5

FreeBSD 15.0-CURRENT #47 main-n265480-95a4709b2cca-dirty, latest
available bios.

What can be done to investigate?


I'm not sure about gen11, but for the earlier generations, the sleep 
state can be adjusted in BIOS. This is what on my gen6: 
https://twitter.com/lwhsu/status/1039711710913945601


Unfortunately, I did not find these settings in BIOS.
P.S. I try ubuntu livecd and suspend-resume works.

Re: panic in cypto code

2023-10-06 Thread Kristof Provost



> On 6 Oct 2023, at 08:46, Steve Kargl  
> wrote:
> 
> On Thu, Oct 05, 2023 at 03:11:02PM -0700, Steve Kargl wrote:
>> 
>> I'll ping you off list when it's available.
>> 
> 
> Well, this is interesting.  I cannot upload the files to
> a location from which I can then put them up on freefall. :(
> 
> % scp -P1234 kernel.debug 10.95.76.21:
> kernel.debug0%  255KB 255.0KB/s   04:01 
> ETAclient_loop: send disconnect: Broken pipe
> lost connection
> % scp -P1234 vmcore.2  10.95.76.21:
> vmcore.20%  255KB 254.9KB/s   49:46 
> ETAclient_loop: send disconnect: Broken pipe
> lost connection
> 
> Looks like if_ovpn,ko is autoloaded.
> %  kldstat | grep ovpn
> 231 0x82042000 6650 if_ovpn.ko
> 
> Don't know what if_ovpn.ko does in hijacking tun0, but dying after
> 255kB is likely not correct.
> 
If_ovpn.ko is the kernel side of the DCO (data channel offload) thing for 
OpenVPN. It’s loaded and activated automatically if available. 
You can add “disable-dco” to your OpenVPN config to disable that.

Kristof


Re: panic in cypto code

2023-10-06 Thread Steve Kargl
On Thu, Oct 05, 2023 at 03:11:02PM -0700, Steve Kargl wrote:
> 
> I'll ping you off list when it's available.
> 

Well, this is interesting.  I cannot upload the files to 
a location from which I can then put them up on freefall. :(

% scp -P1234 kernel.debug 10.95.76.21:
kernel.debug0%  255KB 255.0KB/s   04:01 
ETAclient_loop: send disconnect: Broken pipe
lost connection
% scp -P1234 vmcore.2  10.95.76.21:
vmcore.20%  255KB 254.9KB/s   49:46 
ETAclient_loop: send disconnect: Broken pipe
lost connection

Looks like if_ovpn,ko is autoloaded.
%  kldstat | grep ovpn
231 0x82042000 6650 if_ovpn.ko

Don't know what if_ovpn.ko does in hijacking tun0, but dying after
255kB is likely not correct.

-- 
Steve