The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
#required by media-libs/mesa-9.0.1[-gbm,xorg], required by x11-base/xorg-server-1.13.1[-minimal], required by x11-drivers/nvidia-drivers-313.18[X], required by x11-base/xorg-drivers-1.13[video_cards_nvidia]
=x11-libs/libdrm-2.4.40 libkms

so it looks like we need mesa and libkms, which won't emerge (mesa) and we took out (libkms)...

so I tried emerge'ing mesa and I see that libkms is necessary for that too...

CFLAGS="-O2 -pipe"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j3"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="bindist mmx sse sse2 X dbus consolekit policykit udev udisks bzip2 ipv6 truetype nptl suid xorg libkms minizip"

Remove the USE= line after taking note of the flags you have there. An Easy way to do this is to Comment it out, like so:
#USE="bindist mmx sse sse2 X dbus consolekit policykit udev udisks bzip2 ipv6 truetype nptl suid xorg libkms minizip"
Then repost:

Make sure profile is set to 13/desktop/kde
By Commenting out USE we are forcing your System to rebuild itself using only the flags inherited from your profile that we set/verified above. Your base still isn't clean We are almost there though_________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

, and we are both off to bed... I'll show you how to add all your flags back and more, with an interesting old tool, but we need to rebuild these 1st. In case you couldn't tell I APPROVE. Get to building these _________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

Last edited by eyoung100 on Wed Mar 06, 2013 5:56 am; edited 1 time in total

Making all in mesa
gmake[2]: Entering directory `/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1/src/mesa'
GEN main/api_exec_es1_dispatch.h
GEN main/api_exec_es1_remap_helper.h
GEN main/api_exec_es1.c
Error: unable to dicide the max size of params in Fogxv
Error: unable to dicide the max size of params in GetLightxv
Error: unable to dicide the max size of params in GetMaterialxv
Error: unable to dicide the max size of params in GetTexEnvxv
Error: unable to dicide the max size of params in GetTexGenivOES
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in GetTexGenxvOES
Error: unable to dicide the max size of params in GetTexParameterxv
Error: unable to dicide the max size of params in LightModelxv
Error: unable to dicide the max size of params in Lightxv
Error: unable to dicide the max size of params in Materialxv
Error: unable to dicide the max size of params in PointParameterxv
Error: unable to dicide the max size of params in TexEnvxv
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in TexGenivOES
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in TexGenxvOES
Error: unable to dicide the max size of params in TexParameterxv

Making all in mesa
gmake[2]: Entering directory `/var/tmp/portage/media-libs/mesa-9.0.1/work/Mesa-9.0.1/src/mesa'
GEN main/api_exec_es1_dispatch.h
GEN main/api_exec_es1_remap_helper.h
GEN main/api_exec_es1.c
Error: unable to dicide the max size of params in Fogxv
Error: unable to dicide the max size of params in GetLightxv
Error: unable to dicide the max size of params in GetMaterialxv
Error: unable to dicide the max size of params in GetTexEnvxv
Error: unable to dicide the max size of params in GetTexGenivOES
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in GetTexGenxvOES
Error: unable to dicide the max size of params in GetTexParameterxv
Error: unable to dicide the max size of params in LightModelxv
Error: unable to dicide the max size of params in Lightxv
Error: unable to dicide the max size of params in Materialxv
Error: unable to dicide the max size of params in PointParameterxv
Error: unable to dicide the max size of params in TexEnvxv
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in TexGenivOES
No base converter for type 'GLint' found. Ignoring.
Error: unable to dicide the max size of params in TexGenxvOES
Error: unable to dicide the max size of params in TexParameterxv

Not sure if I should continue with rm -vR /usr/src/linux-3.7.9-gentoo yet...

gotta run, and will be away from comps all morning, and will get back this afternoon. Thanks e

Get used to those, that's normal, just looked at your outfile, and saw:

Quote:

>>> Installing (26 of 26) net-misc/openssh-5.9_p1-r4

which means it finished successfully. The only thing we need to worry about now (if you want to use KDE, while rebuilding it) is making sure KDE starts:

Quote:

* WARNING! Your system configuration contains neither "kde-base/kdebase-runtime-meta"
* nor "kde-base/kdebase-startkde". You need one of above.
* With this setting you are unsupported by KDE team.
* All missing features you report for misc packages will be probably ignored or closed as INVALID.

What is the output of:

Code:

emerge -avt kde-meta
lspci
cat /etc/X11/xorg.conf

