I am seeking to Dual Boot a DELL Latitude laptop. I know one needs to load Win 11 first so that the installation of Linux with GRUB can sort out the boot loader. (Windows over writes it - typical MS take everything over and do it their way!!). I installed Win 11 pro 25H2 on to the laptop with a single user who is an administrator on the Windows device. It was a stripped down Windows install using an unattended.xml file in the USB. I then shrunk the 1Tb SSD disk. Disk 100Mb then C: OS partition of 442G. An unallocated partition of 488 Gb for Linux. Finally a 650Mb recovery partition. Using latest Rufus and latest Linux Mint created an Installation USB (I ensured the stick was GPT aka UEFI capablity). One time boot select the Linux install on the USB. Get a small message in the upper LH corner. Hard to read before it disappears but appears to say No Image found and some thing about a mok manager? Maybe using Rufus and the latest ISO image I did something wrong? I have installed Linux on its own on to a DELL laptop but I thought I would have a Dual Boot laptop. While I explore using Linux and say Libre Office instead of Copilot! Office 365!!! Any suggestions on what I may be doing wrong. I did try with the USB stick using MBR the first time but as the Windows is UEFI no-legacy aka GPT I tried that.
Need help with setting up Dual Boot Latitude laptop Windows & Linux Mint
- Thread starter grahamm7
- Start date
Hello there!!!
If you're encountering a "no image found" issue during a Linux Mint dual-boot installation on a Dell device, it's likely due to BIOS/UEFI settings or drive configuration. Here’s how to address it:
If you're encountering a "no image found" issue during a Linux Mint dual-boot installation on a Dell device, it's likely due to BIOS/UEFI settings or drive configuration. Here’s how to address it:
- Check Boot Mode Consistency: Ensure both Windows and Linux are installed in the same mode (UEFI or Legacy BIOS). Mismatched modes (e.g., Windows on UEFI, Linux on Legacy) can prevent detection. Use sudo efibootmgr -v from a live Linux terminal to check boot entries. If you see ubuntu or grubx64.efi, you're likely in UEFI mode.
- Verify Drive Visibility: Run sudo lsblk from the Linux Mint live environment. If your SSD isn’t listed, the issue may be with the drive’s controller mode. Dell laptops often ship with IRST/Intel RAID enabled, which can prevent Linux from detecting the drive. Switch the drive mode to AHCI in BIOS/UEFI (under "SATA Operation" or similar). Note: Changing this may require reinstalling Windows afterward.
- Disable Fast Boot and Secure Boot: In BIOS/UEFI, disable Fast Boot and Secure Boot. Fast Boot can prevent the installer from detecting the boot device, and Secure Boot may interfere with the boot process.
- Use Correct Installation Media: Re-create the bootable USB using tools like Rufus (in DD mode) or Balena Etcher, ensuring the ISO is written correctly. Some Dell systems require a Legacy boot option—press F12 at boot to access the boot menu and select "Legacy" if available.
- Use Boot Repair Tool: If the system boots but fails to detect Windows during installation, use the Boot Repair tool from the live environment to fix GRUB and restore dual-boot functionality.
Condobloke
Well-Known Member
Which leads me to another possible solution.
Have you considered installing windows and Linux on separate drives ?
Thanks guys. Let me set out what I have done. This is a DELL latitude with only ONE disk M2 SSD etc. I had already used the laptop for Windows 11. Now for the adventure of DUAL boot. I used WINPE/diskpart and cleaned the internal disk and convert GPT. So new disk. Created a Win 11 install from Windows 11 iso with latest rufus. Installed this first so that Windows wouldn't overide the GRUB linux operation. Then created a Linux install from the latest Linux mint with Cinamon interface using Rufus. This gives the image not found and some manger error? Hard to read small. I tried with an MBR and GPT format on the USB. Should be GPT as the BIOS is set to NON-legacy and UEFI. I have now used Etcher. Downloaded a fresh copy of Linux from the Kent server in UK (I am in UK). I tried checkin the hash using certil and with powershell:
PowerShell 7.5.4
PS C:\Windows\System32> Get-FileHash "C:\ISO\linuxmint-22.3-cinnamon-64bit.iso" -Algorithm MD5
Algorithm Hash Path
--------- ---- ----
MD5 093F418E6765D2CB34039699EF22FBFF C:\ISO\linuxmint-22.3-cinnamon-…
Nothing like what is given on Linux site
Linux Mint MD5
a081ab202cfda17f6924128dbd2de8b63518ac0531bcfe3f1a1b88097c459bd4 *linuxmint-22.3-cinnamon-64bit.iso ??
Anyway I have tried another way using Etcher. Created a new USB linux install. It says it created and verified ok.
Then tried to install Linux on the laptop with Win 11 already installed. Says Headless Operation Active !!
Then ignores the USB not shown in boot options and loads Windows 11.
I have been in the BIOS and tried to set everything I think it should need.
I can't use a second disk haven't got one. The disk is divided into 2 partitions First contains Win 11 OS (C
the second is blank ready for Linux - hopefully?
I have build plenty of Windows 7; 10; 11; from ISO installs where I work in a hospice as an IT volunteer. I have fought MS and wrestled with all the BIOS stuff on DELL, HP etc.. Maybe there is some setting on the DELL BIOS that I need to change. But these days the BIOS especially on DELL have so many settings.
Any ideas why I am running into these problems. When I was working I was a Solaris UNIX engineer. I like UNIX not very keen on Microsoft Windows as an OS. Long live UNIX/linux etc..
Thanks
PowerShell 7.5.4
PS C:\Windows\System32> Get-FileHash "C:\ISO\linuxmint-22.3-cinnamon-64bit.iso" -Algorithm MD5
Algorithm Hash Path
--------- ---- ----
MD5 093F418E6765D2CB34039699EF22FBFF C:\ISO\linuxmint-22.3-cinnamon-…
Nothing like what is given on Linux site
Linux Mint MD5
a081ab202cfda17f6924128dbd2de8b63518ac0531bcfe3f1a1b88097c459bd4 *linuxmint-22.3-cinnamon-64bit.iso ??
Anyway I have tried another way using Etcher. Created a new USB linux install. It says it created and verified ok.
Then tried to install Linux on the laptop with Win 11 already installed. Says Headless Operation Active !!
Then ignores the USB not shown in boot options and loads Windows 11.
I have been in the BIOS and tried to set everything I think it should need.
I can't use a second disk haven't got one. The disk is divided into 2 partitions First contains Win 11 OS (C
the second is blank ready for Linux - hopefully?I have build plenty of Windows 7; 10; 11; from ISO installs where I work in a hospice as an IT volunteer. I have fought MS and wrestled with all the BIOS stuff on DELL, HP etc.. Maybe there is some setting on the DELL BIOS that I need to change. But these days the BIOS especially on DELL have so many settings.
Any ideas why I am running into these problems. When I was working I was a Solaris UNIX engineer. I like UNIX not very keen on Microsoft Windows as an OS. Long live UNIX/linux etc..
Thanks
I use university of Kent for my downloads as well, never had a problem with downloads from them,
OK so did you go through my checklist????? When you install/re-install or make some updates to Win 10/11 they will automatically enable secure boot and quick start/fast boot, these will need to be disabled again and a full power re-boot done before you insert the ISO [do not use windows re-start]
This post is coming to you from my dell Latitude 5490 with NVMe and 16gb ram and Mint LMDE7 downloaded from UOK, the following may interest you
Brickwizard [a Kentish man in exile]
OK so did you go through my checklist????? When you install/re-install or make some updates to Win 10/11 they will automatically enable secure boot and quick start/fast boot, these will need to be disabled again and a full power re-boot done before you insert the ISO [do not use windows re-start]
This post is coming to you from my dell Latitude 5490 with NVMe and 16gb ram and Mint LMDE7 downloaded from UOK, the following may interest you
Brickwizard [a Kentish man in exile]
Last edited:
Condobloke
Well-Known Member
It is impossible to know what changes etc you have made in BIOS. So, set it to default, + uefi, disable secure boot and fastboot, and leave the rest alone.
Try again, taking note of @Brickwizard's advice above re usb ports
I have disabled Secure Boot in the Latitude BIOS. Can't see any Fast Boot to disable. But there sure is a lot of BIOS setting these days on Intel PC/Laptops. The disk is an M.2 SSD pretty new. I also turned off SATA settings and just left the M2.SSD stuff. You talk about a hidden sector on the disk. Not sure where that is. The Disk was partitioned: |100Mb EFI| c: OS 488Gb| Recover|| new spare partition 488Gb|. I kept getting Headless State Active. This just means it goes on past errors. Turned this on. But now it won't even boot up the Windows. Reinstalling windows. Happy to start again with a blank disk. Ok so I need Secure Boot OFF when I install the Linux Mint. Also I can turn off TPM chip. Not sure Windows will be happy about after Dual Boot? I would be happy to start again - BLANK SDD. Install Windows. I am trying to keep up with all the steps as Install Linux Mint so that the GRUB will give me the Dual Boot.
1. Turn OFF fast boot IN Win 11 once installed
2. Secure Boot OFF (but still UEFI)
3. TPM chip off before installing Linux
4. Do a FULL boot up from Power OFF to clear CMOS.
Happy to use Rufus to create Linux ISO install or Etcher. Ventoy but it gave a ZIP with 3 ,exe install files???
Any thing I have missed?
I will keep trying till I get a Dual Boot Latitude laptop Windows & Linux Mint.l
Thanks for all you helpful Linux guys and advice. There's a lot of settings particularly aka the BIOS
Confused of Chelmsford UK
1. Turn OFF fast boot IN Win 11 once installed
2. Secure Boot OFF (but still UEFI)
3. TPM chip off before installing Linux
4. Do a FULL boot up from Power OFF to clear CMOS.
Happy to use Rufus to create Linux ISO install or Etcher. Ventoy but it gave a ZIP with 3 ,exe install files???
Any thing I have missed?
I will keep trying till I get a Dual Boot Latitude laptop Windows & Linux Mint.l
Thanks for all you helpful Linux guys and advice. There's a lot of settings particularly aka the BIOS
Confused of Chelmsford UK
What model number and CPU
I have re-installed Windows 11. Using Windows - turned OFF Fast Boot. In BIOS turned OFF TPM. Turned OFF Secure Boot.
Created Linux Mint install using rufus (it used MBR by default). Then from cold rebooted and use One time Boot. It say the USB but failed said something was missing something like mx64.efi. As the BIOS is set to UEFI surely the USB should be using GPT?? That might be the trouble. The DELL laptop is Latitude 5400 CPU Intel i&-8665U I fitted a new SSD Samsung PC1e NVMe 1Tb. Maybe I should use Etcher it doesn't use options. Or Ventoy but that is ZIP with 3 .exe installs?? I will get there in the end. In my volunteer role at Hospice have fought MS and BIOS settings for Win 7;10 and now 11 25h2. So much of the MS DELL/BIOS is making it tricky to dual-boot.
Created Linux Mint install using rufus (it used MBR by default). Then from cold rebooted and use One time Boot. It say the USB but failed said something was missing something like mx64.efi. As the BIOS is set to UEFI surely the USB should be using GPT?? That might be the trouble. The DELL laptop is Latitude 5400 CPU Intel i&-8665U I fitted a new SSD Samsung PC1e NVMe 1Tb. Maybe I should use Etcher it doesn't use options. Or Ventoy but that is ZIP with 3 .exe installs?? I will get there in the end. In my volunteer role at Hospice have fought MS and BIOS settings for Win 7;10 and now 11 25h2. So much of the MS DELL/BIOS is making it tricky to dual-boot.
Your laptop is mechanically the same as mine follow both my pre-mentiond post on how I set it up [post 6 above] If yourd dosnt have the primary usb port on the back ue the one on the left of the keyboard
Code:
brian@Deep-Thought:~$ inxi -Fnxz
System:
Kernel: 6.12.69+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
Desktop: Cinnamon v: 6.6.7 Distro: LMDE 7 Gigi base: Debian 13.0 trixie
Machine:
Type: Laptop System: Dell product: Latitude 5490 v: N/A
serial: <superuser required>
Mobo: Dell model: 08NJ82 v: A00 serial: <superuser required> UEFI: Dell
v: 1.35.0 date: 04/02/2024
Battery:
ID-1: BAT0 charge: 44.1 Wh (73.5%) condition: 60.0/68.0 Wh (88.3%)
volts: 7.8 min: 7.6 model: SMP DELL GD1P653 status: discharging
CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP
arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 700 min/max: 400/3400 cores: 1: 700 2: 700 3: 700 4: 700
5: 700 6: 700 7: 700 8: 700 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel
arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
bus-ID: 1-5:3
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 1366x768~60Hz
API: EGL v: 1.5 drivers: iris,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
API: Vulkan v: 1.4.309 drivers: intel,llvmpipe surfaces: xcb,xlib
devices: 2
Info: Tools: api: eglinfo, glxinfo, vulkaninfo x11: xdriinfo, xdpyinfo,
xprop, xrandr
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3
API: ALSA v: k6.12.69+deb13-amd64 status: kernel-api
Server-1: PipeWire v: 1.4.2 status: active
Network:
Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6
IF: enp0s31f6 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
bus-ID: 02:00.0
IF: wlp2s0 state: up mac: <filter>
Drives:
Local Storage: total: 252.99 GiB used: 198.27 GiB (78.4%)
ID-1: /dev/mmcblk0 vendor: SanDisk model: SD16G size: 14.52 GiB
type: Removable
ID-2: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNV256G KIOXIA
size: 238.47 GiB temp: 30.9 C
Partition:
ID-1: / size: 225.33 GiB used: 183.82 GiB (81.6%) fs: ext4
dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 285.4 MiB used: 4.4 MiB (1.5%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 8.2 GiB used: 0 KiB (0.0%)
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 50.0 C mobo: 35.0 C
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 16 GiB available: 15.48 GiB used: 2.54 GiB (16.4%)
Processes: 292 Uptime: 3m Init: systemd
Packages: 2737 Compilers: gcc: 14.2.0 Shell: Bash v: 5.2.37 inxi: 3.3.38
brian@Deep-Thought:~$
Last edited:
Graham, your machine was designed to use either windows or Ubuntu as standard, I have been poking around the dell documentation and this is what they recommend
This article does not apply to Alienware 16 Aurora AC16250
Check out other resources
BIOS must be updated or is unable to boot using RAID On mode for Serial ATA (SATA) Operation.
Linux does not natively support SATA Operation in RAID On mode as of May 2022.
To apply the recommended BIOS settings to your Dell computer with a Linux operating system, do the following:
This article does not apply to Alienware 16 Aurora AC16250
Check out other resources
Symptoms
BIOS must be updated or is unable to boot using RAID On mode for Serial ATA (SATA) Operation.
Cause
Linux does not natively support SATA Operation in RAID On mode as of May 2022.
Resolution
To apply the recommended BIOS settings to your Dell computer with a Linux operating system, do the following:
- Power off the computer.
- Power the computer on and quickly press the F2 button until you see the BIOS setting menu.
- Under the General section, Boot Sequence, check that the dot is selected for Unified Extensible Firmware Interface (UEFI).
- Under the System Configuration section, SATA Operation, check that the dot is selected for Advanced Host Controller Interface (AHCI).
- Under the Secure Boot section, Secure Boot Enable, check that the dot is selected for Disabled.
- Click the Apply button on the bottom-right and then the Exit button.
- copyrite dell computers
I Decided to just install Linux Mint which I have done before on a DELL laptop. I made an ISO install USB for Linux. I cleaned the existing disk in the laptop using Diskpart and CLEAN. However when I try to install it crashes out with a message about a missing file something like /EFI/efi.*** in the top LH corner where the GRUB dual boot info appears. I have tried redoing the USB with RUFUS. I did try to check the ISO using MD5 or a HASH exe. But the very long MD5 value on the LINUX mint ISO page doesn't match with the MD5 compute of it (much shorter). Maybe someone can explain how to do the check with MD5 or a HASH program on my Windows 11 machine so I can check that the ISO on the USB is OK. I tried install Windows 11 on the now blank disk and it fails with the failed to find message!! So there is something wrong with the USB/ISO OR there is something wrong with the BIOS settings on the laptop now?? Sorry to be a pain. I am an ex IT engineer but I don't know my way totally around BIOS/formats etc... To understand ISO installs particularly of Linux. I have done loads of Windows 7/10/11 installs on desktops and laptops.
PowerShell MD5:
Get-FileHash C:\path\to\file.iso -Algorithm MD5
PowerShell SHA256:
Get-FileHash C:\path\to\file.iso -Algorithm SHA256
CertUtil MD5:
certutil -hashfile C:\path\to\file.iso MD5
CertUtil SHA256:
certutil -hashfile C:\path\to\file.iso SHA256
If you computer boots Win 10 or 11. It supports UEFI, and is likely in UEFI mode.
Also it supports secure boot, and is likely in secure boot mode.
CaffeineAddict
Well-Known Member
The OP already known about PS command based on his post #5 that was 1.5 months ago but it looks like he confuses MD5 with some other algorithm from mint download site.
@grahamm7
You should provide us link to where you download ISO from, and give us edition that you download.
edit:
I just check mint site and they don't provide MD5 sums, so there you go.
Good point.
"Worth noting — MD5 has known cryptographic weaknesses and is no longer considered secure. It's vulnerable to collision attacks, meaning a malicious actor could theoretically substitute a file that produces the same checksum. Some distros still publish MD5 checksums, which is why I've included it here, but SHA-256 is strongly preferred."
I download Linux Mint from:https://www.linuxmint.com/download.php
So how do I check its valitidy there are CheckSums given:
Linux Mint Checksums
a081ab202cfda17f6924128dbd2de8b63518ac0531bcfe3f1a1b88097c459bd4 *linuxmint-22.3-cinnamon-64bit.iso
What tool to check these Checksums (I thought MD5 was for this) on my Windows 11 machine to check ISO.
When ever I try to boot from USB with the Linux ISO I get a message in top LH corner (where GRUB dual boot message appears)
and says it can't find an EFI file - too small to read and but something like /EFI/efi.***. I have been through the DELL 5400 BIOS and ensured Secure BOOT off minimal Fast BOOT disk set to ACHD. I tried then cleaned the Disk on the laptop and tried installing Windows from Win 11 iso but still same message. I then took out ALL boot loaders including NIC put in the original Windows 10 ISO and it has installed Win 10 OK from the USB stick. I then asked it to install Linux Mint from ISO USB and I again get the msg in TOP RH corner saying it can't find a file???? I am pretty used to changing BOOT settings I do it at the charity I work when installing Windows 7/10 and now 11 24H2 on our machines when required. Never met this BOOT message before an nobody seems to know what it means. I am using RUFUS but have used Enable. There must be some setting in the BIOS or in constructing an ISO install for either Windows 11 or Linux Mint. Maybe I will ask the author of RUFUS he often will answer these questions. But I hoped somebody on Linux Forum might have met this message in top LH corner and give me an answer to fix it in the BIOS or USB installation format..
So how do I check its valitidy there are CheckSums given:
Linux Mint Checksums
a081ab202cfda17f6924128dbd2de8b63518ac0531bcfe3f1a1b88097c459bd4 *linuxmint-22.3-cinnamon-64bit.iso
What tool to check these Checksums (I thought MD5 was for this) on my Windows 11 machine to check ISO.
When ever I try to boot from USB with the Linux ISO I get a message in top LH corner (where GRUB dual boot message appears)
and says it can't find an EFI file - too small to read and but something like /EFI/efi.***. I have been through the DELL 5400 BIOS and ensured Secure BOOT off minimal Fast BOOT disk set to ACHD. I tried then cleaned the Disk on the laptop and tried installing Windows from Win 11 iso but still same message. I then took out ALL boot loaders including NIC put in the original Windows 10 ISO and it has installed Win 10 OK from the USB stick. I then asked it to install Linux Mint from ISO USB and I again get the msg in TOP RH corner saying it can't find a file???? I am pretty used to changing BOOT settings I do it at the charity I work when installing Windows 7/10 and now 11 24H2 on our machines when required. Never met this BOOT message before an nobody seems to know what it means. I am using RUFUS but have used Enable. There must be some setting in the BIOS or in constructing an ISO install for either Windows 11 or Linux Mint. Maybe I will ask the author of RUFUS he often will answer these questions. But I hoped somebody on Linux Forum might have met this message in top LH corner and give me an answer to fix it in the BIOS or USB installation format..
This is actually a common message. Seen it many times. But there is a gotcha here.
I myself don't use Mint, so I don't know how it sets up it's default file system layout.
This gets a little complicaed/technical, so I just explain it as I know how. This is my home system layout.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p3 236G 40G 196G 17% /
devtmpfs 3.3G 0 3.3G 0% /dev
tmpfs 3.4G 12K 3.4G 1% /dev/shm
efivarfs 128K 50K 74K 40% /sys/firmware/efi/efivars
tmpfs 1.4G 1.9M 1.4G 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
/dev/nvme0n1p3 236G 40G 196G 17% /home
tmpfs 3.4G 8.0M 3.4G 1% /tmp
/dev/nvme0n1p2 2.0G 424M 1.4G 24% /boot
/dev/nvme0n1p1 599M 20M 580M 4% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 686M 15M 672M 3% /run/user/1000
Notice: have a partition here --
/dev/nvme0n1p1 599M 20M 580M 4% /boot/efi
I would say "most" (but not all) distro's need this /boot/efi partition.
It has a lot of stuff here, but it's not the same for every distro.
/boot/efi# tree
.
├── EFI
│ ├── BOOT
│ │ ├── BOOTIA32.EFI
│ │ ├── BOOTX64.EFI
│ │ ├── fbia32.efi
│ │ └── fbx64.efi
│ └── fedora
│ ├── BOOTIA32.CSV
│ ├── BOOTX64.CSV
│ ├── gcdia32.efi
│ ├── gcdx64.efi
│ ├── grub.cfg
│ ├── grubia32.efi
│ ├── grubx64.efi
│ ├── mmia32.efi
│ ├── mmx64.efi
│ ├── shim.efi
│ ├── shimia32.efi
│ └── shimx64.efi
├── mach_kernel
└── System
└── Library
└── CoreServices
└── SystemVersion.plist
7 directories, 18 files
These are little mini boot kernels, these are the first files your system uses to boot up in EFI mode.
Those directories could be missing for some reason, or the files beneath them could be missing.
One of the reasons we asked to do a checksum, was to make sure you have the complere iso, and some
of it didnt get downloaded or corrupted.
I myself don't use Mint, so I don't know how it sets up it's default file system layout.
This gets a little complicaed/technical, so I just explain it as I know how. This is my home system layout.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p3 236G 40G 196G 17% /
devtmpfs 3.3G 0 3.3G 0% /dev
tmpfs 3.4G 12K 3.4G 1% /dev/shm
efivarfs 128K 50K 74K 40% /sys/firmware/efi/efivars
tmpfs 1.4G 1.9M 1.4G 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
/dev/nvme0n1p3 236G 40G 196G 17% /home
tmpfs 3.4G 8.0M 3.4G 1% /tmp
/dev/nvme0n1p2 2.0G 424M 1.4G 24% /boot
/dev/nvme0n1p1 599M 20M 580M 4% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 686M 15M 672M 3% /run/user/1000
Notice: have a partition here --
/dev/nvme0n1p1 599M 20M 580M 4% /boot/efi
I would say "most" (but not all) distro's need this /boot/efi partition.
It has a lot of stuff here, but it's not the same for every distro.
/boot/efi# tree
.
├── EFI
│ ├── BOOT
│ │ ├── BOOTIA32.EFI
│ │ ├── BOOTX64.EFI
│ │ ├── fbia32.efi
│ │ └── fbx64.efi
│ └── fedora
│ ├── BOOTIA32.CSV
│ ├── BOOTX64.CSV
│ ├── gcdia32.efi
│ ├── gcdx64.efi
│ ├── grub.cfg
│ ├── grubia32.efi
│ ├── grubx64.efi
│ ├── mmia32.efi
│ ├── mmx64.efi
│ ├── shim.efi
│ ├── shimia32.efi
│ └── shimx64.efi
├── mach_kernel
└── System
└── Library
└── CoreServices
└── SystemVersion.plist
7 directories, 18 files
These are little mini boot kernels, these are the first files your system uses to boot up in EFI mode.
Those directories could be missing for some reason, or the files beneath them could be missing.
One of the reasons we asked to do a checksum, was to make sure you have the complere iso, and some
of it didnt get downloaded or corrupted.
CaffeineAddict
Well-Known Member
Run this (update path to downloaded ISO as needed) :
C#:
(Get-FileHash "C:\ISO\linuxmint-22.3-cinnamon-64bit.iso" -Algorithm SHA256).Hash -eq "a081ab202cfda17f6924128dbd2de8b63518ac0531bcfe3f1a1b88097c459bd4"If the output is "True" the ISO is fine, if it's "False" it's not good.
I suspect this is due to TPM, go to BIOS and disable TPM in addition to disabling secure boot.
If there's option to disable it.
To create bootable USB with rufus you need to use options
dd when starting rufus and later UEFI + GPT when formatting.don't have rufus to test but this are 2 option you need to make sure you use.
Last edited:
I just checked my debian system, and it is similar.
Debian13:~# tree /boot/efi
/boot/efi
└── EFI
├── BOOT
│ ├── BOOTX64.EFI
│ ├── fbx64.efi
│ ├── grubx64.efi
│ └── mmx64.efi
└── debian
├── BOOTX64.CSV
├── fbx64.efi
├── grub.cfg
├── grubx64.efi
├── mmx64.efi
└── shimx64.efi
4 directories, 10 files
root@Debian13:~#
Debian13:~# tree /boot/efi
/boot/efi
└── EFI
├── BOOT
│ ├── BOOTX64.EFI
│ ├── fbx64.efi
│ ├── grubx64.efi
│ └── mmx64.efi
└── debian
├── BOOTX64.CSV
├── fbx64.efi
├── grub.cfg
├── grubx64.efi
├── mmx64.efi
└── shimx64.efi
4 directories, 10 files
root@Debian13:~#
Similar threads
