Irgendwie läuft Yadd nicht bei mir !!!!

Beitrag von **avesoft** » Dienstag 5. Februar 2002, 01:59

Also ich hab ne Nokia 2xI Avia500. Ich möchte mit Windoof die Yadd mal starten. Ich benutze als WinBoot von Field. Ich denke, das ich schon die richtigen einstellungen dort gemacht habe. Ich kann schon garnicht mehr zählen, wie oft ich die faq's und howto's gelesen habe. Und hier im Forum hab ich auch noch nix gefunden darüber. Also ich bekomme im BootManager folgende Meldungen:

debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-f0.33.1f.07.00.00-5d
debug: HWrev X5 SWrev 0.81
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.1, My IP 192.168.0.202
debug: Sending TFTP-request for file c/dbox2/yadd/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 224356
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

ppcboot 0.6.4 (Jan 10 2002 - 16:35:20)

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-18-c7-cc
FLASH: 8 MB
LCD driver (KS0713) initialized
LCD logo at: 0x80832 (0x1C20 bytes)
FB logo at: 0x8247A (0xDDD2 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
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.202
Filename 'c/dbox2/yadd/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: #######################################################################
##################################################

## Booting Linux kernel at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 616299 Bytes = 601 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: WATCHDOG RESET
debug: BMon V1.0 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-f0.33.1f.07.00.00-5d
debug: HWrev X5 SWrev 0.81
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.1, My IP 192.168.0.202
debug: Sending TFTP-request for file c/dbox2/yadd/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 224356
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000

ppcboot 0.6.4 (Jan 10 2002 - 16:35:20)

Initializing...
CPU: PPC823ZTnnA at 67 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: xxxxxxxxxxxxx
FLASH: 8 MB
LCD driver (KS0713) initialized
LCD logo at: 0x80832 (0x1C20 bytes)
FB logo at: 0x8247A (0xDDD2 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
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.202
Filename 'c/dbox2/yadd/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: #######################################################################
##################################################

## Booting Linux kernel at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 616299 Bytes = 601 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.2 (steffen@sr01.sth-serv.de) (gcc version 3.0.3) #1 Fri Jan 11
00:16:01 CET 2002
Boot arguments: console=ttyS0 root=/dev/nfs rw nfsroot=192.168.0.1:c/dbox2/yadd/
cdkroot/
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.0.1:c/dbox2/
yadd/cdkroot/
time_init: decrementer frequency = 251250000/60
mpc8xx-wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
mpc8xx-wdt: keep-alive trigger activated (PITC: 0x3000)
Console: colour dummy device 80x25
Calibrating delay loop... 66.56 BogoMIPS
Memory: 30584k available (1116k kernel code, 432k data, 68k init, 0k highmem)
Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0380 is a SMC
pty: 256 Unix98 ptys configured
block: queued sectors max/low 20218kB/6739kB, 64 slots per queue
loop: enabling 8 loop devices
eth0: CPM ENET Version 0.2, xx-xx-xx-xx-xx-xx
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)
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 192.168.0.1, my address is 192.168.0.202
IP-Config: Guessing netmask 255.255.255.0
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
devfs: v0.102 (20000622) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Looking up port of RPC 100003/2 on 192.168.0.1
Looking up port of RPC 100005/2 on 192.168.0.1
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 68k it
Bummer, can't write to log on /dev/tty5!
console=/dev/consoleinit started: BusyBox v0.60.1 (2002.01.06-17:12+0000) multi
-call Setting hostname
hostname: not found
Mounting anything
Starting inetd
Loading modules
Real Time Clock Driver v0.1
i2c-core.o: i2c core module
[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
mID: 01
feID: dd
fpID: 5a
enxID: ffffffff
gtxID: 0b
hwREV: 05
fpREV: 81
DEMOD: VES1893
i2c-core.o: driver i2c saa7126 driver registered.
i2c-core.o: client [i2c saa7126 chip] registered to adapter [](pos. 0).
event: init ...
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 1
).
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia500.ux'.
/lib/modules/2.4.2/misc/avia.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
/lib/modules/2.4.2/misc/avia.o: insmod /lib/modules/2.4.2/misc/avia.o failed
/lib/modules/2.4.2/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
/lib/modules/2.4.2/misc/cam.o: insmod /lib/modules/2.4.2/misc/cam.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
event: cleanup ...
/lib/modules/2.4.2/misc/cam.o: insmod dvb failed
event: init ...
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 1
).
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia500.ux'.
/lib/modules/2.4.2/misc/avia.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
/lib/modules/2.4.2/misc/avia.o: insmod /lib/modules/2.4.2/misc/avia.o failed
/lib/modules/2.4.2/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
/lib/modules/2.4.2/misc/cam.o: insmod /lib/modules/2.4.2/misc/cam.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
event: cleanup ...
/lib/modules/2.4.2/misc/cam.o: insmod tuner failed
gtx-core.c: init_gtx: gtxID 0b
gtx-core.c: init_gtx: loaded AViA GTX core driver
Console: switching to colour frame buffer device 90x36
fb0: AViA eNX/GTX Framebuffer frame buffer device
event: init ...
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 1
).
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia500.ux'.
/lib/modules/2.4.2/misc/avia.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
/lib/modules/2.4.2/misc/avia.o: insmod /lib/modules/2.4.2/misc/avia.o failed
/lib/modules/2.4.2/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
/lib/modules/2.4.2/misc/cam.o: insmod /lib/modules/2.4.2/misc/cam.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
event: cleanup ...
avia_vbi: version (Jan 12 2002-01:00:28)
avia_vbi: error - no demux found
/lib/modules/2.4.2/misc/gtx_vbi.o: init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters
/lib/modules/2.4.2/misc/gtx_vbi.o: insmod /lib/modules/2.4.2/misc/gtx_vbi.o fail
ed
$Id: gtx_capture.c,v 1.3 2001/12/01 06:37:06 gillem Exp $
gtx_pig: init
gtx_pig: WIDTH=160, S=0, HEIGHT=144
lcd.o: LCD driver (KS0713) module
Starting loopback device
/dev/dbox/rc0: No such file or directory

