Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Gentoo>
  3. User
Nvidia-drivers fails to patch
rdalek1967 at gmail
Apr 20, 2023, 3:36 PM
Post #1 of 21 (462 views)
Permalink
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 kernel options goes.  Then it fails with this error. 


* Package:    x11-drivers/nvidia-drivers-470.182.03:0/470
 * Repository: mine
 * USE:        X abi_x86_64 amd64 driver elibc_glibc kernel_linux tools
userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.1.23-gentoo
 * Checking for suitable kernel configuration options ...
 [ ok ]
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-470.182.03.run to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Unpacking nvidia-installer-470.182.03.tar.bz2 to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Unpacking nvidia-modprobe-470.182.03.tar.bz2 to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Unpacking nvidia-persistenced-470.182.03.tar.bz2 to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Unpacking nvidia-settings-470.182.03.tar.bz2 to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Unpacking nvidia-xconfig-470.182.03.tar.bz2 to
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Source unpacked in
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work
>>> Preparing source in
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/work ...
 * Applying nvidia-drivers-470.141.03-clang15.patch ...
/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
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/temp/environment:
line 1294:
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
No such file or directory
 [ !! ]
 * ERROR: x11-drivers/nvidia-drivers-470.182.03::mine failed (prepare
phase):
 *   patch -p1  failed with
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch
 *
 * Call stack:
 *               ebuild.sh, line  136:  Called src_prepare
 *             environment, line 3731:  Called default
 *      phase-functions.sh, line  872:  Called default_src_prepare
 *      phase-functions.sh, line  948:  Called __eapi8_src_prepare
 *             environment, line  468:  Called eapply '--'
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch'
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-modprobe-390.141-uvm-perms.patch'
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-settings-390.144-desktop.patch'
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-settings-390.144-no-gtk2.patch'
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-settings-390.144-raw-ldflags.patch'
 *             environment, line 1359:  Called _eapply_patch
'/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch'
 *             environment, line 1297:  Called __helpers_die 'patch -p1 
failed with
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *              die "$@"
 *


According to the nvidia website, I'm using the correct version.  Thing
is, it's old.  I may have to get a newer video card.  If I can correct
this error tho and it work when I reboot, it would be great.  I don't
think that driver version is in the tree anymore.  It shows it is in my
local overlay.  Given the next version of driver doesn't work with this
card, I may be stuck with current kernel version or buying a newer
card.  Do I need to switch to a different driver?  Novau or something? 

Any thoughts?  Ideas? 

Thanks. 

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
markknecht at gmail
Apr 20, 2023, 4:44 PM
Post #2 of 21 (462 views)
Permalink
On Thu, Apr 20, 2023 at 3:36?PM Dale <rdalek1967@gmail.com> wrote:
<SNIP>
> * patch -p1 failed with
>
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch
<SNIP>

You know I don't run Gentoo, right?

That looks weird to me - building 470.182.03 but patching it with
470.141.03.
Just looks weird...

I think the other day someone - maybe Thelma? - had a problem
where there was something left over in some 'patch' directory.
Possibly you have something like that going on?

You know I don't run Gentoo, right? ;-)

Cheers,
Mark
Re: Nvidia-drivers fails to patch [ In reply to ]
gentoo-bugzilla at pp
Apr 20, 2023, 5:13 PM
Post #3 of 21 (462 views)
Permalink
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
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 20, 2023, 6:33 PM
Post #4 of 21 (462 views)
Permalink
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

:-)  ;-)
Re: Nvidia-drivers fails to patch [ In reply to ]
Warp_7 at gmx
Apr 21, 2023, 12:24 AM
Post #5 of 21 (462 views)
Permalink
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 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. 

If I read your error output correctly, it’s not that the patch file is
missing, but that a file that is mentioned inside the patch is.

--
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

Error: this virus requires DirectX and 64 MB of RAM!

Attached Files:

Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 1:58 AM
Post #6 of 21 (462 views)
Permalink
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 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. 
> If I read your error output correctly, it’s not that the patch file is
> missing, but that a file that is mentioned inside the patch is.
>


Oh.  The output of emerge has always been sort of cryptic.  LOL  I just
hope nothing happens where I have to re-emerge it.  At this point, I'd
be in a pickle if the drivers failed and needed to be reinstalled. 

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 to a local overlay to make sure I don't
lose it.  It seems emerge gives my local overlay priority over the one
in the tree.  I renamed the ebuild in my overlay with .old tacked on. 
It emerges fine after that since it uses the ebuild in the tree.  It
seems my overlay is broken somehow.  Likely a design improvement.  ;-) 

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 different versions. 

