| Summary: | An error that MTRR is not loaded occurs when following the install instructions and trying to load nvidia-kernel while in the chroot environment on the LiveCD boot. | ||
|---|---|---|---|
| Product: | Gentoo Release Media | Reporter: | Johnny Hughes <jhughes> |
| Component: | Everything | Assignee: | Daniel Drake (RETIRED) <dsd> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | andrewbevitt |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://www.gentoo.org/doc/en/gentoo-x86-install.xml | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Johnny Hughes
2003-08-12 05:08:41 UTC
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 |