| View previous topic :: View next topic |
| Author |
Message |
Snagarelle
n00b
Joined: 11 May 2003
Posts: 23
|
 Posted: Wed May 28, 2003 5:01 pm Post subject: Nvidia GeForce Install problems: MTRR error |
 |
|
When I did an emerge nvidia_glx it returned an error saying that MTRR support was not in the kernel so i dutifully went into the kernel and selected it [*] and then recompiled. I rebooted and emerged nvidia_glx resulting in the same error. I then went back into my kernel and unselected it again and rebooted, then i again went into my kernel and reselected it, again the same error. So with all this recompiling ALSA was broken, I fixed it, but I still cannot use my nvidia card. Anybody run into this problem and/or know how to fix it.
Thanks everybody |
|
| Back to top |
|
 |
shadow255
Guru
Joined: 04 Apr 2003
Posts: 412
|
| Posted: Wed May 28, 2003 5:13 pm Post subject: Re: Nvidia GeForce Install problems: MTRR error |
|
|
| Snagarelle wrote: | | When I did an emerge nvidia_glx it returned an error saying that MTRR support was not in the kernel so i dutifully went into the kernel and selected it [*] and then recompiled. |
Whoa there, did you also copy the bzImage over to /boot so that your reboot would use it? It's an important step which I don't see you mentioning!
| Snagarelle wrote: | I rebooted and emerged nvidia_glx resulting in the same error. I then went back into my kernel and unselected it again and rebooted, then i again went into my kernel and reselected it, again the same error. So with all this recompiling ALSA was broken, I fixed it, but I still cannot use my nvidia card. Anybody run into this problem and/or know how to fix it.
Thanks everybody |
If you actually copied over the bzImage after compiling in MTRR support, I probably can't help you. Good luck!
_________________
Vogon poetry is of course the third worst in the Universe. -- Douglas Adams, The Hitchhiker's Guide to the Galaxy |
|
| Back to top |
|
|
TheCoop
Veteran
Joined: 15 Jun 2002
Posts: 1814
Location: Where you least expect it
|
| Posted: Wed May 28, 2003 6:17 pm Post subject: |
|
|
i take it nvidia-glx is a typo? The kernel module is nvidia-kernel, and make sure you mount /boot then copy the kernel across before rebooting
_________________
95% of all computer errors occur between chair and keyboard (TM)
"One World, One web, One program" - Microsoft Promo ad.
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler
Change the world - move a rock |
|
| Back to top |
|
|
TheAgent
n00b
Joined: 23 May 2003
Posts: 29
Location: Waukesha, WI
|
| Posted: Wed May 28, 2003 8:29 pm Post subject: |
|
|
...and if you're using LILO, run it after you copy bzImage to /boot... otherwise, you won't boot into the new kernel...
it doesn't make much sense to me, but that's what i have been told and it seems to be true...
_________________
TheAgent
Total Linux N00b
Shuttle SN41G2:
Athlon XP 2100+
512 MB Corsair PC2700
40GB Maxtor
NForce2 Soundstorm, VGA, Network |
|
| Back to top |
|
|
shadow255
Guru
Joined: 04 Apr 2003
Posts: 412
|
| Posted: Wed May 28, 2003 11:22 pm Post subject: |
|
|
| TheAgent wrote: | ...and if you're using LILO, run it after you copy bzImage to /boot... otherwise, you won't boot into the new kernel...
it doesn't make much sense to me, but that's what i have been told and it seems to be true... |
Good point. The reason you must run /sbin/lilo after replacing the kernel image in /boot is so that the boot loader gets absolutely correct information about the location and size of the image file. In general, I don't usually replace a working kernel image with one I've just compiled, so my steps to replacing the image would be something like this:
- Compile the new kernel
- cp /usr/src/linux/arch/i386/boot/bzImage /boot/testing20030528
- Modify /etc/lilo.conf, adding the new target image (usually cloning the section for my working kernel and modifying appropriately)
- /sbin/lilo
- Cross fingers and reboot
Note that in step 2 I'm using a numeric representation of today's date in the filename for purposes of differentiation and (hopefully) uniqueness.
Later on, when I've decided that the kernel will work okay, I'll remove the entry from lilo.conf for the previous working kernel, but still leave that image on /boot (you never really know!). Of course, this is no longer how I do things because I've switched to GRUB, but it should work pretty well if you're using LILO.
_________________
Vogon poetry is of course the third worst in the Universe. -- Douglas Adams, The Hitchhiker's Guide to the Galaxy |
|
| Back to top |
|
|
Weejoker
n00b
Joined: 11 Sep 2002
Posts: 69
Location: Scotsman in England
|
| Posted: Fri May 30, 2003 10:29 am Post subject: |
|
|
Just a quick point (probably irrelevant) - the emerge of the nvidia-kernel failed with me once (giving MTRR error) because /usr/src/linux didn't point to the currently used sources. 
I had gs-sources as the running kernel at the time, but with gaming-sources sym-linked to /usr/src/linux, thus giving the emerge process a headache when it saw the irregularities between the running kernel and default source.
Summary: Have your current kernel source located at /usr/src/linux, preferably by symbolic link.
John [/b] |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
