5:51 p.m.
I have rebuilt rpmfusion packages using nvidia 275.09.04 (beta) and confirm (as
many others have) that it fixes the problems with older versions on F15,
including konsole locking up the server, and corruption.
I have the packages built and would offer them to anyone who wants to try them,
but I don't have a public server to put them on.
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
6:11 p.m.
2011/6/10 Neal Becker <ndbecker2(a)gmail.com>:
I have rebuilt rpmfusion packages using nvidia 275.09.04 (beta) and
confirm (as
many others have) that it fixes the problems with older versions on F15,
including konsole locking up the server, and corruption.
Resize in KDE as indeed written as fixed in the driver changelog, that
been said this driver is still advertissed as beta. (The fix could
have been made in the stable driver branch).
So what I plan to do instead is to import the driver in rawhide and
request users affected by this bug to use akmod-nvidia from rawhide.
The other plan is to maintain another branch of the driver as
nvidia-latest or nvidia-beta (which branch already exists). to provide
another parallele driver.
The problem with the current beta driver is that it has also other issues:
http://www.nvnews.net/vbulletin/showthread.php?t=163213
Are you affected by this ?
Nicolas (kwizart)
6:17 p.m.
On Friday, June 10, 2011, Nicolas Chauvet wrote:
2011/6/10 Neal Becker <ndbecker2(a)gmail.com>:
> I have rebuilt rpmfusion packages using nvidia 275.09.04 (beta) and
> confirm (as many others have) that it fixes the problems with older
> versions on F15, including konsole locking up the server, and
> corruption.
Resize in KDE as indeed written as fixed in the driver changelog, that
been said this driver is still advertissed as beta. (The fix could
have been made in the stable driver branch).
So what I plan to do instead is to import the driver in rawhide and
request users affected by this bug to use akmod-nvidia from rawhide.
The other plan is to maintain another branch of the driver as
nvidia-latest or nvidia-beta (which branch already exists). to provide
another parallele driver.
The problem with the current beta driver is that it has also other issues:
http://www.nvnews.net/vbulletin/showthread.php?t=163213
Are you affected by this ?
Nicolas (kwizart)
So far no problems, but I'll keep testing
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
5:33 p.m.
On Fri, Jun 10, 2011 at 1:11 PM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
So what I plan to do instead is to import the driver in rawhide and
request users affected by this bug to use akmod-nvidia from rawhide.
The other plan is to maintain another branch of the driver as
nvidia-latest or nvidia-beta (which branch already exists). to provide
another parallele driver.
Sorry for the late reply, I was on vacation until today.
I have built some -beta packages successfully but have some
questions/observations:
1. I added a "Conflict:" for the non-beta package in the beta package.
I assume we'd need to do the opposite for the non-beta package?
2. There are a few places where the spec file differ significantly
from the template[1]. Specifically in the "buildforkernels" macros. I
as able to follow the wiki and get a new akmod package built but
there's a small typo on the wiki as well. In the macro definition it
should be "akmod" not "akmods" as that isn't a valid kmodtool
option.
3. On a related note, the --newest, --current, & --akmod options are
not shown in "kmodtool --help". Is this intentional?
Thanks,
Richard
[1] http://rpmfusion.org/Packaging/KernelModules/Kmods2
1:19 p.m.
FYI, an official 275.09.07 is released.
On Tuesday, June 14, 2011, Richard Shaw wrote:
On Fri, Jun 10, 2011 at 1:11 PM, Nicolas Chauvet
<kwizart(a)gmail.com> wrote:
> So what I plan to do instead is to import the driver in rawhide and
> request users affected by this bug to use akmod-nvidia from rawhide.
> The other plan is to maintain another branch of the driver as
> nvidia-latest or nvidia-beta (which branch already exists). to provide
> another parallele driver.
Sorry for the late reply, I was on vacation until today.
I have built some -beta packages successfully but have some
questions/observations:
1. I added a "Conflict:" for the non-beta package in the beta package.
I assume we'd need to do the opposite for the non-beta package?
2. There are a few places where the spec file differ significantly
from the template[1]. Specifically in the "buildforkernels" macros. I
as able to follow the wiki and get a new akmod package built but
there's a small typo on the wiki as well. In the macro definition it
should be "akmod" not "akmods" as that isn't a valid kmodtool
option.
3. On a related note, the --newest, --current, & --akmod options are
not shown in "kmodtool --help". Is this intentional?
Thanks,
Richard
[1] http://rpmfusion.org/Packaging/KernelModules/Kmods2
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
6:56 p.m.
W dniu 15.06.2011 15:19, Neal Becker pisze:
FYI, an official 275.09.07 is released.
On Tuesday, June 14, 2011, Richard Shaw wrote:
> On Fri, Jun 10, 2011 at 1:11 PM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
>> So what I plan to do instead is to import the driver in rawhide and
>> request users affected by this bug to use akmod-nvidia from rawhide.
>> The other plan is to maintain another branch of the driver as
>> nvidia-latest or nvidia-beta (which branch already exists). to provide
>> another parallele driver.
>
> Sorry for the late reply, I was on vacation until today.
>
> I have built some -beta packages successfully but have some
> questions/observations:
>
> 1. I added a "Conflict:" for the non-beta package in the beta package.
> I assume we'd need to do the opposite for the non-beta package?
> 2. There are a few places where the spec file differ significantly
> from the template[1]. Specifically in the "buildforkernels" macros. I
> as able to follow the wiki and get a new akmod package built but
> there's a small typo on the wiki as well. In the macro definition it
> should be "akmod" not "akmods" as that isn't a valid kmodtool
option.
> 3. On a related note, the --newest, --current, & --akmod options are
> not shown in "kmodtool --help". Is this intentional?
>
> Thanks,
> Richard
>
> [1] http://rpmfusion.org/Packaging/KernelModules/Kmods2
It is built already AFAIK, just not pushed yet.
Julian
4910
days inactive
4915
days old
rpmfusion-developers@lists.rpmfusion.org
5 comments
4 participants
participants (4)
-
Julian Sikorski -
Neal Becker -
Nicolas Chauvet -
Richard Shaw