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: alex stone <compose59@xxxxxxxxx>
- Date: Tue, 13 Oct 2009 12:21:50 +0400
- 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=BT0q9xMcwTMaUdPWkjm/7wrdMqmbztVlji3IAV2hGdE=; b=jTf5O8wWusbC62jC+Yskr6/ClMSS9Te0nd3BQ0Rrv7cyvvBXXKuSdvUM6vmDJY1R1y OO86Rw4rH2+J488Z3K2ZbVpis0XF5q9Q1+LXmBaCkVp+rbEhIV2JypWG6osIzZGrQCud +RtUqlzxBzaqSoNgZ8/yj9iVv64QYRSy5EGuo=
- 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=pEsK8+SejlbbmvAjracmaBk0C4tzeWjS8WZyZiPx/kKdVj1keR+C1BhF22R3QWX6wq s91CZsPQcWh3CLvaiMWtb2ZAvlQ310/8bLAVtRNUmLBEXIGQK/yZs0UVTymFBFb5pmZ4 wyGBElOymN2xI+xtCsSk1CbgxpzMFj2uNrGPw=
Arve, after testing 2.6.31.1-rt (built from vanilla, and rt patch),
and 2.6.31.2 with rt patches, i recommend you use 2.6.31.2 to build up
a kernel.
2.6.31.1 had a bug with usb drivers, preventing usb devices from
re-igniting. the 2.6.31.2 vanilla kernel doesn't suffer with this bug.
(Lots of mouse freezing, and usb midi keyboard dropout with 2.6.31.1-rt)
Good luck, and thanks again to Lucio, who's patch works fine here too,
after a few days solid testing.
I share the view the Nvidia driver with Lucio's patch could go in the
overlay, at least until the nvidia drivers have caught up.
Alex.
On Tue, Oct 13, 2009 at 10:38 AM, Arve Barsnes <arve.barsnes@xxxxxxxxx> wrote:
> Just tried updating to a .31-kernel myself yesterday and ran into this
> same problem. Had to go back to the old kernel, but then I remembered
> this thread. The ebuild seems to work perfectly Lucio, and I can't
> wait to get back home to try out the new kernel!
>
> Arve
>
>
>
--
www.openoctave.org
midi-subscribe@xxxxxxxxxxxxxx
development-subscribe@xxxxxxxxxxxxxx