Who said it's easy ...

[JOCKYW2001]

I compiled latest HEAD and succesfully created a YADD and a jffs2only image from it. The YADD works but the image doesn't

The bootlog shows this:

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-ac.xxxxxxxxx
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: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/philips-dbox2/kernel/os in Flash-FS
debug: Got Block #0036

will verify ELF image, start= 0x800000, size= 145428
verify sig: 262
Branching to 0x40000


U-Boot 0.4.0 (TuxBox) (Aug 2 2003 - 08:09:08)

CPU: PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Phillips
Watchdog enabled
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
Scanning JFFS2 FS: .
find_inode failed for name=logo-lcd
load: Failed to find inode
ready - can't find logo in flash - try network
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
...

So it complains about a missing logo-lcd, but I did copy it into cdkflash/root/boot before creating the image. I flashed the image already twice, doesn't help. I did patch the kernel dbox2-flash.c and do_mounts.c
Unplugged the lan cable, the null-mode, rebooted using stdby-arrow up, ... still a no go

I am running out of options.

Does anyone have an idea?

Thanks, JockyW

[miller_bln]

first of all:
press ctrl-c (strg-c).

two possibilities can appear:
1) the image starts normally
2) you get an other error

[Homar]

JOCKYW2001:

did you change your bootcommand ??

[JOCKYW2001]

JOCKYW2001:

did you change your bootcommand ??

hi there Homar,

no I changed nothing, should I?

JockyW

[Homar]

yes, you should!

in tuxbox-cvs\boot\u-boot\include\configs\dbox2.h:

/*
#define CONFIG_BOOTCOMMAND \
"protect off 10040000 107fffff; " \
"fsload; setenv bootargs root=/dev/mtdblock2 console=$(console); " \
"bootm"
*/

activate this bootcommand and exclude the other one

[JOCKYW2001]

Cool! I'll give that a go ... and I thought I had read everything

JockyW

[Homar]

[JOCKYW2001]

yes, you should!

in tuxbox-cvs\boot\u-boot\include\configs\dbox2.h:

/*
#define CONFIG_BOOTCOMMAND \
"protect off 10040000 107fffff; " \
"fsload; setenv bootargs root=/dev/mtdblock2 console=$(console); " \
"bootm"
*/

activate this bootcommand and exclude the other one

Homar,

Do I need to make the same patch in order to get the latest YADD (from HEAD) to run?

I just compiled a clean YADD and get this :
.......
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:xx:xx:xx:xx:xx
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
cfi_cmdset_0001: Erase suspend on write enabled
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"
Linux video capture interface: v1.00
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.90, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.1.90, domain=, nis-domain=(none),
bootserver=192.168.1.85, rootserver=192.168.1.85, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.1.85
Looking up port of RPC 100005/1 on 192.168.1.85
VFS: Mounted root (nfs filesystem).
mount_devfs_fs(): unable to mount devfs, err: -2
Freeing unused kernel memory: 68k init
Warning: unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel.
<0>Rebooting in 180 seconds..

JockyW

[JOCKYW2001]

Homar,

Do I need to make the same patch in order to get the latest YADD (from HEAD) to run?
JockyW

The answer is no (just tried it). But what else causes that error in the unmodified HEAD? (mount_devfs_fs(): unable to mount devfs, err: -2
)

JockyW

[JOCKYW2001]

Homar,

Do I need to make the same patch in order to get the latest YADD (from HEAD) to run?
JockyW

The answer is no (just tried it). But what else causes that error in the unmodified HEAD? (mount_devfs_fs(): unable to mount devfs, err: -2
)

JockyW

The problem that devfs can not be mounted is caused by Knoppix. I copied the YADD from Knoppix to Redhat 9 and under Redhat 9 the YADD runs fine

So there must be something wrong with NFS or the permissions in Knoppix or ... or what?

Is there any Linux guru who can explain this?

JockyW

[JOCKYW2001]

So there must be something wrong with NFS or the permissions in Knoppix or ... or what?

Is there any Linux guru who can explain this?

JockyW

So I compared the bootlogs in Knoppix and Redhat 9.0
Here is the only difference.

Knoppix bootlog:
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.85:/home/tuxbox/dbox2/ ip=192.168.1.90:192.168.1.85::255.255.255.0:::off console=ttyS0
Decrementer Frequency = 247125000/60

Redhat 9.0 bootlog:
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.85:/home/tuxbox/dbox2/cdkroot ip=192.168.1.90:192.168.1.85::255.255.255.0:::off console=ttyS0
Decrementer Frequency = 247125000/60

In Knoppix' kernel cmdline the nfsroot path is /home/tuxbox/dbox2 whereas in Redhat 9.0 it is :/home/tuxbox/dbox2/cdkroot

What the heck! Why is Knoppix behaving faulty? What should I change in Knoppix so that I can boot a YADD from it?

JockyW

[JOCKYW2001]

What the heck! Why is Knoppix behaving faulty? What should I change in Knoppix so that I can boot a YADD from it?

JockyW

Eh, my fault
I forgot to append cdkroot in dhcpd.conf ....... sorry

JockyW

[Homar]

may, you have to change your root-path in Knoppix dhcpd.conf from /home/tuxbox/dbox2 to home/tuxbox/dbox2/cdkroot

it seems to be a faulty configuration

[Homar]

a little bit to late my answer