Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #258542 > unrolled thread

nvidia package 340xx

Back to article view | Back to linux.debian.user

Contents

  nvidia package 340xx Hans <hans.ullrich@loop.de> - 2023-05-20 18:40 +0200
    Re: nvidia package 340xx Richmond <dnomhcir@gmx.com> - 2023-05-20 19:30 +0200
      Re: nvidia package 340xx "Marlin S. Petre" <marlinpetre@gmail.com> - 2023-05-20 19:40 +0200
      Re: nvidia package 340xx Greg Wooledge <greg@wooledge.org> - 2023-05-20 19:50 +0200
      Re: nvidia package 340xx "Marlin S. Petre" <marlin@redrunelectronics.net> - 2023-05-20 20:30 +0200
        Re: nvidia package 340xx Richmond <dnomhcir@gmx.com> - 2023-05-20 21:00 +0200
      Re: nvidia package 340xx Hans <hans.ullrich@loop.de> - 2023-05-21 20:40 +0200
        Re: nvidia package 340xx Richmond <dnomhcir@gmx.com> - 2023-05-21 22:50 +0200
          Re: nvidia package 340xx Hans <hans.ullrich@loop.de> - 2023-05-22 17:10 +0200
          Re: nvidia package 340xx Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-05-23 09:40 +0200

#258542 — nvidia package 340xx

Dear debian team, 

I just discovered the "nividia-legacy-340xx"-packages in debian sid. 

However, as they were in buster, but NOT in bullseye, NOR in bookworm, I 
wonder, if there is a chance, they will transfer from testing to bookworm some 
day. 

I tested them on bookworm, and they built (what a pleasent surprise!!), but I 
could not load them on actual bookworm kernel 6.1.0.9. Ok, this might be, that 
some other libs needed by the driver, are incompatible, because they need libs 
from sid, but that does not matter for me.

My question is more: Will these packages be transferred to testing some day 
and then from testing to stable? Or will they (when transferred to testing) 
NEVER be transferred to stable (until the next big release, of course).

What is the policy with those (unfree and third party packages )and what are 
the chances at all? 

Thanks for your help, oh and thank you for the people, who got this package 
buildable!

Best regards

Hans  

[toc] | [next] | [standalone]

#258545

Hans <hans.ullrich@loop.de> writes:

> Dear debian team,
>
> I just discovered the "nividia-legacy-340xx"-packages in debian sid.
>
> However, as they were in buster, but NOT in bullseye, NOR in bookworm,
> I wonder, if there is a chance, they will transfer from testing to
> bookworm some day.
>
> I tested them on bookworm, and they built (what a pleasent
> surprise!!), but I could not load them on actual bookworm kernel
> 6.1.0.9. Ok, this might be, that some other libs needed by the driver,
> are incompatible, because they need libs from sid, but that does not
> matter for me.
>
> My question is more: Will these packages be transferred to testing
> some day and then from testing to stable? Or will they (when
> transferred to testing) NEVER be transferred to stable (until the next
> big release, of course).
>
> What is the policy with those (unfree and third party packages )and
> what are the chances at all?
>
> Thanks for your help, oh and thank you for the people, who got this
> package buildable!
>
> Best regards
>
> Hans

As far as I remember the problem in Nvidia does not support kernels
above 4. This is why my laptop is stuck on Debian 10, although I did
wonder if Debian 11 can run with kernel 4.

(Nouveaux is no good to me).

[toc] | [prev] | [next] | [standalone]

#258546

On 5/20/23 1:15 PM, Richmond wrote:
> As far as I remember the problem in Nvidia does not support kernels
> above 4. This is why my laptop is stuck on Debian 10, although I did
> wonder if Debian 11 can run with kernel 4.
>
> (Nouveaux is no good to me).
>
I am using the "nvidia-tesla-450-driver" on Debian 12 bookworm. You
need to install the linux-headers package that matches your kernel version
in order for the nvidia driver to build into the kernel. For Bullseye amd64,
I think this would be "linux-headers-5.10.0-22-amd64". For Bookworm, it is
"linux-headers-6.1.0-9-amd64".

If a point release of stable ships with a different kernel version, I learned that I
needed to install the headers package that matched, or the driver would build
for the old kernel.

-- 

Regards,
Marlin

[toc] | [prev] | [next] | [standalone]

#258547

On Sat, May 20, 2023 at 06:15:18PM +0100, Richmond wrote:
> As far as I remember the problem in Nvidia does not support kernels
> above 4. This is why my laptop is stuck on Debian 10, although I did
> wonder if Debian 11 can run with kernel 4.

