I have but ONE persistent problem in Mint.

Discussion in 'General Linux Discussion' started by Daniel~, May 19, 2021.

Page 1 of 2
  1. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    I'm sure nothing is broken as In some releases it goes away.
    I have a 5.1 sound system that works in Roku, works in PS 4.

    Only plays stereo in Mint. I use a HDMI connection
    Even worse I can't use "Suspend or restart" I must completely shut down and restart my box to get any sound at all.

    Recently I had to replace my Power supply, didn't help.
    I have gone over and gone over all Mint and BIOS settings, could not find a solution.

    So I come to you, my more knowledgeable friends, hat in hand to ask for your advice.

    I also have one new and extremely unhappy making problem.
    In BIOS I set my system to pause at the boot screen until I hit escape.

    The first time I did it I hit Esc then immediately hit Del and entered my BIOS. But Now it doesn't seem to get the del message in time and I go straight past BIOS.to my desktop

    Thus effectively locking me out of my BIOS!!! AHAAA!!!
    All suggestions welcome!!!

    Do I really need to pull my battery hiding behind my Video card to get back in???

    Don't forget your here to help me!! LOL
    Daniel~, May 19, 2021
    #1
    booman likes this.
  2. booman

    booman Grand High Exalted Mystic Emperor of Linux Gaming Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    8,339
    Likes Received:
    624
    Trophy Points:
    113
    Location:
    Linux, Virginia
    Home page:
    Hmm I can't remember a single computer pausing at the boot screen. Some BIOS have a logo setting that gives you more time to enter the BIOS, but I've never seen one paus there waiting for input.

    Are you sure you don't mean the GRUB boot screen?

    For example, I used to dual-boot Mint and Windows, so a boot screen would appear and allow me to select Windows or Mint. It has a countdown, but there is a way edit the GRUB config file so it will pause there indefinitely.

    Normally if I want to get into the BIOS after a quick boot screen, I'll just keep tapping the key on the keyboard to access it.
    Like on Dell its F12
    Others its Del or Enter
    booman, May 19, 2021
    #2
  3. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    Hi Boo, thanks for showing up! ":O)
    No this was a BIOS boot option, set how long you think you need to look at the boot screen. 1-10 seconds or wait until I hit esc.
    after a dozen tries I hit the timing just right and got back into my bios. I reset to 10 sec. and that was that.
    Yep I was tapping to, but I got in by holding it down....then waiting 5 minutes for it to actually let me in.

    I have no real idea as to what is going on. But it can take 15 minutes to reach the desktop, where is runs fast and true.
    then the next boot all is fine and I get there in about two minutes. it will boot a dozen times normally then pull a 30 min. boot.

    When ever i use suspend or hibernate, I lose all sound until I reboot.
    Daniel~, May 21, 2021
    #3
  4. booman

    booman Grand High Exalted Mystic Emperor of Linux Gaming Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    8,339
    Likes Received:
    624
    Trophy Points:
    113
    Location:
    Linux, Virginia
    Home page:
    Interesting. Are you updating Mint when they are available?
    Sometimes those types of issues are Kernel related. So make sure to update!

    I'll have to check my BIOS/UEFI and see there there is a time setting.

    One thing you can do at boot is press TAB when you see the Mint icon.
    Then you will see everything that is happening while its booting. If its stuck on something, then you might know what the problem is.

    Please post whatever you find here and we'll help you
    booman, May 21, 2021
    #4
  5. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    LOL Even when my sys update icon says I'm up to date
    I check anyway, half the time I get something.":O

    For the third morning in a row after battling all day and going to sleep to a sys running almost as I would like, I woke my system to dead silence!!

    I was in and out of my BIOS from 830 to 1130.

    I gave up and came hear to cry on your shoulder.
    Then only after rebooting at lest a dozen time it hit me.

    I checked my stand alone reciver, the remote had gotten bumped and it was set to the wrong input. Hit the right input and MUSIC was everywhere around me! LOL
    But I stumbled upon several things in the preocess.
    1 For the first time one of my setttings gave me a UFI boot!
    Up til now when I tried to boot to UFI, she sacreen would blink and that was it, I think I know what to do.

    You have a UFI BIOS?

    Do you boot to it UFI> if so tell me your setting, mean while I'll check and see if I can get the UFI boot back.
    ":O}

    BTW I turned off Intel fast boot and got a faster boot! LOL
    Daniel~, May 21, 2021
    #5
  6. booman

    booman Grand High Exalted Mystic Emperor of Linux Gaming Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    8,339
    Likes Received:
    624
    Trophy Points:
    113
    Location:
    Linux, Virginia
    Home page:
    Nice! Wrong input would give you hard time!

    Yes, I always boot into UEFI
    Legacy BIOS doesn't have all the features Linux will need.

    Yes to disabling Fast Boot... that is for Windows only... funny that your system boots faster with "fast boot" off..
    booman, May 21, 2021
    #6
  7. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    I'm dwelingl in the land of uncertainty
    went through my settings and got a UFI boot.
    How some ever if I choose UFI only and pick UFI in the boot menu
    Clonezillia, my back up app on dvd comes up.

    If I choose UFI first I can now boot from the UFI drive, but my non UFI hard drive backs up, is in second place in the boot order so I don't know If I'm getting UFI or the sys to giving uo on it and booting BIOS?
    Just realized how to test this, Ill take my hard drive out of the boot order and see what happens":O)

    Back in a bit.":O}
    Daniel~, May 21, 2021
    #7
  8. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    can you please give me your UFI settings?
    Daniel~, May 21, 2021
    #8
  9. booman

    booman Grand High Exalted Mystic Emperor of Linux Gaming Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    8,339
    Likes Received:
    624
    Trophy Points:
    113
    Location:
    Linux, Virginia
    Home page:
    I'm not at home, so I can't access my UEFI settings

    There is a UEFI boot feature in the boot options.
    So that is why its probably booting to Clonezilla.

    I bet if you unplug the backup drive, it will boot to UEFI
    booman, May 21, 2021
    #9
  10. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    It's the same drive. I ask it to boot UFI when it can't or just won't to be mean it boots the drive as BIOS.

    Take your time Boo, I'm not hurting at the moment and can play by myself.

    When I set the UFI to UFI ONLY as opposed to UFI first then legacy BiOS,
    the drive list changes.
    before I would see my boot drive and a UFI OS drive.

    A DVD player drive AND a UFI dvd player drive.
    At UFI only setting I see only a UFI OS and a UFI DVD.

    The DVD will boot at that setting but so far not my drive.
    I'm thinking there's something I'm just plane missing.
    Daniel~, May 22, 2021
    #10
  11. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    Ok I got a pure UFI only boot and all looks fine.
    I took the disk out of the DVD player so it couldn't boot it.

    Thing ids though is that the UFI OS is now my only choice..
    No backup drive, no Music driove and no DVD drive.

    Right now I'm thinking UFI is a selfish little prick.":O}

    Going to go play some more...like see what happens If I put the clonzillia disk back in the DVD ":O)
    Daniel~, May 22, 2021
    #11
  12. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    I'm done for tonight. I get a good pure UFI boot once next time it screws the pooch. I'll wait till your work and family can spare you.

    Thank them for me for being so generous with your time
    Daniel~, May 22, 2021
    #12
  13. Daerandin

    Daerandin Well-Known Member

    Joined:
    Oct 18, 2013
    Messages:
    1,157
    Likes Received:
    258
    Trophy Points:
    83
    Location:
    Northern Norway
    Home page:
    Just a little explanation on UEFI vs Legacy boot. You can't boot in UEFI mode unless you actually installed Mint while having UEFI enabled. UEFI requires an EFI partition with the bootloader. Of course, maybe Mint actually sets it up even when booted in Legacy mode.

    But AFTER booting, there is absolutely no difference at all. UEFI or Legacy only affects the actual boot process, nothing else. Hardware support, functionality, and so on, is exactly the same after you have booted.

    Warning, technical details upcoming:

    Also, Legacy booting boots directly from your drive, this works because Legacy bootloaders are actually written to your hard drive in the space before the first partition. This limits what can be included in the bootloader. So no fancy high resolution splash screens. UEFI mode however supports high resolution boot splash screens.

    UEFI requires an EFI partition, either formatted as FAT32 or VFAT, and on this partition there must be an EFI executable. This is normally your bootloader, or it could also just be the kernel itself (the Linux kernel is EFI executable). The path to the EFI executable must be stored in the UEFi NVRAM on your motherboard for it to be able to boot from it. Some newer motherboards are also able to find EFI executables and present a list of them. But in many cases, they will just list the EFI partitions that are found, where an executable can be found in the default path.

    Technical details are over

    In short, the two boot modes are not compatible and you can't switch between them unless the system has been set up with both modes. UEFI boot in particular requires writing to your motherboard firmware, in order for it to know what to boot. When you boot a Linux install media in UEFI mode, a specific directory on your system will be created:

    /sys/firmware/efi/efivars

    And that's how Linux knows you have booted in UEFI mode, and when you then install your Linux distro, it will specifically install for UEFI. Otherwise, it will install in Legacy mode.

    So unless you want to install Mint all over, leave your boot mode on what it was. Changing it will not solve any problems.

    EDIT: It could be that your BIOS will try the other boot mode if it can't find a bootable medium in the selected mode.
    Daerandin, May 22, 2021
    #13
  14. Daerandin

    Daerandin Well-Known Member

    Joined:
    Oct 18, 2013
    Messages:
    1,157
    Likes Received:
    258
    Trophy Points:
    83
    Location:
    Northern Norway
    Home page:
    As for the slow boot times, it would be better to see where in the boot process it's actually being slow.

    So on your next slow boot, open a terminal and type in the following:

    Code:
    systemd-analyze
    Then copy the output from your terminal and post it here. I would also like to see the output from:

    Code:
    systemd-analyze critical-chain
    Once again, just copy it and paste it here.

    Lastly, still on a slow boot, run this command:

    Code:
    sudo journalctl --no-pager -b > ~/slowboot.txt
    This last command will create a file in your home directory, named "slowboot.txt". This text file will include the entire system journal for the current boot. Then just attach the file to your next boot. I am no expert in sifting through the syslog, but IF the slow boot is happening during the booting of Mint, then hopefully we can see something in the journal.
    Daerandin, May 22, 2021
    #14
  15. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    How generous you are with you time and knowledge!
    Many thanks.

    !. first question that pops up is Can one set bios to UFI then restore from a Non UFI Back up?
    2. On my next slow boot up...unsure as hell as to how to open a terminal in mid boot? Or would one wait until one reaches desktop?

    3 this boot was but moderately slow, not one of my 30 minutes to reach desktop. I think that problem got fix along the way, Please please don't ask me how it got fix.LOL

    Moving right along....

    Screenshot from 2021-05-23 14-34-38.png
    daniel@daniel-System-Product-Name:~$ systemd-analyze critical-chain
    The time when unit became active or started is printed after the "@" character.
    The time the unit took to start is printed after the "+" character.

    graphical.target @2.682s
    └─multi-user.target @2.681s
    └─getty.target @2.681s
    └─getty@tty1.service @2.681s
    └─system-getty.slice @2.680s
    └─setvtrgb.service @2.676s +3ms
    └─systemd-user-sessions.service @2.512s +6ms
    └─network.target @2.510s
    └─networking.service @2.359s +150ms
    └─apparmor.service @2.251s +73ms
    └─local-fs.target @2.251s
    └─boot-efi.mount @2.243s +7ms
    └─systemd-fsck@dev-disk-by\x2duuid-478E\x2d1B2E.service @>
    └─dev-disk-by\x2duuid-478E\x2d1B2E.device @664ms
    lines 1-17/17 (END)

    from desktop terminal:

    l@daniel-System-Product-Name:~$ systemd-analyze
    Startup finished in 5.444s (kernel) + 2.691s (userspace) = 8.136s
    graphical.target reached after 2.682s in userspace
    daniel@daniel-System-Product-Name:~$
    Daniel~, May 23, 2021
    #15
  16. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    Sorry about the order of my responses, it's never easy with me.":O}

    Our new slow boot file. It seems to have a lot tp sday, to much for oe post
    Ill have to break it up.
    -- Logs begin at Thu 2021-05-06 00:11:41 PDT, end at Sun 2021-05-23 14:44:39 PDT. --
    May 23 14:10:44 daniel-System-Product-Name kernel: microcode: microcode updated early to revision 0x2f, date = 2019-02-17
    May 23 14:10:44 daniel-System-Product-Name kernel: Linux version 5.4.0-73-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 (Ubuntu 5.4.0-73.82-generic 5.4.106)
    May 23 14:10:44 daniel-System-Product-Name kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=bb41457f-2e33-4a1c-be44-6b054164bace ro quiet splash
    May 23 14:10:44 daniel-System-Product-Name kernel: KERNEL supported cpus:
    May 23 14:10:44 daniel-System-Product-Name kernel: Intel GenuineIntel
    May 23 14:10:44 daniel-System-Product-Name kernel: AMD AuthenticAMD
    May 23 14:10:44 daniel-System-Product-Name kernel: Hygon HygonGenuine
    May 23 14:10:44 daniel-System-Product-Name kernel: Centaur CentaurHauls
    May 23 14:10:44 daniel-System-Product-Name kernel: zhaoxin Shanghai
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-provided physical RAM map:
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd188fff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000dd189000-0x00000000dd807fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000dd808000-0x00000000dd818fff] ACPI data
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000dd819000-0x00000000dd940fff] ACPI NVS
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000dd941000-0x00000000de7d0fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000de7d1000-0x00000000de7d1fff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000de7d2000-0x00000000de814fff] ACPI NVS
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000de815000-0x00000000dec4afff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000dec4b000-0x00000000deff3fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000deff4000-0x00000000deffffff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: BIOS-e820: [mem 0x0000000100000000-0x000000041effffff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: NX (Execute Disable) protection: active
    May 23 14:10:44 daniel-System-Product-Name kernel: SMBIOS 2.7 present.
    May 23 14:10:44 daniel-System-Product-Name kernel: DMI: System manufacturer System Product Name/SABERTOOTH Z77, BIOS 2104 08/13/2013
    May 23 14:10:44 daniel-System-Product-Name kernel: tsc: Fast TSC calibration using PIT
    May 23 14:10:44 daniel-System-Product-Name kernel: tsc: Detected 3411.127 MHz processor
    May 23 14:10:44 daniel-System-Product-Name kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 23 14:10:44 daniel-System-Product-Name kernel: last_pfn = 0x41f000 max_arch_pfn = 0x400000000
    May 23 14:10:44 daniel-System-Product-Name kernel: MTRR default type: uncachable
    May 23 14:10:44 daniel-System-Product-Name kernel: MTRR fixed ranges enabled:
    May 23 14:10:44 daniel-System-Product-Name kernel: 00000-9FFFF write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: A0000-BFFFF uncachable
    May 23 14:10:44 daniel-System-Product-Name kernel: C0000-CFFFF write-protect
    May 23 14:10:44 daniel-System-Product-Name kernel: D0000-E7FFF uncachable
    May 23 14:10:44 daniel-System-Product-Name kernel: E8000-FFFFF write-protect
    May 23 14:10:44 daniel-System-Product-Name kernel: MTRR variable ranges enabled:
    May 23 14:10:44 daniel-System-Product-Name kernel: 0 base 000000000 mask C00000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 1 base 400000000 mask FF0000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 2 base 410000000 mask FF8000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 3 base 418000000 mask FFC000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 4 base 41C000000 mask FFE000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 5 base 41E000000 mask FFF000000 write-back
    May 23 14:10:44 daniel-System-Product-Name kernel: 6 base 0E0000000 mask FE0000000 uncachable
    May 23 14:10:44 daniel-System-Product-Name kernel: 7 disabled
    May 23 14:10:44 daniel-System-Product-Name kernel: 8 disabled
    May 23 14:10:44 daniel-System-Product-Name kernel: 9 disabled
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
    May 23 14:10:44 daniel-System-Product-Name kernel: total RAM covered: 16368M
    May 23 14:10:44 daniel-System-Product-Name kernel: Found optimal setting for mtrr clean up
    May 23 14:10:44 daniel-System-Product-Name kernel: gran_size: 64K chunk_size: 32M num_reg: 7 lose cover RAM: 0G
    May 23 14:10:44 daniel-System-Product-Name kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
    May 23 14:10:44 daniel-System-Product-Name kernel: found SMP MP-table at [mem 0x000fd7d0-0x000fd7df]
    May 23 14:10:44 daniel-System-Product-Name kernel: check: Scanning 1 areas for low memory corruption
    May 23 14:10:44 daniel-System-Product-Name kernel: RAMDISK: [mem 0x2da61000-0x32d27fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Early table checksum verification disabled
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: XSDT 0x00000000DD80B078 00006C (v01 ALASKA A M I 01072009 AMI 00010013)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: FACP 0x00000000DD815E28 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: DSDT 0x00000000DD80B180 00ACA5 (v02 ALASKA A M I 00000022 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: FACS 0x00000000DD93F080 000040
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: APIC 0x00000000DD815F38 000092 (v03 ALASKA A M I 01072009 AMI 00010013)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: FPDT 0x00000000DD815FD0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: MCFG 0x00000000DD816018 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0x00000000DD816058 0007CA (v01 Intel_ AoacTabl 00001000 INTL 20091112)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: HPET 0x00000000DD816828 000038 (v01 ALASKA A M I 01072009 AMI. 00000005)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0x00000000DD816860 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0x00000000DD8175D8 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0x00000000DD816C28 0009AA (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Local APIC address 0xfee00000
    May 23 14:10:44 daniel-System-Product-Name kernel: No NUMA configuration found
    May 23 14:10:44 daniel-System-Product-Name kernel: Faking a node at [mem 0x0000000000000000-0x000000041effffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: NODE_DATA(0) allocated [mem 0x41efc8000-0x41eff2fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: Zone ranges:
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: Normal [mem 0x0000000100000000-0x000000041effffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: Device empty
    May 23 14:10:44 daniel-System-Product-Name kernel: Movable zone start for each node
    May 23 14:10:44 daniel-System-Product-Name kernel: Early memory node ranges
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x0000000000001000-0x000000000009cfff]
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x0000000000100000-0x00000000dd188fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x00000000de7d1000-0x00000000de7d1fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x00000000de815000-0x00000000dec4afff]
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x00000000deff4000-0x00000000deffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: node 0: [mem 0x0000000100000000-0x000000041effffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: Zeroed struct page in unavailable ranges: 15000 pages
    May 23 14:10:44 daniel-System-Product-Name kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000041effffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: On node 0 totalpages: 4179304
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA zone: 64 pages used for memmap
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA zone: 21 pages reserved
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA zone: 3996 pages, LIFO batch:0
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA32 zone: 14104 pages used for memmap
    May 23 14:10:44 daniel-System-Product-Name kernel: DMA32 zone: 902604 pages, LIFO batch:63
    May 23 14:10:44 daniel-System-Product-Name kernel: Normal zone: 51136 pages used for memmap
    May 23 14:10:44 daniel-System-Product-Name kernel: Normal zone: 3272704 pages, LIFO batch:63
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: PM-Timer IO Port: 0x408
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Local APIC address 0xfee00000
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    May 23 14:10:44 daniel-System-Product-Name kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: IRQ0 used by override.
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: IRQ9 used by override.
    May 23 14:10:44 daniel-System-Product-Name kernel: Using ACPI (MADT) for SMP configuration information
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    May 23 14:10:44 daniel-System-Product-Name kernel: TSC deadline timer available
    May 23 14:10:44 daniel-System-Product-Name kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdd189000-0xdd807fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdd808000-0xdd818fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdd819000-0xdd940fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdd941000-0xde7d0fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xde7d2000-0xde814fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdec4b000-0xdeff3fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xdf000000-0xf7ffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    May 23 14:10:44 daniel-System-Product-Name kernel: [mem 0xdf000000-0xf7ffffff] available for PCI devices
    May 23 14:10:44 daniel-System-Product-Name kernel: Booting paravirtualized kernel on bare hardware
    May 23 14:10:44 daniel-System-Product-Name kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
    May 23 14:10:44 daniel-System-Product-Name kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
    May 23 14:10:44 daniel-System-Product-Name kernel: percpu: Embedded 55 pages/cpu s188416 r8192 d28672 u262144
    May 23 14:10:44 daniel-System-Product-Name kernel: pcpu-alloc: s188416 r8192 d28672 u262144 alloc=1*2097152
    May 23 14:10:44 daniel-System-Product-Name kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 23 14:10:44 daniel-System-Product-Name kernel: Built 1 zonelists, mobility grouping on. Total pages: 4113979
    May 23 14:10:44 daniel-System-Product-Name kernel: Policy zone: Normal
    May 23 14:10:44 daniel-System-Product-Name kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=bb41457f-2e33-4a1c-be44-6b054164bace ro quiet splash
    May 23 14:10:44 daniel-System-Product-Name kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
    May 23 14:10:44 daniel-System-Product-Name kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
    May 23 14:10:44 daniel-System-Product-Name kernel: mem auto-init: stack:eek:ff, heap alloc:eek:n, heap free:eek:ff
    May 23 14:10:44 daniel-System-Product-Name kernel: Calgary: detecting Calgary via BIOS EBDA area
    May 23 14:10:44 daniel-System-Product-Name kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    May 23 14:10:44 daniel-System-Product-Name kernel: Memory: 16244868K/16717216K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2732K init, 4972K bss, 472348K reserved, 0K cma-reserved)
    May 23 14:10:44 daniel-System-Product-Name kernel: random: get_random_u64 called from kmem_cache_open+0x2d/0x410 with crng_init=0
    May 23 14:10:44 daniel-System-Product-Name kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 23 14:10:44 daniel-System-Product-Name kernel: Kernel/User page tables isolation: enabled
    May 23 14:10:44 daniel-System-Product-Name kernel: ftrace: allocating 44586 entries in 175 pages
    May 23 14:10:44 daniel-System-Product-Name kernel: rcu: Hierarchical RCU implementation.
    May 23 14:10:44 daniel-System-Product-Name kernel: rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
    May 23 14:10:44 daniel-System-Product-Name kernel: Tasks RCU enabled.
    May 23 14:10:44 daniel-System-Product-Name kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
    May 23 14:10:44 daniel-System-Product-Name kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 23 14:10:44 daniel-System-Product-Name kernel: NR_IRQS: 524544, nr_irqs: 488, preallocated irqs: 16
    May 23 14:10:44 daniel-System-Product-Name kernel: Console: colour dummy device 80x25
    May 23 14:10:44 daniel-System-Product-Name kernel: printk: console [tty0] enabled
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Core revision 20190816
    May 23 14:10:44 daniel-System-Product-Name kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
    May 23 14:10:44 daniel-System-Product-Name kernel: APIC: Switch to symmetric I/O mode setup
    May 23 14:10:44 daniel-System-Product-Name kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 23 14:10:44 daniel-System-Product-Name kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x312b5e33c4e, max_idle_ns: 440795327319 ns
    May 23 14:10:44 daniel-System-Product-Name kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6822.25 BogoMIPS (lpj=13644508)
    May 23 14:10:44 daniel-System-Product-Name kernel: pid_max: default: 32768 minimum: 301
    May 23 14:10:44 daniel-System-Product-Name kernel: LSM: Security Framework initializing
    May 23 14:10:44 daniel-System-Product-Name kernel: Yama: becoming mindful.
    May 23 14:10:44 daniel-System-Product-Name kernel: AppArmor: AppArmor initialized
    May 23 14:10:44 daniel-System-Product-Name kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
    May 23 14:10:44 daniel-System-Product-Name kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
    May 23 14:10:44 daniel-System-Product-Name kernel: *** VALIDATE tmpfs ***
    May 23 14:10:44 daniel-System-Product-Name kernel: *** VALIDATE proc ***
    May 23 14:10:44 daniel-System-Product-Name kernel: *** VALIDATE cgroup1 ***
    May 23 14:10:44 daniel-System-Product-Name kernel: *** VALIDATE cgroup2 ***
    May 23 14:10:44 daniel-System-Product-Name kernel: mce: CPU0: Thermal monitoring enabled (TM1)
    May 23 14:10:44 daniel-System-Product-Name kernel: process: using mwait in idle threads
    May 23 14:10:44 daniel-System-Product-Name kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    May 23 14:10:44 daniel-System-Product-Name kernel: Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V2 : Mitigation: Full generic retpoline
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
    May 23 14:10:44 daniel-System-Product-Name kernel: Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl
    May 23 14:10:44 daniel-System-Product-Name kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
    May 23 14:10:44 daniel-System-Product-Name kernel: MDS: Mitigation: Clear CPU buffers
    May 23 14:10:44 daniel-System-Product-Name kernel: Freeing SMP alternatives memory: 40K
    May 23 14:10:44 daniel-System-Product-Name kernel: smpboot: CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (family: 0x6, model: 0x2a, stepping: 0x7)
    May 23 14:10:44 daniel-System-Product-Name kernel: Performance Events: PEBS fmt1+, SandyBridge events, 16-deep LBR, full-width counters, Intel PMU driver.
    May 23 14:10:44 daniel-System-Product-Name kernel: ... version: 3
    May 23 14:10:44 daniel-System-Product-Name kernel: ... bit width: 48
    May 23 14:10:44 daniel-System-Product-Name kernel: ... generic registers: 4
    May 23 14:10:44 daniel-System-Product-Name kernel: ... value mask: 0000ffffffffffff
    May 23 14:10:44 daniel-System-Product-Name kernel: ... max period: 00007fffffffffff
    May 23 14:10:44 daniel-System-Product-Name kernel: ... fixed-purpose events: 3
    May 23 14:10:44 daniel-System-Product-Name kernel: ... event mask: 000000070000000f
    May 23 14:10:44 daniel-System-Product-Name kernel: rcu: Hierarchical SRCU implementation.
    May 23 14:10:44 daniel-System-Product-Name kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
    May 23 14:10:44 daniel-System-Product-Name kernel: smp: Bringing up secondary CPUs ...
    May 23 14:10:44 daniel-System-Product-Name kernel: x86: Booting SMP configuration:
    May 23 14:10:44 daniel-System-Product-Name kernel: .... node #0, CPUs: #1 #2 #3 #4
    May 23 14:10:44 daniel-System-Product-Name kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
    May 23 14:10:44 daniel-System-Product-Name kernel: #5 #6 #7
    May 23 14:10:44 daniel-System-Product-Name kernel: smp: Brought up 1 node, 8 CPUs
    May 23 14:10:44 daniel-System-Product-Name kernel: smpboot: Max logical packages: 1
    May 23 14:10:44 daniel-System-Product-Name kernel: smpboot: Total of 8 processors activated (54578.03 BogoMIPS)
    May 23 14:10:44 daniel-System-Product-Name kernel: devtmpfs: initialized
    May 23 14:10:44 daniel-System-Product-Name kernel: x86/mm: Memory block size: 128MB
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registering ACPI NVS region [mem 0xdd819000-0xdd940fff] (1212416 bytes)
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: Registering ACPI NVS region [mem 0xde7d2000-0xde814fff] (274432 bytes)
    May 23 14:10:44 daniel-System-Product-Name kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
    May 23 14:10:44 daniel-System-Product-Name kernel: futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
    May 23 14:10:44 daniel-System-Product-Name kernel: pinctrl core: initialized pinctrl subsystem
    May 23 14:10:44 daniel-System-Product-Name kernel: PM: RTC time: 21:10:38, date: 2021-05-23
    May 23 14:10:44 daniel-System-Product-Name kernel: NET: Registered protocol family 16
    May 23 14:10:44 daniel-System-Product-Name kernel: audit: initializing netlink subsys (disabled)
    May 23 14:10:44 daniel-System-Product-Name kernel: audit: type=2000 audit(1621804238.044:1): state=initialized audit_enabled=0 res=1
    May 23 14:10:44 daniel-System-Product-Name kernel: EISA bus registered
    May 23 14:10:44 daniel-System-Product-Name kernel: cpuidle: using governor ladder
    May 23 14:10:44 daniel-System-Product-Name kernel: cpuidle: using governor menu
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: bus type PCI registered
    May 23 14:10:44 daniel-System-Product-Name kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 23 14:10:44 daniel-System-Product-Name kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    May 23 14:10:44 daniel-System-Product-Name kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    May 23 14:10:44 daniel-System-Product-Name kernel: PCI: Using configuration type 1 for base access
    May 23 14:10:44 daniel-System-Product-Name kernel: core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
    May 23 14:10:44 daniel-System-Product-Name kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    May 23 14:10:44 daniel-System-Product-Name kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Module Device)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Processor Device)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Linux-Dell-Video)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: 5 ACPI AML tables successfully acquired and loaded
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Dynamic OEM Table Load:
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0xFFFF8F658C559000 00083B (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Dynamic OEM Table Load:
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0xFFFF8F658C0DB000 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: Dynamic OEM Table Load:
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: SSDT 0xFFFF8F658C105200 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: EC: EC started
    May 23 14:10:44 daniel-System-Product-Name kernel: ACPI: EC: interrupt blocked
    Daniel~, May 23, 2021
    #16
  17. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    I posted a TINY fraction of the out put as we are limited to 40,000 charters.

    If you need it all, that's how I'll spend my afternoon LOL
    Last edited: May 23, 2021
    Daniel~, May 23, 2021
    #17
  18. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    11,352
    Likes Received:
    169
    Trophy Points:
    63
    Location:
    Greenwater WA
    Home page:
    After reading your excellent explanation the question arises,
    Why would I want to boot UFI?

    What if any advantage is there for mint users in going UFI?
    Daniel~, May 23, 2021
    #18
  19. Daerandin

    Daerandin Well-Known Member

    Joined:
    Oct 18, 2013
    Messages:
    1,157
    Likes Received:
    258
    Trophy Points:
    83
    Location:
    Northern Norway
    Home page:
    As far as I know, the only practical advantages with UEFI is that you can have partitions larger than 2TB. Also Secure Boot, although the actual security advantages there are open for discussion. Besides, actually using Secure Boot on Linux takes some work so it's not really a point for most users. As far as I know, there is no change in hardware compatibility or functionality.

    Also, don't forget the 'E' in UEFI. Sorry for picking on details, I'm just an obsessive perfectionist. (Should I make this a part of my signature?)

    Now for your earlier questions:

    [quote="Daniel~, member: 57]!. first question that pops up is Can one set bios to UFI then restore from a Non UFI Back up?[/quote]

    I actually don't know. It depends on your Backup/Restore solution. The only difference that I can think of would be in your /boot directory, because GRUB has a BIOS/Legacy version, and a different UEFI version. Might also be some slight differences in configuration files related to booting in your /etc directory.

    I would not risk using restore from any kind of backup software between boot methods. But let me state my earlier point, you can't switch boot modes without reinstalling, or spending a lot of time reconfiguring. Making changes in the BIOS will not change the installed boot method in your OS.

    But for all your personal files, programs and so on, it makes no difference.

    [quote="Daniel~, member: 57]2. On my next slow boot up...unsure as hell as to how to open a terminal in mid boot? Or would one wait until one reaches desktop?[/quote]

    You just wait until you reach the desktop. You can even use for computer for hours, or even days, before doing this stuff. As long as you are still on the same boot.

    [quote="Daniel~, member: 57]I posted a TINY fraction of the out put as we are limited to 40,000 charters.

    If you need it all, that's how I'll spend my afternoon LOL[/quote]

    Please don't copy the log into a forum post. If you ran the command as I said, then you will have a file in your home directory called slowboot.txt. Just find the "Upload a File" button when you are posting your reply here. Click on that, and you can upload the text file that contains the log. It's much easier for me as well when I can just download the file, open it in VIM and much more easily scan through it.
    Daerandin, May 26, 2021
    #19
  20. Daerandin

    Daerandin Well-Known Member

    Joined:
    Oct 18, 2013
    Messages:
    1,157
    Likes Received:
    258
    Trophy Points:
    83
    Location:
    Northern Norway
    Home page:
    But the slow boot times is something that appears to be happening in your Firmware, and not related to your OS. The two commands you ran show us that Mint only took 8 seconds to boot, so the slowness seems to happen before Linux takes over the boot process.

    That might be related to settings in your BIOS, and I might not be the best help there. But please upload the journal file still, there is a chance it contains something useful.
    Daerandin, May 26, 2021
    #20
Page 1 of 2

Share This Page