Date: Tue, 29 Mar 2016 20:53:39 +0000 (UTC) From: Will Parsons <varro@nodomain.invalid> To: freebsd-questions@freebsd.org Subject: Re: how to downgrade X server Message-ID: <slrnnflqqj.1j0.varro@anukis.local> References: <slrnnfaung.1ae.varro@anukis.local> <56F60B8D.8080900@ShaneWare.Biz> <slrnnfdcvt.1m3.varro@anukis.local> <56F77C30.5090808@ShaneWare.Biz> <slrnnfj6ol.1oh.varro@anukis.local> <alpine.BSF.2.20.1603281740340.96792@wonkity.com> <slrnnflegq.1jl.varro@anukis.local> <alpine.BSF.2.20.1603291301470.35810@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warren Block wrote: > On Tue, 29 Mar 2016, Will Parsons wrote: > >> Warren Block wrote: >>> On Mon, 28 Mar 2016, Will Parsons wrote: >>> >>>> I haven't been using one. The Xorg log shows: >>>> ... >>> >>> The fbdev errors are ignorable. Is that the entire log? The Intel >>> HD3000 should work fine. >> >> No - I just started with the first errror messages. I've included the >> entire log below. >> >>> As a start, please describe your hardware. Some notebooks have hybrid >>> graphics like Optimus which are a problem. If that is not present, >>> defining just the device in xorg.conf.d might be all that is needed. >> >> It's a Lenovo Edge E520 laptop - see below for info from dmesg. >> Any help is much appreciated. > > Specs from the web don't indicate any hybrid graphics, which is good > news. The log file does not have any obvious problems. > > Please make sure there are no old xorg.conf files in /etc/X11/ or > /usr/local/etc/X11/. Nothing more should be required, but it would do > no harm to manually set a Device as shown here: > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html#x-config-video-cards-file-intel I double-checked, but there wasn't. I created the file /usr/local/etc/X11/xorg.conf.d/driver-intel.conf as per the handbook, but without success. One other thing I tried (I don't know why this didn't occur to me before) was to disconnect the external monitor I usually use. But again, I just got a black screen, this time on the built-in display. > Probably also a good idea to use vt(4) in case the black screen is due > to X exiting. In /boot/loader.conf, add > kern.vty=vt I had already added that, but is there any way of verifying it has taken effect? The line "Using syscons driver with X support (version 2.0)" looks suspicious to me. > That only takes effect after a reboot. > > Finally, check the contents of .xinitrc and .xsession for unexpected > things. Neither is required. There is no .xsession and the .xinitrc I've been using is pretty straight-forward: ================================= if [ -f $HOME/.Xmodmap ] then xmodmap $HOME/.Xmodmap fi if [ -f $HOME/.Xresources ] then xrdb -merge $HOME/.Xresources fi if [ -f $HOME/.xbindkeysrc ] then xbindkeys fi exec wmaker ================================= I tried temporarily renaming it, but no change to symptoms. > Test X with just startx. Don't try to use display managers like xdm or > gdm yet. I do that anyway. -- Will
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrnnflqqj.1j0.varro>