PDA

View Full Version : Proprietary Driver Managment is aweful



beattyml1
February 22nd, 2009, 05:10 PM
I would really like to know why on earth the proprietary driver manager works the way it does.

In 8.04 using the proprietary driver manager my graphics worked ok, but then I upgraded to 8.10 and every thing just stopped working, apparently they had switched to a new beta version of the driver. Does anyone else out there feel like the driver manager should always use the most recent final release driver available, and actually update it as updates come out.

Not that I don't appreciate what the developers do it just seems like using a beta driver that doesn't work when previous drivers work doesn't seem very logical, and updating drivers as they come out seems like the logical choice.

cb951303
February 22nd, 2009, 05:13 PM
AFAIK 177 was stable when 8.10 was released.

EDIT: Sorry you have an ATI card

Skripka
February 22nd, 2009, 05:20 PM
I would really like to know why on earth the proprietary driver manager works the way it does.

In 8.04 using the proprietary driver manager my graphics worked ok, but then I upgraded to 8.10 and every thing just stopped working, apparently they had switched to a new beta version of the driver. Does anyone else out there feel like the driver manager should always use the most recent final release driver available, and actually update it as updates come out.

Not that I don't appreciate what the developers do it just seems like using a beta driver that doesn't work when previous drivers work doesn't seem very logical, and updating drivers as they come out seems like the logical choice.

Just because a driver is a "final release" doesn't mean you want it on your machine. The 177.8 Nvidia driver had many many issues yet was old enough by Ubuntu's standards to be called "stable", yet it caused many headaches and problems. But it was called "stable".

Back in the good old days, ATi was known for it's final release drivers for windows being in fact beta quality.

beattyml1
February 22nd, 2009, 07:40 PM
My point was more that it should

A. Not use a Beta driver that doesn't work when a better stable driver is available

B. Update when a significantly better driver is offered rather than just leave people with whatever was the newest driver at ubuntu release

If they adopted either of these I would be satisfied, both would be great

I am sorry if this sounds like flaming as it was not meant as such, just a little bit of constructive criticism

igknighted
February 22nd, 2009, 07:56 PM
They shipped a beta driver because there was no final release from ATI that worked with the kernel in intrepid. What card do you have? Did it reach EOL?

EDIT: It was either the kernel or the xserver version, I forget which. Either way, the alternatives for Ubuntu were to stiffle its own development because ATI can't make a driver in time, or ship a beta release. I think you ship a beta release every time in the situation, because you can pass the final as an update.

sloggerkhan
February 22nd, 2009, 07:58 PM
Nice thing about ATI cards and their proprietary driver is that you can just download the latest driver and build debs for it.

Vince4Amy
February 22nd, 2009, 08:20 PM
Nice thing about ATI cards and their proprietary driver is that you can just download the latest driver and build debs for it.

It also just works on most distros so you can go through the Automatic installer. I recommend to never use the Restricted Manager on Ubuntu for drivers as it usually contains a really out of date version.

sloggerkhan
February 23rd, 2009, 07:17 AM
Also, if you follow an FGLRX install guie for ubuntu that doesn't use proprietary driver manager or have you make .deb files, the instructions are bad and out of date.

toupeiro
February 23rd, 2009, 07:20 AM
I would be fine if I could just find some better documentation on DKMS... I NEED to use proprietary drivers for some of the modeling I work with, and I would love to learn how to better use dkms to hook into kernel updates with a beta driver. I thought DKMS was a huge breakthrough for seamless kernel updates on GUI intensive linux installations, but its rather limited if you can only use it with a specific accompanying distro repository based driver.

sloggerkhan
February 23rd, 2009, 09:30 AM
DKMS has worked fine for me with the build deb options in the fglrx driver in the past. I haven't used my ATI based system nearly at all lately, but I seem to recall as long as you had a few basic build dependancies used by the DKMS system installed things went fine.

beattyml1
February 26th, 2009, 08:45 PM
I just wish that it would change what driver it used if the one it used didn't work and one that does work comes out, I've heard all the stuff about just do it yourself but every time I try it seems to mess up my computer.
Once again may I restate that I greatly appreciate what the dev's do I am just pointing out somewhere where ubuntu needs to grow if it is to get any reasonable market share, and yes I do realize that the primary blame lies with ATI, which is why I plan to get an nVidia card. :)

PS part of me wishes I hadn't started this thread, and I shall probably never make another cafe post without waiting at least a few hours after I get up.