MX Linux Forum

Posted: **Sat Oct 21, 2017 6:05 pm**

I am taking this out of the liquorix thread where it does not belong.

I did upgrade the kernel in my antiX 17 beta2 fully updated.
I can select either the new kernel 4.13 antix 64 bit or the stock 4.10.

The 4.10 still works, but the new one gives a black screen log in.

So I logged in, that works so the system is there.
But when I startx, I get nothing but a fatal error, "no screens"

So how to get video?
Can I run one of the scripts sgfxi or smxi ?
Will that get me an xorg and an nvidia driver?

Or, if this is a long path, I will try downloading antix 17 rc1 and starting over.
I am getting close, and with some advice to help me when I am the edge of my linux experience, I think I can do this.

Thanks anticapitalista and all the kernel experts here.

Posted: **Sat Oct 21, 2017 6:31 pm**

Was the nvidia driver for the 4.10 kernel installed using sgfxi?

If it was you might try sgfxi's -! 40 option, here's what sgfxi's help says about it:

Code: Select all

-! 40 Create modules for all your kernels (nVidia only). Will loop through and test
      each if can be made, then create the modules, excluding your running kernel.
      You must have already installed an nVidia driver with sgfxi to use -! 40
      Note: if your installed driver is NOT the default sgfxi offers, you have to
      use either the -o <driver number> OR the -B option (if you are using current beta driver)
      as well as the -! 40 option. EG: to install beta to all kernels: sgfxi -B -! 40
      -! 40 must be the LAST option in your list of options or errors will occur!

You can run the -! 40 sgfxi command while at the desktop in X and running the 4.10 kernel.
The version of the nvidia driver that's currently installed for the 4.10 kernel does also need to support the 4.13 kernel.
Even if it fails during installation because it doesn't support a 4.13 kernel, your existing nvidia install for the 4.10 kernel should keep working.

Code: Select all

sgfxi -! 40

Posted: **Sat Oct 21, 2017 7:09 pm**

I get no desktop in 4.13, only a terminal, and startx fails with the fatal error 'NO SCREENS'

I did not use sgfxi to install the nvidia driver
I used the antix control center,

or does that just invoke the sgfxi script?
So, could I run the script from my 4.10 kernel, accept what ever sgfxi recommends for the nvidia
( I have this :
Graphics: Card: NVIDIA GK208 [GeForce GT 710B]
Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1920x1080@60.00hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 version: 4.5.0 NVIDIA 375.82

Posted: **Sat Oct 21, 2017 7:21 pm**

entropyfoe wrote:I did not use sgfxi to install the nvidia driver
I used the antix control center,

or does that just invoke the sgfxi script?

I don't know what the antix control center uses to install the nvidia driver, if you do the nvidia install while in X it's probably not using sgfxi.

You can only run sgfxi -! 40 thing I mentioned if sgfxi is what was used originally to install the nvidia driver for the 4.10 kernel.

Posted: **Sat Oct 21, 2017 7:50 pm**

You can always reboot with the older kernel to get back to a GUI, right?

Check if you have the Debian version, which is appears you do, by running

Code: Select all

apt policy nvidia-driver

If so, try reinstalling the nvidia-kernel-dkms package

Code: Select all

apt install --reinstall nvidia-kernel-dkms

Watch the output to see what kernels it's building for and if there are any failures. There a command to trigger rebuilds for all kernels for dkms, but I don't remember it offhand...I'm sure the Google can turn it up.

Posted: **Sat Oct 21, 2017 8:35 pm**

kmathern

Yup,

I don't know what the antix control center uses to install the nvidia driver, if you do the nvidia install while in X it's probably not using sgfxi.

It was while in x.

You can only run sgfxi -! 40 thing I mentioned if sgfxi is what was used originally to install the nvidia driver for the 4.10 kernel.

So my option I was thinking was to download the antix rc1, try it out, then install nvidia (need for stability) with sgfxi

Then I can use that option for all kernels which is cool.

Posted: **Sat Oct 21, 2017 8:38 pm**

Stevo
Yup, I can get back to my normal antix 17 desktop woth the 4.10 kernel.

I will have to look into that dkms stuff, this is a bit outside my linux knowledge, so an opportunity to learn

I was also thinking of installing the antix 17 rc1 as a trial, then I could use the sgfxi to get the nvidia driver, and then use the all kernels option

Posted: **Sat Oct 21, 2017 10:15 pm**

You should run that command to see if nvidia-driver is installed from Debian. Since that 375.82 is the Stretch version, odds are that it is, and that the antiX installer installed it and the nvidia-kernel-dkms package. Those automatically rebuild the drivers for a new kernel if its headers are also installed, which makes me suspect that perhaps something is wrong concerning the headers. It's easy to manually install the wrong headers if you are not careful. I know that the Stretch nvidia driver builds on the 4.13 Liquorix kernel--am running it right now, in fact. But we can only check if you run those simple commands.

Other options: run the antiX Nvidia installer from the command line when booted to the 4.13 kernel CLI, if it offers that mode. I think it might make sure you have the current headers installed. Otherwise, install module-assistant if necessary and run

Code: Select all

m-a prepare

when booted to the new kernel to make sure you have the headers.

Posted: **Sun Oct 22, 2017 9:23 am**

I think this dkms command will build/install the nvidia module for the 4.13 kernel if it (dkms) was used to install the nvidia driver for the 4.10 kernel. You can execute the command while running from the 4.10 kernel.

Code: Select all

sudo dkms install nvidia/375.82 -k 4.13{press tab key  to autocomplete}

Posted: **Sun Oct 22, 2017 9:27 am**

antiX-17 uses ddm-mx.

Posted: **Sun Oct 22, 2017 9:30 am**

anticapitalista wrote:antiX-17 uses ddm-mx.

Okay, and ddm-mx uses dkms.

Posted: **Sun Oct 22, 2017 1:14 pm**

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

Code: Select all

 Host: Ryzen Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64
           Desktop: IceWM 1.4.2
           Distro: antiX-17.rc1_x64-full Heather Heyer 6 October 2017
Machine:   Device: desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: N/A
           UEFI [Legacy]: American Megatrends v: 0902 date: 09/08/2017
CPU:       Hexa core AMD Ryzen 5 1600X Six-Core (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 3600 MHz 1: 2200 MHz 2: 2200 MHz 3: 2200 MHz 4: 2200 MHz
           5: 2200 MHz 6: 2200 MHz 7: 2200 MHz 8: 2200 MHz 9: 2200 MHz 10: 2200 MHz
           11: 2200 MHz 12: 2200 MHz
Graphics:  Card: NVIDIA GK208 [GeForce GT 710B]
           Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 version: 4.5.0 NVIDIA 384.90
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457 driver: snd_hda_intel
           Card-2 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp
Network:   Card: Intel I211 Gigabit Network Connection driver: igb
           IF: eth0 state: up speed: 100 Mbps duplex: 
Drives:    HDD Total Size: 2250.5GB (0.9% used)
           ID-1: /dev/sda model: WDC_WD2002FAEX size: 2000.4GB
           ID-2: /dev/nvme0n1 model: Samsung_SSD_960_EVO_250GB size: 250.1GB
Partition: ID-1: / size: 101G used: 3.9G (4%) fs: ext4 dev: /dev/nvme0n1p4
           ID-2: swap-1 size: 17.83GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p2
Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 37C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 279 Uptime: 14 min Memory: 521.3/16046.7MB
           Client: Shell (bash) inxi: 2.3.40 
music@Ryzen:~

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

Code: Select all

error 169 no previous nvidia sgfxi run package install detected for -k option module build

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

Code: Select all

apt policy nvidia-driver
Installed: (none)
candidate 375.82-1-deb901

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.

Posted: **Sun Oct 22, 2017 1:26 pm**

384.90 with smxi

375.82 with debian

maybe that's the issue.

Posted: **Sun Oct 22, 2017 1:52 pm**

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.

Posted: **Sun Oct 22, 2017 1:54 pm**

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.

Posted: **Sun Oct 22, 2017 2:02 pm**

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.

Posted: **Sun Oct 22, 2017 3:40 pm**

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.

Posted: **Sun Oct 22, 2017 4:05 pm**

Open a root terminal and type

Code: Select all

update-grub

Posted: **Sun Oct 22, 2017 5:49 pm**

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.

Posted: **Sun Oct 22, 2017 9:25 pm**

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?

Posted: **Mon Oct 23, 2017 1:29 pm**

Just a suggestion:

Now , that you surely installed the nvidia-driver with sgfxi (which wasn't the case before)

.......entropyfoe wrote "I did not use sgfxi to install the nvidia driver
I used the antix control center, ".....

and finally updated grub properly

you could try kmatherns suggestion and use the " sgfxi -! 40 " command

Posted: **Mon Oct 23, 2017 2:10 pm**

I did try the -! 40 option, and sgfxi says there is no sign of an earlier install.

I clearly have the new driver, but sgfxi cannot find evidence of the earlier action.

Posted: **Mon Oct 23, 2017 3:12 pm**

I know it works with the 4.13 Liquorix kernel and the stock Debian 375.82 version of the driver installed by ddm-mx. Perhaps you can add my OBS repo and install the Liquorix kernel & headers to see what happens with that one. You'll also have to rerun sgfxi if that's how you installed the driver.

Posted: **Fri Nov 03, 2017 9:28 am**

Still banging away on this.
The Antix 17 install was very stable (>8 days up) with the 4.10 stock kernel.

After more messing around with sgfxi, suddenly 4.13 kernel was working , looking like a normal AntiX desktop as I had customized it.
But two days in a row, it crashed to a black screen, with no keyboard or mouse able to restart it...so hit the reset button, and tried to go back to the 4.10 kernel in the advanced options. It seems if I get one kernel going, it borks the other one !

But now the old stock 4.10 kernel install boots to a command prompt. I ran the sgfxi again, and was able to startx, and log into the bare install. No wallpaper, no Antix customization, panel at the bottom, not on the side, most applications not listed on the applications menu. I am thinking this appearance must mean something to out experts here. I have to enable something, connect some configuration to my user or install.

I logged out and back in as my user (not root), same view. I was able to invoke firefox by typing it at the terminal. Same as synaptic, I ran it updating a few packages. But still no Antix appearance.

My user is there, the applications are there, but somehow I need to reinstall the Antix magic. I ran inxi -F, I have antix 17 RC1, fully updated, with Nvidia 387.22.

Any ideas? The 4.10 kernel was stable for 8 days, but 4.13 couldn't last a day on two occasions. So, my best bet for stability is the 4.10 kernel.

Posted: **Fri Nov 03, 2017 1:02 pm**

antiX-17 is released and it has a lot of the old rc1 problems fixed.
https://sourceforge.net/projects/antix- ... /antiX-17/

Posted: **Sat Nov 04, 2017 10:39 am**

Shay2, Good Idea (maybe) to go with the final. I usually do that after the beta testing, go get final and install.

But, alas, that gave me many problems...

I downloaded the final iso (64 bit_ Antix 17), the md5 was good, so I burned it to a USB using the MX tools. First attempt, said it was successful, but it wouldn't boot, goes to a black screen, not even a cursor.
Re do it from antix tool, no luck..."Couldn't open \EFI\Boot\fallback efi :14"

So, different USB stick wrote the iso with antix tool, this time use the dd option. Boots into the live session, so I installed. All normal but then upon restart, No boot, so go back to MX16.1, update grub. I looked at the partition that antix is installed to, and in the boot folder, the kernel is there, and grub config lists the correct uuid for that partition.

Now boots to a green screen starting with-

Code: Select all

ACPI error needed [Integer/string/Buffer found [region] fff88041....

[...] waiting for /dev to be fully populated [5.772881] kvm : disabled by bios

My MX16 when booting briefly flashes the message -kvm : disabled by bios, but then goes on to boot normally, so not sure what this means.

In summary, with a valid download of antix 17, boots to live session, but the installed antix17 does not boot, even though grub is updated, and it seems that the files are on my 4th partition (antix 17 installed to nmveO1 P4, grub to root.)

I am not sure where to go from here.

Posted: **Sat Nov 04, 2017 11:02 am**

entropyfoe wrote:Now boots to a green screen starting with-
Code: Select all
 kvm : disabled by bios
My MX16 when booting briefly flashes the message -kvm : disabled by bios, but then goes on to boot normally, so not sure what this means.
In summary, with a valid download of antix 17, boots to live session, but the installed antix17 does not boot, even though grub is updated, and it seems that the files are on my 4th partition (antix 17 installed to nmveO1 P4, grub to root.)I am not sure where to go from here.

KVM is a Kernel-based Virtual Machine and some BIOS block the instructions that KVM uses. You can try some fixes in case that your BIOS is blocking it and the BIOS has KVM enabled: on some hardware (e-g HP nx6320), you need to power-off/power-on the machine after enabling virtualization in the BIOS. Enabling some BIOS features may break VT support on some hardware (e-g Enabling Intel AMT on a Thinkpad T500 will prevent kvm-intel from loading with "disabled by bios"). On some Dell hardware, you also need to disable "Trusted Execution", otherwise VT will not be enabled. Here link.

Posted: **Sat Nov 04, 2017 11:18 am**

Ogis,

Thanks for this lead, but I am thinking not to go this route yet, as my working MX 16.1 flashes the same message, and the antix 17 beta worked fine.

It is waiting for the /dev to be populated.

I may try the old beta that worked before, or maybe there are some other ideas to try first....

Does the dd method of USB creation give a different product than the normal full live method?

Posted: **Sat Nov 04, 2017 11:33 am**

Shay2 wrote:antiX-17 is released and it has a lot of the old rc1 problems fixed.
https://sourceforge.net/projects/antix- ... /antiX-17/

I'd like to say that something was broken somehow on the release.

antix 17rc: Conky had been showing wifi Up/Down inet connection graph right upon my wifi got connected.

antix 17 final: Conky is never reacting to show up that Up/Down connection graph after wifi connected.

Tested on Desktop PC and Laptop. Both 32bit or 64bit releases have an issue.

Posted: **Sat Nov 04, 2017 1:02 pm**

Darn, It looks like I deleted my antix 17 rc1 iso when I downloaded the final. Stupid me....

Is there a place I can still get the rc1 iso to test again? I did not see it at sourceforge.
I had it on the USB stick, but I over wrote the stick with final. (That's how I know the USB stick is OK, it worked on the beta and rc1)

I should have done a CD disk burn!

Posted: **Sat Nov 04, 2017 4:07 pm**

Distrowatch lists it
https://distrowatch.com/?newsid=09982

Posted: **Sat Nov 04, 2017 5:14 pm**

That link just goes to the same sourceforge link.
And the testing directory is all empty, and the main is all cleaned up, with the only rc items are some deltas, and I don't know how that works. Delta against what file [other rc iso?].

Like me anti has probably just cleaned up the directories once final arrives. I did the same thing, and I wish I had not deleted old isos. I have the space.
USB install fast, but a burned disk is s record of what booted, and I tossed a few away recently, "cleaning" up.

I found an old antix17 beta 1 disk, it does install, but I cant get the sound working with the generic option as in later isos.

So, beta1 produces a bootable install after updating grub

antix17 final does not, booting the install has the error listed above and now additional

Code: Select all

ACPI Exception : AE_AML_OPERAND_TYPE could not execute arguments for [IOB2] (region 20160930/nsinit-412)
waiting for /dev to fully populate Address 0x0cd6 already in use kvm disabled

Posted: **Sat Nov 04, 2017 9:58 pm**

http://linuxtracker.org/index.php?page= ... 0&active=0

There seems to be a torrent still, although I cant imagine what you tell.

But you can try.

Posted: **Sun Nov 05, 2017 12:17 am**

caprea

Thanks for the lead, but that torrent is dead, no one to download from.

Thanks anyway...

MX Linux Forum

no video after antiX 17 kernel upgrade to 4.13

no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13

Re: no video after antiX 17 kernel upgrade to 4.13