[opensuse] 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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
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.
I'm trying to get a bug which seems to come from the factory repo fixed. It causes zypper to do strange things (look at bug https://bugzilla.novell.com/show_bug.cgi?id=393531 ) and I have referenced two other bugs there. The worst thing about this bug, is that it can leave your system in a mess and it only happens at certain times. Maybe this is what is happening. The bug was there for a day and once again it disappeared. Read the bug it's interesting reading. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+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 <jpr@novell.com> Novell, Inc. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, May 23, 2008 at 11:31 AM, JP Rosevear <jpr@novell.com> 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.
-JP -- JP Rosevear <jpr@novell.com> Novell, Inc.
But why would that all of a sudden be needed on machines which ran fine with acpi in 10.3? And Why would the initial install be fine, but subsequent upgrades by zypper cause acpi to suddenly fail? And how is turning off acpi ever a good Idea when most modern hardware (especially laptops) absolutely rely on acpi to provide access to all hardware? -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Basil Chupin -
Dave Plater -
John Andersen -
JP Rosevear