Solved upgrading from 14.2 to 14.3 didn't went well

Charlie Brown

Charlie Brown

Code: 
$ freebsd-version -kru
14.3-RELEASE
14.3-RELEASE
14.3-RELEASE-p1

Code: 
kernel: link_elf_obj: symbol linux_kfree_async undefined
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/dmabuf.ko - unsupported file type
Jul 17 21:28:11 nomonoru kernel: KLD drm.ko: depends on dmabuf - not available or version mismatch
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/drm.ko - unsupported file type
Jul 17 21:28:11 nomonoru kernel: KLD i915kms.ko: depends on drmn - not available or version mismatch
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/i915kms.ko - unsupported file type

Basically I have no graphic session under userland 14.3 and if I can still have that session in 14.2.p1 it's extremely buggy. And I have mismatched kernel file under the new kernel.

This happened following the upgrade from 14.2-p4 to 14.3 using
freebsd-update upgrade -r 14.3

I can still access the command line to get into my account. So nothing is desperate here. I normally should be easily able to receive support from the forum in these conditions.
 
LibreQuest said:
You need to rollback your update.
freebsd-update rollback


Then follow the handbook procedure for installing your security updates for v14.2

https://docs.freebsd.org/en/books/handbook/cutting-edge/

After your are up to date on 14.2 then update your system to version 14.3
Click to expand...
I did exactly that but it didn't fix the issue because there is something else but I'm on it.

Daniel Wayne Armstrong (@dwarmstrong@fosstodon.org)

[ SOLVED - SEE COMMENTS ] !! Word of caution if anyone is thinking of upgrading FreeBSD 14.2->14.3 on a desktop machine !! First time upgrading FreeBSD. Everything seemed OK but upon reboot no longer have working Intel graphic card support: $ dmesg | grep drm KLD drm.ko: depends on...
fosstodon.org fosstodon.org

for now I just booted back in the old environment since i have zfs snapshot back up.
 
Frankly, this forum is full of similar subjects. It's not of today, it's at each minor version upgrade.

This time, you have a new repo to avoid to recompile yourself that sort of kernel modules.
 
Emrion said:
Frankly, this forum is full of similar subjects. It's not of today, it's at each minor version upgrade.

This time, you have a new repo to avoid to recompile yourself that sort of kernel modules.
Click to expand...
Hi mister we'll get the world we deserve, a lot of people THINK they are smart n off that their opinions mater, but in fact it's just noises, next time please abstain from giving me your opinion, thanks,
 
I just did 14.2 to 14.3 update on a system using i915; I had to pkg delete drm-kmod && pkg install drm-kmod.
If you are using ZFS Boot Environments, one can mount the broken BE, modify /etc/rc.conf to not load the driver, boot into that BE and do the pkg delete/pkg install stuff.
After doing freebsd-update upgrade -r 14.3-RELEASE did you:
freebsd-update install (this installs the new kernel, typically you want to reboot after this)
freebsd-update install (this will install the new userland)
freebsd-update install (this may do nothing but it may clean old libraries)
pkg-static -f (this will upgrade all the packages and is needed whenever you update to a newer release).

Since you are using ZFS, you can manually create a new BE and do all the commands on the new BE in a chroot.
man freebsd-update, the -b option
and pkg-static -c (-c is chroot).

It's a quick way to create a new BE with the new release and have it coherent and you just reboot once.
 
Charlie Brown said:
Hi mister we'll get the world we deserve, a lot of people THINK they are smart n off that their opinions mater, but in fact it's just noises, next time please abstain from giving me your opinion, thanks,
Click to expand...
Sorry, didn't want to be rude.

It's not an opinion; it's just an help for this and also for future problems. Until then you got no answer, I explained why.
 
Charlie Brown said:
Code: 
$ freebsd-version -kru
14.3-RELEASE
14.3-RELEASE
14.3-RELEASE-p1

Code: 
kernel: link_elf_obj: symbol linux_kfree_async undefined
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/dmabuf.ko - unsupported file type
Jul 17 21:28:11 nomonoru kernel: KLD drm.ko: depends on dmabuf - not available or version mismatch
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/drm.ko - unsupported file type
Jul 17 21:28:11 nomonoru kernel: KLD i915kms.ko: depends on drmn - not available or version mismatch
Jul 17 21:28:11 nomonoru kernel: linker_load_file: /boot/modules/i915kms.ko - unsupported file type

Basically I have no graphic session under userland 14.3 and if I can still have that session in 14.2.p1 it's extremely buggy. And I have mismatched kernel file under the new kernel.

This happened following the upgrade from 14.2-p4 to 14.3 using
freebsd-update upgrade -r 14.3

I can still access the command line to get into my account. So nothing is desperate here. I normally should be easily able to receive support from the forum in these conditions.
Click to expand...
Hi Charlie,

Sorry this happened - I had the same experience as well.

The issue is that you need to load freebsd-update FreeBSD-kmods to update these files. Follow the instructions here: FreeBSD-kmods

Thanks.
 
