[opensuse] 13.2 Upgrade issue
Hello, I have just upgraded my 13.1 to 13.2 by "zypper dup" following the instructions. Rebooting stops to very early stage of grub. I then used an older DVD of openSUSE to boot my system and login into 13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk. Wonder how I can recover this issue. Beside this I can use only XFCE, Gnome both Classic and Standard are not working at all. Thanks, -- Marco Calistri opensuse 13.1 (Bottle) 64 bit - Kernel 3.16.2-1.gdcee397-default Gnome 3.12.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marco Calistri [06.11.2014 13:37]:
Hello,
I have just upgraded my 13.1 to 13.2 by "zypper dup" following the instructions.
Rebooting stops to very early stage of grub.
I did not do a "zypper dup", instead, I used the graphical frontend in YaST2. I think it's easier to work out problematic packages here.
I then used an older DVD of openSUSE to boot my system and login into 13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk.
Wonder how I can recover this issue.
In my case, I had to change the GRUB_DISTRIBUTOR line in file /etc/default/grub to get 13.2 instead of 13.1 in the boot menu.
Beside this I can use only XFCE, Gnome both Classic and Standard are not working at all.
I would be happy if my Gnome did not run ;), so I am not supposed to have any tips here :) I'd suggest to check that all packages that belong together are from the same repository. I have some special repos active, like obs:filesystems, and there often were errors when a package (like e2fsprogs) was from the distro and the required libraries were from the OBS. Just my 2¢ Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 06/11/2014 11:24, Werner Flamme ha scritto:
Marco Calistri [06.11.2014 13:37]:
Hello,
I have just upgraded my 13.1 to 13.2 by "zypper dup" following the instructions.
Rebooting stops to very early stage of grub.
I did not do a "zypper dup", instead, I used the graphical frontend in YaST2. I think it's easier to work out problematic packages here.
I then used an older DVD of openSUSE to boot my system and login into 13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk.
Wonder how I can recover this issue.
In my case, I had to change the GRUB_DISTRIBUTOR line in file /etc/default/grub to get 13.2 instead of 13.1 in the boot menu.
Beside this I can use only XFCE, Gnome both Classic and Standard are not working at all.
I would be happy if my Gnome did not run ;), so I am not supposed to have any tips here :)
I'd suggest to check that all packages that belong together are from the same repository. I have some special repos active, like obs:filesystems, and there often were errors when a package (like e2fsprogs) was from the distro and the required libraries were from the OBS.
Just my 2¢ Werner
Hello Werner, I sorted out the grub2 issue by following a SDB guide. I'm up and running with Harlequin now! -- Marco Calistri Accidents cause History. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marco Calistri <marco.calistri <at> yahoo.com.br> writes:
Il 06/11/2014 11:24, Werner Flamme ha scritto:
Marco Calistri [06.11.2014 13:37]:
Hello,
I have just upgraded my 13.1 to 13.2 by "zypper dup" following the instructions.
Rebooting stops to very early stage of grub.
I did not do a "zypper dup", instead, I used the graphical frontend in YaST2. I think it's easier to work out problematic packages here.
I then used an older DVD of openSUSE to boot my system and login into 13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk.
Wonder how I can recover this issue.
In my case, I had to change the GRUB_DISTRIBUTOR line in file /etc/default/grub to get 13.2 instead of 13.1 in the boot menu.
Beside this I can use only XFCE, Gnome both Classic and Standard are not working at all.
I would be happy if my Gnome did not run ;), so I am not supposed to have any tips here :)
I'd suggest to check that all packages that belong together are from the same repository. I have some special repos active, like obs:filesystems, and there often were errors when a package (like e2fsprogs) was from the distro and the required libraries were from the OBS.
Just my 2¢ Werner
Hello Werner,
I sorted out the grub2 issue by following a SDB guide.
I'm up and running with Harlequin now!
Hello Marco, I also have upgraded from 13.1 to 13.2, but from the YAST GUI and after the upgrade was finished was asked to reboot. When rebooting, the 13.2 release of GRUB was loaded with the new graphics, but the menu was just like yours showing 13.1 instead of 13.2. The main issue however, is that after after it starts loading, I immediately get a kernel panic and reboot after 90 seconds, because it can not find swap, root, etc. I am hoping the solution you found will work for me. Could you please post the link to the SDB guide you used? Thanks in advance! Gergely -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-06 21:16, Pócsi Gergely wrote:
Marco Calistri <> writes:
When rebooting, the 13.2 release of GRUB was loaded with the new graphics, but the menu was just like yours showing 13.1 instead of 13.2.
This is intentional and no error. You can change whatever that menu title says to your liking, upgrades will not change it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-11-06 14:24, Werner Flamme wrote:
Marco Calistri [06.11.2014 13:37]:
13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk.
Wonder how I can recover this issue.
In my case, I had to change the GRUB_DISTRIBUTOR line in file /etc/default/grub to get 13.2 instead of 13.1 in the boot menu.
This is an intentional feature. It is the administrator who writes this string, not the distribution. The idea is that once written, it is not changed across the years. I believe that a fresh install of 13.2 uses just "openSUSE" with no version number at all. This does not affect the other issues. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/06/2014 09:50 AM, Carlos E. R. wrote:
On 2014-11-06 14:24, Werner Flamme wrote:
Marco Calistri [06.11.2014 13:37]:
13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk.
Wonder how I can recover this issue.
In my case, I had to change the GRUB_DISTRIBUTOR line in file /etc/default/grub to get 13.2 instead of 13.1 in the boot menu.
This is an intentional feature. It is the administrator who writes this string, not the distribution. The idea is that once written, it is not changed across the years.
I believe that a fresh install of 13.2 uses just "openSUSE" with no version number at all.
This does not affect the other issues.
Speaking of Grub2, On a fresh install I get this
jsa@poulsbo:/boot/grub2> l total 20 drwxr-xr-x 1 root root 168 Nov 4 16:44 ./ drwxr-xr-x 1 root root 698 Nov 5 18:39 ../ drwxr-xr-x 1 root root 0 Oct 25 09:31 backgrounds/ -rw------- 1 root root 15 Nov 4 16:43 device.map -rw-r--r-- 1 root root 15 Nov 4 15:48 device.map.old drwxr-xr-x 1 root root 22 Nov 4 16:44 fonts/ -rw------- 1 root root 6961 Nov 4 16:44 grub.cfg -rw-r--r-- 1 root root 1024 Nov 4 16:44 grubenv drwxr-xr-x 1 root root 6010 Nov 4 16:44 i386-pc/ drwxr-xr-x 1 root root 290 Nov 4 16:44 locale/ drwxr-xr-x 1 root root 16 Nov 4 16:44 themes/ drwxr-xr-x 1 root root 0 Nov 4 15:44 x86_64-efi/
So the question is, How long has grub been installing an i386-pc directory? (Don't remember seeing that. (its been a while since I did a fresh install). - -- Explain again the part about rm -rf / -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRbx1cACgkQv7M3G5+2DLJD4ACfcX3/cgAXH7WD44OmVsQD89RJ sooAnAkJPBzh/lZhRMf5rCr+p4i3YZUZ =WeNl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2014 02:37 PM, Marco Calistri wrote:
I then used an older DVD of openSUSE to boot my system and login into 13.2 ...................
- please, kindly explain details : how you achieved this ? thanks ellan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2014 12:30 PM, ellanios82 wrote:
On 11/06/2014 02:37 PM, Marco Calistri wrote:
I then used an older DVD of openSUSE to boot my system and login into 13.2 ...................
- please, kindly explain details : how you achieved this ?
That could be one of two things. The DVD has a 'boot from hard disk' option that seems to get around problems I've had with the BIOS ---> Grub functioning. The other is that you can boot in maintenance mode, mount the hard drive, Chroot to the mount and log in there. I've used this to repair (including fsck on ROOT) the /boot, grub and files in /etc on the hard drive quite a number of times using a variety of file systems under a variety of versions of Suse and Linux. It has nothing what so ever to do with systed vs sysvinit, with BrtFs vs ext4, or with IDE vs SATA. It is one area where the meaningful nameing of devices (/dev/disk/by-*) has provem more useful than the anonymous and unhelpful /dev/sd*. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2014 08:16 PM, Anton Aylward wrote:
On 11/06/2014 02:37 PM, Marco Calistri wrote:
I then used an older DVD of openSUSE to boot my system and login into 13.2 ...................
- please, kindly explain details : how you achieved this ? That could be one of two things. The DVD has a 'boot from hard disk' option that seems to get around
On 11/06/2014 12:30 PM, ellanios82 wrote: problems I've had with the BIOS ---> Grub functioning.
The other is that you can boot in maintenance mode, mount the hard drive, Chroot to the mount and log in there. I've used this to repair (including fsck on ROOT) the /boot, grub and files in /etc on the hard drive quite a number of times using a variety of file systems under a variety of versions of Suse and Linux. .............
- many thanks regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 06/11/2014 15:30, ellanios82 ha scritto:
On 11/06/2014 02:37 PM, Marco Calistri wrote:
I then used an older DVD of openSUSE to boot my system and login into 13.2 ...................
- please, kindly explain details : how you achieved this ?
thanks ellan
I used the 13.1 RC2 DVD to boot my machine and desfrute newer kernel, then followed this guide following the 13.1 paragraph: https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install Regards, -- Marco Calistri (amdturion) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/07/2014 04:32 PM, Marco Calistri wrote:
I used the 13.1 RC2 DVD to boot my machine and desfrute newer kernel, then followed this guide following the 13.1 paragraph:
https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install
............ thank you regards ellan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Carlos E. R. -
ellanios82 -
John Andersen -
Marco Calistri -
Pócsi Gergely -
Werner Flamme