Shared object "libmd.so.6" not found, requiere by "Xorg"

Got a new, quite big, monitor, but I cannot read what's on that tiny picture.
 
freebsd-version(1) shows (according to its man page)
Code: 
     If several of the above options are specified, freebsd-version will print its output as below.
     the installed kernel version first, then the running kernel version, next
     the userland version, and finally the userland version of the specified
     jails, on separate lines.
Looking into the photo, your userland is still at 14.3-RELEASE-p6, while both installed and runnig kernel is at 15.0-RELEASE, thus, mis-match happenes.

Have you restarted your computer after the last phase of freebsd-update?
Or even forgotton the last run?
 
1764946528384.jpeg
 
Still need to update the userland before updating your ports/packages. So that's after the second freebsd-update install, and before the third and final freebsd-update install.
 
Maybe FreeBSD needs staging for upgrade like OS/2 (and maybe Windows, too) did.
If I recall correctly, when applying service packs, OS/2 saved dynamic link libraries (DLLs) into temporary place and list on which directory each DLLs to be installed into hidden temporary system file, install anything "not write-locked" components, register special device driver (would've been filter driver) into \config.sys, then restarts.
On restart, when updated kernel start running, processing \config.sys and loads the special device driver as specified, then the driver reads stored list and overwrites not yet locked DLLs with updated ones, delete list and unregister itself from \config.sys, and finally start up the OS.

On FreeBSD, maybe special rc.d script could do.

Note that, if I recall correctly, OS/2 write-locks DLLs when loading them into memory, at least for genuine system DLLs. So the procedure above was mutually unavoidable on upgrades.
 
T-Aoki said:
Maybe FreeBSD needs staging for upgrade like OS/2 (and maybe Windows, too) did.
Click to expand...
The third and final freebsd-update install removes the 'old' 14.x libraries. So typical userland applications will still be able to link to the old version of the libraries and would still work. That's why you need to reinstall ports/packages between the second and third run of freebsd-update install.

Problems only happen with kernel modules installed from ports/packages. Ideally those should simply fail to load, but apparently it still tries to load modules built for 14.3 on the 'new' 15.0 kernel and it then crashes the system.
 
judd said:
I'm doing that, package upgrade and then reboot ??
Click to expand...
If it completed without issues, yes, try it.

If it rebooted and booted 15.0-RELEASE correctly (check freebsd-version -urk). Check if all your packages are complete; pkg version -vRL= Pay attention if anything shows up, especially if there's anything with ?.
 
judd said:
Okay, that's 626 packages, we'll see...
Click to expand...
Yeah, that might take a while. It needs to replace everything you have installed with packages that have been built for 15.0. Or else you're going to run into "missing" libraries as they will be looking for the libraries that came with 14.3.
 
SirDice said:
If it completed without issues, yes, try it.

If it rebooted and booted 15.0-RELEASE correctly (check freebsd-version -urk). Check if all your packages are complete; pkg version -vRL= Pay attention if anything shows up, especially if there's anything with ?.
Click to expand...
1764951662625.jpeg
 
Hmm, wondering why a bunch of packages appear to be 'orphaned', those should be available.

What does pkg repos show? On 15.0 the package repository got renamed from FreeBSD to FreeBSD-ports. Maybe you have a /usr/local/etc/pkg/repos/FreeBSD.conf that's now pointing in the wrong direction?
 
Smells like you've not yet done pkg bootstrap -f (or pkg-static bootstrap- f) AFTER you've sanely finished upgrading your base to 15.0-RELEASE.
 
T-Aoki said:
Smells like you've not yet done pkg bootstrap -f (or pkg-static bootstrap- f) AFTER you've sanely finished upgrading your base to 15.0-RELEASE.
Click to expand...
It's showing in the picture of post #31, so that should be good. But even with an 'old' pkg(8) from 14.3 it should still not show all those orphaned packages. When a package is 'orphaned' it means it cannot be found in the repository. I'm quite sure x11/xrandr and few others on that picture are available.
 
While on version 15.0, I ran `pkg update -f` and the orphaned packages in the screenshot changed when I ran `pkg upgrade -f`. Now updating... we'll see what happens next with `pkg version -vRL=`
 
judd said:
I ran `pkg update -f` and the orphaned packages in the screenshot changed
Click to expand...
Right. It actually checks with a locally cached "catalogue", that may have been in some odd or weird state. pkg update -f forces an update of that catalogue. It has the information of what's available in the repository. Because it was in this weird state pkg-version(8) could not figure out if those packages were available, so it figured they must all be 'orphaned'.

Code: 
     -f, --force
            Force a full download of the repository catalogue without regard
            to the respective ages of the local and remote copies of the
            catalogue.
pkg-update(8)
 
Well, it seems there's been some progress, at least it's not throwing away so many orphaned packages anymore...
1764968849147.jpeg
 
You must log in or register to reply here.
Back
Top