Emrion said:
Sorry, didn't want to be rude.

It's not an opinion; it's just an help for this and also for future problems. Until then you got no answer, I explained why.
Click to expand...
Sorry if i misinterpreted you. I'll take your advice in consideration and search to forum more thoroughly next time.

Jose

Thread 'Possible solution to the drm-kmod kernel mismatch after upgrade from Bapt'

There are a lot of threads on this subject. It's a thorny problem that often comes up after upgrades from a minor version that has not reached EOL yet. bapt@ has posted a solution to freebsd-ports:
  • Thanks
  • Like
 
mer said:
I just did 14.2 to 14.3 update on a system using i915; I had to pkg delete drm-kmod && pkg install drm-kmod.
If you are using ZFS Boot Environments, one can mount the broken BE, modify /etc/rc.conf to not load the driver, boot into that BE and do the pkg delete/pkg install stuff.
After doing freebsd-update upgrade -r 14.3-RELEASE did you:
freebsd-update install (this installs the new kernel, typically you want to reboot after this)
freebsd-update install (this will install the new userland)
freebsd-update install (this may do nothing but it may clean old libraries)
pkg-static -f (this will upgrade all the packages and is needed whenever you update to a newer release).

Since you are using ZFS, you can manually create a new BE and do all the commands on the new BE in a chroot.
man freebsd-update, the -b option
and pkg-static -c (-c is chroot).

It's a quick way to create a new BE with the new release and have it coherent and you just reboot once.
Click to expand...
Hi mer, thank you for your support much appreciated, to answer your questions, no I didn't do frebsd-update install after the reboot of the upgrade. I'm doing it now.

I also have questions for you ,
When you talk about mounting a specific be are you talking of the file system for example that output when you input the command zfs list -t fs ?

And if it's the case should I mount it like that:
zfs mount filesystem ?
I suppose then I will immediately be in that file system?

Thanks
 
start with the command:
bectl list

That will list all of your Boot Environments. Think of a Boot Envrionment (BE) as a "root filesystem".
When you run freebsd-update it automatically creates a new BE that represents the system BEFORE any updates are applied. The "BEFORE" is important to remember.
Example from one of my systems. NR means "N is currently active, R is active on next reboot" So I'm currently running 14.3-RELEASE-p1.

bectl list
BE Active Mountpoint Space Created
14.2-RELEASE-p3 - - 6.92G 2025-04-17 05:48
14.3-RELEASE-p1 NR / 23.4G 2025-07-18 12:54

bectl mount 14.2-RELEASE-p3 /mnt

That mounts the BE named 14.2-RELEASE-p3 at /mnt. As root if you vi /mnt/etc/rc.conf you are modifiying rc.conf in the BE named 14.2-RELEASE-p3.

When I upgrade across releases (anytime you run freebsd-update upgrade -r) I do the following: Please do not blindly cut and paste, read the man pages and understand what the commands are doing. This was from when I was upgrading from 12 to 13. This process works for me, I've been using it for a while, other's may do things differently.


bectl create 13.1-RELEASE
bectl mount 13.1-RELEASE /mnt

freebsd-update upgrade -b /mnt -d /mnt/var/db/freebsd-update -r 13.1-RELEASE
freebsd-update -b /mnt -d /mnt/var/db/freebsd-update install
freebsd-update -b /mnt -d /mnt/var/db/freebsd-update install
freebsd-update -b /mnt -d /mnt/var/db/freebsd-update install # yes run three times

mount -t devfs devfs /mnt/dev # pkg needs devfs mounted
pkg-static -c /mnt upgrade -f
umount /mnt/dev
# at this point I will typically edit kldlist to not automatically load the drm kmods. I then modify after reboot once everything is verified.
vi /mnt/etc/rc.conf

# At this point you can update bootcode IF YOU WANT, using /mnt/boot as the source directory.

bectl umount 13.1-RELEASE
bectl activate 13.1-RELEASE
# this is where you reboot
 
CShell said:
Hi Charlie,

Sorry this happened - I had the same experience as well.

The issue is that you need to load freebsd-update FreeBSD-kmods to update these files. Follow the instructions here: FreeBSD-kmods

Thanks.
Click to expand...
Thanks, yes, that definitely solves the issue with the graphical environment. But not the issues with the keyboard lag and the touch pad not working
 
Charlie Brown said:
Thanks, yes, that definitely solves the issue with the graphical environment. But not the issues with the keyboard lag and the touch pad not working
Click to expand...
Excellent, glad you got the UI going. Not sure what's going on with those other issues - hopefully someone else will speak up on those.
 
CShell said:
Excellent, glad you got the UI going. Not sure what's going on with those other issues - hopefully someone else will speak up on those.
Click to expand...
I Think something was broken in that specific environment because I did the upgrade in another one and everything is fine, I will not delete the broken environment because I'd like to know what happen there. So if someone is willing to assist a bit, I'll be happy continuing investigating that issues. Thanks for the support.
 
You must log in or register to reply here.
Back
Top