The First Command Tells me if all of KDE installed. The Second will list all your pci devices so I can see if nvidia drivers are really what yoou have, since you said you tried to login and saw garbled lines. The Third tells me howX is configured. It's OK to manually delete the Kernel source because if we need it again we unmask and emerge it._________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

What was weird about the login was that it had a login/pass sequence and then the screen went black for a half second and then it returned to the login screen again, as if I'd messed up my password or something. Also, it's a graphical login, but certainly not kde or gnome. No garbled lines though.

UFED is the Gentoo Use Flag EDitor, catchy name Using this tool we are going to slowly add back all the flags we took out, until the system is Completely customized the way you want it. A small explanation is in order here, but it's easier to explain by doing than by telling, so before you "activate" the code blocks below:

Code:

emerge ufed

Start ufed by typing ufed as root

Type X, it should search for all Flags starting with X of which there is only 1.

There should be a + Next to X. This plus signifies that a Use Flag is being inherited from your build profile, set with eselect profile. Hitting spacebar should add another +, and the entry will now look like ++X. This is redundant, as the first + is a user enabled Flag, and the second + is explained in the previous sentence. Hitting spacebar again changes your user flag to a -, since X is inherited from your profile, setting a minus here would override the default profile. A speccial note on -*:

-* sets all flags inherited by a profile to off, meaning that you must set the inherited Flags as user flags. Some people do this and some people don't. I happen to fall in the camp that doesn't, unless I'm troubleshooting a particular package. Hit Esc. When asked to save, hit N, and now start the code blocks. Once saved, /etc/make.conf is written to with your changes.

The First Code Block gives us a default xorg.conf file with only the binary driver installed. This Prepares us for KDE later on. The Second Code Block adds the flag required by PyQt in order to emerge kde-meta and removes the Gui from the Auto Boot at startup so we can see if it still crashes using plain startx in the Third Code Block, which actually emerges all of KDE._________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper

Donahue and I solved these steps from the bottom up That's the quickest way to properly remove udev I've seen to date. I solved the KMS error by skipping KMS setup altogether by switching you to nvidia-drivers. I had no idea that nvidia-drivers doesn't support kernels >3.6, so that stretched out the post. I "cheated" by having you use genkernel so we wouldn't waste time deciding on drivers etc. For an explanation of why I prefer genkernel see:Initial RAM Disk HOWTO. When I wrote that post, I was still building kernels by hand, following the handbook. What I've learned since then is that a genkerneled kernel provides a responsive system, more so than hours of tweaking my own config. This is of course personal preference. Moving on...
Because I decided to abandon nouveau in favor of nvidia-drivers, I had to establish a working baseline before I added stuff that didn't work. I did that by:

Having removed the need for libdrm in the new kernel, I removed all use flags to prevent compile issues with KDE.

Barring compile issues, kde-meta will give you a full running desktop

You'll notice that if any of the above or below steps fail, you have a working system that's able to compile because the circular dependencies have been removed. Logic dictates that if we make a mistake, we go in reverse to the listed 2 items above, and start over.

From now on/System Maintenance and Upkeep

Using ufed is the proper way to add them back for many reasons. These reasons include typo prevention, you can read what the flag actually does and what package it affects before enabling it.

As you add flags using ufed, only add a few at a time to prevent issues like the udev blocker earlier. You'll find that some flags require other flags. Flag Stacking is what causes the nasty dependencies like we solved between libdrm and mesa

After adding flags, proper use of emerge should be followed. Proper use dictates the use of the N flag to catch packages affected by the flags you set. Best Practice is:

Code:

emerge -uDN world

When switching or updating profiles, unless otherwise noted in a HOWTO always use the --emptytree option -e for short. This rebuilds every package on the system up to the package being emerged. Most people don't use -e with a package but with the world set:

Code:

emerge -e world

will rebuild every installed package in the proper order. It is the parent of -uDN

Messages for package kde-misc/kde-gtk-config-2.1.1:
WARNING! Your system configuration contains neither "kde-base/kdebase-runtime-meta" nor "kde-base/kdebase-startkde". You need one of the above.

Messages for package kde-base/kdm-4.9.5:
You have compiled 'kdm' with consolekit support. If you want to use kdm, make sure consolekit daemon is running and started at login time
rc-update add consolekit default && /etc/init.d/consolekit start

Add Consolekit support as donahue suggested and YOU ARE FINISHED Can you believe it Thought of something else. Be sure and add the nvidia kernel module to your autoload file. I cant remember the name for the new kernel versions but the old one was /etc/modules.autoload.d/kernel-x.y. I think the new one is /etc/conf.d/modules.autoload _________________The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735Adopt a Post | Strip Comments| Emerge Wrapper