Date: Thu, 29 Sep 2016 08:17:52 -0500 From: Bob Willcox <bob@immure.com> To: Pete Wright <pete@nomadlogic.org> Cc: freebsd-x11@freebsd.org Subject: Re: gfx-next update: drm-4.8-rc2 tagged in drm-next Message-ID: <20160929131751.GW845@rancor.immure.com> In-Reply-To: <3d7950a2-0312-0a17-cce5-9eece2430daa@nomadlogic.org> References: <157496f7268.ac5eb5ca278618.8741026532558973404@nextbsd.org> <20160920212545.GU8480@rancor.immure.com> <d93f0a38-f2c1-ff61-a1db-6efad39c1ffd@nomadlogic.org> <20160920221954.GV8480@rancor.immure.com> <20160921233610.GI845@rancor.immure.com> <9582349b-cf1e-1d75-4784-a1d712aedac4@nomadlogic.org> <1574f2fb8aa.e60df17234511.2445927962639207447@nextbsd.org> <20160923122301.GK845@rancor.immure.com> <20160929014049.GV845@rancor.immure.com> <3d7950a2-0312-0a17-cce5-9eece2430daa@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 28, 2016 at 07:42:39PM -0700, Pete Wright wrote: > > > On 9/28/16 6:40 PM, Bob Willcox wrote: > > > > > Well, I may have spoken a little too soon. I switched monitors (from a > > 1920x1080 Dell to a 2560x1440 Dell) and installed vlc (with a number of > > dependencies) and now X won't start up for my ID any longer (still works for > > root). In case it may help, below is my latest Xorg.0.log file. For some > > reason the intel driver isn't working. Note the line: > > > > (WW) Falling back to old probe method for fbdev > > > > And then it trys fbdev, which also fails due to a problem with fbdevhw. Anyone > > have any idea what may be wrong? > > > > > interesting - are you specifically calling fbdev in your xorg.conf? > this is an unaccelerated driver i think, which leads me to believe that > the xf86-intel driver is not working for some reason. No, I don't believe I have an xorg.conf file anywhere on the system. I have searched for one to check this, but the closest thing I can find is and empty /usr/local/etc/X11/xorg.conf.d directory. > > > what is the version of your xf86-intel driver? this is the version i am > using with my skylake system: > > $ pkg info -f xf86-video-intel-2.99.917.20160614 > xf86-video-intel-2.99.917.20160614 > Name : xf86-video-intel > Version : 2.99.917.20160614 > Installed on : Thu Jul 28 18:45:42 2016 PDT > Origin : x11-drivers/xf86-video-intel > Architecture : freebsd:12:x86:64 > <snip> Mine looks to be the same as yours: bob@padme:0 /var/log> pkg info -f xf86-video-intel xf86-video-intel-2.99.917.20160614 Name : xf86-video-intel Version : 2.99.917.20160614 Installed on : Thu Sep 22 09:43:13 2016 CDT Origin : x11-drivers/xf86-video-intel Architecture : freebsd:12:x86:64 > > > also this is the relevant section of my xorg for reference: > > Section "Device" > Identifier "Card0" > Driver "intel" > Option "TearFree" "true" > BusID "PCI:0:2:0" > EndSection Since I didn't have an xorg.conf file, I created one (via 'Xorg -configure') which got me past the problem with the intel driver. However I still couldn't get X to start. So I then started scrutinizing my .xinitrc file and I discovered two things that appear to have been causing problems. First was that I was setting 'DISPLAY=$HOSTNM:0.0' where $HOSTNM was the first element of the system's host name and the second was that my old .xinitrc file didn't have this line at the end: exec xterm -geometry 80x66+0+0 -name login as the xinitrc file in /usr/local/etc/X11/xinit does. I have no problem removing the DISPLAY variable setting (I have no memory of why I had it there...that was YEARS ago that I did it), but the exec'ing of the xterm bothers me. I don't understand why it's now required, and I can't say that I like it (if I exit the xterm X terminates, most annoying). Any ideas why this is now needed and if there is a way to get rid of it? Thanks, Bob -- Bob Willcox | In real love you want the other person's good. In bob@immure.com | romantic love you want the other person. Austin, TX | -- Margaret Anderson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160929131751.GW845>