On Wed, 2002-11-20 at 11:27, lovswr1 wrote: > On Mon, 2002-11-18 at 21:18, Jesse Keating wrote: > > On 18 Nov 2002 20:03:02 -0500 > > lovswr1 <lovswr1@earthlink.net> wrote: > > > > # I also got the same error when i went from the kernel on the redhat > > # 8 discs, 2.4.18-14 to the current 2.4.18-17.8.0. I realized that I > > # did not have the source loaded for 2.4.18-14 & as soon as I did this > > # , I was able to upgrade. However, as noted above I did download the > > # latest kernel & its source files from redhat. Any help in this > > # matter would be greatly appreciated. > > > > You must be booted to the new kernel when you rebuild the nvidia rpms. > Yes I was. As I stated. When I try to boot into the new kernel, X does > not start & I then went to the command line. Two additional questions. > I have seen some other people describing similar problems. They all > seem to mention booting to command line only (run level 3?) & not even > attempting to start X. Will that make a difference? Also, do the no! However you get to the command line doesn't really matter. I usually do it this way (wait for X to fail, and then recompile) when I've forgotton that new linux kernel + old nvidia = no X! > nvidia drivers have to explicitly be for kernel ver.2.4-X.x.x? or will > the current ones work for just about all flavors of 2.4-X.x .x? Generally no! Only once did this work for me (and I don't remember the particular versions no.s) all other times I've had to recompile nvidia. It's not really too hard once you've done it a couple of times, just annoying. Have you got it going yet? -- Iain Buchanan <iain@nospam.pcorp.com.au> I think we are in Rats' Alley where the dead men lost their bones. -- T.S. Eliot
Attachment:
signature.asc
Description: This is a digitally signed message part
