Date: Fri, 11 Sep 2020 16:50:11 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Niclas Zeising <zeising+freebsd@daemonic.se> Cc: Pete Wright <pete@nomadlogic.org>, x11-list freebsd <freebsd-x11@freebsd.org> Subject: Re: drm-*-kmod port for Comet Lake Message-ID: <CAN6yY1u5wCrYS=Zj619=e23fR3D0kPOR-mz6ZGvAW5i_62MW0g@mail.gmail.com> In-Reply-To: <1a63a112-1df1-783a-e5e6-c79be0dc92b0@daemonic.se> References: <CAN6yY1ua%2B6NfMOJS2fBBxoCMh6=ou0FV4fSGBuaQsfON1f32rQ@mail.gmail.com> <14637168-ee43-3983-ee7f-20fa77dcfcde@nomadlogic.org> <CAN6yY1vfg0EHe2YTV4=yDTxQ1cHiMvBA52jJW955ejnm4MqVFA@mail.gmail.com> <331881e5-5053-6f49-b501-48ce8eb2d429@daemonic.se> <CAN6yY1tRMwxXHn4uUVWERhvpUxPMhqbAKmOYak6Tjfq-Ze07NA@mail.gmail.com> <1a63a112-1df1-783a-e5e6-c79be0dc92b0@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
I think I have found the problem and it's not X related. In a thread on current@ I have reported an issue with the system freezing. This has happened repeatedly, often while I was installing packages. It appears that, in at least three cases, some files that appeared to have been installed were lost after a freeze. It looks like several files from xorg-server were simply lost. (Well, actually lost when they were not year fully witten with all metadata at the time of the freeze.) So this was not an X issue at all. It's a file system problem that is likely unfixable involving a system livelock as files were written to disk. I am seeing serious X issues on the system, but that is for a separate thread. Thanks, Niclas! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Wed, Sep 9, 2020 at 8:31 AM Niclas Zeising <zeising+freebsd@daemonic.se> wrote: > On 2020-09-09 16:37, Kevin Oberman wrote: > > On Wed, Sep 9, 2020 at 7:10 AM Niclas Zeising > > <zeising+freebsd@daemonic.se <mailto:zeising%2Bfreebsd@daemonic.se>> > wrote: > > > > On 2020-09-09 02:30, Kevin Oberman wrote: > > > Thanks! As often happens, I got it working just a little after I > > sent this > > > report. The problem is that I installed from packages and i > > didn't realize > > > that the default xorg-server defaults to devd and does not > > include the > > > modesetting driver. I pulled down the ports tree and reinstalled > > > xorg-server and that got X working. > > > > This sounds like you have enabled DEVD manually in the ports options. > > The xorg-server version distributed with FreeBSD 12 and 13 uses > > udev/evdev, and the xorg-drivers meta package includes a dependency > on > > xf86-input-libinput. The modeseteting driver is part of xorg-server. > > Regards > > -- > > Niclas > > > > > > Very odd, but I installed the package on Sunday (6-Sept.) and my system > > had no /usr/local/lib/xorg/modules/drivers/modesetting_drv.so. Only scfb > > and vesa. I built the port (once I had downloaded the ports tree) and it > > had the modesetting driver and X started up just fine. I was assuming > > that udev vs. devd was the issue, as that is the only option (other than > > wrapper). Is installing modesetting controlled by something else? > > The modesetting driver should be built and installed in all cases, on > all versions of FreeBSD. devd is still the default on FreeBSD 11, but > udev is the default on 12 and later. > If you still have the package (the actual .txz file) it might be > intereseting to see if modesetting_drv.so is in the file. I find it > strange that it hasn't been installed by default. There have been no > reports from the pkg build cluster about the xorg packages either. > Regards > -- > Niclas >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1u5wCrYS=Zj619=e23fR3D0kPOR-mz6ZGvAW5i_62MW0g>