Mint install on Samsung NP905S3G fails to boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Mint install on Samsung NP905S3G fails to boot

Post by w23 »

I'm not completely new to linux, but have used Windows 10 now for a long time. My last Linux systems were Gentoo-Linux on older bios systems.

I need help to install mint 19.3 on a newer Windows laptop that lacks a Windows system, but fails to boot after installation of mint cinnamon from magazin-dvd, "linuxmint-19.3-cinnamon-64bit.iso".
Therefore the Windows related partitions on the SSD were already purged from the SSD, before I purchased this laptop.

Basically, I'm searching for a HOWTO to install mint on this laptop, best in UEFI mode, but if it has to be legacy mode, it'll have to do too.
But as this is a uefi-Laptop, I'd prefer Uefi setup, if possible.

I've searched the web, found many interesting links, but all of which were not successful.

One main thing I couldn't find was howto install mint in UEFI mode from DVD boot media.
I don't know what boot options I have to place on kernel command line or elsewhere to get mint to install itself in UEFI mode to SSD.
Do I need a special DVD version of mint that explicitly supports UEFI?

I can't remember which other command I used to find out that my installation of mint is in legacy mode.

I've deactivated fast boot, secure boot and password on boot in the Bios.
I've switched OS Mode selection to CSM and UEFI OS and AHCI Mode control to Auto in the Bios.
Boot option Priorities don't list any OS or drive until I connect a DVD drive via USB with a bootable linux live system on it.

I've used the install option "other" to get to see what gparted does and to assign
sda1 to efi
sda2 to / (root)
sda3 to linuxdata
sda4 to swap

I intend to use Hybernate and suspend functions later, so if swap partition is essential for that, I'll have one, else I could also do with a swap file and use the 5gb for some other system, e.g. tails.

What I don't understand is what files have to reside in the EFI partition?

Here is the output of inxi -Fxxxrz

Code: Select all

System:
  Host: mint Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 
  Desktop: Cinnamon 4.4.5 wm: muffin 4.4.1 dm: LightDM 1.26.0 
  Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: SAMSUNG product: 905S3G/906S3G/915S3G/9305SG 
  v: P13RBV serial: <filter> Chassis: type: 9 serial: N/A 
  Mobo: SAMSUNG model: NP905S3G-K02DE v: SAMSUNG_SW_REVISION_1234567890ABCD 
  serial: <filter> BIOS: American Megatrends v: P13RBV.083.140805.FL 
  date: 08/05/2014 
Battery:
  ID-1: BAT1 charge: 29.1 Wh condition: 30.0/30.6 Wh (98%) volts: 8.4/7.5 
  model: SAMSUNG Electronics SR Real Battery type: Li-ion serial: <filter> 
  status: Unknown cycles: 564 
CPU:
  Topology: Quad Core model: (up to ) bits: 64 type: MCP arch: Jaguar rev: 1 
  L1 cache: 256 KiB L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 7985 
  Speed: 599 MHz min/max: 600/1000 MHz boost: enabled Core speeds (MHz): 
  1: 599 2: 598 3: 598 4: 599 
Graphics:
  Device-1: AMD Temash [Radeon HD 8250/8280G] vendor: Samsung Co 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:983d 
  Display: server: X.Org 1.20.4 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD KABINI (DRM 2.50.0 5.0.0-32-generic LLVM 8.0.0) 
  v: 4.5 Mesa 19.0.8 direct render: Yes 
Audio:
  Device-1: AMD Kabini HDMI/DP Audio vendor: Samsung Co 
  driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:9840 
  Device-2: AMD FCH Azalia vendor: Samsung Co driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1022:780d 
  Sound Server: ALSA v: k5.0.0-32-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Samsung Co driver: r8169 v: kernel port: e000 bus ID: 01:00.0 
  chip ID: 10ec:8168 
  IF: enp1s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
  vendor: Samsung Co driver: ath9k v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 168c:0036 
  IF: wlp2s0 state: down mac: <filter> 
  Device-3: Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb 
  bus ID: 4-2:3 chip ID: 0cf3:3004 
Drives:
  Local Storage: total: 119.24 GiB used: 10.16 GiB (8.5%) 
  ID-1: /dev/sda vendor: Samsung model: MZMTD128HAFV-000 size: 119.24 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 1K0Q scheme: GPT 
Partition:
  ID-1: / size: 1.65 GiB used: 29.8 MiB (1.8%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 56.1 C mobo: N/A gpu: radeon temp: 55 C 
  Fan Speeds (RPM): N/A 
Repos:
  Active apt repos in: /etc/apt/sources.list 
  1: deb cdrom:[Linux Mint 19.3 _Tricia_ - Release amd64 20191213]/ bionic contrib main non-free
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com tricia main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ bionic partner
Info:
  Processes: 196 Uptime: 19m Memory: 3.30 GiB used: 683.6 MiB (20.2%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.4.0 alt: 7 
  Shell: bash (sudo) v: 4.4.20 running in: gnome-terminal inxi: 3.0.32 
Here is the output of fdisk -l /dev/sda

Code: Select all

Disk /dev/sda: 119,2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FEA72D57-8996-432F-B6E3-8DAB8FD715BE

Device         Start       End   Sectors  Size Type
/dev/sda1       2048   2191359   2189312    1G EFI System
/dev/sda2    2191360 121649151 119457792   57G Linux filesystem
/dev/sda3  132036608 250068991 118032384 56,3G Linux filesystem
/dev/sda4  121649152 132036607  10387456    5G Microsoft basic data

Partition table entries are not in disk order.
root@mint:/# 
Meanwhile, I have changed sda4 to a linux swap partition, as there is no need for a M$-Partition when no M$ OS is no longer installed.

This may also be helpful:

Code: Select all

mint@mint:~$ sudo efibootmgr
EFI variables are not supported on this system.
mint@mint:~$ 
This is a partial output of dmesg, because I got an error saying my message was too long.
I will post the complete dmesg code in a second post as soon as I may do so due to spam policies in this forum, if it seems neccessary to do so:

Code: Select all

[    0.000000] Linux version 5.0.0-32-generic (buildd@lgw01-amd64-015) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 (Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21)
[    0.000000] Command line: BOOT_IMAGE=(loop)/casper/vmlinuz file=/cdrom/preseed/linuxmint.seed boot=casper quiet splash iso-scan/filename=/Image-Dateien/linuxmint-19.3-cinnamon-64bit.iso debian-installer/language=de console-setup/layoutcode?=de --
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000009d5abfff] usable
[    0.000000] BIOS-e820: [mem 0x000000009d5ac000-0x000000009d5dbfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000009d5dc000-0x000000009d5f2fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000009d5f3000-0x000000009dbeafff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000009dbeb000-0x000000009e747fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000009e748000-0x000000009e748fff] usable
[    0.000000] BIOS-e820: [mem 0x000000009e749000-0x000000009e750fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000009e751000-0x000000009e8a4fff] usable
[    0.000000] BIOS-e820: [mem 0x000000009e8a5000-0x000000009eccdfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000009ecce000-0x000000009ed10fff] usable
[    0.000000] BIOS-e820: [mem 0x000000009ed11000-0x000000009eff1fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000009eff2000-0x000000009effffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec01fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100001000-0x000000013effffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.7 present.
[    0.000000] DMI: SAMSUNG ELECTRONICS CO., LTD. 905S3G/906S3G/915S3G/9305SG/NP905S3G-K02DE, BIOS P13RBV.083.140805.FL 08/05/2014
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 998.129 MHz processor
[    0.005009] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.005014] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.005037] last_pfn = 0x13f000 max_arch_pfn = 0x400000000
[    0.005046] MTRR default type: uncachable
[    0.005049] MTRR fixed ranges enabled:
[    0.005052]   00000-9FFFF write-back
[    0.005055]   A0000-BFFFF write-through
[    0.005057]   C0000-CEFFF write-protect
[    0.005060]   CF000-E7FFF uncachable
[    0.005062]   E8000-EFFFF write-protect
[    0.005065]   F0000-FFFFF write-through
[    0.005067] MTRR variable ranges enabled:
[    0.005071]   0 base 0000000000 mask FF80000000 write-back
[    0.005075]   1 base 0080000000 mask FFE0000000 write-back
[    0.005076]   2 -7 disabled
...
    0.005088] TOM2: 000000013f000000 aka 5104M