Now I need to figure out why the overlay version isn't working.  I've
had occasion to need older versions before, due to some bug or
something.  Gonna see if it builds against the new kernel now.  Let us
pray. 

Always something.  :/

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
arve.barsnes at gmail
Apr 21, 2023, 2:27 AM
Post #7 of 21 (462 views)
Permalink
On Fri, 21 Apr 2023 at 10:58, Dale <rdalek1967@gmail.com> 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 different versions.
>
> Now I need to figure out why the overlay version isn't working. I've
> had occasion to need older versions before, due to some bug or
> something. Gonna see if it builds against the new kernel now. Let us
> pray.

If your ebuild and the repo ebuild are the same, that means that the
patch was changed, look in your
/usr/local/portage/x11-drivers/nvidia-drivers/files/ folder and
compare with the current files.

Regards,
Arve
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 2:55 AM
Post #8 of 21 (462 views)
Permalink
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 10:58, Dale <rdalek1967@gmail.com> 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 different versions.
>>
>> Now I need to figure out why the overlay version isn't working. I've
>> had occasion to need older versions before, due to some bug or
>> something. Gonna see if it builds against the new kernel now. Let us
>> pray.
> If your ebuild and the repo ebuild are the same, that means that the
> patch was changed, look in your
> /usr/local/portage/x11-drivers/nvidia-drivers/files/ folder and
> compare with the current files.
>
> Regards,
> Arve
>
>


Well, there's the problem.  There's no files directory there.  I ran the
ebuild command when I added it to the overlay, I don't think it
downloaded anything.  I just copied the ebuild file from the Gentoo
tree.  If I ever need to emerge from the overlay, I hope it works now. 

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 slipped my mind? 

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
arve.barsnes at gmail
Apr 21, 2023, 3:22 AM
Post #9 of 21 (462 views)
Permalink
On Fri, 21 Apr 2023 at 11:55, Dale <rdalek1967@gmail.com> 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 slipped my mind?

I don't think the files/ directory contents were ever downloaded by
the ebuilds, they are a part of the portage tree, so they appear when
you sync. Maybe the files/ contents from the main tree were available
for your overlay ebuild somehow? I've never had that luxury, so now
I*m wondering how your ebuild ever worked :-)

Regards,
Arve
Re: Nvidia-drivers fails to patch [ In reply to ]
rainer.woitok at gmail
Apr 21, 2023, 3:42 AM
Post #10 of 21 (462 views)
Permalink
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 personal repo? Do you have a local patch applied?

Sincerely,
Rainer
Re: Nvidia-drivers fails to patch [ In reply to ]
ionen at gentoo
Apr 21, 2023, 4:21 AM
Post #11 of 21 (462 views)
Permalink
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 the patch is not found.

> this error tho and it work when I reboot, it would be great.  I don't
> think that driver version is in the tree anymore.  It shows it is in my
> local overlay.

It is in the tree, 470.x is a long-term-support branch and as long as
NVIDIA continue to support it there's no reason to drop it from the
tree. Just use the ::gentoo version.

470.182.03 is even fairly recent, was a security release added to the
tree last month followed by the cleanup of the vulnerable 470.161.03.

https://packages.gentoo.org/packages/x11-drivers/nvidia-drivers

--
ionen

Attached Files:

Re: Nvidia-drivers fails to patch [ In reply to ]
neil at digimed
Apr 21, 2023, 6:28 AM
Post #12 of 21 (462 views)
Permalink
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 to a local overlay to make sure I don't
> lose it.  It seems emerge gives my local overlay priority over the one
> in the tree.  I renamed the ebuild in my overlay with .old tacked on. 
> It emerges fine after that since it uses the ebuild in the tree.  It
> seems my overlay is broken somehow.  Likely a design improvement.  ;-) 

That's the default by design. If you copy an ebuild to your overlay, it's
usually because you want to make changes to it, so it should be given
priority. You can change the priority of overlays in
/etc/portage/repos.conf, or you can simply mask the overlay version.


--
Neil Bothwick

Dream as if you'll live forever. Live as if you'll die today.
Re: Nvidia-drivers fails to patch [ In reply to ]
neil at digimed
Apr 21, 2023, 6:30 AM
Post #13 of 21 (462 views)
Permalink
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, AFAIR. You just enable nouveau drivers in your kernel config,
uninstall the nvidia package and reboot. This assumes you haven't got any
direct references to the nvisia driver in /etc/xorg.conf*.


--
Neil Bothwick

New sig wanted good price paid.
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 7:55 AM
Post #14 of 21 (462 views)
Permalink
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
>> like a big deal. 
> Not really, AFAIR. You just enable nouveau drivers in your kernel config,
> uninstall the nvidia package and reboot. This assumes you haven't got any
> direct references to the nvisia driver in /etc/xorg.conf*.
>
>


