[opensuse-factory] ALERT: Confirm this re 11.0 Beta3 current upgrades
Confirm this for yourself. In recent messages it has been indicated that there is a problem with the kernel which was upgraded in the past (?)few days when zypper goes to upgrade 11.0 Beta3. Not so as far as I am concerned. The problem lies somewhere else. And this is what I am asking you to be aware of and to confirm. A short while ago I re-installed 11.0 Beta3 after trying a suggestion to fix the non-boot problem of 11.0 Beta3 after the recent upgrades by doing, amongst things, "rm /.buildenv and calling mkinitrd". Other suggestions also failed, so I decided to re-install 11.0 Beta3 from the DVD, but after installing it I wasn't going to allow zypper or smart to upgrade the kernel to 2.6.25.4-2 which is claimed to be the the cause of all the problems. Well, it's not the kernel ...25.4-2. Something else in the Factory to upgrade 11.0 Beta3 is causing the big-time problem. If you install 11.0 Beta3 to test it then do not allow it to be upgraded by zypper. (Just for the record, the version I have installed - and before the latest upgrades it was working fine - is the 32-bit version and I was using KDE4 to see what it looked liked.) Ciao. -- Vulgar language is the linguistic crutch of inarticulate brain-dead. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, 2008-05-23 at 17:00 +1000, Basil Chupin wrote:
Confirm this for yourself.
(Just for the record, the version I have installed - and before the latest upgrades it was working fine - is the 32-bit version and I was using KDE4 to see what it looked liked.)
This is probably the acpi problem, requiring acpi=off to be enter as a
boot option in the grub screen.
-JP
--
JP Rosevear
JP Rosevear wrote:
On Fri, 2008-05-23 at 17:00 +1000, Basil Chupin wrote:
Confirm this for yourself.
(Just for the record, the version I have installed - and before the latest upgrades it was working fine - is the 32-bit version and I was using KDE4 to see what it looked liked.)
This is probably the acpi problem, requiring acpi=off to be enter as a boot option in the grub screen.
I don't know much about how things work and from this perspective I would say that it is not an "acpi=off" problem because I tried it last night and it didn't really 'fix' anything. So, I re-installed 11.0 Beta3 from the DVD with KDE4. (BTW, why has the ability to "Boot Installed System" been removed from the installation DVD? (I had to use the DVD for 10.3 to be able to boot an installed system.) Re-installing 11.0 Beta3 worked OK; and it worked OK after I used Yast2 Control Centre to upgrade ONLY the patches following the installation. The patches which were installed were: kde4-kdm kde4-kwin kdebase4-workspace libzypp satsolver-tools yast2-qt-pkg I rebooted the OS and everything kept working OK. A couple of hours ago I decided that I will allow Yast2 Control Centre's Online Upgrade to do the rest of the available PACKAGE upgrades -- had to use the Control Centre because the Updater in the taskbar doesn't work, is showing that all repositories are rubbish, and is therefore sitting there as a yellow triangle with a "!" through it -- **BUT** I did NOT allow the kernel and the kernel source to be upgraded to 2.6.25.4-2- I wanted the kernel to remain at the original x.25.3-2. Over an hour+ later the upgrades completed. I then decided to reboot to see what would happen. At this point a wheel fell off. Just one wheel. So I decided to post this message while I still could still use Thunderbird to post a message and the other 3 wheels were still on. What made me conclude that a wheel fell off? Well, when I went to reboot, the menu which comes up with the options to either close relog, close down, reboot or cancel is greyed out EXCEPT for the icons themselves which are in full colourful colour. This I have seen before which is why I decided to post this message before rebooting because seeing such a greyed out menu means that things are SNAFU. Remember, I have NOT upgraded the kernel to x.25.4-2. OK, now I will send this message off...... and I expect that I will be back online in a day or so based on past experience :'( . (But at least this time I did make a back of Thunderbird.) Ciao. -- Vulgar language is the linguistic crutch of inarticulate persons. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Basil Chupin wrote:
JP Rosevear wrote:
On Fri, 2008-05-23 at 17:00 +1000, Basil Chupin wrote:
Confirm this for yourself.
(Just for the record, the version I have installed - and before the latest upgrades it was working fine - is the 32-bit version and I was using KDE4 to see what it looked liked.)
This is probably the acpi problem, requiring acpi=off to be enter as a boot option in the grub screen.
I don't know much about how things work and from this perspective I would say that it is not an "acpi=off" problem because I tried it last night and it didn't really 'fix' anything.
So, I re-installed 11.0 Beta3 from the DVD with KDE4.
(BTW, why has the ability to "Boot Installed System" been removed from the installation DVD? (I had to use the DVD for 10.3 to be able to boot an installed system.)
Re-installing 11.0 Beta3 worked OK; and it worked OK after I used Yast2 Control Centre to upgrade ONLY the patches following the installation. The patches which were installed were:
kde4-kdm kde4-kwin kdebase4-workspace libzypp satsolver-tools yast2-qt-pkg
I rebooted the OS and everything kept working OK.
A couple of hours ago I decided that I will allow Yast2 Control Centre's Online Upgrade to do the rest of the available PACKAGE upgrades -- had to use the Control Centre because the Updater in the taskbar doesn't work, is showing that all repositories are rubbish, and is therefore sitting there as a yellow triangle with a "!" through it -- **BUT** I did NOT allow the kernel and the kernel source to be upgraded to 2.6.25.4-2- I wanted the kernel to remain at the original x.25.3-2.
Over an hour+ later the upgrades completed. I then decided to reboot to see what would happen.
At this point a wheel fell off. Just one wheel. So I decided to post this message while I still could still use Thunderbird to post a message and the other 3 wheels were still on.
What made me conclude that a wheel fell off?
Well, when I went to reboot, the menu which comes up with the options to either close relog, close down, reboot or cancel is greyed out EXCEPT for the icons themselves which are in full colourful colour. This I have seen before which is why I decided to post this message before rebooting because seeing such a greyed out menu means that things are SNAFU.
Remember, I have NOT upgraded the kernel to x.25.4-2.
OK, now I will send this message off...... and I expect that I will be back online in a day or so based on past experience :'( .
(But at least this time I did make a back of Thunderbird.)
Update on the previous msg (above). The upgrades (~890) have been done and the system booted OK. I have also rebooted a couple of times to confirm that the OS does reboot. HOWEVER, when rebooting the menu I mentioned above still has all the options greyed out except for the icons which are in their full technicolour mode; nevertheless, clicking on the icon of your choice does produce the correct result - restart icon produces a reboot of the system. BUT a new development - possibly not new but just something I didn't notice earlier - is that the clock (bottom RH, which is supposed to be set by the ntp daemon) is suddenly showing Tuesday 27 May 01:43 hours when it is in fact Sunday 25 May 19:43 hours. The clock has been showing the correct date/time all day. Also, just mentioned earlier (nothing's changed) the zypper updater in the taskbar is still showing that the repositories it has tried to access are illegal and could not be refreshed. In Yast2, the repositories are being refreshed correctly. (Looks like zypper is still the ultimate winner ever since it was pushed onto us! smart, BTW, is doing, and showing, all the right things -- hasn't faulted yet in 11.0 Beta3.) OK, now to take life into my hands and ugrade the kernel/source to 2.6.25.4-2. I hold my breath....... Cccciao. (BTW, see the above "Cccciao"? Another side effect of 11.0 and possibly KDE4: the multiple repetition of the first character on occasions at the beginning of a para.) -- Vulgar language is the linguistic crutch of inarticulate persons. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Basil Chupin
BUT a new development - possibly not new but just something I didn't notice earlier - is that the clock (bottom RH, which is supposed to be set by the ntp daemon) is suddenly showing Tuesday 27 May 01:43 hours when it is in fact Sunday 25 May 19:43 hours.
The clock has been showing the correct date/time all day.
you are not possibly at GMT-6?? then your clocks is displaying gmt rather than local time. Adjust ps: would really by nice if you could trim a little of your copious quotes. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Patrick Shanahan wrote:
* Basil Chupin
[05-25-08 06:04]: BUT a new development - possibly not new but just something I didn't notice earlier - is that the clock (bottom RH, which is supposed to be set by the ntp daemon) is suddenly showing Tuesday 27 May 01:43 hours when it is in fact Sunday 25 May 19:43 hours.
The clock has been showing the correct date/time all day.
you are not possibly at GMT-6?? then your clocks is displaying gmt rather than local time. Adjust
Ah, Patrick, your mind is as alert and incisive as usual. "Adjust" you say. Could I possible be at "GMT-6"? No, absolutely not. I am at GMT-10 -- I am in Canberra, the Capital of Australia. And I know that "my" clocks are showing the wrong date/time otherwise I would not mentioned this in the message above. I was stating that the clock was wrong for the very bleeding obvious reason which is that I re-installed 11.0 Beta3 and the clock (once again, and again, and again,...) comes up with the wrong time - until it is reset with ntpdate. The clock is perfect while I am running 10.3, perfect. But when I install 11.0 Beta3 the clock goes RS. Just to make it kinda interesting, I'll throw this in: I adjusted the clock during the installation process - at the point where one selects the time zone and where one is also asked if one wants to adjust the date/clock. (I didn't do the "ntpdate -u <serverID> this time 'round). Well, doing so seems to have no real effect because the clock is still wrong, as you saw above.
ps: would really by nice if you could trim a little of your copious quotes.
And this on top of your private message to me..... I'm flattered that you are keeping such a close eye on me and looking out that I don't do anything 'naughty' (wink, wink, nudge, nudge!) If you HAVE been paying attention to what is being/has been stated in this thread, you will see that I am keeping up the information to the reply from JP Rosevear on 24/05/08 at 0431hours to me in this thread and which he also crossposted to opensuse. If your MUTT, 1.5.13 (2006.08.11) which you are using on SUSE 10.1, with Linux 2.6.18.8-396-default (x86_64), cannot pick up on these nuances in addressing then I suggest that you "get hip", "get with it", and upgrade to the latest versions of the software, and OS, you are now using. BTW, your MUTT is showing that my reply should *also* go to opensuse but I have decided not to send it there as well. Aren't I gracious? Ciao. PS In case it causes you - and others - great distress, this message will have a time stamp of something like 1820 hours on Wed 28 May 2008 because this is what Beta3 has determined should be the time stamp even though it is now 1630 hours on Monday 26 May, Australian Eastern Daylight Time (ie, GMT-10). 11.0 Beta3, I luvsya! :-* .) -- Vulgar language is the linguistic crutch of inarticulate persons. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-05-28 at 18:22 +1000, Basil Chupin wrote:
And I know that "my" clocks are showing the wrong date/time otherwise I would not mentioned this in the message above. I was stating that the clock was wrong for the very bleeding obvious reason which is that I re-installed 11.0 Beta3 and the clock (once again, and again, and again,...) comes up with the wrong time - until it is reset with ntpdate.
The clock is perfect while I am running 10.3, perfect. But when I install 11.0 Beta3 the clock goes RS.
Check whether you have "/etc/init.d/boot.getclock" and/or "/etc/init.d/boot.clock", and whether any/both/none of those scripts are set to run at boot (chkconfig). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIOoL2tTMYHG2NR9URAoRQAKCC4zrzZqLuBjeIRB6cNqJr3mpjHgCfedt5 KVCzlGfCy+CbOozSnVzX6eQ= =XY2M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Basil Chupin
Ah, Patrick, your mind is as alert and incisive as usual.
As is your usual sarcasm
ps: would really by nice if you could trim a little of your copious quotes.
And this on top of your private message to me..... I'm flattered that you are keeping such a close eye on me and looking out that I don't do anything 'naughty' (wink, wink, nudge, nudge!)
again with the sarcasm and public posting/quoting of private email
If you HAVE been paying attention to what is being/has been stated in this thread, you will see that I am keeping up the information to the reply from JP Rosevear on 24/05/08 at 0431hours to me in this thread and which he also crossposted to opensuse.
If your MUTT, 1.5.13 (2006.08.11) which you are using on SUSE 10.1, with Linux 2.6.18.8-396-default (x86_64), cannot pick up on these nuances in addressing then I suggest that you "get hip", "get with it", and upgrade to the latest versions of the software, and OS, you are now using.
and you deride *my* choice of mail client and linux version
BTW, your MUTT is showing that my reply should *also* go to opensuse but I have decided not to send it there as well. Aren't I gracious?
to a fault, many faults. Please continue to exist blissfully in your own squalor. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Basil Chupin
-
Carlos E. R.
-
JP Rosevear
-
Patrick Shanahan