Thanks for the reply. In <[EMAIL PROTECTED]>, on 25/Jan/2001 at 09:52 AM,(-0800 GMT) Geoffrey Brimhall <[EMAIL PROTECTED]> said:
>1. Cant mount root FS on ... >milo just needs to tell the kernel where the hard disk partition which >contains the root file system is located. But I'm using root=/dev/fd0. ( or hdb if booting from the CD) >If your root partition is /dev/sda2 (First scsi hard disk, second >partition), the milo command to boot everthing should look something >like: >boot sda2:/vmlinuz root=/dev/sda2 Yes that will be the case once I have this thing installed. >(sda2:/vmlinuz tells milo where the kernel binary is located, > root=/dev/sda2 is command line parameters which milo will hand the linux > kernel when it is loaded). so when I do boot fd0:linux.gz root=/dev/fd0 load_ramdisk it should work? Trouble is that it doesen't here! boot fd0:linux.gz root=/dev/fd0 load_ramdisk=1 dies with You didn't specify the type of your ufs file system mount -t ufs -o ufstype=sun|sunx86|44bsd|old|nextstep|nextstep-cd|opensep... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old ufs_read_super: bad magic number Kernel panic: VFS: Unable to mount root fs on 02:00 >2. try passing init= to kernel >I don't think you need to do this. You could append the init=1, etc after >the root=/dev/sda2, but this just has the kernel tell the init program >to only start the os up to a certain level. Normally you'd leave this >out and let the default thing happen. I think it has to do with not being able to find the root.bin image boot hdb:linux root=/dev/hdb load_ramdisk=1dies with Unable to open initial console. Kernel panic No init found. Try passing init= option to kernel >3. unable to handle kernel paging request at virtual address... >This is a wierd one. Is your swap partition set up correctly ? Look at >/etc/fstab to see where the os thinks the swap partition is. /etc/fstab boes not exist on the install floppys. >Other than that, the only other thing I can think of is maybe you're >using the wrong kernel for the particular kind of alpha system you have. Everything I have says this is a pc164 board so that's what I'm using. "Display hardware configuration" shows Alpha processor and system information: Processor ID 21164 Processor Revision 5.0 System Revision 0x1 Processor speed 366.03 MHz Extended firmware information Version: 4.49-7961016.1355 Any other ways I can confirm what exactly it is? I get the paging request error if I try something fancy like booting from the CD while using the fd as root. vis... boot hdb:linux root=/dev/fd0 load_ramdisk=1 results in Unable to handle kernel paging request at virtual address 0229a8000085e590 Swapper (1): oops 0 pc=[<fffffc0000351ef0>] ra=[<fffffc0000351ec8>] ps=0000 v0=0000000000000400 t0=0229a8000085e560 t1=fffffc00005e4000 t2=fffffc00005a4b20 t3=0000000000000000 t4=0000000000000001 t5=0000000000019840 t6=0000000000000000 t7=fffffc0000004000 s0=fffffc000fdc7b60 s1=0000000000000001 s2=fffffc00005a58d8 s3=fffffc000fdc7b60 s4=0000000000000400 s5=0000000000000662 s6=0000000000000400 a0=fffffc000fdc7b60 a1=0000000000000000 a2=0000000000000661 a3=fffffc0000351a20 a4=0000000000000000 a5=0000000000000004 t8=fffffc00005a4c20 t9=0000000000000000 t10=0000000000000004 t11=0000000000000000 pv=fffffc0000351ea0 at=fffffc0000356a90 gp=fffffc000059b470 sp=fffffc0000006bb0 code: a47db8b8 ldq t2,-18248(gp) 4821b681 srl t0,13,t0 40210441 s4addq t0,t0,t0 a4430000 ldq t1,0(t2) 48209721 sll t0,4,t0 40220401 addq t0,t1,t0 *a8810030 ldl_l t3,48(t0) 44809003 and t3,4,t2 trace: 356b60 4360a8 436ee4 4370ac 437164 4377bc 310000 3102d8 3102c0 310888 3102c0 31085c 310838 3102c0 31085c 3102c0 Anybody able to decipher this ? Thanks for your interest :). -- /-- Bob Ogden [EMAIL PROTECTED] --------------/ / -... --- -... --- --. -.. . -. Finger for PGP key -----/ Only 31554704183 seconds till the _next_ millennium!
