Didier,
I realize I'm late to need, but I wanted to thank you for putting together this method for installing Slackware 14.2 to an NVMe device. I followed the steps you outlined in the first post in this thread and now have a machine running Slackware 14.2 on a Plextor NVMe (the only drive in the machine). Went very smoothly! Thanks! Lumpy |
You don't need to patch eliloconfig anymore
The new ISO fake_slackware64-14.2-4.iso in the directory: http://slint.fr/forSlackware/NVMe includes a modified installer shipping the patch for eliloconfig, applied by the slackinstall script at end of packages' installation. I just had to slightly modify the build script.
So now, you can just follow these instructions:
EDIT 21 August 2017, 22h00 UTC+2: uploading a new ISO (build #4) the previous failed to patch eliloconfig. |
Quote:
Best, Lumpy |
Didier,
Thanks for this; I installed current (kernnel 4.9.44) on a Samsung SM961 M.2, NVMe card and both install and elilo-config worked as a dream; never got the windows test install so quickly replaced on a drive ;-) rob |
Didier,
just to let you know that I used your latest image to install Slackware64 14.2 on a ThinkPad X1 6th generation (with a Samsung 1Tb NVMe drive). It went smoothly as I pointed it to another USB with the full Slackware installation files (incredibly this ultrabook has 2 USB3 slots). The part that was more complicated for me was dealing with UEFI, as this is the first time I have installed anything not using MBR, but I still managed to do this without errors. I also used luks+lvm and encrypted root and swap together (as explained in README_CRYPT.TXT). All is working well. Thank you! |
Impossible to boot on NVME partition
Hi Didier
I have a new laptop with NVME partitions To install the Slackware 14.2 I have followed your instructions -Download and verify fake_slackware64-14.2-4.iso - Put it on an USB stick - Boot my laptop with this USB stick - Give the source with another USB stick - Installation finished without asking me to use Elilo ? I have made an initrd using mkinitrd in the newly installed system and put the initrd.gz in /boot/efi/EFI/Slackware Reboot on this EFI partition Elilo starts reads initrd.gz and vmlinuz-huge : start of the Slack boot list Just after starting eudevd , stop with an error message mount /dev/nvme... on /mnt : No such file or directory Seems that I have forgooten to do something ? Didier Courtaud Quote:
|
Quote:
To investigate further please do this:
Then you can redirect all commands above to files in /stick and just type: Code:
cp /floppy/EFI/Slackware/elilo.conf /stick |
Quote:
I have thought about two possible explanations : 1- It does not work with reiserfs partitions ? 2- As I have made a Code:
chroot /mnt .. In any case thanks for your help ! |
Quote:
Code:
lsblk -l -o model,name,type,size,fstype Quote:
Quote:
Oh and there is no benefit in having in having separate partitions for /var and /usr in a desktop. I don't even have one for /home and encounter no issue: actually all my systems have just one partition: / Some people think that having a separate partition for /home helps in case of upgrade but I strongly disagree: the content of /home can be backed up then restored after upgrade, ant it is inadvisable to keep all hidden files and directories as is after upgrade. You are better off saving and restoring only case by case the ones that should not be modified. In any case, the more you cut your space on a mass storage device in slices, the sooner you will have a partition filled up. You can still set LVM, but why complicate things? tl;dr: install anew with the huge kernel, ext4 and only one / partition (also /home if you insist, but again I don't see the usefulness of that). When this will be done, come back to get some advice about installing the generic kernel and an initrd, while setting elilo.conf to keep two boot entries just in case: one for the huge kernel, one for the generic one with an initrd). |
[
Maybe. I recommend installing with the huge kernel, then start the new system and only then make an initrd. Didier, that is just what I want to do : start the huge kernel but without an initrd, it is impossible ! With elilo.efi wmlinuz-huge and the elilo.conf I showed you in /boot/efi/EFI/Slackware and the UEFI in BIOS pointed to that .efi file , the laptop does not show anything and refuses to boot |
Finally I have succeded to boot my Dell Latitude 5490 on Slack !!!!
I have to switch the laptop to AHCI as described here : http://triplescomputers.com/blog/unc...hci-operation/ and then with only the kernel and elilo.efi in /boot/efi/EFI/Slacware it boots normally ! Thanks to Dell to make me spend a week before succedding : - Decrypt the root partition in order to shrink the Windows Partition - Obliged to use UEFI to boot the Slack - Turn the laptop from RAID IDE to AHCI All this stuff to forbid the installation of Linux on this laptop ! DC Quote:
|
Must admit, your fake_slackware works a treat, UEFI/LVM on NVME worked first time. thanks for the image
|
Will fake_slackware64-14.2-4.iso also work with non-NVMe computers? The reason I'm asking is that I'm starting a new job next week and don't know what laptop will I have (should have asked) and of course I want to put Slackware on it. And I think that the answer for this question is yes - it will work because I've just tried it in VirtualBox that doesn't expose any /dev/nvme devices and it's ok but just want to make sure.
|
Quote:
|
Or install Slint64-14.2.1.2, that ships a 4.19 kernel and speaks Polish during installation ;)
|
All times are GMT -5. The time now is 12:56 PM. |