Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: 20.04 Save working configuration and make it default configuration for next boot

  1. #11
    Join Date
    Apr 2020
    Beans
    11

    Re: 20.04 Save working configuration and make it default configuration for next boot

    Dear Oldfred,

    Apologies for not having noticed your reply. I couldn't see an option in the forum settings to create an email alert.

    Quote Originally Posted by oldfred View Post
    If you have floppy drive enabled in BIOS, but no floppy drive, then BIOS writes that you have floppy drive, operating system tries to load it and has to time out on failure.
    But the grub entry includes --no-floppy. Doesn't that fix it?

    Quote Originally Posted by oldfred View Post
    I found boot to be a bit faster with this boot parameter: noplymouth
    Will replace quiet splash with noplymouth.

    Quote Originally Posted by oldfred View Post
    Check all the UUIDs in fstab, if slow boot.
    Will do. Need some more guidance at the moment. I accidentally deleted the partition table, happened because I ran gparted, chose an unformatted partition in the hard disk, and tried to create a new partition table, mistaking that a partition table can be created within a partition. Within a moment understood that it is a process for the entire disk, but the table was gone already. I switch off the computer in an attempt to save further damage, now need to find a way to safely restore the partition table.

    Thank you.

  2. #12
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: 20.04 Save working configuration and make it default configuration for next boot

    If you had not shutdown system, partition table is still in RAM and possibly can be restored.
    Have you run Boot-Repair? It has text info on exact start & size of every partition which can be used to restore partitions.
    Otherwise testdisk or parted rescue may be able to restore partitions.

    Used parted rescue
    https://ubuntuforums.org/showthread.php?t=2362656
    http://ubuntuforums.org/showthread.php?t=2315405
    backup partition table before any changes, so you can get back to current if changes not correct
    sudo sfdisk -d /dev/sda > PT_sda.txt
    So you know sectors:
    sudo parted /dev/sda unit s print

    https://help.ubuntu.com/community/DataRecovery
    http://www.cgsecurity.org/wiki/TestDisk
    repairs including testdisk info & links
    https://help.ubuntu.com/community/Da...Lost_Partition
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  3. #13
    Join Date
    Apr 2020
    Beans
    11

    Re: 20.04 Save working configuration and make it default configuration for next boot

    Dear Oldfred,

    Still haven't learnt to visit the forum regularly to check for updates. I am late by 3 weeks to reply to your helpful solution. Before applying the boot repair / parted solution to the disk ( I will get to it this week ), I installed a new hard disk, began by installing 16.04, first with an attempt at hard disk encryption, update to 18.04 showed lvm errors, did not proceed smoothly, deleted the crypt partition, re-formatted the entire hard disk, proceeded to reinstall 16.04 without encryption, update to 18.04 was smooth, and as a solution to the display issue, followed a post and installed xfce4 which resolved almost all of the hardware issues that I posted in this and other threads, same old hardware, same samsung 2030 monitor, same nvidia graphics. Then proceeded to update to 19.10, then to 20.4 all by update-manager. With xfce4 there was no need to attempt any fix, such as install an old nvidia driver, or to blacklist noveau, or even a nomodeset, there were no plymouth errors, Top, with no application running showed less than 5% CPU usage, display works at 1600x900 on its own, no boot issues. Then I purged unity (might be unnecessary, but ubuntu's login screen was pixelated before I strugggled a bit with the invisible cursor to type my password for a clean xfce environment), installed xubuntu desktop, purged mate, (mate loaded with a corrupt display).

    20.04 with XFCE4, XUBUNTU desktop work splendidly with the same 10 year old hardware with limited resources, without any fixes.

    Saying this,

    (1) in a manner of withdrawing the few posts, that might have given a few readers the impression that 20.04 has some issues. The issues probably had to do with the path of trying upgrades from the unsupported 10.04 installation, by a complex path of installing drivers, enabling third party repositories, and trying any fix found in the forum such as grub edit, blacklist...

    2) This might be helpful to some who reported display issues, plymouth issues on 20.04, the solution could be found in choosing a desktop such as xubuntu or LXDE.

    3) In trying to find bug fixes for plymouth or or for some versions of nvidia, the developers may find it useful to focus on the reasons why some display manager work and others don't.

    Thank you.
    Last edited by s1van; June 13th, 2020 at 10:48 PM. Reason: typographical errors corrected.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

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