--- Adam Jackson <ajackson(a)redhat.com> wrote:
> 1) this is pretty serious as vtty's are often
handy to
> kill off procs in X that lock up the server.
Meh. If you have a process that does that, it's
preferable that the
process gets fixed, rather than working around it.
Not that I don't
understand the appeal, just that you're treating the
symptom not the
disease.
no i'm trying to keep a system - and my X apps up and
running after an errant app has locked things up.
> 2) during boot we can go from X to vtty showing
boot
> details with that graphical border just fine so it
> should be possible - right ?
If you're referring to the screen you get when you
click "Show Details"
or whatever during rhgb, then no, that's not text
mode. That's a vte
widget embedded into the rhgb process' window.
ah - ok. thought it was a text-mode / framebuffer
like thing (like for penguin icons durring boot).
... The workaround
was to disable the
"extended" save/restore bits for some cards. (Yes,
in a generic driver.
God I hate vesa.) I'll see if doing the same for
R500 works.
I'll be happy to test it too ;)
In the meantime, doing "vbetool post" once you've
switched back to text
mode might work, but might also break X horribly.
Try it and see!
it works - i can see all my text-mode lines again!!!
thank you
das
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com