Hallo!
Meine neue Qbox bleibt nach dem Boot Logo leider hängen :2:.
Auch das Aufspielen der Firmware über die serielle Schnittstelle hilft leider nicht.
Meine neue Qbox bleibt nach dem Boot Logo leider hängen :2:.
Auch das Aufspielen der Firmware über die serielle Schnittstelle hilft leider nicht.
Code:
U-Boot 1.2.0 (Apr 29 2008 - 12:11:35)
CPU: IBM PowerPC STBx25xx(51510950) at 252 MHz (PLB=63)
16 kB I-Cache 8 kB D-Cache
Board: QBOX ONE
I2C: ready
DRAM: 64 MB
FLASH: 512 kB
NAND: NanD_Command (ReadID) got ec 56
Flash chip found:
Manufacturer ID: 0xEC, Chip ID: 0x56 (Samsung K9F1216U0A)
1 flash chips found. Total nand_chip size: 64 MB
devices_init
i2c_init
drv_video_init
I2c read: failed 4
failed.
checking welcome image... ok.
clear screen.
drv_system_initjumptable
console
IDE: IDE detected on IOADDR: f2000000
ide reset not yet implemented
ide reset not yet implemented
Bus 0: not available
NAND read: device 0 offset 62783488, size 131072 ...
131072 bytes read: OK
I2c read: failed 4
failed.
Rear Button Released
Hit any key to stop autoboot: 2 1 0
Launching Linux...
NAND read: device 0 offset 62914560, size 524288 ...
524288 bytes read: OK
NAND read: device 0 offset 63963136, size 2097152 ...
2097152 bytes read: OK
## Booting image at 037f0000 ...
Image Name: Linux Kernel Image
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1432847 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.6.17-duodvb (root@localhost.localdomain) (gcc version 3.4.4) #1 Mon May 5 14:52:42 CEST 2008
Duolabs DVB Board http://www.duolabs.com
Built 1 zonelists
Kernel command line: console=ttyS2,115200 root=/dev/mtdblock/0 panic=10
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 61708k available (2296k kernel code, 804k data, 92k init, 0k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
squashfs: version 3.1 + autolzma (2006/10/05) Phillip Lougher
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered (default)
IBM GPIO driver version 07.25.02
IBM GPIO driver version 07.25.02
GPIO #0 at 0xc505e000
Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 20) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 21) is a 16550A
serial8250: ttyS2 at MMIO 0x0 (irq = 22) is a 16550A
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
NET: Registered protocol family 24
dm9000 Ethernet Driver
dm9000: 16 bit io datasize.
dm9000: Invalid ethernet MAC address feched from srom, tring bios
eth0: dm9000 at c5060000,c5062004 IRQ 26 MAC: 00:19:28:92:3d:3a
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
IBM Redwood 4/6 IDE driver version 2.1 S
detected IOADDR: f2000000/f4000000
DMA addr: fce00000
using irq 25
NAND device: Manufacturer ID: 0xec, Chip ID: 0x56 (Samsung NAND 64MiB 3,3V 16-bit)
Scanning device for bad blocks
Creating 8 MTD partitions on "NAND 64MiB 3,3V 16-bit":
0x00000000-0x01000000 : "root"
0x01000000-0x038e0000 : "var"
0x038e0000-0x03ae0000 : "options0"
0x03ae0000-0x03be0000 : "options1"
0x03be0000-0x03c00000 : "logo"
0x03c00000-0x03c80000 : "bs1"
0x03c80000-0x03d00000 : "bs2"
0x03d00000-0x03f00000 : "kernel"
i2c /dev entries driver
IBM IIC driver v2.1
ibm-iic0: using standard (100 kHz) mode
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
end_request: I/O error, dev mtdblock0, sector 2
EXT3-fs: unable to read superblock
end_request: I/O error, dev mtdblock0, sector 2
EXT2-fs: unable to read superblock
end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
end_request: I/O error, dev mtdblock0, sector 8
Buffer I/O error on device mtdblock0, logical block 1
end_request: I/O error, dev mtdblock0, sector 8
Buffer I/O error on device mtdblock0, logical block 1
end_request: I/O error, dev mtdblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
end_request: I/O error, dev mtdblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
end_request: I/O error, dev mtdblock0, sector 24
Buffer I/O error on device mtdblock0, logical block 3
end_request: I/O error, dev mtdblock0, sector 24
Buffer I/O error on device mtdblock0, logical block 3
end_request: I/O error, dev mtdblock0, sector 0
SQUASHFS error: sb_bread failed reading block 0x0
end_request: I/O error, dev mtdblock0, sector 0
FAT: unable to read boot sector
VFS: Cannot open root device "mtdblock/0" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
<0>Rebooting in 10 seconds..<NULL>
