Redcore Linux Project Forum

Unfortunately, no one can be told what Redcore Linux is. You have to see it for yourself!

You are not logged in.

#1 Archived posts » Nvidia driver failed instalation » 2022-07-11 10:00:06

Al
Replies: 2

Hello , I recently installed Redcore OS but i seem to run into a little problem while installing my Nvidia drivers . If somebody would be so kind to help me .

* Package:    sys-kernel/nvidia-drivers-legacy-dkms-390.147
* Repository: redcore
* USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES:   compressdebug network-sandbox preserve-libs sandbox splitdebug usersandbox
>>> Unpacking source...
Creating directory NVIDIA-Linux-x86_64-390.147
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 390.147..............................................................................................
.......................................................................................................................................................................
.......................................................................................................................................................................
........................................................................................
>>> Source unpacked in /var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/work
>>> Preparing source in /var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/work/NVIDIA-Linux-x86_64-390.147 ...
* Applying dkms.patch ...
[ ok ]
* Applying kernel-5.14.patch ...
patching file kernel/conftest.sh


1 out of 1 hunk FAILED -- saving rejects to file kernel/nvidia/nvlink_linux.c.rej
patching file kernel/nvidia/os-interface.c
Hunk #1 FAILED at 580.
1 out of 1 hunk FAILED -- saving rejects to file kernel/nvidia/os-interface.c.rej
patching file kernel/nvidia-drm/nvidia-drm-drv.c
Hunk #1 FAILED at 811.
1 out of 1 hunk FAILED -- saving rejects to file kernel/nvidia-drm/nvidia-drm-drv.c.rej
patching file kernel/nvidia-drm/nvidia-drm.Kbuild
Hunk #1 FAILED at 102.
1 out of 1 hunk FAILED -- saving rejects to file kernel/nvidia-drm/nvidia-drm.Kbuild.rej
[ !! ]
* ERROR: sys-kernel/nvidia-drivers-legacy-dkms-390.147::redcore failed (prepare phase):
*   patch -p1  failed with /var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/files/kernel-5.14.patch
*
* Call stack:
*               ebuild.sh, line  127:  Called src_prepare
*             environment, line 2043:  Called default
*      phase-functions.sh, line  858:  Called default_src_prepare
*      phase-functions.sh, line  923:  Called __eapi6_src_prepare
*             environment, line  243:  Called eapply '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/files/dkms.patch' '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/files/kernel-5.14.patch'
*             environment, line  527:  Called _eapply_patch '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/files/kernel-5.14.patch'
*             environment, line  465:  Called __helpers_die 'patch -p1  failed with /var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/files/kernel-5.14.patch'
*   isolated-functions.sh, line  112:  Called die
* The specific snippet of code:
*              die "$@"
*
* If you need support, post the output of `emerge --info '=sys-kernel/nvidia-drivers-legacy-dkms-390.147::redcore'`,
* the complete build log and the output of `emerge -pqv '=sys-kernel/nvidia-drivers-legacy-dkms-390.147::redcore'`.
* The complete build log is located at '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/temp/environment'.
* Working directory: '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/work/NVIDIA-Linux-x86_64-390.147'
* S: '/var/tmp/portage/sys-kernel/nvidia-drivers-legacy-dkms-390.147/work/NVIDIA-Linux-x86_64-390.147'

Board footer

Powered by FluxBB