It should, so long as you don't care about the newer kernel features.

https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#glibc-and-linux

    Starting with glibc 2.26, Linux kernel 3.2 or later is required. To
    avoid completely breaking the system, the preinst for libc6 performs
    a check. If this fails, it will abort the package installation,
    which will leave the upgrade unfinished. If the system is running
    a kernel older than 3.2, please update it before starting the
    distribution upgrade.

To the best of my knowledge, the Linux kernel 3.2 requirement is still
the same in bullseye as it was in buster.

[toc] | [prev] | [next] | [standalone]

#258550

On 5/20/23 1:15 PM, Richmond wrote:
> As far as I remember the problem in Nvidia does not support kernels
> above 4. This is why my laptop is stuck on Debian 10, although I did
> wonder if Debian 11 can run with kernel 4.
>
> (Nouveaux is no good to me).
>
I am using the "nvidia-tesla-450-driver" on Debian 12 bookworm. You
need to install the linux-headers package that matches your kernel version
in order for the nvidia driver to build into the kernel. For Bullseye amd64,
I think this would be "linux-headers-5.10.0-22-amd64". For Bookworm, it is
"linux-headers-6.1.0-9-amd64".

If a point release of stable ships with a different kernel version, I 
learned that I
needed to install the headers package that matched, or the driver would 
build
for the old kernel.

Regards,
Marlin

[toc] | [prev] | [next] | [standalone]

#258551

"Marlin S. Petre" <marlin@redrunelectronics.net> writes:

> On 5/20/23 1:15 PM, Richmond wrote:
>> As far as I remember the problem in Nvidia does not support kernels
>> above 4. This is why my laptop is stuck on Debian 10, although I did
>> wonder if Debian 11 can run with kernel 4.
>>
>> (Nouveaux is no good to me).
>>
> I am using the "nvidia-tesla-450-driver" on Debian 12 bookworm. You
> need to install the linux-headers package that matches your kernel version
> in order for the nvidia driver to build into the kernel. For Bullseye amd64,
> I think this would be "linux-headers-5.10.0-22-amd64". For Bookworm, it is
> "linux-headers-6.1.0-9-amd64".
>
> If a point release of stable ships with a different kernel version, I
> learned that I
> needed to install the headers package that matched, or the driver
> would build
> for the old kernel.
>
> Regards,
> Marlin

I am referring to the legacy 340 driver which OP is using and I am
using. Nvidia doesn't support that driver above kernel 4. Tesla 450
doesn't look like legacy to me, it's in the Debian 11 repo.

[toc] | [prev] | [next] | [standalone]

#258570

[Multipart message — attachments visible in raw view] — view raw

Am Samstag, 20. Mai 2023, 19:15:18 CEST schrieb Richmond:
> Hans <hans.ullrich@loop.de> writes:

> 
> As far as I remember the problem in Nvidia does not support kernels
> above 4. This is why my laptop is stuck on Debian 10, although I did
> wonder if Debian 11 can run with kernel 4.
> 
> (Nouveaux is no good to me).

Hi Richmond,

regarding to debian/sid the package supports kernels up to 6.2. 

However, there are some issues, so it will segfault any qt-windowmangers (at the moment) and 
got some security issues.

I succcessfully could build the sources with kernel-headers 6.0.1-9 (which with former kernels 
later than 5.10-22 did not work).

But sadly in the end I did not succced at all, as it did not load the kernel modul and additionally 
it breaked my acceleration from the inbuilt gpu of the intel processor. 

So it was more a disappointment. On the other hand it could be, I made some mistakes and 
should upgrade additional libs from unstable. 

There is another thing, I also might done wrong (I wrote about some weeks ago in this forum): 
lspci says it is 

NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1)

and nvidia-detect (and some other sources, are telling me, that for this chipset NOT 340xx but 
390xx should be used.

Thisis wrong, as I could prove, that only 340xx (with kernel 5.10-22) is working. Installing 390xx, 
the kernel says: Wrong module, you have to use 340xx.

This is the state at the moment. As I have only this laptop and no spare harddrive at the 
moment, I could not install debian/unstable for testing purposes. Maybe some time I will, or 
maybe some other guy will do it.

Hope this makes some things clearer.

Best regards

Hans

[toc] | [prev] | [next] | [standalone]

#258576

Hans <hans.ullrich@loop.de> writes:

> Am Samstag, 20. Mai 2023, 19:15:18 CEST schrieb Richmond:
>
>> Hans <hans.ullrich@loop.de> writes:
>
>
>>
>
>> As far as I remember the problem in Nvidia does not support kernels
>
>> above 4. This is why my laptop is stuck on Debian 10, although I
> did
>
>> wonder if Debian 11 can run with kernel 4.
>
>>
>
>> (Nouveaux is no good to me).
>
>
> Hi Richmond,
>
>
> regarding to debian/sid the package supports kernels up to 6.2.
>
>
> However, there are some issues, so it will segfault any
> qt-windowmangers (at the moment) and got some security issues.
>
>
> I succcessfully could build the sources with kernel-headers 6.0.1-9
> (which with former kernels later than 5.10-22 did not work).
>
>
> But sadly in the end I did not succced at all, as it did not load the
> kernel modul and additionally it breaked my acceleration from the
> inbuilt gpu of the intel processor.
>
>
> So it was more a disappointment. On the other hand it could be, I
> made some mistakes and should upgrade additional libs from unstable.
>
>
> There is another thing, I also might done wrong (I wrote about some
> weeks ago in this forum): lspci says it is
>
>
> NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1)
>
>
> and nvidia-detect (and some other sources, are telling me, that for
> this chipset NOT 340xx but 390xx should be used.
>
>
> Thisis wrong, as I could prove, that only 340xx (with kernel 5.10-22)
> is working. Installing 390xx, the kernel says: Wrong module, you have
> to use 340xx.
>
>
> This is the state at the moment. As I have only this laptop and no
> spare harddrive at the moment, I could not install debian/unstable
> for testing purposes. Maybe some time I will, or maybe some other guy
> will do it.
>
>
> Hope this makes some things clearer.

Not really, but I found this website which says the driver supports
kernels "up to" 5.4 which I guess means up to and including.

https://nvidia.custhelp.com/app/answers/detail/a_id/3142/

But debian seems to drop after debian 10 because kernel is 5.10 ?

https://wiki.debian.org/NvidiaGraphicsDrivers

I see here someone has patched the drivers:

https://github.com/MeowIce/nvidia-legacy

:-?

Ubuntu 20.04 supports kernel 5.4 until 2025. So I might try that after
debian 10 expires.

https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

My card:

nvidia-detect 
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1)

Checking card:  NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1)
Your card is only supported up to the 340 legacy drivers series.
It is recommended to install the
    nvidia-legacy-340xx-driver
package.

[toc] | [prev] | [next] | [standalone]

#258608

[Multipart message — attachments visible in raw view] — view raw

Hi Richmond, 

I found this from https://packages.debian.org/sid/nvidia-legacy-340xx-driver[1]

"Building the kernel module has been tested up to Linux 6.2."

Ok, building does not really mean, it is working, only it is buildable.

The other information I mentioned ("it segfaults with qt-libs") I could not find any more. Maybe I 
saw it in the wiki and the wiki is now changed.

So, just stay with the Intel driver and NO Nvidia and No Optimus, sigh.

Best 

Hans

  
> Not really, but I found this website which says the driver supports
> kernels "up to" 5.4 which I guess means up to and including.
> 
> https://nvidia.custhelp.com/app/answers/detail/a_id/3142/
> 
> But debian seems to drop after debian 10 because kernel is 5.10 ?
> 
> https://wiki.debian.org/NvidiaGraphicsDrivers
> 
> I see here someone has patched the drivers:
> 
> https://github.com/MeowIce/nvidia-legacy
> 
> :-?
> 
> Ubuntu 20.04 supports kernel 5.4 until 2025. So I might try that after
> debian 10 expires.
> 
> https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel
> 
> My card:
> 
> nvidia-detect
> Detected NVIDIA GPUs:
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [GeForce
> 8400M GS] [10de:0427] (rev a1)
> 
> Checking card:  NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1)
> Your card is only supported up to the 340 legacy drivers series.
> It is recommended to install the
>     nvidia-legacy-340xx-driver
> package.



--------
[1] https://packages.debian.org/sid/nvidia-legacy-340xx-driver

[toc] | [prev] | [next] | [standalone]

#258636

Richmond <dnomhcir@gmx.com> writes:

> Ubuntu 20.04 supports kernel 5.4 until 2025. So I might try that after
> debian 10 expires.
>
> https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

Off topic but they actually increased that to 2030 recently, at least on
x86-64. I thought I could benefit from it with my Raspberry Pi but no
luck.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web