Welcome!
Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.3.1 release info here

New users[/u
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Could not open \EFI\BOOT\fallback.efi": 14 [SOLVED]

User avatar
j2mcgreg
Forum Regular
Forum Regular
Posts: 462
Joined: Tue Oct 23, 2007 12:04 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#31

Post by j2mcgreg » Thu Jan 24, 2019 12:58 pm

yes
Acer Aspire 3 A315-41-R2W5, AMD Ryzen 5 2500U, Radeon Vega Mobile Graphics, 8 GB ram, 1000 TB hdd

User avatar
Sparky
Forum Regular
Forum Regular
Posts: 131
Joined: Sun Dec 23, 2018 7:07 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#32

Post by Sparky » Thu Jan 24, 2019 2:35 pm

fehlix wrote:
Thu Jan 24, 2019 11:25 am
Sparky wrote:
Thu Jan 24, 2019 3:26 am
I tried it, I got the frozen cursor. I think this machine has a problem with Debian, it works on Ubuntu distros. Very strange.
Would you mind to show some system info from this laptop,
when you booted from Ubuntu or Mint:
like

Code: Select all

inxi -Fxz

Code: Select all

lsblk -f

Code: Select all

sudo fdisk -l
We will need to fix this grub. I'll do some excersises to see whether I can provide a workarround. stay tuned ... :turtle:
ok, from Linux Mint Live USB, here are the results:

Code: Select all

inxi-FXZ
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

mint@mint:~$ inxi -Fxz
System:
  Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc 
  v: 7.3.0 Desktop: Cinnamon 4.0.8 Distro: Linux Mint 19.1 Tessa 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: Jumper product: EZbook v: N/A serial: <filter> 
  Mobo: Jumper model: EZbook serial: <filter> UEFI: American Megatrends 
  v: Jumper10x.P8.WP3132.NHNAUHL02 date: 02/01/2018 
Battery:
  ID-1: BAT0 charge: 31.7 Wh condition: 36.5/36.5 Wh (100%) 
  model: Intel SR 1 SR Real Battery status: Discharging 
CPU:
  Topology: Quad Core model: Intel Celeron N3450 bits: 64 type: MCP 
  arch: Goldmont rev: 9 L2 cache: 1024 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
  Speed: 790 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 796 2: 796 
  3: 796 4: 796 
Graphics:
  Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6) 
  v: 4.5 Mesa 18.0.5 direct render: Yes 
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster vendor: Realtek driver: snd_hda_intel v: kernel bus ID: 00:0e.0 
  Sound Server: ALSA v: k4.15.0-20-generic 
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: f040 
  bus ID: 01:00.0 
  IF: wlp1s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 191.92 GiB used: 37.38 GiB (19.5%) 
  ID-1: /dev/mmcblk1 model: DF4064 size: 58.24 GiB 
  ID-2: /dev/sda model: NT-128 size: 119.24 GiB temp: 33 C 
  ID-3: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 
  size: 14.44 GiB 
Partition:
  ID-1: / size: 2.84 GiB used: 81.4 MiB (2.8%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 216 Uptime: 4m Memory: 5.67 GiB used: 850.5 MiB (14.6%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 Shell: bash v: 4.4.19 
  inxi: 3.0.27 

Code: Select all

mint@mint:~$ System:
System:: command not found
mint@mint:~$   Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc 
Host:: command not found
mint@mint:~$   v: 7.3.0 Desktop: Cinnamon 4.0.8 Distro: Linux Mint 19.1 Tessa 
v:: command not found
mint@mint:~$   base: Ubuntu 18.04 bionic 

Command 'base:' not found, did you mean:

  command 'basez' from deb basez
  command 'basex' from deb basex

Try: sudo apt install <deb name>

mint@mint:~$ Machine:
Machine:: command not found
mint@mint:~$   Type: Laptop System: Jumper product: EZbook v: N/A serial: <filter> 
bash: syntax error near unexpected token `newline'
mint@mint:~$   Mobo: Jumper model: EZbook serial: <filter> UEFI: American Megatrends 
bash: filter: No such file or directory
mint@mint:~$   v: Jumper10x.P8.WP3132.NHNAUHL02 date: 02/01/2018 
v:: command not found
mint@mint:~$ Battery:
Battery:: command not found
mint@mint:~$   ID-1: BAT0 charge: 31.7 Wh condition: 36.5/36.5 Wh (100%) 
bash: syntax error near unexpected token `('
mint@mint:~$   model: Intel SR 1 SR Real Battery status: Discharging 
model:: command not found
mint@mint:~$ CPU:
CPU:: command not found
mint@mint:~$   Topology: Quad Core model: Intel Celeron N3450 bits: 64 type: MCP 
Topology:: command not found
mint@mint:~$   arch: Goldmont rev: 9 L

2nd commmand
mint@mint:~$ ]lsblk -f[

Command ']lsblk' not found, did you mean:

  command 'lsblk' from deb util-linux

Try: sudo apt install <deb name>

mint@mint:~$ clear

Code: Select all

mint@mint:~$ lsblk -f
NAME FSTYPE LABEL                UUID                                 MOUNTPOINT
loop0
     squash                                                           /rofs
sda                                                                   
├─sda1
│    vfat   SYSTEM               46C2-8827                            
├─sda2
│                                                                     
├─sda3
│    ntfs   Windows              B4F0C956F0C91F8A                     
└─sda4
     ntfs                        EABA987CBA9846CB                     
sdb  iso966 Linux Mint 19.1 Cinnamon 64-bit
│                                2018-12-17-14-00-47-00               /cdrom
├─sdb1
│    iso966 Linux Mint 19.1 Cinnamon 64-bit
│                                2018-12-17-14-00-47-00               
└─sdb2
     vfat   Linux Mint 19.1 Cinnamon 64-bit
                                 044E-AC17                            
mmcblk1
│                                                                     
├─mmcblk1p1
│    ntfs   New Volume           7C9C6FF99C6FABF8                     /media/min
├─mmcblk1p2
│                                                                     
├─mmcblk1p3
│    ntfs   Storage              9A062EAE062E8B79                     /media/min
└─mmcblk1p4
     ntfs   Recovery             7E16CA3A16C9F367                     
mmcblk1boot0
                                                                      
mmcblk1boot1
                                                                      
mint@mint:~$ 

3rd command
sdb  iso966 Linux Mint 19.1 Cinnamon 64-bit
│                                2018-12-17-14-00-47-00               /cdrom
├─sdb1
│    iso966 Linux Mint 19.1 Cinnamon 64-bit
│                                2018-12-17-14-00-47-00               
└─sdb2
     vfat   Linux Mint 19.1 Cinnamon 64-bit
                                 044E-AC17                            
mmcblk1
│                                                                     
├─mmcblk1p1
│    ntfs   New Volume           7C9C6FF99C6FABF8                     /media/min
├─mmcblk1p2
│                                                                     
├─mmcblk1p3
│    ntfs   Storage              9A062EAE062E8B79                     /media/min
└─mmcblk1p4
     ntfs   Recovery             7E16CA3A16C9F367                     
mmcblk1boot0
                                                                      
mmcblk1boot1
                                                                      
mint@mint:~$ clear

Code: Select all

mint@mint:~$ sudo fdisk -l
Disk /dev/loop0: 1.8 GiB, 1890041856 bytes, 3691488 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


Disk /dev/mmcblk1: 58.2 GiB, 62537072640 bytes, 122142720 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: 1138A656-226F-4892-A2E1-704D0927ADB8

Device             Start       End   Sectors  Size Type
/dev/mmcblk1p1      2048    204799    202752   99M Microsoft basic data
/dev/mmcblk1p2    206848    468991    262144  128M Microsoft reserved
/dev/mmcblk1p3    468992 121157631 120688640 57.6G Microsoft basic data
/dev/mmcblk1p4 121157632 122140671    983040  480M Windows recovery environment


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 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


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: 9A7AAC2B-6B1D-417C-8E20-2CA8AB33B83A

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    206847    204800   100M EFI System
/dev/sda2     206848    468991    262144   128M Microsoft reserved
/dev/sda3     468992 249056380 248587389 118.5G Microsoft basic data
/dev/sda4  249057280 250064895   1007616   492M Windows recovery environment


Disk /dev/sdb: 14.4 GiB, 15502147584 bytes, 30277632 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: dos
Disk identifier: 0x09bebfcf

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *          0 3855295 3855296  1.9G  0 Empty
/dev/sdb2       3843044 3847715    4672  2.3M ef EFI (FAT-12/16/32)
mint@mint:~$ 
hope this helps.
----
Mod note: Please wrap text output into code-tags : [code] text output goes here [/code]
Fixed it now.
MX-18 Dell 7559 16GB RAM GTX960 256GB SSD Sandisk & 256GB SSD Samsung 860 Evo

User avatar
BitJam
Forum Guide
Forum Guide
Posts: 2766
Joined: Sat Aug 22, 2009 11:36 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#33

Post by BitJam » Thu Jan 24, 2019 2:50 pm

Thanks Sparky! I Googled(linux EZbook uefi) and found this Fedora thread:[Solved] Installation on the laptop with UEFI. I have not studied it thoroughly but two things popped out. Someone said these machines will not boot with Grub (which we use). I'm not sure if that's true. I think the OP got it to work by putting REFInd on another stick and using that to boot their live-usb.
Will I cry when it's all over?
When I die will I see Heaven?

User avatar
Sparky
Forum Regular
Forum Regular
Posts: 131
Joined: Sun Dec 23, 2018 7:07 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#34

Post by Sparky » Thu Jan 24, 2019 3:02 pm

Thanks, I'll look into what REFInd is and how it works.
MX-18 Dell 7559 16GB RAM GTX960 256GB SSD Sandisk & 256GB SSD Samsung 860 Evo

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2929
Joined: Wed Apr 11, 2018 5:09 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#35

Post by fehlix » Thu Jan 24, 2019 3:31 pm

Sparky wrote:
Thu Jan 24, 2019 3:02 pm
Thanks, I'll look into what REFInd is and how it works.
Refind is a realy cool tool. not only for this situation.
Go and grab the USB-image of refind here:
https://www.rodsbooks.com/refind/getting.html
and get "A USB flash drive image file".
Downlod here:
http://sourceforge.net/projects/refind/ ... p/download

Unzip dd-dump usb-image to another usb-stick and boot from the stick.
keep your existing MX-linux stick also plugged in.
Refind will scan all available efi-booloader.
With some luck it will show you also the MX EFI boot loader.

It might not work, as we got already to the point where it loaded the
EFI-bootloader but still stuck with the blinking cursor.

I'm still checking the other alternative, which is
in short to re-use exsiting ubuntu/mints grub-efi-loader,
and replace our's with the one you have tested to work with from ubuntu/mint.
But try the rEFInd variant first.
--fehlix
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2929
Joined: Wed Apr 11, 2018 5:09 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#36

Post by fehlix » Thu Jan 24, 2019 4:42 pm

OK, here the workaround:
Let's re-use existing Ubunt/Mint EFI-loader for MX-Linux (as we know they are working on that laptop)

We could do this with Live-USB-Maker variant, but I have just tested it with the FAT32 variant with rufus installation.
We use two USB sticks and do install with rufus MX-Linux and Linux Mint on those two sticks.

Now on the MX-Linux stick:
- rename those folders and files:

rename /EFI to /EFI-MX

within the folder /boot/grub
rename efi.img to efi.img-MX
rename x86_64-efi to x86_64-efi-MX

Now we copy from Lnux Mint the Ubuntu EFI-loader to the MX-Lnux usb stick:

copy from LinuxMints-stick:
[MINT]/EFI to [MXlinux]/EFI
[MINT]/boot/grub/efi.img to [MXlinux]/boot/grub/efi.img
[MINT]/boot/grub/x86_64-efi to [MXlinux]/boot/grub/x86_64-efi

With this procedure, we have exatly the same EFI-Bootloader
from Ubunt as Linux Mint is using. And we know you have tested
that Ubunt's EFI-loader works.
So let's reboot now ;=)
Good luck.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
BitJam
Forum Guide
Forum Guide
Posts: 2766
Joined: Sat Aug 22, 2009 11:36 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#37

Post by BitJam » Thu Jan 24, 2019 10:46 pm

@Sparky (and anyone else interested): I've applied the fehlix fix to antiX-17.3.1_x64-base.iso. I would greatly appreciate it if you would download the iso file from: antiX-17.3.1b_x64-base and see if it fixes the problem for you. If so then we can start fixing the other iso files. The antiX-base iso is less than half the size of MX and it still took me two hours to upload.
Will I cry when it's all over?
When I die will I see Heaven?

User avatar
Sparky
Forum Regular
Forum Regular
Posts: 131
Joined: Sun Dec 23, 2018 7:07 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#38

Post by Sparky » Thu Jan 24, 2019 11:00 pm

BitJam wrote:
Thu Jan 24, 2019 10:46 pm
@Sparky (and anyone else interested): I've applied the fehlix fix to antiX-17.3.1_x64-base.iso. I would greatly appreciate it if you would download the iso file from: antiX-17.3.1b_x64-base and see if it fixes the problem for you. If so then we can start fixing the other iso files. The antiX-base iso is less than half the size of MX and it still took me two hours to upload.
Thank you!! Thwe entering two USB keys at once scared me a bit. Can we download it know?
MX-18 Dell 7559 16GB RAM GTX960 256GB SSD Sandisk & 256GB SSD Samsung 860 Evo

User avatar
Sparky
Forum Regular
Forum Regular
Posts: 131
Joined: Sun Dec 23, 2018 7:07 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#39

Post by Sparky » Thu Jan 24, 2019 11:02 pm

Is this for the XX Linux 18, not 17not??
MX-18 Dell 7559 16GB RAM GTX960 256GB SSD Sandisk & 256GB SSD Samsung 860 Evo

User avatar
BitJam
Forum Guide
Forum Guide
Posts: 2766
Joined: Sat Aug 22, 2009 11:36 pm

Re: Could not open \EFI\BOOT\fallback.efi": 14

#40

Post by BitJam » Thu Jan 24, 2019 11:14 pm

The download is ready now. There is also a .md5 file which you should check.

This is not for MX. It is for antiX-17.3.1_x64-base.iso. This is less than half the size of MX. If it boots for you then we can apply the fix to the MX iso files. This may seem out of the way for you but fixing all the iso files and uploading them all is a big task. We first want to verify the fix works for you with a smaller iso file before fixing and uploading all the others.
Will I cry when it's all over?
When I die will I see Heaven?

Post Reply

Return to “Installation”