LinuxQuestions.org
Review your favorite Linux distribution.
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 05-10-2019, 02:37 PM   #1
nix84
Member
 
Registered: Apr 2014
Posts: 272

Rep: Reputation: Disabled
Can't get 14.2 installed after several attempts


Am having prob with 14.2 install. I used slack since 90's until ver.13.37
and have been univ. instructor on bash + other langs, so am no nurd.
Am installing to flash drive.
1) created partitions with fdisk including EFI, Swap, and Linux.
2) performed install as expert -no hitches
3) found out about files needing to be moved about in the EFI and did that
4) FD doesn't boot. PC's boot sequence checks OK
5) ancillary boot stick doesn't work either

A) what is the correct sequence to file fiddling in 3) I could have it wrong
B) does 1) need use of gdisk instead? Used correct partition types of 82 etc. not the 8200, but that didn't work either (fdisk reference runs off of screen)
c) boot sequence was checked and was correct.
Can anyone think of what I might be leaving out per their own experiences?
Please DO NOT refer to that other flash drive method which uses persistence as that IS NOT the way I wish to attack this problem, i.e. I use flash drive like a HD.
I do not have web access except at the local library so your responses may need careful construction for my subsequent trials as my responses may take a 2-3 days. Thanks for the help and consideration.

Last edited by nix84; 05-10-2019 at 02:40 PM.
 
Old 05-10-2019, 03:46 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,837

Rep: Reputation: Disabled
Slackware-14.2 can't be installed on an USB flash drive.

As an aside, it would be bad if it could as none of the file systems that can be used to format the root or / partition is suitable for a flash drive, so it would wear out very fast.

Further there is no need to set up an EFI partition in the target if you mean to install Slackware-14.2 (32 bit) that doesn't handle EFI booting. Only Slackware64-14.2 does.

Last edited by Didier Spaier; 05-10-2019 at 03:51 PM.
 
1 members found this post helpful.
Old 05-10-2019, 05:21 PM   #3
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,874

Rep: Reputation: 448Reputation: 448Reputation: 448Reputation: 448Reputation: 448
To boot on efi system do the following.
chroot into flash drive installation,
mount your flash drive efi partition to /boot/efi
Code:
grub-install --target=x86_64-efi --removable  --no-nvram  /dev/sdb
assuming the flash drive is /dev/sdb change accordingly.

run mkinitrd to load usb_storage drivers at bootup.

add rootdelay=10 to /etc/default/grub/
edit /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT line to this
Code:
GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=10"
Code:
grub-mkconfig -o /boot/grub/grub.cfg

exit out then reboot

You didn't give any detail information on exactly what you did. was it 32bit or 64bit iso you used? To allow to boot on both efi and legacy need more information. what partition scheme you used GPT or MSDOS? You didn't say exactly what you did on the efi partition either so someone can figure out what you did wrong there.

Last edited by colorpurple21859; 05-16-2019 at 05:26 AM.
 
1 members found this post helpful.
Old 05-11-2019, 03:59 AM   #4
Fat_Elvis
Member
 
Registered: Oct 2016
Distribution: FreeDOS 1.2
Posts: 244

Rep: Reputation: 67
In addition to the above, I've needed to run efibootmgr on my slightly older (2014-ish) boards.

Here's the command I've been using:

Code:
efibootmgr \
        --write-signature \
        --create \
        --disk "/dev/sda" \
        --part "1" \
        --loader "\\EFI\\Slackware\\grubx64.efi" \
        --label "Slackware" \
        --verbose

efibootmgr --bootnum 0 --active
Obviously, modify the disk parameter accordingly. "/dev/nvme0n1" on NVMe type drives.

Last edited by Fat_Elvis; 05-11-2019 at 04:01 AM.
 
Old 05-14-2019, 03:34 PM   #5
nix84
Member
 
Registered: Apr 2014
Posts: 272

Original Poster
Rep: Reputation: Disabled
@Didier Spaier: laptop is 64bit efi. Install DVD contains Slackware64-14.2. Examined flash drive and it has most of the slackware stuff I would expect to find. My desktop install went well using 32 bit version and that is working.
@colorpurple21859: instructions I used have me creating 3 partitions swap, efi, and linux in order as I said these were created with fdisk. All the /boot/efi instructions I have had me put specified files for EFI there then jerk them about I don't have them with me but feel certain that where they went initially was correct.
Have never used grub to do a slack install. Is that an editor or partition maker? Yes, am using sdb.
Sorry 'bout that it is a 64bit laptop Toshiba c55-5126. Please point me to grub overview and detail which you used to get familiar as this is new to me. What should I expect from executing those commands? Should I still do a fdisk to create partitions or will grub be doing that for me?
@Fat_Elvis: is efibootmgr a non-slackware application software product? What is NVMe? Looks like you are using the PC's hard drive and I am using a flash drive. My reading indicates this makes no difference. I did a non-EFI install on my 32bit laptop which works great (except for marble being created 4 times).
Sure appreciate the assistance. Will be fiddling with grub which I think I have a copy. Hope it has some instructions as it is not on my man page. Be back in 3 days THANKS
 
Old 05-14-2019, 03:58 PM   #6
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,874

Rep: Reputation: 448Reputation: 448Reputation: 448Reputation: 448Reputation: 448
Quote:
instructions I used have me creating 3 partitions swap, efi, and linux
that is good.

Quote:
All the /boot/efi instructions
What instructions were you following can you post a link to the instructions?
Quote:
Have never used grub to do a slack install. Is that an editor or partition maker?
neither, grub is a bootloader, when you run the grub-install command I posted it will put the appropriate files on the efi partition. I edited the grub-install command in my earlier post with this being a removable usb.

