On 29.12.2013 01:27, John Paul Adrian Glaubitz wrote:
This is a common fallacy: Just because a piece of hardware is working
properly on Windows doesn't mean anything is adherent to the
specifications. The reason why your hardware is running on Windows
without any problems is that the manufacturer of your hardware
actually tested the combination of drivers, hardware and operating
system and tweaked it long enough to get the combination running
stable. Possible errors in the ACPI implementation can be fixed by
additional hacks in the driver or Windows.
…and since debian 6's kernel etc.pp. also were able to hotfix or
whatever, so that my system runs without any issues… but this gets
pointless, because I keep saying A² and you keep understanding B/µ.
Let's just assume my ACPI tables are completely according to standard,
because they are.
(…)
Not necessarily. The internal interfaces of the kernel change very often
and compiling the nVidia module glue code on a 2.6 kernel is certainly
quite different to compiling it on a 3.x kernel. You probably have
noticed that very often you need to update the nVidia drivers to be
able to use them with newer kernels.
The driver might use features present in the 3.x kernels only which
trigger the problems you are seeing.
Did you already try the most recent version of the nVidia driver? You
may also try the version from experimental or directly downloaded
from nVidia if you know how to install it.
I tried debian's nvidia-glx package, which didn't work. From Nvidia's
site: The most recent driver which supports both of my GPUs, the 304
release, as well as the most recent one which supports the GF9, the 331
release. And the 290 release, which runs smoothly in the debian 6
installation.
I already wrote that a few mails back.
As you say yourself above, some things like "udev" etc. pp. would
certainly have to be rebuilt to use the 2.6 features and not to try to
use 3.x ones. Again we rotate to "building the distro from scratch on a
2.6 kernel".
No, they don't. You don't need to rebuilt the whole distribution to
use an older kernel. Linux hasn't changed it's userland ABI for
over 20 years AFAIK. However, some tools which are part of the
kernel's plumberland on Wheezy might complain if you're booting
the system with a kernel significantly older than the one in
Wheezy.
Then it's worth a try to use the 2.6 sources from Squeeze and compile a
kernel in Wheezy.
(…)
Sorry, but the rest of your reply amounts to the mail I sent to
debian-devel only –– pointless bla-bla that shows a) you didn't really
read my mails, b) think I am a complete idiot and c) don't even try to
understand the problematic while I am gathering those logs etc you are
so fanatic about, instead hiding yourself beneath a "another
wannabe-idiot wants to try linux and screwed" attitude.
Thanks, nonetheless, for the help. I consider this whole case closed.
Regards, René
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52bfac37.8070...@alice-dsl.net
