jetzt bin ich drann! Meine erste selbst kompilierte YADD :)
Alles hat bis jetzt Prima funktioniert (kleine probleme schon gelöst mit suche im Forum)
Jetzt kriege ich aber beim booten ein paar "insmod aviaxyz failed" und dann bleibt die Kiste stehen. Ist mein YADD doch nicht so toll?
Hier der LOG: (Ja und die ucodes sind drinne!!! :) (scheint ein standard fehler quelle wenn mann sucht)
[/quote]ppcboot 0.6.4 (Jan 28 2003 - 04:47:59)
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-XX-XX-XX
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.1.105; our IP address is 192.168.1.10
Filename '/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1FD2AD8 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.1.105; our IP address is 192.168.1.10
Filename '/tftpboot/logo-fb'.
Load address: 0x120000
Loading: ###
done
FB logo at: 0x0 (0x1FD2AD8 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.1.105; our IP address is 192.168.1.10
Filename '/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: 722708 Bytes = 705 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.20-dbox2 (tuxbox@luzy) (gcc version 3.2.2) #1 Sun Mar 16 22
:14:48 CET 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.1.105:/cdkro
ot/ ip=192.168.1.10:192.168.1.105::255.255.255.0:::off
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 67 busfreq = 67
WARNING: NEW intfreq = 67000000 busfreq = 67000000
Decrementer Frequency = 251250000/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... 66.76 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:1e:08:bc
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
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: Complete:
device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.1.10, domain=, nis-domain=(none),
bootserver=192.168.1.105, rootserver=192.168.1.105, 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.1.105
Looking up port of RPC 100005/1 on 192.168.1.105
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 76k init
init started: BusyBox v0.61.pre (2003.03.22-20:17+0000) multi-caDetected STB:
Vendor: Nokia
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 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 [CXA2092] 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 $
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
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt failed
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt_fb failed
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt_lirc failed
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt_oss failed
Linux video capture interface: v1.00
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt_v4l2 failed
avia_av: $Id: avia_av_core.c,v 1.60 2003/03/13 21:04:21 wjoost Exp $
avia_av_event: $Id: avia_av_event.c,v 1.5 2003/01/02 05:26:43 obi Exp $
avia_av_proc: $Id: avia_av_proc.c,v 1.4 2003/01/02 05:26:43 obi Exp $
$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 (VES1820 based DVB-C frontend)...
VES1x93 not found (identity 11)
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
write 1 event's ...
write 1 event's ...
$Id: cam_napi.c,v 1.5 2003/01/14 08:43:17 jolt Exp $
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_av_napi failed
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: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.20-dbox2/misc/fp.o: init_module: Device or resource busy
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/fp.o: insmod /lib/modules/2.4.20-dbox2/misc/fp.o
failed
/lib/modules/2.4.20-dbox2/misc/fp.o: insmod avia_gt_napi failed
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] no card is in slot #2
[camd] a card is in slot #1
[camd] ca system id: 1722
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) EAUDIO
+ (5) d-Box LCD Hardware
[LCD] set brightness 130, contrast 32
+ (5) eActionMapList
currentStyle=default
+ (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
[FONT] Intializing font cache, using max. 4MB...
+ (10) gRC
RC thread createted successfully
+ (11) GFBDC
/dev/fb/0: No such file or directory
framebuffer not available.
no framebuffer available
no active skin
