Upgraded Freebsd 13.2 to 13.3

I just upgraded from 13.2 to 13.3

I did the
freebsd-update fetch install
pkg update && pkg upgrade
freebsd-update upgrade -r 13.3 -RELEASE
freebsd-update install

after it installed it instructed me to reboot and to the last command again.

I do this but this time when it boots into a gnome desktop before it gets there
there's a kernel panic.

Here's an identical issue: https://forums.freebsd.org/threads/radeonkms-causing-kernel-panic-after-13-2-13-3-upgrade.93259/

It's the same kind of kernel panic message I see where it shows those 17 items.

I couldn't boot in multi-user mode. I then decided to boot into single mode.

I then edited rc.conf to not automatically start GDM and commented out a KLD setting to load in drm-kmod

after doing this. I was able to boot into multi-mode and use terminal command line.

I think ran the command
freebsd-update install
it ran successfully and completed

I did another
pkg update && pkg upgrade
pkg deinstall clean drm-kmod
pkg install clean drm-kmod
pkg update && pkg upgrade
This time it shown that there's a new version of drm-kmod
it asked do you want to upgrade it to the latest version I put yes
then it finished installing successfully
Then edited rc.conf to kld that drm-kmod and rebooted the system.

now, it still shows the kernel panic just like in the link I provided above nothing changed.

I don't know what to do..

should I continue and upgrade to freebsd 13.4 ? I am trying to get to 14.1 the latest version.
However, I was told I need to upgrade to each version one step at a time.

I just want to know if this is the right way to do it?

why is the kernel having that panic issue?

My guess is that the latest version of drm-kmod is supported in 14.1

and I would assume if this is true then I just need to use the terminal
and just upgrade the OS to version 13.4 then to 14.0 and then 14.1
by 14.1 the drm-kmod should work properly?

any ideas on how I should proceed ?
 
pkg deinstall clean drm-kmod
This looks like a mix of a make(1) command and pkg(8)pkg-delete(8) deletes a package.

My guess is that the latest version of drm-kmod is supported in 14.1
Yes, that is graphics/drm-61-kmod, that is not available for 13.3-RELEASE or 13.4-RELEASE. That doesn't mean that graphics/drm-510-kmod or graphics/drm-515-kmod* couldn't work on 13.3-RELEASE or 13.4-RELEASE on your system.

Could you post some info about your system?
freebsd-version -kru
pciconf -lv | grep -B4 -A1 display
sysctl hw.model hw.machine hw.ncpu
pkg info -g 'drm-*-kmod'

___
* edit: graphics/drm-515-kmod is only for 14.0 and above
 
Last edited:
This looks like a mix of a make(1) command and pkg(8)pkg-delete(8) deletes a package.


Yes, that is graphics/drm-61-kmod, that is not available for 13.3-RELEASE or 13.4-RELEASE. That doesn't mean that graphics/drm-510-kmod or graphics/drm-515-kmod couldn't work on 13.3-RELEASE or 13.4-RELEASE on your system.

Could you post some info about your system?
freebsd-version -kru
pciconf -lv | grep -B4 -A1 display
sysctl hw.model hw.machine hw.ncpu
pkg info -g 'drm-*-kmod'
below are screenshots. I was able to get the gnome to work but committing out
gdm="YES" In the
rc.conf file.

Below is screenshots of the desktop:

IMG_0245.jpg

IMG_0248.jpg

IMG_0249.jpg

IMG_0250.jpg

The 4th spoiler has both the 3rd command you asked for and the 4th.


I ask this question if it's ok to proceed to upgrade the OS?

I originally had version 13.2 and now it's 13.3

I plan on upgrading to 13.4 and then to 14.0 and then t o 14.1

The reason I ask this is so that I don't mess up any software. I don't want to proceed if it's going to
mess up the driver used for video / graphics.

I commented out the " gdm="YES" and the kldload="driver"

before I changed gdm='NO' and it loaded up only the terminal.

This time just commented the stuff out being lazy. I then noticed the desktop loaded up.
In my opinion I feel like it's ok to proceed installing the other OS versions one by one.
I just thought I should come on here and ask before proceeding. I want to avoid possible common issues
that come from upgrading various versions. In the past had many issues after the 6th upgrades.
Where config file formats changed and didn't know that and after upgrading so many things broke.
I had to wipe the drive clean and start over. I was told the issue was I jumped from example 8.0 to 9.0
and was told that if I had 8.0 I had to first upgrade to the OS versions after 8.0 and not go to the directly latest one.

That is why I am doing this one by one to avoid any possible issues with the software and drivers loading old or wrong versions

