Thanks again Michael
It so happens I went to the Nvidia website today, and they have updated
their linux drivers...
S' all working just fine ... for now :p
AL3XR
Michael Schwendt Wrote:
>
> > I have been trying to install the updated drivers for my nvidia
> > graphics card, and it seems th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Dec 2002 13:56:14 +0800, Alex RENE wrote:
> I have been trying to install the updated drivers for my nvidia
> graphics card, and it seems there might be a conflict during the
> install... To summarize what I did:
>
> I run RH8 on a pentium III
Alex RENE wrote:
> Hi there... again...
>
> I have been trying to install the updated drivers for my nvidia graphics
> card, and it seems there might be a conflict during the install... To
> summarize what I did:
>
> I run RH8 on a pentium III => kernel-2.4.18-18.8.0 i686
>
> Went to Nvidia webs
Hi there... again...
I have been trying to install the updated drivers for my nvidia graphics
card, and it seems there might be a conflict during the install... To
summarize what I did:
I run RH8 on a pentium III => kernel-2.4.18-18.8.0 i686
Went to Nvidia website, downloaded an ran NVchooser ap
On Thu, 16 Apr 1998, Phillip Johnson wrote:
> I know I am being dense, but if I just point to a different kernel using lilo,
> how do I get past the module dependencies? It seems to me like I have deleted
> the old modules during the kernel compile. How do you get around this?
>
> Phil
> (feel
>I know I am being dense, but if I just point to a different kernel using lilo,
>how do I get past the module dependencies? It seems to me like I have deleted
>the old modules during the kernel compile. How do you get around this?
>
>Phil
For a completely different kernel version, that shouldn'
>
> I thinking of bringing up the 2.1.96 kernel.
>
> Has anyone set up Redhat so that a good/working 2.0.32 kernel and all of its
> stuff is available for use in case something goes wrong with a newer kernel?
Easiest, I think, would be to keep your existing known-good kernel on the
hard drive,
for let's say 2.0.33 go in /lib/modules/2.0.33 and the modules
for 2.1.89 go in /lib/modules/2.1.89
The kernel knows where to look.
also do a man lilo.conf
that should explain how to set up multiple kernels. just
copy the corresponding section in lilo.conf for linux to a new entry, change
> I know I am being dense, but if I just point to a different kernel
> using lilo,
> how do I get past the module dependencies? It seems to me like I have
> deleted
> the old modules during the kernel compile. How do you get around
> this?
>
[Tempel, Philippe] If the kernel is a differ
best thing would be to have a separate partition that is
>> bootable from LILO, with the good distribution bootable as well.
>
> Sounds like too much work to be useful. :) Why not just have multiple kernels
> that you choose which one to boot from the lilo prompt. For example
>
would be to have a separate partition that is
> bootable from LILO, with the good distribution bootable as well.
Sounds like too much work to be useful. :) Why not just have multiple kernels
that you choose which one to boot from the lilo prompt. For example
in addition to having choices like
> I thinking of bringing up the 2.1.96 kernel.
>
> Has anyone set up Redhat so that a good/working 2.0.32 kernel and all
> of its
> stuff is available for use in case something goes wrong with a newer
> kernel?
>
> I suspect that the best thing would be to have a separate partition
> that is
> b
I thinking of bringing up the 2.1.96 kernel.
Has anyone set up Redhat so that a good/working 2.0.32 kernel and all of its
stuff is available for use in case something goes wrong with a newer kernel?
I suspect that the best thing would be to have a separate partition that is
bootable from LILO, w
13 matches
Mail list logo
