[U-Boot-Users] Newbie... still stuck with RAM disk

Finally got access to hardware again. So here's the full o/p from my ARM target. Still trying to get a root file system on a RAM disk. Without any success. Here's o/p from my booting.... Again apologies if its in-appropriate. I'm absolutely stuck!
The RAM disk is programmed into FLASH at 0x8200000. The kernel is tftpeed to RAM at 0x30300000
my bootargs are root=/dev/ram
A couple of questions before I'm roasted.......
-> Do I need CONFIG_SETUP_MEMORY_TAGS enabled -> Do I need CONFIG_INITRD_TAG enabled -> Should CONFIG_DEVFS_FS be enabled in kernel? -> Should CONFIG_DEVFS_MOUNT be enabled in kernel -> When running mkimage for RAM disk what relevance are load and entry addresses. My 'Karim Yaghmour' book says not needed. -> Do I need to specify 'initrd=' -> Do I need to specify 'initrd_start='
Sorry for appearing dumb but there are so many combinations...... and I have already tried so many my head is spinning.
Thanks, Luke
bootm 30300000 8200000 ## Booting image at 30300000 ... Image Name: 2.4.18 rmk pxa1 Created: 2004-03-16 17:44:43 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 664024 Bytes = 648.5 kB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 08200000 ... Image Name: RAM disk Created: 2004-03-16 14:46:33 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4164813 Bytes = 4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux................................................ done, bootin g the kernel. Linux version 2.4.18-rmk7-pxa1 (lukef@target1) (gcc version 2.95.2 20000516 (rel ease) [Rebel.com]) #16 Tue Mar 16 17:41:30 GMT 2004 CPU: ARM/CIRRUS Arm920Tsid(wb) revision 0 Machine: Samsung-SMDK2410 On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/ram DEBUG: timer count 15626 Console: colour dummy device 80x30 Calibrating delay loop... 49.86 BogoMIPS Memory: 64MB = 64MB total Memory: 62880KB available (1253K code, 257K data, 76K init) Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket CPU clock = 200.000 Mhz, HCLK = 100.000 Mhz, PCLK = 50.000 Mhz Starting kswapd devfs: v1.10 (20020120) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 ttyS%d0 at I/O 0x50000000 (irq = 52) is a S3C2410 ttyS%d1 at I/O 0x50004000 (irq = 55) is a S3C2410 ttyS%d2 at I/O 0x50008000 (irq = 58) is a S3C2410 Console: switching to colour frame buffer device 30x40 Installed S3C2410 frame buffer pty: 256 Unix98 ptys configured s3c2410-ts initialized S3C2410 Real Time Clock Driver v0.1 block: 128 slots per queue, batch=32 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize eth0: cs8900 rev J(3.3 Volts) found at 0xd0000300 cs89x0 media RJ-45, IRQ 37 No NAND device found!!! NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 4096) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com Kernel panic: VFS: Unable to mount root fs on 01:00
_________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

In message BAY10-F73zrZB5WLlLt000334d2@hotmail.com you wrote:
A couple of questions before I'm roasted.......
-> Do I need CONFIG_SETUP_MEMORY_TAGS enabled
Yes.
-> Do I need CONFIG_INITRD_TAG enabled
Yes.
And CONFIG_CMDLINE_TAG as well.
-> Should CONFIG_DEVFS_FS be enabled in kernel?
No.
-> Should CONFIG_DEVFS_MOUNT be enabled in kernel
No.
-> When running mkimage for RAM disk what relevance are load and entry addresses. My
They are irrelevant and can be omitted.
'Karim Yaghmour' book says not needed.
Karim is right.
-> Do I need to specify 'initrd=' -> Do I need to specify 'initrd_start='
Never needed any of these.
Ummm... do you have ext2 support enabled in your kernel configu- ration? [or whichever filesystem type you use in your ramdisk.]
Best regards,
Wolfgang Denk
participants (2)
-
Luke Fimmerzane
-
Wolfgang Denk