When using the instructions for "Using genkernel to compile your kernel" (while still in the chroot environment) it says to emerge nvidia-kernel. This produces an error that the kernel doesn't have MTRR support enabled. (At least on the LiveCD 1.4rc4.) This isn't a major problem ... I just enabled the MTRR in the kernel and did the merge after I restarted on the new kernel. The fix would be either wait until a reboot with MTRR enabled in the kernel ... OR ... enable MTRR on the liveCD boot so the module will load. Reproducible: Always Steps to Reproduce: 1. Try to emerge nvidia-kernel with when booted from the liveCD (1.4rc4) per the install instructions. Actual Results: kernel doesn't have MTRR support enabled Expected Results: emerge nvidia-kernel Also, since some of the additional hardware drivers listed on the table in the section will load XFree86 ... specifically emu10k1 did with X enabled on the USE= line ... wouldn't it be better to emerge those drivers after you boot on your new kernel?
I guess it isn't a PITA to add MTRR to the LiveCD... LiveWire?
It seems the check for mtrr was introduced in response to bug 12015 but it is overkill. I ran into this after a kernel upgrade. mtrr was enabled in the kernel, but the processor didn't support it. The nvidia driver had been running fine before the kernel upgrade, so I commented out the mtrr check in the ebuild. emerge nvidia-kernel ran smoothly and everything's working fine again. mtrr may be required in some environments but not all, so I would prefer to see this total block replaced with a warning thet mtrr _may_ be required. K6 350 (doesn't support mtrr) TNT2 Ultra linux-2.4.25-gentoo-r2 with mtrr enabled nvidia-kernel-1.0.4496-r3
From an xfree perspective I dont see nvidia-kernel as something that should be merged before you have rebooted into your installed system... That almost suggests X11 and its drivers are part of the system profile (which they shouldnt be). IRT the mtrr block in the ebuilds its easier to make people have it in their kernel then say it maybe required and have to field everyone not reading / checking ... well thats my oppinion.
old bug, reopen if necessary
