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.
I downloaded and burned Slackware64 current to disc. I then tried to install on a laptop that had worked just fine with Linux before.
This time however LILO complains that a newly wiped SSD, which has only 1 partition, is somehow not "linear" and refuses to install to its MBR. This is an old system without EFI.
Has anyone else seen this? Unless I'm somehow "not holding it right", I think Patrick may have to downgrade LILO.
LILO hasn't been touched since Apr 2018 (which was due to the mass rebuild of the whole system and didn't have any changes). The previous rebuild and almost all of the rebuilds before that have been to add features to liloconfig.
Can you post the actual error and we can try and figure out what is the issue?
Can you post the actual error and we can try and figure out what is the issue?
Hi,
Here's the sequence of events.
1. I wiped my Crucial M4 SSD by doing dd if=/dev/zero of=/dev/sdb
2. I put this SSD into a ~2008 laptop which already had another Crucial M4 SSD in it (a smaller one).
3. I booted slackware64-current, ran fdisk, set up one partition, and then set it up as a LUKS partition. All very standard stuff.
4. Ran setup, everything installed, got to the point where LILO install happens and it ran.
5. It said Fatal error: only linear boot device supported.
6. I recalled that the SSD had a DOS label, so I thought maybe filling the drive with all 0's had put it in some legacy mode that fdisk and LILO don't like, so I rebooted, repartitioned with a GPT label and repeated the process-- same result.
Last edited by MozillaUser3172; 03-29-2020 at 05:51 PM.
PS Argon2 support from cryptsetup will eventually not make its way in GRUB 2.06, but at least the PBKDF2 key derival function is already supported in pre-2.06. So there will be a full support of LUKS1 and a partial support of LUKS2 in this version.
Last edited by Didier Spaier; 03-30-2020 at 06:47 AM.
Reason: PS added.
You'll need an unencrypted /boot if you're using LUKS.
Ah yes, I did skip that step, thanks.
I wonder though if the LILO developers realize what a misleading error message they're producing. It caused me to look for the wrong thing in the wrong place, and not to reflect on whether I left out a step.
Having an unencrypted boot partition is risky. Any organization whose operatives can get physical access to your computer can in theory replace your kernel with a special kernel that contains spyware.
Having an unencrypted boot partition is risky. Any organization whose operatives can get physical access to your computer can in theory replace your kernel with a special kernel that contains spyware.
Yeah. It's up to you, to make sure they can't do that.
After that, let's hope you have a system that's still usable.
Having an unencrypted boot partition is risky. Any organization whose operatives can get physical access to your computer can in theory replace your kernel with a special kernel that contains spyware.
Yes, but the linked to article proposes a way to use an encrypted boot partition.
Having an unencrypted boot partition is risky. Any organization whose operatives can get physical access to your computer can in theory replace your kernel with a special kernel that contains spyware.
You're right. In my case, after installing/upgrading kernel and generate initrd.gz, I keep a checksum (sha256sum) of these files on another computer. When I had to restart my computer I can check integrity.
Unless I forgot something, I'll see if something wrong.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.