right now looks like I don't need the kldload. Tis is my server and the gpu is on the main board. I don't have any GPU cards.
Let me know if it is ok to proceed. My guess is that it should be safe to proceed and do you think I need that kldload driver?
I assume that driver is for desktop machines pci gpu cards. I don't have any intense gpu card.
So, I think I can omit it. It's just I don't want to do something and then regret it later finding out
it was needed for some reason. I added it in because when I installed gnome it wouldn't show up
and the tutorial that showed how to install gnome it said to use this to load the right driver.
it's ether nvidia or radon ati drivers.
 
should I continue and upgrade to freebsd 13.4 ? I am trying to get to 14.1 the latest version.
However, I was told I need to upgrade to each version one step at a time.

If your plan is to go to 14.1 and that you can reach the command line every time then I am not sure if it is worth the effort to build the port graphics/drm-5X for every single version in between(13.2, 13.3, 13.4, 14.0, 14.1). I would skip that part, save the pain for the final step, that what I would do.
Before proceeding you should of course make backups.

Just so you know:
graphics/drm-510-kmod --> FreeBSD 13.X (no packages available for 14.X)
graphics/drm-515-kmod --> FreeBSD 14.X (no packages available for 13.X)
graphics/drm-610-kmod --> FreeBSD 14.X for newer graphics cards but IIRC in order to work one needs to build it from port

I did recently upgrade to 13.4 and also had to built from ports graphics/drm-510-kmod
Strangely X was half working, my desktop (i3wm) was okay but not Firefox, Kitty and probably few other apps, they were complaining about X.
I eventually could start XTerm and Firefox by passing "--safe-mode" option which helped me to fix the issue by using my VM poudriere (thanks to my notes ^_^).
 
If your plan is to go to 14.1 and that you can reach the command line every time then I am not sure if it is worth the effort to build the port graphics/drm-5X for every single version in between(13.2, 13.3, 13.4, 14.0, 14.1). I would skip that part, save the pain for the final step, that what I would do.
Before proceeding you should of course make backups.

Just so you know:
graphics/drm-510-kmod --> FreeBSD 13.X (no packages available for 14.X)
graphics/drm-515-kmod --> FreeBSD 14.X (no packages available for 13.X)
graphics/drm-610-kmod --> FreeBSD 14.X for newer graphics cards but IIRC in order to work one needs to build it from port

I did recently upgrade to 13.4 and also had to built from ports graphics/drm-510-kmod
Strangely X was half working, my desktop (i3wm) was okay but not Firefox, Kitty and probably few other apps, they were complaining about X.
I eventually could start XTerm and Firefox by passing "--safe-mode" option which helped me to fix the issue by using my VM poudriere (thanks to my notes ^_^).
I have a backup of the system with the 13.2 version. I don't plan on backing up inbetween.
Right now going to start upgrading from 13.3 to 13.4 then to 14.0 and then 14.1.

I don't even know if I needed that drm kmod module. I just remember when installing gnome it wouldn't work. I then read online
a tutorial that it needed it. They said to load the right one nvidia or ati. My server runs amd cpu's and it has an onboard ati gpu chip.
right now it's not loaded and it looks like gnome work fine. I don't know if it's really needed. I just know I had it and on 13.2 it got gnome to work.
I never had issues until upgrading to 13.3. Right now I can still boot into the desktop gui and use the GUI on desktop.

I am right now going forward to install the rest.

Also what do you mean by building the ports?

I normally use "pkg install' I know I can go to the ports tree and then do make install clean.

If you mean this. I did this but I uninstalled it and then installed using "pkg install" it asked me if I wanted to upgrade the software.. that it found a newer version. I hit yes.
So, I think I have the latest package installed.
I am going to upgrade the OS one by one until I get to the latest one 14.1 and then will put the rc.conf settings back and if it doesn't work.

I will do a pkg update and upgrade for each os installed and then uninstall it and reinstall using the latest one.

If it doesn't work and I can still run the GUI environment without it. I would just do that.
 
Below is screenshots of the desktop:
<snip>
Right, it looks like you have a AMD Opteron 8435 from 2009 with a ATI ES1000 graphics chip from 2007 on your motherboard.

If you intend to progress to 14.1-RELEASE anyway, I see no apparent reason why Xorg with this GPU is more likely to work (or not to work) on 13.x-RELEASE than on 14.1-RELEASE. When I were to upgrade, I'd be sure to get the latest patch of 13.3-RELEASE, read 14.0-RELEASE and 14.1-RELEASE (especially in the context of updating the bootloader) and upgrade from 13.3-RELEASE to 14.1-RELEASE.