I think, pretty much certain, I have it set to nvidia in xorg.conf. 
This is a old install.  If I recall correctly, I have to change that. 
Also, I'd need to edit make.conf I think.  I read the wiki thingy a few
times.  It's mostly undoing things but with the age of this install, I
don't think my old way is the new way.  Yep.  I'm getting better at
grep.  lol

root@fireball / # cat /etc/X11/xorg.conf | grep driver
    Driver         "mouse"
    Driver         "kbd"
    Driver         "nvidia"
root@fireball / #cat /etc/make.conf | grep video_cards
VIDEO_CARDS="nvidia vesa"
root@fireball / #

I think I'd have to change those.  It may or may not rebuild some
packages.  Would I need to leave out vesa or OK to leave it in?

The easiest part, enable in kernel and build it.  With your nifty dracut
command option, it just works. LOL  By the way, the nvidia-driver
package compiled fine against the new kernel.

I may be into to much today to play with this tho.  Maybe late today. 
Tomorrow depending on weather. 

Next time I copy a ebuild to a local overlay, I need to remember to copy
any files directory over too.  I don't recall ever doing that before. 

Thanks to all.  Gotta do some things so may reply to others later. 

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 9:23 AM
Post #15 of 21 (462 views)
Permalink
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
>> copied the ebuild a while back to a local overlay to make sure I don't
>> lose it.  It seems emerge gives my local overlay priority over the one
>> in the tree.  I renamed the ebuild in my overlay with .old tacked on. 
>> It emerges fine after that since it uses the ebuild in the tree.  It
>> seems my overlay is broken somehow.  Likely a design improvement.  ;-) 
> That's the default by design. If you copy an ebuild to your overlay, it's
> usually because you want to make changes to it, so it should be given
> priority. You can change the priority of overlays in
> /etc/portage/repos.conf, or you can simply mask the overlay version.
>
>

Found the needed info on the wiki and added the priority setting.  I
added "priority=100" which should work right?  It will use the Gentoo
tree first and then mine?  That's my reading of the wiki page anyway. 

Thanks.

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 9:26 AM
Post #16 of 21 (462 views)
Permalink
Arve Barsnes wrote:
> On Fri, 21 Apr 2023 at 11:55, Dale <rdalek1967@gmail.com> 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 slipped my mind?
> I don't think the files/ directory contents were ever downloaded by
> the ebuilds, they are a part of the portage tree, so they appear when
> you sync. Maybe the files/ contents from the main tree were available
> for your overlay ebuild somehow? I've never had that luxury, so now
> I*m wondering how your ebuild ever worked :-)
>
> Regards,
> Arve
>
>

That's right.  I rarely do anything with local overlays so I forgot
about that.  Next time I'll try to remember to copy the whole directory,
without deleting files no longer in the tree tho.  Don't want to remove
one I need.  ;-)

Thanks.

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 9:29 AM
Post #17 of 21 (462 views)
Permalink
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 normal Gentoo tree. So why use
> your personal repo? Do you have a local patch applied?
>
> Sincerely,
> Rainer
> .
>

I ran into a buggy driver a while back and once I synced and upgraded,
the old one was gone.  So, I started keeping a local copy just in case. 
Of course, as long as I keep a older driver to fall back on, it won't
break anymore.  As soon as I miss one tho, problems.  LOL 

Thanks to you and Ionen.

Dale

:-)  :-) 
Re: Nvidia-drivers fails to patch [ In reply to ]
neil at digimed
Apr 21, 2023, 11:47 AM
Post #18 of 21 (461 views)
Permalink
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. 
> > Not really, AFAIR. You just enable nouveau drivers in your kernel
> > config, uninstall the nvidia package and reboot. This assumes you
> > haven't got any direct references to the nvisia driver in
> > /etc/xorg.conf*.

> I think, pretty much certain, I have it set to nvidia in xorg.conf. 
> This is a old install.  If I recall correctly, I have to change that. 
> Also, I'd need to edit make.conf I think.  I read the wiki thingy a few
> times.  It's mostly undoing things but with the age of this install, I
> don't think my old way is the new way.  Yep.  I'm getting better at
> grep.  lol
>
> root@fireball / # cat /etc/X11/xorg.conf | grep driver
>     Driver         "mouse"
>     Driver         "kbd"
>     Driver         "nvidia"

xorg.conf is often unnecessary these days. I only have a file in
xorg.conf.d to switch the buttons on my trackball.