[    0.005895] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.006069] e820: update [mem 0xa0000000-0xffffffff] usable ==> reserved
[    0.006082] last_pfn = 0x9f000 max_arch_pfn = 0x400000000
[    0.016529] found SMP MP-table at [mem 0x000fd730-0x000fd73f]
[    0.031071] check: Scanning 1 areas for low memory corruption
[    0.031083] Using GB pages for direct mapping
...
[    0.032347] RAMDISK: [mem 0x33477000-0x35a32fff]
[    0.032362] ACPI: Early table checksum verification disabled
[    0.035912] ACPI: RSDP 0x00000000000F0490 000024 (v02 SECCSD)
[    0.035920] ACPI: XSDT 0x000000009D5E4080 000084 (v01 SECCSD LH43STAR 01072009 AMI  00010013)
[    0.035935] ACPI: FACP 0x000000009D5EA8F8 00010C (v05 SECCSD LH43STAR 01072009 AMI  00010013)
[    0.035948] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20181213/tbfadt-624)
[    0.035959] ACPI: DSDT 0x000000009D5E4198 00675F (v02 SECCSD LH43STAR 00000000 INTL 20051117)
[    0.035969] ACPI: FACS 0x000000009DBE1080 000040
[    0.035976] ACPI: APIC 0x000000009D5EAA08 00007E (v03 SECCSD LH43STAR 01072009 AMI  00010013)
[    0.035984] ACPI: FPDT 0x000000009D5EAA88 000044 (v01 SECCSD LH43STAR 01072009 AMI  00010013)
[    0.035992] ACPI: MCFG 0x000000009D5EAAD0 00003C (v01 SECCSD LH43STAR 01072009 MSFT 00010013)
[    0.036000] ACPI: MSDM 0x000000009D5EAB10 000055 (v03 SECCSD LH43STAR 01072009 AMI  00010013)
[    0.036008] ACPI: HPET 0x000000009D5EAB68 000038 (v01 SECCSD LH43STAR 01072009 AMI  00000005)
[    0.036016] ACPI: SSDT 0x000000009D5EABA0 000B10 (v01 AMD    AGESA    00000001 AMD  00000001)
[    0.036024] ACPI: SSDT 0x000000009D5EB6B0 0046D1 (v02 AMD    AGESA    00000002 MSFT 04000000)
[    0.036032] ACPI: CRAT 0x000000009D5EFD88 000380 (v01 AMD    AGESA    00000001 AMD  00000001)
[    0.036040] ACPI: SSDT 0x000000009D5F0108 0013CA (v01 AMD    CPMDFIGP 00000001 INTL 20051117)
[    0.036049] ACPI: SSDT 0x000000009D5F14D8 00008C (v01 AMD    CPMDFMOT 00000001 INTL 20051117)
[    0.036057] ACPI: SSDT 0x000000009D5F1568 0010E8 (v01 AMD    CPMCMN   00000001 INTL 20051117)
[    0.036090] ACPI: Local APIC address 0xfee00000
[    0.036409] No NUMA configuration found
[    0.036412] Faking a node at [mem 0x0000000000000000-0x000000013effffff]
[    0.036437] NODE_DATA(0) allocated [mem 0x13efd3000-0x13effdfff]
[    0.037371] Zone ranges:
[    0.037373]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.037376]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.037379]   Normal   [mem 0x0000000100000000-0x000000013effffff]
[    0.037381]   Device   empty
[    0.037383] Movable zone start for each node
[    0.037390] Early memory node ranges
[    0.037392]   node   0: [mem 0x0000000000001000-0x000000000009dfff]
[    0.037394]   node   0: [mem 0x0000000000100000-0x000000009d5abfff]
[    0.037396]   node   0: [mem 0x000000009e748000-0x000000009e748fff]
[    0.037398]   node   0: [mem 0x000000009e751000-0x000000009e8a4fff]
[    0.037400]   node   0: [mem 0x000000009ecce000-0x000000009ed10fff]
[    0.037402]   node   0: [mem 0x000000009eff2000-0x000000009effffff]
[    0.037404]   node   0: [mem 0x0000000100001000-0x000000013effffff]
[    0.037993] Zeroed struct page in unavailable ranges: 10514 pages
[    0.037996] Initmem setup node 0 [mem 0x0000000000001000-0x000000013effffff]
[    0.038000] On node 0 totalpages: 902894
[    0.038003]   DMA zone: 64 pages used for memmap
[    0.038005]   DMA zone: 21 pages reserved
[    0.038007]   DMA zone: 3997 pages, LIFO batch:0
[    0.038335]   DMA32 zone: 10014 pages used for memmap
[    0.038337]   DMA32 zone: 640850 pages, LIFO batch:63
[    0.094293]   Normal zone: 4032 pages used for memmap
[    0.094300]   Normal zone: 258047 pages, LIFO batch:63
[    0.114546] ACPI: PM-Timer IO Port: 0x808
[    0.114557] ACPI: Local APIC address 0xfee00000
[    0.114576] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.114592] IOAPIC[0]: apic_id 5, version 33, address 0xfec00000, GSI 0-23
[    0.114600] IOAPIC[1]: apic_id 6, version 33, address 0xfec01000, GSI 24-55
[    0.114606] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.114610] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.114614] ACPI: IRQ0 used by override.
[    0.114617] ACPI: IRQ9 used by override.
[    0.114622] Using ACPI (MADT) for SMP configuration information
[    0.114626] ACPI: HPET id: 0x10228210 base: 0xfed00000
[    0.114640] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.114696] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
...
[    0.114754] PM: Registered nosave memory: [mem 0x100000000-0x100000fff]
[    0.114759] [mem 0x9f000000-0xfebfffff] available for PCI devices
[    0.114762] Booting paravirtualized kernel on bare hardware
[    0.114769] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.114795] random: get_random_bytes called from start_kernel+0x97/0x516 with crng_init=0
[    0.114815] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[    0.115815] percpu: Embedded 47 pages/cpu s155648 r8192 d28672 u524288
[    0.115841] pcpu-alloc: s155648 r8192 d28672 u524288 alloc=1*2097152
[    0.115844] pcpu-alloc: [0] 0 1 2 3 
[    0.115924] Built 1 zonelists, mobility grouping on.  Total pages: 888763
[    0.115926] Policy zone: Normal
[    0.115932] Kernel command line: BOOT_IMAGE=(loop)/casper/vmlinuz file=/cdrom/preseed/linuxmint.seed boot=casper quiet splash iso-scan/filename=/Image-Dateien/linuxmint-19.3-cinnamon-64bit.iso debian-installer/language=de console-setup/layoutcode?=de uefi --
[    0.140745] Calgary: detecting Calgary via BIOS EBDA area
[    0.140752] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.171421] Memory: 3415576K/3611576K available (14339K kernel code, 2335K rwdata, 4408K rodata, 2588K init, 5192K bss, 196000K reserved, 0K cma-reserved)
[    0.171784] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.171804] ftrace: allocating 41617 entries in 163 pages
[    0.218472] rcu: Hierarchical RCU implementation.
[    0.218478] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4.
[    0.218480] 	Tasks RCU enabled.
[    0.218483] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.218485] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.228592] NR_IRQS: 524544, nr_irqs: 1000, preallocated irqs: 16
[    0.228980] spurious 8259A interrupt: IRQ7.
[    0.232152] Console: colour VGA+ 80x25
[    0.232163] printk: console [tty0] enabled
[    0.232205] ACPI: Core revision 20181213
[    0.232762] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
[    0.232781] hpet clockevent registered
[    0.232792] APIC: Switch to symmetric I/O mode setup
[    0.233525] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.252792] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1cc65f36a68, max_idle_ns: 881590538042 ns
[    0.252820] Calibrating delay loop (skipped), value calculated using timer frequency.. 1996.25 BogoMIPS (lpj=3992516)
[    0.252825] pid_max: default: 32768 minimum: 301
[    0.252908] LSM: Security Framework initializing
[    0.252936] Yama: becoming mindful.
[    0.252982] AppArmor: AppArmor initialized
[    0.254973] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.256027] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.256124] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.256163] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.256831] LVT offset 1 assigned for vector 0xf9
[    0.256841] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
[    0.256843] Last level dTLB entries: 4KB 512, 2MB 256, 4MB 128, 1GB 0
[    0.256846] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.256851] Spectre V2 : Mitigation: Full AMD retpoline
[    0.256853] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.256857] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.257264] Freeing SMP alternatives memory: 36K
[    0.376894] smpboot: CPU0: AMD Quad-Core Processor (up to 1.4GHz) (family: 0x16, model: 0x0, stepping: 0x1)
[    0.377273] Performance Events: AMD PMU driver.
[    0.377282] ... version:                0
[    0.377284] ... bit width:              48
[    0.377286] ... generic registers:      4
[    0.377288] ... value mask:             0000ffffffffffff
[    0.377289] ... max period:             00007fffffffffff
[    0.377290] ... fixed-purpose events:   0
[    0.377292] ... event mask:             000000000000000f
[    0.377400] rcu: Hierarchical SRCU implementation.
[    0.379084] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.379252] smp: Bringing up secondary CPUs ...
[    0.379606] x86: Booting SMP configuration:
[    0.379609] .... node  #0, CPUs:      #1 #2 #3
[    0.387484] smp: Brought up 1 node, 4 CPUs
[    0.387484] smpboot: Max logical packages: 1
[    0.387484] smpboot: Total of 4 processors activated (7985.03 BogoMIPS)
[    0.389414] devtmpfs: initialized
[    0.389414] x86/mm: Memory block size: 128MB
[    0.390158] PM: Registering ACPI NVS region [mem 0x9d5f3000-0x9dbeafff] (6258688 bytes)
[    0.390158] PM: Registering ACPI NVS region [mem 0x9e749000-0x9e750fff] (32768 bytes)
[    0.390158] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.390158] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.390158] pinctrl core: initialized pinctrl subsystem
[    0.390158] RTC time: 03:29:47, date: 2020-06-16
[    0.390158] NET: Registered protocol family 16
[    0.392943] audit: initializing netlink subsys (disabled)
[    0.392960] audit: type=2000 audit(1592278186.160:1): state=initialized audit_enabled=0 res=1
[    0.393133] EISA bus registered
[    0.393157] cpuidle: using governor ladder
[    0.393168] cpuidle: using governor menu
[    0.393205] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.393205] ACPI: bus type PCI registered
[    0.393205] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.393205] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.393205] PCI: not using MMCONFIG
[    0.393205] PCI: Using configuration type 1 for base access
[    0.393205] PCI: Using configuration type 1 for extended access
[    0.393723] mtrr: your CPUs had inconsistent fixed MTRR settings
[    0.393724] mtrr: your CPUs had inconsistent variable MTRR settings
[    0.393725] mtrr: probably your BIOS does not setup all CPUs.
[    0.393726] mtrr: corrected configuration.
[    0.397760] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.397760] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.397760] ACPI: Added _OSI(Module Device)
[    0.397760] ACPI: Added _OSI(Processor Device)
[    0.397760] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.397760] ACPI: Added _OSI(Processor Aggregator Device)
[    0.397760] ACPI: Added _OSI(Linux-Dell-Video)
[    0.397760] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.397760] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.432537] ACPI: 6 ACPI AML tables successfully acquired and loaded
[    0.442990] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.452859] ACPI: EC: EC started
[    0.452861] ACPI: EC: interrupt blocked
[    0.565067] ACPI: \_SB_.PCI0.SBRG.H_EC: Used as first EC
[    0.565082] ACPI: \_SB_.PCI0.SBRG.H_EC: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.565092] ACPI: \_SB_.PCI0.SBRG.H_EC: Used as boot DSDT EC to handle transactions
[    0.565095] ACPI: Interpreter enabled
[    0.565288] ACPI: (supports S0 S3 S4 S5)
[    0.565294] ACPI: Using IOAPIC for interrupt routing
[    0.565610] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.566058] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[    0.566159] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.568629] ACPI: Enabled 5 GPEs in block 00 to 1F
[    0.618071] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.618102] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.620007] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR]
[    0.621867] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.621874] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.624636] PCI host bridge to bus 0000:00
...
[    0.624680] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
...
[    0.624736] pci 0000:00:00.0: [1022:1536] type 00 class 0x060000
[    0.625336] pci 0000:00:01.0: [1002:983d] type 00 class 0x030000
[    0.625384] pci 0000:00:01.0: reg 0x10: [mem 0xc0000000-0xcfffffff 64bit pref]
[    0.625409] pci 0000:00:01.0: reg 0x18: [mem 0xd0000000-0xd07fffff 64bit pref]
[    0.625428] pci 0000:00:01.0: reg 0x20: [io  0xf000-0xf0ff]
[    0.625446] pci 0000:00:01.0: reg 0x24: [mem 0xfeb00000-0xfeb3ffff]
[    0.625465] pci 0000:00:01.0: reg 0x30: [mem 0xfeb40000-0xfeb5ffff pref]
[    0.625479] pci 0000:00:01.0: enabling Extended Tags
[    0.625587] pci 0000:00:01.0: supports D1 D2
[    0.625594] pci 0000:00:01.0: PME# supported from D1 D2 D3hot
[    0.626109] pci 0000:00:01.1: [1002:9840] type 00 class 0x040300
[    0.626155] pci 0000:00:01.1: reg 0x10: [mem 0xfeb64000-0xfeb67fff 64bit]
[    0.626216] pci 0000:00:01.1: enabling Extended Tags
[    0.626314] pci 0000:00:01.1: supports D1 D2
[    0.626764] pci 0000:00:02.0: [1022:1538] type 00 class 0x060000
[    0.627274] pci 0000:00:02.3: [1022:1439] type 01 class 0x060400
[    0.627352] pci 0000:00:02.3: enabling Extended Tags
[    0.627460] pci 0000:00:02.3: PME# supported from D0 D3hot D3cold
[    0.627983] pci 0000:00:02.4: [1022:1439] type 01 class 0x060400
[    0.628060] pci 0000:00:02.4: enabling Extended Tags
[    0.628168] pci 0000:00:02.4: PME# supported from D0 D3hot D3cold
[    0.628716] pci 0000:00:10.0: [1022:7814] type 00 class 0x0c0330
[    0.628768] pci 0000:00:10.0: reg 0x10: [mem 0xfeb68000-0xfeb69fff 64bit]
[    0.628973] pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
[    0.629516] pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
[    0.629560] pci 0000:00:11.0: reg 0x10: [io  0xf140-0xf147]
[    0.629579] pci 0000:00:11.0: reg 0x14: [io  0xf130-0xf133]
[    0.629598] pci 0000:00:11.0: reg 0x18: [io  0xf120-0xf127]
[    0.629617] pci 0000:00:11.0: reg 0x1c: [io  0xf110-0xf113]
[    0.629635] pci 0000:00:11.0: reg 0x20: [io  0xf100-0xf10f]
[    0.629654] pci 0000:00:11.0: reg 0x24: [mem 0xfeb6e000-0xfeb6e3ff]
[    0.629761] pci 0000:00:11.0: PME# supported from D3hot
[    0.630239] pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
[    0.630275] pci 0000:00:12.0: reg 0x10: [mem 0xfeb6d000-0xfeb6dfff]
[    0.630813] pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
[    0.630854] pci 0000:00:12.2: reg 0x10: [mem 0xfeb6c000-0xfeb6c0ff]
[    0.630996] pci 0000:00:12.2: supports D1 D2
[    0.631004] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot D3cold
[    0.631483] pci 0000:00:13.0: [1022:7807] type 00 class 0x0c0310
[    0.631518] pci 0000:00:13.0: reg 0x10: [mem 0xfeb6b000-0xfeb6bfff]
[    0.632085] pci 0000:00:13.2: [1022:7808] type 00 class 0x0c0320
[    0.632125] pci 0000:00:13.2: reg 0x10: [mem 0xfeb6a000-0xfeb6a0ff]
[    0.632268] pci 0000:00:13.2: supports D1 D2
[    0.632275] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot D3cold
[    0.632758] pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
[    0.633312] pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
[    0.633357] pci 0000:00:14.2: reg 0x10: [mem 0xfeb60000-0xfeb63fff 64bit]
[    0.633482] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
...
[    0.637854] pci 0000:01:00.0: reg 0x10: [io  0xe000-0xe0ff]
[    0.637976] pci 0000:01:00.0: reg 0x18: [mem 0xfea00000-0xfea00fff 64bit]
[    0.638057] pci 0000:01:00.0: reg 0x20: [mem 0xd0800000-0xd0803fff 64bit pref]
[    0.638489] pci 0000:01:00.0: supports D1 D2
[    0.638496] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.639025] pci 0000:00:02.3: PCI bridge to [bus 01]
...
    0.639235] pci 0000:02:00.0: [168c:0036] type 00 class 0x028000
