DRM failure on 15.0

charlie137

charlie137

img_2788-jpeg.24286

After upgrading from 14.3 drm kmod died. Tried Building from source both drm and gpu kmod, but no change.
 

Attachments

  • IMG_2788.jpeg
    IMG_2788.jpeg
    476.1 KB · Views: 382
With a major version upgrade you must reinstall all your ports/packages. This poses a problem with kernel modules because you need to upgrade the kernel first, and those kernel modules will immediate fail.

My advice is, disable those modules during the OS upgrade. And keep them disabled until you're done upgrading the base OS and your ports/packages. Then you can enable them again.
 
SirDice said:
My advice is, disable those modules during the OS upgrade. And keep them disabled until you're done upgrading the base OS and your ports/packages. Then you can enable them again.
Click to expand...
Best advice ever.

My opinion on what you may be able to do. Others will chime in if they have additional info (even if it's don't do that)

If you are using ZFS (you can probably do this with UFS too), you should be able to boot off live/install media and manually mount the broken boot environment. Then go and edit your /boot/loader.conf and /etc/rc.conf, save changes, reboot and remove the live/install media. I believe the system will boot enough for you to correctly finish the update (including the pkg -f upgrade); this may involve pkg delete any drm packages you have installed before running pkg -f upgrade. Then reboot into the console, do the pkg install of the correct drm packages. Then go look in /boot/firmware and see if the bin files are there. If not, then you may need to install more stuff, perhaps gpu-firmware-kmod packages.
 
LibreQuest said:
Would it be best to do the upgrade from single user mode?
Click to expand...
If you can, sure. But keep in mind filesystems are read-only or not mounted at all. And for packages you're going to need network (which won't be active either).

Just keep things simpler, disable all the 'extra' modules from kld_list (just remark the line in rc.conf) and perhaps disable a bunch of services but keep sshd(8) enabled (especially if you're doing the upgrade remotely). Do the entire upgrade process (OS, ports/packages). And once you're done start enabling things, step by step, again.
 
SirDice said:
If you can, sure. But keep in mind filesystems are read-only or not mounted at all. And for packages you're going to need network (which won't be active either).

Just keep things simpler, disable all the 'extra' modules from kld_list (just remark the line in rc.conf) and perhaps disable a bunch of services but keep sshd(8) enabled (especially if you're doing the upgrade remotely). Do the entire upgrade process (OS, ports/packages). And once you're done start enabling things, step by step, again.
Click to expand...
I will give that a try later on thank you for the advice. The install on my laptop (that I am using now) went without issue. I did follow the prompts during the update on this and it seemed to work with i915kms enabled. But for some reason it was not ok with something I had enabled on the other system.
 
SirDice said:
Note that kernel modules that are part of FreeBSD itself are not a problem. They're updated along with the kernel, so they should always be in sync. Problems typically happen with kernel modules installed from ports/packages, like the graphics/drm-kmod port/package. The emulators/virtualbox-ose-kmod is also notorious for breaking during an upgrade.
Click to expand...
I tried your suggestions did the upgrade again but still have kernel panic. Rolling it back again. 😟 Beige Goby is borked on 15.
 
LibreQuest said:
Would it be best to do the upgrade from single user mode?
Click to expand...
The first phase (# freebsd-update upgrade ...) only checks your current system and fetches the required patches, but doesn't touch your system at all. It requires a connection and can safely be done in a multi-user environment, even from a terminal emulator under X.
 
If you were using graphics/drm-510-kmod, you need to transit to graphics/drm-66-kmod (default for 15.0), graphics/drm-61-kmod or graphics/drm-515-kmod. Note that they need to be built on matching kernel with yours.

For official 15.0-RELEASE, official pkgs are built on official 15.0-RELEASE kernel.

And graphics/drm-510-kmod has this in its Makefile, disallowing to be built / installed any versions that are 14.2 or later.

As currently all supported *-RELEASE has single minor release (15.0, 14.3 and 13.5 respectively), so if pkgs in FreeBSD-ports-kmod are somehow problematic, you can try forcing FreeBSD-ports repo for kmod ports with -r option.

For firmware part, lost track with, but someone forgot to upgrade firmwares and being bitten.
Have you tried fwget(8)?
 
T-Aoki said:
If you were using graphics/drm-510-kmod, you need to transit to graphics/drm-66-kmod (default for 15.0), graphics/drm-61-kmod or graphics/drm-515-kmod. Note that they need to be built on matching kernel with yours.

For official 15.0-RELEASE, official pkgs are built on official 15.0-RELEASE kernel.

And graphics/drm-510-kmod has this in its Makefile, disallowing to be built / installed any versions that are 14.2 or later.

As currently all supported *-RELEASE has single minor release (15.0, 14.3 and 13.5 respectively), so if pkgs in FreeBSD-ports-kmod are somehow problematic, you can try forcing FreeBSD-ports repo for kmod ports with -r option.

For firmware part, lost track with, but someone forgot to upgrade firmwares and being bitten.
Have you tried fwget(8)?
Click to expand...
i tested 515 yesterday and it worked fine on 15
 
You must log in or register to reply here.
Back
Top