Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co
!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-o
line.de!t-online.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Hadron 
Newsgroups: alt.os.linux.ubuntu
Subject: Re: Info: NVidia working with vmlinuz-2.6.17-10-386
Date: Sat, 03 Mar 2007 14:51:53 +0100
Lines: 87
Message-ID: <87wt1yxwna.fsf@geemail.com>
References:  <87fy8mpl9h.fsf@geemail.com>
 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: individual.net 0R2oQLZjBeXDqh14PtJZrgFAFEwYIO77JeqvLvcHd/Oiyvm/A0
X-Orig-Path: news.individual.net!news
X-Face:  2h#||Cd#d%F*NCm59[_6/{1a@jy%;|j>{D~4^gKg(^i%7j0IK?+,/GmW&:CD5fEKb_!
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)
Cancel-Lock: sha1:7FokgkgmuGq9uVSq4zajIVwsjVo=
Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:11348

Andreas Duffner  writes:

>>> This works:
>>> /boot/vmlinuz-2.6.17-10-386 root=/dev/hda6 ro vga=0x0307
>>> Perhaps this will help someone.
>>> Or if someone could tell why that is so ?
>
>> AFAIK they have nothing whatsoever to do with nvidia drivers : they are
>> kernel versions with a vga mode at boot time - before the drivers are
>> installed.
>
>
> You may *sound* right. But you *are* not right.

Hmm. I think you misunderstand.

> Because this is how it *is*. It is not some guessing or so.
> I do *not* know why that is so. But it *is*. Sorry.
>
> Why I even tried it was some post of someone who suggested to
> remove the "vga=blabla" part because this enables the framebuffer.
> Or so he told at least.
> I have no idea about all this stuff so I just tried it.
> It did not work.
> But while I tried that, I tried my old kernel.
> And that one worked with the new nvidia settings.

Yes. As I said, these are kernel versions - but they dont affect the
driver loaded. Yes, the driver must be compiled to work with the
specific kernel. But the kernel itself does not affect the driver - the
driver stays the same but just wont load.

Google up "envy milone" and download the envy script - it takes care of
installing the correct nvidia driver for your kernel. You can not then
switch between kernel versions as the driver (latest that is) must be
compiled for the specific kernel version.

>
> So again:
> The kernel version happens to have an effect on the nvidia driver.

No. It has no affect. The driver simply will not work with the wrong
kernel. If you see the difference.

> With the new one (I got it via the automatic update) does prevent
> my X-Server to start at all.
>
> The old one does start without any problems at all.
>
> Some people try for days to get nvidia cards to work.
> The normal working way is - as far as I read in this forum -
> to remove all nvidia stuff, get the nvidia-drivers from
> the nvidia homepage and let the driver so some
> kernel-compile-rebuild-stuff I do not understand.

Here, I did the google for you:

http://albertomilone.com/nvidia_scripts1.html

This should help you out.

>
> And would have tried that as last resort, because I do
> not want a graphics driver to rebuild my "kernel".
> I do not have any understanding of "kernels".
> I just think they are the system per se and the
> most important thing of my linux.
> And I fear that allowing some driver to change the kernel could
> interfere with the security updates.

The driver does nothing to your kernel. It is a loadable module which
must be compiled to match the kernel in question.

>
> Sorry if I talk nonsense :-)
>
> It seems you have some understand what a kernel "is".
> So you are in a better position you try to understand what happens.
> Please try. Just some ideas would be helpfully. Perhaps.  .-)

Follow the instructions at the link I gave and it should all just work.

Good luck.

-- 
"On the Internet, no one knows you're using Windows NT"
(Submitted by Ramiro Estrugo, restrugo@fateware.com)
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: Omicron Theta BBS (1:261/20)