While getting graphics things to work and as you already mentioned, do not enable any display/login server like x11/gdm, and start Xorg manually. When applicable: after boot verify that the relevant kernel module (like radeonkms) is loaded; use kldstat(8) before starting Xorg.

Contrary to a previous message, as to the situation of available packages of various graphics drm/kms kernel modules for 14.1-RELEASE, at the moment:
There is no need to build these packages from ports yourself.
Given that on 14.1 drm-61-kmod is the default, eventually 510 & 515 will get deprecated; I have no time line for that.

However, given that the ATI ES1000 is from 2007 and seems to be mentioned in radeon(4), as in
RV100 Radeon 7000(VE), M6, RN50/ES1000
this driver is probably the easiest way to a working Xorg driver that is appropriate for your ES1000; albeit using User Mode Setting (=UMS) and not Kernel Mode Setting (=KMS). For this use and, as mentioned in 5.4.3. Video Cards (see also xorg.conf(5)), specify in directory /usr/local/etc/X11/xorg.conf.d/ a conf file, for example 20-radeon.conf:
Code:
Section "Device"
	Identifier  "ES1000"
	Driver		"radeon"
EndSection

Note: in addition to this setting you might want to load a DRM/KMS driver, by specifying the kernel module in /etc/rc.conf:
kld_list="radeonkms" (not kld_list="amdgpu" because your GPU is from 2007) from graphics/drm-61-kmod*; you'll get drm-61-kmod by using pkg install drm-kmod on 14.1-R because this meta package pulls in the default (=drm-61-kmod). The loaded kernel module will not be used by the Xorg radeon driver; its use is merely for terminal use (Xorg not running) where it may be more power sufficient and enabling more resolutions for your text terminal.

If this (or when using KMS, see below) gives any problems post your Xorg log file.



If you like, instead of using UMS, you can try Kernel Mode Setting (KMS) with an Xorg KMS capable driver (i.e. for a KMS device) by using:
  1. graphics/drm-61-kmod*; available drm/kms kernel modules: radeonkms and amdgpu**
    file /boot/modules/radeonkms.ko referenced by kld_list="radeonkms" in /etc/rc.conf
    or
    file /boot/modules/amdgpu.ko referenced by kld_list="amdgpu" in /etc/rc.conf
  2. x11-drivers/xf86-video-amdgpu; availbale Xorg driver amdgpu**
    file: /usr/local/lib/xorg/modules/drivers/amdgpu_drv.so referenced by Driver "amdgpu" in a Section Device
    or
    using the standard Xorg modesetting(4) driver, file /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
    referenced by Driver "modesetting" in a Section Device

ad #1: specify in /etc/rc.conf
- A
kld_list="radeonkms"
or
- B
kld_list="amdgpu"

ad #2: specify in directory /usr/local/etc/X11/xorg.conf.d/ a file, for example ATI-ES1000.conf
- C
Code:
Section "Device"
	Identifier  "ES1000"
	Driver		"modesetting"
EndSection
or
- D
Code:
Section "Device"
	Identifier  "ES1000"
	Driver		"amdgpu"
EndSection

Given that you have the following combinations:
A-C
A-D
B-C
B-D

In my estimation B-C and B-D are not likely to work because B is for rather recent AMD GPU-s and your ATI ES-1000 is from a previous era. A-C may work, but my guess is that A-D is probably the best chance you have to get KMS to work.



If all attempts fail, at long last, you should be able to deploy the vesa or scfb Xorg driver: Handbook - Xorg

___
* If this fails, then (instead of graphics/drm-61-kmod) use the package graphics/drm-510-kmod; on 14.1-RELEASE you must install this explicitly with pkg install drm-510-kmod

** To emphasize: there are two different files representing two drivers that each have a distinct function in the graphics stack; notably both are referenced by the same label amdgpu, which can be rather confusing.
 
Last edited:
I just upgraded to 13.4 and then proceeded to upgrade to 14.0

I did everything for 14.0

but when I had to reboot it and then
do the last
freebsd-update install
command it would take a snapshot of the boot image.
Then start installing updates.

I don't know if it's froze or if there's a huge amount of stuff needed to be installed.
I kept going on for hours.

I decided to leave it overnight and I woke up this morning to check on it and it's still at this level.
It's been more than 12 hours. Is this normal when upgrading to major numbers? like going from 13.4 to 14.0?
 
Is this a ZFS on root system?
Did you update the boot code as specified in 14.0-RELEASE release notes?
Any noticable disk activity?
Yes' it's on a zfs.
I been running it for 2 days. It just finished right now.
not just updating the packages. There was a message to remove the old ports
and rebuild the new ones for the new version 14.0
I am using the pkg install and upgrade commands. I assume this is what it will automatically do.
 
Back
Top