From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about xorg and a kill process
Date: Wed, 27 May 2009 09:56:08 -0500 [thread overview]
Message-ID: <4A1D5488.1080400@gmail.com> (raw)
In-Reply-To: <4A1D4CAF.80508@alstadheim.priv.no>
Håkon Alstadheim wrote:
> Daniel da Veiga wrote:
>> On Wed, May 27, 2009 at 10:03, Dale <rdalek1967@gmail.com> wrote:
>>
>>> Hung Dang wrote:
>>>
>>>> I often use Ctrl+F1 to F6 to back to the command line and if your X is
>>>> fine you can back the X screen using Ctrl+F7. Or if you want to kill
>>>> your X then Ctrl+Alt+Backspace may be helpful.
>>>>
>>>> Hung
>>>>
>>>>
>>>> Dale wrote:
>>>>
>>>>> I know the subject is a bit lacking but here goes. I'm thinking
>>>>> about
>>>>> trying this xorg-server upgrade again. I been thinking about a
>>>>> way to
>>>>> do this and not have to pull the plug on my rig if it fails, which
>>>>> I bet
>>>>> it does. This is the command I am thinking about trying.
>>>>> /etc/init.d/xdm start && sleep 5m && /etc/init.d/xdm stop
>>>>>
>>>>> I'm thinking this way. Start X first. If it fails, it will stop
>>>>> in 5
>>>>> minutes and come back to a console. Think this will work? If xorg
>>>>> works, I can switch back to a console and ctrl C the command and
>>>>> carry on.
>>>>>
>>>>> Thoughts? Better ideas?
>>>>>
>>>>> Dale
>>>>>
>>>>> :-) :-)
>>>>>
>>>>>
>>> That won't work because if xorg-server fails, my keyboard doesn't work
>>> when I switch to X. If the keyboard doesn't work, I can't switch back
>>> to anything or type anything.
>>>
>>> I done been through this one time. I'm trying to figure out how to get
>>> back to console with a keyboard that doesn't work at all.
>>>
>>>
>>
>> Best way to do this is using a remote shell (SSH for example) in
>> another machine. If that's not an option or X driver fails in
>> conflicts with the kernel (mine did before I found a suitable config)
>> then you're pretty much lost, cause your video is gone for good.
>>
>> You can try SYSREQ combinations to kill the server and if that fails
>> even cleanly reboot the rig, but as I said before, depending on the
>> problem your video is gone.
>>
>>
> stick a "chvt 1" after the "xdm stop".
>
>
>
Did a man chvt and that is interesting. I got to add that to the
command just in case. ;-)
Thanks
Dale
:-) :-)
next prev parent reply other threads:[~2009-05-27 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 4:30 [gentoo-user] Question about xorg and a kill process Dale
2009-05-27 6:01 ` Hung Dang
2009-05-27 12:04 ` bn
2009-05-27 13:03 ` Dale
2009-05-27 14:16 ` Daniel da Veiga
2009-05-27 14:22 ` Håkon Alstadheim
2009-05-27 14:56 ` Dale [this message]
2009-05-27 15:01 ` Dale
2009-05-27 15:09 ` Neil Bothwick
2009-05-27 15:35 ` Dale
2009-05-28 10:51 ` Daniel Iliev
2009-05-27 14:26 ` Neil Bothwick
2009-05-27 14:58 ` Dale
2009-05-27 15:06 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A1D5488.1080400@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox