Sagem Sat 2xI Kanalsuche erfolglos Bitte um Hilfe

[Bea1]

Hallo.
Hardware: Sagem Dbox2 SAT 2x Intel Avia 600
Software : Neutrino alexW2xBaseimageV1.6.9

Problem : Meldung Es wurden keine Kanäle gefunden.
Im Service Menue habe ich Kanalsuche gestartet, aber er zeigt Suche an beendet aber erfolglos.

Zeigt weder Transponder, Frequenz, Anbieter, Kanal an.


Bei der UCode Prüfung zeigt sich:
AVIA 500: not found (habe ich rausgelöscht)
AVIA 600: avia600vb022
UCode: using built-in (habe ich auch mal rausgelöscht)
CaM-Alpha: cam_01_02_105E

werden noch weitere Infos benötigt ?

Bitte um Hilfe!

[DieMade]

Poste mal ein komplettes Bootlog inkl. Senderscan bitte.

[Bea1]

Danke für die Antwort, aber ...

wie geht das mit dem Bootlog ("Newbie") ?

[Dietmar]

Guckst Du FAQ.

[Bea1]

also falls ich das jetzt richtig gemacht habe ?! :

ist das das gewünschte log ?

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 01-27.0a.6a.03.00.00-dc
debug: HWrev 01 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.0.40, My IP 192.168.0.30
debug: Sending TFTP-request for file C/Programme/DBoxBoot/ppcboot_writeflash
will verify ELF image, start= 0x800000, size= 201596
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


ppcboot 0.6.4 (Apr 11 2002 - 16:10:44)

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-30-c5-2d
FLASH: 8 MB
LCD driver (KS0713) initialized
BOOTP broadcast 1
TFTP from server 192.168.0.40; our IP address is 192.168.0.30
Filename 'C/Programme/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##

LCD logo at: 0x130000 (0x1F9FFC0 bytes)
BOOTP broadcast 1
TFTP from server 192.168.0.40; our IP address is 192.168.0.30
Filename 'C/Programme/tftpboot/logo-fb'.
Load address: 0x120000
Loading: #########

FB logo at: 0x0 (0x1FC0000 bytes)
AVIA Frambuffer
Input: serial
Output: serial


1: Console on ttyS0
2: Console on null
3: Console on framebuffer
Select (1-3), other keys to stop autoboot: 0
BOOTP broadcast 1
TFTP from server 192.168.0.40; our IP address is 192.168.0.30
Filename 'C/Programme/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: T T T T T T T T T
Retry count exceeded; starting again
BOOTP broadcast 2


ok?

[Bea1]

Werden sonst noch Angaben benötigt ? Ach ja ein anderer Receiver läuft am selben Satkabel. Satempfang ist ok.

[Dietmar]

Fürs Bootlog: Nur das com-terminal im Bootmanager aktivieren, alle Server ausmachen.
Das Log sieht aus wie eins vom flashen, bei dem das Nullmodem locker ist.

[Bea1]

besser ? :

BOOTP broadcast 260
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 01-27.0a.6a.03.00.00-dc
debug: HWrev 01 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= 203620
verify sig: 262
Branching to 0x40000


PPCBoot 1.1.6 (TuxBox) (Mar 13 2003 - 12:11:32)

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: . .
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
...............................................................
Un-Protected 63 sectors
### FS (cramfs) loading 'vmlinuz' to 0x100000
### FS load compleate: 641754 bytes loaded to 0x100000
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 641690 Bytes = 626 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.20-dbox2 (von alexW) Wer Kernels nachmacht, oder faelscht, wir
d bestraft ;-) #1 Fre Apr 11 11:35:47 CEST 2003
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.74 BogoMIPS
Memory: 30796k available (1132k kernel code, 380k data, 60k 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, 2002 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:30:c5:2d
Linux video capture interface: v1.00
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
cfi_cmdset_0001: Erase suspend on write enabled
Using word write method
Creating 6 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "flfs (ppcboot)"
0x00040000-0x00720000 : "root (cramfs)"
0x00720000-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
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: 60k init
Starting pid 10, console /dev/console: '/etc/init.d/rcS' multi-ca
Using /lib/modules/2.4.20-dbox2/misc/event.o
event: init ...
Using /lib/modules/2.4.20-dbox2/misc/tuxbox.o
Using /lib/modules/2.4.20-dbox2/misc/dvb-core.o
SIOCADDRT: Invalid argument
Using /lib/modules/2.4.20-dbox2/misc/dbox2_i2c.o
[i2c-8xx]: mpc 8xx i2c init
i2c-core.o: adapter PowerPC 8xx I2C adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
Using /lib/modules/2.4.20-dbox2/misc/dbox2_fp.o
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [PowerPC
8xx I2C adapter](pos. 0).
Using /lib/modules/2.4.20-dbox2/misc/dbox2_fp_input.o
Using /lib/modules/2.4.20-dbox2/misc/avs.o
i2c-core.o: driver i2c audio/video switch driver registered.
i2c-core.o: client [CXA2126] registered to adapter [PowerPC 8xx I2C adapter](pos
. 1).
Using /lib/modules/2.4.20-dbox2/misc/saa7126.o
i2c-core.o: driver saa7126 registered.
i2c-core.o: client [saa7126] registered to adapter [PowerPC 8xx I2C adapter](pos
. 2).
Using /lib/modules/2.4.20-dbox2/misc/lcd.o
Using /lib/modules/2.4.20-dbox2/misc/cam.o
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface
$Id: cam.c,v 1.22 2003/01/14 10:26:36 jolt Exp $
i2c-core.o: driver DBox2-CAM registered.
CAM: attaching CAM at 0x6e
i2c-core.o: client [DBOX2-CAM] registered to adapter [PowerPC 8xx I2C adapter](p
os. 3).
CAM: attached to adapter PowerPC 8xx I2C adapter
Using /lib/modules/2.4.20-dbox2/misc/dvb_i2c_bridge.o
Using /lib/modules/2.4.20-dbox2/misc/avia_napi.o
$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.
i2c-core.o: client [dvb] registered to adapter [PowerPC 8xx I2C adapter](pos. 4)
.
dvb_i2c_bridge: enabled DVB i2c bridge to PowerPC 8xx I2C adapter
Using /lib/modules/2.4.20-dbox2/misc/cam_napi.o
$Id: cam_napi.c,v 1.5 2003/01/14 08:43:17 jolt Exp $
Using /lib/modules/2.4.20-dbox2/misc/dbox2_fp_napi.o
[LCDFONT] initializing core...
[LCDFONT] adding font /share/fonts/micron.ttf...OK (Micron/Regular)
[LCDFONT] Intializing font cache...
[LCDFONT] FTC_Face_Requester (Micron/Regular)
Using /lib/modules/2.4.20-dbox2/misc/avia_av.o
avia_av: $Id: avia_av_core.c,v 1.62 2003/05/11 02:42:58 obi Exp $
avia_av_event: $Id: avia_av_event.c,v 1.6 2003/04/17 07:29:48 obi Exp $
avia_av_proc: $Id: avia_av_proc.c,v 1.6 2003/05/26 03:11:28 obi Exp $
Using /lib/modules/2.4.20-dbox2/misc/avia_gt.o
avia_gt_core: $Id: avia_gt_core.c,v 1.35 2003/04/14 00:13:10 obi Exp $
avia_gt_core: autodetecting chip type... AViA eNX found
avia_gt_enx: $Id: avia_gt_enx.c,v 1.17 2003/04/14 00:13:10 obi Exp $
write 1 event's ...
write 1 event's ...
avia_gt_accel: $Id: avia_gt_accel.c,v 1.15 2003/01/14 23:59:32 jolt Exp $
avia_gt_dmx: $Id: avia_gt_dmx.c,v 1.174 2003/05/25 23:54:25 woglinde Exp $
avia_gt_dmx: No firmware found at /var/tuxbox/ucodes/ucode.bin, using compiled-i
n version.
avia_gt_dmx: Successfully loaded ucode v0014
avia_gt_dmx: warning, misaligned queue 0 (is 0x32A00, size 65536), aligning...
avia_gt_gv: $Id: avia_gt_gv.c,v 1.31 2003/04/14 00:13:10 obi Exp $
avia_gt_gv: set_input_size (width=720, height=576)
avia_gt_pcm: $Id: avia_gt_pcm.c,v 1.23 2003/04/14 00:13:10 obi Exp $
avia_gt_capture: $Id: avia_gt_capture.c,v 1.27 2003/04/14 00:13:10 obi Exp $
avia_gt_pig: $Id: avia_gt_pig.c,v 1.35 2003/04/14 00:13:10 obi Exp $
avia_gt_ir: $Id: avia_gt_ir.c,v 1.23 2003/04/14 00:13:10 obi Exp $
avia_gt_vbi: $Id: avia_gt_vbi.c,v 1.23 2003/04/25 05:27:09 obi Exp $
avia_gt_core: Loaded AViA eNX/GTX driver
Using /lib/modules/2.4.20-dbox2/misc/avia_gt_fb.o
avia_gt_fb: $Id: avia_gt_fb_core.c,v 1.45 2003/04/14 00:13:10 obi 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
Using /lib/modules/2.4.20-dbox2/misc/avia_gt_lirc.o
avia_gt_lirc: $Id: avia_gt_lirc.c,v 1.7 2003/04/14 00:13:10 obi Exp $
Using /lib/modules/2.4.20-dbox2/misc/avia_gt_oss.o
avia_oss: $Id: avia_gt_oss.c,v 1.18 2003/04/17 07:29:48 obi Exp $
Using /lib/modules/2.4.20-dbox2/misc/avia_gt_v4l2.o
avia_gt_v4l2: $Id: avia_gt_v4l2.c,v 1.8 2003/04/14 00:13:10 obi Exp $
Using /lib/modules/2.4.20-dbox2/misc/ves1x93.o
DVB: registering frontend 0:0 (VES1993)...
Using /lib/modules/2.4.20-dbox2/misc/at76c651.o
Using /lib/modules/2.4.20-dbox2/misc/avia_av_napi.o
avia_av_napi.c: $Id: avia_av_napi.c,v 1.17 2003/04/17 07:29:48 obi Exp $
Using /lib/modules/2.4.20-dbox2/misc/avia_gt_napi.o
avia_gt_napi: $Id: avia_gt_napi.c,v 1.180 2003/05/11 02:42:59 obi Exp $
avia_gt_napi: hw section filtering enabled.
cdkVcInfo $Id: cdkVcInfo.c,v 1.3 2003/05/24 22:04:36 alexW Exp $

$Id: sectionsd.cpp,v 1.166 2003/03/14 04:27:55 obi Exp $
caching 504 hours
events are old 60min after their end time
[camd] no card is in slot #2
[camd] a card is in slot #1
[camd] ca system id: 0000
$Id: zapit.cpp,v 1.314 2003/05/22 20:41:31 digi_casi Exp $
/var/tuxbox/config/zapit/bouquets.xml: No such file or directory
$Id: controld.cpp,v 1.106 2003/04/23 13:00:12 alexw Exp $

[controld] Boxtype detected: (3, Sagem D-BOX2)
set event: 00000009
[nhttpd] Neutrino HTTP-Server starting..
[neutrino] NeutrinoNG $Id: neutrino.cpp,v 1.456 2003/05/25 08:42:06 alexw Exp $

[neutrino] frameBuffer Instance created
1024k video mem
avia_gt_gv: set_input_mode (mode=2)
avia_gt_gv: set_input_size (width=720, height=576)
[neutrino] enable flash
[neutrino] Software update enabled
[lcdd] time-skin not found -> using default...
[lcdd] weekday-skin not found -> using default...
[lcdd] date-skin not found -> using default...
[lcdd] month-skin not found -> using default...
[LCDFONT] initializing core...
[LCDFONT] adding font /share/fonts/micron.ttf...OK (Micron/Regular)
[LCDFONT] Intializing font cache...
[LCDFONT] FTC_Face_Requester (Micron/Regular)
[neutrino] menue setup
[CHTTPUpdater] HTTP-Basepath: http://dboxupdate.berlios.de/images/
[CHTTPUpdater] Image-Filename: cdk.cramfs
[CHTTPUpdater] Version-Filename: cdk.cramfs.version
loading locales: scandir: No such file or directory
[neutrino] control event register
[neutrino] sectionsd event register
[neutrino] zapit event register
[neutrino] timerd event register
[sectionsd] getUTC: read: Connection timed out
[sectionsd] getUTC: read: Connection timed out

[DieMade]

Einen Senderscan hättest Du auch noch machen können

Aber "[camd] ca system id: 0000" ist schon *sehr* merkwürdig.

Ist das evtl. das HEAD-Image (neutrino.cramfs)? Was sagt Neutrino unter "Service - Software-Aktualisierung"?

[mash4077]

Ist das evtl. das HEAD-Image (neutrino.cramfs)?

ich würde sagen ja.

Vielleicht den Senderscan noch mal mit eigener ucode.bin ausprobieren.

avia_gt_napi: hw section filtering enabled.

Scheint ja auf enx noch nicht so gut zu laufen.

Gruß
mash

[DieMade]

Ich würde dann erstmal auf das Release-Image wechseln, um die Box als Fehlerquelle ausschließen zu können.

[Bea1]

Beim Loggen konnte ich leider keinen Sendersuchlauf machen - die Box stand da einfach .

Unter Software-Aktualisierung:

Updatemodus internet
-- instalierte Version --
Datum 26.05.03
Uhrzeit 10:54
Basisimage 1.6
ImageTyp Snapshot

[mash4077]

-- instalierte Version --
Datum 26.05.03
Uhrzeit 10:54
Basisimage 1.6
ImageTyp Snapshot[/b]

Na dann mach mal was DieMade vorgeschlagen hat.

Gruß
mash

P.S. wo haste denn den Snapshot ausgegraben?

[Bea1]

mal ne böde Frage wo bekomme ich ein"Release Image" bzw. was ist das ?

[mash4077]

Hi,

ein Release-Image ist ein vom "Erzeuger" sozusagen zum Gebrauch freigebenes Image, da es soweit als funktionstüchtig und stabil in Erscheinung getreten ist. Wenn Du beim Betrieb von einem Release-Image Probleme hast, dann wird man versuchen Dir zu helfen.

Ein Snapshot-Image ist im Gegensatz dazu halt eine Kurzaufnahme eines gewissen weiteren/neueren Entwicklungsstands des aktuellen Release-Image. Hier gibt es keine Unterstützung bei Problemen.

Hier gibt es das aktuelle alexW-Image:
http://dboxupdate.berlios.de/

Gruß
mash