Linux Mint Guide

4,000 · March 26, 2016

7 hours ago, T3X4S said:

I spoke too soon - it is locking up like crazy.

Before it completely locks up I cant open any programs.

I'd like to say I will work through it and try to fix it but dont know where/how to begin.

it's always difficult to make any diagnosis that way but it could be that your running out of ram and your tmpfs is too small. how much ram do you have and please show the output of:

df -h

in terminal

7,082 · March 27, 2016

24GB of RAM -
its on a 500GB Samsung 950 Pro - I gave it a 4GB swap partition.

Going out to eat - I'll check it out tonight when I get back - I need an excuse to not go out afterwards - I can say I have work to do

4,806 · March 27, 2016

It's odd that it's misbehaving so much for you. Perhaps Ubuntu 16.04 will have the fixes and stability updates you'll need. I have a machine with a GTX 950 here that I can test the driver on, maybe I can replicate the issues myself and figure out how to deal with them. :yes:

7,082 · March 27, 2016

7 minutes ago, Unobscured Vision said:

It's odd that it's misbehaving so much for you. Perhaps Ubuntu 16.04 will have the fixes and stability updates you'll need. I have a machine with a GTX 950 here that I can test the driver on, maybe I can replicate the issues myself and figure out how to deal with them.

Well - if you get bored and decide to test it out.

Once I added nomodeset after the splash command in GRUB and was able to get to a desktop - I selected the latest nVidia driver that was presented when I went into Driver Manager - it had issues.
Did a reinstall and tried the other nVidia driver (same version but it said "updates" in the title) - to no avail

Since you have same gen - maybe you will see what the weirdness is.

Whats crazy is when it locks up, and I wait long enough it will let me restart - but it wont reboot the computer - it will drop me to a tty login prompt and mention :

blk update request: I/O error

over and over again

4,806 · March 27, 2016

Try removing the nomodeset from your GRUB command. I've never had to use that, even when on the older driver for my 750ti -- that's Maxwell too, same as your 950.

Just a stab in the dark. I know guides have said use 'nomodeset'; my experience says don't use it because I've never had to.

I'm going to fire up the PC with the 950 in it and see what's what when my nephew gets home. It's his computer. He won't mind making a small partition for testing purposes, he's been wanting to do some testing with Linux anyway. :yes:

4,806 · March 27, 2016

7 minutes ago, T3X4S said:

Well - if you get bored and decide to test it out.

Once I added nomodeset after the splash command in GRUB and was able to get to a desktop - I selected the latest nVidia driver that was presented when I went into Driver Manager - it had issues.
Did a reinstall and tried the other nVidia driver (same version but it said "updates" in the title) - to no avail

Since you have same gen - maybe you will see what the weirdness is.

Whats crazy is when it locks up, and I wait long enough it will let me restart - but it wont reboot the computer - it will drop me to a tty login prompt and mention :

blk update request: I/O error

over and over again

Which driver are you using? nvidia-352-updates (aka nvidia-352.63-0ubuntu0.14.04.1) in the Driver Manager? And which Linux Kernel? The stock 3.19.0-32?

7,082 · March 27, 2016

2 hours ago, Unobscured Vision said:

Which driver are you using? nvidia-352-updates (aka nvidia-352.63-0ubuntu0.14.04.1) in the Driver Manager? And which Linux Kernel? The stock 3.19.0-32?

Yes sir - that is the 2nd one I tried, the first one was the 352.63 that didnt say "updates"

As for the kernel - I want to try and update now - Im gonna bounce into linux and see what happens -

7,082 · March 27, 2016

2 hours ago, Unobscured Vision said:

Try removing the nomodeset from your GRUB command. I've never had to use that, even when on the older driver for my 750ti -- that's Maxwell too, same as your 950.

Just a stab in the dark. I know guides have said use 'nomodeset'; my experience says don't use it because I've never had to.

I'm going to fire up the PC with the 950 in it and see what's what when my nephew gets home. It's his computer. He won't mind making a small partition for testing purposes, he's been wanting to do some testing with Linux anyway.

I cant get past GRUB if I dont put nomodeset in there. It will just sit at a black screen - even "disconnecting" the monitor connection from the computer - so the monitor goes into sleep mode.

1,725 · March 27, 2016

2 hours ago, Unobscured Vision said:

And which Linux Kernel? The stock 3.19.0-32?

I'm using the stock kernel, everything seems to be working well, all except wifi, now it did drop out with Windows, so I know that's not the problem, but the wifi loses all signals and yet it's turned on. Do you think upgrading the kernel may fix that?

7,082 · March 27, 2016

Right now it is the stock kernel:

Linux mint 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I see the latest stable is 4.5 - I am looking @ the instructions to update it.

7,082 · March 27, 2016

13 hours ago, Simon Lang 9047 said:

df -h

in terminal

Filesystem Size Used Avail Use% Mounted on
udev 5.9G 4.0K 5.9G 1%      /dev
tmpfs 1.2G 1.6M 1.2G 1%     /run
/dev/sdb5 21G 6.0G 14G 31% /
none 4.0K 0 4.0K    0%    /sys/fs/cgroup
none 5.0M 0 5.0M    0%   /run/lock
none 5.9G 27M 5.9G 1% /run/shm
none 100M 12K 100M 1% /run/user

7,082 · March 27, 2016

So I guess this isnt good:

Selecting previously unselected package linux-headers-4.5.0-040500.
(Reading database ... 164779 files and directories currently installed.)
Preparing to unpack linux-headers-4.5.0-040500_4.5.0-040500.201603140130_all.deb ...
Unpacking linux-headers-4.5.0-040500 (4.5.0-040500.201603140130) ...
Selecting previously unselected package linux-headers-4.5.0-040500-generic.
Preparing to unpack linux-headers-4.5.0-040500-generic_4.5.0-040500.201603140130_amd64.deb ...
Unpacking linux-headers-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Selecting previously unselected package linux-image-4.5.0-040500-generic.
Preparing to unpack linux-image-4.5.0-040500-generic_4.5.0-040500.201603140130_amd64.deb ...
Done.
Unpacking linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Setting up linux-headers-4.5.0-040500 (4.5.0-040500.201603140130) ...
Setting up linux-headers-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/bbswitch/0.7/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.0.4/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/nvidia-352-updates/352.63/build/make.log for more information.
Setting up linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/bbswitch/0.7/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.0.4/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.5.0-040500-generic (x86_64)
Consult /var/lib/dkms/nvidia-352-updates/352.63/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
update-initramfs: Generating /boot/initrd.img-4.5.0-040500-generic
Warning: No support for locale: en_US.utf8
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.5.0-040500-generic
Found initrd image: /boot/initrd.img-4.5.0-040500-generic
Found linux image: /boot/vmlinuz-3.19.0-32-generic
Found initrd image: /boot/initrd.img-3.19.0-32-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
No volume groups found
Found Windows 10 (loader) on /dev/sdb1

4,806 · March 27, 2016

I've had problems with using anything past Kernel 4.2 on 14.04 (the Ubuntu that Mint 17.x is built on). I got all kinds of errors related to DKMS and other drivers much like you're seeing. I know, I know -- that shouldn't be happening, and it's stupid that it happens at all. There's an incompatibility in the DKMS of Kernels newer than 4.2, Nvidia Drivers and Ubuntu 14.04 that I was never able to sort out, so I stopped trying and stuck to the 4.2 Kernel (which did work).

That could also be why the proprietary driver can't load, so it tries falling back to the Nouveau driver and that's why you can't get started without nomodeset. I haven't had the chance to test yet on my end to see or not.

And it's likely a dumb question but it bears asking (because I had this problem in the past) -- you're connecting your monitor using HDMI or DVI? I'm sorry to pester you with questions; but specifics matter.

4,806 · March 27, 2016

2 hours ago, Thomas the Tank Engine said:

I'm using the stock kernel, everything seems to be working well, all except wifi, now it did drop out with Windows, so I know that's not the problem, but the wifi loses all signals and yet it's turned on. Do you think upgrading the kernel may fix that?

Yeah, most likely. I wouldn't go past Kernel 4.2 though, for the reasons I specified previously. You can always try out newer ones, and if they don't work install an older one. :yes:

4,000 · March 27, 2016

i have to say sorry then for suggesting the latest kernel update, not knowing what mint is based on. i probably stole +T3X4S a lot of time.

1,725 · March 27, 2016

19 minutes ago, Unobscured Vision said:

Yeah, most likely. I wouldn't go past Kernel 4.2 though, for the reasons I specified previously. You can always try out newer ones, and if they don't work install an older one.

Which 4.2 do you have? I am asking because the instructions on the site are for 4.2.5.

4,000 · March 27, 2016

Just now, Thomas the Tank Engine said:

Which 4.2 do you have? I am asking because the instructions on the site are for 4.2.5.

well he probably means 4.2 exactly.

7,082 · March 27, 2016

1 hour ago, Unobscured Vision said:

I've had problems with using anything past Kernel 4.2 on 14.04 (the Ubuntu that Mint 17.x is built on). I got all kinds of errors related to DKMS and other drivers much like you're seeing. I know, I know -- that shouldn't be happening, and it's stupid that it happens at all. There's an incompatibility in the DKMS of Kernels newer than 4.2, Nvidia Drivers and Ubuntu 14.04 that I was never able to sort out, so I stopped trying and stuck to the 4.2 Kernel (which did work).

That could also be why the proprietary driver can't load, so it tries falling back to the Nouveau driver and that's why you can't get started without nomodeset. I haven't had the chance to test yet on my end to see or not.

And it's likely a dumb question but it bears asking (because I had this problem in the past) -- you're connecting your monitor using HDMI or DVI? I'm sorry to pester you with questions; but specifics matter.

Actually I am connecting through DisplayPort.... should I change to HDMI ?

47 minutes ago, Simon Lang 9047 said:

i have to say sorry then for suggesting the latest kernel update, not knowing what mint is based on. i probably stole +T3X4S a lot of time.

Absolutely not - you are only trying to help - and I am learning things in the process. This is how I have learned everything I know about computers. Trial and error and reading suggestions from those more knowledgeable - so no apology needed.

4,806 · March 27, 2016

39 minutes ago, T3X4S said:

Actually I am connecting through DisplayPort.... should I change to HDMI ?

No, DP should be fine. I'll consult the documentation, but I've never heard of DP causing any trouble or being handled any differently than HDMI. We'll keep that on the back burner as a possibility though.

1 hour ago, Simon Lang 9047 said:

i have to say sorry then for suggesting the latest kernel update, not knowing what mint is based on. i probably stole +T3X4S a lot of time.

Nah, you're trying to help. No apologies necessary.

1 hour ago, Thomas the Tank Engine said:

Which 4.2 do you have? I am asking because the instructions on the site are for 4.2.5.

1 hour ago, Simon Lang 9047 said:

well he probably means 4.2 exactly.

4.2.0-22 is the one I have. That was the newest 4.2 series Kernel when I installed Mint back in September or October of last year. I'm showing a lot of newer ones in the list now, going up to 4.2.0-34 and then it jumps to 4.4.0-13. I'm going to try that one -- any of them that show up in the list are supposed to be built, tested and uploaded by the Mint Developers personally. If the 4.4 works without errors I'll stick to that one and pass the info along. (I still wanna know how you got 4.5 ... did you download it yourself?)

7,082 · March 27, 2016

Im watching some Daredevil episodes on Netflix - as soon as this one is over - I'll bounce over to mint and see if that failed kernel update ruined it.

4,806 · March 27, 2016

No rush, I'm going to install the 4.4.0-13 shortly and see how many DKMS errors I can generate. :laugh:

1,725 · March 27, 2016

8 minutes ago, Unobscured Vision said:

4.2.0-22 is the one I have. That was the newest 4.2 series Kernel when I installed Mint back in September or October of last year. I'm showing a lot of newer ones in the list now, going up to 4.2.0-34 and then it jumps to 4.4.0-13. I'm going to try that one -- any of them that show up in the list are supposed to be built, tested and uploaded by the Mint Developers personally. If the 4.4 works without errors I'll stick to that one and pass the info along.

This is the command from Mint Guide (https://mintguide.org/system/507-install-linux-kernel-4-2-5-stable-on-linux-mint.html):

cd /tmp; wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.5-wily/linux-headers-4.2.5-040205-generic_4.2.5-040205.201510270124_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.5-wily/linux-headers-4.2.5-040205_4.2.5-040205.201510270124_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.5-wily/linux-image-4.2.5-040205-generic_4.2.5-040205.201510270124_amd64.deb; sudo dpkg -i *.deb

So, we'd need the exact version you used if we want to change the above to get 4.2.0-22.

4,806 · March 27, 2016

Or use the Mint Update Manager in the System Tray, View and then Linux Kernels. Scroll down, click the one you want, then install.

1,725 · March 27, 2016

1 minute ago, Unobscured Vision said:

Or use the Mint Update Manager in the System Tray, View and then Linux Kernels. Scroll down, click the one you want, then install.

Didn't know you could get kernels listed. Thanks.

The most recent one that is showing is:

4.4.0-13

The 3.x & 4.2 kernels are still listed, but the aforementioned one should be given a try.

4,806 · March 27, 2016

1 minute ago, Thomas the Tank Engine said:

Didn't know you could get kernels listed. Thanks.

The most recent one that is showing is:

4.4.0-13

The 3.x & 4.2 kernels are still listed, but the aforementioned one should be given a try.

Not a problem. :yes:

I've just installed the 4.4.0-13 -- it generated errors on ndiswrapper and vbox host drivers (so I'll need to reinstall Virtualbox, no big deal). The ndiswrapper isn't that big of a deal to me, but someone using Windows Wireless Drivers on 'nix might be annoyed by that one.

Gonna restart the system and see how the 4.4 behaves.

Sign In

Linux Mint Guide

Recommended Posts

simonlang

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Thomas the Tank Engine

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

simonlang

Link to comment

Share on other sites

Thomas the Tank Engine

Link to comment

Share on other sites

simonlang

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

T3X4S

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

Thomas the Tank Engine

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

Thomas the Tank Engine

Link to comment

Share on other sites

Unobscured Vision

Link to comment

Share on other sites

Recently Browsing 0 members