Mailing List Archive: MythTV: Users

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading

Index | Next | Previous | View Threaded

kim+j2 at alleroedderne

Nov 26, 2009, 2:10 AM

Post #1 of 11 (1543 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading

Gabe Rubin wrote:
> Hi all,
>
> I just updated my system to Fedora 12 (from 10) by using a DVD and
> then yum-upgrade. In the process, I can't get Xorg starting due to a
> nvidia issue.
I had the same problems and googled after "nvidia fedora 12" ...

The base thing to do is to add "nouveau.modeset=0" kernel argument to
kernel line in the /boo/grub/grub.conf file.

Good luck,
Kim

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

gaberubin at gmail

Nov 26, 2009, 9:08 AM

Post #2 of 11 (1469 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

As many pointed out, adding "nouveau.modeset=0" at the end of the
kernel line in grub.conf is the solution. I also specified a VGA
mode, but that caused more problems so I changed that to "vga=normal".
Not sure if a vga argument is needed.

I guess I will need to add this to the kernel line each time I upgrade
the kernel. Also strange, it appears that atrpms script write to
/etc/modprobe.conf to specify the driver version when that has been
depreciated and it should go into /etc/modprobe.d/local.conf.

This seems like such a big deal and really surprised that it was so
hard to figure out (I did not see it in the release notes and my
googling did not show it, although obviously others were able to
figure it out). I personally don't think that fedora should make it
this difficult to run the nvidia drive and attempt to impose the
nouveau driver upon users. Hopefully this thread will help others.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Nov 26, 2009, 9:46 AM

Post #3 of 11 (1462 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On 11/26/2009 12:08 PM, Gabe Rubin wrote:
> As many pointed out, adding "nouveau.modeset=0" at the end of the
> kernel line in grub.conf is the solution. I also specified a VGA
> mode, but that caused more problems so I changed that to "vga=normal".
> Not sure if a vga argument is needed.

Its not. And nouveau.modeset=0 isn't strictly required. If you have the
nouveau module blacklisted, a newly built initrd won't include the
nouveau module, and you can boot w/o any extra params.

> I guess I will need to add this to the kernel line each time I upgrade
> the kernel.

No. The kernel update mechanism is bright enough to carry args from your
existing grub stanza to the new one.

However, as I said above, if nouveau is blacklisted, a newly created
initrd (including the one that'll be created when you install a new
kernel) won't have have the nouveau module in it, and thus won't need
the param anyway.

> Also strange, it appears that atrpms script write to
> /etc/modprobe.conf to specify the driver version when that has been
> depreciated and it should go into /etc/modprobe.d/local.conf.

Or better yet, /etc/modprobe.d/<somethingunique>.conf.

> This seems like such a big deal and really surprised that it was so
> hard to figure out (I did not see it in the release notes and my
> googling did not show it, although obviously others were able to
> figure it out).

Its pretty well covered in the rpm fusion wiki, not sure if its spelled
out in the ATrpms docs anywhere. Its definitely NOT covered in the
Fedora docs, because, well, it has to do with a binary-only driver that
Fedora doesn't ship.

> I personally don't think that fedora should make it
> this difficult to run the nvidia drive and attempt to impose the
> nouveau driver upon users.

Um. I'm not even sure where to begin with a reply to this. Fedora ships
a functional driver that Just Works, complete with kernel mode setting,
dual-head support, etc, and that shouldn't be "imposed" on people? And
the Fedora project is supposed to do what exactly to make it as easy as
possible for you to install a 3rd-party binary-only driver?

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

gaberubin at gmail

Nov 26, 2009, 10:06 AM

Post #4 of 11 (1463 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On Thu, Nov 26, 2009 at 9:46 AM, Jarod Wilson <jarod [at] wilsonet> wrote:
> On 11/26/2009 12:08 PM, Gabe Rubin wrote:
>>
>> As many pointed out, adding �"nouveau.modeset=0" at the end of the
>> kernel line in grub.conf is the solution. �I also specified a VGA
>> mode, but that caused more problems so I changed that to "vga=normal".
>> �Not sure if a vga argument is needed.
>
> Its not. And nouveau.modeset=0 isn't strictly required. If you have the
> nouveau module blacklisted, a newly built initrd won't include the nouveau
> module, and you can boot w/o any extra params.

I have this stanza in /etc/modprobe.d/blacklist.conf:
blacklist nouveau

That did not help me until I actually added the kernel parameter in
grub.conf. I did reboot.

>
>> I guess I will need to add this to the kernel line each time I upgrade
>> the kernel.
>
> No. The kernel update mechanism is bright enough to carry args from your
> existing grub stanza to the new one.
>
> However, as I said above, if nouveau is blacklisted, a newly created initrd
> (including the one that'll be created when you install a new kernel) won't
> have have the nouveau module in it, and thus won't need the param anyway.

That is good to know (although, as I said, blacklisting did not seem to help).

>
>> Also strange, it appears that atrpms script write to
>> /etc/modprobe.conf to specify the driver version when that has been
>> depreciated and it should go into /etc/modprobe.d/local.conf.
>
> Or better yet, /etc/modprobe.d/<somethingunique>.conf.
>

Any way to make this automatic or is that just the choice of the
package distributor (i.e., should I let Axel know about this situation
or can I fix it myself)?

>> This seems like such a big deal and really surprised that it was so
>> hard to figure out (I did not see it in the release notes and my
>> googling did not show it, although obviously others were able to
>> figure it out).
>
> Its pretty well covered in the rpm fusion wiki, not sure if its spelled out
> in the ATrpms docs anywhere. Its definitely NOT covered in the Fedora docs,
> because, well, it has to do with a binary-only driver that Fedora doesn't
> ship.
>
That is understandable. I don't use rpmfusion so did not look there
until directed to. Hopefully these messages on the mythlist and
atrpms list will let others find it.

>> I personally don't think that fedora should make it
>> this difficult to run the nvidia drive and attempt to impose the
>> nouveau driver upon users.
>
> Um. I'm not even sure where to begin with a reply to this. Fedora ships a
> functional driver that Just Works, complete with kernel mode setting,
> dual-head support, etc, and that shouldn't be "imposed" on people? And the
> Fedora project is supposed to do what exactly to make it as easy as possible
> for you to install a 3rd-party binary-only driver?
>

Re-reading what I wrote, I see why offense could be taken to what I
said. I respect that fedora comes shipping with a free (in all senses
of the word) and functional driver for nvidia cards. I said "impose"
because my thinking was if you have to much with grub.conf and add
kernel parameters, that is very tricky for most users to figure out
how to get the binary drivers going. Of course, the reality is
probably is that fedora wants to ship a highly functional system that
works out of the box without resorting to the binary non-free stuff
and if someone wants to use the nvidia binary, they should figure out
how to do it. My frustration was that it took a lot of time for me to
figure out how to do that, which was the result of the choice to put
in nouveau. But upon reflection, that was not a bad thing that the
fedora team did, and I should not have implied or directly stated that
it was.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

bc-mythtv at comcast

Nov 26, 2009, 12:54 PM

Post #5 of 11 (1448 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On 11/26/09 13:06, Gabe Rubin wrote:
> On Thu, Nov 26, 2009 at 9:46 AM, Jarod Wilson<jarod [at] wilsonet> wrote:
>> Its not. And nouveau.modeset=0 isn't strictly required. If you have the
>> nouveau module blacklisted, a newly built initrd won't include the nouveau
>> module, and you can boot w/o any extra params.
>
> I have this stanza in /etc/modprobe.d/blacklist.conf:
> blacklist nouveau
>
>
> That did not help me until I actually added the kernel parameter in
> grub.conf. I did reboot.

You have to rebuild initrd *after* you blacklist nouveau.

Bolek
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Nov 26, 2009, 6:02 PM

Post #6 of 11 (1426 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On 11/26/2009 01:06 PM, Gabe Rubin wrote:
> On Thu, Nov 26, 2009 at 9:46 AM, Jarod Wilson<jarod [at] wilsonet> wrote:
>> On 11/26/2009 12:08 PM, Gabe Rubin wrote:
>>>
>>> As many pointed out, adding "nouveau.modeset=0" at the end of the
>>> kernel line in grub.conf is the solution. I also specified a VGA
>>> mode, but that caused more problems so I changed that to "vga=normal".
>>> Not sure if a vga argument is needed.
>>
>> Its not. And nouveau.modeset=0 isn't strictly required. If you have the
>> nouveau module blacklisted, a newly built initrd won't include the nouveau
>> module, and you can boot w/o any extra params.
>
> I have this stanza in /etc/modprobe.d/blacklist.conf:
> blacklist nouveau
>
>
> That did not help me until I actually added the kernel parameter in
> grub.conf. I did reboot.

You're missing a step. The nouveau module is already in your existing
initrd, where it will be loaded *before* your root filesystem is
mounted, *before* the blacklist file can be read. You have to rebuild
your initrd after adding the blacklist entry. I've done this. I know it
works. Later kernels will get installed and have their initrd generated
with the blacklisting already in place, and their initrd won't have nouveau.

>>> I guess I will need to add this to the kernel line each time I upgrade
>>> the kernel.
>>
>> No. The kernel update mechanism is bright enough to carry args from your
>> existing grub stanza to the new one.
>>
>> However, as I said above, if nouveau is blacklisted, a newly created initrd
>> (including the one that'll be created when you install a new kernel) won't
>> have have the nouveau module in it, and thus won't need the param anyway.
>
> That is good to know (although, as I said, blacklisting did not seem to help).

See above.

>>> Also strange, it appears that atrpms script write to
>>> /etc/modprobe.conf to specify the driver version when that has been
>>> depreciated and it should go into /etc/modprobe.d/local.conf.
>>
>> Or better yet, /etc/modprobe.d/<somethingunique>.conf.
>>
>
> Any way to make this automatic or is that just the choice of the
> package distributor (i.e., should I let Axel know about this situation
> or can I fix it myself)?

Package distributor. I believe RPM Fusion's nvidia drivers include
either an /etc/modprobe.d/nouveau.conf or nvidia.conf for this purpose.

...
>>> I personally don't think that fedora should make it
>>> this difficult to run the nvidia drive and attempt to impose the
>>> nouveau driver upon users.
>>
>> Um. I'm not even sure where to begin with a reply to this. Fedora ships a
>> functional driver that Just Works, complete with kernel mode setting,
>> dual-head support, etc, and that shouldn't be "imposed" on people? And the
>> Fedora project is supposed to do what exactly to make it as easy as possible
>> for you to install a 3rd-party binary-only driver?
>>
>
> Re-reading what I wrote, I see why offense could be taken to what I
> said. I respect that fedora comes shipping with a free (in all senses
> of the word) and functional driver for nvidia cards. I said "impose"
> because my thinking was if you have to much with grub.conf and add
> kernel parameters, that is very tricky for most users to figure out
> how to get the binary drivers going. Of course, the reality is
> probably is that fedora wants to ship a highly functional system that
> works out of the box without resorting to the binary non-free stuff
> and if someone wants to use the nvidia binary, they should figure out
> how to do it. My frustration was that it took a lot of time for me to
> figure out how to do that, which was the result of the choice to put
> in nouveau. But upon reflection, that was not a bad thing that the
> fedora team did, and I should not have implied or directly stated that
> it was.

Wasn't offended, just saddened that all the hard work being done to
create a free and open driver that Just Works gets stomped on because it
made it harder to install a 3rd-party binary blob. :)

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

support at ocg

Nov 26, 2009, 7:08 PM

Post #7 of 11 (1422 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

Same here..I had to recompile the kernel (initrd) without rivafb/nvidiafb
and then the Nvidia driver started to work

-----Original Message-----
From: mythtv-users-bounces [at] mythtv
[mailto:mythtv-users-bounces [at] mythtv] On Behalf Of Jarod Wilson
Sent: Thursday, November 26, 2009 9:02 PM
To: Myth TV Users List
Subject: Re: [mythtv-users] [ATrpms-users] Updated from fedora 10 to 12 and
have issues with nvidia driver loading

On 11/26/2009 01:06 PM, Gabe Rubin wrote:
> On Thu, Nov 26, 2009 at 9:46 AM, Jarod Wilson<jarod [at] wilsonet> wrote:
>> On 11/26/2009 12:08 PM, Gabe Rubin wrote:
>>>
>>> As many pointed out, adding "nouveau.modeset=0" at the end of the
>>> kernel line in grub.conf is the solution. I also specified a VGA
>>> mode, but that caused more problems so I changed that to "vga=normal".
>>> Not sure if a vga argument is needed.
>>
>> Its not. And nouveau.modeset=0 isn't strictly required. If you have
>> the nouveau module blacklisted, a newly built initrd won't include
>> the nouveau module, and you can boot w/o any extra params.
>
> I have this stanza in /etc/modprobe.d/blacklist.conf:
> blacklist nouveau
>
>
> That did not help me until I actually added the kernel parameter in
> grub.conf. I did reboot.

You're missing a step. The nouveau module is already in your existing
initrd, where it will be loaded *before* your root filesystem is mounted,
*before* the blacklist file can be read. You have to rebuild your initrd
after adding the blacklist entry. I've done this. I know it works. Later
kernels will get installed and have their initrd generated with the
blacklisting already in place, and their initrd won't have nouveau.

>>> I guess I will need to add this to the kernel line each time I
>>> upgrade the kernel.
>>
>> No. The kernel update mechanism is bright enough to carry args from
>> your existing grub stanza to the new one.
>>
>> However, as I said above, if nouveau is blacklisted, a newly created
>> initrd (including the one that'll be created when you install a new
>> kernel) won't have have the nouveau module in it, and thus won't need the
param anyway.
>
> That is good to know (although, as I said, blacklisting did not seem to
help).

See above.

>>> Also strange, it appears that atrpms script write to
>>> /etc/modprobe.conf to specify the driver version when that has been
>>> depreciated and it should go into /etc/modprobe.d/local.conf.
>>
>> Or better yet, /etc/modprobe.d/<somethingunique>.conf.
>>
>
> Any way to make this automatic or is that just the choice of the
> package distributor (i.e., should I let Axel know about this situation
> or can I fix it myself)?

Package distributor. I believe RPM Fusion's nvidia drivers include either an
/etc/modprobe.d/nouveau.conf or nvidia.conf for this purpose.

...
>>> I personally don't think that fedora should make it this difficult
>>> to run the nvidia drive and attempt to impose the nouveau driver
>>> upon users.
>>
>> Um. I'm not even sure where to begin with a reply to this. Fedora
>> ships a functional driver that Just Works, complete with kernel mode
>> setting, dual-head support, etc, and that shouldn't be "imposed" on
>> people? And the Fedora project is supposed to do what exactly to make
>> it as easy as possible for you to install a 3rd-party binary-only driver?
>>
>
> Re-reading what I wrote, I see why offense could be taken to what I
> said. I respect that fedora comes shipping with a free (in all senses
> of the word) and functional driver for nvidia cards. I said "impose"
> because my thinking was if you have to much with grub.conf and add
> kernel parameters, that is very tricky for most users to figure out
> how to get the binary drivers going. Of course, the reality is
> probably is that fedora wants to ship a highly functional system that
> works out of the box without resorting to the binary non-free stuff
> and if someone wants to use the nvidia binary, they should figure out
> how to do it. My frustration was that it took a lot of time for me to
> figure out how to do that, which was the result of the choice to put
> in nouveau. But upon reflection, that was not a bad thing that the
> fedora team did, and I should not have implied or directly stated that
> it was.

Wasn't offended, just saddened that all the hard work being done to create a
free and open driver that Just Works gets stomped on because it made it
harder to install a 3rd-party binary blob. :)

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jarod at wilsonet

Nov 26, 2009, 7:17 PM

Post #8 of 11 (1419 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On 11/26/2009 10:08 PM, Michelle Dupuis wrote:
> Same here..I had to recompile the kernel (initrd) without rivafb/nvidiafb
> and then the Nvidia driver started to work

Um. Just for the record, building a new initrd is nothing even *close*
to "recompile the kernel". A new initrd is just a compressed image of
stuff that is either scripts or already compiled. Recompiling the kernel
involves building a new kernel from source code. Very very different things.

> -----Original Message-----
> From: mythtv-users-bounces [at] mythtv
> [mailto:mythtv-users-bounces [at] mythtv] On Behalf Of Jarod Wilson
> Sent: Thursday, November 26, 2009 9:02 PM
> To: Myth TV Users List
> Subject: Re: [mythtv-users] [ATrpms-users] Updated from fedora 10 to 12 and
> have issues with nvidia driver loading
>
> On 11/26/2009 01:06 PM, Gabe Rubin wrote:
>> On Thu, Nov 26, 2009 at 9:46 AM, Jarod Wilson<jarod [at] wilsonet> wrote:
>>> On 11/26/2009 12:08 PM, Gabe Rubin wrote:
>>>>
>>>> As many pointed out, adding "nouveau.modeset=0" at the end of the
>>>> kernel line in grub.conf is the solution. I also specified a VGA
>>>> mode, but that caused more problems so I changed that to "vga=normal".
>>>> Not sure if a vga argument is needed.
>>>
>>> Its not. And nouveau.modeset=0 isn't strictly required. If you have
>>> the nouveau module blacklisted, a newly built initrd won't include
>>> the nouveau module, and you can boot w/o any extra params.
>>
>> I have this stanza in /etc/modprobe.d/blacklist.conf:
>> blacklist nouveau
>>
>>
>> That did not help me until I actually added the kernel parameter in
>> grub.conf. I did reboot.
>
> You're missing a step. The nouveau module is already in your existing
> initrd, where it will be loaded *before* your root filesystem is mounted,
> *before* the blacklist file can be read. You have to rebuild your initrd
> after adding the blacklist entry. I've done this. I know it works. Later
> kernels will get installed and have their initrd generated with the
> blacklisting already in place, and their initrd won't have nouveau.
>
>>>> I guess I will need to add this to the kernel line each time I
>>>> upgrade the kernel.
>>>
>>> No. The kernel update mechanism is bright enough to carry args from
>>> your existing grub stanza to the new one.
>>>
>>> However, as I said above, if nouveau is blacklisted, a newly created
>>> initrd (including the one that'll be created when you install a new
>>> kernel) won't have have the nouveau module in it, and thus won't need the
> param anyway.
>>
>> That is good to know (although, as I said, blacklisting did not seem to
> help).
>
> See above.
>
>>>> Also strange, it appears that atrpms script write to
>>>> /etc/modprobe.conf to specify the driver version when that has been
>>>> depreciated and it should go into /etc/modprobe.d/local.conf.
>>>
>>> Or better yet, /etc/modprobe.d/<somethingunique>.conf.
>>>
>>
>> Any way to make this automatic or is that just the choice of the
>> package distributor (i.e., should I let Axel know about this situation
>> or can I fix it myself)?
>
> Package distributor. I believe RPM Fusion's nvidia drivers include either an
> /etc/modprobe.d/nouveau.conf or nvidia.conf for this purpose.
>
> ...
>>>> I personally don't think that fedora should make it this difficult
>>>> to run the nvidia drive and attempt to impose the nouveau driver
>>>> upon users.
>>>
>>> Um. I'm not even sure where to begin with a reply to this. Fedora
>>> ships a functional driver that Just Works, complete with kernel mode
>>> setting, dual-head support, etc, and that shouldn't be "imposed" on
>>> people? And the Fedora project is supposed to do what exactly to make
>>> it as easy as possible for you to install a 3rd-party binary-only driver?
>>>
>>
>> Re-reading what I wrote, I see why offense could be taken to what I
>> said. I respect that fedora comes shipping with a free (in all senses
>> of the word) and functional driver for nvidia cards. I said "impose"
>> because my thinking was if you have to much with grub.conf and add
>> kernel parameters, that is very tricky for most users to figure out
>> how to get the binary drivers going. Of course, the reality is
>> probably is that fedora wants to ship a highly functional system that
>> works out of the box without resorting to the binary non-free stuff
>> and if someone wants to use the nvidia binary, they should figure out
>> how to do it. My frustration was that it took a lot of time for me to
>> figure out how to do that, which was the result of the choice to put
>> in nouveau. But upon reflection, that was not a bad thing that the
>> fedora team did, and I should not have implied or directly stated that
>> it was.
>
>
> Wasn't offended, just saddened that all the hard work being done to create a
> free and open driver that Just Works gets stomped on because it made it
> harder to install a 3rd-party binary blob. :)

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Axel.Thimm at ATrpms

