On Thu, Jan 28, 2021 at 09:22:13PM +0100, Emmanuel Vadot wrote: > On Thu, 28 Jan 2021 12:02:55 -0800 > Steve Kargl <s...@troutmask.apl.washington.edu> wrote: > > > It works to the extent that the X server loads and > > the fvwm2 window manager comes up with my normal > > desktop. In fact, I'm typing this in a xterm at > > that moment. > > > > No I meant does the previous version of the ports works or was it > since today's update ? >
I lost the information about which version of drm-current-kmod I had previouslu installed. The 2 Dec 2020 world/kernel/drm worked without an issue. Looking at 'svn log' on the Makefile for 'drm-current-kmod' shows 5.4.62.g20201003 for 2020-10-03 and an update to latest version on 2020-11-09 (but no version number info). So, I was likely running the 2020-11-09, and so that version did not have the chip reset message. The issue may be in the linuxkpi and not directly drm-current-kmod. I was hoping that by reporting 'chip reset on rcs0' would ring a bell for someone. This is all likely academic as I just saw John Baldwin's email that stated i386 support is being dropped in FreeBSD-current. I suppose my next update will move the laptop to amd64. -- Steve _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
