Date: Sun, 23 Feb 2020 03:28:32 +0100 From: Kit Smith <kit@hypostasis.com> To: Michael Gmelin <freebsd@grem.de> Cc: ajtiM <starikarp@dismail.de>, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Script to help find xorg configuration issues Message-ID: <A505E754-705E-46DE-B77C-D49B15CED66C@hypostasis.com> In-Reply-To: <20200222231332.655c663e@bsd64.grem.de> References: <20200222231332.655c663e@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--kit > On 22 Feb 2020, at 23:14, Michael Gmelin <freebsd@grem.de> wrote: >=20 > =EF=BB=BF >=20 >> On Sat, 22 Feb 2020 13:01:15 -0500 >> ajtiM <starikarp@dismail.de> wrote: >>=20 >> On Sat, 22 Feb 2020 15:36:19 +0100 >> Michael Gmelin <freebsd@grem.de> wrote: >>=20 >>> Hi, >>>=20 >>> I've been helping others configuring X11 with UDEV/evdev for quite >>> some time now. Since UDEV recently became the default option on >>> 12.1[0], I thought that having something automated (yet >>> non-intrusive) to help users fix their setup might be useful. >>>=20 >>> To achieve this, I created a small/hacky script today that checks >>> all the usual problems I found while helping people figuring out >>> what's wrong with their setup. >>>=20 >>> You can find it on github: >>> https://github.com/grembo/xorg-udev-setup-check >>>=20 >>> Direct download link: >>> https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xo= rg-udev-setup-check.sh >>>=20 >>> Usage: ./xorg-udev-setup-check.sh [-hdpi] >>> -h print this help >>> -d skip drm checks >>> -p skip package version checks >>> -i only show errors (suppress info) >>>=20 >>> You should be able to run it as an unprivileged user - fixing things >>> will require root privileges though. >>>=20 >>> I didn't test it thoroughly, so feel free to open pull requests >>> on github - functional improvements only please, don't try to >>> improve the code quality. >>>=20 >>> Cheers, >>> Michael >>>=20 >>> [0]https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196678 >>>=20 >>=20 >> Thank you for the script but I did downgrade 11th times because new >> xserve doesn't work on my system. >> The script found just that I need to put radeon or intel in rc.conf. >> For my Radeon drm.kmod doesn't work - black screen and I am using scfb >> driver which doesn't work on new xserver or I do nnot know how to do. >> As I wrote before I have >> in /usr/local/etc/xorg.conf.d/driver_scfb.conf where I have=20 >> Section "Device" >> Identifier "Card0" >> Driver "scfb" >> EndSection =20 >>=20 >> and work for me on old xserver. >>=20 >> Thank you. No more update and downgrade. I need to work too. >>=20 >=20 > So does everyone else who's trying to help you :) >=20 > I seem to remember having issues with scfb a while ago. To make it work > I had to make sure that scfb is the only driver available. An easy way > to test this without dealing with pkg problems is to move everything > except "scfb_drv.so" out of /usr/local/lib/xorg/modules/drivers > manually (especially vesa_drv.so) >=20 > With all alternative drivers removed, driver_scfb.conf shouldn't be > necessary anymore, as scfb is the only option left. So it should be > removed - which should make auto-detection of the server layout work, > which should make input devices work - if my memory doesn't fool me. It > might be worth a shot. >=20 > That was over two years ago though, so I can't guarantee this will > actually fix it for you. If you feel like testing is an undue burden, > don't try it > Cheers, > Michael >=20 > --=20 >=20 i=E2=80=99ve been playing on current cos shiny (I know bad human) to see if i= t will run on my laptop. I=E2=80=99m not there yet, but I did have to drop V= esa from X to get it to detect the scfb properly=20 There were many other errors so that may be a false reference point.=20 =E2=80=94kit=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A505E754-705E-46DE-B77C-D49B15CED66C>