[    0.639292] pci 0000:02:00.0: reg 0x10: [mem 0xfe900000-0xfe97ffff 64bit]
[    0.639369] pci 0000:02:00.0: reg 0x30: [mem 0xfe980000-0xfe98ffff pref]
[    0.639512] pci 0000:02:00.0: supports D1 D2
[    0.639520] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.639810] pci 0000:00:02.4: PCI bridge to [bus 02]
[    0.639828] pci 0000:00:02.4:   bridge window [mem 0xfe900000-0xfe9fffff]
[    0.643151] ACPI: PCI Interrupt Link [LNKA] (IRQs *4 5 7 10 11 14 15)
...
[    0.650562] ACPI: EC: interrupt unblocked
[    0.650582] ACPI: EC: event unblocked
[    0.650615] ACPI: EC: 0 stale EC events cleared
[    0.650615] ACPI: \_SB_.PCI0.SBRG.H_EC: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.650615] ACPI: \_SB_.PCI0.SBRG.H_EC: Used as boot DSDT EC to handle transactions and events
[    0.650615] SCSI subsystem initialized
[    0.652830] libata version 3.00 loaded.
[    0.652930] pci 0000:00:01.0: vgaarb: setting as boot VGA device
[    0.652930] pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.652930] pci 0000:00:01.0: vgaarb: bridge control possible
[    0.652930] vgaarb: loaded
[    0.652997] ACPI: bus type USB registered
[    0.653087] usbcore: registered new interface driver usbfs
[    0.653132] usbcore: registered new interface driver hub
[    0.653257] usbcore: registered new device driver usb
[    0.653434] pps_core: LinuxPPS API ver. 1 registered
[    0.653438] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.653454] PTP clock support registered
[    0.653560] EDAC MC: Ver: 3.0.0
[    0.653560] PCI: Using ACPI for IRQ routing
[    0.665742] PCI: pci_cache_line_size set to 64 bytes
[    0.665876] e820: reserve RAM buffer [mem 0x0009e800-0x0009ffff]
...
[    0.665915] e820: reserve RAM buffer [mem 0x13f000000-0x13fffffff]
[    0.666475] NetLabel: Initializing
[    0.666480] NetLabel:  domain hash size = 128
[    0.666483] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.666571] NetLabel:  unlabeled traffic allowed by default
[    0.666673] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.666673] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[    0.670023] clocksource: Switched to clocksource tsc-early
[    0.744662] VFS: Disk quotas dquot_6.6.0
[    0.744743] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.745393] AppArmor: AppArmor Filesystem Enabled
[    0.745543] pnp: PnP ACPI init
[    0.746439] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[    0.746469] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.747034] system 00:01: [mem 0xa0000000-0xbfffffff] has been reserved
[    0.747058] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.747462] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.747651] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.748063] system 00:04: [io  0x04d0-0x04d1] has been reserved
[    0.748088] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.748309] pnp 00:05: Plug and Play ACPI device, IDs MSF0001 PNP0303 (active)
[    0.748684] pnp 00:06: Plug and Play ACPI device, IDs ETD0b00 PNP0f13 PNP0f0e PNP0f03 (active)
[    0.751365] system 00:07: [io  0x04d0-0x04d1] has been reserved
...
[    0.751581] system 00:07: [mem 0xff000000-0xffffffff] has been reserved
[    0.751605] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.752644] system 00:08: [io  0x0a00-0x0a07] has been reserved
[    0.752668] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.755449] pnp: PnP ACPI: found 9 devices
[    0.770791] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.770870] pci 0000:00:02.3: PCI bridge to [bus 01]
...
[    0.771564] NET: Registered protocol family 2
[    0.772595] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)
[    0.772711] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[    0.773130] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[    0.773500] TCP: Hash tables configured (established 32768 bind 32768)
[    0.773672] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[    0.773810] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[    0.774187] NET: Registered protocol family 1
[    0.774344] NET: Registered protocol family 44
[    0.774396] pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.774423] pci 0000:00:01.1: Linked as a consumer to 0000:00:01.0
[    0.806399] pci 0000:00:12.0: quirk_usb_early_handoff+0x0/0x6a0 took 30152 usecs
[    0.807136] pci 0000:00:12.2: PME# does not work under D3, disabling it
[    0.808435] pci 0000:00:13.2: PME# does not work under D3, disabling it
[    0.808559] PCI: CLS 64 bytes, default 64
[    0.808829] Unpacking initramfs...
[   19.198112] Freeing initrd memory: 38640K
[   19.198323] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[   19.198327] software IO TLB: mapped [mem 0x995ac000-0x9d5ac000] (64MB)
[   19.198504] amd_uncore: AMD NB counters detected
[   19.198511] amd_uncore: AMD LLC counters detected
[   19.198788] LVT offset 0 assigned for vector 0x400
[   19.198870] perf: AMD IBS detected (0x000000ff)
[   19.199009] check: Scanning for low memory corruption every 60 seconds
[   19.203907] Initialise system trusted keyrings
[   19.203938] Key type blacklist registered
[   19.204103] workingset: timestamp_bits=36 max_order=20 bucket_order=0
[   19.209030] zbud: loaded
[   19.210302] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   19.210975] fuse init (API version 7.28)
[   19.310580] Key type asymmetric registered
[   19.310584] Asymmetric key parser 'x509' registered
[   19.310632] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[   19.310766] io scheduler mq-deadline registered
[   19.311879] pcieport 0000:00:02.3: Signaling PME with IRQ 25
[   19.312329] pcieport 0000:00:02.4: Signaling PME with IRQ 27
[   19.312474] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   19.313087] ACPI: AC Adapter [ADP1] (on-line)
[   19.313280] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[   19.313306] ACPI: Power Button [PWRB]
[   19.313443] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
[   19.313463] ACPI: Lid Switch [LID0]
[   19.313585] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[   19.313628] ACPI: Power Button [PWRF]
[   19.322211] thermal LNXTHERM:00: registered as thermal_zone0
[   19.322216] ACPI: Thermal Zone [TZ00] (68 C)
[   19.324250] thermal LNXTHERM:01: registered as thermal_zone1
[   19.324252] ACPI: Thermal Zone [TZ01] (68 C)
[   19.324733] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[   19.331236] Linux agpgart interface v0.103
[   19.339032] loop: module loaded
[   19.339661] libphy: Fixed MDIO Bus: probed
[   19.339663] tun: Universal TUN/TAP device driver, 1.6
[   19.339779] PPP generic driver version 2.4.2
[   19.339893] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   19.339900] ehci-pci: EHCI PCI platform driver
[   19.340248] ehci-pci 0000:00:12.2: EHCI Host Controller
[   19.340262] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
[   19.340272] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[   19.340283] ehci-pci 0000:00:12.2: debug port 1
[   19.340365] ehci-pci 0000:00:12.2: irq 17, io mem 0xfeb6c000
[   19.352980] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
[   19.353151] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[   19.353155] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.353158] usb usb1: Product: EHCI Host Controller
[   19.353161] usb usb1: Manufacturer: Linux 5.0.0-32-generic ehci_hcd
[   19.353163] usb usb1: SerialNumber: 0000:00:12.2
[   19.353545] hub 1-0:1.0: USB hub found
[   19.353564] hub 1-0:1.0: 4 ports detected
[   19.354201] ehci-pci 0000:00:13.2: EHCI Host Controller
[   19.354219] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 2
[   19.354232] ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[   19.354243] ehci-pci 0000:00:13.2: debug port 1
[   19.354306] ehci-pci 0000:00:13.2: irq 17, io mem 0xfeb6a000
[   19.368983] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
[   19.369157] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[   19.369161] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.369164] usb usb2: Product: EHCI Host Controller
[   19.369167] usb usb2: Manufacturer: Linux 5.0.0-32-generic ehci_hcd
[   19.369169] usb usb2: SerialNumber: 0000:00:13.2
[   19.369522] hub 2-0:1.0: USB hub found
[   19.369541] hub 2-0:1.0: 4 ports detected
[   19.369976] ehci-platform: EHCI generic platform driver
[   19.370020] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   19.370041] ohci-pci: OHCI PCI platform driver
[   19.370359] ohci-pci 0000:00:12.0: OHCI PCI host controller
[   19.370373] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 3
[   19.370435] ohci-pci 0000:00:12.0: irq 18, io mem 0xfeb6d000
[   19.433112] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[   19.433119] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.433122] usb usb3: Product: OHCI PCI host controller
[   19.433125] usb usb3: Manufacturer: Linux 5.0.0-32-generic ohci_hcd
[   19.433127] usb usb3: SerialNumber: 0000:00:12.0
[   19.433547] hub 3-0:1.0: USB hub found
[   19.433568] hub 3-0:1.0: 4 ports detected
[   19.434202] ohci-pci 0000:00:13.0: OHCI PCI host controller
[   19.434215] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 4
[   19.434265] ohci-pci 0000:00:13.0: irq 18, io mem 0xfeb6b000
[   19.450714] battery: ACPI: Battery Slot [BAT1] (battery present)
[   19.497101] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[   19.497107] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.497110] usb usb4: Product: OHCI PCI host controller
[   19.497113] usb usb4: Manufacturer: Linux 5.0.0-32-generic ohci_hcd
[   19.497116] usb usb4: SerialNumber: 0000:00:13.0
[   19.497577] hub 4-0:1.0: USB hub found
[   19.497599] hub 4-0:1.0: 4 ports detected
[   19.497994] ohci-platform: OHCI generic platform driver
[   19.498035] uhci_hcd: USB Universal Host Controller Interface driver
[   19.498398] xhci_hcd 0000:00:10.0: xHCI Host Controller
[   19.498416] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 5
[   19.498605] xhci_hcd 0000:00:10.0: hcc params 0x014040c3 hci version 0x100 quirks 0x0000000000000410
[   19.499082] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[   19.499086] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.499089] usb usb5: Product: xHCI Host Controller
[   19.499092] usb usb5: Manufacturer: Linux 5.0.0-32-generic xhci-hcd
[   19.499094] usb usb5: SerialNumber: 0000:00:10.0
[   19.499372] hub 5-0:1.0: USB hub found
[   19.499391] hub 5-0:1.0: 2 ports detected
[   19.499659] xhci_hcd 0000:00:10.0: xHCI Host Controller
[   19.499667] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 6
[   19.499673] xhci_hcd 0000:00:10.0: Host supports USB 3.0 SuperSpeed
[   19.502013] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[   19.502073] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[   19.502077] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   19.502079] usb usb6: Product: xHCI Host Controller
[   19.502082] usb usb6: Manufacturer: Linux 5.0.0-32-generic xhci-hcd
[   19.502085] usb usb6: SerialNumber: 0000:00:10.0
[   19.502357] hub 6-0:1.0: USB hub found
[   19.502376] hub 6-0:1.0: 2 ports detected
[   19.502727] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
[   19.506132] serio: i8042 KBD port at 0x60,0x64 irq 1
[   19.506143] serio: i8042 AUX port at 0x60,0x64 irq 12
[   19.506472] mousedev: PS/2 mouse device common for all mice
[   19.506879] rtc_cmos 00:03: RTC can wake from S4
[   19.507084] rtc_cmos 00:03: registered as rtc0
[   19.507126] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[   19.507147] i2c /dev entries driver
[   19.507386] device-mapper: uevent: version 1.0.3
[   19.507578] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[   19.507623] platform eisa.0: Probing EISA bus 0
...
[   19.507658] platform eisa.0: EISA: Detected 0 cards
[   19.507826] ledtrig-cpu: registered to indicate activity on CPUs
[   19.507965] x86/pm: family 0x16 cpu detected, MSR saving is needed during suspending.
[   19.508579] NET: Registered protocol family 10
[   19.508892] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[   19.523275] Segment Routing with IPv6
[   19.523337] NET: Registered protocol family 17
[   19.523453] Key type dns_resolver registered
[   19.524135] mce: Using 6 MCE banks
[   19.524168] RAS: Correctable Errors collector initialized.
[   19.524262] microcode: CPU0: patch_level=0x0700010b
[   19.524278] microcode: CPU1: patch_level=0x0700010b
[   19.524287] microcode: CPU2: patch_level=0x0700010b
[   19.524301] microcode: CPU3: patch_level=0x0700010b
[   19.524409] microcode: Microcode Update Driver: v2.2.
[   19.524440] sched_clock: Marking stable (19520537912, 3860095)->(19526502880, -2104873)
[   19.525032] registered taskstats version 1
[   19.525056] Loading compiled-in X.509 certificates
[   19.529975] Loaded X.509 cert 'Build time autogenerated kernel key: 8248cf0f90a942a6d35391b2654e2baeb494e1df'
[   19.530043] zswap: loaded using pool lzo/zbud
[   19.544910] Key type big_key registered
[   19.544924] Key type trusted registered
[   19.552163] Key type encrypted registered
[   19.552172] AppArmor: AppArmor sha1 policy hashing enabled
[   19.552192] ima: No TPM chip found, activating TPM-bypass!
[   19.552205] ima: Allocated hash algorithm: sha1
[   19.552225] No architecture policies found
[   19.552254] evm: Initialising EVM extended attributes:
...
[   19.553220]   Magic number: 8:443:462
[   19.553534] rtc_cmos 00:03: setting system clock to 2020-06-16T03:30:06 UTC (1592278206)
[   19.554074] acpi_cpufreq: overriding BIOS provided _PSD data
[   19.560142] Freeing unused decrypted memory: 2040K
[   19.561787] Freeing unused kernel image memory: 2588K
[   19.593001] Write protecting the kernel read-only data: 22528k
[   19.594311] Freeing unused kernel image memory: 2016K
[   19.595348] Freeing unused kernel image memory: 1736K
[   19.632033] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[   19.632054] Run /init as init process
[   19.688860] usb 1-1: new high-speed USB device number 2 using ehci-pci
[   19.832866] usb 5-1: new high-speed USB device number 2 using xhci_hcd
[   19.845462] usb 1-1: New USB device found, idVendor=214b, idProduct=7250, bcdDevice= 1.00
[   19.845468] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   19.845472] usb 1-1: Product: USB2.0 HUB
[   19.845910] hub 1-1:1.0: USB hub found
[   19.846079] hub 1-1:1.0: 4 ports detected
[   19.852311] ACPI: Video Device [VGA1] (multi-head: yes  rom: no  post: no)
[   19.853237] acpi device:3f: registered as cooling_device4
[   19.853379] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
[   19.917897] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[   19.917903] piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
[   19.924405] r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
[   19.929046] ahci 0000:00:11.0: version 3.0
[   19.929542] ahci 0000:00:11.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[   19.929550] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part 
[   19.929571] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[   19.930621] scsi host0: ahci
[   19.931163] scsi host1: ahci
[   19.931399] ata1: SATA max UDMA/133 abar m1024@0xfeb6e000 port 0xfeb6e100 irq 34
[   19.931405] ata2: SATA max UDMA/133 abar m1024@0xfeb6e000 port 0xfeb6e180 irq 34
[   19.940873] libphy: r8169: probed
[   19.941433] r8169 0000:01:00.0 eth0: RTL8168g/8111g, 18:67:b0:4d:30:82, XID 4c0, IRQ 35
[   19.941438] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   19.973020] usb 1-3: new high-speed USB device number 3 using ehci-pci
[   20.001137] usb 5-1: New USB device found, idVendor=152e, idProduct=2571, bcdDevice= 1.00
[   20.001144] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   20.001148] usb 5-1: Product: Portable Super Multi Drive
[   20.001152] usb 5-1: Manufacturer: HLDS Inc
[   20.001155] usb 5-1: SerialNumber: HitachLGda000000140
[   20.012838] usb 4-2: new full-speed USB device number 2 using ohci-pci
[   20.091617] r8169 0000:01:00.0 enp1s0: renamed from eth0
[   20.102669] usb-storage 5-1:1.0: USB Mass Storage device detected
[   20.103045] scsi host2: usb-storage 5-1:1.0
[   20.103311] usbcore: registered new interface driver usb-storage
[   20.105255] [drm] radeon kernel modesetting enabled.
[   20.106034] [drm] initializing kernel modesetting (KABINI 0x1002:0x983D 0x144D:0xC730 0x00).
[   20.106077] [drm] doorbell mmio base: 0xD0000000
[   20.106078] [drm] doorbell mmio size: 8388608
[   20.106189] ATOM BIOS: AMD
[   20.106274] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
[   20.106279] radeon 0000:00:01.0: GTT: 2048M 0x0000000020000000 - 0x000000009FFFFFFF
[   20.106288] [drm] Detected VRAM RAM=512M, BAR=256M
[   20.106290] [drm] RAM width 128bits DDR
[   20.106462] [TTM] Zone  kernel: Available graphics memory: 1731316 kiB
[   20.106465] [TTM] Initializing pool allocator
[   20.106476] [TTM] Initializing DMA pool allocator
[   20.106544] [drm] radeon: 512M of VRAM memory ready
[   20.106546] [drm] radeon: 2048M of GTT memory ready.
[   20.106580] [drm] Loading kabini Microcode
[   20.106924] [drm] Internal thermal controller without fan control
[   20.108467] [drm] radeon: dpm initialized
[   20.108752] [drm] Found UVD firmware Version: 1.64 Family ID: 9
[   20.109104] usbcore: registered new interface driver uas
[   20.112928] [drm] Found VCE firmware/feedback version 40.2.2 / 15!
[   20.112970] [drm] GART: num cpu pages 524288, num gpu pages 524288
[   20.129801] usb 1-3: New USB device found, idVendor=0bda, idProduct=0129, bcdDevice=39.60
[   20.129809] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   20.129813] usb 1-3: Product: USB2.0-CRW
[   20.129817] usb 1-3: Manufacturer: Generic
[   20.129821] usb 1-3: SerialNumber: 20100201396000000
[   20.137642] [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
[   20.137950] radeon 0000:00:01.0: WB enabled
...
[   20.139273] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   20.139275] [drm] Driver supports precise vblank timestamp query.
[   20.139390] radeon 0000:00:01.0: radeon: using MSI.
[   20.139449] [drm] radeon: irq initialized.
...
[   20.209436] [drm] UVD initialized successfully.
[   20.216866] usb 1-1.2: new low-speed USB device number 4 using ehci-pci
[   20.232851] tsc: Refined TSC clocksource calibration: 998.127 MHz
[   20.232869] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1cc65b93289, max_idle_ns: 881590487074 ns
[   20.318661] clocksource: Switched to clocksource tsc
[   20.318703] [drm] ring test on 6 succeeded in 17 usecs
[   20.318719] [drm] ring test on 7 succeeded in 3 usecs
[   20.318720] [drm] VCE initialized successfully.
[   20.318741] ata2: SATA link down (SStatus 0 SControl 300)
[   20.320245] [drm] ib test on ring 0 succeeded in 0 usecs
...
[   20.322910] usb 4-2: New USB device found, idVendor=0cf3, idProduct=3004, bcdDevice= 0.01
[   20.322916] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   20.333298] usbcore: registered new interface driver rtsx_usb
[   20.342133] random: fast init done
[   20.342416] random: systemd-udevd: uninitialized urandom read (16 bytes read)
...
[   20.408801] usb 1-1.2: New USB device found, idVendor=0000, idProduct=0538, bcdDevice= 1.00
[   20.408850] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   20.408855] usb 1-1.2: Product:  USB OPTICAL MOUSE
[   20.431128] hidraw: raw HID events driver (C) Jiri Kosina
[   20.440336] usbcore: registered new interface driver usbhid
[   20.440339] usbhid: USB HID core driver
[   20.447130] input:  USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1.2/1-1.2:1.0/0003:0000:0538.0001/input/input7
[   20.447494] hid-generic 0003:0000:0538.0001: input,hidraw0: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-0000:00:12.2-1.2/input0
[   20.480881] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   20.482019] ata1.00: NCQ Send/Recv Log not supported
[   20.482023] ata1.00: ATA-9: SAMSUNG MZMTD128HAFV-000, DXT41K0Q, max UDMA/133
[   20.482028] ata1.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 32), AA
[   20.482431] ata1.00: NCQ Send/Recv Log not supported
[   20.482520] ata1.00: configured for UDMA/133
[   20.483094] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG MZMTD128 1K0Q PQ: 0 ANSI: 5
[   20.483784] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   20.483943] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[   20.484002] sd 0:0:0:0: [sda] Write Protect is off
[   20.484007] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   20.484108] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   20.488241]  sda: sda1 sda2 sda3 sda4
[   20.488869] usb 1-1.4: new high-speed USB device number 5 using ehci-pci
[   20.489866] sd 0:0:0:0: [sda] Attached SCSI disk
[   20.535957] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x575f05)
[   20.549308] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x15, 0x0e.
[   20.562362] psmouse serio1: elantech: Elan sample query result 10, 01, 97
[   20.628858] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
[   20.664902] usb 2-3: new high-speed USB device number 3 using ehci-pci
[   20.869155] [drm] ib test on ring 5 succeeded
[   20.890068] [drm] ib test on ring 6 succeeded
[   20.890924] [drm] ib test on ring 7 succeeded
[   20.905159] usb 2-3: New USB device found, idVendor=2232, idProduct=1054, bcdDevice= 0.15
[   20.905167] usb 2-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[   20.905172] usb 2-3: Product: WebCam SC-10HDD13335N
[   20.905175] usb 2-3: Manufacturer: Generic
[   20.905179] usb 2-3: SerialNumber: 200901010001
[   20.952911] [drm] radeon atom DIG backlight initialized
[   20.952920] [drm] Radeon Display Connectors
[   20.952924] [drm] Connector 0:
[   20.952927] [drm]   LVDS-1
[   20.952929] [drm]   HPD1
[   20.952934] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
[   20.952935] [drm]   Encoders:
[   20.952937] [drm]     LCD1: INTERNAL_UNIPHY
[   20.952939] [drm] Connector 1:
[   20.952941] [drm]   HDMI-A-1
[   20.952942] [drm]   HPD2
[   20.952947] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
[   20.952948] [drm]   Encoders:
[   20.952950] [drm]     DFP1: INTERNAL_UNIPHY
[   20.952951] [drm] Connector 2:
[   20.952953] [drm]   VGA-1
[   20.952957] [drm]   DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 0x65cc
[   20.952958] [drm]   Encoders:
[   20.952960] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[   21.000981] usb 1-1.4: device not accepting address 5, error -32
[   21.081001] usb 1-1.4: new high-speed USB device number 6 using ehci-pci
[   21.126755] scsi 2:0:0:0: CD-ROM            HL-DT-ST BD-RE BP40NS20   ML04 PQ: 0 ANSI: 0
[   21.131668] sr 2:0:0:0: [sr0] scsi3-mmc drive: 31x/31x writer dvd-ram cd/rw xa/form2 cdda tray
[   21.131675] cdrom: Uniform CD-ROM driver Revision: 3.20
[   21.132398] sr 2:0:0:0: Attached scsi CD-ROM sr0
[   21.132647] sr 2:0:0:0: Attached scsi generic sg1 type 5
[   21.576990] usb 1-1.4: device not accepting address 6, error -32
[   21.577258] usb 1-1-port4: attempt power cycle
[   21.935165] [drm] fb mappable at 0xC0722000
[   21.935169] [drm] vram apper at 0xC0000000
[   21.935171] [drm] size 4325376
[   21.935173] [drm] fb depth is 24
[   21.935175] [drm]    pitch is 5632
[   21.935490] fbcon: radeondrmfb (fb0) is primary device
[   22.035879] Console: switching to colour frame buffer device 170x48
[   22.046291] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[   22.070477] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0
[   22.078966] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[   22.078968] AMD-Vi: AMD IOMMUv2 functionality not available on this system
[   22.210548] [drm] amdgpu kernel modesetting enabled.
[   22.210830] Parsing CRAT table with 1 nodes
[   22.210839] Ignoring ACPI CRAT on non-APU system
[   22.210848] Virtual CRAT table created for CPU
[   22.210849] Parsing CRAT table with 1 nodes
[   22.210852] Creating topology SYSFS entries
[   22.210891] Topology: Add CPU node
[   22.210892] Finished initializing topology
[   22.240976] usb 1-1.4: new high-speed USB device number 7 using ehci-pci
[   22.736987] usb 1-1.4: device not accepting address 7, error -32
[   22.816988] usb 1-1.4: new high-speed USB device number 8 using ehci-pci
[   23.312983] usb 1-1.4: device not accepting address 8, error -32
[   23.313402] usb 1-1-port4: unable to enumerate USB device
[   26.902808] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[   26.921376] JFS: nTxBlock = 8192, nTxLock = 65536
[   27.020797] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   27.184700] EXT4-fs (sda2): recovery complete
[   27.191695] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   27.234904] EXT4-fs (sda3): recovery complete
[   27.236400] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[   27.807421] ISO 9660 Extensions: Microsoft Joliet Level 3
[   27.876444] ISO 9660 Extensions: RRIP_1991A
[   31.241401] ISO 9660 Extensions: Microsoft Joliet Level 3
[   31.241586] ISO 9660 Extensions: RRIP_1991A
[   70.186302] random: crng init done
[   70.186308] random: 7 urandom warning(s) missed due to ratelimiting
[   96.165353] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[   96.185332] systemd[1]: Detected architecture x86-64.
[   96.191415] systemd[1]: Set hostname to <mint>.
[   97.764437] systemd[1]: Unnecessary job for /dev/loop1 was removed.
[   97.764455] systemd[1]: Unnecessary job for BD-RE_BP40NS20 LinuxWelt_2020-2 was removed.
[   97.765752] systemd[1]: Created slice User and Session Slice.
[   97.765881] systemd[1]: Reached target User and Group Name Lookups.
[   97.765913] systemd[1]: Reached target Swap.
[   97.765947] systemd[1]: Reached target Remote File Systems.
[   97.766406] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[   98.803468] systemd-journald[1014]: Received request to flush runtime journal from PID 1
[  101.221415] lp: driver loaded but no devices found
[  101.314930] ppdev: user-space parallel port driver
[  107.738516] cryptd: max_cpu_qlen set to 1000
[  110.115858] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[  110.123729] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[  110.224566] samsung_laptop: detected SABI interface: SwSmi@
[  110.234424] AVX version of gcm_enc/dec engaged.
[  110.234428] AES CTR mode by8 optimization enabled
[  115.486768] snd_hda_intel 0000:00:01.1: Force to non-snoop mode
[  122.626737] media: Linux media interface: v0.10
[  125.468387] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input8
[  125.481489] Bluetooth: Core ver 2.22
[  125.481555] NET: Registered protocol family 31
[  125.481558] Bluetooth: HCI device and connection manager initialized
...
[  126.111985] videodev: Linux video capture interface: v2.00
[  127.943647] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC269VC: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
...
[  127.951680] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input9
[  127.951865] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input10
[  132.792338] usbcore: registered new interface driver btusb
[  135.792702] uvcvideo: Found UVC 1.00 device WebCam SC-10HDD13335N (2232:1054)
[  135.805819] uvcvideo 2-3:1.0: Entity type for entity Extension 4 was not initialized!
[  135.805831] uvcvideo 2-3:1.0: Entity type for entity Processing 2 was not initialized!
[  135.805838] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[  135.806174] input: WebCam SC-10HDD13335N: WebCam S as /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/input/input11
[  135.806620] usbcore: registered new interface driver uvcvideo
[  135.806624] USB Video Class driver (1.1.1)
[  139.734315] usb 4-2: USB disconnect, device number 2
[  139.735407] usbcore: registered new interface driver ath3k
[  140.192274] usb 4-2: new full-speed USB device number 3 using ohci-pci
[  145.538130] usb 4-2: New USB device found, idVendor=0cf3, idProduct=3004, bcdDevice= 0.02
[  145.538143] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  146.384122] ath: phy0: WB335 2-ANT card detected
...
[  148.271664] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[  148.274289] ieee80211 phy0: Atheros AR9565 Rev:1 mem=0xffff9c9cc2700000, irq=40
[  149.921322] ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
[  150.982574] kvm: Nested Virtualization enabled
[  150.982582] kvm: Nested Paging enabled
[  151.900401] MCE: In-kernel MCE decoding enabled.
[  152.752119] EDAC amd64: Node 0: DRAM ECC disabled.
[  152.752124] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
...
[  153.034204] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
...
[  299.395158] xor: automatically using best checksumming function   avx       
[  299.907465] Btrfs loaded, crc32c=crc32c-intel
[  343.687402]  sda: sda1 sda2 sda3 sda4
[  534.255126]  sda: sda1 sda2 sda3 sda4
[  535.124292]  sda: sda1 sda2 sda3 sda4
[  855.896208] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[  878.813777] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[13605.998369] bpfilter: Loaded bpfilter_umh pid 3378
...
I hope I have given enough info to get help.

