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

[Fixed] 4.14.12 kernel + nvidia driver

Help for Current Versions of MX
Message
Author
dr-kart
Forum Regular
Forum Regular
Posts: 129
Joined: Sun Oct 22, 2017 8:12 pm

[Fixed] 4.14.12 kernel + nvidia driver

#1 Post by dr-kart » Mon Jan 08, 2018 8:00 am

moved to

Code: Select all

4.14.0-3-amd64 #1 SMP Debian 4.14.12-2~mx17+1 (2018-01-06)
but failed to install nvidia video drivers via ddm-mx then (both main 375 and newer 384 backported one)

So I did

Code: Select all

ddm-mx -p nvidia 
then tried

Code: Select all

ddm-mx -i nvidia 
no joy.
Last edited by dr-kart on Tue Jan 09, 2018 6:12 pm, edited 1 time in total.

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

Re: 4.14.12 kernel + nvidia driver

#2 Post by dolphin_oracle » Mon Jan 08, 2018 8:53 am

install

Code: Select all

libelf-dev
and try ddm-mx again.

we are still working on update strategies for the 4.14.12 kernel. we uncovered that depend issue last nite.
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.

dr-kart
Forum Regular
Forum Regular
Posts: 129
Joined: Sun Oct 22, 2017 8:12 pm

Re: 4.14.12 kernel + nvidia driver

#3 Post by dr-kart » Mon Jan 08, 2018 12:05 pm

installed libelf-dev and libelf-dev:386 as well

ddm-mx logs:

1. As for 384 backported

Code: Select all

...
DKMS: install completed.
Setting up nvidia-legacy-304xx-driver (304.137-3~bpo9+1) ...
Processing triggers for nvidia-alternative:i386 (384.98-3~bpo9+1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvidia/current because link group nvidia is broken
Setting up nvidia-kernel-dkms (384.98-3~bpo9+1) ...
Loading new nvidia-current-384.98 DKMS files...
Building for 4.14.0-3-amd64
Building initial module for 4.14.0-3-amd64
Error! Bad return status for module build on kernel: 4.14.0-3-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/384.98/build/make.log for more information.
Setting up nvidia-driver (384.98-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for glx-alternative-nvidia:i386 (0.7.4) ...
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for update-glx (0.7.4) ...
Processing triggers for glx-alternative-nvidia:i386 (0.7.4) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.14.0-3-amd64
New X configuration file written to '/etc/X11/xorg.conf'

Finished
but I have black screen at the end (same as before with no libelf-dev installed)

2. Main 375 even worse now.

Code: Select all

...
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) ...
Preparing to unpack .../linux-headers-4.14.0-3-amd64_4.14.12-2~mx17+1_amd64.deb ...
Unpacking linux-headers-4.14.0-3-amd64 (4.14.12-2~mx17+1) over (4.14.12-2~mx17+1) ...
Setting up build-essential (12.3) ...
Setting up linux-headers-4.14.0-3-amd64 (4.14.12-2~mx17+1) ...
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:
 libgl1-nvidia-glx:i386 : Depends: libnvidia-glcore:i386 (= 375.82-9mx17+1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Finished
I notice couple 'FATAL ERROR' messages during boot process saying something about nvidia module. This msg comes out every time I boot with nvidia proprietary drivers. What log file should I look at?

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

Re: 4.14.12 kernel + nvidia driver

#4 Post by dolphin_oracle » Mon Jan 08, 2018 1:07 pm

for the 384 backport version, I would try removing /etc/X11/xorg.conf and rebooting to see if the driver picks up.
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.

dr-kart
Forum Regular
Forum Regular
Posts: 129
Joined: Sun Oct 22, 2017 8:12 pm

Re: 4.14.12 kernel + nvidia driver

#5 Post by dr-kart » Mon Jan 08, 2018 1:34 pm

removing /etc/X11/xorg.conf
didn't help.

But I made "screenshot"
its DRM module error
Image

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

Re: 4.14.12 kernel + nvidia driver

#6 Post by dolphin_oracle » Mon Jan 08, 2018 1:37 pm

dr-kart wrote:
removing /etc/X11/xorg.conf
didn't help.

But I made "screenshot"
its DRM module error
Image
shoot, I missed that, sorry.

reported up the line to the repo guys.
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
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4480
Joined: Wed Jul 12, 2006 4:05 pm

Re: 4.14.12 kernel + nvidia driver

#7 Post by timkb4cq » Mon Jan 08, 2018 2:30 pm

You shouldn't need to install any i386 libraries to install nvidia drivers on a 64bit system.

Your best bet for clearing up the mess is to use sgfxi to install the nvidia driver for now. Just <Ctl><Alt><F1> into a console terminal, log in as root and run

Code: Select all

sgfxi
Just follow the prompts.
It will remove ddm-mx in the process, but that can be reinstalled later if you wish to use it to switch to a different driver.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6222
Joined: Wed Jul 12, 2006 2:10 am

Re: 4.14.12 kernel + nvidia driver

#8 Post by Eadwine Rose » Mon Jan 08, 2018 2:33 pm

Just make sure you run sgfxi TWICE. Complete one, then repeat.
MX-17.1_x64 Horizon 3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP Envy5030

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4480
Joined: Wed Jul 12, 2006 4:05 pm

Re: 4.14.12 kernel + nvidia driver

#9 Post by timkb4cq » Mon Jan 08, 2018 2:43 pm

...
DKMS: install completed.
Setting up nvidia-legacy-304xx-driver (304.137-3~bpo9+1) ...
Processing triggers for nvidia-alternative:i386 (384.98-3~bpo9+1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvidia/current because link group nvidia is broken
Setting up nvidia-kernel-dkms (384.98-3~bpo9+1) ...
It looks as though you have different versions of i386 & amd64 libraries fighting with each other. I don't think ddm-mx allows for the possibility that you have installed both i386 & amd64 versions of the nvidia drivers on the same install. That's definitely an unusual corner case.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

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

Re: 4.14.12 kernel + nvidia driver

#10 Post by Stevo » Mon Jan 08, 2018 3:21 pm

ddm-mx installs some of the 32-bit Nvidia libraries on a 64-bit system in order to support Steam or Wine games, such as the openGL one, but versions have to match exactly. The mismatch probably where the problem lies.

Post Reply

Return to “MX Help”