[SOLVED] Use the xf86-intel-driver

laerne · 2011-12-19 21:05:28

Hello, i would like to use the intel driver on my hp mini laptop (64bits os).

I've been using a fresh installation of archlinux for a year, but I'm getting tired of not being able to use xrandr.

for example, `xrandr -o left` complains with :

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  2 (RRSetScreenConfig)
  Serial number of failed request:  14
  Current serial number in output stream:  14

I uninstall the vesa driver, but starting xorg then fails :

X.Org X Server 1.11.3
Release Date: 2011-12-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.1.5-1-ARCH x86_64 

(...)

(==) Log file: "/var/log/Xorg.2.log", Time: Mon Dec 19 21:15:47 2011
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) open /dev/fb0: No such file or directory
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

I have no xorg.conf to force use of vesa. Only some unrelated files in /etc/X11/xorg.conf.d

% ls /etc/X11/xorg.conf.d 
10-evdev.conf  10-quirks.conf  10-synaptics.conf  50-joystick.conf  50-vmmouse.conf  50-wacom.conf

It seems anyway to force me to use vesa. But lspci tells me I should use i915 !

% lspci -ks 0:02 
00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller
        Subsystem: Hewlett-Packard Company Device 3660
        Kernel modules: i915
00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller
        Subsystem: Hewlett-Packard Company Device 3660

And that's not the worst of it. I've uninstalled xf86-video-intel, rebooted, but lsmod tells the module i915 is loaded !

i915                  725922  0 
drm_kms_helper         25721  1 i915
drm                   185768  2 i915,drm_kms_helper
intel_agp              10904  1 i915
i2c_algo_bit            5199  1 i915
button                  4470  1 i915
intel_gtt              14455  3 i915,intel_agp
i2c_core               20460  6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video                  11164  1 i915

I really do not understand anything anymore...

Can someone help ?

Thanks !

Last edited by laerne (2011-12-24 09:38:27)

karol · 2011-12-20 09:43:17

What's the output of

grep i915 /etc/mkinitcpio.conf

You need to remove the mention of 'i915' from the places you've put it in when you did set it up.

RichAustin · 2011-12-20 09:55:11

This sounds sort of like an issue I had on ArchBang where the system tries to default to vesa. I fixed it by editing the following file:

sudo nano /etc/X11/xorg.conf.d/20-gpudriver.conf

Then replacing "vesa" with "intel" so the file reads like this:

Section "Device"
Identifier "Card0"
Driver     "intel"
EndSection

You can also check what drivers are installed using the following:

pacman -Qqs ^xf86-video

In my case a huge list was returned and I deleted all of them, with "sudo pacman -R name-of-driver-here", except the intel one, rebooted and the video worked fine. Your error is different to mine but the fact that it is complaining about vesa when it should be intel I figure is enough of a reason to at least check the file I mentioned - took me ages to find the darn error so I hope it works for you!

Rich

samuvuo · 2011-12-20 10:11:35

Don't give up on i915 yet.

Make sure these packages are installed:
xf86-video-fbdev
xf86-video-intel
xf86-video-vesa

In /etc/modprobe.d/modprobe.conf:

options i915 modeset=1

In /etc/mkinitcpio.conf:

MODULES="intel_agp i915"

and uncomment:

FILES="/etc/modprobe.d/modprobe.conf"

If you made changes to /etc/mkinitcpio.conf, don't forget to regenerate initramfs:

$ sudo mkinitcpio -p linux

Create /etc/X11/xorg.conf.d/20-intel.conf:

Section "Device"
    Identifier "card0"
    Driver "intel"
    VendorName  "Intel Corporation"
    BoardName   "Intel Corporation N10 Family Integrated Graphics Controller"
    BusID       "PCI:0:2:0"
EndSection

Reboot

Test if KMS on (should reply with 1):

$ sudo cat /sys/module/i915/parameters/modeset

