Date: Fri, 17 May 2019 11:59:16 +0200 From: Milan Obuch <freebsd-x11@dino.sk> To: Niclas Zeising <zeising+freebsd@daemonic.se> Cc: x11@freebsd.org Subject: Re: Nothing newer as https://wiki.freebsd.org/Graphics/Intel-GPU-Matrix? Message-ID: <20190517115916.0b8dbd58@zeta.dino.sk> In-Reply-To: <f3d2c81d-56e7-018d-4809-c8903ac1182a@daemonic.se> References: <20190516110515.11afc7ad@zeta.dino.sk> <8df3c740-5a84-bd0c-7b9a-8d8d24e041c0@daemonic.se> <940088bd-a545-8b02-06c2-a6388ea6e69c@daemonic.se> <20190517113621.2762239e@zeta.dino.sk> <f3d2c81d-56e7-018d-4809-c8903ac1182a@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 May 2019 11:49:36 +0200 Niclas Zeising <zeising+freebsd@daemonic.se> wrote: > On 2019-05-17 11:36, Milan Obuch wrote: > > On Thu, 16 May 2019 11:35:13 +0200 > > Niclas Zeising <zeising+freebsd@daemonic.se> wrote: > > =20 > >> On 2019-05-16 11:12, Niclas Zeising wrote: =20 > >>> On 2019-05-16 11:05, Milan Obuch wrote: =20 > >>>> Hi, > >>>> > >>>> this page is last edited end of year 2018. Is there anything > >>>> newer? Of particular interest for me are Bay Trail CPUs I am > >>>> trying to run X on, but no success yet. Well, vesa video works, > >>>> kind of, but I need Full HD resolution which seems not possible > >>>> with vesa. > >>>> > >>>> If anybody has something to share, maybe some work-in-progress > >>>> for test, it would bee great... > >>>> =20 > >>> > >>> Hi! > >>> Graphics driver versions hans't been updated since the end of > >>> 2018, so that is the newest version.=C2=A0 There is ongoing work to > >>> update the driver to current, but that is not in base yet. > >>> Regards =20 > >> > >> Hi! > >> The bay trail SoCs could be supported from a graphics perspective > >> even if they aren't listed. I suggest you install drm-kmod and > >> try. You'll see if it attaches to the hardware. > >> =20 > >=20 > > Hi, > >=20 > > so I did full reinstall with 12.0-STABLE snapshot, used port > > drm-fbsd12.0-kmod-4.16.g20190430, kldload /boot/modules/i915kms.ko > > and it works - kind of. Just one trouble, I can't see anything on > > screen connected to VGA output, just mouse X cursor, because other > > output is active before VGA and all three xterms are there, left of > > my visible screen (I can move mouse cursor to the left, off the > > screen). > >=20 > > grep EDID Xorg.0.log > >=20 > > [ 715.398] (II) intel(0): EDID for output eDP1 > > [ 715.398] (II) intel(0): EDID Version: 1.4 > > [ 715.399] (II) intel(0): EDID (in hex): > > [ 715.427] (II) intel(0): EDID for output VGA1 > > [ 715.428] (II) intel(0): EDID Version: 1.3 > > [ 715.429] (II) intel(0): EDID (in hex): > > [ 715.429] (II) intel(0): EDID for output DP1 > > [ 715.430] (II) intel(0): EDID for output HDMI1 > >=20 > > So I think I need somehow disable eDP1 output and it should be OK, > > but how? When i915kms module is kldloaded, there are some tunables > > mentioned, like kern.vt.fb.modes.VGA-1 - could it be used for it? =20 >=20 > Hi! > If you have started X (which I assume you have from your > description), try fiddling with xrandr. Just running xrandr without > any arguments should show all screens connected to your computer. > You can then disable certain screens with > xrandr --output [name-of-output] --off > The name of the output is listed in the xrandr output from the first > run. Is this a dual or multi screen set up? >=20 I did, and yes, I tried already xrandr. It gives me just what I need. My question was if it is possible to do it before starting X, but calling xrandr from xinitrc is not a big deal for me. I just checked, works satisfactorily. There is one strange thing, though not X related - when i915kms module is kldloaded, screen switched to higher resolution, but strangely, not full screen could be used, it looks like it scrolls up in the middle of physical screen. Any idea on this? Regards, Milan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190517115916.0b8dbd58>