LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 09-03-2017, 10:27 AM   #1
Launfal
Member
 
Registered: Jun 2014
Location: Ohio, USA
Posts: 65

Rep: Reputation: 49
More noob coolness


OK, so I just inherited my kid's Athlon X4 and I threw Slack 14.2 on it, but Xorg kept crashing with the Noveau drivers, so I had to figure out how to build and use the Nvidia drivers from Slackbuilds. The office comp is all Intel, so the drivers are fine in there. A couple of trials and error, and Slack is solid as ever. This rig's in the living room so I can watch Twitch and stuff when I'm not writing the next great American novel. TTY's are 80x24, but nothing in life is perfect.

Speaking of the other rig, I wanted to update the Intel microcode in there, so I did some searching and found the process. More Slackbuilds, but this time the trick was to build AND install the iucode program before I build the microcode. Otherwise, the intel file I needed in boot wouldn't appear. That was just from not paying more attention to the instructions. Oh, and according to the Gentoo guys, microcode_ctl is deprecated, so I didn't end up using that.

So, once again, there was something I wanted to do and Slack just did it, once I understood what it was I wanted. Video drivers and microcodes are stuff that I've never tried to use before, but when a distro makes it this easy to learn and do new stuff, somebody did something right when they put it together.

Oh, and speaking of novels, anytime you need a quick PDF that works anywhere, forget Pandoc. Just grab text2html from SlackBuilds, and build it. Then throw some Control-L's where you want pagebreaks, and voila, instant PDF with pages. 7-bit PDF's, but I got better things to do with my time than spend time formatting stuff for books I just give away anyway.

BTW, ratpoison on a 1920x1200 is the rat's pajamas. More real estate than on 1920x1080, and Tmux means it's completely mouseless (startx -- -nocursor ftw). I just wished I hadn't waited so long for the upgrade.

That's about all the irrelevant stuff I can think of for now. One of these days I'll do something that everyone else hasn't already been doing for years, and then I'll really be something.

Stay cool, and keep Slacking
Launfal
 
Old 09-03-2017, 09:57 PM   #2
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,230
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
sorry I stop reading at nvidia slackbuilds. That is not the slackware way acording to the slackware documents. Slackbuilds on that build does not conform to Slackware.
https://docs.slackware.com/howtos:ha...aphics_drivers
you will find your self down the rode with a switch that never switches. Slackware is KISS slackbuilds is wonderful but not always the Slackware way. Ok going to read the rest reply later.
Nvidia gives you an option during install to blacklist just like slackware wants. why because Slackware is built to run programs vanilla
That means a programer spent years working on something to run stable so let it run stable on slackware. KISS

Last edited by Drakeo; 09-03-2017 at 10:02 PM. Reason: Nvidia has built in option for blacklist
 
Old 09-03-2017, 10:47 PM   #3
jmccue
Member
 
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 259

Rep: Reputation: 126Reputation: 126
Quote:
Originally Posted by Drakeo View Post
That is not the slackware way acording to the slackware documents. Slackbuilds on that build does not conform to Slackware.
Granted I do not fully understand what your post is saying about slackbiulds, but please see Linux Questions

As for me, when I set up a new box with Slackware I know I do things not "the Slackware way". But that is the best thing about Slackware. I can easily do things on Slackware (my way) that range from difficult to next to impossible in most distro
 
3 members found this post helpful.
Old 09-03-2017, 11:38 PM   #4
Launfal
Member
 
Registered: Jun 2014
Location: Ohio, USA
Posts: 65

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by Drakeo View Post
sorry I stop reading at nvidia slackbuilds. That is not the slackware way acording to the slackware documents. Slackbuilds on that build does not conform to Slackware.
https://docs.slackware.com/howtos:ha...aphics_drivers
OK, color me confused. That docs link describes two methods of installing the Nvidia drivers, and the SBo instructions are what I did: Download the legacy drivers with dependencies and run the SlackBuilds. If I read the official docs and follow the instructions, which part of the Slackware Way do I not conform to?
 
Old 09-04-2017, 12:20 AM   #5
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,230
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by Launfal View Post
OK, color me confused. That docs link describes two methods of installing the Nvidia drivers, and the SBo instructions are what I did: Download the legacy drivers with dependencies and run the SlackBuilds. If I read the official docs and follow the instructions, which part of the Slackware Way do I not conform to?
Not conform your learning slackware linux. Slackbuilds is a wonderful tool and like many things if you do not understand slackware and linux you can break a ton of stuff using slackbuilds. conform is not what i mean sorry I said slackware way is documented slackbuilds. is another path. alien bob slackbuilds is anopther path. then you have Patricks path since you bring this up. it is very simple since you use a legacy driver some may need patched look at the patch where did it come from and how was it made. and why was it made. If you have a legacy device that needs patching for a newer version of xorg most of the times your just telling the installer to not see the problem. Keep it simple. do you really need qt5 from slackbuilds for many things no. but they push it down your throat. learn what slackbuilds is and understand has very little to do with slackware way. It is a great tool use it as you need i do.

Last edited by Drakeo; 09-04-2017 at 12:27 AM.
 
Old 09-04-2017, 03:05 AM   #6
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 504

Rep: Reputation: 210Reputation: 210Reputation: 210
My advice is to carefully follow the instructions (nvidia-switch) if you decide to remove the SBo nvidia driver. I just use the nvidia run file and use the slackbuild when that doesn't work. Also with slackpkg blacklist xf86-video-nouveau and [0-9]+_SBo if you haven't (which I suspect you probably have).

There are a lot of nice repositories in this community.
 
Old 09-04-2017, 07:08 AM   #7
Launfal
Member
 
Registered: Jun 2014
Location: Ohio, USA
Posts: 65

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by RadicalDreamer View Post
My advice is to carefully follow the instructions (nvidia-switch) if you decide to remove the SBo nvidia driver. I just use the nvidia run file and use the slackbuild when that doesn't work. Also with slackpkg blacklist xf86-video-nouveau and [0-9]+_SBo if you haven't (which I suspect you probably have).
Yeah, blacklist-nouveau is installed. I saw the instructions for nvidia-switch, but on this machine, Xorg will crash without the binary driver. Every time. I was just about to try one of the 'Buntus before I checked out SlackDocs and gave building the drivers a shot.

Quote:
Originally Posted by RadicalDreamer View Post
There are a lot of nice repositories in this community.
There sure are. I prefer to build everything I use locally, but for some of the heavy monsters, it's nice to know that there are repos I can trust to find a pre-built binary.
 
1 members found this post helpful.
Old 09-04-2017, 01:43 PM   #8
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 504

Rep: Reputation: 210Reputation: 210Reputation: 210
There is also /etc/slackpkg/blacklist which prevents slackpkg from installing/removing packages.
 
Old 09-04-2017, 06:41 PM   #9
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,517

Rep: Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466Reputation: 1466
Just FTR, I too prefer and have done for going on 17 years, dropping to runlevel 3 and running nVidia's run file installer. I like that it is an interactive install asking me, for example, if I want to install the 32 bit compatibility drivers and that it comes with glx and mesa that works with each driver. I always build a custom kernel sans initrd and I have never had nVidia's installer fail on me as long as I had the correct driver. In the past several years even that has become easier with nVidia's manual search function where one enters either 32 bit or 64bit Linux and selects the appropriate video card.

It even handles uninstalling previous ones before installing upgrades so I see no reason, especially on a system that doesn't require KMS, for employing a Slackbuild. I choose nVidia exactly because they are longtime veterans at "alternate" operating systems. I support them because they have never failed to support my needs. Despite Linus' and others' complaints, nVidia does it right in my book. I love OSS but it has always been my understanding that the GPL promotes coexistence, and I think that's a good thing.
 
2 members found this post helpful.
Old 09-04-2017, 09:29 PM   #10
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 550
Blog Entries: 1

Rep: Reputation: 231Reputation: 231Reputation: 231
Quote:
Originally Posted by enorbet View Post
Just FTR, I too prefer and have done for going on 17 years, dropping to runlevel 3 and running nVidia's run file installer. I like that it is an interactive install asking me, for example, if I want to install the 32 bit compatibility drivers and that it comes with glx and mesa that works with each driver. I always build a custom kernel sans initrd and I have never had nVidia's installer fail on me as long as I had the correct driver. In the past several years even that has become easier with nVidia's manual search function where one enters either 32 bit or 64bit Linux and selects the appropriate video card.
Before I even knew of the existence of SlackBuilds for NVIDIA's driver, I was using this exact method. In my experience, this is the simplest method to install a new driver, or have an old one link to a newly-compiled kernel. It has the advantage that the installation and upgrade paths are relatively clean, and there's no messy files left behind.

Quote:
It even handles uninstalling previous ones before installing upgrades so I see no reason, especially on a system that doesn't require KMS, for employing a Slackbuild. I choose nVidia exactly because they are longtime veterans at "alternate" operating systems. I support them because they have never failed to support my needs. Despite Linus' and others' complaints, nVidia does it right in my book. I love OSS but it has always been my understanding that the GPL promotes coexistence, and I think that's a good thing.
As some of you know, I upgraded from an ASUS R9 270 to a pair of NVIDIA GTX 970 in SLI, and have since had no reason to regret my purchase. NVIDIA's engineers have done a superb job of implementing hardware and software, and there's nothing of significance that I would have changed. I will probably upgrade to the 10xx series once I upgrade to Ryzen. Of course, by then, NVIDIA's architecture would probably have progressed by several orders of magnitude, but that's technology for you.

There's nothing wrong with coexistence, and as long as it gets the job done, it can be considered a good thing (TM).

Happy Slacking!

Last edited by 1337_powerslacker; 09-04-2017 at 09:57 PM. Reason: Clarity
 
Old 09-08-2017, 06:49 PM   #11
Launfal
Member
 
Registered: Jun 2014
Location: Ohio, USA
Posts: 65

Original Poster
Rep: Reputation: 49
As an update, on the advice of several in this thread, I backtracked the Nvidia drivers I had built and downloaded the legacy Nvidia installer and ran it.

Never having used it before, I have to admit, that was as painless as it gets. Answer a few simple questions then let it do its thing.

Chalk one up for living and learning. Thanks everybody for the heads up.
 
1 members found this post helpful.
Old 09-08-2017, 09:00 PM   #12
slac-in-the-box
Member
 
Registered: Mar 2010
Location: oregon
Distribution: slackware64-14.2
Posts: 218

Rep: Reputation: 87
I like slackware because of it's package system, and when slackbuild.org doesn't have a build, or when it's build failed or didn't work, I've rolled my own packages--except for nvidia. Like Enorbet, I've just used their .run file and it's always worked... It kind of irritates me though--just not the slackware way--no entry in /var/log/packages, etc. I've wondered if it would be possible to install slackware into a folder; install it again into a second folder, and copy the .run script to second folder; chroot into second folder, execute the .run script, and then exit the chroot. Wouldn't a diff between the two folders reveal every change the .run script made. Then couldn't I make a /tmp/nvidia folder, duplicate the slackware file system in /tmp/nvidia, and copy the changes to the appropriate directories in that file system; give it a slack-desc and an .install, and then use makepkg?

Seemed conceivable... but haven't had time to try yet...

Has anyone else ever built a package from some 3rd party .run script this way?
 
Old 09-08-2017, 09:11 PM   #13
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,527

Rep: Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463Reputation: 2463
Quote:
Originally Posted by slac-in-the-box View Post
I like slackware because of it's package system, and when slackbuild.org doesn't have a build, or when it's build failed or didn't work, I've rolled my own packages--except for nvidia. Like Enorbet, I've just used their .run file and it's always worked... It kind of irritates me though--just not the slackware way--no entry in /var/log/packages, etc. I've wondered if it would be possible to install slackware into a folder; install it again into a second folder, and copy the .run script to second folder; chroot into second folder, execute the .run script, and then exit the chroot. Wouldn't a diff between the two folders reveal every change the .run script made. Then couldn't I make a /tmp/nvidia folder, duplicate the slackware file system in /tmp/nvidia, and copy the changes to the appropriate directories in that file system; give it a slack-desc and an .install, and then use makepkg?

Seemed conceivable... but haven't had time to try yet...

Has anyone else ever built a package from some 3rd party .run script this way?
I don't know about building a script, but I do know 55020 uses a similar method on his slackrepo program and builds everything inside a chroot, but he still uses normal packaging methods and then checks the chroot for to see if there's any files that were modified that shouldn't have been (in general, pretty much anything outside of the build and packaging directories should be off limits to changes by compiling programs).
 
1 members found this post helpful.
  


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
LXer: The sheer coolness of TrackingPoint’s Mile Marker Linux rifle LXer Syndicated Linux News 0 01-09-2015 09:39 PM
Howto: LiveCD/DVD with ramdisk coolness uppman Slackware 22 05-05-2010 04:55 PM
LXer: Linux coolness: Linux Cooler, Linux serves you beer LXer Syndicated Linux News 0 03-09-2010 01:50 PM
PS3 YDL NOOB (linux NOOB completly) korn_16_f_t_l Linux - Newbie 1 07-09-2008 12:32 PM
Complete noob question from a noob noob_hampster Linux - Software 2 09-04-2003 01:03 AM

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

All times are GMT -5. The time now is 02:00 PM.

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