William Poaster wrote:
> Kelsey Bjarnason wrote:
>
>> [snips]
>>
>> On Mon, 14 Jan 2008 03:31:42 -0500, Moshe Goldfarb wrote:
>>
>>> Well I can't speak for Kubutu but I spent 4 hours trying to get Ubuntu to
>>> work on a friends system.
>>> He has onboard video but has it disabled because he has a high end video
>>> card which is Nvidia based.
>>
>> Exactly the same setup I have here on this machine, plus two more at home.
>
> I have high end nVIDIA cards in the other machines, running Mandriva,
> Kubuntu, etc. Installed the drivers, no problem. :-)
>
>>> Fsking ubuntu misconfigures everything because it's not smart enough to
>>> see the onboard video disabled in the BIOS.
>>
>> Yet when I've installed Ubuntu in just the setups you describe, they have
>> never had this problem, leading me to conclude you're simply a troll.
>
> And an incompetent one at that.
>
>> HTH. HAND.
The experiences can vary drastically based on the specific hardware, and
revision of the hardware. Sometimes Linux does detect devices disabled
in the BIOS. There are so many combinations of PC hardware and firmware
that it leads to a lot of different experiences with Linux, and it
doesn't mean that everyone is a troll.
Ubuntu's restricted driver manager had a frustrating bug on my system.
It used a newer driver than my hardware supported. The result was that
the nv (Xorg) driver would initialize some state, and the nvidia
(proprietary) driver would work, and give acceleration, until a cold
boot. So you can imagine how frustrating that was to diagnose.
I tried to use the same driver as the Nvidia installer from their
website, and it wouldn't even allow me to. So I have to use a legacy
driver, which is what the restricted driver manager should have done.
The legacy Nvidia driver works fine, when installed with the Nvidia
installer, and the kernel module loaded with insmod. Since this problem
I've learned I'm not alone with experiencing this problem with the
restricted driver manager.
George
|
|
