| 1 |
2009/9/19 Mick <michaelkintzios@×××××.com>: |
| 2 |
> On Saturday 19 September 2009, meino.cramer@×××.de wrote: |
| 3 |
>> > cleaner shutdown. This is taken from a email that was sent to me during |
| 4 |
>> > that horrible xorg-server and hal upgrade. |
| 5 |
>> > |
| 6 |
>> > > Hold down Atl, hold down SysRq, press each of the keys in turn. The |
| 7 |
>> > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly |
| 8 |
>> > > Broken By ${DEITY} - this tagline picker is spooky at times :-O |
| 9 |
>> > > -- Neil Bothwick |
| 10 |
>> > |
| 11 |
>> > I tried this once when I was unable to get my keyboard to respond to |
| 12 |
>> > anything else. I made it through the first three or four and was |
| 13 |
>> > returned to a console with a working keyboard. Since you are shutting |
| 14 |
>> > down, you may want to go through them all to be safe. I think the last |
| 15 |
>> > one does a reboot. |
| 16 |
>> > |
| 17 |
>> > Hope that helps. |
| 18 |
>> > |
| 19 |
>> > Dale |
| 20 |
>> > |
| 21 |
>> > :-) :-) |
| 22 |
>> |
| 23 |
>> Hi Dale, |
| 24 |
>> |
| 25 |
>> thanks a lot for your help!!! :) |
| 26 |
>> |
| 27 |
>> This will help to bring donw the machine in an more |
| 28 |
>> cleaner way as simply pressing the power switch ;-) |
| 29 |
>> |
| 30 |
>> But: |
| 31 |
>> How can I figure out, what hangs the shutdown process itsself? |
| 32 |
> |
| 33 |
> Last time I came across a problem like this I had forgotten to select the |
| 34 |
> right chipset under Graphics support/AGP Support/ in the kernel. So I |
| 35 |
> suggest you revisit your kernel and xorg drivers setups for your card. |
| 36 |
> -- |
| 37 |
> Regards, |
| 38 |
> Mick |
| 39 |
> |
| 40 |
|
| 41 |
Hi, |
| 42 |
I got a similar problem too once... and what was making the system |
| 43 |
hang wasn't the last shutting down thing listed, but the one just |
| 44 |
after (so i don't think it's net.lo fault in your case). So i suggest |
| 45 |
to have a look at which services are started at boot, but aren't |
| 46 |
shutted down. Turning off parallel boot could help you find out the |
| 47 |
responsible service. |
| 48 |
In my case it was a misconfiguration of the alsa module, which |
| 49 |
shouldn't be unloaded at shotdown time... |
| 50 |
HTH |
| 51 |
Davide |
Archives