Difference between revisions of "Talk:Kernel Panics"

From ArchWiki
Jump to: navigation, search
(chroot instructions: new section)
Line 13: Line 13:
  
 
It would be nice to add that as a sort of countermeasure there is the possibility of add init=/bin/sh to the grub's kernel line in  order to quickly access the battlefield and solve some things without a rescue cd.
 
It would be nice to add that as a sort of countermeasure there is the possibility of add init=/bin/sh to the grub's kernel line in  order to quickly access the battlefield and solve some things without a rescue cd.
 +
 +
== chroot instructions ==
 +
 +
I'm having some troubles with a possible kernel panic.  I found this page disagrees with the actual [[Chroot]] page.  So while I procrastinate on my own problem and attempt to take a breather before all my hair falls out, I thought I would make this suggestion.  Either one of these pages should be updated to agree with each other. The [[Chroot]] article has a newer edit date so I tend to think it should be the standard.
 +
 +
 +
;[[Chroot]] article reads:
 +
<pre>
 +
mount -t proc proc proc/
 +
mount -t sysfs sys sys/
 +
mount -o bind /dev dev/
 +
</pre>
 +
 +
;[[Kernel Panics]] article reads:
 +
<pre>
 +
# mount -t proc none /mnt/proc
 +
# mount -t sysfs none /mnt/sys
 +
# mount --bind /dev /mnt/dev"
 +
</pre>
 +
 +
Perhaps the end result is equal or insignificant but it is a bit confusing for someone who has to read these articles, e.g. me.

Revision as of 09:19, 16 May 2011

How do I make computer automaticaly restart after kernel panic? Obsrv 22:53, 30 September 2008 (EDT)

http://www.google.com/search?hl=en&q=linux+restart+%22kernel+panic%22 --byte 20:28, 2 October 2008 (EDT)

Login Wrong

If one uses arch to login, the response to the mount command is "mount: only root can do that". You might want to try root instead. - KitchM 00:14, 22 October 2009 (EDT)

Kernel ID

Need to explain how to identify the last kernel used. - KitchM 00:38, 22 October 2009 (EDT)

"Recovery Console" evolved

It would be nice to add that as a sort of countermeasure there is the possibility of add init=/bin/sh to the grub's kernel line in order to quickly access the battlefield and solve some things without a rescue cd.

chroot instructions

I'm having some troubles with a possible kernel panic. I found this page disagrees with the actual Chroot page. So while I procrastinate on my own problem and attempt to take a breather before all my hair falls out, I thought I would make this suggestion. Either one of these pages should be updated to agree with each other. The Chroot article has a newer edit date so I tend to think it should be the standard.


Chroot article reads
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
Kernel Panics article reads
# mount -t proc none /mnt/proc
# mount -t sysfs none /mnt/sys
# mount --bind /dev /mnt/dev"

Perhaps the end result is equal or insignificant but it is a bit confusing for someone who has to read these articles, e.g. me.