Nov 27, 2009, 9:14 AM

Post #9 of 11 (1387 views)
Permalink

Re: Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

Hi,

On Thu, Nov 26, 2009 at 10:17:12PM -0500, Jarod Wilson wrote:
> >>>>As many pointed out, adding "nouveau.modeset=0" at the end of
> >>>>the kernel line in grub.conf is the solution.
> >>>
> >>>Its not. And nouveau.modeset=0 isn't strictly required. If you
> >>>have the nouveau module blacklisted, a newly built initrd won't
> >>>include the nouveau module, and you can boot w/o any extra
> >>>params.
> >>
> >>I have this stanza in /etc/modprobe.d/blacklist.conf: blacklist
> >>nouveau
> >>
> >>That did not help me until I actually added the kernel parameter
> >>in grub.conf. I did reboot.

> >Same here..I had to recompile the kernel (initrd) without
> >rivafb/nvidiafb and then the Nvidia driver started to work
>
> Um. Just for the record, building a new initrd is nothing even
> *close* to "recompile the kernel". A new initrd is just a compressed
> image of stuff that is either scripts or already compiled.
> Recompiling the kernel involves building a new kernel from source
> code. Very very different things.

Just as a mini-howto: If one wants to rebuild the initrd for a
packaged kernel and make sure it is done exactly the same way the
Fedora/RHEL/etc. package did it, just look at the new-kernel-pkg of
rpm -q --qf '%{postin}\n' kernel gives, for example

[...]
/sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --install 2.6.31.5-127.fc12.x86_64 || exit $?
[...]

Copy and paste this into your root's console. It does the mkinitrd and
other stuff.
--
Axel.Thimm at ATrpms.net

promac at gmail

Nov 29, 2009, 1:54 AM

Post #10 of 11 (1303 views)
Permalink

Re: [ATrpms-users] Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On Sat, Nov 28, 2009 at 10:39 PM, O&M Ugarcina <mo.ucina [at] gmail> wrote:

> Hello Guys,
>
> I have just done a Fedora 10 to Fedora 12 upgrade myself . Tried with
> preupgrade , as I did on my other machine , but on my mythbox it failed .
> Tried it twice but it failed both times just after the reboot phase saying
> something like preupgrade has encountered a unexpected failure etc... So
> then I had to go with the yum method . With the yum method because of the
> changes to the rpms done in fedora 12 , I could not go to 12 directly ,
> needed to go to 11 first . Going to 11 was smooth , just needed to remove
> Numeric due to dep issues . Once at 11 could not get nvidia to come up and
> had to blacklist nouveau and remake the inittrd . Tried preupgrade again ,
> but it failed at exactly same spot as before . Then did yum upgrade again
> from 11 to 12 . The only dep issue was tigervnc that I uninstalled and once
> at 12 put back in again . With fedora 12 I had a bit of an issue with nvidia
> not starting up . I thought that it was our nouveau friend again , but it
> turned out that the kernel had run out of memory and I had to vmalloc some
> more , to be on the safe side I doubled the initial allocation and set
> vmalloc to 256M . I guess there is more stuff to load in fed 12 . The only
> thing that has stopped working for me on fed 12 is spdif sound , but that is
> a subject for another thread .
>
>
This is a different subject, but this message is related to your sound
problem, I guess:

