[SOLVED]Problems with getting X to work

[Jaglover]

[LIsLinuxIsSogood]

Also which kernel modules have you tried building...i would suspect if you did some research about the difference between answering M or Y for different configuration settings within the kernel you would find that one reason modules exist could be in case of conflicting drivers, which could be the case here as well. As an added benefit it you build i915 as a module then it will be exactly the way that Neddy demonstrated it, which does not guarantee it being correct.

Also read over Jaglover's comment it is important. In terms of knowing which kernel you are on, and also having something that shows which branch of software you are on etc. I think it would be more helpful if you could run emerge --info from system once booted into and not through the chroot process you described earlier. Can you do this or is there some issue that is preventing that?

Please post back with emerge --info from the target system that will show the branch you are using and whether or not in order to change kernels, which is not a bad idea is really going to make a difference or not. Not sure about that last thing.

[Garbanzo]

How do I know which kernel version to get? I looked at sys-kernel/gentoo-sources and there are quite a few to choose from. Should I try the newest 14.18.3?

The emerge --info from the new system:

[Leio]

Looks like your Intel chip is rather new. I suggest using a 4.18.x kernel instead, to get all the latest improvements for your GPU. For new hardware these days it usually boots at hardware release time, but has various improvements the next couple of kernel cycles and then settles down. If you want to use the 4.14 LTS kernels, then it seems like (from the logs) that you need to enable alpha (experimental) support via kernel command line or an extra config knob, as the log you posted clearly tells:

[LIsLinuxIsSogood]

Another way of saying the same thing is pretty much you have to test out kernels, to see which ones work and don't work. A good guide is use what's in the portage tree those are patches sources, but you need to specify maybe during install what version and slot the packages should be installed.

In terms of upgrading I couldn't agree more with the previous post and especially with something sort of sensitive on a Gentoo host which is a working kernel for the system, what definitely makes sense there could be to lock in the working version by masking the more recent in package.mask until you are ready to continue moving to a new kernel.

[NeddySeagoon]

Garbanzo,

The newest 4.18 is a good choice for now.

If that gives the same message, you will need to enable that alpha support.
4.19.0-rc* series kernel will appear soon. Only try those, if 4.18 won't work for you.

There is a section in the handbook about mixing stable and testing.

-- edit --

There is the fallback of not using the Intel driver too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[LIsLinuxIsSogood]

On the more specific topic of utilizing graphics what I might also recommend rather than spend time recompiling the kernel is to edit the boot configuration entry within grub, using 'e' to edit at boot time, and then add the recommended portion to the line that begins with 'linux' as the first word that specifies the location and some simple boot parameters, and then press the key to boot. If it works then later you can recompile the kernel and if it does not then I'm pretty sure that fixing it in the kernel is not going to change anything either. But you gotta start somewhere.

By the way thanks Garbanzo for including the dmesg output and that definitely helped catch more of what could be contributing to this mess!

[Garbanzo]

Just an update. Upgrading to kernel 14.18.5 fixed the problem, twm runs fine. Next I'll try a DE.

Thanks for the help everyone.

[MikeNigh]

Thanks!!!!!

This got the intel graphics card working on my 9600k with asrock Z390M-ITX/ac !! (upgrading the kernel to 4.20.0 from 4.14.78 )

Also followed this -

https://wiki.gentoo.org/wiki/Intel

Didn't do any specific kernel passing parameters into grub etc.