Results 1 to 7 of 7

Thread: edit grub entries after update

  1. #1

    Default edit grub entries after update

    Hello,

    done and the upgrade to 13.1, there is a detail in the grub and put entries in the previous version 12.3 instead of the new.

    He was thinking hand-edit the grub.cfg and change to the new version but I worry about breaking the boot. How I can edit?

    Thank you.

    Attached is a picture of yast grub configuration, if it would not here to change the version number to update the entries.

    grub

  2. #2

    Default Re: edit grub entries after update

    Just change the "Distributor" string (the very first one) there in that YaST window to "openSUSE 13.1" (or whatever you want actually).

    The menu will then be automatically recreated with the changed string.

    And no, you should not edit grub.cfg by hand. Your changes will be lost if an update rewrites the boot loader.

  3. #3

    Default Re: edit grub entries after update

    I have the same problem, but the problem is not only the label, is that the system is booting with the old 3.7 kernel instead of the new 3.11.
    The Default boot section continues being Advanced options for openSUSE 12.3>openSUSE 12.3, with Linux 3.7.10-1.16-default

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: edit grub entries after update

    On 2014-01-04 23:26, jony127 wrote:

    > 'grub' (http://www.subirimagenes.com/imagen-grub-8761546.html)


    Next time, please use susepaste.org. The site you used is very intrusive
    with their commercial popups.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  5. #5
    Join Date
    Jun 2009
    Location
    Florida, USA
    Posts
    236

    Default Re: edit grub entries after update

    Quote Originally Posted by fperal View Post
    I have the same problem, but the problem is not only the label, is that the system is booting with the old 3.7 kernel instead of the new 3.11.
    The Default boot section continues being Advanced options for openSUSE 12.3>openSUSE 12.3, with Linux 3.7.10-1.16-default
    Look into /var/log/zypp/history - I found an error had occurred during the kernel installation (out of space in / during mkinitrd) which bypassed the grub update. Fixing that and reinstalling the 13.1 kernel made it all better.
    Use the Source, Luke

  6. #6

    Default Re: edit grub entries after update

    Quote Originally Posted by fperal View Post
    I have the same problem, but the problem is not only the label, is that the system is booting with the old 3.7 kernel instead of the new 3.11.
    The Default boot section continues being Advanced options for openSUSE 12.3>openSUSE 12.3, with Linux 3.7.10-1.16-default
    Run YaST->System->Boot Loader->Boot Loader Options and change the default.

    If that doesn't help, try to delete the file /boot/grub2/grubenv.

  7. #7

    Default Re: edit grub entries after update

    Quote Originally Posted by GeoBaltz View Post
    Look into /var/log/zypp/history - I found an error had occurred during the kernel installation (out of space in / during mkinitrd) which bypassed the grub update. Fixing that and reinstalling the 13.1 kernel made it all better.
    It was a similar problem

    Here it is:
    Code:
    # 2014-01-07 13:44:27 kernel-desktop-devel-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # Changing symlink /usr/src/linux-obj/x86_64/desktop from ../../linux-3.7.10-1.24-obj/x86_64/desktop to ../../linux-3.11.6-4-obj/x86_64/desktop
    # 
    2014-01-07 13:44:27|install|kernel-desktop-devel|3.11.6-4.1|x86_64||repo-oss|decc5240472845ab2ea69065055cae8a946885d51a05a9e6d166580005415750|
    # 2014-01-07 13:44:43 kernel-desktop-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # 
    # Kernel image:   /boot/vmlinuz-3.11.6-4-desktop
    # Initrd image:   /boot/initrd-3.11.6-4-desktop
    # plymouth: symbol lookup error: plymouth: undefined symbol: ply_logger_is_tracing_enabled
    # plymouth: symbol lookup error: plymouth: undefined symbol: ply_logger_is_tracing_enabled
    # grep: /usr/share/plymouth/themes//.plymouth: No such file or directory
    # The default plymouth plugin () doesn't exist.
    # There was an error generating the initrd (1)
    # 
    2014-01-07 13:44:43|install|kernel-desktop|3.11.6-4.1|x86_64||repo-oss|8f71100805fe51071a5656b8e0b6894baf3396ad38999e9ed3e1b0b985871b77|
    # 2014-01-07 13:44:45 kernel-default-devel-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # Changing symlink /usr/src/linux-obj/x86_64/default from ../../linux-3.7.10-1.24-obj/x86_64/default to ../../linux-3.11.6-4-obj/x86_64/default
    # 
    2014-01-07 13:44:45|install|kernel-default-devel|3.11.6-4.1|x86_64||repo-oss|504e31a8cb594e78bcaf1db51f7edf017f7f3db68b0392caa828ff880dfc38d6|
    # 2014-01-07 13:44:55 kernel-default-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # 
    # Kernel image:   /boot/vmlinuz-3.11.6-4-default
    # Initrd image:   /boot/initrd-3.11.6-4-default
    # plymouth: symbol lookup error: plymouth: undefined symbol: ply_logger_is_tracing_enabled
    # plymouth: symbol lookup error: plymouth: undefined symbol: ply_logger_is_tracing_enabled
    # grep: /usr/share/plymouth/themes//.plymouth: No such file or directory
    # The default plymouth plugin () doesn't exist.
    # There was an error generating the initrd (1)
    Then I reinstalled all about plymouth, then I reinstalled kernel (both desktop and default) and kernel source just in case and..
    Code:
    2014-01-07 21:25:57|install|kernel-source|3.11.6-4.1|noarch|root@andromeda|repo-oss|e6dc877aabc6959e649d3443d9a3ebbef8d2aa80b27bc5ad961b3997b8fab133|
    # 2014-01-07 21:26:40 kernel-default-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # Free diskspace below /boot: 158627304 blocks
    # 
    # Kernel image:   /boot/vmlinuz-3.11.6-4-default
    # Initrd image:   /boot/initrd-3.11.6-4-default
    # Root device:  /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part6 (/dev/sda6) (mounted on / as ext4)
    # Resume device:        /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part1 (/dev/sda1)
    # Microcode: Adding AMD microcode microcode_amd.bin
    # Kernel Modules:       thermal_sys thermal processor fan pata_atiixp ata_generic scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj hid-generic hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ehci-pci ohci-pci libcrc32c xor zlib_deflate raid6_pq btrfs crc32c-intel 
    # Features:       acpi amd_microcode plymouth block usb btrfs resume.userspace resume.kernel
    # 
    2014-01-07 21:26:40|install|kernel-default|3.11.6-4.1|x86_64|root@andromeda|repo-oss|1af6fbb8c5bf34ebad3e94bf624fe5ba83ac075bcb8056e7eda6ee94324dc1fb|
    # 2014-01-07 21:27:25 kernel-desktop-3.11.6-4.1.x86_64.rpm installed ok
    # Additional rpm output:
    # Free diskspace below /boot: 158709048 blocks
    # 
    # Kernel image:   /boot/vmlinuz-3.11.6-4-desktop
    # Initrd image:   /boot/initrd-3.11.6-4-desktop
    # Root device:  /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part6 (/dev/sda6) (mounted on / as ext4)
    # Resume device:        /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part1 (/dev/sda1)
    # Microcode: Adding AMD microcode microcode_amd.bin
    # Kernel Modules:       thermal_sys thermal processor fan pata_atiixp ata_generic scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua xhci-hcd hid-logitech-dj hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ohci-pci libcrc32c xor zlib_deflate raid6_pq btrfs crc32c-intel 
    # Features:       acpi amd_microcode plymouth block usb btrfs resume.userspace resume.kernel
    # 
    2014-01-07 21:27:25|install|kernel-desktop|3.11.6-4.1|x86_64|root@andromeda|repo-oss|8f71100805fe51071a5656b8e0b6894baf3396ad38999e9ed3e1b0b985871b77|

    All fine. Just one more thing. I had to reinstall nvidia drivers because X wasn't using all my screen


    regards

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •