Ran the latest upgrade (2.6.34-7 to 2.6.34-12) this evening (3rd Dec.) on two systems. And it has all gone pear-shaped! Reports of modules missing, 30 sec time-outs, screen res. wrong, no USB.
Dropped back to 2.6.34-7 but the Yast package manager is now all over the place.
On 2010-12-03 20:06, martinprowe wrote:
>
> Ran the latest upgrade (2.6.34-7 to 2.6.34-12) this evening (3rd Dec.)
> on two systems. And it has all gone pear-shaped! Reports of modules
> missing, 30 sec time-outs, screen res. wrong, no USB.
>
> Dropped back to 2.6.34-7 but the Yast package manager is now all over
> the place.
>
> Help…
Please rephrase. What is the problem?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Sorry to panic! I was initially “raising a flag” to see if the problem was widespread. But I guess that it is particular to my situation. Now that I’ve calmed down, I’ll attempt to answer your questions:
1. “What’s the problem?” Starting from the top. If you would have a look at this screen-shot 2.6.34-12Boot.JPG (a real one because the boot logging has not yet started). The first six “FATAL” did not display prior to this upgrade. Also the missing preloadtrace.ko is present in the previous kernel structure. These more, but if we can resolve one of these problems, I’m hopping that they will all go away?
Hi Tony et al,
Yes, so would I. After spending a day trying to understand what was happening, I un-installed (with crossed fingers) “kernel default base 2.6.34-12.3”.
Phew… Back to the old familiar environment. Then checked again if any upgrades were needed. None?
I guess I’ll never know what happened (on two systems)? I don’t know how upgrades are vetted or released, but I wonder if a package was inadvertently made available and then rescinded?
Anyway, I’m happy again. Thank you all.
Regards, Martin
PS Carlos, we all need help from time to time
> I guess I’ll never know what happened (on two systems)? I don’t know
> how upgrades are vetted or released, but I wonder if a package was
> inadvertently made available and then rescinded?
There are logs.
Your configuration of repos is not the default nor typical.
> Anyway, I’m happy again. Thank you all.
>
> Regards, Martin
> PS Carlos, we all need help from time to time
That was intended as a joke
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
martinprowe wrote:
> Hmmmm… That’s interesting. Where can I find these logs?
generally in /var/logs
the logs showing what you installed will be in /var/log/zypper.log (or
the archived logs, depending on how old the action is and how you have
set up logrotate) or maybe if you don’t find what are looking for
there you might peek into /var/log/YaST2/y2logRPM…
> Hmmmm… That’s interesting. Where can I find these logs?
Almost all logs are in /var/log/*, have a look there and see what you can
find of interest. You have to look for zypper logs, or yast. There is one
in particular, history, with the history of installed packages. Another one
logs the decisions of the installer, but that one is difficult to interpret.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Once again thanks for the pointers, but don’t waste your time.
What these (client side) logs will tell me is WHAT happened.
The key to understanding is the WHY it happened.
In my case, I know that kupdate said that there was an update, and I clicked on “Do It”.