More problems after delleting kernel

[stan]

On Mon, May 02, 2011 at 10:24:43AM +0100, Alan Pope wrote:
> On 2 May 2011 01:12, stan <stanb at panix.com> wrote:
> > Setting up nvidia-current (195.36.24-0ubuntu1~10.04) ...
> > update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode.
> > update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group gl_conf) doesn't exist.
> > update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of link group gl_conf) doesn't exist.
> > update-initramfs: deferring update (trigger activated)
> > Loading new nvidia-current-195.36.24 DKMS files...
> > First Installation: checking all kernels...
> > Building only for 2.6.32-31-generic
> > Building for architecture i686
> > Building initial module for 2.6.32-31-generic
> >
> 
> Looks good.
> 
> What's the issue you have now?
> 
 X still comes up with a warning about running in low resolution mode. I
 ran nvidia-config, and it created a new X config file, but when I restart
 X it still comes up in very low res mode.

 lsmod does show nvdiiafb loaded afterr I modprobe it now, thogh.

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?