> There probably is a good reason why you end up in busybox shell. Often the
> reason is that the initrd could not mount the root file system. > > Can you post the last 20 lines or so on the console before you get the > Busybox shell? > > What is the disk/partition setup that you are using? Here is my disc config: Disk /dev/sda: 18.4 GB, 18400000000 bytes 255 heads, 63 sectors/track, 2237 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 4 32098+ f0 Linux/PA-RISC boot /dev/sda2 5 20 128520 83 Linux (/boot) /dev/sda3 21 2237 17808052+ 5 Extended /dev/sda5 * 21 2192 17446558+ 83 Linux (/) /dev/sda6 2193 2237 361431 82 Linux swap / Solaris The full console log in in a previous message: http://lists.debian.org/debian-hppa/2006/06/msg00050.html The disk configuration is ok, because the system boots fine with 2.6.12-1 kernel. It just fail with any newer kernel. I think this is a initrd issue, but i dont know what more to try. One of the big problem is that every time i try a new kernel or a new initrd image to try to solve the problem, if the test fail and the machine falls in the busibox shell, y cant reboot it remotely. There is no shutdown command nor reboot. I need to call somebody at the phisical location of the machine to push the power button. ========================================== Alvaro Consuegra - Zaragoza (Spain [EU]) Consultor T.I. MCSE email: [EMAIL PROTECTED] ========================================== -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
