On Sat, 2023-07-01 at 11:32 +1000, Stephen Morris wrote:
> Does this mean that these drivers are replaced and accessed on the fly
> but the associated kernel modules do not become active until after a reboot?
That's generally the case. Various library updates can only be used
after ones in memor
On 28/6/23 20:33, francis.montag...@inria.fr wrote:
Hi.
On Wed, 28 Jun 2023 18:45:51 +1000 Stephen Morris wrote:
On 26/6/23 20:17, Barry wrote:
Maybe there is user mode code that was upgraded that caused the issue?
Thanks Barry, that could have been the case but I'm not aware of any
compon
Hi.
On Wed, 28 Jun 2023 18:45:51 +1000 Stephen Morris wrote:
> On 26/6/23 20:17, Barry wrote:
>> Maybe there is user mode code that was upgraded that caused the issue?
> Thanks Barry, that could have been the case but I'm not aware of any
> component like that, but that doesn't mean there isn'
On 26/6/23 20:17, Barry wrote:
On 26 Jun 2023, at 09:08, Stephen Morris wrote:
I was just expecting the kmod/akmod nvidia drivers the system was using when I
did the upgrade would still be being used until I rebooted, but that seemed to
not be the case.
The upgrade does not do anything to
> On 26 Jun 2023, at 09:08, Stephen Morris wrote:
>
> I was just expecting the kmod/akmod nvidia drivers the system was using when
> I did the upgrade would still be being used until I rebooted, but that seemed
> to not be the case.
The upgrade does not do anything to the already loaded kern
On 26/6/23 03:47, Barry Scott wrote:
On 25/06/2023 13:20, George N. White III wrote:
You should check the version of the nvidea drivers you are currently
using.
If you don't want to wait 5 minutes there are ways to determine that
the installation
has finished, e.g, using journalctl.
The way
On 25/06/2023 13:20, George N. White III wrote:
You should check the version of the nvidea drivers you are currently
using.
If you don't want to wait 5 minutes there are ways to determine that
the installation
has finished, e.g, using journalctl.
The way I use to figure out its safe to reboo
On Sun, Jun 25, 2023 at 5:43 AM Stephen Morris
wrote:
> Hi,
> When we issue the command "sudo dnf upgrade" and it updates the
> nvidia drivers, does the update of those drivers remove them from memory
> and load the nouveau drivers?
>
Nvidia updates can be messy. Did you reboot after the
Hi.
On Sun, 25 Jun 2023 18:43:27 +1000 Stephen Morris wrote:
> When we issue the command "sudo dnf upgrade" and it updates the
> nvidia drivers, does the update of those drivers remove them from memory
> and load the nouveau drivers?
The kernel drivers no. They are most probably in use, f
> On 25 Nov 2022, at 15:25, Josh Roberts wrote:
>
> I am also facing this issue. Will it work with my Video card?
> https://www.allhdd.com/nvidia-fx5200-videdo-card/
Try it and see. Please let us know here the result.
Barry
> ___
> users mailing l
I am also facing this issue. Will it work with my Video card?
https://www.allhdd.com/nvidia-fx5200-videdo-card/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Cond
On 15/05/2022 15:21, Barry wrote:
On 14 May 2022, at 09:15, Barry Scott wrote:
I have been using the nvidia driver from rpmfusion on f35 without problem.
Just upgraded to F36 and its using nouveau.
There is a nvidia-fallback service that ran and did the modprobe nouveau.
(Nice that this i
> On 14 May 2022, at 09:15, Barry Scott wrote:
>
> I have been using the nvidia driver from rpmfusion on f35 without problem.
>
> Just upgraded to F36 and its using nouveau.
>
> There is a nvidia-fallback service that ran and did the modprobe nouveau.
> (Nice that this is here as a fallback)
On 5/14/22 23:39, Joe Zeff wrote:
On 5/15/22 00:17, Samuel Sieb wrote:
The akmod still has to compile against the current kernel. If the
module source isn't compatible with the new kernel, the compile will
fail.
If the akmod won't work against the newest kernel, that will be fixed
before
On 5/15/22 00:17, Samuel Sieb wrote:
The akmod still has to compile against the current kernel. If the
module source isn't compatible with the new kernel, the compile will fail.
If the akmod won't work against the newest kernel, that will be fixed
before the kernel is released, because that
On 5/14/22 22:05, Joe Zeff wrote:
On 5/14/22 22:08, Samuel Sieb wrote:
Maybe the new kernel isn't supported yet.
That's only a problem with the kmod, and it's the reason for the akmond.
The akmod still has to compile against the current kernel. If the
module source isn't compatible with t
On 5/14/22 22:08, Samuel Sieb wrote:
Maybe the new kernel isn't supported yet.
That's only a problem with the kmod, and it's the reason for the akmond.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le..
On 5/14/22 01:15, Barry Scott wrote:
I have been using the nvidia driver from rpmfusion on f35 without problem.
Just upgraded to F36 and its using nouveau.
There is a nvidia-fallback service that ran and did the modprobe nouveau.
(Nice that this is here as a fallback)
Anyone know why the rpmfu
On 11/21/19 9:36 PM, Tom Horsley wrote:
> I turn my display port connected monitor off over night
> and when I turn it back on in the morning, I get no
> video (no valid video anyway). This used to happen a while
> back, then it stopped, now it is happening again.
>
> I find this nonsense in the Xo
On 8 June 2015 at 18:45, François Patte:
>
> I think that it was the problem... Now it works, but yum installed also
> kmod-nvidia, which seems to me as something useless if akmod is supposed
> to compile the module on the fly if it is missing or if a new kernel is
> installed...
>
> BTW why kernem
Le 05/06/2015 17:56, Joachim Backes a écrit :
> On 06/05/2015 04:22 PM, Peter Thermometer wrote:
>>> I tried to install akmod-nvidia-304xx in order to have the nvidia driver
>>> compiled, but, nothing happens! driver is not compiled neither at the
>>> install of akmod-nvidia-304xx nor when I reboot
On 06/05/2015 04:22 PM, Peter Thermometer wrote:
>> I tried to install akmod-nvidia-304xx in order to have the nvidia driver
>> compiled, but, nothing happens! driver is not compiled neither at the
>> install of akmod-nvidia-304xx nor when I reboot the system...
>>
>> Yes, gcc etc. are installed, y
> I tried to install akmod-nvidia-304xx in order to have the nvidia driver
> compiled, but, nothing happens! driver is not compiled neither at the
> install of akmod-nvidia-304xx nor when I reboot the system...
>
> Yes, gcc etc. are installed, yes kernel-headers are installed...
kernel-devel also
Does it produce any logs? I once had a problem with a similar package,
turned out make was not installed.
John
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 04/06/2015 20:01, Kevin Cummings a écrit :
> On 06/04/2015 11:30 AM, François Patte wrote:
>> Bonjour,
>>
>>
>> I tried to install akmod-nvidia-304xx in order to have the nvidia
>> driver compiled, but, nothing happens! driver is not compiled
>> n
On 06/04/2015 11:30 AM, François Patte wrote:
> Bonjour,
>
>
> I tried to install akmod-nvidia-304xx in order to have the nvidia driver
> compiled, but, nothing happens! driver is not compiled neither at the
> install of akmod-nvidia-304xx nor when I reboot the system...
>
> Yes, gcc etc. are in
On Thu, 08 Jan 2015 09:54:44 -0600
Michael Cronenworth wrote:
> Based on your e-mail I don't have enough information to know what the problem
> is, but I recommend posting your Xorg.log, dmesg log, list of RPMs you've
> installed, etc. and posting that to the RPMFusion list
OK, I gathered lots
On 01/08/2015 06:55 AM, Tom Horsley wrote:
[snip]
Is this stuff supposed to be working with maxwell cards?
Is something not configured right? Is there something
a ordinary mortal can do to fix this (most of this
graphics system stuff is complete gibberish to me:-).
You need to fix the installat
On Wed, Apr 09, 2014 at 03:23:29PM +0200, Rafnews wrote:
> Hi,
>
> after i followed the tutorial from
> http://www.if-not-true-then-false.com/2014/fedora-20-nvidia-guide/
> about installing nVidia driver for my ASUS G73SW laptop (with a
> GTX460M nvidia card), i'm getting blocked at boot time of f
On 9 April 2014 15:23, Rafnews wrote:
> Hi,
>
> after i followed the tutorial from
> http://www.if-not-true-then-false.com/2014/fedora-20-nvidia-guide/ about
> installing nVidia driver for my ASUS G73SW laptop (with a GTX460M nvidia
> card), i'm getting blocked at boot time of fedora 20.
> i used
On 04/09/2014 07:40 AM, Rafnews wrote:
On 09.04.2014 16:32, Joe Zeff wrote:
On 04/09/2014 07:28 AM, Rafnews wrote:
But the problem happened just after following this tutorial how to
install nvidia drivers...
so problem comes from a step there, as for 2 weeks everything worked
well.
Just beca
On 09.04.2014 16:32, Joe Zeff wrote:
On 04/09/2014 07:28 AM, Rafnews wrote:
But the problem happened just after following this tutorial how to
install nvidia drivers...
so problem comes from a step there, as for 2 weeks everything worked
well.
Just because things broke shortly after you inst
On 04/09/2014 07:28 AM, Rafnews wrote:
But the problem happened just after following this tutorial how to
install nvidia drivers...
so problem comes from a step there, as for 2 weeks everything worked well.
Just because things broke shortly after you installed the drivers
doesn't mean they're
On 09.04.2014 16:22, Joe Zeff wrote:
On 04/09/2014 06:23 AM, Rafnews wrote:
and now when it loads Fedora, it stops at different steps:
1. Starting Network Manager Script Dispatcher Service
or
2. Started Hostname Service
or
3. ASAHI mDNS/DNS-SD Stack
Unless there's a reason that any of these
On 04/09/2014 06:23 AM, Rafnews wrote:
and now when it loads Fedora, it stops at different steps:
1. Starting Network Manager Script Dispatcher Service
or
2. Started Hostname Service
or
3. ASAHI mDNS/DNS-SD Stack
Unless there's a reason that any of these services depend on your video
driver, t
On Tue, 2013-11-05 at 22:51 +, Matthew Saltzman wrote:
> https://urldefense.proofpoint.com/v1/url?u=http://bumblebee-project.org/&k=dsHy%2FVymniCD0osh6tze%2Fw%3D%3D%0A&r=6lbkzZQmkGgL7ITxCWNsIJwNXCdRDnxsPepTVOzWl24%3D%0A&m=3Qq%2B1AAJhQnjOt2h7xWd%2BDcnmbrne%2FqGqK2MjngD%2BG8%3D%0A&s=a2ea19ae2ab3
It's actually a dual cards(intel+nvidia) problem.
I know there are supports for optimus in newest kernel/xorg/nvidia .
According to http://nouveau.freedesktop.org/wiki/Optimus/, new kernel supports
seamless switch between intel graphics driver and nouveau.
About nvidia
http://us.download.nvidia.
On Tue, 2013-11-05 at 21:08 +0800, WangWentao wrote:
> I have tried the repos version, but it doesn't work either.
>
> There is also an intel card along with nvidia card, so it supports optimus,
> but I can't disable it in BIOS.
>
Just FYI, there is a pilot project to support Optimus here:
htt
I have tried the repos version, but it doesn't work either.
There is also an intel card along with nvidia card, so it supports optimus, but
I can't disable it in BIOS.
I have tried a few methods:
* specify BusID in xorg.conf
* remove nouveau module(blacklist+dracut)
* increase vmalloc
On 11/04/2013 11:33 AM, WangWentao wrote:
However, I failed to install nvidia driver. After I installed
NVIDIA-Linux-x86-319.60.run(no error), the X cannot be started until I restore
open source driver.
Using the binary blob from nVidia is probably the worst way to go. Not
only does it mang
On Sat, 2011-11-26 at 06:47 -0700, Lawrence Graves wrote:
> Forgot to say that I have a
Who what where??? You've posted a NEW message that's totally
disconnected from whatever previous thread you're adding to, so it's
"lost information."
If you want to add information to some previous message,
I don't have any desktop effects enabled that I know of. It might not be
so easy for KDE users to solve this problem.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedor
How did you arrive at this kill list ?
killall -9 compiz;killall -9 gtk-window-decorator;metacity --replace&
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.o
On Thu, 2011-08-25 at 07:53 -0500, Richard Shaw wrote:
> On Thu, Aug 25, 2011 at 5:49 AM, Arthur Dent
> wrote:
>
> First, it would be more appropriate to send this to the RPM Fusion
> mailing list[1] since it appears to be a problem with a package that
> comes from there.
OK Thanks - I'll try th
On Thu, Aug 25, 2011 at 5:49 AM, Arthur Dent
wrote:
First, it would be more appropriate to send this to the RPM Fusion
mailing list[1] since it appears to be a problem with a package that
comes from there.
> The only difference between my account and the other user's account is
> that I have des
On Tue, 2010-07-06 at 17:35 -0400, Mauriat Miranda wrote:
> On Tue, Jul 6, 2010 at 1:36 PM, Gerhard Magnus wrote:
> Sadly the proprietary nvidia driver is a mess.
>
> The best answer to all your questions is: Try and see. If you don't
> have problems then you're fine.
>
> > QUESTION: Google te
> The rpmfusion.org/Howto/nVidia instructions also say that SElinux
> protection should be lowered:
> setsebool -P allow_execstack on
I spent quite a bit of time fighting with this over the weekend and
found that the only thing that worked was lowering or disabling selinux,
and then only the km
On Tue, Jul 6, 2010 at 1:36 PM, Gerhard Magnus wrote:
>
Sadly the proprietary nvidia driver is a mess.
The best answer to all your questions is: Try and see. If you don't
have problems then you're fine.
> QUESTION: Google tells me that specifying "nomodeset" basically tells
> the system to use
On Fri, 2010-06-11 at 13:31 +0100, Chris Ross wrote:
> On 06/07/2010 06:12 PM, Matthew Saltzman wrote:
> > When I start up, the nvidia initscript fails with a segfault.
>
>
> I am seeing exactly the same issue on a brand new, clean install of
> Fedora 13 on a desktop machine. The result is that
On 06/07/2010 06:12 PM, Matthew Saltzman wrote:
> When I start up, the nvidia initscript fails with a segfault.
I am seeing exactly the same issue on a brand new, clean install of
Fedora 13 on a desktop machine. The result is that X won't start and the
machine is essentially unusable.
The onl
On Sun, Mar 14, 2010 at 03:04, Amiga5 wrote:
>
>
> I am just glad I did not have to wipe 4 tbit of drive because of a
> kernel update like the switch from 2.6.31 to 2.6.32
>
>
Why couldn't you boot with the older kernel?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or chan
On 01/-10/-28163 11:59 AM, john wendel wrote:
>
> I incorrectly said that the Nvidia 195 driver has a fan control bug.
>
> The bug is in the 196 driver. Sorry for the bad info.
>
> Regards,
>
> John
>
>
No problem but I sure would like to get 195 back in as the cuda 3 solved
quite a few problems b
On 01/-10/-28163 11:59 AM, john wendel wrote:
> On 03/13/2010 10:29 AM, Amiga5 wrote:
>> The latest kernel upodate reduced my Nvidia 195 driver with cuda 3 down
>> to 190.53 with cuda 2.3
>>
>> I have tried to update the driver through Fedora and RPMFusion and it
>> does not even give me the option
I incorrectly said that the Nvidia 195 driver has a fan control bug.
The bug is in the 196 driver. Sorry for the bad info.
Regards,
John
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Gu
On 03/13/2010 10:29 AM, Amiga5 wrote:
> The latest kernel upodate reduced my Nvidia 195 driver with cuda 3 down
> to 190.53 with cuda 2.3
>
> I have tried to update the driver through Fedora and RPMFusion and it
> does not even give me the option to reinstall 195 series drivers at all
>
> It still
55 matches
Mail list logo
