Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

4.14.9 Kernel crashes

Message
Author
caprea
Forum Regular
Forum Regular
Posts: 111
Joined: Sat Aug 23, 2014 7:01 am

Re: 4.14.9 Kernel crashes

#31 Post by caprea » Sun Jan 14, 2018 6:31 pm

There is a depency of the debian nvidia-kernel-dkms for libelf-dev .
I downloaded and installed the 384.111 directly from the nvidia-side
Thats the difference I think.

entropyfoe , then its maybe enough to install libelf-dev and then install the nvidia-drivers and 4.14.12-kernel again.

User avatar
entropyfoe
Forum Regular
Forum Regular
Posts: 792
Joined: Thu Apr 19, 2007 11:42 am

Re: 4.14.9 Kernel crashes

#32 Post by entropyfoe » Wed Jan 17, 2018 12:31 am

caprea,

Let me clarify what your recommend:
1. With synaptic install libelf-dev
2. Do I need to reinstall the nvidia driver? I already have it under the other kernel.
3. With the MX package manager, reinstall the 4.14.12 kernel
Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-17.1, P4=antiX-17
1TB SSD sda1= Data, 2TB WD =backups
on-board ethernet & sound

caprea
Forum Regular
Forum Regular
Posts: 111
Joined: Sat Aug 23, 2014 7:01 am

Re: 4.14.9 Kernel crashes

#33 Post by caprea » Wed Jan 17, 2018 3:27 am

answered on antixforum

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16174
Joined: Fri Dec 15, 2006 8:07 pm

Re: 4.14.9 Kernel crashes

#34 Post by Stevo » Wed Jan 17, 2018 4:53 pm

I can't remember if I had to patch the MX version of the 375.82 Nvidia driver to build with the 4.14 kernel...I don't believe so. I do know that at least broadcom-sta-dkms, ndiswrapper, and the Debian virtualbox had to be updated, the stretch-backports versions of those are not compatible with the new stretch-backports 4.14 kernel--besides the libelf-dev dependency problem.

caprea
Forum Regular
Forum Regular
Posts: 111
Joined: Sat Aug 23, 2014 7:01 am

Re: 4.14.9 Kernel crashes

#35 Post by caprea » Mon Jan 22, 2018 1:19 am

The nvidia-driver 375.82-9mx17+1 works for the 4.14-kernels
Also on antix with the 4.14.12-antix-kernel.
You have to enbable the mx-repo on antix to install or update to this graphic-driver.

So I like to say Thank you to the mx-developers to keep the 375.82-9 version.
Newer kernels can be installed to a stretch-based system.

Sadly the 384.111-nvidia driver although I installed libelf-dev couldnt get installed bc of depency errors.
Today I saw there have been made changes to the driver from backports
https://tracker.debian.org/pkg/nvidia-graphics-drivers

The nvidia-kernel-dkms doesnt depend anymore on libelf-dev
https://packages.debian.org/de/stretch- ... ernel-dkms

I will give the 384.111 from debian another try tomorrow.

caprea
Forum Regular
Forum Regular
Posts: 111
Joined: Sat Aug 23, 2014 7:01 am

Re: 4.14.9 Kernel crashes

#36 Post by caprea » Thu Jan 25, 2018 11:55 am

Tried again today to install the 384.111-nvidia driver with dd-mx, but there are still depency-errors

Code: Select all

Installing latest nvidia-detect package

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
  nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 114 not upgraded.
Need to get 183 kB of archives.
After this operation, 1.024 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian stretch-backports/non-free amd64 nvidia-detect amd64 384.111-3~bpo9+1 [183 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 183 kB in 0s (542 kB/s)
(Reading database ... 222454 files and directories currently installed.)
Preparing to unpack .../nvidia-detect_384.111-3~bpo9+1_amd64.deb ...
Unpacking nvidia-detect (384.111-3~bpo9+1) over (384.111-1~bpo9+2) ...
Setting up nvidia-detect (384.111-3~bpo9+1) ...

Main repo candidate is:   375.82-9mx17+1
Debian backports candidate is:   384.111-3~bpo9+1
Installed is:  375.82-9mx17+1

Which driver do you wish to install

Main repos or debian-backports?

1: Main 375.82-9mx17+1

2: debian-backports 384.111-3~bpo9+1

3: Exit

Enter Number of selection
2
Ok...



Need driver: nvidia-driver (384.111-3~bpo9+1)
 packages to install are  nvidia-driver nvidia-settings nvidia-kernel-dkms libgl1-nvidia-glx:i386 nvidia-xconfig

Continue?
  1) yes (default)
  2) no
Drücke <Enter> für den Vorgabewert Eintrag
Verwende 'q' für Beenden
1
Frontend: 
Nvidia command  = apt-get install --reinstall -y --force-yes -t $ BP nvidia-driver nvidia-settings nvidia-kernel-dkms libgl1-nvidia-glx:i386 nvidia-xconfig
Reading package lists...
Building dependency tree...
Reading state information...
dpkg-preconfigure: unable to re-open stdin: No such file or directory
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 47 not upgraded.
                                                                              Need to get 0 B/11,2 MB of archives.
                        After this operation, 0 B of additional disk space will be used.
                                                                                        (R(Reading database ... 222454 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.14.12-antix.1-amd64-smp_4.14.12-antix.1-amd64-smp-1_amd64.deb ...
Unpacking linux-headers-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) over (4.14.12-antix.1-amd64-smp-1) ...
Preparing to unpack .../build-essential_12.3_amd64.deb ...
Unpacking build-essential (12.3) over (12.3) ...
Preparing to unpack .../firmware-linux-nonfree_20170823-1mx17+1_all.deb ...
Unpacking firmware-linux-nonfree (20170823-1mx17+1) over (20170823-1mx17+1) ...
Setting up linux-headers-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) ...
Setting up build-essential (12.3) ...
Setting up firmware-linux-nonfree (20170823-1mx17+1) ...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver : Depends: nvidia-driver-libs (= 384.111-3~bpo9+1) but it is not going to be installed or
                          nvidia-driver-libs-nonglvnd (= 384.111-3~bpo9+1) but it is not going to be installed
                 Recommends: nvidia-settings (>= 384) but 375.66-1 is to be installed
E: Unable to correct problems, you have held broken packages.
/usr/local/bin/ddm-mx: line 456: creating /etc/X11/xorg.conf file: No such file or directory

Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Finished
I closed dd-mx ,
enabled the debian-stretch-backports repository and looked in reloaded synaptic for the package nvidia-driver-libs and still 375.82 is the latest version.

nvidia-driver-libs-nonglvnd is there with latest version 384.111
but it depends on libgl1-nvidia-glx and libegl1-nvidia and both are latest version 375.82

So out of pure curiosity and because I dont have much experience with debian-backports ,could someone tell me please
Is this normal behaviour of backports that you have to wait for the depencies?
Or is something else going wrong?

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16174
Joined: Fri Dec 15, 2006 8:07 pm

Re: 4.14.9 Kernel crashes

#37 Post by Stevo » Thu Jan 25, 2018 4:50 pm

We might have to add "-t backports" to the installer script to make sure it install the other libraries from backports to match. This is because backports is purposely set at a lower priority than other repos. You could always try the manual install from backports that Debian users have to use on the command line; I think that's laid out in the Debian wiki.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: 4.14.9 Kernel crashes

#38 Post by dolphin_oracle » Thu Jan 25, 2018 5:12 pm

Stevo wrote:We might have to add "-t backports" to the installer script to make sure it install the other libraries from backports to match. This is because backports is purposely set at a lower priority than other repos. You could always try the manual install from backports that Debian users have to use on the command line; I think that's laid out in the Debian wiki.
ddm-mx uses -t to do the install when choosing backports option.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9298
Joined: Sun Dec 16, 2007 1:17 pm

Re: 4.14.9 Kernel crashes

#39 Post by dolphin_oracle » Thu Jan 25, 2018 5:19 pm

wait, ddm-mx should not be installing nvidia-xconfig when installing from backports. I thought I made this change already. I'll check tonight.

nvidia-xconfig causes dependency issues. there is not backports version of that as they have deprecated making xorg.conf files with nvidia.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

caprea
Forum Regular
Forum Regular
Posts: 111
Joined: Sat Aug 23, 2014 7:01 am

Re: 4.14.9 Kernel crashes

#40 Post by caprea » Thu Jan 25, 2018 5:25 pm

What I dont understand is that synaptic ,when stretch-debian-backports is enabled shows me version 375.82 for nvidia-driver-libs

This is the right repo ?
deb http://ftp.debian.org/debian/ stretch-backports main contrib non-free

Post Reply

Return to “antiX”