Neil Bothwick wrote:
> On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
>
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
l
On Fri, 21 Apr 2023 09:55:24 -0500, Dale wrote:
> >> 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.
Dr Rainer Woitok wrote:
> Dale,
>
> On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
>
>> ...
>> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
>> * Repository: mine
> Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
> vers" version 470.182.03 is still in the n
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 11:55, Dale wrote:
>> Did something change with overlays? In the past, I copied the ebuild
>> over to local overlay and ran the ebuild command for the manifest. It
>> downloaded everything that was needed. Now, it seems it doesn't. They
>> add a ste
Neil Bothwick wrote:
> On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
>
>> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
>> would pick up the needed files. Guess not. I decided to do some more
>> digging. I noticed that the same version is still in the tree. I
>> cop
Neil Bothwick wrote:
> On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
>
>> 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
>> lik
On Thu, 20 Apr 2023 20:33:22 -0500, Dale wrote:
> 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.
Not really,
On Fri, 21 Apr 2023 03:58:11 -0500, Dale wrote:
> I did a emerge -ef nvidia-drivers and it still fails. I was hoping that
> would pick up the needed files. Guess not. I decided to do some more
> digging. I noticed that the same version is still in the tree. I
> copied the ebuild a while back
On Thu, Apr 20, 2023 at 05:36:23PM -0500, Dale wrote:
> /var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
> No such file or directory
This sounds like you copied the ebuild to your local overlay but not
the files/ dir which includes the patch. So
Dale,
On Thursday, 2023-04-20 17:36:23 -0500, you wrote:
> ...
> * Package: x11-drivers/nvidia-drivers-470.182.03:0/470
> * Repository: mine
Maybe I'm missing something, but as of today "x11-drivers/nvidia-dri-
vers" version 470.182.03 is still in the normal Gentoo tree. So why use
your
On Fri, 21 Apr 2023 at 11:55, Dale wrote:
> Did something change with overlays? In the past, I copied the ebuild
> over to local overlay and ran the ebuild command for the manifest. It
> downloaded everything that was needed. Now, it seems it doesn't. They
> add a step? I miss a step that sli
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 10:58, Dale wrote:
>> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
>> since it was trying to use it. I don't understand why it doesn't work
>> tho. I looked at the ebuild in the tree and my overlay, they look the
>> same, in
On Fri, 21 Apr 2023 at 10:58, Dale wrote:
> I put my local ebuilds in /usr/local/portage. Obviously emerge sees it
> since it was trying to use it. I don't understand why it doesn't work
> tho. I looked at the ebuild in the tree and my overlay, they look the
> same, including the patches from d
Frank Steinmetzger wrote:
> Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
>
>> 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 install
Am Thu, Apr 20, 2023 at 08:33:22PM -0500 schrieb Dale:
> 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 e
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 thou
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 e
On Thu, Apr 20, 2023 at 3:36 PM Dale wrote:
> * patch -p1 failed with
>
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch
You know I don't run Gentoo, right?
That looks weird to me - building 470.182.03 but patching it with
470.141.03.
Jus
Howdy,
I tried a while back to upgrade my kernel but nvidia didn't like it.
Given I can do this a piece at a time, I thought I'd try again. Kernel
compiled fine and when nvidia complained about missing options, I fixed
those and recompiled the kernel. I finally got it happy as far as
missing ke
19 matches
Mail list logo