[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-user
Subject: Re: [gentoo-user] Nvidia-drivers fails to patch
From: Dale <rdalek1967 () gmail ! com>
Date: 2023-04-21 1:33:22
Message-ID: 3dd9f342-35bf-ee5a-4d73-0a8a21668c6c () gmail ! com
[Download RAW message or body]
Morgan Wesström wrote:
> On 2023-04-21 00:36, Dale wrote:
>> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/temp/environment:
>> line 1291:
>> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
>>
>> No such file or directory
>>
>> Any thoughts? Ideas?
>>
>
> I couldn't reproduce the error here. One thing that comes to mind is
> that your system might have an error in its repository configuration.
> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files is a
> symlink and should point to your main repository, normally
> /var/db/repos/gentoo/x11-drivers/nvidia-drivers/files. When the emerge
> fails, can you check what that symlink actually points to and if this
> is where your repository is stored? What is the output of emerge
> --info? (Repository info is in that output).
>
> /Morgan
>
>
I cleared the tmp files to give it a fresh start. It still failed. The
directory and files it complains about being missing, they are. I went
to the ebuild to see what patches are supposed to be installed. This is
the part of the ebuild.
PATCHES=(
"${FILESDIR}"/nvidia-drivers-470.141.03-clang15.patch
"${FILESDIR}"/nvidia-modprobe-390.141-uvm-perms.patch
"${FILESDIR}"/nvidia-settings-390.144-desktop.patch
"${FILESDIR}"/nvidia-settings-390.144-no-gtk2.patch
"${FILESDIR}"/nvidia-settings-390.144-raw-ldflags.patch
)
As you can see, it wants to apply patches from several versions so while
odd, I guess it really does it that way. I suspect given the age of the
drivers that the patches no longer exist or something. I'd think it
would report it couldn't download the files but maybe not. I may be
running out of luck here. Odd thing is, it compiled a while back.
I tried to google and find the patch, no luck. No idea where it comes
from. May run emerge -ef nvidia-drivers and see if it works.
Also, I switch to the current kernel, it failed in the same way. It
isn't just the new kernel, it seems to be any of them. I wonder how
hard it is to switch to that other driver. From the wiki page, it looks
like a big deal.
Dale
:-) ;-)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic