Sagem defekt?

Anlaufschwierigkeiten? Was ist was? Worum geht's?
Burak80
Beiträge: 2
Registriert: Freitag 19. Januar 2007, 14:50

Sagem defekt?

Beitrag von Burak80 »

Hallo,
brauche Hilfe.
Habe von einem Bekannten einen SAGEM bekommen. 1xI.
Und zwar beim Einschalten kommt eine Weltkugel im Display (LCD), die sich dreht und dann stehenbleibt (einfriert) Im TV ist nur ein Underline was blinkt. Im Forum habe ich nichts gefunden. Hat die Box einen Hardware fehler?
Mit dem Bootmanager habe ich einmal diese Meldung bekommen:

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-46.4b.56.07.00.00-c8
debug: HWrev 21 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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/sagem-dbox2/kernel/os in Flash-FS
debug: Got Block #0052

will verify ELF image, start= 0x800000, size= 202740
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Jul 12 2002 - 21:12:06)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Watchdog enabled
Board: DBOX2, Sagem
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: . done.
LCD: ready
FB: loading - ready
In: serial
Out: serial
Err: serial

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS load compleate: 582785 bytes loaded to 0x100000
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 582721 Bytes = 569 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.19 (tuxbox@linux) (gcc version 3.2) #1 Die Sep 3 21:32:44 CEST
2002
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 console=ttyS0
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: 30928k available (1016k kernel code, 360k data, 64k 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.12a (20020514) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications
AB.
i2c-core.o: i2c core module
i2c-proc.o version 2.6.1 (20010825)
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:33:9e:e6
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
CFI: Found no D-Box 2 flash memory device at location zero
Using buffer write method
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"
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)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 64k init
init started: BusyBox v0.61.pre (2002.08.18-11:52+0000) multi-ca[i2c-8xx]: mpc
8xx i2c init
i2c-core.o: adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
i2c-core.o: driver FOR_PROBE_ONLY registered.
i2c-core.o: driver unregistered: FOR_PROBE_ONLY
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 3
event: init ...
i2c-core.o: driver i2c audio/video switch driver registered.
i2c-core.o: client [CXA2126] registered to adapter [](pos. 0).
i2c-core.o: driver i2c saa7126 driver registered.
i2c-core.o: client [i2c saa7126 chip] registered to adapter [](pos. 1).
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
Lade alternativen dvb_demux.o
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
der moment ist gekommen...
i2c-core.o: driver DBox2-CAM registered.
CAM: attaching CAM at 0x6e
i2c-core.o: client [DBOX2-CAM] registered to adapter [](pos. 3).
CAM: attached to adapter
Lade alternativen dmxdev.o
write 1 event's ...
write 1 event's ...
Lade alternativen dvb_frontend.o
Lade alternativen avia_gt.o
avia_gt_core: $Id: avia_gt_core.c,v 1.21 2002/08/22 13:39:33 Jolt Exp $
avia_gt_core: autodetecting chip type... AViA eNX found
avia_gt_enx: $Id: avia_gt_enx.c,v 1.13 2002/09/02 19:25:37 neBox Exp $
avia_gt_dmx: $Id: avia_gt_dmx.c,v 1.106 2002/09/04 14:26:49 Jolt Exp $
avia_gt_dmx: Successfully loaded ucode V0.14
avia_gt_dmx: RISC mem map size: 2048
ENX-INITed -> 0
there MIGHT be no TS :(
avia_gt_dmx: warning, misaligned queue 0 (is 0x32A00, size 65536), aligning...
avia_gt_gv: $Id: avia_gt_gv.c,v 1.22 2002/08/22 13:39:33 Jolt Exp $
avia_gt_gv: set_input_size (width=720, height=576)
avia_gt_pcm: $Id: avia_gt_pcm.c,v 1.17 2002/08/22 13:39:33 Jolt Exp $
avia_gt_capture: $Id: avia_gt_capture.c,v 1.22 2002/08/22 13:39:33 Jolt Exp $
avia_gt_pig: $Id: avia_gt_pig.c,v 1.28 2002/08/22 13:39:33 Jolt Exp $
avia_gt_ir: $Id: avia_gt_ir.c,v 1.19 2002/08/22 13:39:33 Jolt Exp $
avia_gt_core: Loaded AViA eNX/GTX driver
Init VES1993
i2c-core.o: driver VES1993 DVB DECODER registered.
i2c-core.o: client [VES1993] registered to adapter [](pos. 4).
i2c-core.o: driver sp5659/tsa5059 tuner driver registered.
i2c-core.o: client [DBox2 Tuner Driver] registered to adapter [](pos. 5).
VES1993: sp5659 tuner found
Lade alternativen avia_gt_napi.o
avia_gt_napi: $Id: avia_gt_napi.c,v 1.103 2002/09/04 13:25:01 neBox Exp $
avia_gt_napi: warning, misaligned queue 0 (is 32a00, size 10000), aligning...
avia_gt_vbi: $Id: avia_gt_vbi.c,v 1.16 2002/08/22 13:39:33 Jolt Exp $
avia_gt_vbi: got demux C-Cube - AViA eNX/GTX
avia_gt_fb: $Id: avia_gt_fb_core.c,v 1.36 2002/08/22 13:39:33 Jolt Exp $
avia_gt_gv: set_input_mode (mode=2)
avia_gt_gv: set_input_size (width=720, height=576)
avia_gt_gv: set_input_mode (mode=2)
avia_gt_gv: set_input_size (width=720, height=576)
avia_gt_gv: set_input_mode (mode=2)
avia_gt_gv: set_input_size (width=720, height=576)
Console: switching to colour frame buffer device 82x32
avia_gt_fb: fb0: AViA eNX/GTX Framebuffer frame buffer device
avia_oss: $Id: avia_gt_oss.c,v 1.8 2002/08/22 13:39:33 Jolt Exp $
/etc/init.d/rcS: /var/tuxbox/start_neutrino_au: No such file or directory

Please press Enter to activate this console. help


BusyBox v0.61.pre (2002.08.18-11:52+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands
Tommy
Tuxboxer
Tuxboxer
Beiträge: 4332
Registriert: Dienstag 7. Mai 2002, 17:04

Beitrag von Tommy »

Code: Alles auswählen

/etc/init.d/rcS: /var/tuxbox/start_neutrino_au: No such file or directory
Was auch immer das für ein Image ist - neutrino soll wahrscheinlich in start_neutrino_au gestartet werden. start_neutrino_au (als skript) existiert nicht.

Falls Du die IP Adresse der Box kennst, kannst Du per FTP nachschauen und zumindest die ucodes sichern.

anschließend flash Dir ein JTG Image.
---------------------------
Alle weiteren Infos findest Du im WIKI
Bitte vor dem posten Boardregeln lesen und verstehen!
Wie erstelle ich ein Bootlog? Wo finde ich die FAQ?
Burak80
Beiträge: 2
Registriert: Freitag 19. Januar 2007, 14:50

Sagem defekt?

Beitrag von Burak80 »

Danke für die schnelle Antwort.
Werde es mal versuchen.