Ich habe ein Problem mit meiner dbox2 avia500 gtx
ich kriege nach dem booten nur ein schwarz-weiß bild und nichts geht...
hier mein log:
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-19-74-a4
FLASH: 8 MB
LCD driver (KS0713) initialized
LCD logo at: 0x80833 (0x1E00 bytes)
FB logo at: 0x8265B (0xA825 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.100; our IP address is 192.168.0.201
Filename 'C/dbox/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.100:C/dbox/cdkr
oot/
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.100:C/dbox
/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, 00:50:9c:19:74:a4
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.100, my address is 192.168.0.201
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.100
Looking up port of RPC 100005/2 on 192.168.0.100
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 68k in
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
modprobe: Can't locate module rtc
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
modprobe: Can't locate module saa7126
event: init ...
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 0
).
avia_core.c: load_dram_image: Microcode verify: 237 errors.
/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
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. 1).
CAM: attached to adapter
i2c-core.o: driver i2c audio/video switch driver registered.
i2c-core.o: client [CXA2092] registered to adapter [](pos. 2).
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_wait
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_wr
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_command
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_rd
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_flush_pcr
/lib/modules/2.4.2/misc/dvb.o: insmod /lib/modules/2.4.2/misc/dvb.o failed
i2c-core.o: client [CXA2092] unregistered.
i2c-core.o: driver unregistered: i2c audio/video switch driver
CAM: detach_client
i2c-core.o: client [DBOX2-CAM] unregistered.
i2c-core.o: driver unregistered: DBox2-CAM
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
event: cleanup ...
/lib/modules/2.4.2/misc/dvb.o: insmod dvb failed
modprobe: Can't locate module tuner
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. 0
).
avia_core.c: load_dram_image: Microcode verify: 227 errors.
/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
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. 1).
CAM: attached to adapter
i2c-core.o: driver i2c audio/video switch driver registered.
i2c-core.o: client [CXA2092] registered to adapter [](pos. 2).
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_wait
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_wr
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_command
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_rd
/lib/modules/2.4.2/misc/dvb.o: unresolved symbol avia_flush_pcr
/lib/modules/2.4.2/misc/dvb.o: insmod /lib/modules/2.4.2/misc/dvb.o failed
i2c-core.o: client [CXA2092] unregistered.
i2c-core.o: driver unregistered: i2c audio/video switch driver
CAM: detach_client
i2c-core.o: client [DBOX2-CAM] unregistered.
i2c-core.o: driver unregistered: DBox2-CAM
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.
das wurde mit der neusten yadd-version erstellt...
vielleicht kann mir jemand helfen, wenn das Problem bekannt sein sollte (Suchfunktion habe ich bereits benutzt...)
Vielen Dank im Vorraus!!!
Grüße
privat
