Brand New Desktop Build: Intel AC 9260 and Slackware



Alexzee

Well-Known Member
Credits
1,162
Thank you for explaining:-

I think what I'm going to try is to set everything in the CSM section to Legacy and see if that disables the secure boot.

If it disables the secure boot that I should be able to install Slackware from what I'm understanding.

If not than I'll have to allow UEFI to install Slackware.
 

Alexzee

Well-Known Member
Credits
1,162
had a quick look :

So i've got 100MB efi and :


512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Is that without Legacy set in the BIO's?
 

Alexzee

Well-Known Member
Credits
1,162
I tried to install Slackware via a usb stick.

I typed in /dev/nvme0n1 at the prompt but it returned no such file or directory.

Disk /dev/nvme0n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Since I couldn't install Slackware I tried to install Mint and it worked. Mint's installer saw the nvme drive but the Slackware installer is not seeing the M.2 NVMe drive.

What do I type at the prompt during the Slackware installation in order to install Slackware to the NVME drive?
 

Alexzee

Well-Known Member
Credits
1,162
Do I need to use gparted and partition the NVME Drive first in order to install Slackware?
 

Alexzee

Well-Known Member
Credits
1,162
I tried once again to install Slackware to the M.2 NVME drive telling the installer to install to:
/dev/nvme0n1 and it returned permission denied.

I also tried to install Debian 10 and the installer got stuck at the Configure the Network screen.

Anyone have any clue what's going on?
 

atanere

Well-Known Member
Credits
0
The -current Slackware builds support nvme, but the 14.2 base does not. I found a thread on another forum (about 4 pages long). You can dig through the whole thing, but at the end of it, one person summarizes to follow the simplified steps in his post here. It describes a UEFI setup, but also says you can simplify it further if you choose BIOS (Legacy) mode instead. The same person also offered this link to Alien Bob's blog with detailed instructions for a UEFI install.

Slackware, Arch, Gentoo, even Debian (if not using non-free edition).... these can be difficult, but you can learn a lot if you can manage to get them up and running (and keep them running). But this struggle is why Ubuntu and Linux Mint have come into being... for lazy people, like me. o_O:D

Cheers
 
Last edited:

Alexzee

Well-Known Member
Credits
1,162
Thank you atanere I'll keep trying and hope for the best.

If I have to I could install Mint to the NVMe drive and install Slackware to either my 500 GBWD or my ! TB Seagate drive. I was hoping to install Slackware to my M.2 drive.
 

Alexzee

Well-Known Member
Credits
1,162
Slackware is now installed-:)

The whole installation was very difficult as I only had 1/2 of the screen showing me my options to choose from. I had to follow this video and it was a big help.

 

Alexzee

Well-Known Member
Credits
1,162
It looks like slpkg is much eaiser to use than slackpkg.

So if I understand you correctly, I can use slpkg to install any pkg that I want and if it has other dependencies I don't have to manually install them, right?
 

Alexzee

Well-Known Member
Credits
1,162
It's installed-:)

Executing install script for slpkg-3.4.3-x86_64-1_SBo.tgz.
Package slpkg-3.4.3-x86_64-1_SBo.tgz installed.
 

captain-sensible

Well-Known Member
Credits
1,189
It looks like slpkg is much eaiser to use than slackpkg.

So if I understand you correctly, I can use slpkg to install any pkg that I want and if it has other dependencies I don't have to manually install them, right?
Basically yes, there are a couple of Caveats which i might get to later .
lets take an example. there is a command in slpkg :
# slpkg repo-enable
//that allows you to pick repo's that have packages; but its a gui so you need

python2-pythondialog

that is available via sbo and i think thats a default repo in slpkg.

So try this: # slpkg -F python2-pythondialog
// F is the find flag, you should see on executing this command that , that packge is found in sbo .

To install it use: # slpkg -s sbo python2-pythondialog
 
Last edited:

captain-sensible

Well-Known Member
Credits
1,189
because your using current open this file in nano or vim : /etc/slpkg/slpkg.conf

look for this line:
# Set Slackware release "stable" or "current". Default is "stable".
after it ,you should see:
RELEASE=stable

chnage it to :
RELEASE=current

now you can execute
# slpkg repo-enable
 

captain-sensible

Well-Known Member
Credits
1,189
i'm quite greedy as well as lazy, so i think i've got all enabled. Now then
lets say you want to install cinelerra video editor
you use F flag to look to see if its available:

ash-5.0# slpkg -F cinelerra

Packages with name matching [ cinelerra ]

+==============================================================================
| Repository Package Size
+==============================================================================
sbo cinelerra-2.3 0 K
slonly cinelerra-2.3-x86_64-6_slonly.txz 10424 K

Found summary
===============================================================================
Total found 2 packages in 2 repositories.

bash-5.0#
 

captain-sensible

Well-Known Member
Credits
1,189
i just looked in my /var/log/packages and i have :
cinelerra-2.3-x86_64-6_slonly

I can tell you that there is a small element of trial and error sometimes.
Anyway lets have a look at deps for cinelerra

bash-5.0# slpkg -t slonly cinelerra --graph=cinelerra.jpg

it shows what you have and whats missing ;also a nice graph

now if you use :

# slpkg -s slonly cinelerra
// syntax is -s (install) slonly (repo you will use ) cinelerra (packge you want)
//it should install not just that package but all its deps.
 

Attachments

captain-sensible

Well-Known Member
Credits
1,189
sometimes its a small effort of trial and error due to deps on one package being replaced when you install a new package and it replaces a "common" dep but maybe older version. Really i've had next to no trouble with it .
 

captain-sensible

Well-Known Member
Credits
1,189
the small caveat is that say when you build "clamav" during the build it will tell you , you need groups setting up before the build. So i usually go to slackbuilds and read the read me. eg clamav at slackbuilds says for clamav:



You must have the 'clamav' group and user

so i did this:

# groupadd -g 210 clamav
# useradd -u 210 -d /dev/null -s /bin/false -g clamav clamav

then i just used slpkg to install clamav , i have : clamav-0.101.4-x86_64-1_SBo

when it installed i ran : #freshclam
//that was a quick test to see if it updated virus sigs, it did !
 

captain-sensible

Well-Known Member
Credits
1,189
what i can say is that I have been running current for a few months now using exclusively slpkg , couple of small trial and error , when one package from one repo didn't work i just removed it , with deps and tried another. I have chromium, clamav, libreoffice5, cinelerra , geany and a few others and all installed seamlessly.
 


Members online


Latest posts

Top