List of video drivers:
intel
(++) Using config file: "/root/xorg.conf.new"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Number of created screens does not match number of detected devices.

When I do try this auto-generated xorg.conf file, the errors 'failed to load module vesa...' dissapear, but I still get the error:

Code:

(EE) No devices detected.

Fatal server error:
no screens found

I tried enabling/disabling i915.modeset=1 in the kernel line in /boot/grub/grub.conf, but no luck.
This seems like a very obvious problem yet I cannot find a solution? Rather recent hardware, installation from scratch, installing intel drivers and getting stuck.. I searched through a lot of fora but couldn't find a solution..
(also tried replacing Screen 0 "screen 0" 0 0 by Screen "screen 0" in the xorg.conf file.

Thanks for your help!

Last edited by katanatje on Wed Aug 17, 2011 2:54 pm; edited 1 time in total

Is KMS in your kernel? You don't need that modeset line in grub, KMS should be on by default, you should configure the kernel so that it is. Then, are you in the video group? And third, is udev running? Put it in the boot runlevel if it's not.

Finally, ignore those vesa and fbdev errors, they're just potential fallback drivers. But we don't want fallbacks, we want intel. Oh, and remove xorg.conf, you don't need it for intel.

Gusar, thanks for the information.
So.. I did step by step:
1) KMS in kernel: yes (was already there)
2) modeset line in grub: Removed (didn't change anything after rebooting)
3) KMS is ok in Kernel (enable modesetting by intel)
4) root was not yet in the video group. Added. (still same error)
5) udev: I put it in default runlevel (rc-update add udev) and rebooted. Still no luck. Why is it needed, actually?
6) Tried by removing xorg.conf, then using the xorg.conf file, both didn't work. The errors are still the same.

Thanks for the advice, but unfortunately, no luck so far.
I'm suprised I cannot get it to work, as I don't do anything fancy. xorg-server doesn't have to be re-emerged after emerging the xf86-video-intel drivers, does it? Also, I can't find any reference for xf86-video-intel in the original gentoo xorg guide (see link in my first post). Maybe it would be wise to put it there as well?

edit: I added udev to boot runlevel. No change.

Regards,
Katanatje

Last edited by katanatje on Tue Aug 09, 2011 12:05 pm; edited 1 time in total

5) udev: I put it in default runlevel (rc-update add udev) and rebooted. Still no luck. Why is it needed, actually?

For the /dev/dri/* device nodes.

VoidMage wrote:

First of all, udev should be in sysinit runlevel.

Bah, I never get that right . Does it really matter though?

VoidMage wrote:

That aside, pastebin whole xorg log

That is good advice. I have a feeling though it won't tell anything useful. There's been a lot of such threads lately, intel driver simply bombing out without giving a useful error. In some cases it was due to lack of udev, in some not even udev helps. It's a weird Gentoo thingy. Just like that nvidia and gtk thingy that you can read about at the nvnews forums, only Gentoo users reported it.

Edit: Log was posted as I was writing this post. And just as expected, no useful error in it.

Actually, I am logged in as root user I know you can start x as normal user, but for now, it doesn't work, and I'm editing xorg files etc... all the time, so I'm logged in as root (I know, I know, I shouldn't do that, I should only log in as root when really necessary :p)

Gusar wrote:

VoidMage wrote:

First of all, udev should be in sysinit runlevel.

Bah, I never get that right . Does it really matter though?

Well.. so.. apparently it doesn't really matter for this issue, if you just followed the gentoo documentation, it's probably good already.

Gusar wrote:

Edit: Log was posted as I was writing this post. And just as expected, no useful error in it.

Yup.. been looking into the log myself but couldn't find anything useful....

This will create much more detailed log, maybe it'll be more useful than the default log.

Other than that... What kind of a machine is it (laptop, desktop), which video outputs are you using (vga, dvi, hdmi) and to what are they outputting (crt, lcd)? Not that it matters, it should work out of the box. You could try LiveCD/LiveUSB versions of other distros, see if those get it right. I recommend Parted Magic, it's a great distro of this kind, it is advisable to always have it around on a cd or usb stick.

Other than that... What kind of a machine is it (laptop, desktop), which video outputs are you using (vga, dvi, hdmi) and to what are they outputting (crt, lcd)? Not that it matters, it should work out of the box. You could try LiveCD/LiveUSB versions of other distros, see if those get it right. I recommend Parted Magic, it's a great distro of this kind, it is advisable to always have it around on a cd or usb stick.

It's a desktop. Using VGA. I also have a DVI output, maybe I can try that one? They are outputting to LCD (Samsung SyncMaster T220). I used GParted to set up the partitions in a X environment, and that worked.

..ok so I tried to switch from VGA to DVI, no luck. Then I tried to copy the xorg.conf file from my laptop, which is connected to the same screen, to my computer (the VGA specs). I just changed driver from nvidia to intel (because my laptop was running an nvidia card). The relevant part here:

With Intel, only KMS is supported. If you disable KMS then X will not start.

Check your kernel configuration again, via /proc/config.gz (requires IKCONFIG_PROC enabled) because that is the only reliable way to determine the configuration of the currently running kernel. /usr/src/linux/.config and /boot/config-`uname -r`are less reliable in this regard.

Invalid module format means that the kernel does not match the modules. Verify with "uname -a" (build date and time) that modules and kernel were built at the same time.

I looked up this error and found the same as you are saying: Check whether it matches..
Apparently, I was making new kernels all the time without copying them to boot... Sorry for this extremely newbie-problem!!
The reason I forgot is that I started out with a genkernel approach, but switched to manually compiling the kernel afterwards..

So... I copied the compiled kernel over (using make install). I made a new option in the grub bootloader, saying