neues YADD geht nicht zum einspielen
-
- Neugieriger
- Beiträge: 4
- Registriert: Donnerstag 26. September 2002, 12:40
neues YADD geht nicht zum einspielen
Hi
Meine Philips-box laeuft mit Neutrino, aber leider haengt sie sich oefters auf. Wollte nun das neue Yadd einspielen bzw. testen --> aber dann haengt die Box beim Reboot.
Hat jemand einen TIP?? THANKS!
Merkwuerdig fand ich die Warnings:
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
und
Kernel panic: Attempted to kill init!
Hier der komplette Log:
The system is halted. Press CTRL-ALT-DEL or turn off power
write 1 event's ...
System halted.
Oops: kernel access of bad area, sig: 11
NIP: 00000000 XER: 00000000 LR: C0009DD0 SP: C1FEFDF0 REGS: c1fefd40 TRAP: 0400
Not tainted
MSR: 08209032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1fee000[1] 'init' Last syscall: 88
last math 00000000 last altivec 00000000
GPR00: C001B6F8 C1FEFDF0 C1FEE000 00000012 00001032 00000001 FF000000 C01432B7
GPR08: 00000000 00000000 FF002830 C1FEFD10 0000000D 10068FBC 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00009032 01FEFF10 00000000 C0004594
GPR24: C0004300 10060FF0 1003B2A0 10060000 00000001 10020000 7FFFFE6C 0000000A
Call backtrace:
10020000 C001B6F8 C000435C 00000000 10020874 7FFFFD58 00000000
100216F0 1003B878 1003B334 0FED9960 00000000
Kernel panic: Attempted to kill init!
<0>Rebooting in 180 seconds..debug: DDF: Calibrating delay loop... debug: DDF:
66.76 BogoMIPS
debug: BMon V1.0 mID 02
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-82.cd.ca.07.00.00-2f
debug: HWrev 01 FPrev 0.30
debug: B/Ex/Fl(MB) 32/00/08
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.23
debug: Sending TFTP-request for file C/yadd/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 200228
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000
ppcboot 0.6.4 (Sep 15 2002 - 22:09:05)
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-2b-2b-47
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/yadd/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
LCD logo at: 0x130000 (0x1FD2AD8 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/yadd/tftpboot/logo-fb'.
Load address: 0x120000
Loading: ###
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.0.1; our IP address is 192.168.0.23
Filename 'C/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: 647340 Bytes = 632 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.19 (Sinnlos98@ATHLON) (gcc version 3.2) #11 Sun Sep 15 22:09:2
0 2002
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/yadd/c
dkroot/ ip=192.168.0.23:192.168.0.1:::::off
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
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: 30788k available (1136k kernel code, 376k data, 68k 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
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:2b:2b:47
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
Using word 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)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, addr=192.168.0.23, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.0.23, domain=, nis-domain=(none),
bootserver=192.168.0.1, rootserver=192.168.0.1, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.0.1
Looking up port of RPC 100005/1 on 192.168.0.1
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 68k init
init started: BusyBox v0.60.3 (2002.09.15-20:17+0000) multi-call[i2c-8xx]: mpc
8xx i2c init
i2c-core.o: adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
mID: 02
feID: 00
fpID: 52
enxID: 03
gtxID: ffffffff
hwREV: 01
fpREV: 30
DEMOD: TDA8044H
Loading /share/keymaps/i386/qwertz/de-latin1.kmap.gz
gunzip: fe=1: No such file or directory
maybekillzombie(): decompressor child exited anormally with code 1.
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 i2c audio/video switch driver registered.
i2c-core.o: client [STV6412] registered to adapter [](pos. 1).
mice: PS/2 mouse device common for all mice
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod dvb failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod tuner failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_fb failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_oss failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_napi failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_vbi failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod dvb_net failed
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 2
Please press Enter to activate this console. /dev/dbox/rc0: No such file or dire
ctory
The system is going down NOW !!
Sending SIGKILL to all processes.
STV6412 found
The system is halted. Press CTRL-ALT-DEL or turn off power
write 1 event's ...
System halted.
Oops: kernel access of bad area, sig: 11
NIP: 00000000 XER: 00000000 LR: C0009DD0 SP: C1FEFDF0 REGS: c1fefd40 TRAP: 0400
Not tainted
MSR: 08209032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1fee000[1] 'init' Last syscall: 88
last math 00000000 last altivec 00000000
GPR00: C001B6F8 C1FEFDF0 C1FEE000 00000012 00001032 00000001 FF000000 C01432B7
GPR08: 00000000 00000000 FF002830 C1FEFD10 0000000D 10068FBC 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00009032 01FEFF10 00000000 C0004594
GPR24: C0004300 10060FF0 1003B2A0 10060000 00000001 10020000 7FFFFE6C 0000000A
Call backtrace:
10020000 C001B6F8 C000435C 00000000 10020874 7FFFFD58 00000000
100216F0 1003B878 1003B334 0FED9960 00000000
Kernel panic: Attempted to kill init!
<0>Rebooting in 180 seconds..
Und Dann passiert nichts mehr.....
Meine Philips-box laeuft mit Neutrino, aber leider haengt sie sich oefters auf. Wollte nun das neue Yadd einspielen bzw. testen --> aber dann haengt die Box beim Reboot.
Hat jemand einen TIP?? THANKS!
Merkwuerdig fand ich die Warnings:
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
und
Kernel panic: Attempted to kill init!
Hier der komplette Log:
The system is halted. Press CTRL-ALT-DEL or turn off power
write 1 event's ...
System halted.
Oops: kernel access of bad area, sig: 11
NIP: 00000000 XER: 00000000 LR: C0009DD0 SP: C1FEFDF0 REGS: c1fefd40 TRAP: 0400
Not tainted
MSR: 08209032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1fee000[1] 'init' Last syscall: 88
last math 00000000 last altivec 00000000
GPR00: C001B6F8 C1FEFDF0 C1FEE000 00000012 00001032 00000001 FF000000 C01432B7
GPR08: 00000000 00000000 FF002830 C1FEFD10 0000000D 10068FBC 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00009032 01FEFF10 00000000 C0004594
GPR24: C0004300 10060FF0 1003B2A0 10060000 00000001 10020000 7FFFFE6C 0000000A
Call backtrace:
10020000 C001B6F8 C000435C 00000000 10020874 7FFFFD58 00000000
100216F0 1003B878 1003B334 0FED9960 00000000
Kernel panic: Attempted to kill init!
<0>Rebooting in 180 seconds..debug: DDF: Calibrating delay loop... debug: DDF:
66.76 BogoMIPS
debug: BMon V1.0 mID 02
debug: feID 00 enxID 03
debug: fpID 52 dsID 01-82.cd.ca.07.00.00-2f
debug: HWrev 01 FPrev 0.30
debug: B/Ex/Fl(MB) 32/00/08
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.23
debug: Sending TFTP-request for file C/yadd/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 200228
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000
ppcboot 0.6.4 (Sep 15 2002 - 22:09:05)
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-2b-2b-47
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/yadd/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
LCD logo at: 0x130000 (0x1FD2AD8 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.1; our IP address is 192.168.0.23
Filename 'C/yadd/tftpboot/logo-fb'.
Load address: 0x120000
Loading: ###
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.0.1; our IP address is 192.168.0.23
Filename 'C/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: 647340 Bytes = 632 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.19 (Sinnlos98@ATHLON) (gcc version 3.2) #11 Sun Sep 15 22:09:2
0 2002
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/yadd/c
dkroot/ ip=192.168.0.23:192.168.0.1:::::off
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 66 busfreq = 66
WARNING: NEW intfreq = 66000000 busfreq = 66000000
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: 30788k available (1136k kernel code, 376k data, 68k 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
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:2b:2b:47
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
Using word 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)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, addr=192.168.0.23, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.0.23, domain=, nis-domain=(none),
bootserver=192.168.0.1, rootserver=192.168.0.1, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.0.1
Looking up port of RPC 100005/1 on 192.168.0.1
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 68k init
init started: BusyBox v0.60.3 (2002.09.15-20:17+0000) multi-call[i2c-8xx]: mpc
8xx i2c init
i2c-core.o: adapter registered as adapter 0.
[i2c-8xx]: adapter: 0
mID: 02
feID: 00
fpID: 52
enxID: 03
gtxID: ffffffff
hwREV: 01
fpREV: 30
DEMOD: TDA8044H
Loading /share/keymaps/i386/qwertz/de-latin1.kmap.gz
gunzip: fe=1: No such file or directory
maybekillzombie(): decompressor child exited anormally with code 1.
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 i2c audio/video switch driver registered.
i2c-core.o: client [STV6412] registered to adapter [](pos. 1).
mice: PS/2 mouse device common for all mice
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod dvb failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod tuner failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_fb failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_oss failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_napi failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod avia_gt_vbi failed
i2c-core.o: driver DBox2 Frontprocessor driver registered.
i2c-core.o: client [DBox2 Frontprocessor client] registered to adapter [](pos. 2
).
AVIA: $Id: avia_core.c,v 1.31 2002/08/22 13:39:33 Jolt Exp $
avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
/lib/modules/2.4.19/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/misc/avia.o: insmod /lib/modules/2.4.19/misc/avia.o failed
i2c-core.o: client [DBox2 Frontprocessor client] unregistered.
i2c-core.o: driver unregistered: DBox2 Frontprocessor driver
/lib/modules/2.4.19/misc/avia.o: insmod dvb_net failed
lcd.o: init lcd driver module
lcd.o: found KS0713/SED153X lcd interface on 2
Please press Enter to activate this console. /dev/dbox/rc0: No such file or dire
ctory
The system is going down NOW !!
Sending SIGKILL to all processes.
STV6412 found
The system is halted. Press CTRL-ALT-DEL or turn off power
write 1 event's ...
System halted.
Oops: kernel access of bad area, sig: 11
NIP: 00000000 XER: 00000000 LR: C0009DD0 SP: C1FEFDF0 REGS: c1fefd40 TRAP: 0400
Not tainted
MSR: 08209032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c1fee000[1] 'init' Last syscall: 88
last math 00000000 last altivec 00000000
GPR00: C001B6F8 C1FEFDF0 C1FEE000 00000012 00001032 00000001 FF000000 C01432B7
GPR08: 00000000 00000000 FF002830 C1FEFD10 0000000D 10068FBC 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00009032 01FEFF10 00000000 C0004594
GPR24: C0004300 10060FF0 1003B2A0 10060000 00000001 10020000 7FFFFE6C 0000000A
Call backtrace:
10020000 C001B6F8 C000435C 00000000 10020874 7FFFFD58 00000000
100216F0 1003B878 1003B334 0FED9960 00000000
Kernel panic: Attempted to kill init!
<0>Rebooting in 180 seconds..
Und Dann passiert nichts mehr.....
-
- Tuxboxer
- Beiträge: 2067
- Registriert: Mittwoch 6. März 2002, 15:29
Re: neues YADD geht nicht zum einspielen
Tja, das ist klar. Du hast die ucodes nicht kopiert...Maharatscha hat geschrieben: avia_core.c: do_firmread: Unable to load '/var/tuxbox/ucodes/avia600.ux'.
Und Dann passiert nichts mehr.....
-
- Neugieriger
- Beiträge: 4
- Registriert: Donnerstag 26. September 2002, 12:40
-
- Senior Member
- Beiträge: 8282
- Registriert: Mittwoch 10. Oktober 2001, 00:00
Die Ucodes sind die gleichen, wie die, die Du zur box kopiert hast.
Mit nem Update der Box hat das nix zu tun, dazu musst Du ein neues Image flashen, bzw. wenn Du schon ein aktuelles Baseimage draufhast ein neues cdk.cramfs einspielen.
Unter http://dboxupdate.berlios.de gibts genaueres.
Ein Yadd ist ganz einfach ne Linux-Distribution die von der Festplatte aus ausgeführt wird.
Mit nem Update der Box hat das nix zu tun, dazu musst Du ein neues Image flashen, bzw. wenn Du schon ein aktuelles Baseimage draufhast ein neues cdk.cramfs einspielen.
Unter http://dboxupdate.berlios.de gibts genaueres.
Ein Yadd ist ganz einfach ne Linux-Distribution die von der Festplatte aus ausgeführt wird.
-
- Neugieriger
- Beiträge: 4
- Registriert: Donnerstag 26. September 2002, 12:40
Hallo Dietmar,
ich dachte mit dem Yadd wird erst vom PC aus getestet und dann kommt der Update in die BOX mit mehr features and bugfixes. Welchen Sinn haben dann die haeufigen Updates von den Yadds mit z.B. zusaetzlichen Spielen wenn man nichts rueberspielen bzw. updaten kann??
Mein Problem :Meine Philips Box stuerzt immer haeufiger beim zappen ab (ich weiss, ich bin nicht der einzige) und deshalb hoffe ich immer noch auf das richtigen Update.
ich dachte mit dem Yadd wird erst vom PC aus getestet und dann kommt der Update in die BOX mit mehr features and bugfixes. Welchen Sinn haben dann die haeufigen Updates von den Yadds mit z.B. zusaetzlichen Spielen wenn man nichts rueberspielen bzw. updaten kann??
Mein Problem :Meine Philips Box stuerzt immer haeufiger beim zappen ab (ich weiss, ich bin nicht der einzige) und deshalb hoffe ich immer noch auf das richtigen Update.
-
- Senior Member
- Beiträge: 8282
- Registriert: Mittwoch 10. Oktober 2001, 00:00
Die Yadds sind zum Testen, bzw. wenn man sich halt einfach nicht flashen will (warum auch immer).
Was hast den aktuell auf der Box?
Schau vielleicht mal unter http://dboxupdate.berlios.de unter Snapshots, evtl. ist ja was neues für Dich dabei.
Was hast den aktuell auf der Box?
Schau vielleicht mal unter http://dboxupdate.berlios.de unter Snapshots, evtl. ist ja was neues für Dich dabei.
-
- Neugieriger
- Beiträge: 4
- Registriert: Donnerstag 26. September 2002, 12:40
-
- Senior Member
- Beiträge: 8282
- Registriert: Mittwoch 10. Oktober 2001, 00:00
-
- Interessierter
- Beiträge: 20
- Registriert: Samstag 28. Dezember 2002, 02:29
Hi,
ich bin noch neu bei der Sache und habe festgestellt, dass das mit dem Internetupdate nicht so toll klappt wie hier http://dboxupdate.berlios.de/install.shtml beschrieben wird.
ZITAT:
Je nach Internetverbindung dauert das Update zwischen 5 und 20 Minuten. Sie müssen die Box neu starten, erst dann wird die neue Version aktiviert. (Stecker ziehen) Leider gehen dabei meist die Einstellungen für Netzwerk und Sprache verloren, die Senderlisten und UCodes bleiben jedoch erhalten, also keine Angst.
Bei mir waren die Dateien hinterher weg, meine Box wollte nicht mehr booten da mußte ich alles neu flashen mir ne xxxx besorgen damit die Box überhaupt läuft.
greez
ich bin noch neu bei der Sache und habe festgestellt, dass das mit dem Internetupdate nicht so toll klappt wie hier http://dboxupdate.berlios.de/install.shtml beschrieben wird.
ZITAT:
Je nach Internetverbindung dauert das Update zwischen 5 und 20 Minuten. Sie müssen die Box neu starten, erst dann wird die neue Version aktiviert. (Stecker ziehen) Leider gehen dabei meist die Einstellungen für Netzwerk und Sprache verloren, die Senderlisten und UCodes bleiben jedoch erhalten, also keine Angst.
Bei mir waren die Dateien hinterher weg, meine Box wollte nicht mehr booten da mußte ich alles neu flashen mir ne xxxx besorgen damit die Box überhaupt läuft.
greez
Zuletzt geändert von gez-konzta am Samstag 28. Dezember 2002, 22:43, insgesamt 1-mal geändert.
-
- Oberlamer, Administrator & Supernanny
- Beiträge: 10532
- Registriert: Samstag 13. Juli 2002, 10:49