Solved Userland mismatch has finally beaten me, or has it?

freebsd-version -kru
Not sure if it is too late to respond to this, but below is what I got after reinstalling my hard drive with FreeBSD on it.

Code:
Simon@Asus ~]$ freebsd-version -kru
15.0-RELEASE-p14
15.0-RELEASE-p14
15.0-RELEASE-p14
 
  • Like
Reactions: mer
Are you using freebsd-update to update FreeBSD itself?
I honestly cannot remember all of the steps which I may have take a week or two ago, but I've taken some time away from this, and now I think that I have a clearer vision of the path ahead of me. Please feel free to take a look at my written plan, and tell me that I'm all wet.
 
Looks like you are using freebsd-update, so people will be able to assist you accordingly.

FreeBSD itself is great, the upgrades are smooth, except for these graphics driver update issues.

I don't use them so can't help, but see they do cause a bit of grief, especially around version upgrade time.
 
Well, my most recent attempt to get through the upgrade process ended in a non bootable system, but I'm pretty sure that the below set of written instructions might get me over the hump this weekend. Any feedback will be gladly welcomed.
Code:
The steps I had listed here earlier didn't work, so I deleted them. 
     
END

Also, wish me luck.
 
Last edited:
9. Issue the below command to diplay kern release date.

sysctl -n kern.osreldate

Before upgrade the number displayed was, 1500068.

It's a long time since I've run CURRENT, and I've never run STABLE, but I think 1500068 is a point on 15-STABLE, on releases the last three digits are 000 in my experience. Were you aware that you are on a development branch?

On the subject of freebsd-update, if you installed with pkg base, it should refuse to run.
 
It's a long time since I've run CURRENT, and I've never run STABLE, but I think 1500068 is a point on 15-STABLE, on releases the last three digits are 000 in my experience.
1500068 is of releng/15.0, which 15.0-RELEASE{-p*} are built from.
You'll mangled with minor releases that are NOT *.0.

