[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91966

--- Comment #161 from Christopher <laserhawk64 at gmail.com> ---
I did some research and came across a PDF from Dell (which now owns WYSE)
referring to the C10LE -- one of several Cx0 models, the differences between
which being capacities of RAM and internal storage as well as preinstalled OS.

It does explicitly refer to the system as having up to 32bpp bit depth, so I
sit corrected :)

I should also note that my HP t5630w (which carries the same motherboard, CPU,
and chipset as the t5145, t5540, t5545, and t5630 non-w)which is an entirely
different offering of course -- it has the same CPU as this dang WYSE thing,
but a VX800 chipset instead of the VX855. It works almost flawlessly with
openchrome. It's a little slow to bring up the display (sequence is -- screen
of gunk > black screen + console cursor > black screen + console and mouse
cursors > full desktop, with ghost of console cursor remaining) but it DOES
work. I suspect that the plodding-ness of it is the CPU rather than the
chipset... VIA CPUs just kind of suck.

Last thing. The full install display fail went a little differently. No screen
full of junk -- it went to a black screen w/ blinking cursor, then a black
screen w/o cursor.

Get yourself a Bluetooth keyboard for that tablet :P they're cheap on eBay I
hear... or, better yet, get an ASUS netbook. I personally can recommend the
ASUS 1000HE -- I've had mine since 2009 and it's been positively amazing.

You might find this page useful on the WYSE Cx0 series and what it can do -->
http://www.parkytowers.me.uk/thin/wyse/cx0/index.shtml
...and this simpler one on the HPs I mentioned -->
http://www.parkytowers.me.uk/thin/hp/t5540/index.shtml

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-devel/attachments/20160126/1c1c54e9/attachment-0001.html>