I915 linux driver fedora

i915 вместо i965

У меня встроенная видяха, и как написано в вики генты, на неё должен ставиться модуль i965. Но в выводе lspci -v указан i915. Пробовал modprobe i965, он говорит что такого модуля просто нет, хотя я ставил mesa с которым он должен идти. В VIDEO_CARDS i965 прописан. ЧЯДНТ?

Это не ядерный модуль, его модпробом не уговоришь
Что скажут
locate i965 | grep usr/lib
grep i965 /var/log/Xorg.0.log

Это разные вещи.

i915 — модуль ядра для всех GPU от Intel.

i965 — юзерспейсный драйвер в составе Mesa для всех GPU от Intel.

xf86-video-intel — иксовый драйвер (DDX) для всех GPU от Intel.

Для аппаратного ускорения графики в иксах они все нужны одновременно. Примечание на полях: с недавних пор последний можно без проблем заменить универсальным xf86-video-modesetting, у некоторых он работает гораздо стабильнее.

xf86-video-modesetting, у некоторых он работает гораздо стабильнее

Недавно ставил поциенту бубунту, там искаропки этот xf86-video-modesetting. Через минуту-две иксы блюют артефактами и превращаются в тыкву. Но, да, ты прав, он гораздо стабильнее не работает.

Тебе пофлеймить захотелось? Для особо непонятливых: у некоторых.

Алсо, «бубунту не линукс»™. Никто не знает, чего они там наворотили с дистроспецифичными патчами.

Акцентирую внимание на проблеме.

Тебе пофлеймить захотелось? ^_

> Примечание на полях: с недавних пор последний можно без проблем заменить универсальным xf86-video-modesetting, у некоторых он работает гораздо стабильнее.

А работает ли VA-API? Или только OpenGL?

И OpenGL не работает. Этот драйвер не занимается ни тем, ни другим.

i965 — юзерспейсный драйвер в составе Mesa для всех GPU от Intel

Всё уже изменилось. Драйвер modesetting умеет использовать DRI-драйверы

Ну да, умеет. А изменилось-то чего? Он как не предоставлял OpenGL и VAAPI, так и не предоставляет. И никогда не будет, этим занимаются другие драйвера.

Через меня проходит очень много железа, плюс куча моего железа, у меня уже давно каша в голове. Я не помню, даже не уверен, был ли это ноутбук.

Просто стоит учитывать, что modesetting знать ничего не знает про интел. 2D ускорением в нём занимается GLAMOR, которые делает это через стандартное OpenGL. Для старых карт, которые не очень умеют более-менее свежий OpenGL (а для гламура нужен стильный модный молодёжный опенгл), и для новых, где 3D драйвер ещё сыроват, могут быть проблемы с 2D, виновато в чём 3D.

Оно немного какаха.

12 из 10 по моему аргументометру. Хотя на гламур лично мне пофигу, просто непонятна претензия к modesetting’у — это универсальный драйвер, он может только в универсальный NoAccel или универсальный GLAMOR, других вариантов у него чисто технически нет.

А оно и не нужно. Швабодный radeon тоже работает либо через Glamor, либо как говно, потому между совсем говном и Glamor я выбрал второе.

А вообще, мы тут не мои какие-то фантомные проблемы решаем, так что забей.

> Ну да, умеет. А изменилось-то чего? Он как не предоставлял OpenGL

Раньше при работе modesetting нельзя было получить аппаратно ускоренное 3D вообще. Это как драйвер vesa, только vesa это UMS-драйвер. Теперь драйвер modesetting умеет аппаратный OpenGL, используя файлы DRI из директории /usr/lib/dri/. В Fedora встал вопрос о том, чтобы вообще отказаться от драйверов i965 и radeon в пользу modesetting.

Вот мне и интересно, ну работает теперь 3D, а что насчёт VAAPI и тиринга?

Читайте также:  Команда test параметры linux

xf86-video-modesetting, у некоторых он работает гораздо стабильнее

А вот игры на bumblebee показывали слайдшоу, в отличие от xf86-video-intel.

А почему с двойной графикой, когда тяжёлую графику вроде-бы рендерит nvidia, на modesetting всё равно всё плохо? А вот на родном интеле нормально.

Источник

intel-gpu/intel-gpu-i915-backports

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Intel® Graphics Driver Backports for Linux® OS (intel-gpu-i915-backports)

Contains the backported i915 Source Code of intel GPUs on various OSV Kernels. You can create Dynamic Kernel Module Support(DKMS) based packages, which can be installed on supported OS distributions.

These out of tree i915 kernel module source codes are generated by the backpoprt project. «https://backports.wiki.kernel.org/index.php/Main_Page»

This repo is a code snapshot of particular version of backports and does not contain individual git change history

This driver is part of a collection of kernel-mode drivers that enable support for Intel graphics. The backports collection within https://github.com/intel-gpu includes:

  • Intel® Graphics Driver Backports for Linux — The main graphics driver (includes a compatible DRM subsystem and dmabuf if necessary)
  • Intel® Converged Security Engine Backports — Converged Security Engine
  • Intel® Platform Monitoring Technology Backports — Intel Platform Telemetry
  • Intel® GPU firmware — Firmware required by intel GPUs.

Each project is tagged consistently, so when pulling these repos, pull the same tag.

Источник

I915 linux driver fedora

Recently Intel started including their graphics drivers into the mainline Linux kernel. This is great except when it stops working. Having suffered intermittent, sporadic GPU freezes on my Lenovo x270 (Kabylake) work laptop since Kernel 4.12+ I came across a bug report that seemed related. Here’s my temporary fix on Fedora 28 for getting things stable again until it’s fixed for good upstream.

The Intel Integrated Graphics Crash
I started having complete system freezes intermittently where my laptop display would shudder / jitter and then hard lock. There was no real pattern to this happening nor was I able to get any log file information or journal information about the issue as it completely froze. No network, no ping, nothing.

I’ve had this issue on both Skylake and Kabylake Intel-based laptop systems with integrated HD graphics (i915 driver) across Kernels 4.12+ through the 4.16.8 Fedora 28 Kernel. I recall this also happened on my previous Lenovo x240 though less frequently.

I am sure at some point this will be permanently fixed and disseminate down to all the major Linux distributions. I was impatient and frustrated and wanted something to work right away, here’s how I got there.

Unrelated – Micro Freezes on Linux 5.x Kernels and i915

Update 2019-09-09: The original issue I will walk through in this blog post is not related to recent micro-freezes on Linux 5.x kernels and i915 integrated GPU’s. There is a proposed patch pending for this here and I’ve been testing out the following kernel option to work around this right now

Читайте также:  Hp 1200 как вытащить картридж

Panel Self Refresh (PSR), a power saving feature used by Intel iGPUs is known to cause flickering in some instances FS#49628 FS#49371 FS#50605. A temporary solution is to disable this feature using the kernel parameter i915.enable_psr=0.

Update: 2018-05-28: It seems that as of Skylake Fedora no longer uses the intel/i915 driver by default if you’re using Xorg. It instead uses the xorg-x11-drv-intel driver which means the testing below is not relevant currently (thanks to Venemo in the comments).

I doing more testing now against the stock 4.16.10 kernel using the Intel driver in lieu of the xorg-x11-drv-intel driver.

To switch to the intel driver make yourself an xorg shim config and then restart Xorg or reboot.

If you were running the xorg Intel drivers you’d have seen something like this in /var/log/Xorg.0.log:

If you are now running the Intel i915 driver you’d see this instead:

Update: 2018-05-29: I’m still getting GPU freezes with the 4.16.11 Fedora 28 kernel and the Intel i915 driver.

I have also tried the following kernel parameter which doesn’t help:

I am now testing the latest drm-tip against the Fedora Rawhide 4.17.0-rc kernels as I have time to hopefully see if/when a fix appears.

Update: 2018-06-04: So far things have been stable for 4 days on 4.17.0-rc7 and latest Intel drm-tip kernel tree modules copied in, I will keep this updated if I have another freeze.

Commenter Venemo has stated he’s still getting this freeze on 4.17.0-rc7 however on another system.

Update: 2018-06-05: I experienced another GPU freeze but it took about

5 days of normal usage and dozens of suspend/resumes. For giggles I tested trying to trigger this in the BIOS and was able to get screen artifacts by jerking the laptop around and also by squeezing (a normal amount) the palm rest area of the laptop.

I also tried a Windows 10 USB stateless image and indeed I get the same GPU freezes there too. This makes be believe it’s a hardware defect. I’ve filed a ticket with Lenovo and I’ll be mailing my laptop in for repair/replacement – I’ll let ya know how it goes.

Update: 2018-07-17: I received my laptop back from repair and the motherboard and SATA cables were replaced. I’ve had zero issues for almost a month now on 4.17.7+ kernel on Fedora28. Here’s the work receipt from Lenovo (replaced assemblies PCB, motherboard, cables, wire):

I am leaving the rest of this blog post / guide up in case it might be useful for someone tracing down Intel GPU issues on Linux or filing bugs against upstream.

Testing Intel Upstream Linux Kernel Drivers

Below is how I previously tested the latest 4.17.0-rc kernel and Intel drm-tip kernel modules which may still be useful to others so I’m leaving it here.

Temporary Fix for the Intel Graphics Crash
The fix I found was to use the absolute latest Intel drm-tip git kernel code combined with a 4.17.0-rc5 Kernel build. I then installed a Fedora development (rawhide kernel) and later copied in the compiled Intel kernel modules in afterwards, Yolo.

The full docs for setting up the latest Intel stack is here but I’m going to explain just the basics in case you are hitting this as well and want to get up and running quickly.

Читайте также:  Kernel build options linux

Build Kernel (Modules) Against drm-tip
This is going to clone a rather large git repository of all the upstream intel drm bits and build the latest kernel and modules. Note that we’re ommitting the actual make install of the kernel, we only care about the modules. You’re going to need this later.

First you’ll need some build and compiler tools, this is what I needed to install prior:

Next build the thing against the latest upstream Intel drm-tip repository. This may take quite some time. Ironically the GPU froze on me a few times trying to build the latest drivers that should supposedly contain the crash fix! Maybe it could sense it.

The last line will copy the kernel modules you create into /lib/modules/KERNEL_VERSION/kernel/drivers/gpu/drm along with a bunch of other kernel drivers we’re not going to need.

If you get a compilation issue about asm-goto support you’ll need to comment that out of arch/x86/Makefile and try again:

Install Rawhide Development Kernel
While you could just run the drm-tip Kernel chances are you’d need a whole lot more modules configured/enabled for your hardware. I find it is much easier to just use your distributions latest kernel (if it matches latest upstream) as those are generally better configured for most hardware use cases and you’ll have everything reasonable provided as a loadable module.

You might substitute Rawhide here for your distributions development / bleeding edge Kernel like Tumbleweed for SuSE. For Fedora users I am providing the direct paths here, which may change so double check the parent location.

Install the Development 4.17+ Kernel
Now install the Rawhide development kernel and associated packages.

Copy the drm-tip Kernel GPU Modules Over
The current Rawhide kernel does not have the latest version of the Intel drivers that we’ll need that contain the actual fix so we’re going to copy them in manually. This is fairly bad practice but in general but we don’t really care – we’d prefer something working to good etiquette that doesn’t.

Your paths and names may vary, but I copied over the entirety of the /lib/modules/KERNEL_MODULES_YOU_BUILT/kernel/drivers/gpu/drm/* into the modules location of the Rawhide kernel that I just installed.

Again, not the most elegant fix but gets the job done. At this point just reboot into the new kernel and if you had crashes before due to the bug I was hitting hopefully they have gone away.

Usage and Testing
After

20 hours of GPU torture tests (hundreds of glxgears spinning, open/close images in a shell loop, suspend and resume constantly over and over, old games raging in wine) things seem pretty stable. Before I’d get hard GPU lockups anywhere from 6 minutes to 6 hours into normal desktop usage.

I realize this is a rather temporary blog post and I’m positive that all this will get fixed in upstream kernels. For now it was important (and frustrating enough) to find a fix as soon as possible and then write about it. I hope this helps someone else.

How to Debug an Intel GPU Crash
If you’re lucky enough to get logs or data written in case of a GPU crash there’s an easy way to gather debug information to file an Intel graphics driver bug.

Источник

Поделиться с друзьями
КомпСовет
Adblock
detector