o figure out that you needed to add another repo, and how to do
it.
NVidia was notorious for stomping over system files, hence the RPM
Fusion packages rather than getting binary blobs directly from NVidia.
They were also notorious for dropping support on older hardware,
whereas open-source things
On Wed, 2025-05-07 at 00:20 -0400, Jon LaBadie wrote:
> An AMD user does "dnf update". I do "dnf update". Neither of us need
> to do anything further. At least, not being an AMD user, I assume they
> need not do anything more. I certainly don't.
Correct.
;> as possible. I ended up with the Geforce GTX 1660 Super.
>>
>
>Did you have any particular reason for choosing Nvidia again?
>Why not AMD, which is supported without the hassle of drivers?
>
Really, AMD doesn't use drivers for its cards :-))
I didn't say AMD was
t; as possible. I ended up with the Geforce GTX 1660 Super.
> >>
> >
> >Did you have any particular reason for choosing Nvidia again?
> >Why not AMD, which is supported without the hassle of drivers?
> >
> Really, AMD doesn't use drivers for its c
my 660 card was acting up, forget how.
I decided to replace it with something newer but as similar
as possible. I ended up with the Geforce GTX 1660 Super.
Did you have any particular reason for choosing Nvidia again?
Why not AMD, which is supported without the hassle of drivers?
Really, AMD doe
derate problems
> >with f40 (which did have the current, correct RPM Fusion driver). I
> >figure a little better than 50% chance the card was bad, almost 50%
> >chance my problems were because the RPM Fusion nvidia driver was not yet
> >re-installed, and a slim chance the c
was bad, almost 50%
chance my problems were because the RPM Fusion nvidia driver was not yet
re-installed, and a slim chance the card needed re-seating.
A year or 2 ago my 660 card was acting up, forget how.
I decided to replace it with something newer but as similar
as possible. I ended up with
ut no RPM Fusion driver with that), and moderate problems
with f40 (which did have the current, correct RPM Fusion driver). I
figure a little better than 50% chance the card was bad, almost 50%
chance my problems were because the RPM Fusion nvidia driver was not yet
re-installed, and a slim c
On Sun, 2025-04-27 at 21:37 -0600, home user via users wrote:
> Removing the card worked. That's evidence, an argument, not proof,
> that the card was bad.
Did you also try putting it back in again?
Back in my early days of fixing up people's PCs, reseating cards was
often needed. Few cases wer
home user composed on 2025-04-27 21:28 (UTC-0600):
> Felix Miata wrote:
>> home user composed on 2025-04-26 16:01 (UTC-0600):
>>> The workstation rebooted fine without the card. No problems so far. So
>>> the CPU does have integrated graphics, which answers Felix and Samuel.
>>> There is one c
yesterday afternoon. It's practically unusable. I'm now
on a windows-10 box (separate hardware, no dual boot).
In my "securing..." thread, Samuel said:
"...Anaconda won't install the proprietary NVidia drivers, so you must
be using nouveau. If it works, then great. If yo
On 4/26/25 5:10 PM, Felix Miata wrote:
home user composed on 2025-04-26 16:01 (UTC-0600):
The workstation rebooted fine without the card. No problems so far. So
the CPU does have integrated graphics, which answers Felix and Samuel.
There is one cost: this was a 2-monitor workstation; now it's
home user composed on 2025-04-26 16:01 (UTC-0600):
> The workstation rebooted fine without the card. No problems so far. So
> the CPU does have integrated graphics, which answers Felix and Samuel.
> There is one cost: this was a 2-monitor workstation; now it's only one.
Why is that? Most comp
sable. I'm now on a windows-10
box (separate hardware, no dual boot).
In my "securing..." thread, Samuel said:
"...Anaconda won't install the proprietary NVidia drivers, so you must
be using nouveau. If it works, then great. If you have issues, you
might want to inst
GPU, removing the GTX may buy you some time before complete PSU
>> breakdown.
>> If the problem actually is the GTX, then removal should constitute a
>> complete fix.
>> Without NVidia proprietary drivers installed, an AMD or Intel iGPU 12 years
>> old
>> shoul
sable. I'm now on a windows-10
box (separate hardware, no dual boot).
In my "securing..." thread, Samuel said:
"...Anaconda won't install the proprietary NVidia drivers, so you must
be using nouveau. If it works, then great. If you have issues, you
might want to inst
afternoon. It's practically unusable. I'm now on a windows-10
box (separate hardware, no dual boot).
...
I do not game.
The most graphics-intense thing that I do (as far as I know) is watch
youtube videos with a resolution of about 1.4k.
So I'm wondering...
Suppose I remove the graphi
lly unusable. I'm now on a windows-10
> box (separate hardware, no dual boot).
...
> I do not game.
> The most graphics-intense thing that I do (as far as I know) is watch
> youtube videos with a resolution of about 1.4k.
> So I'm wondering...
> Suppose I remove the gr
On 4/26/2025 10:45 AM, Jeffrey Walton wrote:
On Sat, Apr 26, 2025 at 12:23 PM home user via users
wrote:
Before starting this experiment, the top 3 things that were crashing
were Thunderbird, Firefox, and gnome; there were other things. Some
crashes took me back to the graphical login scre
> yesterday afternoon. It's practically unusable. I'm now on a windows-10
> box (separate hardware, no dual boot).
>
> In my "securing..." thread, Samuel said:
> "...Anaconda won't install the proprietary NVidia drivers, so you must
> be using nouvea
e hardware, no dual boot).
In my "securing..." thread, Samuel said:
"...Anaconda won't install the proprietary NVidia drivers, so you must
be using nouveau. If it works, then great. If you have issues, you
might want to install the drivers from rpmfusion."
I don&#
On Thu, 2025-02-06 at 10:53 -0500, Bill Oliver via users wrote:
> So, I installed
> akmod-nvidia from rpmfusion. All the screen issues cleared up, but I
> lost wireless networking. There's no wireless device, it seems.
What does 'sudo
On Thu, Feb 6, 2025 at 11:54 AM Bill Oliver via users
wrote:
>
>
> I have an ASUS ROG Strix laptop running Fedora 41, KDE spin. It was working
> OK, though there were some screen issues. So, I installed akmod-nvidia from
> rpmfusion. All the screen issues cleared up, but
I have an ASUS ROG Strix laptop running Fedora 41, KDE spin. It was
working OK, though there were some screen issues. So, I installed
akmod-nvidia from rpmfusion. All the screen issues cleared up, but I
lost wireless networking. There's no wireless device, it seems. The
networking w
The computer seems to be awaken but the screen remains black.
kernel: 6.11.11-200.fc40.x86_64
driver: 560.35.03
cuda: 12.6
I no longer have an Nvidia card, but is this the proprietary driver or
the free one?
driver from rpm-fusion
Maybe post the output of 'inxi -G'.
Graphics:
6_64
> driver: 560.35.03
> cuda: 12.6
I no longer have an Nvidia card, but is this the proprietary driver or
the free one? Maybe post the output of 'inxi -G'.
You might also look at the journal for the time you try to resume.
poc
--
Bonjour,
Since I installed f40 on my computer, it is impossible to suspend: the
screen does not resume and stay black...
kernel: 6.11.11-200.fc40.x86_64
driver: 560.35.03
cuda: 12.6
Is there a fix?
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR
On 2024-11-20 09:16, lejeczek via users wrote:
Older GPUs, eg. GTX 16xx, with playing games in mind - will what's in
Fedora repo's/kernels do or should Nvidia's driver/software be installed?
Try it and see if it works. If it doesn't, then you'll need to install
the driver package from rpmfusi
e Nvidia's site to determine the status of your card on linux and the
current version of the Nvidia driver.
Fedora can't (ask the lawyers) package Nvidia drivers, so you have to
install them from the rpmfusion site
(there are other sites that package Nvidia drivers, but most users should
Hi guys.
Older GPUs, eg. GTX 16xx, with playing games in mind - will
what's in Fedora repo's/kernels do or should Nvidia's
driver/software be installed?
thanks, L.--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an ema
be
installed
- package cuda-runtime-12-6-12.6.2-1.x86_64 from cuda-fedora39
requires nvidia-open-560 >= 560.35.03, but none of the providers can
be installed
- package cuda-12.6.2-1.x86_64 from cuda-fedora39 requires cuda-12-6
>= 12.6.2, but none of the providers can be installed
- packa
2.6.2, but none of the providers can be
> installed
> - package cuda-runtime-12-6-12.6.2-1.x86_64 from cuda-fedora39
> requires nvidia-open-560 >= 560.35.03, but none of the providers can
> be installed
...
> - package nvidia-open-560-3:560.35.03-1.noarch from cuda-fedora39
the providers can be
installed
- package cuda-runtime-12-6-12.6.2-1.x86_64 from cuda-fedora39
requires nvidia-open-560 >= 560.35.03, but none of the providers can
be installed
- package cuda-12.6.2-1.x86_64 from cuda-fedora39 requires cuda-12-6
>= 12.6.2, but none of the providers can be
Hi.
On Mon, 04 Nov 2024 13:26:55 + Paul Smith wrote:
> I am getting the below issues. Could you please help me?
> # dnf update
> Updating and loading repositories:
> Repositories loaded.
> Problem: package cuda-runtime-12-6-12.6.2-1.x86_64 from cuda-fedora39
> requir
Dear All,
I am getting the below issues. Could you please help me?
Thanks in advance,
Paul
--
# dnf update
Updating and loading repositories:
Repositories loaded.
Problem: package cuda-runtime-12-6-12.6.2-1.x86_64 from cuda-fedora39
requires nvidia-open
morning, I wanted to do my weekly patches (dnf upgrade). I saw that dnf wanted
up upgrade the kernel to 6.11.3, but I did not see it wanting to bring in a newer version
of the rpmfusion nvidia driver. This looks like the sort of thing that caused me real
problems multiple times in the past. So I
On 20/10/24 23:09, Barry wrote:
On 20 Oct 2024, at 11:07, Stephen Morris wrote:
The nvidia driver for kernel 6.10.12 has stopped working again as the signing
keys for some reason have been knocked out again,
Wild guess. Do you need to replace the motherboard battery?
Is your nvram losing
> On 20 Oct 2024, at 11:07, Stephen Morris wrote:
>
> The nvidia driver for kernel 6.10.12 has stopped working again as the signing
> keys for some reason have been knocked out again,
Wild guess. Do you need to replace the motherboard battery?
Is your nvram losing its content m
On Oct 19, 2024, at 20:52, Bob Marčan via users
wrote:
> A kind of windows registry and systemd are a good example of this.
> And don't apologize systemd for how much the boot time has shortened.
> How often does the system need start or restart?
> Not to mention that it looks like systemd will r
On Sat, 19 Oct 2024 17:25:06 -0600
"home user via users" wrote:
> On 10/19/24 2:07 PM, Bob Marčan via users wrote:
> > With all these problems with Nvidia, the best thing to do would be to
> > reject all the hardware it uses if possible.
> > The first conditi
On 10/19/24 2:07 PM, Bob Marčan via users wrote:
With all these problems with Nvidia, the best thing to do would be to reject
all the hardware it uses if possible.
The first condition for my purchases is that the equipment has nothing from
this ignorant company.
BR
yeah, I hoping that
!
That's good to know. Please will you post the boot command line shown by
sudo dmesg | grep -i boot
on your dual-boot system running the new f40 kernel and the nvidia 470xx
driver ?
Thanks,
John P
-bash.1[~]: dmesg | grep -i boot
[0.00] Command line:
BOOT_IMAGE=(hd0,m
post the boot command line shown by
sudo dmesg | grep -i boot
on your dual-boot system running the new f40 kernel and the nvidia
470xx driver ?
Thanks,
John P
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an ema
With all these problems with Nvidia, the best thing to do would be to reject
all the hardware it uses if possible.
The first condition for my purchases is that the equipment has nothing from
this ignorant company.
BR
--
___
users mailing list
morning, I wanted to do my weekly patches (dnf upgrade). I saw that dnf wanted
up upgrade the kernel to 6.11.3, but I did not see it wanting to bring in a newer version
of the rpmfusion nvidia driver. This looks like the sort of thing that caused me real
problems multiple times in the past. So I
On 19/10/2024 01:10, home user via users wrote:
On 10/18/24 4:37 PM, John Pilkington wrote:
On 18/10/2024 22:55, home user via users wrote:
(f40; gnome; standalone workstation)
I have not been able to figure out how the rpmfusion nvidia version
numbers relate to the kernel version numbers
On Fri, Oct 18, 2024 at 9:10 PM home user via users <
users@lists.fedoraproject.org> wrote:
> On 10/18/24 4:37 PM, John Pilkington wrote:
>
[...]
>
> On 18/10/2024 22:55, home user via users wrote:
> >> I do NOT want to be running with nouveau!
>
I have an old
GNU/Linux
-bash.3[~]:
- - - - - -
Yesterday morning, I wanted to do my weekly patches (dnf upgrade). I saw that dnf wanted
up upgrade the kernel to 6.11.3, but I did not see it wanting to bring in a newer version
of the rpmfusion nvidia driver. This looks like the sort of thing that caused me real
morning, I wanted to do my weekly patches (dnf upgrade). I
saw that dnf wanted up upgrade the kernel to 6.11.3, but I did not see
it wanting to bring in a newer version of the rpmfusion nvidia driver.
This looks like the sort of thing that caused me real problems multiple
times in the past. So
upgrade). I saw that dnf wanted
up upgrade the kernel to 6.11.3, but I did not see it wanting to bring in a newer version
of the rpmfusion nvidia driver. This looks like the sort of thing that caused me real
problems multiple times in the past. So I "declined" the upgrade. I tried
a
> On 16 Oct 2024, at 13:01, Stephen Morris wrote:
>
> The question now is what in the updates did this and why? Why is F40 causing
> issue with secure boot, the offending update caused a problem and the system
> upgrade from F39 to F40 caused the same issues, although with the F40 upgrade
>
On 16/10/24 20:54, Barry Scott wrote:
On 16 Oct 2024, at 09:55, Stephen Morris via users
wrote:
I issued the command modinfo kmod-nvidia-6.10.12-200.fc40.x86_64 but
that says it can't find that module, so how do I issue that command
against the nvidia driver?
modinfo works on k
> On 16 Oct 2024, at 09:55, Stephen Morris via users
> wrote:
>
> I issued the command modinfo kmod-nvidia-6.10.12-200.fc40.x86_64 but that
> says it can't find that module, so how do I issue that command against the
> nvidia driver?
modinfo works on kernel modules
On 16/10/24 02:01, Barry wrote:
On 15 Oct 2024, at 10:49, Stephen Morris via users
wrote:
How do I check if the nvidia driver is actually signed?
George gave the check.
It maybe that the drive was built before the key was created?
If so you will need to remove built driver, somewhere in
> On 15 Oct 2024, at 10:49, Stephen Morris via users
> wrote:
>
> How do I check if the nvidia driver is actually signed?
George gave the check.
It maybe that the drive was built before the key was created?
If so you will need to remove built driver, somewhere in /var
And te
On Tue, Oct 15, 2024 at 6:49 AM Stephen Morris via users <
users@lists.fedoraproject.org> wrote:
> How do I check if the nvidia driver is actually signed?
>
modinfo should show entries for:
sig_id:
signer:
sig_key:
sig_hashalgo:
signature:
--
George
On 15/10/24 20:49, Stephen Morris via users wrote:
Hi,
I have built the kmod-nvidia modules manually for all 3 kernels I
have installed via akmods, but the startup of KDE or Gnome from SDDM
switches to a black screen and the monitor then switches into sleep
mode with "No Signal Det
Hi,
I have built the kmod-nvidia modules manually for all 3 kernels I
have installed via akmods, but the startup of KDE or Gnome from SDDM
switches to a black screen and the monitor then switches into sleep mode
with "No Signal Detected".
The output from modinfo -F vers
the application
> developer.
> In this case nvidia I assume.
>
I agree. My experience has been that Nvidia provides only the bare minimum
information in error messages -- I assume they worry that error messages
might
reveal the special sauce they are so
> On 7 Sep 2024, at 08:59, François Patte
> wrote:
>
> No more exlanation (as usual with journalctl...)
journalctl does not decide what is logged that is up to the application
developer.
In this case nvidia I assume.
Barry
--
___
u
Le 2024-09-07 08:21, francis.montag...@inria.fr a écrit :
Hi.
On Wed, 04 Sep 2024 16:44:51 +0200 François Patte wrote:
When I suspend my system, it is impossible to resume with the nvidia
module (works with nouveau and was working with f36)
kernel: 6.10.6-200.fc40.x86_64
nvidia
Hi.
On Wed, 04 Sep 2024 16:44:51 +0200 François Patte wrote:
> When I suspend my system, it is impossible to resume with the nvidia
> module (works with nouveau and was working with f36)
> kernel: 6.10.6-200.fc40.x86_64
> nvidia stuff:
> xorg-x11-drv-nvidia-power-560.35.0
Bonjour,
When I suspend my system, it is impossible to resume with the nvidia
module (works with nouveau and was working with f36)
kernel: 6.10.6-200.fc40.x86_64
nvidia stuff:
nvidia-gpu-firmware-20240811-2.fc40.noarch
xorg-x11-drv-nvidia-kmodsrc-560.35.03-3.fc40.x86_64
xorg-x11-drv
On Mon, 2024-07-15 at 10:44 -0700, Samuel Sieb wrote:
> On 7/15/24 9:14 AM, Patrick O'Callaghan wrote:
> > I'm not sure what any of this has to do with installing Nvidia
> > drivers,
> > but then I've never enabled Secure Boot.
>
> If secure boot is enabl
On 7/15/24 4:05 PM, François Patte wrote:
Le 2024-07-14 10:50, François Patte a écrit :
Bonjour,
According to some howto, it is enough to install akmods-nvidia and
reboot. some others tell that we have to generate and install some
signature
I have secure boot enabled.
Is there some how
Le 2024-07-14 10:50, François Patte a écrit :
Bonjour,
According to some howto, it is enough to install akmods-nvidia and
reboot. some others tell that we have to generate and install some
signature
I have secure boot enabled.
Is there some how-to explaining with details how to proceed
On 7/15/24 9:14 AM, Patrick O'Callaghan wrote:
I'm not sure what any of this has to do with installing Nvidia drivers,
but then I've never enabled Secure Boot.
If secure boot is enabled, the kernel can't load unsigned drivers. You
can't sign the drivers with t
gt;
The existing Fedora secure boot configuration may offer some
protection for those
who also boot Windows.
I'm not sure what any of this has to do with installing Nvidia drivers,
but then I've never enabled Secure Boot.
poc
I'm not sure what the current status of your sys
when initread and kernel are separate,
> > and /boot should be encrypted:
> > <https://ruderich.org/simon/notes/secure-boot-with-grub-and-signed-
> > linux-and-initrd>
>
> > The existing Fedora secure boot configuration may offe
On Mon, Jul 15, 2024 at 6:48 AM George N. White III wrote:
>
> On Sun, Jul 14, 2024 at 5:50 AM François Patte
> wrote:
>> [...]
>> I have secure boot enabled.
>>
>> Is there some how-to explaining with details how to proceed. I'm not
>> very good with efi boot system nor secure boot.
>
> You s
On Sun, Jul 14, 2024 at 5:50 AM François Patte <
francois.pa...@mi.parisdescartes.fr> wrote:
> Bonjour,
>
> According to some howto, it is enough to install akmods-nvidia and
> reboot. some others tell that we have to generate and install some
> signature
>
The in
On Jul 14, 2024, at 04:51, François Patte
wrote:
>
> Bonjour,
>
> According to some howto, it is enough to install akmods-nvidia and reboot.
> some others tell that we have to generate and install some signature
>
> I have secure boot enabled.
>
> Is there
Bonjour,
According to some howto, it is enough to install akmods-nvidia and
reboot. some others tell that we have to generate and install some
signature
I have secure boot enabled.
Is there some how-to explaining with details how to proceed. I'm not
very good with efi boot syste
> On 2 May 2024, at 18:11, francis.montag...@inria.fr wrote:
>
> This is a know issue: you rebooted slightly too early, during the
> %post of the kmod-nvidia-KERNEL rpm that does this depmod.
The system-upgrade does the reboot and the user has no way to delay it.
It is, as you
Hi
On Thu, 02 May 2024 13:00:47 -0400 Neal Becker wrote:
> Finally I manually run
> depmod -a
> Then reboot again.
> Now nvidia driver is loaded and nvidia-smi reports success.
> My question is:
> Why did I need to manually run depmod -a?
This is a know issue: you rebooted
Not as bad perhaps as some of your experiences, because I'm using nvidia
GPU for M/L on a remote server and not for desktop display.
After update the nvidia driver is not loaded. Tried rebooting a couple of
times since sometimes akmod seems to need this.
Manually loading the driver
mod
On 4/30/24 2:23 AM, Javier Perez wrote:
What kernel are you using?
The bad patching ("dnf upgrade" early this month) was from
6.7.11-100.fc38x86_64 to 6.8.4-100.fc38x86_64.
The good patching Saturday was from 6.7.11-100.fc38x86_64 to
6.8.7-100.fc38x86_64.
The full upgrade ("dnf system-upgra
What kernel are you using?
On Mon, Apr 29, 2024, 21:15 home user wrote:
> On 4/11/24 11:19 AM, home user wrote:
> > (f-38; stand-alone work station; nvidia graphics card; dual monitor;
> kmod 4xx driver)
> >
> > I just finished doing a "dnf upgrade" as a prere
On 4/11/24 11:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor; kmod 4xx
driver)
I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from
f-38 to f-39.
There were no hints of any problems. The kernel and the graph
Had to have machine with older card keep running the 6.7.11
kernel in order to have a working nvidia driver for BOINC.
The newer ones now work with the 6.8 kernels.
Just to let others know.
++
Michael D. Setzer II - Computer Science
On 15/04/2024 20:02, home user wrote:
On 4/11/24 11:19 AM, home user wrote:
After a few days of being seriously side-tracked, I can try to get back
to this.
Those who explained the kernel numbering: thank-you.
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx
again.
(Todd)
I can tell you that building the 2 or 3 nvidia 470xx packages
works well for the later 6.7 and current 6.8 kernels.
and there's
2.
(John)
AIUI we are moving from X11 graphics towards Wayland, which the nvidia
driver will not support...
(Michael)
So, not sure if this is a ke
On 4/11/24 11:19 AM, home user wrote:
After a few days of being seriously side-tracked, I can try to get back to this.
Those who explained the kernel numbering: thank-you.
(f-38; stand-alone work station; nvidia graphics card; dual monitor; kmod 4xx
driver)
I just finished doing a &quo
On 4/14/24 17:21, Michael D. Setzer II via users wrote:
So, not sure why it works with 6.7.x but not with 6.8.x.
Something changed in the kernel and the NVidia driver needs to be
changed to work with it. The driver is out of tree so it doesn't get
fixed by the people making the change
On 14 Apr 2024 at 18:50, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 18:50:40 +0100
Subject:Re: crippling nvidia display issue.
To: users@lists.fedoraproject.org
From: John Pilkington
Send reply to: Community
On 14/04/2024 16:22, Michael D. Setzer II via users wrote:
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
Just as an additional note. I have an older Acer notebook that has
an NVIDIA GT 650M that had been working fine with the
rpmfusion driver. Have BOINC using its GPU for a
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
To: Community support for Fedora users
Date sent: Mon, 15 Apr 2024 00:29:38 +1000
Subject:Re: crippling nvidia display issue.
Priority: normal
Send reply to: mi
On 14 Apr 2024 at 12:47, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 12:47:57 +0100
Subject:Re: crippling nvidia display issue.
From: John Pilkington
To: users@lists.fedoraproject.org
Send reply to: Community
On 12/04/2024 12:58, John Pilkington wrote:
On 12/04/2024 00:52, home user wrote:
On 4/11/24 5:39 PM, Samuel Sieb wrote:
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02
> On 12 Apr 2024, at 01:06, Tom Horsley wrote:
>
> My system gets regular updates. I've never had a yadda-yadda-100 kernel,
> all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
> kernels in my old fedora 38 partition are also -200, not -100.
The -NNN is the version that is
On 12/04/2024 00:52, home user wrote:
On 4/11/24 5:39 PM, Samuel Sieb wrote:
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
home user composed on 2024-04-11 19:49 (UTC-0600):
> What does the -100 vs. -200 signify?
From observation, not reading any doc:
A fresh Fedora release gets -300, moving the prior release to -200, and the
prior
to prior release to -100. After the prior-prior's support ends, there is only
curren
On 4/11/24 18:49, home user wrote:
On 4/11/24 7:00 PM, Go Canes wrote:
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley
wrote:
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regula
On 4/11/24 7:00 PM, Go Canes wrote:
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley wrote:
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a yadda-ya
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley wrote:
>
> On Thu, 11 Apr 2024 17:52:10 -0600
> home user wrote:
>
> > kmod_build_6.8.4-100.fc38.x86_64
>
> Possibly relevant, but I don't know what it means for sure:
>
> My system gets regular updates. I've never had a yadda-yadda-100 kernel,
> all min
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
> kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a yadda-yadda-100 kernel,
all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
kern
On 4/11/24 5:39 PM, Samuel Sieb wrote:
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
There has been a k
1 - 100 of 1675 matches
Mail list logo
