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 07-17-2017, 12:18 PM   #46
Fat_Elvis
Member
 
Registered: Oct 2016
Posts: 138

Rep: Reputation: 29

The GRUB install utility simply calls efibootmgr. elilo probably does the same.

Quote:
Originally Posted by slackerDude View Post
If I'm UPDATING my EFI config, but not installing for the first time, do I still use eliloconfig?
If you are not changing elilo config, then simply type "efibootmgr" and see if it needs updating. AFAIK EFI stuff is in the motherboard, as opposed to the boot sector like the oldendays of BIOS.

Quote:
Originally Posted by Didier Spaier View Post
As root type:
Code:
ln -sf /boot/vmlinuz-<newkernel> /boot/vmlinuz
ln -sf /boot/<newinitrd> /boot.initrd.gz
# If you need an intrd, else re(move) any existing symlink /boot/initrd.gz
I think some programs need the sources to be in /usr/src/linux as well. Nvidia driver definitely does.

Code:
ln -sv /usr/src/linux-YOUR.VERSION /usr/src/linux

Last edited by Fat_Elvis; 07-17-2017 at 12:28 PM.
 
Old 07-17-2017, 12:28 PM   #47
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,527

Rep: Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480
Quote:
Originally Posted by Fat_Elvis View Post
As far as I know the elilo and grub utilities simply call efibootmgr. Sure about grub, not elilo.
No for Slackware and elilo. eliloconfig puts the stuff necessary to bot in the EFI System partition and optionally runs efibootmanager to add an entry named "Slackware" is the firmware's boot menu, that will point to the stuff it just wrote in the ESP.

For the records grub ships as modules drivers for many filesystems and can access the kernel and initrd in an ext4 partition, for instance. elilo does not have this ability.

Quote:
If you are not changing elilo config, than simply type "efibootmgr" and see if it needs updating.
This is not enough as you also need to put the kernel, and possibly the initrd in the ESP. You can do that manually, but why bother?

Last edited by Didier Spaier; 07-17-2017 at 12:38 PM.
 
Old 07-17-2017, 12:38 PM   #48
slackerDude
Member
 
Registered: Jan 2016
Posts: 41

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
  1. As root type:
    Code:
    ln -sf /boot/vmlinuz-<newkernel> /boot/vmlinuz
    ln -sf /boot/<newinitrd> /boot.initrd.gz # If you need an intrd, else re(move) any existing symlink /boot/initrd.gz
  2. As root type
    Code:
    eliloconfig
The step 1. is necessary because eliconfig copies /boot/vmlinuz (and /boot/initrd.gz if it exists) in the directory /boot/efi/Slackware and writes the config file /boot/efi/Slackware/elilo.conf accordingly.

eliloconfig also copies in /boot/efi/Slackware /boot-elilo-x86_64 renamed elilo.efi. This file which will serve as a bootloader, so there is no need to write a boot sector as does lilo.

In case you wonder, the bootloader elilo.efi needs to have all needed files (elilo.conf, kernel, initrd) in the directory where it is installed, which should be inside an EFI System Partition aka ESP, equipped with a FAT file system.

Have a look at /usr/sbin/elilconfig and the documents in /usr/doc/elilo* to know more.
Thanks. I *THINK* I had all that, and still had a kernel panic.. <shrug> maybe Dusk's pre-compiled kernels aren't suitable for my build.

Figured out how to enable legacy mode, re-installed the old fashioned way, grabbed generic 4.12.2 sources, compiled in 3-4 minutes with -j16. Make install, reboot, and I'm good to go.

Now, on to nvidia drivers.. Then, sound..
 
Old 07-17-2017, 01:11 PM   #49
Fat_Elvis
Member
 
Registered: Oct 2016
Posts: 138

Rep: Reputation: 29
Quote:
Originally Posted by Didier Spaier View Post
No for Slackware and elilo. eliloconfig puts the stuff necessary to bot in the EFI System partition and optionally runs efibootmanager to add an entry named "Slackware" is the firmware's boot menu, that will point to the stuff it just wrote in the ESP.

For the records grub ships as modules drivers for many filesystems and can access the kernel and initrd in an ext4 partition, for instance. elilo does not have this ability.
GRUB does the same. But without running efibootmgr, the only way to update the boot order in firmware seems to be to go into the EFI shell, which seems to be more complicated than efibootmgr.

That's bad news about elilo. I have only the EFI bootloader files on a small vfat partition. Everything else is on ext4. I had a dislike for GRUB until I was forced to use it. I found it to be a very capable program. Don't know if I'd go back to lilo.