I speak english and german and don't mind getting help in either language :)
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

w23 wrote: Tue Jun 16, 2020 4:09 pm One main thing I couldn't find was howto install mint in UEFI mode from DVD boot media.
I don't know what boot options I have to place on kernel command line or elsewhere to get mint to install itself in UEFI mode to SSD.
Do I need a special DVD version of mint that explicitly supports UEFI?
Let's take it one at a time and start with that one as it is most critical to accomplishing what you want and the other questions are more or less secondary.

First of all, the ISO file that you downloaded for installing Mint is itself capable of supporting either of the two boot modes (either "legacy" BIOS-MBR or EUFI-GPT booting). No "special" version is needed and no special command line input is required to determine which boot mode is used. What is required is "burning" the ISO file to the installation media (DVD or USB stick) in a way that will allow it to be booted in the desired mode. And the second requirement is to select the correct options available in your system's UEFI (NVRAM) configuration to actually boot the installation media in that desired mode.

What utility are you using to burn the ISO to the DVD disk?
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

Thank you for your fast response.

On a second laptop of the same kind with Windows 10 Pro installed I use Imgburn v2.5.8.0 to burn CD/DVD media, but I have to unplug the DVD/Blueray Player drive and reconnect it there as I only have one USB DVD-Player to share on all PCs.

