Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 am running 14.2 kernel-huge-4.4.17 on a Sager NP-9778-S and everything is working fine for me.
I started out on Feb 8 with huge-4.4.1 and I've kept up to date via `installpkg` as Pat has released new Kernels.
I had some early issues with lilo and trying to boot from my Samsung NVMe / PCIe SDD so I installed root on a Samsung 850 Pro SDD instead ( /dev/sda3 ).
I did have to disable nouveau to get to runlevel 3 ( I appended nomodeset to the kernel parms as recommended by SeB ).
Once I was able to boot runlevel 3, I did an `installpkg xf86-video-nouveau-blacklist-noarch-1.txz` from the ~/slackware-14.2-64/extra/xf86-video-nouveau-blacklist/ directory.
Then I installed Alien Bob's Multilib.
Finally, I was able to install NVIDIA-Linux-x86_64-VVV.vv.run, both 64-bit and 32-bit ( today I am at VVV.vv = 367.35 ).
Looking at your dmesg vs mine, aside from a few HW and memory diffs, the most obvious differences are the nouveau lines at 5.297736 secs and then the block of lines starting at 7.277448 sec.
HTH and please let us know.
-- kjh
Last edited by kjhambrick; 08-15-2016 at 01:45 PM.
Reason: oops nomodeset was a kernel parm on first boot
I am running 14.2 kernel-huge-4.4.17 on a Sager NP-9778-S and everything is working fine for me.
I started out on Feb 8 with huge-4.4.1 and I've kept up to date via `installpkg` as Pat has released new Kernels.
I had some early issues with lilo and trying to boot from my Samsung NVMe / PCIe SDD so I installed root on a Samsung 850 Pro SDD instead ( /dev/sda3 ).
I did have to disable nouveau to get to runlevel 3 ( I appended nomodeset to the kernel parms as recommended by SeB ).
Once I was able to boot runlevel 3, I did an `installpkg xf86-video-nouveau-blacklist-noarch-1.txz` from the ~/slackware-14.2-64/extra/xf86-video-nouveau-blacklist/ directory.
Then I installed Alien Bob's Multilib.
Finally, I was able to install NVIDIA-Linux-x86_64-VVV.vv.run, both 64-bit and 32-bit ( today I am at VVV.vv = 367.35 ).
Looking at your dmesg vs mine, aside from a few HW and memory diffs, the most obvious differences are the nouveau lines at 5.297736 secs and then the block of lines starting at 7.277448 sec.
HTH and please let us know.
-- kjh
Interesting, thank you for the feedback.
I'm going to try a different installation media (hardware). I'm also installing on Samsung 850 Pro SSD.
I will blacklist nouveau and see if that helps, but traditionally speaking, the nvidia installer should still launch (it's NCURSES I think) and should attempt to disable nouveau automatically.
Sorry, you said lilo and seemed to have issues with mbr, lilo, and where Slackware booted from. EFI requires elilo and you mentioned dual booting with Windows.
Anyway, I would remove the nouveau driver package (not the blacklisted one) and not allow updates to pull it back in.
Last edited by RadicalDreamer; 08-15-2016 at 02:14 PM.
Sorry, you said lilo and seemed to have issues with mbr, lilo, and where Slackware booted from. EFI requires elilo and you mentioned dual booting with Windows.
Anyway, I would remove the nouveau driver package (not the blacklisted one) and not allow updates to pull it back in.
Another difference I just now noticed in your dmesg is that you've got i915 ( Intel Video ) where I don't.
I was disappointed the other day that I didn't have Intel i915 because I wanted to play around with bumblebee.
I am running a Data Conversion so I can't reboot right now to investigate and I don't recall whether I disabled it in my BIOS or not but that may be causing you some grief with the NVidia Installer.
I don't know much about bumblebee ( which is why I wanted to play with it ) but maybe others do.
Another difference I just now noticed in your dmesg is that you've got i915 ( Intel Video ) where I don't.
I was disappointed the other day that I didn't have Intel i915 because I wanted to play around with bumblebee.
I am running a Data Conversion so I can't reboot right now to investigate and I don't recall whether I disabled it in my BIOS or not but that may be causing you some grief with the NVidia Installer.
I don't know much about bumblebee ( which is why I wanted to play with it ) but maybe others do.
-- kjh
I'm learning about Bumblebee now. This was my next step on Slackware, as I don't want to run the NVIDIA 24/7. I'm having some issues on Debian (with bumblebee), and so I haven't gotten around to testing it on Slackware yet, but if I can get Slackware installed and running, Bumblebee is next. :-)
I've got an Intel i7-6700K so I thought the i915 should be there.
I don't recall anymore if I turned off the Intel i915 in my BIOS or not or if Sager somehow disabled it for me ( my Feb 8 Install Date seems like a long time ago now ).
But this is 'on my list' so I can play with bumblebee.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.