<...snip....>
>> cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. >> cf: Octeon bootbus compact flash driver version 1.1 >> cf: Compact flash found in bootbus region 3 (16 bit). >> cfa:cfa: SanDisk SDCFJ-1024 Serial 011716F0507F0341 (2001888 sectors, >> 512 bytes/sector) >> cfa1 cfa2 >> EXT3-fs: INFO: recovery required on readonly filesystem. >> EXT3-fs: write access will be enabled during recovery. >> kjournald starting. Commit interval 5 seconds >> EXT3-fs: recovery complete. >> EXT3-fs: mounted filesystem with ordered data mode. >> VFS: Mounted root (ext3 filesystem) readonly. >> Freeing unused kernel memory: 22424k freed >> Warning: unable to open an initial console. > > Do you get above "Warning:" message with old busybox too? > If not, then something else is wrong: this message means that > kernel cannot open /dev/console, and that happens even before > kernel tried to run init. This might mean that kernel > cannot access your filesystem and is unabe to see files on it > (and thus cannot open /dev/console and busybox binary). > No I don't get this message with the old busybox. Here is that output. cfa:cfa: SanDisk SDCFJ-1024 Serial 011716F0507F0341 (2001888 sectors, 512 bytes/sector) cfa1 cfa2 Freeing unused kernel memory: 22732k freed boot starting Updating module dependencies Creating mount points Mounting file systems kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on cfa2, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting hostname to u4ea_linux Configuring ifcfg-eth0 SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device Configuring ifcfg-eth1 SIOCSIFADDR: No such device eth1: unknown interface: No such device All the interface stuff don't worry about because I know my hardware module hasn't been loaded yet. But I do notice that this line runs.. "EXT3-fs warning: maximal mount count reached, running e2fsck is recommended" Do you think the newer busybox has a problem with this? > EXT3 recovery messages hint at damaged / uncleanly > umounted filesystems being mounted, which should not happen. > >> Kernel panic - not syncing: No init found. Try passing init= option to >> kernel. > >> First things first.. with u-boot and the older version of busybox I >> didn't need to pass in any "root=" command. >> >> Seems like I need to now. > > Where? It talks about init=xxx, not root=xxx. > I understand that it talks about init and not root. I pass in /dev/cfa2 for my root but my root is really the ramdisk that is part of the image and NOT /dev/cfa2. I think this is the crux of my problem. >> But my root is part of the linux kernel that I build (it's all ramdisk >> etc..) so I shouldn't have to. >> >> And to tell you the truth, I think that's my problem but I'm not sure >> what to tell u-boot or busybox. > > As a start, I'd take old ramdisk image, mount it, > just replace busybox binary, umount, and try this modified image. GREAT IDEA! Will do that now and see if that makes a difference. vda...... PS... Rob.. thanks for the link... tried that link and what it suggests. I think my problem is a little deeper than that. I know my init is built properly as it runs with the old version of busybox. That's what started me down this road... -- /* * Steve Iribarne * Software Engineer * (aka Grunt) */ _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
