Problem beim flashen

Wie blitze ich ein Bild - Permanent Outgoing Incomes
Antworten
karldall_
Neugieriger
Neugieriger
Beiträge: 4
Registriert: Donnerstag 12. Juni 2008, 15:57

Problem beim flashen

Beitrag von karldall_ »

Hallo, ich hab hier von nem Bekannten ne Sagem 2xi Kabelbox bekommen, und wollte nen aktuelles Image aufspielen. Im debug ist die box schon. Jetzt bekomme ich u.a. dieses errorlog:


debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.0 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID http://Hallenberg.com
debug: HWrev 41 FPrev 0.23
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: autoboot aborted from terminal
dbox2:root> boot net net net net net net net net net net
debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.178.21, My IP 192.168.178.202
debug: Sending TFTP-request for file u-boot
will verify ELF image, start= 0x800000, size= 140064
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


U-Boot 1.3.1 (Tuxbox - Hallenberg.com) (Dec 23 2007 - 22:22:21)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Sagem, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.202
Filename 'u-boot'.
Load address: 0x100000
Loading: Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.202
Filename 'logo-lcd'.
Load address: 0x100000
Loading: ##
done
Bytes transferred = 7680 (1e00 hex)
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.202
Filename 'u-boot'.
Load address: 0x100000
Loading: Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.202
Filename 'logo-fb'.
Load address: 0x100000
Loading: ####################################
done
Bytes transferred = 179877 (2bea5 hex)

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select option (1-3), other keys to stop autoboot: 0
Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.202
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: #################################################################
##########################################################
done
Bytes transferred = 626108 (98dbc hex)
Using SCC ETHERNET device
TFTP from server 192.168.178.21; our IP address is 192.168.178.20X
Filename 'u-initrd'.
Load address: 0x400000
Loading: #################################################################
#################################################
done
Bytes transferred = 579075 (8d603 hex)
............................................................... done
Un-Protected 63 sectors
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 626044 Bytes = 611.4 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00400000 ...
Image Name: Ramdisk Image
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 579011 Bytes = 565.4 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 01f21000, end 01fae5c3 ... OK
Linux version 2.4.36-dbox2 (Hallenberg.com) (gcc version 3.4.6) #2 So 6. Jan 18:22:41 CET 2008
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0 root=/dev/ram rw ip=192.168.178.202:192.168.178.21:::::off
Decrementer Frequency = 247500000/60
m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
m8xx_wdt: keep-alive trigger installed (PITC: 0x2000)
Console: colour dummy device 80x25
Calibrating delay loop... 65.74 BogoMIPS
Memory: 30356k available (1048k kernel code, 324k data, 72k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 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
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)
CPM UART driver version 0.04
ttyS0 at 0x0280 is on SMC1 using BRGÿttyS1 at 0x0380 is on SMC2 using BRG2
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:38:fe:5e
RAMDISK driver initialized: 16 RAM disks of 3333K size 1024 blocksize
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit bank
Intel/Sharp Extended Query Table at 0x0035
cfi_cmdset_0001: Erase suspend on write enabled
Creating 6 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "FLFS (U-Boot)"
0x00040000-0x006a0000 : "root (rootfs)"
0x006a0000-0x00800000 : "var (jffs2)"
0x00020000-0x00800000 : "Flash without bootloader"
0x00000000-0x00800000 : "Complete Flash"
Linux video capture interface: v1.00
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
kernel BUG at page_alloc.c:228!
Oops: Kernel Mode Software FPU Emulation, sig: 8
NIP: C002B758 XER: 8000004F LR: C002B758 SP: C01DBE20 REGS: c01dbd70 TRAP: 1000 Not tainted
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c01da000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: C002B758 C01DBE20 C01DA000 00000020 00001032 00000001 FFFFCA28 C0129D9F
GPR08: 00000000 C0140000 00000002 C01DBD20 C0140000 00031CBC 01FFB400 00000001
GPR16: FFFFFFFF 007FFF00 01FF5940 00000000 000001F0 C0122BF8 C0120000 C014A870
GPR24: C0140000 00000000 C0122970 00001FD8 00000003 00000008 C01229CC C01CBB28
Call backtrace:
C002B758 C002BA80 C002BF5C C00283F4 C0028324 C004B600 C004CF44
C00B22FC C00C6728 C013AF08 C013AD6C C013B1F4 C00022A0 C0005D5C
Kernel panic: Attempted to kill init!
<0>Rebooting in 180 seconds..


was ist denn an dem teil kaputt ?
danke schonmal
-karl
gurgel
Tuxboxer
Tuxboxer
Beiträge: 2473
Registriert: Dienstag 8. Oktober 2002, 21:06
Kontaktdaten:

Re: Problem beim flashen

Beitrag von gurgel »

CPU/RAM
karldall_
Neugieriger
Neugieriger
Beiträge: 4
Registriert: Donnerstag 12. Juni 2008, 15:57

Re: Problem beim flashen

Beitrag von karldall_ »

kann man da was machen ? bzw. wer kann ?
danke-
karl
Antworten