You are not logged in.
Pages: 1
When I boot into Arch i get a prompt that looks like this "ramfs$". it gives me a message telling me to use echo * instead of ls, new to arch/linux so i don't really know whats going on. I can boot into my fallback with no problem, can log in and everything. Both of the images are in the same place:
initrd /kernel26.img=Arch Linux
initrd /kernel26-fallback.img=Arch fallback
I can use the fallback but i would like to know why Arch is doing this
thanks
Last edited by cplum (2008-05-28 04:35:32)
Offline
Without additional detail, the only answer is that kernel26.img is not correct for some reason. Boot with the fallback image, regenerate kernel26.img with mkinitcpio, and all will be well.
Offline
Check that you have the base udev and filesystem hook inbuild. Logs would also be good... Maybe taking out the autodetect hooks also helps (however this will slow down your boot time)
Offline
Can I scroll up or pause the boot messages so i can actually read them?
Offline
logs are located /var/log/
Offline
Check that you have the base udev and filesystem hook inbuild. Logs would also be good... Maybe taking out the autodetect hooks also helps (however this will slow down your boot time)
With the default configuration (ie if you didn't edit /etc/mkinitcpio.d/example.preset), the only difference between fallback and normal image is that in fallback the 'autodetect' hook is left out.
Offline
Whithout going into the logs yet, all i can read when it does boot, after it says its falling into a recovery shell, is that klibc contains no "ls" binary, use "echo *" instead. Then it says if the device "/dev/disk/by-uuid/ (big ass alpha nermeric #) is created here, try adding "rootdelay=8" or higher to the kernel command line ramfs$ scsi... etc
then if i hit any key it give me the ramfs$ prompt.
Last edited by cplum (2008-05-29 15:34:53)
Offline
Lachkater wrote:Check that you have the base udev and filesystem hook inbuild. Logs would also be good... Maybe taking out the autodetect hooks also helps (however this will slow down your boot time)
With the default configuration (ie if you didn't edit /etc/mkinitcpio.d/example.preset), the only difference between fallback and normal image is that in fallback the 'autodetect' hook is left out.
What would be in there that would cause me to boot into the recovery shell? Im running Arch from an external HD plugged into a usb port, would that have anything to do with it?
Offline
What would be in there that would cause me to boot into the recovery shell?
This is pretty hard to tell:
Whithout going into the logs yet,
nor have you commented on the first suggestion given to you by tomk
Offline
Yes, as czar and tomk say: boot fallback, make sure you have 'usb' hook included in your hooks, and regenerate kernel26.img with mkinitcpio.
Offline
just FYI: scroll lock should pause messages on boot.
Offline
Here is my mkinitcpio example.preset file
# Example mkinitcpio preset file
# preset names
PRESETS=('default' 'fallback')
# ALL_kver is used if presetname_kver is not set
# note for distribution kernels: this should be in a separate file
# and read like this:
# source /etc/mkinitcpio.d/exmaple.kver
ALL_kver='2.6.24-ARCH'
ALL_config='/etc/mkinitcpio.conf'
# presetname_kver - the kernel version (omit if ALL_kver should be used)
# presetname_config - the configuration file (omit if ALL_config should be used)
# presetname_image - the filename of generated image
# presetname_options - any extra options
#default_kver="2.6.18-ARCH"
#default_config="/etc/mkinitcpio.conf"
default_image="/tmp/kernel26.img"
default_options=""
#fallback_kver="2.6.18-ARCH"
#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/tmp/kernel26-fallback.img"
fallback_options="-S autodetect"
I looked in logs and i can't find a boot log.... unless its called something else.
Offline
Check that you have the base udev and filesystem hook inbuild. Logs would also be good... Maybe taking out the autodetect hooks also helps (however this will slow down your boot time)
where do i find the hooks?.... please bear with me
Offline
this is the kernel 26 preset
# mkinitcpio preset file for kernel26
########################################
# DO NOT EDIT THIS LINE:
source /etc/mkinitcpio.d/kernel26.kver
########################################
ALL_config="/etc/mkinitcpio.conf"
PRESETS=('default' 'fallback')
#default_config="/etc/mkinitcpio.conf"
default_image="/boot/kernel26.img"
#default_options=""
#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/kernel26-fallback.img"
fallback_options="-S autodetect"
Offline
If you want to post something, post the MODULES and HOOKS lines from /etc/mkinitcpio.conf. Also tell us what type of harddrive do you have (SATA? IDE? over USB?).
But, above all, why don't you do what was suggested above?
1) boot the fallback
2) run '/sbin/mkinitcpio -g /boot/kernel26.img' as root
3) reboot
And I'm sorry, example.preset has no influence on the images generated.
Offline
I ran mkinitcpio -g on kernel26.img as root, it rebuilt but still does the same thing, here are my modules and hooks lines:
MODULES="pata_acpi pata_amd ata_generic sata_nv"
HOOKS="base udev autodetect pata scsi sata usb usbinput keymap filesystems"
I have an ide in an external box through the usb
Offline
I know this is an old thread, but I don't see the point in starting a new one (let me know if I should). Anywho, I was having the exact problem and doing what blender02 said seems to have worked perfectly. What I'm wondering is after 5 or so months of working flawlessly, why did the kernel decide to fuck up?
dnyy in IRC & Urban Terror
Offline
Do the partitions in the two grub boot lines match? Also, are you using an old kernel or an unstable one? Have you updated your system lately?
I'm pretty sure that all of these have the potential to mess the boot up.
urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand
Offline
I update twice a day or so.
~/ uname -r
2.6.29-ARCH
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/d137dc90-0d5d-4210-8ce1-5846b431ba0e ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/d137dc90-0d5d-4210-8ce1-5846b431ba0e ro
initrd /kernel26-fallback.img
dnyy in IRC & Urban Terror
Offline
Just to add a little information to this, I am having the same problem.
I know what it is but I haven't figured out how to fix it yet.
I have compiled a xen kernel and it can't find my sata drives because mkinitcpio can't find the module sata_nv. The IDE drivers are found.
It isn't in the lib/modules/xen-2.6.18-xen directory.
I could copy the root to an ide drive but I would rather get the build right.
Just to clarify the problems above, the kernel has a problem with the driver module for that hard disk.
Offline
Pages: 1