Date: Sun, 13 Oct 2019 17:06:36 -0700 From: John Kennedy <warlock@phouka.net> To: Chuck Tuffli <ctuffli@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Confused about i915kms on 12.1 Message-ID: <20191014000636.GB91243@phouka1.phouka.net> In-Reply-To: <CAKAYmMJhSQBr8JHuUXKHy4KFR_YLk6ta53PMaSt-yd-OKvZNBA@mail.gmail.com> References: <CAKAYmM%2BwqRkro5SDBtdWddE8x94DVdSTy6-g9kR9fEBEF0=pJQ@mail.gmail.com> <20191013201135.GA91243@phouka1.phouka.net> <CAKAYmMJhSQBr8JHuUXKHy4KFR_YLk6ta53PMaSt-yd-OKvZNBA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 13, 2019 at 02:42:46PM -0700, Chuck Tuffli wrote: > Many thanks to Pete and John. See inline below > ... > I upgraded the box per the release announcement: > freebsd-update upgrade -r 12.1-RC1 > freebsd-update install > with the prescribed reboots and installs. Afterwards, I did a pkg > update and pkg upgrade. Note, I don't install anything from ports. The FreeBSD handbook might have the extra bits you were missing: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Bonus note: the 2nd "freebsd-update install" after the reboot to delete some now-obsolete files. The announcement really doesn't talk about upgrading ports. In 23.2.3.2 ("Upgrading Packages After a Major Version Upgrade") they say to do this (among other things): pkg-static upgrade -f So pkg-static (vs pkg) in case you have shared-library problems with the dynamically-linked pkg, and then -f to "force" the upgrade. That may be the missing piece here in getting rid of your previous-kernel packages even if they might otherwise run just fine. > $ pkg info drm-fbsd12.0-kmod-4.16.g20190814 | grep -i version > Version : 4.16.g20190814 > FreeBSD_version: 1200086 > This version is for FreeBSD 12.0. Clearly the old 12.0-* kernel. > The advice I received was 'you need to build drm-kmod from ports'. I > don't typically have a ports tree, so I did: > # portsnap fetch > # portsnap extract > # cd /usr/ports/graphics/drm-kmod > # make && make install > After doing the makes, my immediate thought was 'that finished too fast'. That is apparently a meta-port that doesn't behave like you'd expect. I had to do a similar thing for myself. But I think the "-f" might have fixed it for you above, if the packages were built on the repo (below). > If, instead, I follow Pete's advice and run make package in > /usr/ports/graphics/drm-fbsd12.0-kmod, a) make appears to do something > and b) the resulting package allows my laptop to boot to a graphical > desktop. And the FreeBSD_version looks correct: > $ pkg info drm-fbsd12.0-kmod-4.16.g20190814 | grep -i version > Version : 4.16.g20190814 > FreeBSD_version: 1201000 > This version is for FreeBSD 12.0. > > I did go back and verify that a pkg install drm-kmod appears to > install the same (older) i915kms.ko as pkg install drm-fbsd12.0-kmod. > Out of curiosity, is the new world order that I'll always need to > compile drm-kmod from ports, or did I hit a window where packages > hadn't quite caught up to ports? I don't know. Finding out which package your .ko file came from would tell us a bit there. I've just got in the habit of build all my packages myself because I can get into the bleeding-edge area and run into problems like that. I suspect that the official answer would be "hell no" and this is the type of experience that the FreeBSD folks like to see for the purposes off adding things to UPDATING and such. But I know that it is going to take a while for their poudraire to grid through all the ports In any case, I'm glad we got you up and running.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191014000636.GB91243>