| 1 |
On Mon, Jan 18, 2010 at 12:47 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
|
| 3 |
> James Ausmus wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>> |
| 7 |
>> On Mon, Jan 18, 2010 at 11:59 AM, Dale <rdalek1967@×××××.com <mailto: |
| 8 |
>> rdalek1967@×××××.com>> wrote: |
| 9 |
>> <snip> |
| 10 |
>> |
| 11 |
>> That was my problem, no keyboard or mouse. Sort of hard to do |
| 12 |
>> much in that situation. |
| 13 |
>> Dale |
| 14 |
>> |
| 15 |
>> |
| 16 |
>> Pshaw... ;) |
| 17 |
>> |
| 18 |
>> <ctrl>-<alt>-<F1>, or, if that doesn't work: |
| 19 |
>> |
| 20 |
>> <alt>-<SysRq>-R |
| 21 |
>> <alt>-<F1> |
| 22 |
>> |
| 23 |
>> Of course, method 2 only works if you have the "Magic SysRq keys" (or |
| 24 |
>> whatever it's called) option enabled in the kernel, and not enough people |
| 25 |
>> know about the Magic SysRq keys at this point... |
| 26 |
>> |
| 27 |
>> -James |
| 28 |
>> |
| 29 |
> |
| 30 |
> In that case, ctrl alt F1 does nothing. You also need to understand that |
| 31 |
> most people don't even know how to use SysRq keys. |
| 32 |
|
| 33 |
<snip> |
| 34 |
|
| 35 |
I know, I just felt like being a smart-ass... ;) |
| 36 |
|
| 37 |
|
| 38 |
> I didn't and had to do a hard shutdown. I had to actually pull the plug to |
| 39 |
> do any good. Luckily I knew how to get it to boot into single user mode so |
| 40 |
> I could disable hal otherwise I would be right back on the same screen again |
| 41 |
> with no mouse or keyboard. |
| 42 |
|
| 43 |
<snip> |
| 44 |
|
| 45 |
Another option (I know - too late for you, but might be useful for someone |
| 46 |
that runs across this on Google), is to press I during the initscript |
| 47 |
processes - enters "Interactive Boot" mode, so you can Y/N individual |
| 48 |
startup scripts, including xdm/X |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
> It would be really bad if even that didn't work with devicekit. I'm not |
| 53 |
> sure how it couldn't but we never know do we? |
| 54 |
> |
| 55 |
<snip> |
| 56 |
|
| 57 |
I agree - there has been a lot of churn with X/HAL/udev/input devices over |
| 58 |
the past year or so, and it's really bitten some people badly, certainly not |
| 59 |
an ideal situation, and the DeviceKit migration really should be tested more |
| 60 |
thoroughly, in more combinations, than some of the other changes have been. |
| 61 |
However, the only real way it will get tested in more combinations is if we, |
| 62 |
the users, try it out early and often, and let the Gentoo devs and/or |
| 63 |
upstream devs know when we run into problems - anybody who specifically had |
| 64 |
issues with input devices using HAL would probably be a *very* useful test |
| 65 |
data point, as they most likely have SW/config/HW combinations that upstream |
| 66 |
specifically does *not* have - as evidenced by the fact that it broke |
| 67 |
previously... ;) |
| 68 |
|
| 69 |
|
| 70 |
|
| 71 |
> |
| 72 |
> I could work around it if needed but some other user may not can. What if |
| 73 |
> that hard shutdown corrupts a file system and causes data loss? I'm not |
| 74 |
> just wanting it to work better for me but for others who use Linux and know |
| 75 |
> even less than I do. |
| 76 |
> Dale |
| 77 |
> |
| 78 |
|
| 79 |
And this is why it is a Very Good Thing to spread the word about the Magic |
| 80 |
SysRq keys. Did <ctrl>-<alt>-<del> not do anything, or a single press of the |
| 81 |
power button (which should send an ACPI shutdown signal, causing the system |
| 82 |
to self-power-off)? |
| 83 |
|
| 84 |
|
| 85 |
I'll try to stop being a smart-ass, but it's just one of those kind of |
| 86 |
days... <grin> |
| 87 |
|
| 88 |
-James |
Archives