Hello,

I cant seem to boot a unbranded Ralink RT305X using openwrt
trunk/trunk co on june 02. Essentialy code after
https://lists.openwrt.org/pipermail/openwrt-devel/2011-March/009924.html.
Attached below is a log of the boot process
<snip>
[    0.360000] TCP reno registered
[    0.370000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.380000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.390000] NET: Registered protocol family 1
!*-- Note: These messages are dude to a *very* hacky patch that i added. *--!
!*-- hacky printk messages begins *--!
[    0.400000] <code@sekon> ~ pronto says hello ~
[    0.410000] <code@sekon> ~ Registration of flash is done ~
[    0.420000] ralink flash device: 0x400000 at 0x1f000000
[    0.440000] Error: 0 flash device was found
!*-- hacky printk messages ends *--!
[    0.470000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.480000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME)
(CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.500000] msgmni has been set to 122
[    0.510000] io scheduler noop registered
[    0.520000] io scheduler deadline registered (default)
[    0.530000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.540000] serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
[    0.560000] serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
[    0.570000] physmap platform flash device: 00800000 at bf000000
[    0.580000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit
bank. Manufacturer ID 0x0000c2 Chip ID 0x002b
[    0.600000] Amd/Fujitsu Extended Query Table at 0x0040
[    0.620000]   Amd/Fujitsu Extended Query version 1.1.
[    0.630000] number of CFI chips: 1
[    0.630000] RedBoot partition parsing not available
[    0.640000] Using physmap partition information
[    0.650000] Creating 5 MTD partitions on "physmap-flash.0":
[    0.660000] 0x000000000000-0x000000030000 : "Bootloader"
[    0.670000] mtd: Giving out device 0 to Bootloader
[    0.690000] 0x000000030000-0x000000040000 : "Config"
[    0.700000] mtd: Giving out device 1 to Config
[    0.710000] 0x000000040000-0x000000050000 : "Factory"
[    0.720000] mtd: Giving out device 2 to Factory
[    0.730000] 0x000000050000-0x0000003e0000 : "Kernel"
[    0.740000] mtd: Giving out device 3 to Kernel
[    0.750000] 0x0000003e0000-0x000000400000 : "RW-FS"
[    0.760000] mtd: Giving out device 4 to RW-FS
[    0.770000] physmap-flash.0: failed to claim resource 0
[    0.790000] Generic platform RAM MTD, (c) 2004 Simtec Electronics
[    0.810000] slram: not enough parameters.
[    0.820000] TCP westwood registered
[    0.820000] NET: Registered protocol family 17
[    0.830000] 802.1Q VLAN Support v1.8 Ben Greear <gree...@candelatech.com>
[    0.850000] All bugs added by David S. Miller <da...@redhat.com>
[    0.860000] VFS: Cannot open root device "1f04" or unknown-block(31,4)
[    0.870000] Please append a correct "root=" boot option; here are
the available partitions:
[    0.890000] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(31,4)
</snip>
This page (http://www.linux-usb.org/usb.ids) seems to be of little
help as of this moment. The hacky patch forces a partition down the
throat while booting and it seems to be written over by code before
the kernel panic, because if i disable certain options in the mtd
subsystem, i do get a misleading list of mtd partitions after
[    0.870000] Please append a correct "root=" boot option; here are
the available partitions:

A sample of that log is posted below
<snip>
[    0.780000] List of all partitions:
[    0.790000] 1f00             192 mtdblock0  (driver?)
[    0.800000] 1f01              64 mtdblock1  (driver?)
[    0.810000] 1f02              64 mtdblock2  (driver?)
[    0.820000] 1f03            3648 mtdblock3  (driver?)
[    0.830000] 1f04             128 mtdblock4  (driver?)
[    0.840000] No filesystem could mount root, tried:  squashfs jffs2
[    0.850000] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(31,4)
</snip>

I could post the actual patch, but it is just files from wive-ng
project hacked to just compile.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to