Akemi Yagi wrote:
> On Fri, Oct 8, 2010 at 1:00 PM, James A. Peltier wrote:
>
>> You can also use the nVidia driver package as part of rpmforge or
>> rpmfusion which uses DKMS to build the driver for you on each reboot.
>
> You don't have to build for each kernel update if you use kernel
> versi
On Fri, Oct 8, 2010 at 1:00 PM, James A. Peltier wrote:
> You can also use the nVidia driver package as part of rpmforge or
> rpmfusion which uses DKMS to build the driver for you on each reboot.
You don't have to build for each kernel update if you use kernel
version independent, kABI-trackin
- Original Message -
| James A. Peltier wrote:
| >
| > - Original Message -
| > | James A. Peltier wrote:
| > | > This is a known issue. The next proprietary ATI driver is due to
| > | > be
| > | > released sometime next month and will correct it.
| > | >
| > | Oh, *great*. So I w
Todd Denniston wrote:
> m.r...@5-cent.us wrote, On 10/08/2010 02:55 PM:
>> James A. Peltier wrote:
>>> This is a known issue. The next proprietary ATI driver is due to be
>>> released sometime next month and will correct it.
>>>
>> Oh, *great*. So I wait a month before I can get his system running
James A. Peltier wrote:
>
> - Original Message -
> | James A. Peltier wrote:
> | > This is a known issue. The next proprietary ATI driver is due to be
> | > released sometime next month and will correct it.
> | >
> | Oh, *great*. So I wait a month before I can get his system running a
> | s
m.r...@5-cent.us wrote, On 10/08/2010 02:55 PM:
> James A. Peltier wrote:
>> This is a known issue. The next proprietary ATI driver is due to be
>> released sometime next month and will correct it.
>>
> Oh, *great*. So I wait a month before I can get his system running a
> security-fixed kernel...
No problem. It was 6 hours of troubleshooting for me. This is certainly why I
hate proprietary drivers. I haven't had any problems with nVidia that I can
recall.
- Original Message -
| James A. Peltier wrote:
| > This is a known issue. The next proprietary ATI driver is due to be
| >
James A. Peltier wrote:
> This is a known issue. The next proprietary ATI driver is due to be
> released sometime next month and will correct it.
>
Oh, *great*. So I wait a month before I can get his system running a
security-fixed kernel
Btw, while I was waiting for a reply, I created an acc
BTW: If you choose the previous kernel entry, build the driver you will see
that it built fine. The issue is that some functions were removed/renamed in
the latest kernel update that the driver uses.
- Original Message -
| Upgraded the kernel to the latest, then tried to rebuild the
|
This is a known issue. The next proprietary ATI driver is due to be released
sometime next month and will correct it.
- Original Message -
| Upgraded the kernel to the latest, then tried to rebuild the
| proprietary
| Catalyst driver for a Radeon HD 4550 on a Dell Optiplex 980.
|
| The
Upgraded the kernel to the latest, then tried to rebuild the proprietary
Catalyst driver for a Radeon HD 4550 on a Dell Optiplex 980.
The install dies, with a c error. Anyone else out there succeed in
building one on the 2.6.18-194.17.1.el5-x86_64 kernel? I went to the ATI
website, and the "instal
11 matches
Mail list logo