[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 #151 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to Christopher from comment #148)

Hi Christopher, 

> Behavior is indeed different. Before it would either fail with a nonblinking
> cursor, fail with a blinking cursor, or not last long enough to get out of
> text mode.
> 
> I will try and boot it again (I rebooted to save the driver progress, so
> that I wouldn't have to compile it *again* and the image is what I got upon
> it coming back up and trying to GUI) and see if it can be caught and
> CTRL+ALT+BKSP'd before everything packs up and goes away.
> 
> If I can't do that, I will have to reinstall a different way, compile the
> driver all over again, and get the files that way... the way it's installed
> now it runs in RAM which is bad for crash reports but better for the drive
> I'm using in it -- an SD card in an IDE adapter. (Hey, it fits in the
> housing! A 2.5" drive would not, and the system does not have enough oomph
> to spin up a mechanical hard drive of any kind.)
> 
> We'll see what happens. I'll keep you posted :)

I will say that based on dealing with OpenChrome for a while, when my Lubuntu
12.04 i386 boots back from hibernation, it does display some junk on the screen
somewhat similar to what you saw.
Of course, I do not like this, and I plan to remedy this down the road (at this
point, it is a low priority since it is not a fatal bug).
I would imagine it is merely displaying whatever in the RAM considering that we
are dealing with an integrated graphics based system here.
When the computer boots up, the RAM that was not really used during the boot up
is undefined.
DRAM (Dynamic RAM) used for pretty much all computer working memory requires
constant refreshing (i.e., one refresh command per 7.8 micro seconds typical
for recent DRAM devices) to maintain the stored contents.
If a refresh command was not issued for a while (i.e., not maintaining one
refresh command per 7.8 micro seconds average), than the contents of the RAM
can change randomly (i.e., DRAM is made out of capacitors, and capacitors leak
charge).

Regards,

Kevin Brace

-- 
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/20160125/62de7708/attachment-0001.html>