[SOLVED]Ubuntu reposts graphics driver unknown

[PerseP]

Hi,
Ive installed ubuntu 1204 32 desktop without problems and when I go to System Settings -> Details, it says graphics oracle vm virtualbox vbe adapter.
But when I install the virtual guest additions with the iso they install ok and then it reports the graphics driver as unknown.

Does anybody why it can read the correct driver any more?

My host if window 7 64 with virtualbox 4.3.10 rc93012

[mpack]

The guest additions provide a different (higher performance) driver, and it doesn't correspond to a specific chipset - hence "unknown". If you install the GAs then you don't need to care about the graphics hardware or drivers.

[PerseP]

The guest additions provide a different (higher performance) driver, and it doesn't correspond to a specific chipset - hence "unknown". If you install the GAs then you don't need to care about the graphics hardware or drivers.

Can't the GA driver at least return a string with a name,ie 'VirtualBox Driver'

[mpack]

Moving this discussion to "Linux Guests" since it's off topic in "Windows Hosts".

If you mean, can the driver identify itself: it does, at least on Windows guests - I don't use 64bit Linux guests. Obviously it can't claim to have a chipset it doesn't have, as apps might expect to be able to use features of that chipset. Think of it this way: there is no chipset, your graphics are being rendered by a separate PC, so an "unknown" chipset sounds correct.

Why do you care anyway? If you're expecting to be able to run GPU code in a VM then I'm afraid you'll be disappointed.

[PerseP]

Because it's a modification that the guest additions does over the operating system

[PerseP]

The only way in my system to get the graphics driver name was by using:

Code: Select all

/usr/lib/nux/unity_support_test -p

After more research I tried installing:

Code: Select all

apt-get install mesa-utils

And then I did get the same driver name in both unity_support_test and System Settings. It was always my understanding that the name of the driver was given by the driver itself and not the os.

Here is some more explanation.