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

Mainline Kernel 4.14.13 won't boot

Help for Current Versions of MX
Post Reply
Message
Author
roadapathy
Forum Novice
Forum  Novice
Posts: 66
Joined: Sun Dec 31, 2017 5:19 pm

Mainline Kernel 4.14.13 won't boot

#1 Post by roadapathy » Sat Jan 13, 2018 5:28 pm

I am trying to compile my Linux Kernel with no luck. I had 4.13.x working fine though but 4.14.13 gives me strange problems that I didn't have with super buggy Xubuntu/Ubuntu 16.x through 17.x


I use this command, which again works fine for 4.13.x
sudo fakeroot sudo make -j`getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-ryzenz KDEB_PKGVERSION=1 CFLAGS="-O3 -march=native" CPPFLAGS="-O3 -march=native" CXXFLAGS="-O3 -march=native" X_CFLAGS="-O3 -march=native"

Things look fairly normal here, with only a warning:
dpkg-deb: building package 'linux-headers-4.14.12-ryzenz' in '../linux-headers-4.14.12-ryzenz_1_amd64.deb'.
dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_1_amd64.deb'.
dpkg-deb: building package 'linux-image-4.14.12-ryzenz' in '../linux-image-4.14.12-ryzenz_1_amd64.deb'.
dpkg-source: info: using source format '3.0 (custom)'
dpkg-source: info: building linux-4.14.12-ryzenz in linux-4.14.12-ryzenz_1.dsc
dpkg-source: warning: missing information for output field Standards-Version
dpkg-genchanges: info: including full source code in upload

Then to install:
cd ..
sudo dpkg -i *headers*.deb

Then a strange error after:
sudo dpkg -i *image*.deb

Selecting previously unselected package linux-image-4.14.12-ryzenz.
(Reading database ... 484003 files and directories currently installed.)
Preparing to unpack linux-image-4.14.12-ryzenz_1_amd64.deb ...
Unpacking linux-image-4.14.12-ryzenz (1) ...
Setting up linux-image-4.14.12-ryzenz (1) ...
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Error! Bad return status for module build on kernel: 4.14.12-ryzenz (x86_64)
Consult /var/lib/dkms/nvidia-current/384.98/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.14.12-ryzenz (x86_64)
Consult /var/lib/dkms/nvidia-legacy-304xx/304.137/build/make.log for more information.
update-initramfs: Generating /boot/initrd.img-4.14.12-ryzenz
Generating grub configuration file ...
using custom appearance settings


That doesn't fully stop the booting process though. It will boot and look normal until it reaches what I presume to be the Nvidia driver part, or possibly network.

I did this to see the error:
cat /var/lib/dkms/nvidia-current/384.98/build/make.log

The end of the make.log looks like this, which sounds like Nvidia driver issues:
make[2]: *** [/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_va_block.o] Error 1
make[2]: *** Waiting for unfinished jobs....
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_tracker_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_kvmalloc_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_channel_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_push_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_ce_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_lock_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_perf_events_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_get_rm_ptes_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_perf_module_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_pmm_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_page_tree_test.o";
./tools/objtool/objtool orc generate --no-fp "/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm/uvm8_perf_utils_test.o";
make[2]: *** wait: No child processes. Stop.
Makefile:1507: recipe for target '_module_/var/lib/dkms/nvidia-current/384.98/build' failed
make[1]: *** [_module_/var/lib/dkms/nvidia-current/384.98/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.14.12-ryzenz'
Makefile:81: recipe for target 'modules' failed
make: *** [modules] Error 2


I know that I should know how to do this but I don't: How do we remove the Nvidia driver from MX Linux?
Another question is: How can we install the Nvidia driver during a "recovery mode" or CLI-only mode during boot before the GUI is loaded? I like doing it that way because I like to uncompress the Nvidia driver and add some GCC CFLAGS (like -O3 -march=native)?

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

Re: Mainline Kernel 4.14.13 won't boot

#2 Post by Stevo » Sat Jan 13, 2018 6:29 pm

I don't think the 384.98 Nvidia supports the build on 4.14 kernels. You might try the new 384.111 version in stretch-backports, or the 375.82 in our normal repo. I'm currently looking at porting over that 384.111 to our testing repo.

Post Reply

Return to “MX Help”