The usb connected drive I use is mentioned in my first post:

Code: Select all

...
[   21.126755] scsi 2:0:0:0: CD-ROM            HL-DT-ST BD-RE BP40NS20   ML04 PQ: 0 ANSI: 0
[   21.131668] sr 2:0:0:0: [sr0] scsi3-mmc drive: 31x/31x writer dvd-ram cd/rw xa/form2 cdda tray
...
At the moment the PC/Laptop I'm writing from is using the mounted Live DVD media which seems to be having been installed in legacy mode by default.
If neccessary, I can provide pictures of Laptop screen of Bios setup used.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

Yes, I saw the USB-connected DVD drive in your posted info and that should not be an issue. Unfortunately, however, I have never used and know nothing at all about that ImgBurn utility. From what I'm able to find about it on line, it looks like it should do the job okay, although I see one old report (here) of failure to burn for UEFI booting. Just as a quick check, take a Windows Explorer look at your DVD disk itself to verify that it includes /EFI/BOOT/BOOTx64.EFI and /EFI/BOOT/grubx64.efi files. If so, it should be fine.

I suspect that your main difficulties may arise from the rather poorly implemented and documented UEFI/BIOS set-up in that Samsung NP905S3G notebook. As you've no doubt discovered, having already managed to boot the DVD in "legacy" BIOS-MBR mode, just finding a way to do that can be a challenge. Now you have to make it boot that same DVD in UEFI mode instead. From what you've already done, I must assume that you've disabled its so-called "fast bios" and "secure boot" settings and have also set its boot mode selection to allow both UEFI and CSM (compatibilty support mode) booting. You should therefore now be able to select from the notebook's start-up boot list (F10?) or its UEFI/BIOS boot override options (F2 -> Exit?) the DVD to boot in either of those two modes. Are you able to see the DVD listed twice in either place? If so, select the option labelled [UEFI] and not the other one without that label.

If you're able to do that and it boots successfully, you're on your way to installing Mint for the same UEFI-GPT mode booting as your existing Windows installation and we can move along to those other questions you've asked.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

The actual linux image booted does contain the requested files:

Code: Select all

mint@mint:~$ ls -l /cdrom/EFI/BOOT/
total 2424
-r--r--r-- 1 root root 1334816 Okt 25  2019 BOOTx64.EFI
-r--r--r-- 1 root root 1146744 Okt 25  2019 grubx64.efi
mint@mint:~$ 
But as I plan to burn the newly downloaded images to DVD soon, perhaps you can suggest free alternatives you may know of I could use instead of Imgburn, as the reported problem seems to be the same version of Imgburn I have installed on the windows laptop.
An alternative windows software capable of burning UEFI-DVDs would let me burn an alternative media downloaded last night from a mirror site, so we have a common linux media base.

Strange enough though, I used Imgburn because it was suggested here.
... I must assume that you've disabled its so-called "fast bios" and "secure boot" settings and have also set its boot mode selection to allow both UEFI and CSM (compatibilty support mode) booting.
That is correct.

However, as the DVD media is from a german linux magazine containing seven live linux systems, at the moment I don't know with what burner software they created that disk.

With the magazine DVD in the DVD drive I was only presented one boot option, to boot from that DVD drive, there were no other options as you mentioned them, to alternately choose legacy or UEFI boot. Without the DVD in the drive, I am not presented any boot options, I just get a system error that all boot options have been tried...

Furthermore, I will want to check an idea that came up last night, that one possibility for installation in legacy mode could be the boot options in BIOS were set to CSM and UEFI. I would therefore like to give it a try to restart boot from DVD with a different setup in BIOS.
If that fails, there is a chance to email the publisher of the magazine DVD and ask him, if the magazine DVD has been tested to boot on UEFI systems.

And the last testing can only be done with an alternate burning tool in windows so if you have any idea which preferably free software I could use would be very helpful.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

w23 wrote: Wed Jun 17, 2020 2:10 am And the last testing can only be done with an alternate burning tool in windows so if you have any idea which preferably free software I could use would be very helpful.
Well, I can't offer much help with that, I'm afraid, as I very seldom use optical media any more. On the rare occasions when I do, in Windows I either use Nero (not free) or I just use Window 10's own ISO burning capability (see here).

However, I really don't think that's your problem. As I said, if you see those two bootloader files included, the DVD disk itself should be okay for UEFI booting. Have you not been able to locate that boot option as I described it in your system's UEFI/BIOS set-up? If not, maybe someone more familiar than I am with that Samsung notebook can explain it better for you.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

My tries to do so all failed using yumi, rufus and other tools on windows in the past. That's why I got back to burn DVDs.
I was unable to find the windows burning tool you used in my windows 10 pro.

I'm not about to give up here :)

I've looked through my dvd sets an found:
1. a gentoo rescue disk, that booted my laptop, I was able to choose uefi or not uefi start from DVD.
2. a windows recovery cd offering uefi boot from cd, but I was unable to tweak any other firmware boot options other than those I can tweak using F2-key on bootup.

So I'm willing to try usb-boot, I downloaded rufus 3.10 and also the linuxmint-19.3-cinnamon-64bit.iso .

I suspect the media I used isn't complete somehow.

At the moment, rufus is burning the usb drive with that image, see picture of rufus working, in german language

If all goes well, I'll report what happens.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

I admire your persistence, but I really don't know what else I can tell you. Unless and until you can discover your system's UEFI settings that will allow you to boot the installation media in the required UEFI boot mode, no number of ISO "re-burns" by any method is going to alter the outcome.
fabien85
Level 7
Level 7
Posts: 1877
Joined: Tue Mar 11, 2014 4:30 pm

Re: Mint install on Samsung NP905S3G fails to boot

Post by fabien85 »

