Box fährt hoch und ist im Standby

Boxenweitwurf
da25qu
Beiträge: 2
Registriert: Donnerstag 13. Februar 2003, 09:23

Box fährt hoch und ist im Standby

Beitrag von da25qu »

Hallo ihr lieben da draußen,

ich habe hier ein Problem mit der BOX, ich denke es ist ein Hardware Problem. Das flashen war erfolgreich. Und sie lief sogar 2 Tage bis auf einmal, folgendes passierte. Sie fährt hoch und geht sofort in Standby.
Darauf hin habe ich mal mitgelogt was passiert und folgendes wird ausgegeben.

D-Box 2 flash driver (size->0x800000 mem->0x10000000)
CFI: Found no D-Box 2 flash memory device at location zero

was bedeutet es??? Wo kann das Problem liegen, gibt es noch Möglichkeiten?

Das komplette LOG sieht folgendermassen aus:

debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.2 mID 03
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-d5.22.ec.07.00.00-48
debug: HWrev 61 FPrev 0.23
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
dbox2:root> debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.5.3, My IP 192.168.5.5
debug: Sending TFTP-request for file C/yadd/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 201612
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


ppcboot 0.6.4 (Feb 8 2003 - 23:52:51)

Initializing...
CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-3d-52-da
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.5.3; our IP address is 192.168.5.5
Filename 'C/yadd/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1FD2E80 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.5.3; our IP address is 192.168.5.5
Filename 'C/yadd/tftpboot/logo-fb'.
Load address: 0x120000
Loading: #######
done
FB logo at: 0x0 (0x1FD2E80 bytes)
AVIA Frambuffer
Input: serial
Output: serial

Images:
1: cdk
2: yadd
3: debian
4: tiab
5: flash
Select image (1-5), other keys to stop autoboot: 0
sagem bmon 1.2
debug mode is enabled
BOOTP broadcast 1
TFTP from server 192.168.5.3; our IP address is 192.168.5.5
Filename 'C/yadd/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: #######################################################################
#######################################################################
done
## Booting Linux kernel at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 722641 Bytes = 705 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.20-dbox2 (Sinnlos98@athlon) (gcc version 3.2.1) #4 Sat Feb 8 2
3:53:06 2003
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0 root=/dev/nfs rw nfsroot=192.168.5.3:C/yadd/c
dkroot/ ip=192.168.5.5:192.168.5.3:::::off
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
Decrementer Frequency = 247500000/60
mpc8xx-wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
mpc8xx-wdt: keep-alive trigger activated (PITC: 0x2000)
Console: colour dummy device 80x25
Calibrating delay loop... 65.53 BogoMIPS
Memory: 30632k available (1256k kernel code, 404k data, 76k 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
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
i2c-core.o: i2c core module
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0380 is a SMC
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2 on SCC2, 00:50:9c:3d:52:da
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
CFI: Found no D-Box 2 flash memory device at location zero
Creating 6 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "flfs (ppcboot)"
0x00040000-0x00700000 : "root (cramfs)"
0x00700000-0x00800000 : "var (jffs2)"
0x00020000-0x00800000 : "flash without bootloader"
0x00000000-0x00800000 : "complete flash"
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, addr=192.168.5.5, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.5.5, domain=, nis-domain=(none),
bootserver=192.168.5.3, rootserver=192.168.5.3, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Looking up port of RPC 100003/2 on 192.168.5.3
Looking up port of RPC 100005/1 on 192.168.5.3
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 76k init
init started: BusyBox v0.61.pre (2003.02.08-21:32+0000) multi-caDetected STB:
Vendor: Sagem
Model: D-BOX2
[i2c-8xx]: mpc 8xx i2c init
i2c-core.o: adapter PowerPC 8xx I2C adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
event: init ...
i2c-core.o: driver FOR_PROBE_ONLY registered.
i2c-core.o: driver unregistered: FOR_PROBE_ONLY
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [PowerPC
8xx I2C adapter](pos. 0).
i2c-core.o: driver i2c audio/video switch driver registered.
i2c-core.o: client [CXA2126] registered to adapter [PowerPC 8xx I2C adapter](pos
. 1).
i2c-core.o: driver saa7126 registered.
i2c-core.o: client [saa7126] registered to adapter [PowerPC 8xx I2C adapter](pos
. 2).
$Id: cam.c,v 1.22 2003/01/14 10:26:36 jolt Exp $
/lib/modules/2.4.20-dbox2/misc/cam.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/cam.o: insmod /lib/modules/2.4.20-dbox2/misc/cam.
o failed
/lib/modules/2.4.20-dbox2/misc/cam.o: insmod cam failed
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 3
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt_fb failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt_lirc failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt_oss failed
Linux video capture interface: v1.00
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt_v4l2 failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_av failed
$Id: avia_napi.c,v 1.12 2003/01/18 00:52:35 obi Exp $
DVB: registering new adapter (C-Cube AViA GTX/eNX with AViA 500/600).
i2c-core.o: driver DVB I2C bridge registered.
DVB: registering frontend 0:0 (Atmel AT76c651(B) with DAT7021)...
i2c-core.o: client [dvb] registered to adapter [PowerPC 8xx I2C adapter](pos. 3)
.
dvb_i2c_bridge: enabled DVB i2c bridge to PowerPC 8xx I2C adapter
$Id: cam.c,v 1.22 2003/01/14 10:26:36 jolt Exp $
cam: mio address unknown
/lib/modules/2.4.20-dbox2/misc/cam.o: init_module: Invalid argument
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/cam.o: insmod /lib/modules/2.4.20-dbox2/misc/cam.
o failed
/lib/modules/2.4.20-dbox2/misc/cam.o: insmod cam_napi failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_av_napi failed
avia_av: $Id: avia_av_core.c,v 1.55 2003/01/18 01:22:10 obi Exp $
avia_av_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.20-dbox2/misc/avia_av.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod /lib/modules/2.4.20-dbox2/misc/
avia_av.o failed
/lib/modules/2.4.20-dbox2/misc/avia_av.o: insmod avia_gt_napi failed
Loading /share/keymaps/i386/qwertz/de-latin1.kmap.gz
gunzip: Short read
maybekillzombie(): decompressor child exited anormally with code 1.

Please press Enter to activate this console. [LCDFONT] initializing core...
[LCDFONT] adding font /share/fonts/micron_bold.ttf...OK (Micron/Bold)
[LCDFONT] Intializing font cache...
[LCDFONT] FTC_Face_Requester (Micron/Bold)
[camd] /dev/dvb/adapter0/ca0: No such file or directory
enigma, Copyright (C) dbox-Project
enigma comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome
to redistribute it under certain conditions.
It is licensed under the GNU General Public License,
Version 2

+ (0) Configuration
+ (1) d-Box LCD Hardware
[LCD] set brightness 130, contrast 32
+ (1) gRC
RC thread createted successfully
+ (1) GFBDC
/dev/fb/0: No such file or directory
framebuffer not available.
no framebuffer available
no active skin
CXA2126 found
Sending SIGKILL to all processes.
The system is halted. Press Reset or turn off power
System halt


Würde mich über eine Antwort sehr freuen.

ROBudus!
Viel SPaß beim basteln!!!
Reichi
Erleuchteter
Erleuchteter
Beiträge: 477
Registriert: Sonntag 7. Oktober 2001, 00:00

Beitrag von Reichi »

ucodes können nicht geladen werden (avia600.ux)
bzw sind sie oder gar das ganze jffs2 kaputt, neu flashen ist wohl das Beste...

oder maintenance benutzen um die ucodes nochmal hochzuladen, kannste ja mal testen
mfg,

Reichi
SoLaLa
Tuxboxer
Tuxboxer
Beiträge: 6119
Registriert: Mittwoch 3. April 2002, 00:32

Beitrag von SoLaLa »

warum bootest Du denn jetzt ne Yadd?
laß doch mal die Box ausm flash booten und poste das LOG hier

und warum war das ganze überhaupt dopplet gepostet?
never change a running system
da25qu
Beiträge: 2
Registriert: Donnerstag 13. Februar 2003, 09:23

Yadd oder flash ist egal

Beitrag von da25qu »

Es ist egal ob ich Yadd oder direkt vom flash boote die Meldungen sind die gleichen.
Habe probleme mit dem Server gehabt und wohl zweimal auf Submit getickert.

Das Problem hat sich nach einem Schütteln der Box erledigt.
Deswegen gehe ich davon aus, das ich ein Wackelkontakt oder eine kalte Lötstelle habe. Die Frage ist wo?

Was sagt mir die Zeile?

D-Box 2 flash driver (size->0x800000 mem->0x10000000)
CFI: Found no D-Box 2 flash memory device at location zero

darauf beziehen sich wohl die Fehlermeldungen?
Ich vermute mal es muß eine Lötstelle am Flash sein oder so, da er den ja beim hochfahren nicht findet. Wie gesagt einwenig auf die Box klopfen und sie fährt normal hoch und arbeitet fehlerfrei. Sehr seltsam

Danke für Hilfe