Edit: Added FILES="/etc/modprobe.d/modprobe.conf" to /etc/mkinitcpio.conf (which was the crucial part, see my post #11 below).

Last edited by samuvuo (2011-12-24 13:10:18)

laerne · 2011-12-20 19:42:29

Thank you for your help.
I didn't say in my first post I didn't have i915 listed in mkinitcpio.conf at the first time, and that I eventually add it when I removed xf86-video-intel (I obviously forgot it). Loading it in mkinitcpio or not didn't change anything.

So now I've added that etc/X11/xorg.conf.d/20-intel.conf like karol and samuvoo, and i even added "options i915 modeset=1" in /etc/modprobe.d/modprobe.conf, but it still fails :

Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 20 20:28:05 2011
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) No devices detected.

Fatal server error:
no screens found

also it looks like I have no KMS enabled :

# cat /sys/module/i915/parameters/modeset
-1

Well, if KMS is the problem I don't know how to enable it.

Last edited by laerne (2011-12-20 19:43:40)

karol · 2011-12-20 19:47:33

I assume you have re-installed Intel driver, right? So now read the wiki on KMS :-) https://wiki.archlinux.org/index.php/In … Setting.29
First check your kernel commandline in grub to see if you haven't added 'nomodeset' there.

If you still can't get it to work, post the xorg log.

Last edited by karol (2011-12-20 19:49:12)

stqn · 2011-12-21 06:21:51

For what it's worth, on my Core i3 "cat /sys/module/i915/parameters/modeset" returns -1 too even though KMS is obviously on since it's mandatory and enabled automatically . Theorically there should be no need for any configuration with the intel driver, well, as far as I know...

karol · 2011-12-21 11:30:52

@stqn
You can disable KMS and then "cat /sys/module/i915/parameters/modeset" returns -1.

Ramses de Norre · 2011-12-21 11:37:15

I have -1 in that file as well but KMS is certainly enabled, I have, for instance, the fast tty switching, which was a lot slower in the pre-KMS days.
FWIW, I'm on a core2duo with a GM965 graphics chip.

laerne · 2011-12-22 13:16:07

Yes, i've reinstalled xf86-video-intel.

And I indeed booted with the nomodeset option.
I've regenerated my grub.cfg, and now I boot with

menuentry 'Arch Linux, with Linux linux' --class archlinux --class gnu-linux --class gnu --class os {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='(hd0,gpt1)'
    search --no-floppy --fs-uuid --set=root c8d85ba3-c490-49b6-a131-112bb2b5333b
    echo    'Loading Linux linux ...'
    linux   /vmlinuz-linux root=UUID=2351507b-5a31-4a7c-9e32-30ca91225d14 ro  quiet
    echo    'Loading initial ramdisk ...'
    initrd  /initramfs-linux.img
}

But still, my kernel complains with kms :

# cat /sys/module/i915/parameters/modeset
-1

Last edited by laerne (2011-12-22 13:25:06)

samuvuo · 2011-12-24 04:26:35

Ramses de Norre wrote:

FWIW, I'm on a core2duo with a GM965 graphics chip.

Same setup here. Have also installed Arch Linux on 10 Thinkpad R51 laptops (82852/855GM) that use i915 and they showed -1 unless i915 was loaded early + KMS enabled as early as possible (see below).

@laerne:

My mistake, and apologies for not monitoring this thread in a couple of days (busy times). Looks like I've left out one important step.

I forgot to add one (crucial?) piece to the recipe above. i915 gets loaded early (included in the initramfs) so KMS should be enabled as early as possible. On my setups I do this via adding to /etc/mkinitcpio.conf:

FILES="/etc/modprobe.d/modprobe.conf"

I believe the line is there already, just commented out. If you uncomment / add it, don't forget to re-generate the image afterwards (sudo mkinitcpio -p linux).

Or you can add i915.modeset=1 to kernel options in Grub. It's a matter of personal reference and setup style, including modprobe.conf suits mine better.

Could you please test that and tell us if it worked?

Last edited by samuvuo (2011-12-24 04:29:12)

laerne · 2011-12-24 09:38:05

Thank you very much ! I works !

# cat /sys/module/i915/parameters/modeset 
1

I've also edited modprobe.conf, I do not like very much to edit grub.cfg .

Many thanks to everybody who helped.

samuvuo · 2011-12-24 13:11:38

Great news! I've edited my post above (#4) to include the vital piece of the recipe.

1archgamenon2 · 2012-01-03 12:37:50

edited!