You will probably have better luck with burning to a USB stick rather than to a DVD. I know systems which do not boot DVDs in UEFI mode.
I suggest you also disable the CSM (=Compatibility Support Module) in your firmware/BIOS, if that's possible.
This CSM allows to boot in Legacy/BIOS mode. So if you can disable it, it will force to boot in UEFI mode.
Most manufacturers allow to disable the CSM, though I dont know for Samsung. And if yes, I dont know how complicated they made it.

That said, you could also just install in Legacy/BIOS mode. Unless you intend to experiment and learn fancy stuff with UEFI, it frankly makes no difference to your Linux Mint. If anything it makes it a bit simpler, since you dont have to worry about secure boot.
It's possible to have a Legacy install even if you want your hard drive to be formatted with GPT. See this tutorial : viewtopic.php?f=42&t=223015
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

Yes, persistence is a neat personal feature of mine, that let me do my work as a professional computer programmer in the old days prior to my retirement :)

I did a little testing of different options in rufus 3.10, as well as playing with BIOS options and I must say, it was worth it :)

This setup of rufus, in german language
and the BIOS boot option "UEFI only"
and the download of linuxmint-19.3-cinnamon-64bit.iso from a mirror nearby (never again will I use linux magazines with included DVDs to setup a UEFI system)
finally led to a booted mint in UEFI mode, tested with this command:

Code: Select all

[ -d /sys/firmware/efi ] && echo "UEFI mode" || echo "Legacy mode"
.

I'm also adding the screenshots from BIOS setup BIOS UEFI only and BIOS Boot priorities with plugged in usb-stick for the chance other users with the same problem on this type of laptop have the full advantage of a full documentation.

Installation from usb-stick succeeded, but after reboot of the system without inserted usb-stick, my laptop says "all boot options are tried...." and fails to start the system.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

Well, it's all good with getting the installation media booted in UEFI mode and you say that, having done that, you then successfully ran the installer in that Mint "live" session. However, your system is now unable to find and boot that successful Mint installation on its main drive.

The only two possibilities that I can infer from that are that either (a) the LM installation was not actually successful as you thought, or (b) your system requires your manual assistance in updating its UEFI (NVRAM) boot order sequence to include the newly installed LM boot loader.

To narrow that down, you can examine the *.efi boot loader files that should now be installed into the EFI System Partition (ESP) of the Samsung notebook's main drive and list them here. Also, without the installation media attached, what, if anything, now appears in the system's UEFI boot order list and do you see any option there for adding an entry manually?
fabien85
Level 7
Level 7
Posts: 1877
Joined: Tue Mar 11, 2014 4:30 pm

Re: Mint install on Samsung NP905S3G fails to boot

Post by fabien85 »

Congrats on the UEFI install, now let's debug why it wont boot.
A good way to answer arvy's questions and give us more information with a complete view of the system is to create a Boot-info report and post it here.
To do so :
1) boot the live USB
2) connect to internet (not mandatory but makes it easier to share the report)
3) Launch Boot-repair
4) it will take a few seconds to scan the system and then you will get two options : one to repair the boot, and one to create a boot-info report. Use that second one.
5) If you were connected to internet, boot-repair will offer to upload the report on pastebin. Do so, and share the link here. Dont worry there is no sensitive information there. (and anyway you do not have any personal data on the system yet)
If you did not connect to internet, then you will get the report in text form. Save it and post it here between code tags (button </> above the typing area) which improves readability for us.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

I had to install boot repair first and that at least worked. Here is the link to the pastebin.
The only two possibilities that I can infer from that are that either (a) the LM installation was not actually successful as you thought, or
(b) your system requires your manual assistance in updating its UEFI (NVRAM) boot order sequence to include the newly installed LM boot loader.
to a) LM installer said Installation was successful, reboot now or commence with live system.
to b) perhaps LM thought everything is ok, but forgot to install something. There is no boot loader active in NVRam.

Grub is new to me, I'm an old lilo fan :)

This is my gparted setup I used to install LM:
/dev/sda1 fat32 EFI-partition 1G boot flags: boot, hidden,esp
/dev/sda2 ext4 / (root partition) 57G no flags
/dev/sda3 ext4 56G no flags will later be mounted as /data
/dev/sda4 lnx-swap 5G no flags

/dev/sda2 is mounted on /mnt at the moment, I want to see which files are where.

In the live system I created a dir /efi and mounted /dev/sda1 into it.
I had to strip off some contents of the listing of "./grub/themes/linuxmint/icons" as it would otherwise exceed posting limits.
These are the contents of /efi:

Code: Select all

ls -alR /efi
/efi:
total 8
drwxr-xr-x 3 root root 4096 Jan  1  1970 .
drwxr-xr-x 1 root root  280 Jun 20 05:01 ..
drwxr-xr-x 4 root root 4096 Jun 18 13:22 EFI

/efi/EFI:
total 16
drwxr-xr-x 4 root root 4096 Jun 18 13:22 .
drwxr-xr-x 3 root root 4096 Jan  1  1970 ..
drwxr-xr-x 2 root root 4096 Jun 18 13:23 BOOT
drwxr-xr-x 3 root root 4096 Jun 18 13:23 ubuntu

/efi/EFI/BOOT:
total 2500
drwxr-xr-x 2 root root    4096 Jun 18 13:23 .
drwxr-xr-x 4 root root    4096 Jun 18 13:22 ..
-rwxr-xr-x 1 root root 1334816 Jun 18 13:23 BOOTX64.EFI
-rwxr-xr-x 1 root root 1213032 Jun 18 13:23 fbx64.efi

/efi/EFI/ubuntu:
total 3732
drwxr-xr-x 3 root root    4096 Jun 18 13:23 .
drwxr-xr-x 4 root root    4096 Jun 18 13:22 ..
-rwxr-xr-x 1 root root     108 Jun 18 13:23 BOOTX64.CSV
drwxr-xr-x 2 root root    4096 Jun 18 13:20 fw
-rwxr-xr-x 1 root root   75992 Jun 18 13:20 fwupx64.efi
-rwxr-xr-x 1 root root     126 Jun 18 13:23 grub.cfg
-rwxr-xr-x 1 root root 1116536 Jun 18 13:23 grubx64.efi
-rwxr-xr-x 1 root root 1269496 Jun 18 13:23 mmx64.efi
-rwxr-xr-x 1 root root 1334816 Jun 18 13:23 shimx64.efi

/efi/EFI/ubuntu/fw:
total 8
drwxr-xr-x 2 root root 4096 Jun 18 13:20 .
drwxr-xr-x 3 root root 4096 Jun 18 13:23 ..
mint@mint:~$ 

These are the contents of /mnt/boot, where again I had to strip off some contents of the listing of "./grub/themes/linuxmint/icons" and "./grub/x86_64-efi" as it would otherwise exceed posting limits:

Code: Select all

mint@mint:/mnt/boot$ ls -alR
total 75932
drwxr-xr-x  3 root root     4096 Jun 20 05:11 .
drwxr-xr-x 25 root root     4096 Jun 19 09:23 ..
-rw-------  1 root root  4295198 Oct 10  2019 System.map-5.0.0-32-generic
-rw-r--r--  1 root root   224447 Oct 10  2019 config-5.0.0-32-generic
drwxr-xr-x  6 root root     4096 Jun 18 13:23 grub
-rw-r--r--  1 root root 63886596 Jun 18 13:21 initrd.img-5.0.0-32-generic
-rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
-rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
-rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
-rw-r--r--  1 root root  8769272 Jun 18 11:46 vmlinuz-5.0.0-32-generic

./grub:
total 2388
drwxr-xr-x 6 root root    4096 Jun 18 13:23 .
drwxr-xr-x 3 root root    4096 Jun 20 05:11 ..
drwxr-xr-x 2 root root    4096 Jun 18 13:22 fonts
-r--r--r-- 1 root root    7029 Jun 18 13:24 grub.cfg
-rw-r--r-- 1 root root    1024 Jun 18 13:22 grubenv
drwxr-xr-x 2 root root    4096 Jun 18 13:23 locale
drwxr-xr-x 3 root root    4096 Dec 13  2019 themes
-rw-r--r-- 1 root root 2397557 Jun 18 13:22 unicode.pf2
drwxr-xr-x 2 root root   12288 Jun 18 13:23 x86_64-efi

./grub/fonts:
total 2388
drwxr-xr-x 2 root root    4096 Jun 18 13:22 .
drwxr-xr-x 6 root root    4096 Jun 18 13:23 ..
-rw-r--r-- 1 root root   34259 Nov 20  2019 UbuntuMono16.pf2
-rw-r--r-- 1 root root 2397557 Jun 18 13:23 unicode.pf2

./grub/locale:
total 276
drwxr-xr-x 2 root root   4096 Jun 18 13:23 .
drwxr-xr-x 6 root root   4096 Jun 18 13:23 ..
-rw-r--r-- 1 root root 134741 Jun 18 13:23 de.mo
-rw-r--r-- 1 root root 120128 Jun 18 13:23 en@quot.mo
-rw-r--r-- 1 root root    976 Jun 18 13:23 en_AU.mo
-rw-r--r-- 1 root root    512 Jun 18 13:23 en_CA.mo
-rw-r--r-- 1 root root   4771 Jun 18 13:23 en_GB.mo

./grub/themes:
total 12
drwxr-xr-x 3 root root 4096 Dec 13  2019 .
drwxr-xr-x 6 root root 4096 Jun 18 13:23 ..
drwxr-xr-x 3 root root 4096 Dec 13  2019 linuxmint

./grub/themes/linuxmint:
total 252
drwxr-xr-x 3 root root   4096 Dec 13  2019 .
drwxr-xr-x 3 root root   4096 Dec 13  2019 ..
-rw-r--r-- 1 root root   1237 Nov 20  2019 LICENSE
-rw-r--r-- 1 root root 212299 Nov 20  2019 background.png
drwxr-xr-x 2 root root   4096 Dec 13  2019 icons
-rw-r--r-- 1 root root     70 Nov 20  2019 item_c.png
-rw-r--r-- 1 root root    161 Nov 20  2019 select_c.png
-rw-r--r-- 1 root root    219 Nov 20  2019 select_e.png
-rw-r--r-- 1 root root    211 Nov 20  2019 select_w.png
-rw-r--r-- 1 root root     68 Nov 20  2019 selected_item_c.png
-rw-r--r-- 1 root root     67 Nov 20  2019 terminal_box_c.png
-rw-r--r-- 1 root root    821 Nov 20  2019 theme.txt

