Announcement

Collapse
No announcement yet.

Boot problems since generic-X-36 maj.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Boot problems since generic-X-36 maj.

    the maj work at his release date and during one month. But i don't know why since last minor update: Boot start on failsafe mode, and tell me to run journalctl. - "Failed to Parse boot descriptor '+'"

    - Force starting generic x-36 kernel loop to fail safe boot.
    - Force loading generic x-35 kernel work with file system checks at startup.
    - Trying to run boot-repair, purge and reinstalling grub change nothing.
    - Purge kernel and reisntall it : no change.

    #2
    story:
    - loosing window boot capacity 4 months ago
    - loosing kubuntu boot with -36 kernel

    what i have done to stabilize the boot at working kernel:
    there was a dual boot with windows11.
    - default select -35 kernel to boot.
    - trying to reinstall kernel ...
    - Clear and destroying windows partitions i do not use from a couple of month now. no need to keep a spyware system on my UC.
    - Removing old kernel manually ( dpkg -l / apt remove ) ( there was -21 to -31 remains , i also removing -36)
    - Removing Grub/grub.cfg bad remain configs into it
    - Removing /boot/efi/efi/windows and old not used EFIs persitent data.

    but:
    The system is still booting in a 2 minutes long times. that is not normal,
    there are those efi entries:

    BootOrder: 0003,0001
    Boot0001* neon VenHw(xxxxxxxxx-xxxx-xxxx-xxxx-c5385e6c00cb)
    Boot0003* Ubuntu HD(1,GPT,xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,0x800,0 xee000)/File(\EFI\UBUNTU\SHIMX64.EFI)



    hmm, neon haven't valid start entry, can't activate it. can i i'll clear it from bootmgr ?

    DSMEG
    [ 0.036828] kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-6.8.0-35-generic root=UUID=xxxxxxxxxxxxxxxxxxxxxxxxxx ro quiet splash vt.handoff=7
    [ 0.036883] kernel: Unknown kernel command line parameters "splash BOOT_IMAGE=/vmlinuz-6.8.0-35-generic", will be passed to user space.


    old kernel to ram, becoming no compatible ?
    Last edited by MegsOconnor; Jun 28, 2024, 04:21 AM.

    Comment

    Working...
    X