LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 12-04-2015, 11:29 PM   #16
bimboleum
Member
 
Registered: Oct 2009
Posts: 111

Rep: Reputation: 23

Hi,
Have you tried a different distribution? I have a w530 running Slackware 14.1 and using the nouveau driver and I have seen no problems. I realise we are talking apples and oranges here, but try a different recent distribution and see if you get the same behaviour.

cheers
pete

ps i am in SV too so if you want to try a different distribution, bring your laptop over and we can slot in a different harddrive with Slackware on it.
 
Old 12-05-2015, 05:56 AM   #17
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
I have no idea what watchdog is. It might be that Debian 8 has it enabled by standard, I do not know. It is the first time I hear about that mechanism.
But you are right, I should have reacted and asked about that point.

Last edited by browny_amiga; 12-05-2015 at 06:03 AM.
 
Old 12-06-2015, 08:41 AM   #18
Germany_chris
Senior Member
 
Registered: Jun 2011
Location: Wiesbaden, Germany
Distribution: Arch
Posts: 1,053

Rep: Reputation: 492Reputation: 492Reputation: 492Reputation: 492Reputation: 492
You're going to say no because you ran a 5 hour test but every computer I've had that acted like yours was bad RAM no matter what the Mem test said. If you not low just pull a DIMM and go on about life, if it stops happening then you know if it continues swap them out. This computer is not a spring chicken by any means
 
Old 12-15-2015, 11:05 AM   #19
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
Quote:
Originally Posted by Germany_chris View Post
You're going to say no because you ran a 5 hour test but every computer I've had that acted like yours was bad RAM no matter what the Mem test said. If you not low just pull a DIMM and go on about life, if it stops happening then you know if it continues swap them out. This computer is not a spring chicken by any means
You know, I have to disagree with you there. No system that I have ever seen in my life, and that is about probably about over a hundred that I have build myself or maintained, server, desktops, laptops etc.. EVER had RAM problems, but came back negative with the standard Linux RAM test. The BIOS test normally does not detect much, but the RAM test that you can run from a life CD does wonders.
RAM problems are really terrible, you also notice them immediately, if you are like me always use pretty much all the ram (and deactivate swap space for more speed, and more risk and fun, living on the edge ;-)
The fact is, I now switched to the proprietary driver from Nvidia and would you look at that, no more kernel panics, so I was right about it being nouveau and not being hardware. Now the crash is just the X server crashing, not the whole system locking up.

by the way, this is what the logs spits out when using nouveau:

Nov 30 01:02:37 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000002 00000029 00000004 00000004 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000003 0000002a 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000004 00000007 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000005 0000000a 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000006 0000000b 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000007 00000008 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000008 00000022 00000002 00000000 00000002
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000009 00000023 00000002 00000000 00000002
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000a 00000027 00000004 00000004 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000b 00000025 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000c 00000024 00000004 00000004 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000d 00000020 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000e 0000002e 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 0000000f 0000003d 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000010 00000019 00000004 00000004 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000011 00000032 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000012 00000034 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000013 00000018 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000014 00000030 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000015 0000003b 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: buf 00000016 00000028 00000002 00000002 00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: ch0: psh 00000000 000001fa0c 0000020058
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x0004721c
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x0fac6881
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00086ff4
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x044c0000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x02260000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00146200
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x40d50000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x000000d5
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00000040
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00000000
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00087240
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x00000898
Nov 30 01:02:38 California /etc/gdm3/Xsession[4258]: nouveau: #0110x0000044c

Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00087650
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000377
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000476b8
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000010
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000476b0
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0000000e
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0004740c
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0007f880
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0004798c
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000029
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047298
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000004
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000479a8
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0004796c
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047414
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0007f300
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0004764c
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047914
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000476ac
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000010
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x001076bc
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x03020100
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x07060504
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x0b0a0908
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x400e0d0c
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00147900
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x01000404
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000004
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000000f1
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00046fd4
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x000475cc
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047988
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x080b040b
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00107540
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047798
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00047660
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x002073c0
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000
Nov 30 04:54:48 California /etc/gdm3/Xsession[1138]: nouveau: #0110x00000000

This is just in one second, the log is 120 MB large, thousands of lines of this.
Also, as I said before, I have just upgraded this laptop to Debian Jessie a week ago, so before it worked flawlessly. Now in my experience, hardware will fail at the very start of a system, not after years of successful usage and no problems. The reason for this seems to be that in electronics, nothing moves, so nothing changes. Either it is bad, and you will notice it at the very start, or it does not happen anymore. Doing bad stuff to your system, for example not cooling it correctly of course is not included in this.
 
Old 12-27-2015, 05:48 PM   #20
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
So I had to downgrade again, nobody could (or wanted) to help me troubleshooting this. And it is definitely, 100 no hardware problem: I am now running Debian Wheezy again (oldstable) and it works flawlessly, no crashes, nothing.
So it looks like you can't run Debian 8 (Jessie) on a Lenovo T61 without massive trouble.
 
Old 12-27-2015, 06:30 PM   #21
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
Quote:
Originally Posted by bimboleum View Post
Hi,
Have you tried a different distribution? I have a w530 running Slackware 14.1 and using the nouveau driver and I have seen no problems. I realise we are talking apples and oranges here, but try a different recent distribution and see if you get the same behaviour.

cheers
pete

ps i am in SV too so if you want to try a different distribution, bring your laptop over and we can slot in a different harddrive with Slackware on it.
I really appreciate it. But I want to stick to Debian for now, I run all machines on it and like the package manager and the (so far) excellent stability.
 
Old 12-27-2015, 07:07 PM   #22
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 6,170
Blog Entries: 21

Rep: Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089
I run Jessie on a t23 with savage graphics. Also a Z60m with intel graphics.

http://www.linuxquestions.org/questi...5/#post5469137

http://www.linuxquestions.org/questi...5/#post5469606

trying to make them crash as a favor for another member here. Not sure why Jessie acts up but not Wheezy on your gear.
Pretty much a wonderment to me.

http://www.thinkwiki.org/wiki/Category:T61

Either you are not the only one experiencing this or this is you.

https://www.mail-archive.com/debian-...sg1381286.html

I roll with vesa on my T23 because Savage graphics chip support is abysmal in the newer releases.
Regression is killing off certain things.
 
Old 12-27-2015, 07:14 PM   #23
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 6,170
Blog Entries: 21

Rep: Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089Reputation: 3089
Digging around. I found you this

Quote:
The 173xx & 96xx nvidia legacy drivers which supported older nvidia cards were removed from the repos while Jessie was in development because they lack support for the 1.16 Xorg version that Jessie is using. (and you won't really get a better result with those cards using smxi/sgfxi)

In Jessie those old nvidia cards are pretty much limited to using either the nouveau driver or the vesa or fbdev non-kms drivers.
http://antix.freeforums.org/post40994.html#p40994

Last edited by rokytnji; 12-28-2015 at 04:42 PM.
 
Old 06-13-2016, 07:42 PM   #24
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
Quote:
Originally Posted by bimboleum View Post
Hi,
Have you tried a different distribution? I have a w530 running Slackware 14.1 and using the nouveau driver and I have seen no problems. I realise we are talking apples and oranges here, but try a different recent distribution and see if you get the same behaviour.

cheers
pete

ps i am in SV too so if you want to try a different distribution, bring your laptop over and we can slot in a different harddrive with Slackware on it.
Please see the most recent post I did in this thread, at this point I doubt that any Linux Distro will work, it is a Kernel-Nouveau issue.
 
Old 06-13-2016, 07:49 PM   #25
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
So I have some more info:
Debian works, as long as you use the 3.2 Kernel. Wheezy works, but Jessie, Stretch and any Ubuntu release that I have tried has the same problem: Nouveau spilling out an insane amount of error messages and then crash, freeze, wait 10 seconds and the system automatically reboots.

Interesting enough, the regression bug is in the Kernel component of Nouveau: I tried to install Docker on my laptop, to run newer software on it, so I upgraded to Kernel 3.16 (Docker does not run on anything lower than 3.10) and look there, I get the same crash as on Jessie or newer or on a new Ubuntu. So when doing this, the non-kernel components of Nouveau in Wheezy are unchanged and old, yet the system still crashes.

I'm very sad and frustrated: I got a perfectly fine great Laptop, but thanks to this regression in Nouveau/Kernel the Laptop is trash and has now end of life written all over it.
I'm facing many issues on Wheezy, of software that is just too old. Nouveau on it works more or less, but sometimes gives hideous graphics corruptions. But it never ever crashes.
Is there a way to help the nouveau guys to fix this bug? I realize that this is an old laptop, but I wish I could still use it, I can't afford to buy a new one.
I'm also not the only one, others with the same hardware are facing this problem.

How is FB or VESA working on this laptop? Can you even use the full resolution? Isn't battery life abysmal, as the CPU has to do all the heavy lifting for graphics?
I will reconsider when buying my next laptop and steer clear of Nvidia graphics, as they seem to be a liability due to shitty drivers.
 
Old 06-13-2016, 10:08 PM   #26
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,508

Rep: Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162Reputation: 1162
You can't run nvidia-alternative in Jessie? It's the 340.96 drivers that according to nvidia support the 140M:

Quote:
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER

Version: 340.96
Release Date: 2015.11.16
Operating System: Linux 64-bit

<snipped>

NVS Series (Notebooks):
NVS 5400M, NVS 5200M, NVS 5100M, NVS 4200M, NVS 3100M, NVS 2100M, Quadro NVS 320M, Quadro NVS 160M, Quadro NVS 150M, Quadro NVS 140M, Quadro NVS 135M, Quadro NVS 130M
 
Old 06-15-2016, 12:02 AM   #27
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
I have to try that. Hopefully that will work.

I ran the proprietary drivers that are included in Jessie and instead of a kernel panic (freeze and restart), I just get the X11 Server crashes and restarts (to login screen)
 
Old 06-15-2016, 05:07 PM   #28
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,030

Rep: Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106Reputation: 3106
It seems quite rare that a Kernel Panic would not have an accompanying warning during bootup. Can you disable Splash and switch to text mode and see? As pretty as Splash can be but as little as I reboot, I always use text mode. I like "heads up". Since, if I understand correctly, you're using nouveau and getting into X there really shouldn't be any sort of graphics driver issue. Debian Stable has always been "tried and true" even to a fault so I doubt a software issue and like others here suspect hardware compromise. Can you load Debian 7 as a known good to check? or even a Live CD? (especially one with lost of diagnostic software) like Hirens.
 
Old 06-15-2016, 07:45 PM   #29
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
I'm curious, can you elaborate on what you mean with kernel messages about a kernel panic?
I have no spash screen on, as no Debian that I have ever seen has that and I like to know what is going on. But as to my knowledge, there is no kernel that marks or even remembers a kernel panic in the logs, it has been something that I have been criticising on Linux, that after all these years, there are no mechanism to detect a very serious crash like that. So would love to hear about it, where in the logs it would be listed and what the phrasing would be so I could find it.

Hmm, I seem to have to repeat myself over and over. Could you guys please read the whole thread, before posting. I have already said a million times, this is no hardware issue.
Why do I know? I'm writing this on Debian Wheezy (7), with Kernel 3.2 and there is positively absolutely no crashes, none. I can run this laptop for days on end and never get a kernel panic, as it is normal on Debian Stable, that is why I'm using it in the first place. I have to use Wheezy, even though I am missing tons of software that I can't use due to it, because Jessie and Stretch and all new Ubuntus are just impossible to use, due to constant crashes. You have no idea how incredible disruptive it is to have your computers crash randomly after 10 minutes of use, no matter what you are using.

As I said, upgrading to kernel 3.16 makes the machine crash, even on Wheezy, just using that kernel will do it. I tried Ubuntu 16.04 (Live CD and installed) and it either gives me massive graphics corruptions or tons and tons of errors in the log from nouveau.

This is not against Debian, as Debian runs very very perfect on tons of my systems and I have never ever had anything like this. I am pretty sure this is a regression bug in Nouveau (in the kernel component of it) with this graphics card that I have (NVIDIA Quadro NVS 140M). It was never fixed and so now it is in every Linux that uses nouveau and a kernel that is newer than 3.2.
 
Old 06-17-2016, 08:20 PM   #30
browny_amiga
Member
 
Registered: Dec 2001
Location: /mnt/UNV/Mlkway/Earth/USA/California/Silicon Valley
Distribution: Kubuntu, Debian Buster Stable, Windoze 7
Posts: 653

Original Poster
Rep: Reputation: 46
Are 340.96 drivers in Jessie standard when using the proprietary NVIDIA driver that Debian provides through the packages?
Because if yes, I have tried that already and it did not work: It restarts the X11 server from time to time.
I hope that it is not so, that I still have something to try.

It is a pretty thorny issue, since I really cannot use any current software at all: The only way to run it would be docker, but docker requires a newer kernel and that is where the panics and crashes start.
 
  


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 On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] wlan pci on Lenovo T520 Debian Wheezy not working stable; HowTo solve? floppy_stuttgart Linux - Wireless Networking 5 08-25-2015 04:01 PM
moved harddrive from t61 lenovo to t60 lenovo, now cpu freezes Peter Shepard Ubuntu 3 10-26-2009 06:11 PM
Slackware 12.0 on a Lenovo Thinkpad T61 Savet Linux - Laptop and Netbook 11 10-29-2008 12:14 AM
Lenovo T61 users! Archer36 Slackware 6 04-03-2008 05:08 AM
Thinkpad Lenovo T61 Nikosis Slackware 33 07-05-2007 06:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 07:12 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
Open Source Consulting | Domain Registration