Mailinglist Archive: opensuse (888 mails)

[Mark Misulich <munguanaweza@xxxxxxxxx>]

On Sun, 2011-01-09 at 18:16 -0500, Patrick Shanahan wrote:
> * Mark Misulich <munguanaweza@xxxxxxxxx> [01-09-11 17:55]:
> > I just did a software update via yast after being away from home on a
> > two-week business trip.  One of the patches installed was an upgrade to
> > the 2.6.37 default kernel. After a reboot, I can't get to a working
> > desktop anymore.
>
> ...
>   
> > I wonder if the Nvidia graphics driver didn't upgrade to match the new
> > kernel, and if that is the source of the problems?  If so, how does one
> > upgrade it by booting to runlevel 3 and using command line when booting
> > the 2.6.37 kernel?
>
> I cannot tell you how to replace your kernel, but someone will.  
>
> You can install the downloaded binary NVidia driver:
>   sh ./NVIDIA-Linux-x86_64-260.19.29.run -a -K
>
>   -a   accepts license
>   -K   keeps that particular nv kernel driver when you install another 
>        kernel
>
> note: you need kernel-devel for the nvidia binary to update your kernel
> driver. (and maybe kernel-source, I have them both).
>
>
> Suggestion.  I *never* replace a running kernel until I am satisfied the
> new kernel is completely usable.  I have three kernels installed in
> tandum at the moment:
>   kernel-default-2.6.31.14-2.1.x86_64
>   kernel-default-2.6.36-94.1.x86_64
>   kernel-default-2.6.37-33.1.x86_64
>
> and am using 2.6.37 on 11.2 x86_64
>
> btw, I do not normally use yast to install software, either zypper or rpm
> on the commandline.
>
> Let me know if I can help further.

I downloaded the Nvidia driver binary from the Nvidia website last
evening, and saved it to my home folder.  Then, I booted the 2.6.37
kernel last evening to runlevel 3.  After that I tried to cd to the
place in my home folder where I saved the Nvidia driver so I could use
the run command you gave me to install the driver in that kernel.  But I
couldn't cd to the driver.  

I played around with commands, and found that there was no home
directory present with that kernel.  So the upgrade to the 2.6.37 kernel
went bad. 

I still have the 2.6.34 kernel entry in grub that I can use to boot the
operating system, which happens to be what I am using now.  Now I am
wondering what is next?  Why hasn't this upgrade to a new kernel worked
for the last few months, and how do I get it to upgrade sucessfully?

I am open to your inputs.

Mark


-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx