Have you got a version of 2.6 that is booting to command line?
If so this should allow you to get X to work by installing a Nvidia kernel 
driver for 2.6

Boot to command line in 2.6 if you want.
Download NVIDIA-Linux-x86-1.0-XXXX-pkg#.tar.bz2 chosing the version XXXX which 
equals the current nvidia driver you have installed and 
NVIDIA_kernel-1.0-XXXX-2.6.diff.bz2.
as root go to /usr/src and make sure the link linux there is pointing to your 
2.6 kernel source. If it isn't remove the link
rm linux
then create a new link to the kernel source
ln -s /whereeverthesourceis/linux-2.6.0 linux

then go to where the Nvidia driver is installed. and follow these 
instructions.
http://www.minion.de/files/NVIDIA_kernel-1.0-4620.README (this is for Nvidias 
4620 kernel version) you'll find readme's for the other versions at 
http://www.minion.de/ the links to the readmes are right in front of the 
patch files and on Mozilla for me they appear to be one big long link when 
acctually the first half is a link to the readme the second to the patch.

-------------------
If you already installed the NVIDIA 1.0-4620 driver using the official
installer on a supported Linux 2.4 kernel, have only recently decided to
experiment with Linux 2.6 and wish to use the NVIDIA binary driver, you
can achieve this by following these instructions:

FAQ: The 1.0-4496 driver release introduced the -pkg# suffix to the .run
file to distinguish between packages with the same driver version, but
with different sets of precompiled kernel interfaces. The -pkg0 file has
no precompiled kernel interface files and was thus chosen here.

You can use other revisions, but need to adapt the package number below.

1) download:

   NVIDIA-Linux-x86-1.0-4620-pkg0.run       (nvidia)
   NVIDIA_kernel-1.0-4620-2.6.diff.bz2      (minion.de)

2) install the kernel module (as root):

   # sh NVIDIA-Linux-x86-1.0-4620-pkg0.run --extract-only
   # cd NVIDIA-Linux-x86-1.0-4620-pkg0
   # cd usr/src/nv
   # bzcat ../../../../NVIDIA_kernel-1.0-4620-2.6.diff.bz2 | patch -p1
   # ln -s Makefile.kbuild Makefile
   # make install

The instructions assume that you are running the target kernel. If that
is not the case, you can still build the kernel module for that kernel,
but since the KBUILD Makefile only respects the KERNDIR directive when
it builds the module, you'll have to install the module manually; as an
example (instead of 'make install'):


On Sun, 21 Dec 2003 22:07, anton wrote:
> >best of luck.
> >
> >Is it time for another OSTC kernel compiling lesson? All afternoon one
> > day.
>
> Well, unfortunately lady luck has eluded me on this one. I have an
> nvidia graphics card and to be quite honest I don't know what the
> fudge-ripple icecream I'm doing! I have to patch the driver I think, but
> I don't really how or where, or whether I have downloaded the right
> things. There are lots of "required" things that have to be installed to
> do it properly - half of them aren't available in mdk rpms, which means
> finding them and installing from source. Not that hard, but do I really
> need to install the isdn support just to compile a kernel that will not
> have isdn support?
>
> And what about initrd? surely I need to do something with that. Not that
> I really know what it does apart from something to do with creating an
> initial ram-disk or something of that nature... My other two installed
> kernels (rh9 and mdk9.2 standards) have initrds and also system maps
>
> And configuration! The "just get to it" philosophy is great. I really do
> like it and don't mind breaking things but I think that far too many
> people have configured far too many kernels and have forgotten just how
> completely bewildering the hundreds of options that may or may not be
> necessary for the kernel to work. Lots of options seem to default to
> values that the comments (make xconfig) say are NOT recommended! hmmmm.
> And what about the drivers. I can work out what I've got (lspci, etc)
> and have managed to unselect most of the hundreds of other useless
> drivers ( for me, again why the defaults?) but some things seem to be
> useful. What are these "useful things", oh that's easy, you just "know".
> Great.
>
> I know kernel configuration is NOT a newbie thing to do and I am
> certainly still a newbie, but a kernel configuration session OSTC would
> be MOST appreciated!
>
> Thanks and PLEASE FORGIVE my tone. I have just had a rather frustrating
> weekend of garbled screens full of errors when my spanking new 2.6.0s
> fail miserably!
>
> Anton

Reply via email to