On *.0-RELEASE, corresponding stable branch is branched from main (aka CURRENT) and release engineering starts from there. Within this periods of time, __FreeBSD_version still could bumped many times to get last minutes feature additions that are STRONGLY wanted for the *.0-RELEASE (basically avoided for not-so-important feature changes).
And once corresponding releng/*.0 is branched, stable branch is bumped to *500 in preparation for upcoming *.1-RELEASE.

On release engineering for *.1 and later, stable is marked as PRERELEASE and releng/*.* is branched with __FreeBSD_version of *000 as you mentioned. Then stable branch is marked as STABLE again and bumped to *500 again (for upgrades from 15.0 to 15.1, 1500500 to 1501500).

On releng/* branches, basically large changes that need __FreeBSD_version bumps are NOT allowed.
But exceptions could be huge security upgrades that __FreeBSD_version bump is unavoidable.

Edit: Additional example.
  1. Commit to stable/15 when release engineering for 15.2 started
  2. Commit to stable/15 when releng/15.2 branched
 
Previously you said you were using freebsd-update, but now you are saying that you used or are going to use pkg (point 4 in your list) to try and do the OS upgrades?
Yeah, I know. I tried one method,then that didn't work, so I wrongfully assumed that the other choice must be the right answer. Now I realize that one of my big mistakes was trying to re add my old Nvidia packages from a folder on a separate drive. Now I realize that the base package system upgrade is the correct process, but I just need to handle these Nvidia drivers. I fetched the below packages and have placed them into a folder on a second drive. If the pkg install command doesn't work, I will try to re add them from the folder. I think that will work.
Code:
drm-66-kmod-6.6.25.1501000_11~2$eiic5crk.pkg
nvidia-drm-66-kmod-580-580.178.04.1501000~2$qd886t8m.pkg
nvidia-kmod-580-580.178.04.1501000~2$6u9ba87e.pkg
 
Okay, so I just realized that the one of the Nvidia packages stored in my backup folder is named, nvidia-drm-66-kmod-580-580.142.1500068.pkg. The current userland on my machine is, 1500068. I'm trying to upgrade this operating system to, 1501000. So, that probably means that I was following the correct upgrade procedure in the first place, more or less, but I kept screwing things up by trying to use a package which ended in 1500068, while I'm trying to upgrade my operating system to 1501000. Well, do I really feel dumb right now? Yes I do.
 
Cedric , on 10-10-26 the Quarterly REPOS were updated to binaries built on freebsd 15.1 . All the Nvidia drivers , any version ( 595, 580 a.s.o) available on the Quarterly Repo is for 15.1 ( eg all the kmods are 150100 or higher ) If you try to mix in a 1500068 version driver your in trouble.

Delete all you existing DRM and Nvidia packages
Reboot
Upgrade to FreeBSD base to 15.1
Reboot
Reinstall DRM and Nvidia Packages ( 580 version if you have an old GPU )
finally uppgrade the non-base packages.
 
Well, after about the fifth or sixth try, I finally managed to get across the finish line with my desktop still in tact! However, for some reason the nvidia-xconfig command is no longer on my system, and I have one or two minor errors here and there, but I think that I've finally beaten the upgrade process. Also, the written process I had didn't go exactly has planned, and I will try to post a follow up regarding exactly what I did, in case anyone else gets stuck like I did.
 

Attachments

  • 110726_After_Upgrade_b.jpg
    110726_After_Upgrade_b.jpg
    65.7 KB · Views: 31
Well, I tried to keep pretty detailed notes of the steps I took to get through the upgrade process, and I think that the below is pretty accurate to what I did.
Code:
1.  Use the, pkg lock –show, command to identify all of the locked packages on system.

2.  Use the, pkg unlock -y, command to unlock each of the above locked packages identified in step one.  You must repeat the unlock command for each and every locked package listed by the command in step one in order for the rest of the process to work.

Example: pkg unlock -y nvidia-settings  

3.  Reboot and open a new terminal.  Enter the below command to identify all of the Nvidia packages on the system.

Example: pkg info | grep nvidia  

4. Use the, pkg delete -y, command to delete each and every package listed by the pkg info command in step three.

Example: pkg delete -y nvidia-settings
   
5.  Edit /etc/rc.conf and place a # mark in front of the below line to comment it out.

Example: # kld_list="nvidia-modeset nvidia-drm cuse fusefs"
   
6.  Reboot, and login as root and enter the below commands.

pkg upgrade -r FreeBSD-base
(above to ensure health of current package state)
   
pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base
(upgrade base system)
   
pkg upgrade -r FreeBSD-ports-kmods
(upgrade third‑party kernel modules. At this point had to adjust name server in resolv.conf, in order to overcome "srv" error.  Commented out old name server and replaced it with, nameserver 1.1.1.1
, and nameserver 8.8.8.8. Was then able to continue.)
   
find /etc /usr/local/etc -name '*.pkgnew' -ls
(scan for configuration file update conflicts that require manual updates)
   
7.  Mount the efi partition and update boot loader.
   
 mount_msdosfs /dev/ada0p1 /boot/efi
(mount the efi partition. Received an error stating device was busy. Continued to next step with no problems.)
   
cp /boot/loader.efi /boot/efi/efi/freebsd/loader.efi
cp /boot/loader.efi /boot/efi/efi/boot/bootx64.efi
(upgrade the boot loader)
   
8.  Rebuild legacy graphics and reboot with below commands.

pkg bootstrap -f
(re-bootstrap the package management system)
   
pkg upgrade -y
(bring installed packages up to date)
   
pkg install -y drm-66-kmod x11/nvidia-driver-580
pkg install -y nvidia-drm-66-kmod-580
pkg install -y linux-nvidia-libs-580
(above reinstall Nvidia driver.  Entered each line separately.)
   
nvidia-xconfig
(modify /etc/X11/xorg.conf. No longer seems to exist.)
   
9.  Remove the # symbol from the below line within /etc/rc.conf.

Example: kld_list="nvidia-modeset nvidia-drm cuse fusefs"
   
10.  Reboot the machine, if everything goes well, then the lightdm greeter should return.

11.  Log in and issue the below command to display kern release date.

sysctl -n kern.osreldate  

After upgrade the number displayed is now, 1501000.
I guess that many of my earlier problems probably stemmed from the fact that I was obsessed with trying to hold onto the Nvidia drivers from before the upgrade, but of course that didn't work, and then I went down a bunch of wrong paths before I finally figuring out that those old drivers could no longer be a part of my installation. Hopefully the above might be useful to someone.
 
Back
Top