./grub/themes/linuxmint/icons:
total 216
drwxr-xr-x 2 root root 4096 Dec 13  2019 .
drwxr-xr-x 3 root root 4096 Dec 13  2019 ..
-rw-r--r-- 1 root root  283 Nov 20  2019 Manjaro.i686.png
-rw-r--r-- 1 root root  283 Nov 20  2019 Manjaro.x86_64.png
-rw-r--r-- 1 root root  559 Nov 20  2019 antergos.png
-rw-r--r-- 1 root root  467 Nov 20  2019 arch.png
...
-rw-r--r-- 1 root root  385 Nov 20  2019 windows.png
-rw-r--r-- 1 root root  526 Nov 20  2019 xubuntu.png

./grub/x86_64-efi:
total 3228
drwxr-xr-x 2 root root  12288 Jun 18 13:23 .
drwxr-xr-x 6 root root   4096 Jun 18 13:23 ..
-rw-r--r-- 1 root root  15392 Jun 18 13:23 acpi.mod
-rw-r--r-- 1 root root   1928 Jun 18 13:23 adler32.mod
-rw-r--r-- 1 root root   7960 Jun 18 13:23 affs.mod
-rw-r--r-- 1 root root   8176 Jun 18 13:23 afs.mod
-rw-r--r-- 1 root root  22744 Jun 18 13:23 ahci.mod
...
-rw-r--r-- 1 root root  57520 Jun 18 13:23 zfs.mod
-rw-r--r-- 1 root root   8584 Jun 18 13:23 zfscrypt.mod
-rw-r--r-- 1 root root  10648 Jun 18 13:23 zfsinfo.mod
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

I am very sorry to have to tell you this after all your effort to boot the installation media in UEFI mode, but the attempt to install Mint for booting itself in UEFI-GPT mode appears not, in fact, to have fully succeeded. Your system's SSD (/dev/sda) has been properly laid out with the required EFI System Partition (ESP) but no Grub boot loader has been installed into that SSD's ESP. At least not according to your linked pastebin report from boot-repair, and that would certainly explain why your system's UEFI boot order can't find it. Was the list of *.efi files that you've posted possibly taken from /dev/sdb1 (the installation media) or from somewhere else rather than from the /dev/sda1 ESP into which they must be installed in order to boot Mint on your SSD?

Anyhow, you've now got the installation media UEFI booting issue sorted out okay. You just have to get it to install the Grub boot loader files properly into the correct EFI System Partition of your SSD. You can either try again yourself or else let boot-repair try it for you as it says it wants to do. Once that correct Grub boot loader installation has succeeded either way, your system's UEFI set-up should accept it as the default UEFI-GPT boot option -- in fact the only one that will be available without the installation media attached.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

Was the list of *.efi files that you've posted possibly taken from /dev/sdb1 (the installation media) or from somewhere else rather than from the /dev/sda1 ESP into which they must be installed in order to boot Mint on your SSD?
No, the listed files are from /dev/sda1 partition. I double checked it and made a new dir

Code: Select all

sudo mkdir /mnt/efi
I unmounted /efi and instead mounted /dev/sda1 to /mnt/efi, but the listing is the same.
You just have to get it to install the Grub boot loader files properly into the correct EFI System Partition of your SSD.
If the listed files are correct where they should be, and the written stuff did not work, then I will next need help in perhaps manually installing the grub boot loader (cmd line style).

I then did a boot-repair using the first option and here is the report to pastebin.

Boot-repair says it was successful and I can now reboot, so I'll see if it gets listed in NVRam (crossing my fingers :) ).

No, crossing fingers and boot-repair were not successful, no boot option in NVRam.

I guess now comes the command line stuff, I will need help here.

I have removed the hidden flag from /dev/sda1 and ran boot-repair again, but with a few changed options in the advanced section. Here is the new pastebin report and this time there was an error message too "An error occurred during the repair, see line 781 in the pastebin report".

By the way, how do I correct a corrupt backup partition table?

And to the people responsible for boot-repair, please identify the mbr of /dev/sdb correctly
AKEO
is related to the author of rufus, his website: https://rufus.ie . The pastebin file has more notices concerning reporting to them.
Last edited by w23 on Sat Jun 20, 2020 12:52 pm, edited 2 times in total.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
arvy
Level 6
Level 6
Posts: 1286
Joined: Sat Mar 26, 2016 11:22 am

Re: Mint install on Samsung NP905S3G fails to boot

Post by arvy »

w23 wrote: Sat Jun 20, 2020 9:30 am Boot-repair says it was successful and I can now reboot, so I'll see if it gets listed in NVRam (crossing my fingers :) ).

No, crossing fingers and boot-repair were not successful, no boot option in NVRam.
Well, it certainly looks to have been a successful operation, at least in getting the required boot loader files installed into the /dev/sda1 EFI System Partition. It now reports finding them there where it said it couldn't in the previous report. The only remaining issue is persuading your system's EUFI set-up to find the Grub boot loader (/EFI/ubuntu/shimx64.efi) and add it into its NVRAM boot order. That may take some persistence just as it did at first persuading it to let you boot the installation media in UEFI mode. Unfortunately, the Samsung user manual is not very helpful.
fabien85
Level 7
Level 7
Posts: 1877
Joined: Tue Mar 11, 2014 4:30 pm

Re: Mint install on Samsung NP905S3G fails to boot

Post by fabien85 »

You have all the correct EFI files on the EFI partition.
At the end of the boot-repair, the correct boot entry has been told to be written to the NVRAM :

Code: Select all

Boot0000* ubuntu	HD(1,GPT,b0852108-c891-4020-9023-8f546f48a95d,0x800,0x216800)/File(EFIubuntushimx64.efi)
line 888 of your boot-repair report.
(In details, this entry mean : boot the file EFI/ubuntu/shimx64.efi on the partition with PARTUUID=b0852108-c891-4020-9023-8f546f48a95d on the first GPT hard drive. If you look e.g. at line 582 you will see that this partuuid indeed corresponds to the EFI partition /dev/sda1. So all is correct)

efibootmgr is the Linux utility to manipulate NVRAM boot entries.

If it's not working, it's probably a problem of a buggy firmware that does not want to communicate correctly with efibootmgr.
Indeed before the boot-repair, the NVRAM contained the following entry :

Code: Select all

Boot0000* ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
(see e.g. line 860)
This is a weird entry. It looks like it was created by the Mint installer be cause of the "ubuntu" name (for technical reasons, Mint piggybacks on Ubuntu's bootloader), but the content does not make sense to me. My intuition is that the entry was correctly created by the Mint installer, but after reboot the firmware completely mixed up the content of the entry.
Also this entry was already present in your previous boot-info report

My intuition is that if you run sudo efibootmgr -v from a live USB, you will again find that there is an entry with name "ubuntu" but whose content does not make sense.

On top of that, you have a fallback bootloader at the fallback location /EFI/BOOT/bootx64.efi.
So normally when your firmware does not find a valid boot entry, it should default to that fallback bootloader, which should boot you to Mint.
The fact that this does not happen makes me think that your firmware has yet another bug.

I would try the following, in order of despair :
- go into the firmware interface/BIOS and look whether you find a utility to define a boot entry manually.
It may be called "create a boot entry" or "select a UEFI file as trusted for executing" or something else.
It's not mandatory you have such utility, and if you have one it's unfortunately also possible that it's buggy. (e.g. on my computer there is such utility, but it only works if the bootloader is at the root of the EFI partition, not in a folder)
- look for a "BIOS update" for your machine
if there is one, then comes the question of how to apply it. It may be that samsung only makes them for windows, in which case you are stuck. But now most manufacturer make available a flash utility from the firmware itself. You would need to download the update and put it on a USB stick, then point the flash utility to the file.
- delete all NVRAM boot entries and see if the machine defaults to booting Mint
I suggest this only because you seem persistent and unafraid of command line.
From a live USB, you would use efibootmgr. I suggest reading the manual first (man efibootmgr). Use -v to list the current entries and their details. Then for exemple to delete entry Boot0001 you would do sudo efibootmgr -b 1 -B
- if all else fails and unless someone suggests something else, you could install an EFI shell and use the bcfg command. Tell me if you want the details. I hope we dont get to this.
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

I still think somewhere must be a solution to this problem. I still have a few ideas that I will test the next few days.
Giving up is just not my way to deal with problems. As soon I have new info I will come back.
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
User avatar
w23
Level 1
Level 1
Posts: 30
Joined: Sun Jun 14, 2020 12:47 pm
Location: Germany

Re: Mint install on Samsung NP905S3G fails to boot

Post by w23 »

OK, I haven't managed to get a bios update yet, so that I can change the uefi settings, because Samsung won't support that anymore.

At the moment, I have a workaround I think it may work, but I need some help to do it.

Booting from USB stick does work, also in UEFI mode, so I want to create a boot stick that does nothing else than booting the installed linux system mint.

Even though this is a workaround at the moment, it may also be a future security feature (no usb stick, no booting system).

What do I have to do for the usb stick and how large must it be?

The usb stick sizes I have available at this time are 4gb, 32gb, 64gb.

Which one is neccessary for just booting off usb to boot laptop ssd with installed mint linux?
Samsung NP9[1/0]5S3G-Laptops-AMD 4x CPU 1GHz, Win10 Pro + Mint
Dell Mini 1010 Laptop Intel Atom N270 CPU @ 1.6 GHz 32bt Mint + Kali + Win10 Pro
N100, Win11 Pro + Mint
S500+, Win11 Pro + Mint
fabien85
Level 7
Level 7
Posts: 1877
Joined: Tue Mar 11, 2014 4:30 pm

Re: Mint install on Samsung NP905S3G fails to boot

Post by fabien85 »

I would say to make a refind USB stick :
- go here : http://www.rodsbooks.com/refind/getting.html
- download "A USB flash drive image file"
- follow the instructions in the "Tip" on the same page to install to the USB stick
Pay attention to adapt the device name. The page uses sdd1 as an example, yours may be sdb1 or sdc1 depending on how many drives you have. Use gparted to find out.

I think 200 MB should be enough. So you can make other partitions on that USB stick and use it for other stuff.
Locked

Return to “Installation & Boot”