From: Jonathan R. <mma...@ya...> - 2002-02-11 01:36:46
|
On Sun, 10 Feb 2002, Matthew Franz wrote: > > Hi Jonathan, > > Based on the traffic from uml mailing list I think the initrd is broken in > the latest release. I had similar problems and Bill Burdick's kernel was > the only one I could get working. I also tried multiple compilers and > glibc's, too. Yes, there was a segv problem with 2.4.17-10um, but Jeff provided a solution for that. We'll have to find out what Bill did differently, because I used the same compiler (2.96 20000731), uml patch (2.4.17-5um), and perhaps the same glibc (2.2.4) that he used to create the successful kernel included with trinux-uml. > I have the config on my laptop at work, but the solution is probably to go > back a few releases of UML and not use the latest. Hopefully, the mystery lies within the config, unless, there were some additional alterations to the kernel code. > > Hi, > > > > 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 > > > |