Michael Mol wrote:
On Sun, Dec 25, 2011 at 8:10 PM, Dale<rdalek1...@gmail.com> wrote:
Colleen Beamer wrote:
Thanks for this!
Regards,
Colleen
This may help too. This is from a post Neil made a long time ago:
[QUOTE]
Hold down Atl, hold down SysRq, press each of the keys in turn. The usual
full sequence is R-E-I-S-U-B
Reboot
Even
If
System
Utterly
Broken
[END QUOTE]
Don't forget to build support in the kernel too. I think this is the only
one needed:
root@fireball / # zcat /proc/config.gz | grep -i sysrq
CONFIG_MAGIC_SYSRQ=y
root@fireball / #
Usually I only get to about the E or I then I get a console. Getting the
processes sorted out is the hard part tho. At least you can do a clean
shutdown and reboot tho.
Hope that helps.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
Being that this is the third time the xorg drivers issue has cropped
up in the last week, I put together another blog post for it.
http://funnybutnot.wordpress.com/2011/12/25/xorg-updating-from-1-10-to-1-11-and-fixing-your-system/
This happens every time another version of xorg goes stable. I have to
admit, I forgot to recompile mine too. I noticed the upgrade but forgot
to re-emerge the drivers. I doubt this will change anytime soon
either. We are human and emerge doesn't do it automagically, yet.
Maybe I need to add that to my sig. lol
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