Please press Enter to activate this console.

BusyBox v0.60.1 (2002.01.06-17:12+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

# neutrino
NeutrinoNG $Id: neutrino.cpp,v 1.128 2002/01/11 00:09:10 McClean Exp $

1024k video mem
[FONT] initializing core...
[FONT] loading fonts...
[FONT] adding font /share/fonts/Arial.ttf...OK (Arial/Regular)
[FONT] adding font /share/fonts/Arial_Bold.ttf...OK (Arial/Bold)
[FONT] adding font /share/fonts/Arial_Italic.ttf...OK (Arial/Italic)
[FONT] adding font /share/fonts/Arial_Black.ttf...OK (Arial Black/Regular)
[FONT] Intializing font cache, using max. 4MB...
fbcon_setup: No support for fontwidth 8
fbcon_setup: type 0 (aux 0, depth

not supported
error while loading settings: /var/tuxbox/config/neutrino.conf
using defaults...

[FONT] FTC_Face_Requester (Arial/Regular)
[FONT] FTC_Face_Requester (Arial/Italic)
[FONT] FTC_Face_Requester (Arial/Bold)
[FONT] FTC_Face_Requester (Arial Black/Regular)
/dev/dbox/rc0: No such file or directory
#

So, kann mir mal einer bitte,bitte,bitte sagen, was ich falsch mache oder was da fehlt. Auf meiner Box läuft alles wunderbar, aber darum gehts mir ja nicht.

cu,
AVESOFT

Beitrag von **NoClue** » Dienstag 5. Februar 2002, 09:14

Kann es sein, dass Du vergessen hast, die Ucodes ins richtige Verzeichnis zu kopieren:

avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia500.ux'.

BTW, Du solltest die Ethernet-Adresse (00:50:....) löschen, da die für Deine Box eindeutig ist.

Beitrag von **avesoft** » Dienstag 5. Februar 2002, 15:52

Hmm, das sieht so aus, als wolle er die ucodes von der Box laden. Auf der Box ist bereits ein funktionierendes Image. Ich möchte aber von Platte aus starten mit Windows und WinBoot von Field.

Also ich starte Winboot mit diesen einstellungen:
#############################################
"BootP / TFTP - Server starten" = eingeschltet
Verzeichniss: c:\dbox2\yadd\tftpboot\ppcboot

"NFS - Server starten" = eingeschaltet
Verzeichniss: C:\dbox2\yadd\cdkroot

"RARP - Server starten" = ausgeschaltet

"COM-Port" = eingeschaltet bei 9600

Die Ucodes liegen bei mir in: C:\dbox2\yadd\cdkroot\ucodes
#############################################

So hab ich das gemacht und dann bekomme ich halt genau das, was ich ja oben schon gepostet hab. Dann auf Start und DBox Strom gegeben.

Beitrag von **NoClue** » Dienstag 5. Februar 2002, 16:00

Also wenn das eine neue yadd ist müssen die ucodes schon unter ../cdkroot/var/tuxbox/ucodes/ liegen.

Beitrag von **avesoft** » Dienstag 5. Februar 2002, 16:44

Ich hab die neueste Yadd. Und du hast recht unter "C:\dbox2\yadd\cdkroot\var\tuxbox\ucodes" habe ich nix. Werde es nachher mal testen. Melde mich dann nochmal ob es gefunzt hat oder nicht.