[SOLVED] Wed Jun 13 05:43:00 UTC 2018 and Newer Current bare metal install?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@laprjns many thanks for your efforts anxious to hear about the second system. I'm at a loss never had a problem installing Slackware except when the huge kernel got too huge.
Don't know if this is a help but
the efishell does not see the file system ie
fs0: / fs1: /fsn: etc only lists the file systems on dev/sdb dev/nvme0n1
it does not list a filesystem for /dev/sda
I thought dropping into the efishell might enable a boot
perhaps I should try to zero /dev/sda before starting the install.
Thanks
AlleyTrotter
Last edited by AlleyTrotter; 06-24-2018 at 08:28 AM.
Works on my second system, a desktop tower with a MSI motherboard. Definitely bare metal, it doesn't have a cover on the case . So you installed the EFI partition on sda, not on/nvme0n1?
Fri Jun 15 04:12:46 UTC 2018 a/efibootmgr-16-x86_64-2.txz: Rebuilt.
a/efivar-35-x86_64-1.txz: Upgraded.
Switch to efivar-35, since 36 seems to have problems. Thanks to _RDS_.
Update efivars and efiboomgr.
You can do that from the installer of a Slackware64-current ISO, more recent than this update.
Then, still from he installer, have the / of your installed system mounted as /mnt, bind mount /dev /sys and /proc to /mnt/dev, /mnt/sys and /mnt/proc, chroot /mnt, mount <your EFI partition> /boot/efi, then run elilo.
If that doesn't work, post the output of this command that you can type from an installer:
Code:
lsblk -l -o name,type,parttype,uuid,fstype|grep part
Last edited by Didier Spaier; 06-24-2018 at 09:35 AM.
It is definitely /dev/sda
The nvme is a completely separate install with its own efi partition same as /dev/sdb they each have their own efi partition and function independently of each other
There is no communication between them.
@AlleyTrotter: care to give the output of this command, as requested in my previous post?
Code:
lsblk -l -o name,type,parttype,uuid,fstype|grep part
The value we will find in the parttype field will tell with certainty which partitions are EFI System Partitions, as the UEFI specification states these values both in case of dos and gpt partition labels. blkid does not provide this information so its output is pointless in this case.
Last edited by Didier Spaier; 06-24-2018 at 12:43 PM.
perhaps I should try to zero /dev/sda before starting the install.
WINNER WINNER CHICKEN DINNER!!!!!
zeroing the 1G of /dev/sda then proceeded with the install was the trick for my system.
Selecting Slackware entry from the UEFI menu (for me press F11)boots a new efi partition on /dev/sda1 with elilo.efi, elilo.conf and vmlinuz which now boots Slackware64-Current on /dev/sda2
my other efi partitions (sdb nvme0n1) are intact and still bootable from the UEFI menu.
Many Thanks for all the suggestions I forget which one made me think of zeroing, but that was the trick
[QUOTE=AlleyTrotter;5871413]
zeroing the 1G of /dev/sda then proceeded with the install was the trick for my system./QUOTE]
It's good that you got it fixed but it would have been nice to understand root cause. I was starting to suspect that you had the wrong file system on the sda1 something along the lines of a problem that I had due to a "lingering" file system after a repartitioning. See here https://www.linuxquestions.org/quest...7/#post5810474
Writing zero to the first 1G of space would have cleared any lingering file system in that space. Do you think that is what happened?
Writing zero to the fist 1G of space would have cleared any lingering file system in that space. Do you think that is what happened?
Yes I believe when selecting 'g' create a new gpt with fdisk it does not clear out everything.
I believe this because the installer merely add the efi partition to fstab, after zeroing it first, installer asked if it should format the efi partition then added it to fstab.
This was the only difference I noticed during the install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. So you installed the EFI partition on sda, not on/nvme0n1?
