Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, Jul 14, 2010 at 11:38:38 -0700, Rick Stevens ri...@nerd.com wrote: I can see two possible solutions. One would take the form of yum checking to see if kmods are needed for a new kernel on the system and not downloading the kernel if the kmods aren't available. Simply using dependencies isn't feasible as that would block people who don't need the kmods from using the kernel when it's released. Yum would need to do some snooping on the system to find if kmods are needed or not. I think there is a way to do this reasonably. When kmods are released they should be set to conflict with higher versioned kernels. As long as skip-broken can deal with this, this should allow updating other things until the new kmod is ready. When a new kmod is ready an update is also prepared for the old kmod that removes the conflict. This should allow both the kernel and kmod updates. (Assuming yum doesn't get confused by the conflict from the old installed kmod.) If there are yum problems with this scheme, they are probably fixable. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/18/2010 11:14 AM, Bruno Wolff III wrote: akmod solves all these problems - why are we trying to find additional and more complicated solutions ? It is what akmod was designed to do. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Sun, Jul 18, 2010 at 11:53:49 -0400, Genes MailLists li...@sapience.com wrote: On 07/18/2010 11:14 AM, Bruno Wolff III wrote: akmod solves all these problems - why are we trying to find additional and more complicated solutions ? It is what akmod was designed to do. Both solutions have different drawbacks. akmod doesn't always work. I would argue that akmod is more complicated than using rpm tags. The reason we are looking for other solutions is that akmod doesn't seem to work for some people and they are looking for solutions that might fit their circumstances better. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Thursday, July 15, 2010 06:51:31 Christofer C. Bell wrote: On Wed, Jul 14, 2010 at 10:58 PM, Tim ignored_mail...@yahoo.com.au wrote: On Wed, 2010-07-14 at 11:38 -0700, Rick Stevens wrote: I can see two possible solutions. One would take the form of yum checking to see if kmods are needed for a new kernel on the system and not downloading the kernel if the kmods aren't available. I thought that was already done with the skip-broken option/plugin? Where an update run would only bring in all the things that could be installed. The next run would do whatever else it omitted before, if the modules had been built in the meantime. That's not how it works and not what --skip-broken does. That option skips trying to update packages for which there are broken dependencies. In this case, there are no broken dependencies. The new kernel is available, installable, and all packages on which it depends are available and installable. The Fedora kernel does not have a dependency defined for the proprietary nVidia driver, so it's not considered broken when it can't be updated. True. But I am sure it would be easy for some rpmfusion developer to create a custom yum plugin that would check the existence of an appropriate kmod package for every new kernel that is to be pulled in on an update, and if the kmod is missing, do the yum update exclude=kernel* instead. This plugin could be a dependency of kmod-nvidia, and only users who install kmod-nvidia would use it. I am not familiar with coding yum plugins, but I believe this is not too hard to do. And there certainly is a lot of demand for this kind of thing from the users, apparently. In response to the wider discussion (not specifically to you, Tim), asking the Fedora Project to work around brokenness the user introduces themselves through the use of 3rd party software is entirely unreasonable. When you upgrade the core of your operating system, regardless of vendor, there is no expectation that 3rd party software or drivers will continue to work. It is up to you, the user, to ensure that 3rd party software you depend on works in your new environment. If dealing with kernel upgrades that break 3rd party software is not for you, and you don't know how to work around it, then either find out how or accept that Fedora may not be what you're looking for. Nothing specific is asked from Fedora here. The users just want the conditional kernel updating to be done automatically rather than manually, so that they don't need to learn how to work around the problem when it appears. If the rpmfusion repo provides the 3rd party software, they could easily provide the above custom yum plugin, right? That way the entire thing can be made fully automatic and the user need not worry about it. Once the user installs the kmod-nvidia package, the nvidia-kernel-yum plugin gets pulled as a dependency, installed, enabled, and from then on everything is transparent to the user. We only need to convince someone knowledgeable to write that plugin and package it to rpmfusion repo. AFAIK, once this plugin is done, it doesn't even need any maintenance or so. Hell, if I had a free week to learn yum a bit, I would do it myself. And I don't even use any nvidia cards under Fedora atm... HTH, :-) Marko -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Thu, Jul 15, 2010 at 8:46 AM, Marko Vojinovic vvma...@gmail.com wrote: On Thursday, July 15, 2010 06:51:31 Christofer C. Bell wrote: That's not how it works and not what --skip-broken does. That option skips trying to update packages for which there are broken dependencies. In this case, there are no broken dependencies. The new kernel is available, installable, and all packages on which it depends are available and installable. The Fedora kernel does not have a dependency defined for the proprietary nVidia driver, so it's not considered broken when it can't be updated. True. But I am sure it would be easy for some rpmfusion developer to create a custom yum plugin that would check the existence of an appropriate kmod package for every new kernel that is to be pulled in on an update, and if the kmod is missing, do the yum update exclude=kernel* instead. This plugin could be a dependency of kmod-nvidia, and only users who install kmod-nvidia would use it. If the rpmfusion repo provides the 3rd party software, they could easily provide the above custom yum plugin, right? That way the entire thing can be made fully automatic and the user need not worry about it. Once the user installs the kmod-nvidia package, the nvidia-kernel-yum plugin gets pulled as a dependency, installed, enabled, and from then on everything is transparent to the user. We only need to convince someone knowledgeable to write that plugin and package it to rpmfusion repo. AFAIK, once this plugin is done, it doesn't even need any maintenance or so. Hell, if I had a free week to learn yum a bit, I would do it myself. And I don't even use any nvidia cards under Fedora atm... This is actually a really good idea, and also puts the onus for clean proprietary kmod integration where it belongs (if not in the user's hands), on the packager of the kmod. Who would need convincing to take a look at this? I'd hate to approach the RPM Fusion team and say, provide this. I'm in the same boat as you with regards to learning yum internals and not using nvidia cards under Fedora. It sounds like it would be a fun project! -- Chris -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/15/2010 07:15 AM, Tim wrote: On Thu, 2010-07-15 at 14:46 +0100, Marko Vojinovic wrote: The users just want the conditional kernel updating to be done automatically rather than manually, so that they don't need to learn how to work around the problem when it appears. I don't mind knowing what to do, but since it's the computer, I'd like it to be *able* to automatically handle this by itself, one way or another. Also considering both mainstream graphic cards are Nvidia and Ati and both need attention when updating an automatic process would be greatly appreciated. Michael -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, Jul 14, 2010 at 3:42 AM, Michael Miles mmami...@gmail.com wrote: On 07/13/2010 06:06 PM, Patrick Bartek wrote: --- On Tue, 7/13/10, Michael Milesmmami...@gmail.com wrote: Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking That's why I update manually. No auto-update for me. I don't even use the -y switch with yum, so I can still opt out of the update after I see the download list. As far as the new kmod, wait a few days, then check again. The longest I had to wait one time (with F9) was a week, but most times it was a day or two. However, I don't have to wait anymore: F12's nouveau works just fine with my old GeForce 6600 card. B It just seems odd that this would be overlooked as to someone who is newer to Linux than myself could find themselves in trouble if they just updated because the system says there are updates. It is not overlooked by the Fedora package builders - remember that the Nvidia drivers are built by rpmfusion and not in the Fedora update system. So they are on a third party repo and the guys at rpmfusion will take some time to build the nvidia stuff for a new kernel once it is released. As a previous poster mentioned - just wait a few days and try again. In the meantime it is quite easy to boot back to the previous kernel where you had the nvidia stuff in place - then when the new kmod is available and installed then boot into the new kernel with the new kmod.. -- mike c -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, Jul 14, 2010 at 3:42 AM, Michael Miles mmami...@gmail.com wrote: On 07/13/2010 06:06 PM, Patrick Bartek wrote: --- On Tue, 7/13/10, Michael Milesmmami...@gmail.com wrote: Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking That's why I update manually. No auto-update for me. I don't even use the -y switch with yum, so I can still opt out of the update after I see the download list. As far as the new kmod, wait a few days, then check again. The longest I had to wait one time (with F9) was a week, but most times it was a day or two. However, I don't have to wait anymore: F12's nouveau works just fine with my old GeForce 6600 card. B It just seems odd that this would be overlooked as to someone who is newer to Linux than myself could find themselves in trouble if they just updated because the system says there are updates. It is not overlooked by the Fedora package builders - remember that the Nvidia drivers are built by rpmfusion and not in the Fedora update system. So they are on a third party repo and the guys at rpmfusion will take some time to build the nvidia stuff for a new kernel once it is released. As a previous poster mentioned - just wait a few days and try again. In the meantime it is quite easy to boot back to the previous kernel where you had the nvidia stuff in place - then when the new kmod is available and installed then boot into the new kernel with the new kmod.. On my system I use akmods akmods-nvidia The way it works for me is that if necessary akmods rebuilds the nVidia kernel module when I reboot into a new kernel. Some people have no luck with the akmods method. For me, it has always worked perfectly. This is on Fedora 13. Steven P. Ulrick -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, Jul 14, 2010 at 12:14 PM, Steven P. Ulrick lists-fed...@afolkey2.net wrote: On my system I use akmods akmods-nvidia The way it works for me is that if necessary akmods rebuilds the nVidia kernel module when I reboot into a new kernel. Some people have no luck with the akmods method. For me, it has always worked perfectly. This is on Fedora 13. I used to use the akmod also - mostly it did work for me but there were some graphics cards for which it did not work and I ended up not using the akmod or kmod once the open source drivers started becoming generally reliable (apart from 3d). However the additional use of the mesa-dri-drivers-experimental package is giving some very good results for 3d. -- mike c -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/14/2010 04:14 AM, Steven P. Ulrick wrote: On Wed, Jul 14, 2010 at 3:42 AM, Michael Milesmmami...@gmail.com wrote: On 07/13/2010 06:06 PM, Patrick Bartek wrote: --- On Tue, 7/13/10, Michael Milesmmami...@gmail.com wrote: Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking That's why I update manually. No auto-update for me. I don't even use the -y switch with yum, so I can still opt out of the update after I see the download list. As far as the new kmod, wait a few days, then check again. The longest I had to wait one time (with F9) was a week, but most times it was a day or two. However, I don't have to wait anymore: F12's nouveau works just fine with my old GeForce 6600 card. B It just seems odd that this would be overlooked as to someone who is newer to Linux than myself could find themselves in trouble if they just updated because the system says there are updates. It is not overlooked by the Fedora package builders - remember that the Nvidia drivers are built by rpmfusion and not in the Fedora update system. So they are on a third party repo and the guys at rpmfusion will take some time to build the nvidia stuff for a new kernel once it is released. As a previous poster mentioned - just wait a few days and try again. In the meantime it is quite easy to boot back to the previous kernel where you had the nvidia stuff in place - then when the new kmod is available and installed then boot into the new kernel with the new kmod.. On my system I use akmods akmods-nvidia The way it works for me is that if necessary akmods rebuilds the nVidia kernel module when I reboot into a new kernel. Some people have no luck with the akmods method. For me, it has always worked perfectly. This is on Fedora 13. Steven P. Ulrick I fully understand the obligations of Fedora and RPMFusion and I do understand that it is easy to fall back if thing don't work like they are supposed to but to a person who just loaded Fedora for the first time might be really baffled when they do an update and find the system will not boot up. I just think the updates should be held back until all the required software is present. Michael -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wednesday 14 July 2010 10:27 AM, Michael Miles wrote: I fully understand the obligations of Fedora and RPMFusion and I do understand that it is easy to fall back if thing don't work like they are supposed to but to a person who just loaded Fedora for the first time might be really baffled when they do an update and find the system will not boot up. Some one who has RPMFusion installed is definitely not a brand new user, and some one who has the proprietary nvidia drivers installed are definitely not a novice. After all, they managed to follow the instructions on the RPMFusion wiki to blacklist nouveau. I just think the updates should be held back until all the required software is present. By default fedora provides nouveau, which works. I find it works well enough to even support dual screens (I have tried it with Ubuntu Lucid). So someone using the proprietary drivers made a choice knowingly about the pitfalls. However something that could be improved is probably the instructions on the RPMFusion wiki, to include this warning and explicitly state wait and update would be a healthy practice for a system using proprietary drivers (and maybe even the fedoraproject wiki?). Michael Just my 2 cents. PS: With all these kmod problems suddenly ATI looks very promising to me with much better working opensource drivers. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/14/2010 10:27 AM, Michael Miles wrote: On 07/14/2010 04:14 AM, Steven P. Ulrick wrote: On my system I use akmods akmods-nvidia The way it works for me is that if necessary akmods rebuilds the nVidia kernel module when I reboot into a new kernel. Some people have no luck with the akmods method. For me, it has always worked perfectly. This is on Fedora 13. Steven P. Ulrick I fully understand the obligations of Fedora and RPMFusion and I do understand that it is easy to fall back if thing don't work like they are supposed to but to a person who just loaded Fedora for the first time might be really baffled when they do an update and find the system will not boot up. I just think the updates should be held back until all the required software is present. Chicken and egg, Michael. They can't do kmods until the kernel is out and with your suggestion, the kernel can't come out until the kmods are done. I agree it's a problem. As long as there are two groups working on it (kernel and kmods) and there's little communication pre-release between them, I don't see a simple resolution. I can see two possible solutions. One would take the form of yum checking to see if kmods are needed for a new kernel on the system and not downloading the kernel if the kmods aren't available. Simply using dependencies isn't feasible as that would block people who don't need the kmods from using the kernel when it's released. Yum would need to do some snooping on the system to find if kmods are needed or not. The second could be the grub updater doing a similar thing and not making the new kernel the default booting kernel if kmods don't exist. It'd have to do a similar kind of snoop that yum would have to do. I don't think either of these will be forthcoming anytime soon. -- - Rick Stevens, Systems Engineer, C2 Hosting ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - What is a free gift? Aren't all gifts free? - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wednesday 14 July 2010 11:38 AM, Rick Stevens wrote: The second could be the grub updater doing a similar thing and not making the new kernel the default booting kernel if kmods don't exist. It'd have to do a similar kind of snoop that yum would have to do. The user can do this themselves, $ cat /etc/sysconfig/kernel # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes Change the UPDATEDEFAULT to no -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/14/2010 01:12 PM, Suvayu Ali wrote: On Wednesday 14 July 2010 11:38 AM, Rick Stevens wrote: The second could be the grub updater doing a similar thing and not making the new kernel the default booting kernel if kmods don't exist. It'd have to do a similar kind of snoop that yum would have to do. The user can do this themselves, $ cat /etc/sysconfig/kernel # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes Change the UPDATEDEFAULT to no no there simply means that grub should not make the new kernel the default at boot. It doesn't check to see if a kmod is available for the new kernel or if the user's hardware configuration requires one (or if the user is using a driver that needs one). -- - Rick Stevens, Systems Engineer, C2 Hosting ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - If you are what you eat, then I'm fast, cheap and greasy! - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 14 July 2010 15:50, Rick Stevens ri...@nerd.com wrote: On 07/14/2010 01:12 PM, Suvayu Ali wrote: On Wednesday 14 July 2010 11:38 AM, Rick Stevens wrote: The second could be the grub updater doing a similar thing and not making the new kernel the default booting kernel if kmods don't exist. It'd have to do a similar kind of snoop that yum would have to do. The user can do this themselves, $ cat /etc/sysconfig/kernel # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes Change the UPDATEDEFAULT to no no there simply means that grub should not make the new kernel the default at boot. It doesn't check to see if a kmod is available for the new kernel or if the user's hardware configuration requires one (or if the user is using a driver that needs one). I'm sorry I didn't explain myself well enough. When I say user I mean a user who has installed kmods on their system. What I'm saying is instead of looking for a complicated solution which is going to be used by a relatively small section of the entire fedora user base, maybe its worthwhile for the person using kmods to manage this on their own end by changing that setting. Then when s/he is confident that they have the needed kmods, then can manually change the default kernel. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, 2010-07-14 at 11:38 -0700, Rick Stevens wrote: I can see two possible solutions. One would take the form of yum checking to see if kmods are needed for a new kernel on the system and not downloading the kernel if the kmods aren't available. I thought that was already done with the skip-broken option/plugin? Where an update run would only bring in all the things that could be installed. The next run would do whatever else it omitted before, if the modules had been built in the meantime. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On Wed, Jul 14, 2010 at 10:58 PM, Tim ignored_mail...@yahoo.com.au wrote: On Wed, 2010-07-14 at 11:38 -0700, Rick Stevens wrote: I can see two possible solutions. One would take the form of yum checking to see if kmods are needed for a new kernel on the system and not downloading the kernel if the kmods aren't available. I thought that was already done with the skip-broken option/plugin? Where an update run would only bring in all the things that could be installed. The next run would do whatever else it omitted before, if the modules had been built in the meantime. That's not how it works and not what --skip-broken does. That option skips trying to update packages for which there are broken dependencies. In this case, there are no broken dependencies. The new kernel is available, installable, and all packages on which it depends are available and installable. The Fedora kernel does not have a dependency defined for the proprietary nVidia driver, so it's not considered broken when it can't be updated. In response to the wider discussion (not specifically to you, Tim), asking the Fedora Project to work around brokenness the user introduces themselves through the use of 3rd party software is entirely unreasonable. When you upgrade the core of your operating system, regardless of vendor, there is no expectation that 3rd party software or drivers will continue to work. It is up to you, the user, to ensure that 3rd party software you depend on works in your new environment. If dealing with kernel upgrades that break 3rd party software is not for you, and you don't know how to work around it, then either find out how or accept that Fedora may not be what you're looking for. This is documented in the 4 Foundations of the Fedora Project: First [ . . . ] We recognize that there is also a place for long-term stability in the Linux ecosystem, and that there are a variety of community-oriented and business-oriented Linux distributions available to serve that need. However, the Fedora Project's goal of advancing free software dictates that the Fedora Project itself pursue a strategy that preserves the forward momentum of our technical, collateral, and community-building progress. Fedora always aims to provide the future, first. If you're relying on slow to release proprietary 3rd party software, well, the Fedora train has already left the station. If you need something that's going to provide an unchanging framework in which to run your 3rd party software, there are a variety of community-oriented and business-oriented Linux distributions that serve that need. Likewise, also documented in the 4 Foundations of the project, is the concept of Freedom, and this commitment to Freedom precludes the Project from devoting (or wasting) time on ensuring that proprietary 3rd party kmods work with the operating system: Freedom [ . . . ] Freedom represents dedication to free software and content. We believe that advancing software and content freedom is a central goal for the Fedora Project, and that we should accomplish that goal through the use of the software and content we promote. By including free alternatives to proprietary code and content, we can improve the overall state of free and open source software and content, and limit the effects of proprietary or patent encumbered code on the Project. Sometimes this goal prevents us from taking the easy way out by including proprietary or patent encumbered software in Fedora, or using those kinds of products in our other project work. If this commitment to Free software is something that you find inconvenient or problematic, then again, Fedora may not be the solution you are looking for. However, if you feel the overall goals of the Fedora project are worth supporting, but find you rely on proprietary 3rd party software, then the onus is on you to educate yourself on how to make that happen. -- Chris -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
New Update has no kmod for new kernel and new nvidia driver
Hello Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking Michael -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
--- On Tue, 7/13/10, Michael Miles mmami...@gmail.com wrote: Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking That's why I update manually. No auto-update for me. I don't even use the -y switch with yum, so I can still opt out of the update after I see the download list. As far as the new kmod, wait a few days, then check again. The longest I had to wait one time (with F9) was a week, but most times it was a day or two. However, I don't have to wait anymore: F12's nouveau works just fine with my old GeForce 6600 card. B -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Update has no kmod for new kernel and new nvidia driver
On 07/13/2010 06:06 PM, Patrick Bartek wrote: --- On Tue, 7/13/10, Michael Milesmmami...@gmail.com wrote: Fedora 12 x86_64 I did look this time and it seems the gods that have control did not give a kmod for the new Nvidia driver 195.36.31 for the new kernel 2.6.32.16-141. It has a kmod there for the old kernel 2.6.32.14-127 The metapackage is there to track in new kmod but if there is no kmod there how can it track in? Anyway I hope nobody just pressed update without checking That's why I update manually. No auto-update for me. I don't even use the -y switch with yum, so I can still opt out of the update after I see the download list. As far as the new kmod, wait a few days, then check again. The longest I had to wait one time (with F9) was a week, but most times it was a day or two. However, I don't have to wait anymore: F12's nouveau works just fine with my old GeForce 6600 card. B It just seems odd that this would be overlooked as to someone who is newer to Linux than myself could find themselves in trouble if they just updated because the system says there are updates. I look on every update now just to make sure. I'm just using a nvidia 9400 gt but I need the drivers from nvidia for the Cuda I run s...@home with boinc and GPU crunching is quick Anyway will wait a bit and see. Last time only took 4 days so we shall see Michael -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
