Date: Fri, 12 Aug 2016 18:44:21 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-x11@freebsd.org Subject: Re: testing drm-next 4.6 on i915 broadwell Message-ID: <b949b477-5dd8-c1eb-0a73-ca61b7c139bd@nomadlogic.org> In-Reply-To: <CAKJji3oTPVGk2VAkp3R2yq3a9ryPh%2B1dX92oZ9WKN-hy%2BAh%2BXg@mail.gmail.com> References: <CAKJji3oTPVGk2VAkp3R2yq3a9ryPh%2B1dX92oZ9WKN-hy%2BAh%2BXg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/12/16 11:56, inti.glez.herrera wrote:
> Hello,
>
> My current laptop features the i915 Broadwell microarchitecture. I was
> trying to use FreeBSD when I realized that the graphic support is
> limited. I am interested on actively contributing to the development
> (although unfortunately, so far my knowledge is limited). After
> cloning freebsd-base-graphcis (branch drm-next-4.6), I can finally
> load the device driver and run Xorg. However, there are some problems:
>
> - The response time becomes really slow.
> - Typing a simple command in the console can take 20 seconds.
> - The mouse is also moving slow
> - Executing a simple startx implies a reset because it slowdown the system
> - Even a simple xclock is a problem
>
> I was trying to identify where is the issue and my plan was using
> dtrace. Right now I can use it to collect kernel stack traces, but
> instead of the name of function, the output is only showing the
> addresses.
>
> My question is: do I need to compile the kernel with some special
> flags to support symbols in dtrace ?
>
> A secondary question : do you recommend another profiler (or tool) to
> debug this kind of problem ?
>
> Some basic information: I am using the generic configuration and I
> updated a bunch of ports using freebsd-ports-graphics.
The first thing I would look at is your /var/log/Xorg.0.log. From the
sound of it you may be using a VESA graphics driver in Xorg. If you
*are* running the VESA driver you can update the devices section of
xorg.conf to contain the following:
Driver "intel"
This assumes you have installed the xf86-video-intel-2.99 driver pkg.
here is an example of Xorg successfully loading the intel driver on my
SkyLake system (taken from Xorg.0.log):
[ 8508.514] (II) LoadModule: "intel"
[ 8508.514] (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so
[ 8508.515] (II) Module intel: vendor="X.Org Foundation"
[ 8508.515] compiled for 1.18.3, module version = 2.99.917
[ 8508.515] Module class: X.Org Video Driver
[ 8508.515] ABI class: X.Org Video Driver, version 20.0
[ 8508.515] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33,
Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 8508.516] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 8508.516] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 8508.516] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics:
5200, 6200, P6300
[ 8508.516] (--) Using syscons driver with X support (version 2.0)
[ 8508.516] (--) using VT number 9
[ 8508.516] (II) intel(0): Using Kernel Mode Setting driver: i915,
version 1.6.0 20160229
hope this helps!
-pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b949b477-5dd8-c1eb-0a73-ca61b7c139bd>