Good news today

drhowarddrfine official release isn't till the 16th, or at least planned for then. What I think @fjdir did was upgrade to RC's, then if you ran pkg upgrade on the RC, you wound up with 15.1-RELEASE. I have a vm I've been updating to RC's and today just ran pkg update and pkg upgrade and it upgraded to 15.1-RELEASE without me doing anything, but pkg upgrade and pkg update. For me, I've only done it on VM's so far, I'll probably wait for the official release announecment, but it seems as if updating to RC's and then RELEASE is working.
 
drhowarddrfine official release isn't till the 16th, or at least planned for then. What I think @fjdir did was upgrade to RC's, then if you ran pkg upgrade on the RC, you wound up with 15.1-RELEASE. I have a vm I've been updating to RC's and today just ran pkg update and pkg upgrade and it upgraded to 15.1-RELEASE without me doing anything, but pkg upgrade and pkg update. For me, I've only done it on VM's so far, I'll probably wait for the official reaease announcment, but it seems as if updating to RC's and then RELEASE is working.
Building 15.1 from anonymous ftp freebsd.org
I had to disable VIA padlock RNG in RC2. No idea what that is. See it if compiles now.
 
Kernel panic page fault trap 14

I don't see this on the official release page yet.
Is this related to the drm module? Be sure you are using graphics/drm-latest-kmod and not graphics/drm-kmod if using the meta-port (the latter pulls in the driver for 15.0) or the correct version of the package for 15.1 (1501000_9); both are present in the repository:
Code:
$ pkg search -x '^drm'
drm-515-kmod-5.15.160.1500068_10 Direct Rendering Manager (DRM) GPU drivers
drm-61-kmod-6.1.128.1500068_10 Direct Rendering Manager (DRM) GPU drivers
drm-66-kmod-6.6.25.1500068_10  Direct Rendering Manager (DRM) GPU drivers
drm-kmod-20260508              Direct Rendering Manager (DRM) GPU drivers metaport
drm_info-2.10.0                Dump info about DRM devices
drm-515-kmod-5.15.160.1501000_9 Direct Rendering Manager GPU drivers
drm-61-kmod-6.1.128.1501000_9  Direct Rendering Manager GPU drivers
drm-66-kmod-6.6.25.1501000_9   Direct Rendering Manager GPU drivers
drm-latest-kmod-6.9.1501000_1  DRM drivers modules
 
it will be tied to drm-612-kmod
That would be graphics/drm-kmod, not graphics/drm-latest-kmod.

graphics/drm-kmod has some logic to 'automagically' pick a version:
Code:
.if ${OPSYS} != FreeBSD
IGNORE=		not supported on anything but FreeBSD (missing linuxkpi functionality)
.else
.  if ${OSVERSION} >= 1500509 && ${ARCH} == amd64
RUN_DEPENDS+=	${KMODDIR}/drm.ko:graphics/drm-612-kmod
_DRM_ARCHS=	amd64
.  elif ${OSVERSION} >= 1500031 && ${ARCH} == amd64
RUN_DEPENDS+=	${KMODDIR}/drm.ko:graphics/drm-66-kmod
_DRM_ARCHS=	amd64
.  else
RUN_DEPENDS+=	${KMODDIR}/drm.ko:graphics/drm-61-kmod
_DRM_ARCHS=	amd64 powerpc64 powerpc64le
.  endif
.  if ! ${_DRM_ARCHS:M${ARCH}}
IGNORE=		not supported for this configuration
.  endif
.endif
 
As mentioned, my laptop automatically updated to RELEASE. However, a headless machine I have, that wouldn't be a disaster if I had to reinstall, though I'd rather not of course, was also updated to RC3. However, though its config seems to be the same as the laptop's it's not updating to RELEASE. Which is due, tomorrow, by the way.
 
Well, I upgraded my secondary machine, which went fine. As mentioned, that headless one wasn't upgrading, so I just edited its /usr/local/etc/pkg/repos/FreeBSD.conf to match the one that upgraded successfully, then it pulled in the necessary packages and upgraded to 15.1. All machines are on packagebase. Pretty straight forward.
 
Ok, this might be a longish one, and I even thought of giving it its own thread, but anyway...

My main workstation is an older Dell with an Nvidia card. I went to update it via the instructions, but it said it was up to date, though it was running 15.0-p10. So, I finally realized that on both this machine and the headless one that I couldn't update until I edited what was in /usr/local/etc/pkg/repos that both this one and the headless one had a FreeBSD-base.conf as well as FreeBSD.conf, and that FreeBSD.conf has a line
Code:
 FreeBSD-base: { enabled: yes }.
So yesterday, I fixed the headless one by renaming the FreeBSD-base.conf to FreeBSD-base.conf.orig. I don't know why these two machines had that file and the others didn't--it must have come from when I first converted them to pkgbase. At any rate, I renamed the file to conf.orig and I was able to upgrade the main box to 15.1-RELEASE.

Now, when I, following instructions, upgraded kmods, nothing happened with the nvidia kmods. So, when I rebooted and tried startx it gave a message that the machine was turning off. It restarted in single user mode as a drive hadn't unmounted right, but running fdisk -fy on that disk fixed that problem and upon typing exit, I was back to normal multi user mode.

So, I did what I usually do, when running into nvidia issues. I upgraded ports to the latest and used portmaster to install nvidia-drm-kmod and nvidia-drm-66-kmod. (I used to ignore the drm-66 but T-Aoki had mentioned in another thread that it is sometimes needed). After installation (which also pulled in nvidia-kmod-580) I rebooted, and now X was working as it should be.

So, the two messages I would take from this is one, if it ain't upgrading, make sure all you have in /usr/local/etc/pkg/repos is a FreeBSD.conf. It should have the line about base enabled in it. Hopefully, it's obvious that I mean if you're updating with pkgbase, dunno about freebsd-update. And secondly, if you have nvidia drivers and the update kmod doesn't pull in new ones, update those. I don't know if it was necessary to use the ports or if a simple pkg upgrade would have done it. But, hopefully this will help someone. I doubt I'm the only one dumb---err--careless--enough to overlook that FreeBSD-base.conf file, and I suspect that others who did an early conversion to pkgbase may have it as well.[/code]
 
Back
Top