http://www.gossamer-threads.com/lists/mythtv/commits/409905

I have exactly the same problem. Fedora 12 clean install and no analog sound
in myth.
Everything had sound but myth. In your case is the spdif,
but maybe the solution still applies.

This is how I got my sound back:

1) I added to /etc/asound.conf

"~/.asoundrc"

#
# Place your global alsa-lib configuration here...
#

@hooks [
{
func load
files [
"/etc/alsa/pulse-default.conf"
"~/.asoundrc"
]
errors false
}
]

2) I added to my ~/.asounrc

pcm.nopulse {
type hw
card 0
}

ctl.nopulse {
type hw
card 0
}

3) I used ALSA:nopulse for *sound* and mixer devices in mythfrontend setup.

4) In mythsetup, I have to use /dev/dsp for my capture card. Otherwise,
I cannot change channels (live tv aborts). This implies in uncommenting
the single line in dist-oss.conf and rebooting.

I hope this helps.

--
Paulo Roma Cavalcanti
LCG - UFRJ

ndylist at gmail

Dec 29, 2009, 3:46 PM

Post #11 of 11 (1000 views)
Permalink

Re: Updated from fedora 10 to 12 and have issues with nvidia driver loading [In reply to]

On Fri, Nov 27, 2009 at 6:14 PM, Axel Thimm <Axel.Thimm [at] atrpms> wrote:

> Hi,
>
> On Thu, Nov 26, 2009 at 10:17:12PM -0500, Jarod Wilson wrote:
> > >>>>As many pointed out, adding "nouveau.modeset=0" at the end of
> > >>>>the kernel line in grub.conf is the solution.
> > >>>
> > >>>Its not. And nouveau.modeset=0 isn't strictly required. If you
> > >>>have the nouveau module blacklisted, a newly built initrd won't
> > >>>include the nouveau module, and you can boot w/o any extra
> > >>>params.
> > >>
> > >>I have this stanza in /etc/modprobe.d/blacklist.conf: blacklist
> > >>nouveau
> > >>
> > >>That did not help me until I actually added the kernel parameter
> > >>in grub.conf. I did reboot.
>
> > >Same here..I had to recompile the kernel (initrd) without
> > >rivafb/nvidiafb and then the Nvidia driver started to work
> >
> > Um. Just for the record, building a new initrd is nothing even
> > *close* to "recompile the kernel". A new initrd is just a compressed
> > image of stuff that is either scripts or already compiled.
> > Recompiling the kernel involves building a new kernel from source
> > code. Very very different things.
>
> Just as a mini-howto: If one wants to rebuild the initrd for a
> packaged kernel and make sure it is done exactly the same way the
> Fedora/RHEL/etc. package did it, just look at the new-kernel-pkg of
> rpm -q --qf '%{postin}\n' kernel gives, for example
>
> [...]
> /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
> --install 2.6.31.5-127.fc12.x86_64 || exit $?
> [...]
>
> Copy and paste this into your root's console. It does the mkinitrd and
> other stuff.
>

I tried the mentioned method of using adding a blacklist nouveau and running
new-kernel-pkg on a new mythtv 0.22+Fedora 12+atrpms system. It did prevent
the nouveau driver from being loaded, but for some unknown reason, the
nvidia driver did not try to load at all. Earlier, before using the
"minihowto", the nvidia driver tried to load but failed due to the nouveau
driver.

I have reinstalled and tried the nouveau.modeset=0 and that just works
perfectly.

Inbetween I tried out Mythbuntu. It was easier to make the Nvidia driver run
(but not without bugs) (no need to disable any nouveau driver) but mythtv
did crash on updating my database scheme, so I went back to atrpms again
where the database scheme upgrade went smoothly.

Niels Dybdahl

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads