MX Linux Forum

anticapitalista wrote:antiX-17 uses ddm-mx.

Okay, and ddm-mx uses dkms.

OK, lots of things tried.

I decided to start over. I downloaded antix 17 rc1. I used MX tools to make a USB, which booted just fine (I used toram boot option)
All looked good, sound could be enabled with the control panel sound card picker, going with generic, internet, youtube plays, so I installed.

All went well, (from the usb to nvme it was fast, about 4 minutes).
But I still showed the 4.13 kernel in the advanced mode when booting. So, wanting a simple clean case, I went back to MX 16.1, deleted everything on the antix partition to get rid of the grub, and reformated nvme01P4 with gparted.

Reboot and reinstall antix17 rc1. again all is fast, and runs well. But no only the 4.10 kernel is listed in the advanced options. Correct !
So I CTL-ALT-F1, logged in as root, and ran sgfxi. I had to reboot and re-run to get it installed, with 384.90. VIdeo looks good, so now I think I am ready to try the sgfxi -! 40 trick.
Here is inxi -F
You see I have _rc1, with with NVIDIA 384.90.

So I installed the linux-image-4.13.4-antix.1-amd64-smp,
then the appropriate headers.

Reboot twice, I updated grub, rebooted, and the new kernel does not show up in the advanced options.

Anyway, I ran sgfxi again with the -! 40 option, and it goes all the way through, with the error at the end It did try building for the 4.13 kernel, but couldn't. So it thinks I have the 4.13 installed, I checked, 4.13 shows installed along with the stock 4.10 in synaptic, headers to.

So finally I tried
So different than what sgfxi installed, earlier version.

So how can I see the 4.13 to try booting it?
ANd what video can I run for it since the -! 40 does not work, and I don't have the devbian version?

Where next, to boot the new kernel with video?

Thanks
BTW, the antix 17 rc1 looks good so far. Live and installed to this recent hardware. The network, sound, video (the above issues aside) all work.
I updated with synaptic, and will soon try other installs.

384.90 with smxi

375.82 with debian

maybe that's the issue.

Since Stevo said the 4.13 kernel works with the 375.82 version nvidia driver installed the Debian way, I would of stuck with using the antix control center/ddm-mx/dkms to install the nvidia driver instead of using sgfxi.

Sgfxi might have failed installing the 384.90 nvidia driver on the 4.13 kernel because it might not be patched to support it, where it looks the the Debian 375.82 nvidia driver has been patched to support 4.13 kernels.

384.90 with smxi
375.82 with debian
maybe that's the issue

The issue, but what does it mean, and how to fix it?
If sgfxi gave me 384.90, why does it not detect that previous install and give the same to kernel 4.13?

Or, can I use sgfxi to downgrade to 375.82? Would that be compatible with the 4.13 kernel?

With the noveau driver, the mouse and KB lock up frequently, with an nvidia driver, I get reboots every 2-8 days. So I am looking for stability. I updated the BIOS to latest 0902 and haven't really let it run to see if stability is improved yet.
But many places on the net (reddit and amd boards ) say newer kernels are better for Ryzen stability. I would like to get a 4.13 or maybe 4.12 running on this machine. Even 4.14 will have new drivers and improvements.

kmathern,

But how do I get the 4.13 to show up in the advanced options, even though synaptic shows it is installed with headers, and I ran update-grub?

And last time I got it to show in the boot options I booted to no X, and couldn't start X due to no screens.
I am missing something here, it is different than last time I tried it.

I could still run the nvidia installer from the antix control panel, right?
But then how to get that to a booting 4.13.

I have little effort into this rc1 install yet, so I can easily reinstall or do just about anything to learn and fix.

entropyfoe wrote:kmathern,

But how do I get the 4.13 to show up in the advanced options, even though synaptic shows it is installed with headers, and I ran update-grub?

And last time I got it to show in the boot options I booted to no X, and couldn't start X due to no screens.
I am missing something here, it is different than last time I tried it.

I could still run the nvidia installer from the antix control panel, right?
But then how to get that to a booting 4.13.

I have little effort into this rc1 install yet, so I can easily reinstall or do just about anything to learn and fix.

I don't know why the 4.13 kernel doesn't show up in grub's advanced options menu.

As long as the 4.13 kernel is installed correctly, you can install the nvidia driver for 4.13 while running in the 4.10 kernel using the dkms command I posted earlier: viewtopic.php?p=424273#p424273.

Open a root terminal and type

I am also building the 4.13 Liquorix kernels for MX 17 test and in a separate OBS repo, since the official builds switched to requiring gcc-7 for the headers. I know installing those automatically added the 4.13 kernel to GRUB in MX 16.

http://techpatterns.com/forums/about2615.html

Also built gcc-5 versions for some Ubuntus and gcc-4.8 for Trusty. Like I need more packaging work, but the Liquorix devs asked.

Stevo and anti, you guys are the real kernel experts, I am out of my depth.

Of course, I did figure out the grub, I had updated the grub at the antix root, not the one on MX 16.1, the master grub that controls the boot. So I fixed that.

Now both kernels show. So I got bolder, and booted with the 4.13, got the terminal, logged in as root, startx, error, server connection refused, so I tried sgfxi at that point, and was able to boot into a bare desktop, no antix, no wallpaper, no applications...not sure what that was.

So I rebooted back with 4.10, and it also was messed up, so out of desperation I ran sgfxi again, and now 4.10 boots normally, and 4.13 goes to a terminal only, with an error after startx. [server terminated with error (1)..unable to connect to the x server...]

I guess I really don't understand how the kernel and video are configured together.

What happens if I run the control center Nvidia driver installer? What would I get? Back to 375.82? A functioning system?
And how to propagate that to the 4.13 kernel and still have antix working?