Quote:
This is not enough as you also need to put the kernel, and possibly the initrd in the ESP. You can do that manually, but why bother?
I assumed he was not updating config files or the kernel, but simply modifying EFI settings.

Last edited by Fat_Elvis; 07-17-2017 at 01:12 PM.
 
Old 07-17-2017, 01:29 PM   #50
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,040

Rep: Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031
Quote:
Originally Posted by Didier Spaier View Post
  1. As root type:
    Code:
    ln -sf /boot/vmlinuz-<newkernel> /boot/vmlinuz
    ln -sf /boot/<newinitrd> /boot.initrd.gz # If you need an intrd, else re(move) any existing symlink /boot/initrd.gz
  2. As root type
    Code:
    eliloconfig
The step 1. is necessary because eliconfig copies /boot/vmlinuz (and /boot/initrd.gz if it exists) in the directory /boot/efi/Slackware and writes the config file /boot/efi/Slackware/elilo.conf accordingly.

eliloconfig also copies in /boot/efi/Slackware /boot-elilo-x86_64 renamed elilo.efi. This file which will serve as a bootloader, so there is no need to write a boot sector as does lilo.

In case you wonder, the bootloader elilo.efi needs to have all needed files (elilo.conf, kernel, initrd) in the directory where it is installed, which should be inside an EFI System Partition aka ESP, equipped with a FAT file system.

Have a look at /usr/sbin/elilconfig and the documents in /usr/doc/elilo* to know more.
Can you manually add your kernels/initrds into /boot/efi/Slackware/ and manually edit the elilo.conf file? The reason I ask is I usually keep an old kernel as backup (sometimes several, depending on what kernels I'm running) and I'd always edit lilo to add an new entry for the new kernel rather than replacing an old entry.
 
Old 07-17-2017, 01:43 PM   #51
slackerDude
Member
 
Registered: Jan 2016
Posts: 41

Rep: Reputation: Disabled
So, got a kernal compiled, got the latest beta NVIDIA driver (384.47) compiled. Had to enable usb3, I believe (I also enabled psaux) in order to get USB working so that I had mouse support.. However, that seems to have broken "sensors".. One step forward...
 
Old 07-17-2017, 01:45 PM   #52
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.2 (4.12.3) UEFI enabled
Posts: 427

Rep: Reputation: 111Reputation: 111
Code:
John@NVMe:~$ ls -l /boot/efi/EFI/Slackware/
total 124640
-rwxr-xr-x 1 root root 8161248 May  8 09:12 bzImage-4.11.0
-rwxr-xr-x 1 root root 8153024 May 14 08:54 bzImage-4.11.1
-rwxr-xr-x 1 root root 8166688 May 20 15:25 bzImage-4.11.2
-rwxr-xr-x 1 root root 8162688 May 26 09:02 bzImage-4.11.3
-rwxr-xr-x 1 root root 8169472 Jun  7 09:21 bzImage-4.11.4
-rwxr-xr-x 1 root root 8153344 Jun 15 09:12 bzImage-4.11.5
-rwxr-xr-x 1 root root 8163552 Jun 17 08:41 bzImage-4.11.6
-rwxr-xr-x 1 root root 8156448 Jun 24 10:54 bzImage-4.11.7
-rwxr-xr-x 1 root root 8163968 Jun 29 10:09 bzImage-4.11.8
-rwxr-xr-x 1 root root 8170688 Jul 10 09:16 bzImage-4.11.9
-rwxr-xr-x 1 root root 8198320 Jul  3 12:39 bzImage-4.12.0
-rwxr-xr-x 1 root root 8198800 Jul 12 16:48 bzImage-4.12.1
-rwxr-xr-x 1 root root 8199536 Jul 15 11:42 bzImage-4.12.2
-rwxr-xr-x 1 root root 7635952 Jun 30 21:35 bzImage-4.4.75
-rwxr-xr-x 1 root root 7710480 Apr  8 08:02 bzImage-4.6.3
-rwxr-xr-x 1 root root     643 Jul 15 11:43 elilo.conf
-rwxr-xr-x 1 root root  239720 Apr  1  2016 elilo.efi
-rwxr-xr-x 1 root root 5790480 Apr  8 08:01 vmlinuz-3.13.3-lfs-7.5
you may have as many kernels as will fit in the efi partition
Code:
john@NVMe:~$ cat /boot/efi/EFI/Slackware/elilo.conf 
chooser=simple
delay=50
timeout=1
#
image=bzImage-4.12.2
        label=4122
        read-only
        append="root=/dev/nvme0n1p2 vga=normal ro"
#
image=bzImage-4.12.1
        label=last
        read-only
        append="root=/dev/nvme0n1p2 vga=normal ro"
#
image=bzImage-4.4.75
        label=SDA
        read-only
        append="root=/dev/sda2 vga=normal ro"
#                                                                                          
image=vmlinuz-3.13.3-lfs-7.5
  label=lfs
  read-only
  append="root=/dev/sdb8 vga=normal ro"
#
# was image=bzImage-rescue
image=bzImage-4.6.3
  label=rescue
  read-only
  append="root=/dev/sdb2 vga=normal ro"
#
image=bzImage-4.4.75
  label=build
  read-only
  append="root=/dev/sdb4 vga=normal ro"
#
elilo.conf is used to choose any kernel stanza you wish
you do not have to modify anything else when installing another/new kernel
the first stanza of elilo.conf is the default
the delay=50 will give you 5 seconds to make a choice at the end of the efi splash screen to
type the name of the kernel you wish or press tab to see a list of available kernel labels
running eliloconfig is not necessary except at the initial install
HTH
John

Last edited by AlleyTrotter; 07-17-2017 at 01:52 PM.
 
1 members found this post helpful.
Old 07-17-2017, 02:00 PM   #53
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,527

Rep: Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480
Quote:
Originally Posted by bassmadrigal View Post
Can you manually add your kernels/initrds into /boot/efi/Slackware/ and manually edit the elilo.conf file? The reason I ask is I usually keep an old kernel as backup (sometimes several, depending on what kernels I'm running) and I'd always edit lilo to add an new entry for the new kernel rather than replacing an old entry.
Yes. And then as stated by John you of course do not need to run eliloconfig.

Last edited by Didier Spaier; 07-17-2017 at 02:14 PM.
 
1 members found this post helpful.
Old 07-17-2017, 02:33 PM   #54
slackerDude
Member
 
Registered: Jan 2016
Posts: 41

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
Yes. And then as stated by John you of course do not need to run eliloconfig.
Ah, so it's an automatic update (i.e. reads the files at boot time). That's what I was missing. I was used to having to do SOMETHING after modifying the config file..

Anyway, work on 4.12.2 continues. I think I got some sensors working..
 
Old 07-17-2017, 03:11 PM   #55
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,040

Rep: Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031
Quote:
Originally Posted by AlleyTrotter View Post
you may have as many kernels as will fit in the efi partition

elilo.conf is used to choose any kernel stanza you wish
you do not have to modify anything else when installing another/new kernel
the first stanza of elilo.conf is the default
the delay=50 will give you 5 seconds to make a choice at the end of the efi splash screen to
type the name of the kernel you wish or press tab to see a list of available kernel labels
running eliloconfig is not necessary except at the initial install
HTH
John
Beautiful! So, it is just like a simpler lilo (in that you don't need to run anything afterward to save the config). That makes me feel a bit more comfortable. I had just seen a ton of posts talking about needing to use an automatic tool, but I like to at least know what's going on under the hood, and sometimes I prefer to bypass the automatic tools in favor of manually tweaking things to my liking (I suppose this is why I like Slackware so much )
 
Old 07-18-2017, 02:13 AM   #56
Fat_Elvis
Member
 
Registered: Oct 2016
Posts: 138

Rep: Reputation: 29
Quote:
Originally Posted by slackerDude View Post
Ah, so it's an automatic update (i.e. reads the files at boot time). That's what I was missing. I was used to having to do SOMETHING after modifying the config file..

Anyway, work on 4.12.2 continues. I think I got some sensors working..
Just a small observation: I believe it reads only the config file, and tries to load the kernel at the path you put in there. It really isn't like before when you had to write the bootloader into the MBR of your disk. The new system doesn't check the MBR. I'm not sure you can even make an MBR on a GPT disk. Correct me if I'm wrong about any of this.

Quote:
Originally Posted by bassmadrigal View Post
I had just seen a ton of posts talking about needing to use an automatic tool, but I like to at least know what's going on under the hood, and sometimes I prefer to bypass the automatic tools in favor of manually tweaking things to my liking (I suppose this is why I like Slackware so much )
As long as elilo*.efi is inside the ESP partition, (and the kernels, as Didier Spaier has pointed out that elilo can't read ext4) and is selected as the current boot file in EFI, (which is modifiable either in your BIOS settings or with efibootmgr) you wouldn't need to modify anything other than the elilo config file.

Last edited by Fat_Elvis; 07-18-2017 at 02:23 AM.
 
1 members found this post helpful.
Old 07-18-2017, 02:23 AM   #57
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,527

Rep: Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480Reputation: 2480
Quote:
Originally Posted by Fat_Elvis View Post
I'm not sure you can even make an MBR on a GPT disk. Correct me if I'm wrong about any of this.
Yes you can, if you use cgdisk or cfdisk it will include a protective MBR. This comes handy as you can have two ways of booting the same device: using lilo if you are in legacy mode, elilo in efi mode.

During installation of Slackware64-14.2 with EFI enabled, the installer suggests to skip installing lilo but you can install it, then install elilo too.
 
1 members found this post helpful.
Old 07-18-2017, 02:31 AM   #58
Fat_Elvis
Member
 
Registered: Oct 2016
Posts: 138

Rep: Reputation: 29
Quote:
Originally Posted by Didier Spaier View Post
Yes you can, if you use cgdisk or cfdisk it will include a protective MBR. This comes handy as you can have two ways of booting the same device: using lilo if you are in legacy mode, elilo in efi mode.

During installation of Slackware64-14.2 with EFI enabled, the installer suggests to skip installing lilo but you can install it, then install elilo too.
So two boot methods on the same system. This is actually super useful info. Thanks!

With an NVMe disk, Slack 14.2 installer wasn't able to set up any of the bootloaders automatically in my case. The problem is the "/dev/nvme0n1p1" naming of these devices that the installer scripts mess up, as far as I have figured out.
 
Old 07-18-2017, 06:31 AM   #59
MarcT
Member
 
Registered: Jan 2009
Location: UK
Distribution: Slackware 14.2
Posts: 105

Original Poster
Rep: Reputation: 43
AM4 Sensors Support

Quote:
Originally Posted by slackerDude View Post
So, got a kernal compiled, got the latest beta NVIDIA driver (384.47) compiled. Had to enable usb3, I believe (I also enabled psaux) in order to get USB working so that I had mouse support.. However, that seems to have broken "sensors".. One step forward...
Sensors support on AM4 boards is a bit hit & miss right now. My board (ASRock x370 Taichi) uses the "nct6775" kernel module, which is in kernel 4.11 already - but is not known by "sensors-detect" so is not detected. The solution is to "modprobe nct6775" and run sensors. If you get a result, add the modprobe command to "/etc/rc.d/rc.local".

From what I've read, most other AM4 boards need a patched version of the "it87" module. I don't think the patch has made it into any kernels just yet. Google "Ryzen it87" for details.

Finally, reading the on-die thermistor inside the CPU is currently not possible in Linux (normally handled by the k10temp module for earlier AMD CPUs). This is because AMD have not (yet?) released the BIOS and Kernel Developers Guide (BKDG) for Family 17h CPUs. Some Windows tools can do it - presumably because they've signed an NDA.

Last edited by MarcT; 07-18-2017 at 06:34 AM.
 
1 members found this post helpful.
Old 07-18-2017, 10:07 AM   #60
slackerDude
Member
 
Registered: Jan 2016
Posts: 41

Rep: Reputation: Disabled
Quote:
Originally Posted by MarcT View Post
Sensors support on AM4 boards is a bit hit & miss right now. My board (ASRock x370 Taichi) uses the "nct6775" kernel module, which is in kernel 4.11 already - but is not known by "sensors-detect" so is not detected. The solution is to "modprobe nct6775" and run sensors. If you get a result, add the modprobe command to "/etc/rc.d/rc.local".
Yes, my board (MSI B350 Gaming Plus) seems to work with nct6775 - I grabbed the updated code for that one. In any case, it seems to be working.

I now need to figure out sound..
root@kraken:~# lspci | grep -i audio
23:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1)
25:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457

That seems correct. However, when opening the kde multimedia config, no hardware is shown, only the "dummy" device. Started pulse and alsa, IIRC, but still nothing. IIRC, with my current machine, both nvidia and the built-in audio devices showed up in the list, I just had to play around with them until it worked..

Hmm. From my current machine, I see that KDE just needs to find pulseaudio, because it's set to "HDMI-out", but I use just the regular "line out" plug anyway (it goes into an external amp).

I rebuilt the kernel (again - like the 7th time now) because by default "tmpfs" wasn't turned on (really?), which caused pulseaudio to fail. Now it's complaining about missing module "module-alsa-card"..
 
  


Reply

Tags
ryzen, slackware


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
Ryzen processors quantumbb Linux - Hardware 4 03-06-2017 04:39 PM
LXer: AMD Ryzen 7 1700 Specs Confirmed, A $320 Rival To Intel’s $1099 i7 6900K – 8 Cores, 65W, 3.7Ghz With Unlimited Boost & Unlocked Multip LXer Syndicated Linux News 0 02-12-2017 10:43 AM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
[SOLVED] Slackware64-C client wont detect Slackware64-C Samba server slackass Slackware 5 08-07-2009 11:23 PM


All times are GMT -5. The time now is 06:00 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