Mailing List Archive: atrpms: users

Updated from fedora 10 to 12 and have issues with nvidia driver loading

Index | Next | Previous | View Threaded

gaberubin at gmail

Nov 25, 2009, 3:11 PM

Post #1 of 7 (2074 views)
Permalink

Updated from fedora 10 to 12 and have issues with nvidia driver loading

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 removed all nvidia stuff and reinstalled it,
including the kmdl, and still get this in my Xorg log:
(EE) Nov 25 15:07:10 NVIDIA(0): Failed to initialize the NVIDIA kernel
module. Please see the
(EE) Nov 25 15:07:10 NVIDIA(0): system's kernel log for additional
error messages and
(EE) Nov 25 15:07:10 NVIDIA(0): consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.

and this in dmesg:
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!

It hangs after the visual start-up of fedora (with the tear drop filling).

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

gaberubin at gmail

Nov 25, 2009, 6:31 PM

Post #2 of 7 (2027 views)
Permalink

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

I have continued trying to fix this issue. I rolled back to
nvidia-graphics version 173_14_22.

I realized part of my problem was that edits were being made to
/etc/modprobe.conf and that apparently is no longer used in fedora 12.
I removed that file and made edits to /etc/modprobe.d/local.conf and
have these lines in there:
alias char-major-195 nvidia-173_14_22
alias nvidia nvidia-173_14_22

I still get the same errors in my xorg log and dmesg with the addition
of this line in dmesg: [drm] nouveau 0000:01:00.0: Setting dpms mode 1
on tmds encoder (output 2)

I have tried manually loading the nvidia driver by doing a modprobe
nvidia and get this error:
FATAL: Error inserting nvidia_173_14_22
(/lib/modules/2.6.31.5-127.fc12.i686/updates/drivers/video/nvidia/nvidia-173_14_22.ko):
No such device

However, I do have that file:
[root [at] localhos ~]# locate nvidia-173_14_22.ko
/lib/modules/2.6.31.5-127.fc12.i686/updates/drivers/video/nvidia/nvidia-173_14_22.ko

Any ideas what is going on here?

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

kim+j2 at alleroedderne

Nov 26, 2009, 2:10 AM

Post #3 of 7 (2034 views)
Permalink

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

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

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

gaberubin at gmail

Nov 26, 2009, 9:08 AM

Post #4 of 7 (2022 views)
Permalink

Re: 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.

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

Axel.Thimm at ATrpms

Nov 27, 2009, 9:14 AM

Post #5 of 7 (2006 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

mo.ucina at gmail

Nov 28, 2009, 4:39 PM

Post #6 of 7 (1971 views)
Permalink

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

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 .

Best Regards

Milorad

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

promac at gmail

Nov 29, 2009, 1:54 AM

Post #7 of 7 (1972 views)
Permalink

Re: 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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads