SparkyLinux Forums

Hello,
yesterday I upgraded to Sparky 9.
Everything worked fine.

But I have a question to installed and newer kernels.
Currently kernel linux-image-6.12.31-amd64 with corresponding headers are installed.

I have seen, in the meantime there are a lot of newer kernels, but not with the stand-alone suffix '-amd64'.
For example, there is a newer kernel 'linux-image-6.16.7+deb14-amd64' with corresponding headers too.

Can I use this kernel and corresponding headers instead of my installed?
Or is this installation not recommended?

I use the testing release, my CPU is an Intel i9-10850K, graphic card is nVidia GeForce RTX 2060.

Thank you in advance for help.

Quote from: Splinx64 on September 25, 2025, 03:53:11 PM[....] Can I use this kernel and corresponding headers instead of my installed?
Or is this installation not recommended?

(https://i.imgur.com/bDtcOwK.gif) Apparently, the Kernel you mention is the latest version currently available, in the debian testing (aka: forky) repositories:


(https://i.imgur.com/Jrou3Bm.png)

Quote from: Splinx64 on September 25, 2025, 03:53:11 PM[....]
Thank you in advance for help.

You're welcome !!







Cheers !! (https://i.imgur.com/emjz0.gif)

OK, thank you for your answer, AxL.

I will see, where I can found it. In the package list of Synaptic he still isn't visible.
Maybe, I try it manually or/and check my sources.list.

But, do it tomorrow.

Aha, when I understand the outputs of 'apt policy linux-image-amd64 ' an 'apt show linux-image-amd64' correctly, than is kernel 'linux-image-6.16.7+deb14-amd64' the next installation candidate.

And when it is ready for installation it will be changed or named to 'linux-image-6.16.7-amd64', isn't it?

But, currently, the kernel is not yet ready for installation or only for testing purposes.

Of course, this debian release is called 'testing'. I could install it at my own risk.

Quote from: Splinx64 on September 25, 2025, 07:29:19 PMOK, thank you for your answer, AxL.

You're welcome !! (https://i.imgur.com/RGwcc9H.gif)

Quote from: Splinx64 on September 26, 2025, 11:32:42 AM[....]  And when it is ready for installation it will be changed or named to 'linux-image-6.16.7-amd64', isn't it?

But, currently, the kernel is not yet ready for installation or only for testing purposes.

(https://i.imgur.com/bDtcOwK.gif) Let's see lad. The latest kernel available in Debian Testing, is the one I told you about in my first post.

That's the pure reality:


(https://i.imgur.com/B4jyKVD.png)


I don't know what your problem is, and why you don't have it available. So, thoroughly check your /etc/apt/sources.list.d/ and read the SparkyLinux Wiki.

Also, check all the information available (SourcesList) to the debian user.

Good luck !!  (https://i.imgur.com/4GCd6.gif)








Cheers !!  (https://i.imgur.com/emjz0.gif)

OK, until now I used the 'old way' for upgrading with files 'etc/apt/sources.list' and '/etc/apt/sources.list.d/sparky.list'. This ran without any problems.

In the course of this processing I modernized to the 'new way" with files '/etc/apt/sources.list.d/debian.sources' and '/etc/apt/sources.list.d/sparky.sources'.

But now I get some error messages while 'apt update'.

~$ sudo apt update
OK:1 http://deb.debian.org/debian forky InRelease
OK:2 http://security.debian.org/debian-security forky-security/updates InRelease
OK:3 https://repo.sparkylinux.org core InRelease                              
Error:3 https://repo.sparkylinux.org core InRelease                       
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring "/usr/share/keyrings/sparky.gpg.key"  Caused by:     0: Reading "/usr/share/keyrings/sparky.gpg.key": No such file or directory (os error 2)     1: No such file or directory (os error 2)
OK:4 http://deb.debian.org/debian forky-updates InRelease                
Ign:5 https://repo.sparkylinux.org forky InRelease                       
Error:6 https://repo.sparkylinux.org forky Release
  404  Not Found [IP: 184.174.34.74 443]
OK:7 http://deb-multimedia.org forky InRelease
Warning: https://repo.sparkylinux.org/dists/core/InRelease: The key(s) in the keyring /usr/share/keyrings/sparky.gpg.key are ignored as the file is not readable by user executing gpgv.
Warning: During the verification of the signature, an error occurred. The repository has not been updated and the previous index files are used. OpenPGP signature verification failed. OpenPGP signature verification failed: https://repo.sparkylinux.org core InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring "/usr/share/keyrings/sparky.gpg.key"  Caused by:     0: Reading "/usr/share/keyrings/sparky.gpg.key": No such file or directory (os error 2)     1: No such file or directory (os error 2)
Error: Depot »https://repo.sparkylinux.org forky Release« contains no release file.
Note: Updating such a depot cannot be done in a secure way, so it is disabled by default.
Note: For more details on how to create package repositories and how to configure them, see the manual page apt-secure(8).
Note: Missing Signed-By in file sources.list(5) for »http://deb-multimedia.org«

Some messages in my language I have translated.

Hm, what can I do?

Well, it is clearly indicating that there is a very obvious error in the SparkyLinux repositories. Which, you should correct.

Here. you can see an image with the repositories correctly configured:


(https://i.imgur.com/FOt08Tw.png)







Cheers !!  (https://i.imgur.com/emjz0.gif)

O, wow, thank you for finding the incorrect lines in this config file.
I edit my file tomorrow and will report then.

Quote from: Splinx64 on September 26, 2025, 09:48:50 PMO, wow, thank you for finding the incorrect lines in this config file.

(https://i.imgur.com/rsNxgL4.gif)

You can review and fix this other error as well:

Quote from: Splinx64 on September 26, 2025, 08:23:37 PM

Code Select Expand

[....]  Note: Missing Signed-By in file sources.list(5) for »http://deb-multimedia.org«


In this example image you can see how it should be:

(https://i.imgur.com/Lt4m8sL.png)





Cheers !!  (https://i.imgur.com/rOXmqAV.gif)

OK, I could install the new kernel (in the meantime 6.16.8+deb14-amd64) as in your post #4 discribed. Of course I unstalled the linux-headers too.

Unfortunately, the linux-headers for the new kernel don't build the modules for the nvidia card. That's why I have to keep using the old kernel.

Your post #8 didn't help.
I still have the error message about debian-multimedia.

Quote from: Splinx64 on September 27, 2025, 12:41:56 PMOK, I could install the new kernel (in the meantime 6.16.8+deb14-amd64) as in your post #4 discribed. Of course I unstalled the linux-headers too.

Unfortunately, the linux-headers for the new kernel don't build the modules for the nvidia card. That's why I have to keep using the old kernel.

(https://i.imgur.com/IqZHXhe.gif)  Let's see. As far as I know, in your messages you have commented that you could not install the latest kernel available in the debian testing repositories.

And, you have NOT asked absolutely anything, about the module for your Nvidia card. So, I feel sorry for you. (https://i.imgur.com/0Ej3kS5.gif)

Quote from: Splinx64 on September 27, 2025, 12:41:56 PM[....]
Your post #8 didn't help.
I still have the error message about debian-multimedia.

Well, then try this other option:

(https://i.imgur.com/MoEELBh.png)









Cheers !! (https://i.imgur.com/emjz0.gif)

Yes, at first I thought the new kernel had to have the same suffix as the installed one.
That's why I didn't pay much attention to the post #4.

I saw that there are also appropriate linux-header for the new kernel.
It's a pity that the modules for nvidia haven't been built yet.

With the multimedia part I'll test tomorrow.

Thank you for your continued support

Quote from: Splinx64 on September 27, 2025, 08:31:18 PM[....]  Thank you for your continued support

You're welcome !!  (https://i.imgur.com/qZur36x.gif)


I forgot to tell you, that if you want to continue using LTS Kernels. You have available both the versions of XanMod (6.12.49).
 And the LTS versions of SparkyLinux (6.12.49 or 6.6.108).





Cheers !!  (https://i.imgur.com/emjz0.gif)

I already today tested the data for multimedia.

Now it works.

There is also a file 'unofficial-multimedia-packages.sources'.
This was not completely filled.
Therefore I entered the data there, as you wrote, AxL.

So I think, my question is answered. I can install the newer kernel. But until now the kernel modules for my nvidia card won't build yet.

O, it seems, I have overlooked, that here is wrote about the 'unofficial-multimedia-packages.sources' file. Well, this point is solved.


I don't necessarily want to use LTS kernels. Sometimes it needs some time until the linux-headers support nvidia cards.

Quote from: Splinx64 on September 27, 2025, 10:33:15 PMI already today tested the data for multimedia.

Now it works.
[....]

I'm glad you were able to fix that problem.
Congratulations ... (https://i.imgbox.com/TkbBuT0I.gif)







Bye !!  (https://i.imgur.com/uZvkZOF.gif)

Yes, I'm happy too, that all questions are answered.

Thank you for your help.

I mark this thread as 'solved'.

Quote from: Splinx64 on September 29, 2025, 04:36:23 PMYes, I'm happy too, that all questions are answered.

Thank you for your help.

(https://i.imgur.com/rsNxgL4.gif)