How is 14 doing for folks?

all systems doing fine, gave my notebooks a try with 14 but immediately switched to Debian GNU/Linux again since wifi is just not where it should be (for me). At work, amd64 and arm64 upgrades went flawlessly, the speedup is notable.
 
I installed 14 when I got my new old laptop without even realising that it was brand spanking new. No issues, except that I didn't get audio working over HDMI despite the configuration looking correct and dials jumping as they should've.

Lenovo thinkpad x280, i5-8350U, 16G, i3 + XFCE, integrated graphics.
 
SirDice said:
Two systems upgraded from stable/13 to stable/14 the minute it became available. All systems (~13) at home have all been upgraded to 14.0-RELEASE with zero issues. VPS is still running 13.2 and needs to be done, but I'll get to that soon enough. Have a bunch of jails running there, it takes a bit of effort to get it all done.
Click to expand...
Here I have also upgraded two desktop systems. Everything seems good so far. MATE is running with graphics/drm-515-kmod. Using AMD GPU-s. Naturally had to reinstall graphics/gpu-firmware-kmod. On one system already upgraded the zpool.

Code: 
# uname -aKU
FreeBSD Rhodium 14.0-RELEASE-p3 FreeBSD 14.0-RELEASE-p3 #5 20fae1e16: Sun Dec 17 18:20:21 EET 2023     root@Rhodium:/usr/obj/usr/src/amd64.amd64/sys/RHODIUM amd64 1400097 1400097
 
Just started using FreeBSD 14 on an Intel 10th generation NUC as a headless development server. So far it's been excellent. Very pleased to find all my usual tools like helix, starfish, bat, tailscale, etc. already packaged as ports.
 
unitrunker said:
… DO …
Click to expand...

What's DO?

cracauer@ said:
… My interactive/GUI machines are all 15-current.
Click to expand...

Much the same here. I ran 14.0-CURRENT from day one, then 15.0.

First on an HP EliteBook 8570p, then a ZBook 17 G2. Each one with multiple docking stations (the same type) and multiple displays on DisplayPort. There were occasional issues with 14.0-CURRENT, nothing memorable.

Issues tend to be more with ports, than with base.

Argentum said:
… Naturally had to reinstall graphics/gpu-firmware-kmod. …
Click to expand...

A routine upgrade, with pkg, yes?

meine said:
… www/firefox somehow wasn't re-installed, … (www/qutebrowser can do it all, …
Click to expand...

The latter, not so good for PDF.
 
# uname -aKU
FreeBSD freebsd3 14.0-RELEASE-p3 FreeBSD 14.0-RELEASE-p3 #0: Mon Dec 11 04:56:01 UTC 2023 root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400097 1400097

works fine on my workstation. I mainly use it to run bhyve virtual machines (Windows Server 2022 Standard, Windows 10, Debian 12).

# dmidecode -t processor
# dmidecode 3.5
# SMBIOS entry point at 0x6f4e6000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.2 present.

Handle 0x004B, DMI type 4, 48 bytes
Processor Information
Socket Designation: CPU1
Type: Central Processor
Family: Xeon
Manufacturer: Intel(R) Corporation
ID: 54 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 85, Stepping 4
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
Voltage: 1.6 V
External Clock: 100 MHz
Max Speed: 4000 MHz
Current Speed: 2200 MHz
Status: Populated, Enabled
Upgrade: Socket LGA3647-1
L1 Cache Handle: 0x0048
L2 Cache Handle: 0x0049
L3 Cache Handle: 0x004A
Serial Number: Not Specified
Asset Tag: UNKNOWN
Part Number: Not Specified
Core Count: 14
Core Enabled: 14
Thread Count: 28
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control

Handle 0x004F, DMI type 4, 48 bytes
Processor Information
Socket Designation: CPU2
Type: Central Processor
Family: Xeon
Manufacturer: Intel(R) Corporation
ID: 54 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 85, Stepping 4
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
Voltage: 1.6 V
External Clock: 100 MHz
Max Speed: 4000 MHz
Current Speed: 2200 MHz
Status: Populated, Enabled
Upgrade: Socket LGA3647-1
L1 Cache Handle: 0x004C
L2 Cache Handle: 0x004D
L3 Cache Handle: 0x004E
Serial Number: Not Specified
Asset Tag: UNKNOWN
Part Number: Not Specified
Core Count: 14
Core Enabled: 14
Thread Count: 28
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control

# dmidecode -t system
# dmidecode 3.5
# SMBIOS entry point at 0x6f4e6000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.2 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: WS-C621E-SAGE Series
...
...
Family: Server

# dmidecode -t BIOS
# dmidecode 3.5
# SMBIOS entry point at 0x6f4e6000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.2 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 6605
Release Date: 05/26/2021
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 32 MB
Characteristics:
PCI is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.14

Handle 0x0056, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1

#

# dmidecode -t Memory Module
# dmidecode 3.5
# SMBIOS entry point at 0x6f4e6000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.2 present.

Handle 0x0037, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: Single-bit ECC
Maximum Capacity: 1536 GB
Error Information Handle: Not Provided
Number Of Devices: 12

Handle 0x0038, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0037
Error Information Handle: Not Provided
Total Width: 72 bits
Data Width: 64 bits
Size: 16 GB
Form Factor: DIMM
Set: None
Locator: DIMM_A1
Bank Locator: NODE 1
Type: DDR4
Type Detail: Synchronous
Speed: 2400 MT/s
Manufacturer: Samsung
Serial Number: 1894FFEF
Asset Tag: DIMM_A1_AssetTag
Part Number: M393A2K40BB1-CRC
Rank: 1
Configured Memory Speed: 2400 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V
...
...
...
 
unitrunker said:
I had to abandon DO. Upgrading to 14.0-RELEASE broke networking - this with no firewall and nothing exotic. It was easier to spin up a new instance (with a 14.0-RELEASE image ready to go) at vultr.com than to troubleshoot DO's environment. I moved two VMs to vultr.com and have had no problems since.
Click to expand...
Did you have anything unusual in your networking config? I had no issue, I just ran the usual series of commands (using freebsd-update) and it came right up with no issue. I have a very stock network configuration though.
 
I have to say that KDE (plasma 5) has come a long way in recent times on FreeBSD with stability in general. I remember trying it a couple of years back and there were random segfaults all the time with various kde components. Been using it for a couple of weeks now and its rock solid. So, hats off to those folks who have worked hard to port it to FreeBSD and work on fixing issues :beer::cool:
 
ahhyes said:
Did you have anything unusual in your networking config?
Click to expand...
As stated in the post you quoted - no, nothing exotic. Just nginx and an IPv4 address which had not changed in a few years. I had started with an 11.x image provided by DO and gone though 12.x and 13.x upgrades just fine. Upgrading to 14.0-RELEASE broke networking. Could not ping anything past the gateway. Since DO stopped providing FreeBSD droplet images, I was on my own in terms of support. Once I realized I would have to build a new image from scratch, I decided to look at other options since the effort would be the same. My VMs are static sites with no dynamic content so no data lost (just some of my time). I was a happy customer for five + years until early this month. Mind you, my hosting budget for the last five years was less than what most small businesses spend in a month so I don't expect any provider to jump over backwards for my business.

Back to 14.0-RELEASE, I sometimes run into a package that doesn't work. Take svxlink and msfconsole as recent examples. I submitted bugs on bugzilla with errors attached for msfconsole. Need to do same for svxlink. Ideally the package build system would have a way to do a sanity check on each port but that isn't always practical.
 
unitrunker said:
Once I realized I would have to build a new image from scratch, I decided to look at other options since the effort would be the same.
Click to expand...
I noticed they stopped providing images too - I went to migrate my FreeBSD droplet to a different DC as they now had one that was geographically closer to me, and that's when I discovered it - its not hard to work around though, FreeBSD provide VM images you can import into DO (qcow2, raw, vhd. vmdk images etc) - they can be imported via the DO control panel and I was able to launch a new instance without a lot of drama. The only minor annoyance is that if you use your own image, they wont allow ipv6, which I think is an utterly bizarre decision on their part. Anyway it is what it is.
 
In my past life as a SYSAD at the University of Idaho, I made it a policy to never move to a later OPSYS until at least 1 year had passed in order to be reasonably sure all the major bugs had been smashed.

I am presently using 13.2_RELEASE on two boxes.

Ken
 
Running 14.0 as home server with Intel 12500T and some cheapest motherboard and no issues excluding that I can’t enable DRM with integrated i915 GPU (for Jellyfin/Plex transcodings) as version 515 hangs.

Tempted to switch motherboard to the one with W680 Intel chipset to enable ECC but I’m not sure FreeBSD supports this chipset.

So to summarise, good experience so far. Syncthing, samba, media servers etc works fine. More services to come in near future.
Cannot comment on Firefox or other GUI apps as there is no Xorg installed on this machine.
 
It's doing OK for me until now.
Installed from scratch (fresh) on my Samsung NP350XAA laptop and all the settings for video and sound still works. Except touchpad still not working (like before while on 13.2).

Doing tests locally in bhyve using a backup image of my VPS for the 13.2-RELEASE -> 14.0-RELEASE upgrade, and some heavy lift work in bringing/testing jails from ezjail to bastille included. Doing good. As always, important to have host in the latest 13.2 patch level before upgrading. At least > 13.2-RELEASE-p5 in this case AFAIK
 
Upgraded my thinkpad X201 from 13.2 to 14.0 yesterday. Painless upgrade, very impressed. Everything seems to be working. Pleased to see that xorg is working with dri and glamor/crocus on this hardware (at least, according to Xorg.0.log), crocus is a recent drop from open source gallium3d. All my existing settings were preserved, sound works, nested X works... This is just a desktop system of course. Network config all preserved and lagg works with failover between ethernet and wifi, as before. All very smooth for a full release upgrade. Impressed.

Firefox seems to be using a lot of memory, but it did on 13.2; anyway that's firefox, not bsd. I wish there was still a waterfox port.

Has anyone made any progress getting bluetooth to work with 14.0? I'm thinking of bluetooth audio?

Playing videos - mplayer defaults to chosing the gl driver, and mpv defaults to choosing the gpu driver, so it all looks good. VLC tested working. Suspend/resume works. Thinkpad function keys work, including backlight brightness. Fan is off nearly all the time. It's all good.
 
There appears to be an issue using lagg with a onboard NIC and wifi card.
At least, that is my case and at least someone else's:
forums.freebsd.org

Lagg0 doesn't work properly after upgrade from FreeBSD 13.2 to 14.0

Hi Community, I need your help solving this issue. I had lagg0 and other interfaces assigned in /etc/rc.conf as follows: ifconfig_em0="ether 8c:70:5a:XX:XX:XX" ##MAC address of the wlan0 ifconfig_em0="up" wlans_iwn0="wlan0" create_args_wlan0="regdomain FCC country XX" ifconfig_wlan0="up WPA"...
forums.freebsd.org forums.freebsd.org
 
You must log in or register to reply here.
Back
Top