Opened 16 years ago

Closed 6 years ago

#2950 closed bug (invalid)

Vmware video driver dual Haiku screens

Reported by: kvdman Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

It seems that some of the latest revisions (in the last week), have done something to the Vmware video driver. Under Vmware Fusion and build 23813, there are two Haiku screens (see pic).

Removing the driver and using Vesa solves the problem, but the driver is much slower, and unstable (quitting BePDF will jump it into KDL).

Interestingly, the problem can't be duplicated in Virtual Box, as the Vmware video driver works fine there.

Attachments (1)

weirdgraphics.jpg (87.2 KB ) - added by kvdman 16 years ago.

Download all attachments as: .zip

Change History (7)

by kvdman, 16 years ago

Attachment: weirdgraphics.jpg added

comment:1 by kvdman, 16 years ago

Sorry, I meant rev. 28314.

comment:2 by umccullough, 16 years ago

A result of hrev28301.

see already-existing discussion here:

http://lists.berlios.de/pipermail/haiku-commits/2008-October/018143.html

I believe the consensus is (and has been for quite some time): Don't use that driver. It already had known problems anyway, for example making it nearly impossible to cope with a KDL.

VESA performance is pretty much already good enough in vmware anyhow, so the driver itself provides no real noticeable gain.

comment:3 by kvdman, 16 years ago

Thanks for the info, guess this should be left open, Stephan noted in the discussion that:

"it's a problem of not correctly implementing virtual_height in the driver".

And Axel said:

"Since we're in control of the sources, and the vmware driver currently isn't used because of other reasons, I would be against blacklisting, and rather spend the effort on fixing problematic drivers."

comment:4 by luroh, 9 years ago

Milestone: R1Unscheduled

Moving out of the R1 milestone.

comment:5 by axeld, 7 years ago

Owner: changed from axeld to nobody
Status: newassigned

comment:6 by waddlesplash, 6 years ago

Resolution: invalid
Status: assignedclosed

The VMware driver was outsourced some time ago.

Note: See TracTickets for help on using tickets.