• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2]
16  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: August 27, 2009, 11:58:27 AM
1. no, as far as I know, this patch is not included in any official kernel. The main reason is that it's not necessary for every SD card. Applying this patch disables highspeed, even if the SD card would work correctly with it

2. I don't know. I don't have a Polaroid SDCard.

If you need, I have a 2.6.30.4 kernel with this patch, based on the config of http://sheeva.with-linux.com/sheeva/
17  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: August 21, 2009, 12:21:10 AM
westyd1982, I had exactly the same error when formatting my 8Gb SDHC card in ext3.
Once I formatted it in ext2, the error disappeared.
18  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: August 09, 2009, 06:27:40 AM
Hi all, I'm using the uboot version bundled with the Sheevaplug installer alpha 6.
It can boot on a ext2 SD card, but not on a ext3 SD card (it gives a "bad magic number" in this case)

Is ext3 supported by u-boot? Will it be in the future, or did I miss a step to make it work?

This is how I format my SD card in ext2 :
mkfs -t ext2 -I 128 /dev/mmcblk0p1

If I format it in ext3 :
mkfs -t ext3 -I 128 /dev/mmcblk0p1
U-boot won't boot on the SD card (bad magic number)
19  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: July 28, 2009, 01:13:09 PM
The plug is up for more than 2 days... That's great!
Thank a lot philipl for this patch

PS : my SDHC card is a Crucial CT8GBSDHC
20  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: July 26, 2009, 02:16:36 PM
I also applied this patch on a 2.6.30.3 mainline kernel and used the plug for a few hours.
It looks like it took rid of the -110 errors : without this patch, it took a few minutes before these errors to show up.

I run a few speed tests on the SDHC, based on http://www.computingplugs.com/index.php/SheevaPlug_Performance
As expected, the read speed is reduced : 9.1 Mb/s.
The write speed doesn't seem to be affected :  7.5 Mb/s

That's great news : my plug is finally stable, and it boots on the SD card.

Anyway, it's a pitty we have to reduce the speed. I hope a better solution will be found
21  Linux Stuff / Kernel / Re: SD card support on: May 24, 2009, 01:28:39 PM
My own observations are very similar :

1) Same fact : before I opened the plug, I never managed to have any SD card work. I have tested 3 different cards : a brand new Crucial SDHC 8Gb, an old Canon SD 32Mb, and an old Panasonic SD 256Mb.

2) I tested several different kernels, including orion and mainline, but none of them worked before I opened the plug. Currently, I use a mainline kernel, with patches coming from orion (especially the mvsdio one)

3) Same thing : from a cold boot (with the plug opened), all my cards work reliably when I boot on NAND. I currently don't manage to boot directly from SD (I mean, use a rootfs from SD, even if the kernel is on NAND), but it's probably another problem

4) From a soft reboot, that depends : sometimes it works, sometimes it does not. I did not notice any difference between SD and SDHC card, but I did not have enough time to make complete tests

5) What I can say, it's that a cold reboot (unplug / replug) is always safe. A soft reboot sometimes leads to -110 errors, or undetected cards
22  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 08:25:30 AM
OK I tried again with the "feroceon.cpu arp_examine" line, and with 2000kHz, as requested.
It works too, even if the same kind of warnings appear (see log below)

Code:
sudo ./runme.sh  **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1049). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1110). Workaround: increase "set remotetimeout" in GDB
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 32.932339s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1002). Workaround: increase "set remotetimeout" in GDB
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 117.655731s
 **** U-boot should be up and running now. Open your console ...
23  Linux Stuff / Kernel / Re: SD card support on: May 24, 2009, 02:59:06 AM
I am also puzzled.

As Philipl said, it seems that the SD cards stop working after a soft reboot (even with the sheevaplug opened).
I tried that with a 2.6.30-rc6 patched kernel, and a recent uBoot with SD support, through the installer alpha-5 (http://plugcomputer.org/plugforum/index.php?topic=323.0)

If I unplug and replug it, the SD card works... Quite strange.
24  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 02:51:05 AM
Thanks a lot for your answers.

Changing the frequency was the right thing to do : it worked with 500kHz (but it didn't work with 1000kHz). Maybe it's worth changing this for next version.
See the log below : there seems to be some warnings anyway

Code:
sudo ./runme.sh  **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
500 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1241). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1020). Workaround: increase "set remotetimeout" in GDB
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 52.464920s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1024). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1178). Workaround: increase "set remotetimeout" in GDB
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 188.052399s
 **** U-boot should be up and running now. Open your console ...


After that, the sheevaplug reboots, flashes, reboots... and it works.

First thing that surprises me : it seems that it boots much faster than before. Is this due to UBIFS?
The rootfs is also directly useable : no patch needed for apt or dns lookups, and only 3 update with apt-get upgrade.

I love this installer, because it really eases all the process of flashing, and modifying the uboot parameters. And you get a working and up-to-date OS, with an up-to-date kernel.
Thank you for the good job!
25  Linux Stuff / Kernel / Re: SD card support on: May 23, 2009, 01:35:12 PM
Wow, thanks philipl for the tip.
I was fighting with SD cards and sheevaplug for weeks.
I tried with 3 different SD cards (SD ans SDHC), and kernels (mainline, orion, different patches etc). I had -110 errors every time.

As you proposed, I opened the sheevaplug, and plugged it again : boom, all SD cards are detected by the kernel and can be mounted readwrite (I'm currently using mainline 2.6.30-rc6 with mvsdio patch).
That's great news, because I still thought I had a software problem.
On the other hand, the behavior is quite strange : If I close the plug again (with the 4 screws), the -110 errors are back. It looks like it only works if the sheevaplug is opened.
Could it be due to the red push-button inside the plug? Maybe it's pushed when the plug is closed...
Or maybe it's due to the heat of the power supply next to it?

I'm currently trying to use the SD card (actually a 8Gb SDHC) as my root filesystem (keeping the kernel in NAND). With the plug opened or closed, I get the -110 errors. Maybe it's because I did not patch uBoot, or because the howto has been removed from the FAQ (found http://www.openplug.org/plugwiki/index.php?title=Frequently_Asked_Questions&oldid=413#Make_an_SD_card_be_the_root_filesystem in the history, but it has been removed in the latest version of the page : http://www.openplug.org/plugwiki/index.php?title=Frequently_Asked_Questions)

Philipl, do your SD cards work if you close the sheevaplug? Did you manage to use an SD card as your root file system?
26  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 23, 2009, 10:49:03 AM
Hi,

first of all, I think this is a great idea to make an installer.

Anyway, I didn't manage to make it work on my computer & sheevaplug.
Maybe I did something wrong.

My computer is running Ubuntu 9.04 desktop (x86).
I followed the README.txt in the tar.gz : formatted an USB stick, and put the files in it.
I plugged the mini-USB to the computer, and connected via Putty on /dev/ttyUSB1
Then I ran runme.sh on the computer :

Code:
sudo ./runme.sh
 **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Error: JTAG communication failure, check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x3F. tap=feroceon.cpu pos=0 expected 0x1 got 3
Warn : Could not validate JTAG chain, continuing anyway...
Warn : value captured during scan didn't pass the requested check:
Warn : captured: 0x0F check_value: 0x01 check_mask: 0x0F
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: Target not examined yet
Runtime error, file "../scripts-linux/openocd/config/board/sheevaplug.cfg", line 21:
   
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

The sheevaplug reboots at this moment, but nothing has been flashed.

The README explains that we should in this case disconnect/reconnect the sheevaplug, or even unplug/plug back it.
I did it several times, and even restarted the computer : the same error happens.

It seems that line 20 of sheevaplug.cfg is executed (which restarts the sheevaplug), but line 21 fails ("halt 0")

I tried with or without putty connected, with or without an OS launched on the sheevaplug : always the same error.

Any ideas?
27  Linux Stuff / Linux distributions / Re: Kernel panic - not syncing: No init found on: April 25, 2009, 01:40:33 PM
The problem was apparently coming from the commands after the flash.
If I use the commands from Rev1.0, I can boot correctly :

Code:
setenv bootargs 'console=ttyS0,115200 mtdparts=nand_flash:0x400000@0x100000(uImage)ro,0x1fC00000@0x500000(rootfs)rw root=/dev/mtdblock2'
setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
saveenv
reset

This worked with the jffs2 posted at http://djpandemonium.com/plug/SheevaPlug_FileSystem.zip

With the latest file downloaded from the website (v1.2), the mount gave me this error :
Code:
JFFS2 notice: (294) check_node_data: wrong data CRC in data node at 0x00069000: read 0xc5585480, calculated 0xa78a6243.
JFFS2 warning: (294) jffs2_do_read_inode_internal: Truncating ino #22 to 30236 bytes failed because it only had 16384 bytes to start with!

For now, I'll keep the jffs2 of pandemonium (thank you), and try to upgrade ubuntu to final version.
28  Linux Stuff / Linux distributions / Re: Kernel panic - not syncing: No init found on: April 25, 2009, 11:45:44 AM
I managed to make ubuntu boot correctly!
I simply applied the instructions of the previous version of documentation : Rev1.0, instead of Rev1.2

I'll try to find out which exact command was wrong...
29  Linux Stuff / Linux distributions / Re: Kernel panic - not syncing: No init found on: April 25, 2009, 10:48:00 AM
Thanks for your answer.

I checked again the "Writing Jaunty Filesystem" documentation from http://www.marvell.com/files/products/embedded_processors/developer/kirkwood/SheevaPlug_DocumentationPackage.zip (it's currently Rev1.2)
On page 5, it seems to use -p for both nandwrite commands.
But you're right, on previous versions of this document, the -p option was not used to flash the jffs2.

I tried :
Code:
nandwrite p /dev/mtd1 uImage.sheeva.040309
nandwrite /dev/mtd2 ubuntu-9.0.5.Release.jffs2
It gave me the same behavior.

I also tried :
Code:
nandwrite /dev/mtd1 uImage.sheeva.040309
nandwrite -p /dev/mtd2 ubuntu-9.0.5.Release.jffs2
It failed for uImage with message :
Code:
Input file is not page aligned
Data was only partially written due to error
: Success
So it ends up with a "Bad Magic Number" when trying to boot on the NAND.
30  Linux Stuff / Linux distributions / Kernel panic - not syncing: No init found on: April 25, 2009, 08:06:06 AM
Hi all,

I just received my brand new sheevaplug.
Unfortunately, it did not boot when I first plugged it :
Verifying Checksum ... Bad Data CRC

So I'm trying to reflash the NAND with ubuntu jaunty.
I followed the documentation "SheevaPlug Development Kit - Writing Jaunty Filesystem on the NAND flash-Rev1.2.pdf" found on the website :
- start the sheevaplug via NFS
- flash uImage and jffs2
- reset
- reconfigure to boot from NAND
- reset

The checksum is correct and ubuntu boots... but it stops with the following message :
Code:
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
(see full log below)

I found a few related posts here (http://openplug.org/plugforum/index.php?topic=133.0 and http://openplug.org/plugforum/index.php?topic=139), saying that it might come from a corrupted jffs2 file.
So I tried to use several versions of the ubuntu-9.0.5.Release.jffs2 file :
- the one available on the website (v1.2). By the way, it now gives a 404
- the one available from the provided CDROM (v1.1)
- the one downloaded from http://djpandemonium.com/plug/SheevaPlug_FileSystem.zip
- one that I downloaded a while ago, named ubuntu-9.0.4.Release.jffs2 (v1.0)

All these versions gave the same result.

I also tried to add init=/sbin/init or init=/bin/bash in the bootargs :
Code:
Warning: unable to open an initial console.
Failed to execute /bin/bash.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.


Any help would be appreciated.

Here are the commands I used to boot from NFS :
Code:
set console 'console=ttyS0,115200 mtdparts=:0x100000@0x000000(u-boot),0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw'
set bootargs_root 'root=/dev/nfs rw'
set bootcmd 'tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000'
saveenv
reset
Tha commands I used to flash :
Code:
flash_eraseall /dev/mtd1
flash_eraseall -j /dev/mtd2
nandwrite p /dev/mtd1 uImage.sheeva.040309
nandwrite p /dev/mtd2 ubuntu-9.0.5.Release.jffs2
mount -t jffs2 /dev/mtdblock2 /mnt1
And the commands I used after the flash :
Code:
setenv bootargs 'console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fC00000@0x400000(rootfs)rw root=/dev/mtdblock2'
setenv bootcmd 'nand read.e 0x800000 0x100000 0x300000; bootm 0x800000'
saveenv
reset


Here is the full boot log :
Code:
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.22.18 (root@localhost.localdomain) (gcc version 4.2.0 20070413 (prerelease)) #1 Fri Apr 3 18:49:38 PDT 2009
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fC00000@0x400000(rootfs)rw root=/dev/mtdblock2 init=/bin/bash
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 515584KB available (3772K code, 258K data, 124K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG  Soc: 88F6281 A0 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c08b0600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
  o RAID 5 Xor calculation
  o kernel memcpy
  o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c00117e4)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
RAMDISK driver initialized: 20 RAM disks of 4096K size 4096 blocksize
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o eth0, ifindex = 1, GbE port = 0
    o eth1, ifindex = 2, GbE port = 1

mvFpRuleDb (dfd20000): 16384 entries, 65536 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation

Warning Sata is Powered Off
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 55 at 0x006e0000
Bad eraseblock 214 at 0x01ac0000
Bad eraseblock 228 at 0x01c80000
Bad eraseblock 444 at 0x03780000
Bad eraseblock 484 at 0x03c80000
Bad eraseblock 582 at 0x048c0000
Bad eraseblock 615 at 0x04ce0000
Bad eraseblock 1004 at 0x07d80000
Bad eraseblock 1121 at 0x08c20000
Bad eraseblock 1264 at 0x09e00000
Bad eraseblock 1394 at 0x0ae40000
Bad eraseblock 1545 at 0x0c120000
mtd: bad character after partition (r)
3 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00400000 : "uImage"
0x00400000-0x20000000 : "rootfs"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:
mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9)
assembly=-1,irq=-1
mp_check_config: Error, invalid voice assembley mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     97 MB/s
raid6: int32x2    123 MB/s
raid6: int32x4    126 MB/s
raid6: int32x8    111 MB/s
raid6: using algorithm int32x4 (126 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1084.000 MB/sec
   8regs     :   754.800 MB/sec
   32regs    :   899.600 MB/sec
raid5: using function: arm4regs (1084.000 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdmmc: irq =28 start f1090000
mvsdmmc: no IRQ detect
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
mvCLAudioCodecRegGet: Error while reading register!
mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID!
Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list:
  #0: Marvell mv88fx_snd ALSA driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 124K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Pages: 1 [2]