LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-24-2020, 06:03 PM   #31
thirtySeven
LQ Newbie
 
Registered: Jun 2020
Posts: 24

Original Poster
Rep: Reputation: Disabled

@kevmccor

Code:
ls /boot/efi/EFI/Boot
returns: BOOTX64.EFI elilo.conf elilo.conf~ initrd.gz vmlinuz

Quote:
The elilo.conf file should be something like:
It looks exactly like you said it should.

Quote:
The "root=/dev/nvme0n1pX ro" needs the X to be the root partition number.
I have confirmed that I have this is this the case.

When I go to reboot I get an instant failure for the "slackware-boot" entry that was made using colorpurple21859's instructions.
 
Old 06-24-2020, 06:46 PM   #32
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
Quote:
I get an instant failure
explain in detail what happens.
Post your /boot/efi/EFI/Boot/elilo.conf

Last edited by colorpurple21859; 06-24-2020 at 06:48 PM.
 
Old 06-24-2020, 11:57 PM   #33
kevmccor
Member
 
Registered: Aug 2004
Location: Texas
Distribution: slackware
Posts: 110

Rep: Reputation: 27
I have had a lot of trouble with UEFI myself. Sometimes it is just a blank screen, sometimes the elilo screen just sits there, sometimes it says "vmlinuz loaded" (or something like that). I don't really know that much about it. There may be some sort of efi shell that must pass control over to the booting OS and there may be an efifb framebuffer that passes control over to the video card driver. If it is just a blank screen, with the computer making noises like something is happening, then the user can try typing their login, password, and "startx" which will then show the window manager screen. There may be requirements in the motherboard bios settings. Unfortunately, there may not be any way for the user to know what error is occurring because no log can be written.

Maybe the ReFind boot manager would be helpful. http://www.rodsbooks.com/refind/
 
Old 06-26-2020, 06:55 AM   #34
thirtySeven
LQ Newbie
 
Registered: Jun 2020
Posts: 24

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
explain in detail what happens.
Post your /boot/efi/EFI/Boot/elilo.conf
/boot/efi/EFI/Boot/elilo.conf:
Code:
chooser=simple
delay=1
timeout=1
#
image=vmlinuz
        label=vmlinuz
        initrd=initrd.gz
        read-only
        append="root=/dev/nvme0n1p2 vga=normal ro"

I should have tested that the boot entry would show up multiple times because
it was gone the next time I went to boot up. Here is a complete breakdown of
the situation.

I shut down my computer and load into BIOS. I have two boot options being the
usb and "NVMe: Samsung SSD 970 EVO Plus 500GB". If I select "NVME..." I get this error:
Code:
Boot Failed: Samsung SSd 970 EVO Plus 500GB. Press any key to continue
I then boot into my system using the usb. I run efibootmgr and see that the
two boot options listed above are the only two entries listed.

I then cd into /boot/efi/EFI/Boot/ and see that the four files that are
supposed to be there still are there (elilo.conf, elilo.efi, initrd.gz,
vmlinuz). I then remove them in preperation for my next attempt at making a
new boot entry.

Next I perform equivalent actions in /boot/efi/EFI/Slackware/.

I then run eliloconfig. Each time I have done this I have chosen the option to
create a boot menu entry.

Next I cd into /boot/efi/EFI/Slackware/ and see that the four files
mentioned earlier are all present.

I then go ahead and follow the instructions from colorpurple21859's earlier reply:
Quote:
Copy the /boot/efi/EFI/Slackware/elilo.efi to /boot/efi/EFI/Boot/bootx64.efi and the other files in EFI/Slackware to EFI/Boot.
Then register it to the efi firmware
After following these instructions I can see in efibootmgr that a new entry
has been created

I go to reboot and am able to select the new boot entry. When I select it I am
immediately shown:
Code:
Boot Failed: Slackware-boot. Press any key to continue
I boot back into my system from the usb and in efibootmgr I can still see the entry that
was created.

I go to reboot again and the entry is now not available from BIOS. I boot back
in with the usb and check efibootmgr and the entry is gone.

I cd into /boot/efi/EFI/Boot/ and can see the four files that are supposed to
be there.

Edit: I should have mentioned that I have attempted this three times and gotten the same result each time.

Last edited by thirtySeven; 06-26-2020 at 08:11 AM.
 
Old 06-26-2020, 09:41 AM   #35
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
Maybe your system is efi32 bit.
Copy the /boot/elilo32.efi to both the slackware and/or Boot directory on the efi partition register with efibootmanager.


If that doesn’t work see if grub will work
Code:
grub-install
grub-mkconfig -o /boot/grub/grub.cfg
If that doesn’t work, copy the /boot/efi/EFI/Slackware-14.2/grubx64.efi to /boot/efi/EFI/Boot/bootx32.efi and register to bios as before
You

Last edited by colorpurple21859; 06-26-2020 at 10:57 AM.
 
Old 06-26-2020, 11:08 AM   #36
thirtySeven
LQ Newbie
 
Registered: Jun 2020
Posts: 24

Original Poster
Rep: Reputation: Disabled
I had no luck using /boot/elilo32.efi. I couldn't get it registered with efibootmgr. efibootmgr continuously said that it could not find the file even though I was certainly providing the correct path and had followed prior steps accurately.

When I ran
Code:
grub-install
grub-mkconfig -o /boot/grub/grub.cfg
and then went to reboot I did not have any options besides the usb and the NVMe... selections.

Quote:
If that doesn’t work, copy the /boot/efi/EFI/Slackware-14.2/grubx64.efi to /boot/efi/EFI/Boot/bootx32.efi and register to bios as before
I was able to successfully follow these steps. When I go to boot, this entry shows up but immediately fails in an equivalent way to all the others. What is interesting though is that this boot entry is not going away. I have rebooted 7 times and it has shown up each time.

Edit: This is the output of grub-mkconfig -o /boot/grub/grub.cfg
Code:
bash-5.0# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-huge-5.4.47
Found initrd image: /boot/initrd.gz
Found linux image: /boot/vmlinuz-huge
Found initrd image: /boot/initrd.gz
Found linux image: /boot/vmlinuz-generic-5.4.47
Found initrd image: /boot/initrd.gz
Found linux image: /boot/vmlinuz-generic
Found initrd image: /boot/initrd.gz
Found ELILO Boot Manager on /dev/nvme0n1p1@/EFI/elilo.efi/elilo.efi
Found Slackware 14.2 x86_64 (post 14.2 -current) on /dev/nvme0n1p2
done

Last edited by thirtySeven; 06-26-2020 at 11:24 AM.
 
Old 06-26-2020, 12:07 PM   #37
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
Quote:
copy the /boot/efi/EFI/Slackware-14.2/grubx64.efi to /boot/efi/EFI/Boot/bootx32.efi
that was a typo should have been bootx64.efi
 
Old 06-26-2020, 12:16 PM   #38
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
Quote:
I had no luck using /boot/elilo32.efi. I couldn't get it registered with efibootmgr.
try this
Code:
grub-install --target=i386-efi

Last edited by colorpurple21859; 06-26-2020 at 12:18 PM.
 
Old 06-26-2020, 12:52 PM   #39
thirtySeven
LQ Newbie
 
Registered: Jun 2020
Posts: 24

Original Poster
Rep: Reputation: Disabled
I was able to successfully create a boot entry for /boot/elilo32.efi after running
Code:
grub-install --target=i386-efi
I was able to select the entry from BIOS but I got the usual boot failure.

Last edited by thirtySeven; 06-26-2020 at 12:53 PM.
 
Old 06-26-2020, 03:48 PM   #40
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
post the output of
Code:
efibootmgr -v
Post the directories and subdirecties of the efi directory on the boot usb

At the usb boot menu, press c for the grub prompt, post the output of the following
set pager=1
set
lsmod

Last edited by colorpurple21859; 06-26-2020 at 05:00 PM.
 
Old 06-26-2020, 04:07 PM   #41
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 650

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
There is a functional /boot/efi/EFI/Boot/elilo.conf from one of my boxes which uses UEFI DUET (similar with that EFI payload from CoreBoot) and running on top of a classic BIOS.
Code:
chooser = simple

prompt

delay = 50
timeout = 50

default = Linux

# Linux entry config begins
image = /EFI/Slackware/vmlinuz
    root = "UUID=9a83ce56-19db-4a1d-839c-5273ec4306c8"
    label = Linux
    append = "resume=UUID=76b7c1d7-c467-4a89-83a2-4bb4e8d1c9fd acpi_enforce_resources=lax scsi_mod.use_blk_mq=1 zswap.enabled=1 zswap.compressor=lzo zswap.max_pool_percent=20 zswap.zpool=z3fold rootflags=noatime,commit=60,errors=remount-ro,defaults"
    initrd = /EFI/Slackware/initrd.img

    read-only
# Linux entry config ends

# Linux entry config begins
image = /EFI/Android/kernel
  root = /dev/ram0
  label = Android
  append = "quiet root=/dev/sda2 SRC=/opt/android-8.1-r5 androidboot.selinux=permissive DATA=/data SDCARD=sdc1"
  initrd = /EFI/Android/initrd.img

  read-only
# Linux entry config ends
Yes, I run also Android in that particular box.

It was very useful for running Skype before there was Plasma5 with elogind. Or XFCE with elogind.

BTW, someone notices that I use an INITRD for booting Slackware?

I know, I know, the cool kids does not use an initrd...

Last edited by LuckyCyborg; 06-26-2020 at 04:20 PM.
 
Old 06-26-2020, 04:34 PM   #42
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,391

Rep: Reputation: Disabled
Quote:
Originally Posted by LuckyCyborg View Post
I know, I know, the cool kids does not use an initrd...
According to my crystal ball booting Slackware 15 will need an initrd anyway.
 
2 members found this post helpful.
Old 06-26-2020, 08:02 PM   #43
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 544

Rep: Reputation: Disabled
Quote:
Originally Posted by LuckyCyborg View Post
I know, I know, the cool kids does not use an initrd...
Sure, we do.
 
Old 06-26-2020, 09:17 PM   #44
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 2,855

Rep: Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935Reputation: 2935
A line is being drawn in the sand, or on silicon to be more accurate. We are, or rather have been, in a state of transition since Intel has stated they plan to dump CSM Legacy Boot this year. On one hand this improves security but 1) UEFI has already been fuzzy in it's development and part of that is the hoops that CSM attempts to jump through and it's effects on UEFI 2) There is considerable variation in both chipsets and firmware that is currently forced to mix "oil and water".

This is an extremely fundamental change. The only event more fundamental than bootloaders is POST, and actually even that process is involved. If systemd is PID 1, this is PID 0. If I understand correctly once CSM is eliminated 32 bit software will apparently not run and hardware even as fundamental as peripherals like ethernet, audio, and video cards will not work on post CSM systems unless they have EFI compliant firmware built in.

I expect it will all shake out soon but the transition can be fraught with errors until it does, and some hardware, some software... some people will be left behind in the wreckage of transition. For a decent overview of this 2020 deadline worth keeping an eye on look around but this isn't bad ---

https://www.anandtech.com/show/12068...m-uefi-by-2020

2020 looks to be a very important year for computing, a sea change if there ever was one. It's time to start planning how to deal with this schism now. Learn UEFI and if you don't already have it get compliant hardware that properly handles EFI or accept trying to stay happy with pure BIOS/MBR because the transition can be a bitch.

As it applies to this thread, I have personal (and frustrating) experience with trying to fight with older CSM compliant BIOS/UEFI firmware with better success on newer implementations. My plan is to keep at least one older BIOS/MBR system (probably sans CSM) and buy a new rig that is completely UEFI.

Last edited by enorbet; 06-26-2020 at 09:25 PM.
 
Old 06-26-2020, 11:52 PM   #45
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,435

Rep: Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787Reputation: 787
Code:
grub-install --removable
efibootmgr -c -L "Slackware64" -l \\EFI\\Boot\\BOOTX64.EFI
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Should Slackware Live Edition on USB be able to boot in Secure Boot mode? philip0 Slackware - Installation 1 05-25-2020 05:53 AM
[SOLVED] No longer able to add multiple TC rules on same handle in current kernels (4.5.5 works, but anything current does not) herbalbert Linux - Networking 1 01-24-2019 10:08 AM
Mobo only supports uefi boot - how do I boot off a non-uefi cd? Ulysses_ Linux - Hardware 3 02-25-2016 08:06 PM
slackware64 14.1: not able to install LILO to MBR; not able to boot from USB drive. dcsst28 Slackware 1 11-17-2013 09:03 PM
What are any Good Distros that will run off off of 2.0 GB USB Drive? cjc811 Linux - Newbie 2 05-18-2011 12:09 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration