I accidentally updated my system. Big mistake.

English Install/Boot/Login
1

I am one of those bad people who has an Nvidia graphics card.
Because we are evil people who use stuff with Bad Licenses,
when my system got updated, the graphics driver was not migrated.
Yes, I am a lot irritated. It should not be so difficult
to recover, but it is. I found this nice link that said, “click
this and everything will be better”. Sure. Cool. Except that
I am running on a live CD and not openSuSE so the click only
works if you have graphical Yast installed and you’ve booted
from the root partition. Guess what? It doesn’t work because
the graphics are all screwed up because the nvidia driver does
not load. Very clever.

Now that I’m done ranting, here’s the question: Is there some
place where I can download something or another that will
reconfigure the nvidia rpm so I can have my system back?

2

Boot to command line
press 3 at boot then boot
log on as root
type
sax2 -m 0=vesa (that is a lower case o not a zero)

type
init 5
to start GUI

install the NVIDIA driver and reboot.

3

Wilson_Philips, I’m sure you are reading these threads too. Maybe you should paste the URLs of such threads into openFATE so that the devs can see that this is a real issue.

4

Just found it.

Will do.:slight_smile:

5

opps I said that backwards “that is a lower case o not a zero” should be “that is a zero not a upper case o”

6

Ah. Thank you! That ought to do it. I’m guessing the sax incantation
forces the GUI (X) into some basic vesa mode before going to run level 5.
Thanks!! Regards, Bruce

7

Yes it replace the nvidia driver with the generic vesa driver so you can get to the GUI. You need to re associate the kernel and NVIDA driver for things to work. It all depends on how you installed the NVIDIA driver in the first place. If you used a download from NVIDIA there is no info placed in the RPM database about the relations ship. So when a kernel update happens there is no way that the RPM mechanism can know that they need to be linked. If you use the one step the driver comes from a repository and the relationship is remember at the next kernel update.

If you have the NVIDIA installer then you just need to run it again to get things back and can skip the vesa step. I think there is a command line parameter you can pass that just does the link step ie it does not need to recompile. But I forget what it is , Check the Docs on NVIDIA

In any case it is good to know how to do things from the command line.

8

All ya gotta do is know the right incantations. I don’t. I also don’t want to be forced to do all the research necessary to figure it out. It takes hours (I’ve done it) and then the next time it happens, it is all forgotten and the research has to be redone. Ick.

You need to re associate the kernel and NVIDA driver for things to work. …] If you used a download from NVIDIA there is no info placed in the RPM database about the relations ship. So when a kernel update happens there is no way that the RPM mechanism can know that they need to be linked. If you use the one step the driver comes from a repository and the relationship is remember at the next kernel update.
The repository attempt failed for me, so I used the NVIDIA instructions, which were quite straight forward.

…]

In any case it is good to know how to do things from the command line.

Simple, straight forward, obvious cookbook style instructions are nice. That’s why I’m back here. What is “sax2”? Where does it live? Why can I not find it? I’ve looked in

/sbin
/bin
/usr/bin
/usr/sbin
/usr/X11

to no avail. Perhaps it is re-install time. :frowning:

9

What is “sax2”?

Where does it live? Why can I not find it? I’ve looked in …]

hoppers:~ # which SaX2
/usr/sbin/SaX2