Re: [Trinux-talk] Alternative kernels and trinux-uml

[Bill B. <bi...@ap...>]

The problem might be in the args you're passing to the kernel.  Here are
the command line args I'm using (from my run script):

umid=bob initrd=initrd root=/dev/ram0 umlpacks=$dir/$disk eth0=daemon
eth1=daemon $args

umid -- identifies this instances name for uml_mconsole
initrd	-- identifies initrd file
	-- note that you need this one, NOT init=
	-- this could be your problem right here
root=/dev/ram0 -- identifies the device for initrd
umlpacks=$dir/$disk -- stuff for my linuxrc
eth0=daemon -- ethernet device.  run uml_switch for this to work.
eth1=daemon -- ethernet device


Also, you must make sure that initrd and minix are compiled into the
kernel (not as modules), and make sure that the ram dev size is big
enough (I use 7168)


On Sun, 2002-02-10 at 17:25, Jonathan Rosenbaum wrote:
> Hi,exec ../linux 
> 
> I've been trying to get the initrd from trinux-uml-0.1.tgz to work with
> another kernel which has both CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_INITRD
> configured, the minix fs mounts, but for some reason an initial console
> can't be found, and this isn't a devfs issue either since nomount is used.
> 
> Usually, in a situation like this it would be safe to assume that
> something is amiss in the initrd, but this is definitely not the case, and
> the initrd does work properly with the kernel which comes with trinux-uml. 
> I thought maybe it was a compiler issue so I made a uml (2.4.17-5um) with
> the same compiler used to make the trinux-uml kernel, but I still had the
> same results.
> 
> This leads me to suspect that it is a configuration conflict.  Could you
> please send me the .config you used for the trinux-uml kernel?  It would
> also be a good idea to include this .config with the trinux-uml package. 
> 
> The kernel which ships with gbootroot (gbootroot.sf.net) exhibits the same
> problem, and the config used to make this kernel is included.  I am
> thinking that it may be something simple causing this problem. 
> 
> Thanks,
> 
> 
> Jonathan
> 
> 
> RAMDISK: Minix filesystem found at block 0
> RAMDISK: Loading 4096 blocks [1 disk] into ram disk... done.
> Freeing initrd memory: 4096k freed
> cramfs: wrong magic
> MINIX-fs: mounting unchecked file system, running fsck is recommended.
> VFS: Mounted root (minix filesystem).
> Warning: unable to open an initial console.
> Kernel panic: No init found.  Try passing init= option to kernel. 
> 
> 
> 
> 
> 
> _______________________________________________
> Trinux-talk mailing list
> Tri...@li...
> https://lists.sourceforge.net/lists/listinfo/trinux-talk
-- 
	Bill Burdick
	Bi...@ap...