[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: Re: Fwd: Re: several SIGSEGV bugs in debian 7/AMD64





-------- Original Message --------
Subject: 	Re: Fwd: Re: several SIGSEGV bugs in debian 7/AMD64
Date: 	Sun, 29 Dec 2013 01:57:50 -0100
From: 	René Kuligowski <renekuligowski@alice-dsl.net>
To: 	Ben Hutchings <ben@decadent.org.uk>



On 28.12.2013 23:46, Ben Hutchings wrote:
 On Sat, 2013-12-28 at 19:52 -0100, René Kuligowski wrote:

 Hi Adrian,


 Thanks for your quick answer,… but (sounds like a pouting little boy, I
 know):
 Sorry, but I cannot file a bug report against, say, nvidia-glx, because
 it is most likely not the cause.

 Sure it is.

when I use the exactly same driver from te NVidia site as in debian 6?
Unlikely.

 The problem is far more likely kernel
 3.x- and/or gcc-related, and I need somebody who knows more intimate
 workings of debian 7 before I can file a bug report to the correct
 topic/person:

 But you just rejected the advice of one such person.  Do you want advice
 or not?

Sure.  But advice that makes sense and doesn't assume I don't now at all
what I am talking about.

 –– newer BIOS for my machine does not exist.  Current/last is from
 2009.  And, like I wrote, it works perfectly with debian 6 (kernel 2.6)
 or winXP/win7.  *without* *any* problems. And I don't exactly care if
 APM/ACPI standards have changed in the meantime.  Debian used to be
 backward-compatible to even twenty-years-old hardware and their specs.

 I don't believe this was ever true, and it should not be a high priority
 for us.

 [...]

 –– with kernel *2.6* on debian 6, this does not happen, while I use
 exactly the same settings, libraries, modules, and X modules (well, libs
 with a smaller sub-version number).  With debian 6 using a 3.x kernel,
 *the same* happens as I described here for debian 7.

 [...]

 You are also using a new version of the nvidia driver with this
 kernel...

wrong.  I use the 290, same version I use in debian 6.

 Ben.




Reply to: