problem mit speicher auslesen

Anlaufschwierigkeiten? Was ist was? Worum geht's?
sillicon
Neugieriger
Neugieriger
Beiträge: 15
Registriert: Freitag 31. Mai 2002, 12:11

problem mit speicher auslesen

Beitrag von sillicon »

hallo
hab eine nokia mit 2xintel
bin jetzt soweit die org. soft zu sichern nur sobald ich diese
auslesen möchte bekomme ich folgendes:


debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.2 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-48.ea.81.07.00.00-a2
debug: HWrev 09 FPrev 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.2, My IP 192.168.0.4
debug: Sending TFTP-request for file C/dbox2/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: PPC823ZTnnB2 at 67 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-44-cd-d9
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.2; our IP address is 192.168.0.4
Filename 'C/dbox2/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1FD2864 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.0.2; our IP address is 192.168.0.4
Filename 'C/dbox2/tftpboot/logo-fb'.
Load address: 0x120000
Loading: ###
done
FB logo at: 0x0 (0x1FC0000 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.2; our IP address is 192.168.0.4
Filename 'C/dbox2/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: 600241 Bytes = 586 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.2 (root@noer-lab.noernet.de) (gcc version 3.0.1 20010702 (prer
elease)) #89 Fri Aug 24 21:37:54 CEST 2001
Boot arguments: console=ttyS0 root=/dev/nfs rw nfsroot=192.168.0.2:C/dbox2/cdkro
ot/
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.2:C/dbox2/
cdkroot/
time_init: decrementer frequency = 251250000/60
Warning: real time clock seems stuck!
Console: colour dummy device 80x25
Calibrating delay loop... 66.56 BogoMIPS
Memory: 30624k available (1088k kernel code, 424k data, 64k 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
i2c-core.o: i2c core module
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
pty: 256 Unix98 ptys configured
block: queued sectors max/low 20264kB/6754kB, 64 slots per queue
eth0: CPM ENET Version 0.2, 00:50:9c:44:cd:d9
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit mode
Creating 7 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x000c0000 : "idxfs"
0x000c0000-0x001c0000 : "var"
0x001c0000-0x00760000 : "root"
0x00760000-0x00800000 : "flfs"
0x00020000-0x00800000 : "GesamteFlashOhneBL"
0x007e0000-0x00800000 : "flfs_128"
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)
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 192.168.0.2, my address is 192.168.0.4
IP-Config: Guessing netmask 255.255.255.0
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
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.2
Looking up port of RPC 100005/2 on 192.168.0.2
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 64k in
init started: BusyBox v0.60.2 (2002.02.26-14:29+0000) multi-call

dbox2miniroot zum Flash auslesen v1.0
linux@dbox2 Project http://dbox2.elxsi.de
Wilkommen auf ihrer dbox2
druecken sie bitte einmal Enter
und danach geben sie ein
cat /dev/mtd/5 >/flash.img
das dauert ca 2 bis 5 minuten
dann kommt die Raute wieder
dann befindet sich in c: dbox2 cdkroot
die Datei flash.img , die ganz genau 8257536 Bytes
gross sein solte !
das ist dann ihr backup Flashimage das sie gut aufheben sollten
danach koennen sie die dbox2 einfach ausmachen

Please press Enter to activate this console.


BusyBox v0.60.2 (2002.02.26-14:29+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat /dev/mtd/5 >/org.img
nfs: server 192.168.0.2 not responding, still trying
nfs: server 192.168.0.2 not responding, still trying


wo liegt der fehler?

danke
z/OS
Einsteiger
Einsteiger
Beiträge: 160
Registriert: Donnerstag 29. August 2002, 13:40

Beitrag von z/OS »

nfs: server 192.168.0.2 not responding, still trying
Du hast im Bootmanager den NFS-Server nicht gestartet.
Gruß
z/OS
Philips 2*I, Sat.