[Bug 250700] drm-kmod i915kms binary package not working on 12.2-RELEASE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Dec 13 16:31:31 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250700
Bruce Lilly <bruce.lilly at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruce.lilly at gmail.com
--- Comment #15 from Bruce Lilly <bruce.lilly at gmail.com> ---
First, other things are affected: even after rebuilding drm-fbsd12.0-kmod, sddm
dumps core and gdm just doesn't work. Rebuilding both (and their many
prerequisites) from source appears to work. There are other programss that
appear to have problems (e.g. a couple from recent logs):
kernel: pid 47952 (mate-terminal), jid 0, uid 1000: exited on signal 11 (core
dumped)
kernel: pid 51154 (conftest), jid 0, uid 0: exited on signal 11 (core dumped)
It appears that I'll be dealing with update-related bugs for quite some time.
Second, this is an epic failure of release engineering: [as of this writing]
neither the Release notes
(https://www.freebsd.org/releases/12.2R/relnotes.html) nor Hardware notes
(https://www.freebsd.org/releases/12.2R/hardware.html) mention or even hint at
this set of problems. Per contra, the Release notes state "[amd64,i386] Binary
upgrades between RELEASE versions (and snapshots of the various security
branches) are supported using the freebsd-update(8) utility."
In fact, update from 12.1 via freebsd-update didn't work. `freebsd-update
rollback` also didn't work, resulting in "ld-elf.so.1: /lib/libc.so.7:
Unsupported relocation type 37 in non-PLT relocations". System was left
utterly unusable (couldn't even log in).
I then had to install from scratch, and of course installation of 12.2-RELEASE
has the same problem with non-working display (even the console is
unsatisfactory, because default 800x600 VESA resolution doesn't work well on a
1366x768 laptop display). N.B. without another working OS or device, that
would have been a complete disaster: no X essentially means no browser and no
practical way to even search for a solution.
When it's working, FreeBSD is almost as usable as a desktop OS as a
systemd{ebacle,isaster,estroyer}-less Linux distribution (e.g. Devuan).
"Almost" because of lack of some things (gparted, for example) and non-POSIX
utilities (e.g. ps). But as long as disasters such as the above utter failure
of update/rollback/installation exist, I cannot in good conscience recommend
FreeBSD to others. So it's also an epic failure on the advocacy front.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-x11
mailing list