On Sun, 2006-06-25 at 18:03 -0600, Tom Patton wrote:
Unless you told YOU to delete rpms after install, you will have a copy in /var/lib/YaST2/you/mnt/i386/update/9.3/rpm/i586/kernel-default-2.6.11.4-21.11.i586.rpm
I considered doing that, but thought they were "patch" rpm's. I have them back to x21.7, actually. Looking at the size of them, perhaps you are correct, and they are complete.
Just install it manually, using rpm --oldpackage or --force perhaps. Notice that it is several files: -default, -default-nongpl, kernel-sources (or -smp or whatever).
Cool, I think I'll try that. Thanks, Carlos.
- -- Tom
Carlos, Anders...et al... Thanks, Carlos, for suggesting that I look again at the rpm's in the update directory. I did "rpm -U --oldpackage ....x21.11..." and it restored my x21.11 fine. I then tried to downgrade the "non-gpl", but was told it was already installed as well. It rebuilt the initrd and symmaps as well. And now for the good news...my "X" is back in service. And there is no Oops in dmesg. So the questions remain "what went wrong with the YOU to x21.12?", why did X work ok in my sloppy 2.6.16.18 kernel and now back into the 2.6.11.4-21.11 kernel...? Not to mention, why did two pc's at work update to x21.12 without a hitch? I guess since I know how to recover now, perhaps I should attempt another YOU session, once I remove the 21.12 rpm's from the .../you/... folder. If it was a bad session (dial-up), I'd think yast would have alerted me... I love a good mystery, don't you? Tom -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com