Error everytime I install a kernel

[Stevo]

I haven't tested the antiX 5.2 kernel, but wonder if you are seeing the driver rebuild when you install it. It's pretty apparent when you scroll back up the terminal output after its done.

I also wonder if you're getting the same failures if you install the 5.2 Liquorix kernel--I have more experience with that one.

[Cavsfan]

But, I think it is too much to ask for a user to mix test repo packages with stable packages. I know a little but, just consider me a regular user. I do not feel comfortable installing any kernel this way.

To be clear no one forces a user to install from the test repo. It is a test repo. The packagers want feedback if a user chooses to install. That is why it is test. Only if feedback is positive will the package be moved to main.

Thank you! That was what I was basically saying that I'm not going to do any mixing of repos. I opened this thread thinking there was a problem I didn't know about when I got the checksum error installing the 5.2 antix kernel from MX Package Installer.

I guess I failed to mention that it was not important to me to install this kernel. I trust what is the "Production kernel" as being good enough for me, which is the 4.19.0-5-amd64 kernel.

I am not one to go installing kernels; I prefer to let them be updated automatically.

I also have MX 19 beta1 installed and it installed the same kernel.

[Cavsfan]

I haven't tested the antiX 5.2 kernel, but wonder if you are seeing the driver rebuild when you install it. It's pretty apparent when you scroll back up the terminal output after its done.

I also wonder if you're getting the same failures if you install the 5.2 Liquorix kernel--I have more experience with that one.

Sorry, I didn't see this post before I replied but, this previous reply of mine says what I meant

[Cavsfan]

I believe I was a little naive about MX Linux, in that it does not update it's kernel. I installed Mint a long time ago and it took me a long time to realize that they did not update kernels either.
Unless you want to and I believe once I set that switch, the kernel was regularly updated after that.

I do not believe I should have to troubleshoot why no kernel will install because I'm not a developer nor is MX 18.3 in the developmental stage. I figured more people would have been reporting problems with this but, I didn't see any.
The price is too high when it fails as a complete re-install is required. I'd help if I could but, I've already tried and while I'll admit initially installing systems is my thing, re-installing the same system over and over is not for me.

I like a variety of Operating systems and have Arch Linux with the bleeding edge kernel 5.3.6.arch1-1 released 2 days ago.

I installed MX Linux 19 beta3 a day or two ago. I't looking pretty good.

[Stevo]

Dolphin_oracle just fixed the Nvidia Installer on at least MX 19 to install the 435.21 driver from the test repo correctly when that's the choice, and it now works correctly in my tests. The new version should be pushed as an update to MX 19 and 18 quite soon, so wait a bit. Before the fix, you get the stock Debian version no matter what your choice.

As a workaround before the fix, I was able to update the 418.74 stock Buster driver to the 435.21 version after the stock version was incorrectly installed from the test repo tab of MX PI, as explained above, but you had to check to make sure your hardware would work with the 435 version.

[Cavsfan]

Dolphin_oracle just fixed the Nvidia Installer on at least MX 19 to install the 435.21 driver from the test repo correctly when that's the choice, and it now works correctly in my tests. The new version should be pushed as an update to MX 19 and 18 quite soon, so wait a bit. Before the fix, you get the stock Debian version no matter what your choice.

As a workaround before the fix, I was able to update the 418.74 stock Buster driver to the 435.21 version after the stock version was incorrectly installed from the test repo tab of MX PI, as explained above, but you had to check to make sure your hardware would work with the 435 version.

Sounds good! I have MX 18.3 as well as MX 19 beta installed and on 19 I have the 418.74 driver. So, I'll get that update when it is released.
I forgot MX is based on Debian, so no new kernel every few days like Arch Linux using the 5.3.8.1-1-ARCH-1 kernel.

I installed Debian Buster too and I like how they've worked on compiz/emerald/fusion-icon, probably the same as MX Linux.

Code: Select all

$ inxi -SMCG
System:    Host: mxlinux19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: Z87-K v: Rev X.0x serial: <root required> 
           UEFI: American Megatrends v: 1103 date: 01/02/2014 
CPU:       Topology: Quad Core model: Intel Core i7-4770K bits: 64 type: MT MCP 
           L2 cache: 8192 KiB 
           Speed: 2976 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 3664 2: 3478 3: 3531 
           4: 3491 5: 3587 6: 3676 7: 3656 8: 3453 
Graphics:  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] driver: nvidia v: 418.74 
           Display: x11 server: X.Org 1.20.4 driver: nvidia resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 980 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 

[Stevo]

If you do want to track new kernel releases, you can add the Liquorix kernel repo, or I rebuild them for our test repos about once a week or so.

But then you have to make sure your third party drivers will build against a new kernel release, or at least be prepared to revert to a known working kernel via the "advanced options" submenu in GRUB.

[Cavsfan]

If you do want to track new kernel releases, you can add the Liquorix kernel repo, or I rebuild them for our test repos about once a week or so.

But then you have to make sure your third party drivers will build against a new kernel release, or at least be prepared to revert to a known working kernel via the "advanced options" submenu in GRUB.

Sounds good. That could be something for the future. I've got 9 Linux systems on this computer: Arch Linux, Fedora 30 & 31, openSUSE Tumbleweed, Debian Buster and Testing, MX 18, 19 and Xubuntu 18.04.3 LTS.

I hadn't realized that MX Linux 19 final was released until a few days ago, I had installed a beta 3 ISO. But, this installation went very well.

I was able to install the 5.2 kernel from the MX Package Installer and it said it was going to use the that newer Nvidia driver but, it said there was a newer Nvidia driver in the Test Repo and asked if I wanted to use that; I gave it a "Y" and it installed 435.21.
It all went together, I got some warnings but both kernels boot fine. I created 4 symlinks for both parts of the 2 kernels initrd.img and vmlinuz. I just added antix to the names of the 2 parts of that kernel.

Code: Select all

$ inxi -S -G
System:    Host: mxlinux19 Kernel: 5.2.15-antix.1-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19_x64 patito feo October 21  2019 
Graphics:  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] driver: nvidia v: 435.21 
           Display: x11 server: X.Org 1.20.4 driver: nvidia resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 980 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 

Code: Select all

$ ls -lA /boot | grep " -"
lrwxrwxrwx 1 root root       35 Nov 23 20:55 initrd-antix.img -> initrd.img-5.2.15-antix.1-amd64-smp
lrwxrwxrwx 1 root root       25 Nov 23 19:07 initrd.img -> initrd.img-4.19.0-6-amd64
lrwxrwxrwx 1 root root       22 Nov 23 19:07 vmlinuz -> vmlinuz-4.19.0-6-amd64
lrwxrwxrwx 1 root root       32 Nov 23 20:56 vmlinuz-antix -> vmlinuz-5.2.15-antix.1-amd64-smp

This is really looking good.