linux-kernel - ramdisk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <ab40e9c0709030604u5fecf34dr945ece01b95e622d@mail.gmail.com>
Date:	Mon, 3 Sep 2007 15:04:04 +0200
From:	"Xu Yang" <risingsunxy@...glemail.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: ramdisk

Hi everyone,

I want to use ramdisk to boot my filesystem, as I can't use NFS and harddisk.

I have load the ramdisk into the ram memory (start address :0x4000000)

and in the boot options I specified : root =dev/ram0 initrd=0x4000000

but the kernel said it can not find any file system on it.

Here is the information I can supply :
U-Boot 1.2.0 (Aug 31 2007 - 20:54:55)

***  Auto-detects ethernet chip ***

DRAM:   0 kB
## Unknown FLASH on Bank 1 - Size = 0x00000000 = 0 MB
Flash:  0 kB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial

Hit any key to stop autoboot:  0
## Booting image at 00007fc0 ...
   Image Name:   Linux-2.6.19-arm2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    740372 Bytes = 723 kB
   Load Address: 00008000
   Entry Point:  00008000
OK

## Loading Ramdisk Image at 04000000 ...
   Image Name:   ramdisc
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    12582962 Bytes = 12 MB
   Load Address: 04000000
   Entry Point:  04000000

Starting kernel ...

.........................................................................................

RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
<6>loop: loaded (max 8 devices)
<6>mice: PS/2 mouse device common for all mice
<6>VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 3
No filesystem could mount root, tried:  ext2 cramfs vfat
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)

Who can give me some hints ? or point me some direction to handle this.

I appreciate this very much.

regards,

Yang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/