Last edited by 1archgamenon2 (2012-01-05 01:58:24)

1archgamenon2 · 2012-01-03 19:32:33

edited!

Last edited by 1archgamenon2 (2012-01-05 01:57:50)

1archgamenon2 · 2012-01-05 01:49:19

samuvuo wrote:

xf86-video-vesa

hi! can you explain me(us) why is necessary that driver if you have intel installed? what's the matter with it? is crucial on boot? I tell you cause if I remove(vesa) can't get X's...
sorry for being so 'newbie' on arch...

Last edited by 1archgamenon2 (2012-01-05 01:50:21)

1archgamenon2 · 2012-01-05 13:33:32

no one?

Lone_Wolf · 2012-01-06 13:19:23

1archgamenon2 wrote:

samuvuo wrote:
xf86-video-vesa
hi! can you explain me(us) why is necessary that driver if you have intel installed? what's the matter with it? is crucial on boot? I tell you cause if I remove(vesa) can't get X's...
sorry for being so 'newbie' on arch...

X detemines what videocard you have and then tries different drivers.

vesa and fbdev are the last 2 that are tried and useful as fallback options.

Last edited by Lone_Wolf (2012-01-06 13:19:37)

1archgamenon2 · 2012-01-08 20:59:20

RichAustin wrote:

This sounds sort of like an issue I had on ArchBang where the system tries to default to vesa. I fixed it by editing the following file:
sudo nano /etc/X11/xorg.conf.d/20-gpudriver.conf
Then replacing "vesa" with "intel" so the file reads like this:
Section "Device"
Identifier "Card0"
Driver     "intel"
EndSection

Hey pal...not so easy 4 me! perhaps to u!!

rhoit · 2013-01-13 02:46:06

It almost year late! but..
I'm bit confused with the -1 value of "cat /sys/module/i915/parameters/modeset" i guess intel graphics cards seems to run fine!
does 1 value means the intel driver being used?

jasonwryan · 2013-01-13 04:47:58

Please don't necrobump: https://wiki.archlinux.org/index.php/Fo … Bumping.27

1 means enabled.

Closing.

Arch Linux

#1 2011-12-19 21:05:28

[SOLVED] Use the xf86-intel-driver

#2 2011-12-20 09:43:17

Re: [SOLVED] Use the xf86-intel-driver

#3 2011-12-20 09:55:11

Re: [SOLVED] Use the xf86-intel-driver

#4 2011-12-20 10:11:35

Re: [SOLVED] Use the xf86-intel-driver

#5 2011-12-20 19:42:29

Re: [SOLVED] Use the xf86-intel-driver

#6 2011-12-20 19:47:33

Re: [SOLVED] Use the xf86-intel-driver

#7 2011-12-21 06:21:51

Re: [SOLVED] Use the xf86-intel-driver

#8 2011-12-21 11:30:52

Re: [SOLVED] Use the xf86-intel-driver

#9 2011-12-21 11:37:15

Re: [SOLVED] Use the xf86-intel-driver

#10 2011-12-22 13:16:07

Re: [SOLVED] Use the xf86-intel-driver

#11 2011-12-24 04:26:35

Re: [SOLVED] Use the xf86-intel-driver

#12 2011-12-24 09:38:05

Re: [SOLVED] Use the xf86-intel-driver

#13 2011-12-24 13:11:38

Re: [SOLVED] Use the xf86-intel-driver

#14 2012-01-03 12:37:50

Re: [SOLVED] Use the xf86-intel-driver

#15 2012-01-03 19:32:33

Re: [SOLVED] Use the xf86-intel-driver

#16 2012-01-05 01:49:19

Re: [SOLVED] Use the xf86-intel-driver

#17 2012-01-05 13:33:32

Re: [SOLVED] Use the xf86-intel-driver

#18 2012-01-06 13:19:23

Re: [SOLVED] Use the xf86-intel-driver

#19 2012-01-08 20:59:20

Re: [SOLVED] Use the xf86-intel-driver

#20 2013-01-13 02:46:06

Re: [SOLVED] Use the xf86-intel-driver

#21 2013-01-13 04:47:58

Re: [SOLVED] Use the xf86-intel-driver

Board footer