Re: [proaudio] failed nvidia drivers. |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] failed nvidia drivers.
- From: Arve Barsnes <arve.barsnes@xxxxxxxxx>
- Date: Wed, 7 Oct 2009 06:21:26 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Vp2iOGAoic307+PuH9lBs5KXHmGw9EcFJV7uIdx6Iio=; b=gWVsXbolFKVWtzKeeppFxxoZaW0vULov5UvH+L2ZFQCBJ9DXwW2sqGXnM0x269zKSc Y7KouLxS8ESI2k5Cyt0vN7f+HEPjMhSa2u+GgOLPSwqT/nyQuMoXKCMlaFZRHwt4eFMh ErDleJKc7SegZBpvhExQK82+YgJjXjITEpHf0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=cziyGP++VINV/YFAqD5Qq60UYlvEfgHAW93caFangtVMy6JAatEwYoCzZwQljNE7kY pNxhXdslRjtqmFHA1emqYa+F+BQf82ax0hZzKDh99dcr40oNOJ3n/CpDCEyGb3ra64xt 1pjAIi6/rRJuoX+fgjtETg6xM+oLYo4xkEohw=
Have you done a module-rebuild after upgrading kernel and/or nvidia-drivers?
On Tue, Oct 6, 2009 at 11:52 PM, alex stone <compose59@xxxxxxxxx> wrote:
> Lucio,
> It didn't work for me. The build process seemed to go ok, but i got
> the usual nvidia fatal not found error when o rebooted, after doing
> all the usual stuff, and i'm not sure i followed the 3rd party ebuild
> thing correctly, so i can't say with certainty what the error might
> be. (I'm only a user, not a coder.)
>
>
> Thanks for trying to help out
>
> Alex.
>
> On Tue, Oct 6, 2009 at 10:36 PM, Lucio Asnaghi <kunitoki@xxxxxxxxx> wrote:
>> I had to patch the nvidia drivers to compile them on 2.6.31-rt11 so i've
>> uploaded an ebuild in my roxxorx overlay (search it in google code)
>>
>> Cheers
>>
>> Lucio
>>
>>
>> On 06/ott/09, at 20:06, Vladimir Savic <vladimir.firefly.savic@xxxxxxxxx>
>> wrote:
>>
>>> Works fine for me. AMD64 arch with nvidia 8600GT card.
>>>
>>> $ uname -a
>>> Linux savichome 2.6.31-gentoo #1 SMP PREEMPT RT Mon Sep 21 01:54:34 CEST
>>> 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AuthenticAMD
>>> GNU/Linux
>>>
>>> For simplicity sake, I'll attach patch file to this mail. Patch was
>>> grabbed from nvnews nvidia forums. That means I'm not author of the same.
>>>
>>> Hopefully someone can make ebuild since I haven't had a single crash for
>>> days (weeks even).
>>>
>>> Vlada
>>>
>>> P.S. "2.6.31-gentoo" in uname output is misleading, but it is -rt11
>>> kernel. I just haven't changed Makefile.
>>>
>>>
>>> alex stone wrote:
>>>>
>>>> A quick heads up for the powers to be in the overlay.
>>>>
>>>> Had a weekend of experimenting with a 2.6.31.1-rt11 vanilla kernel
>>>> build, and as i've come to expect, the nvidia drivers ebuilds (all of
>>>> them) failed miserably against this build. This time around, it seems
>>>> to be something in the RT patch that messes the nvidia build up, but
>>>> more importantly to us mere audio users, xf86-video-nv doesn't work
>>>> either, and freezes the desktop. (And a quick google will reveal i'm
>>>> not the only one defaulting to vesa at this stage.)
>>>>
>>>> I've found a patch, that sadly didn't work for me, and more sadly, the
>>>> latest overlay RT build didn't work with the latest nvidia drivers
>>>> either.
>>>>
>>>> I'm still on 2.6.24-rt for good reason it seems, but time is running out.
>>>>
>>>> If anyone is trying this particular combination, you have an uphill
>>>> trek in front of you, so don't get discouraged if it doesn't work.
>>>> You're not on your own.
>>>>
>>>> A final question. Could the overlay maintainers ask the portage chaps
>>>> if they can have a look at the 190.xx nvidia-drivers series ebuilds,
>>>> and ask on my behalf if they could consider fixing the ebuilds to
>>>> satisfy an rt kernel build as well? (2.6.31 in particular)
>>>>
>>>> I've mailed them 3 times, and nobody seems to be home.
>>>>
>>>> Thanks,
>>>>
>>>> Alex.
>>>>
>>>>
>>>
>>> <nv-2.6.31-rt.patch.gz>
>>
>>
>>
>
>
>
> --
> www.openoctave.org
>
> midi-subscribe@xxxxxxxxxxxxxx
> development-subscribe@xxxxxxxxxxxxxx
>
>
>