intel graphics factsheet

[musca]

Hello dear intel users,

let me give a general overview first:

• The last stable release 2.21 of the intel driver is 3 years old and debian jessie is the only distro still shipping it.
• The unreleased beta driver 2.99 is 1 ½ years old and git doesn't show much progress either.
• The current driver defaults to SNA, users of older chipsets may want to try UXA.

As a result Debian and Ubuntu in xserver-xorg-core 2:1.18.3-2 have changed the autodetection to prefer the integrated modesetting driver over the intel driver, possibly causing performance degration.
[update:] Fedora 26/rawhide has integrated this patch from debian.

Now let me list some most recent issues with the intel beta driver:

• intel developers forgot to add pciids for latest intel GPUs. (fixed in libdrm 2.4.68)
• intel has tagged the beta driver as 2.99.918 in git but later withrawn the tag to 917. (Fix see below)
• linux kernel 4.6 enabled Frame-Buffer Compression (FBC) by default on Haswell and Broadwell GPUs.

A nice thread which mangles all of theese details is Firefox slow after DU.

If you want to try the intel driver, please make sure you really have installed the latest.
If  'apt policy xserver-xorg-video-intel' seems suspicious (the .918 installed), you can do:
apt update ; apt purge xserver-xorg-video-intel ; apt install xserver-xorg-video-intel

greetings
musca

[samoht]

Thank you so much for your support regarding the intel driver affairs  .
Greetings
Tom

[horo]

Hi,

Just checked my version:

Code: [Select]

$ apt policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installiert:           2:2.99.918+git20160426-1
  Installationskandidat: 2:2.99.918+git20160426-1
  Versionstabelle:
 *** 2:2.99.918+git20160426-1 500
        500 http://ftp.spline.de/pub/siduction/fixes unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     2:2.99.917+git20160706-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
Executing

Code: [Select]

apt update ; apt purge xserver-xorg-video-intel ; apt install xserver-xorg-video-intel
changes the version to:

Code: [Select]

$ apt policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installiert:           2:2.99.917+git20160706-1
  Installationskandidat: 2:2.99.917+git20160706-1
  Versionstabelle:
 *** 2:2.99.917+git20160706-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

I didn't run into problems in the past as I installed a /etc/X11/xorg.conf.d/20-intel.conf some time ago to enable the UXA mode:
http://forum.siduction.org/index.php?topic=6102.0

Ciao, Martin

[musca]

Hello horo,
thanks for showing this example. It is exactly what I was talking about.

greetz musca

[vilde]

This saved my siduction installation on an old x60. After d-u I was dropped in a blinking shell. Unable to write anything I couldn't log in to root. I manage to start in init 3 by edit in grub during boot, logged in to root and did : apt update ; apt purge xserver-xorg-video-intel ; apt install xserver-xorg-video-intel and now the old laptop is running again. Thanks

[mld]

Maybe a good place to add another hint concerning intel graphics. Since Kernel 4.8 booting up on certain core2duo/Dualcore setups with intel GM965/GL960 Integrated Graphics Controller can get a bit quirky (like on my Inspiron 1525). The combination of KMS and SVIDEO resulted in slow booting up, instabilities and/or freezes.

Luckily on the arch wiki a kind of workaround can be found.

E.g. adding a  video=SVIDEO-1:d to my grub.cfg fixed it

[DeepDayze]

Maybe a good place to add another hint concerning intel graphics. Since Kernel 4.8 booting up on certain core2duo/Dualcore setups with intel GM965/GL960 Integrated Graphics Controller can get a bit quirky (like on my Inspiron 1525). The combination of KMS and SVIDEO resulted in slow booting up, instabilities and/or freezes.

Luckily on the arch wiki a kind of workaround can be found.

E.g. adding a  video=SVIDEO-1:d to my grub.cfg fixed it

This workaround worked for me in the case where I have my HP 8460p laptop in a dock and using an external 22" monitor for the display. As KMS did not use the full resolution of the monitor but of the internal LVDS panel, only part of the monitor was used for display when in text mode (init 3).

Turning off the internal LVDS using the video= boot option enabled the external monitor to use its full resolution. X still used the external display's natural resolution however.

[tomsiduction]

Hello
Maybe an not so young post but still i would like to ask:

Please can you tell which file did you edit with " video=SVIDEO-1:d"

Regards

[jure]

as he wrote

E.g. adding a  video=SVIDEO-1:d to my grub.cfg fixed it

[tomsiduction]

Hello and thank you

the only grub.cfg I can find is located at

/boot/grub

the file starts with:

Code: [Select]


### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
    set gfxpayload="${1}"
}
set linux_gfx_mode=1280x1024
export linux_gfx_mode
menuentry 'siduction 2018.3.0 Patience (KDE) GNU/Linux' --class siduction --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-072ccc73-a2ae-467c-8e25-bd380e4c2e5b' {
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  822fc2c6-1ff6-4681-9dcb-9a9c4b4fb63d
    else
      search --no-floppy --fs-uuid --set=root 822fc2c6-1ff6-4681-9dcb-9a9c4b4fb63d
    fi
    echo    'Linux 5.0.7-towo.4-siduction-amd64 wird geladen …'
    linux    /vmlinuz-5.0.7-towo.4-siduction-amd64 root=/dev/mapper/VGsys-LVroot ro cryptopts=source=UUID=ade37c6d-c298-47bd-b2ce-fa9fdc2078ca,target=cryptsda2,lvm=VGsys-LVroot quiet systemd.show_status=1 splash resume=/dev/sda3
    echo    'Initiale Ramdisk wird geladen …'
    initrd    /initrd.img-5.0.7-towo.4-siduction-amd64
}


Where please do I have to edit it?

Regards

[towo]

Do not edit grub.cfg!
Edit /etc/default/grub instead and after editing do update-grub!

[tomsiduction]

Thank you very much

I looked at
info -f grub -n 'Simple configuration'

to find out how to edit the file.
But I am not sure what to change:

Makes it sense to add a line:

GRUB_VIDEO_BACKEND=video=SVIDEO-1:d

to the file in /etc/default/grub



or do I only have to add:

video=SVIDEO-1:d

Thank you very much


Regards

[axt]

tomsiduction, das Editieren von Bootoptionen (uude-Wiki-Link, ist jedoch nutzbar) ist jetzt aber wirklich nichts neues.

Mit root-Rechten:

• Mit Editor Deiner Wahl öffnen: "leafpad /etc/default/grub"
• Die Zeile "GRUB_CMDLINE_LINUX_DEFAULT=" um die gewünschte Bootoption ergänzen.
• Speichern, Editor beenden.
• grub aktualisieren: "update-grub"
• Reboot.

[samoht]

@axt, dein Wissen kommt besser an, wenn du deinen Oberlehrer-Modus künftig vermeiden kannst 
Kannst Du nicht auf Englisch antworten, wenn die Frage so gestellt war?

@axt, your knowledge will go down better if you can avoid your senior teacher mode in the future
Can't you answer in English if the question was like this?

Greetings,
Tom

[axt]

samoth, ich habe auf eine Frage eines Deutschen (ich sehe vorher nach, sollte ich den User nicht kennen) in Deutsch sowie mit einem Link in ein deutschsprachiges Wiki geantwiortet.

Damit keine Mißverständnisse aufkommen, ich mag en-us. Ich habe zudem in einer texanischen IT-Firma im ProSupport gearbeitet - interne Kommunikation ist Englisch, obwohl bis auf den kleinen Bereich mit Polen und Tschechen, mit denen wir nichts zu tun gehabt haben, nur Deutsche dort gearbeitet haben. Das ist dann verdammt schräg. Nebenbei habe ich mich bspw. mit einem indischen Kd., der sich in den DACH-Support verirrt hat, in Englisch besser verstanden, als mit den zahlreichen Schweizern, die wie selbstverständlich mit diesem unverständlichen Bergdialekt kommen.

Im übrigen: Da es nicht Deine Frage gewesen ist, brauchst Du Dich auch nicht angesprochen fühlen.

Wenn Du Dich zum Kritisieren bemüßigt fühlst, hättest Du mit Necrobumping eher einen Grund gehabt (nur dann eben nicht gegen mich, tja).