Last edited by colorpurple21859; 05-14-2019 at 03:59 PM.
 
Old 05-15-2019, 11:27 AM   #7
Fat_Elvis
Member
 
Registered: Oct 2016
Distribution: FreeDOS 1.2
Posts: 244

Rep: Reputation: 67
Quote:
Originally Posted by nix84 View Post
@Fat_Elvis: is efibootmgr a non-slackware application software product? What is NVMe? Looks like you are using the PC's hard drive and I am using a flash drive. My reading indicates this makes no difference. I did a non-EFI install on my 32bit laptop which works great (except for marble being created 4 times).
Sure appreciate the assistance. Will be fiddling with grub which I think I have a copy. Hope it has some instructions as it is not on my man page. Be back in 3 days THANKS
efibootmgr is included in Slackware. NVMe is a newer type of SSD drive that is used in recent laptops and such. Looks like a tiny stick of RAM. I mentioned that because it was slightly more difficult to install Slackware 14.2 to those types of drives.

Non-EFI will also work, and is probably easier to set up.

By the way, for USB drives, the installation process is slightly different. You could get away with not using efibootmgr, but the boot loader (say, the GRUB image) _must_ be placed in a very specific location.

Code:
mv ./grubx64.efi /boot/efi/EFI/BOOT/BOOTX64.EFI
I don't know if all uppercase is necessary, but I'd go with that anyway.

EDIT: If your laptop is 64-bit capable, I would strongly suggest installing a 64-bit version of Slackware. The CPU has some really neat capabilities when running in 64-bit mode. Unless you are specifically aiming with compatibility with very old, or *ahem* Windows software through WINE. The Windows crowd has a great infatuation with 32-bit software. They will never abandon the i386.

Last edited by Fat_Elvis; 05-15-2019 at 11:33 AM.
 
1 members found this post helpful.
Old 05-15-2019, 09:46 PM   #8
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,874

Rep: Reputation: 448Reputation: 448Reputation: 448Reputation: 448Reputation: 448
Quote:
Non-EFI will also work, and is probably easier to set up.
I 100% agree with you on that one. When I do installs to usb I set them up for both efi and legacy booting.



@nix84 I edited the grub-install command in post #3 and add items to do to make bootable on usb. The --removable will install a /boot/efi/EFI/BOOT/BOOTX64.EFI efi bootloader.
Will have less issues booting if root=UUID=???? is used on the linux line of your /boot/grub/grub.cfg for your menuentries.

Would need to know if usb 'disk label type' is msdos or gpt before giving any advice on legacy booting.

Last edited by colorpurple21859; 05-16-2019 at 05:38 AM.
 
Old 05-16-2019, 07:46 AM   #9
Fat_Elvis
Member
 
Registered: Oct 2016
Distribution: FreeDOS 1.2
Posts: 244

Rep: Reputation: 67
Quote:
Originally Posted by colorpurple21859 View Post
@nix84 I edited the grub-install command in post #3 and add items to do to make bootable on usb. The --removable will install a /boot/efi/EFI/BOOT/BOOTX64.EFI efi bootloader.
Yep. I completely forgot about that. With the --removable switch, you would not need to use efibootmgr.

Quote:
Will have less issues booting if root=UUID=???? is used on the linux line of your /boot/grub/grub.cfg for your menuentries.
I think grub-cfg uses UUID by default anyways. Otherwise the UUID for a drive can be found at the output of:

Code:
lsblk -no uuid,kname,label,mountpoint
 
Old 05-16-2019, 10:03 AM   #10
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, puppy, ubuntu
Posts: 2,874

Rep: Reputation: 448Reputation: 448Reputation: 448Reputation: 448Reputation: 448
Quote:
Yep. I completely forgot about that
I did a minimal install to a usb to see what I had forgotten, I don't remember things like a use to lol. I had also forgot about the "--removable" option for grub-install at first.
The biggest issue was, had to create an initrd.img to load the usb storage drivers, their built into the huge kernel as modules. Without the initrd.img would get serious kernel panic and machine lock up.
Once I got that out of the way, then there was the forgotten "rootdelay=10" added to the grub Linux command line.

Last edited by colorpurple21859; 05-16-2019 at 10:05 AM.
 
Old 05-17-2019, 03:04 AM   #11
Fat_Elvis
Member
 
Registered: Oct 2016
Distribution: FreeDOS 1.2
Posts: 244

Rep: Reputation: 67
Quote:
Originally Posted by colorpurple21859 View Post
Once I got that out of the way, then there was the forgotten "rootdelay=10" added to the grub Linux command line.

Good tip. Thanks!
 
  


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
With Linux 4.15.4 or later several systemd services fail, like flush and partition services, for several distros fusion809 Linux - Laptop and Netbook 6 04-13-2018 11:23 PM
when i right click on aword to correct due to mis-spelling , I often will not open the menu. then after several attempts it will flash bu Linux11mycomputer Linux - General 1 03-17-2016 09:05 PM
How to zip several files to several zip with one command? thomas2004ch Linux - Newbie 4 02-08-2010 08:13 AM
Resetting several Linux account passwords on several systems using Windows ssh Melindhra667 Linux - Enterprise 1 02-26-2009 07:38 PM
eth0 can't get IP with DHCP, static config. attempts can't ping pdt677 Linux - Networking 6 03-06-2005 09:53 PM

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

All times are GMT -5. The time now is 12:34 AM.

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