> root@fireball / #cat /etc/make.conf | grep video_cards
> VIDEO_CARDS="nvidia vesa"
> root@fireball / #
>
> I think I'd have to change those.  It may or may not rebuild some
> packages.  Would I need to leave out vesa or OK to leave it in?

You'll need to replace nvidia with nouveau here, leave in vesa as a
fallback.

The worst that can happen is that X fails to start and you need to
re-emerge the nvidia drivers, which you quickpkg'd of course.


--
Neil Bothwick

This is as bad as it can get; but don't bet on it.
Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 21, 2023, 12:14 PM
Post #19 of 21 (461 views)
Permalink
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
>>>> looks like a big deal. 
>>> Not really, AFAIR. You just enable nouveau drivers in your kernel
>>> config, uninstall the nvidia package and reboot. This assumes you
>>> haven't got any direct references to the nvisia driver in
>>> /etc/xorg.conf*.
>> I think, pretty much certain, I have it set to nvidia in xorg.conf. 
>> This is a old install.  If I recall correctly, I have to change that. 
>> Also, I'd need to edit make.conf I think.  I read the wiki thingy a few
>> times.  It's mostly undoing things but with the age of this install, I
>> don't think my old way is the new way.  Yep.  I'm getting better at
>> grep.  lol
>>
>> root@fireball / # cat /etc/X11/xorg.conf | grep driver
>>     Driver         "mouse"
>>     Driver         "kbd"
>>     Driver         "nvidia"
> xorg.conf is often unnecessary these days. I only have a file in
> xorg.conf.d to switch the buttons on my trackball.

I thought I read that somewhere.  This is a old install tho.  A decade
or so.  To be honest tho, I'd like to configure my 2nd screen in the
conf file.  As it is, I have it set up within KDE itself I think.  When
I kill the X part, the 2nd screen dies since KDE and friends isn't
running.  I just haven't had the nerve to do it yet.  I can't even be
sure how it is done nowadays.  I think nvidia has a command that does it. 


>> root@fireball / #cat /etc/make.conf | grep video_cards
>> VIDEO_CARDS="nvidia vesa"
>> root@fireball / #
>>
>> I think I'd have to change those.  It may or may not rebuild some
>> packages.  Would I need to leave out vesa or OK to leave it in?
> You'll need to replace nvidia with nouveau here, leave in vesa as a
> fallback.
>
> The worst that can happen is that X fails to start and you need to
> re-emerge the nvidia drivers, which you quickpkg'd of course.
>
>


Back when I was using Mandrake, I actually wrote a step by step guide to
installing the video drivers and did it a way that even a noobie could
follow it.  That was back in the mid 2000's tho.  It was on Linux
Questions I think.  That thing had tons of views and lots of grateful
users.  I thought I had to change that and the one in the xorg.conf file
too.  The big one when rebooting is the xorg file tho.  I just wasn't
sure if something had changed. 

I looked at a Nvidia GTX 1050 video card.  May be good for starting to
accumulate parts for new rig.  Anyway, it has a weird set of outputs.  I
need two HDMI, or three, for mine.  My current monitor will take either
DB15HD or HDMI.  My TV ports are HDMI.  I kinda like everything else
about it except the outputs.  I may have to dig further. 

Dale

:-)  :-)
Re: Nvidia-drivers fails to patch [ In reply to ]
realnc at gmail
Apr 22, 2023, 2:32 AM
Post #20 of 21 (461 views)
Permalink
On 21/04/2023 19:29, Dale wrote:
> I ran into a buggy driver a while back and once I synced and upgraded,
> the old one was gone.  So, I started keeping a local copy just in case.
> Of course, as long as I keep a older driver to fall back on, it won't
> break anymore.
It will break with kernel and x.org upgrades. NVidia still updates the
legacy drivers from time to time to support new kernel and x.org versions.
Re: Re: Nvidia-drivers fails to patch [ In reply to ]
rdalek1967 at gmail
Apr 22, 2023, 7:38 AM
Post #21 of 21 (461 views)
Permalink
Nikos Chantziaras wrote:
> On 21/04/2023 19:29, Dale wrote:
>> I ran into a buggy driver a while back and once I synced and upgraded,
>> the old one was gone.  So, I started keeping a local copy just in case.
>> Of course, as long as I keep a older driver to fall back on, it won't
>> break anymore.
> It will break with kernel and x.org upgrades. NVidia still updates the
> legacy drivers from time to time to support new kernel and x.org
> versions.
>
>
>


I don't update kernels that often.  Other than nvidia updating, I don't
have to reinstall them very often.  Maybe I'm lucky on this one??? 
Still, that buggy driver caused me some grief.  I like to have at least
one option available.  Just going back a version is usually enough,
since it worked before.  ;-)

Dale

:-)  :-) 

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal