* Claude Jones [06/03/07 16:38]: > The danger you cite has never manifested for me. If the module fails to build, > generally, the system just boots using the Linux nv driver - I've never > experienced the event you describe. > I have limited experience, but a very bad one. When I tried to install the dell provided rpm I was left with messages at boot up that the nvdia module was missing and couldn't do much still I found the livna driver. > Regarding your question, it seems like even should that be possible, you would > end up doing more work than just putting up with a couple of days delay till > the new Livna modules are released - but, your concerns/needs may be > different than mine > No problem with waiting, my concern is that this morning I had to reboot and found out that the last kernel that yum had updated last night was not able to use my previous nvidia module. So how should I proceed with the updates? If I update the kernel in a couple of days will "yum" download the nvdia driver automatically, or should I update it simultaneously? I'm sort of confused as you see... Another question. In Gnome if I go to System - Administration - Display - Hardware - Video Card - Configure I see that the one that is chosen is: nvidia - Vendor supplied driver for nvdia cards while just above I can see: nv - nvidia Riva 128, RIVA TNT, GeForce, Nforce and Quadro cards My card is 256Mb nVidia Quadro FX3500 Graphics Card shouldn't then I be using the "nv" configuration instead of the "nvidia" one? -- Walter Garcia-Fontes Barcelona
