(smiles) I can not believe a kiwi is bagging the ozzie dollar ..
Compiling Dropbear for DM500
Started by bartender, 25 Jan 2008 03:42
29 replies to this topic
Re: Compiling Dropbear for DM500 #21
Re: Compiling Dropbear for DM500 #22
Re: Compiling Dropbear for DM500 #23
Posted 20 February 2008 - 21:43
Not sure to be honest, sounds like the flash didn't work correctly as I have used both the root.cramfs & dreamup to ugprade from the PLI Iolite 2008 ed to the build I have made many times without an issue. Try downloading and re-flashing, and doing a "flash erase" when prompted in Dreamup.
I also assume you are doing a Serial (non-network) upgrade using dreamup?
I also assume you are doing a Serial (non-network) upgrade using dreamup?
Re: Compiling Dropbear for DM500 #24
Posted 20 February 2008 - 22:12
I have re-flasht it an "flash erase" yes I have tried network and serial.
Is this any help.......
Dreambox DM500
loaded at: 00500000 005F216C
relocated to: 00400000 004F216C
board data at: 004F0124 004F016C
relocated to: 00405194 004051DC
zimage at: 004058D1 004EF05A
avail ram: 004F3000 02000000
Linux/PPC load: consol=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs ro
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.6.9 (build@buildserver) (gcc version 3.4.4) #1 Sat Dec 8 01:38:45 CET 2007
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs ro
PID hash table entries: 256 (order: 8, 4096 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30208k available (1596k kernel code, 532k data, 76k init, 0k highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
Squashfs 2.2-r2 (released 2005/09/08) © 2002-2005 Phillip Lougher
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) © 2001-2003 Red Hat, Inc.
Serial: 8250/16550 driver $Revision: 1.90 $ 7 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 20) is a 16550A
ttyS1 at MMIO 0x0 (irq = 21) is a 16550A
ttyS2 at MMIO 0x0 (irq = 22) is a 16550A
loop: loaded (max 8 devices)
ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0xc3060600:<4>eth0: interrupt from stopped card
00 09 34 20 65 22
eth0: NE2000 found at 0xc3060600, using IRQ 25.
Using deadline io scheduler
dreambox: flash mapping: 800000 at 7f800000
DreamBOX rev3+: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
disable flash VPP
Creating 7 MTD partitions on "DreamBOX rev3+":
0x00000000-0x00600000 : "DreamBOX cramfs+squashfs"
0x00600000-0x007c0000 : "DreamBOX jffs2"
0x007c0000-0x00800000 : "DreamBOX OpenBIOS"
0x00000000-0x007c0000 : "DreamBOX (w/o bootloader)"
0x00000000-0x00800000 : "DreamBOX (w/ bootloader)"
0x00120000-0x00600000 : "DreamBOX SquashedFS"
0x00000000-0x00120000 : "DreamBOX Cramfs"
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
IBM IIC driver v2.1
ibm-iic0: using standard (100 kHz) mode
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
attempt to access beyond end of device
mtdblock5: rw=0, want=10552, limit=9984
SQUASHFS error: sb_bread failed reading block 0x149b
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
<0>Rebooting in 180 seconds..
Is this any help.......
Dreambox DM500
loaded at: 00500000 005F216C
relocated to: 00400000 004F216C
board data at: 004F0124 004F016C
relocated to: 00405194 004051DC
zimage at: 004058D1 004EF05A
avail ram: 004F3000 02000000
Linux/PPC load: consol=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs ro
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.6.9 (build@buildserver) (gcc version 3.4.4) #1 Sat Dec 8 01:38:45 CET 2007
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs ro
PID hash table entries: 256 (order: 8, 4096 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30208k available (1596k kernel code, 532k data, 76k init, 0k highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
Squashfs 2.2-r2 (released 2005/09/08) © 2002-2005 Phillip Lougher
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) © 2001-2003 Red Hat, Inc.
Serial: 8250/16550 driver $Revision: 1.90 $ 7 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 20) is a 16550A
ttyS1 at MMIO 0x0 (irq = 21) is a 16550A
ttyS2 at MMIO 0x0 (irq = 22) is a 16550A
loop: loaded (max 8 devices)
ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0xc3060600:<4>eth0: interrupt from stopped card
00 09 34 20 65 22
eth0: NE2000 found at 0xc3060600, using IRQ 25.
Using deadline io scheduler
dreambox: flash mapping: 800000 at 7f800000
DreamBOX rev3+: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
disable flash VPP
Creating 7 MTD partitions on "DreamBOX rev3+":
0x00000000-0x00600000 : "DreamBOX cramfs+squashfs"
0x00600000-0x007c0000 : "DreamBOX jffs2"
0x007c0000-0x00800000 : "DreamBOX OpenBIOS"
0x00000000-0x007c0000 : "DreamBOX (w/o bootloader)"
0x00000000-0x00800000 : "DreamBOX (w/ bootloader)"
0x00120000-0x00600000 : "DreamBOX SquashedFS"
0x00000000-0x00120000 : "DreamBOX Cramfs"
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
IBM IIC driver v2.1
ibm-iic0: using standard (100 kHz) mode
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
attempt to access beyond end of device
mtdblock5: rw=0, want=10552, limit=9984
SQUASHFS error: sb_bread failed reading block 0x149b
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
<0>Rebooting in 180 seconds..
Re: Compiling Dropbear for DM500 #25
Posted 20 February 2008 - 23:47
@bartender
I've unpacked your uploaded image and you have supplied dropbear4pli.tgz in the root of the squshfs. I think your image is too big to fit...
I've recompiled it and supplied the new CCcam 2.0.7.
Be aware that I haven't tested the uploaded image - use it at your own risk...
I've unpacked your uploaded image and you have supplied dropbear4pli.tgz in the root of the squshfs. I think your image is too big to fit...
I've recompiled it and supplied the new CCcam 2.0.7.
Be aware that I haven't tested the uploaded image - use it at your own risk...
Attached Files
Re: Compiling Dropbear for DM500 #26
Re: Compiling Dropbear for DM500 #27
Posted 22 February 2008 - 13:33
Strange...ssh: Warning: failed creating //.ssh: Read-only file system
When I look in the startup-scripts the folder /var/.ssh should be created, and as far as I know /var is not Read-only...
Could you please check if /var/.ssh and /var/etc/dropbear is created?
Does the image work besides that?
Re: Compiling Dropbear for DM500 #28
Re: Compiling Dropbear for DM500 #29
Posted 27 February 2008 - 17:55
Strange...
ssh: Warning: failed creating //.ssh: Read-only file system
When I look in the startup-scripts the folder /var/.ssh should be created, and as far as I know /var is not Read-only...
Could you please check if /var/.ssh and /var/etc/dropbear is created?
Does the image work besides that?
/var/.ssh is there
root@dm500 ~ # ls -al /var/.ssh/
drwxr-xr-x 2 root root 0 Feb 26 21:40 .
drwx------ 16 root root 0 Feb 26 21:06 ..
-rw------- 1 root root 427 Feb 26 21:40 dbkey.rsa
And /var/etc/dropbear
root@dm500 ~ # ls -al /var/etc/dropbear/
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwx------ 5 root root 0 Feb 26 08:52 ..
-rw------- 1 root root 458 Jan 1 1970 dropbear_dss_host_key
-rw------- 1 root root 427 Jan 1 1970 dropbear_rsa_host_key
but no /.ssh
root@dm500 ~ # ls -al /
-rwxr-xr-x 1 root root 139 Dec 8 01:14 .profile
-rw-r--r-- 1 root root 283 Dec 30 04:22 .version
drwxr-xr-x 1 root root 1165 Feb 4 03:44 bin
drwxr-xr-x 1 root root 0 Jan 1 1970 dev
drwxr-xr-x 1 root root 265 Dec 30 04:22 etc
lrwxrwxrwx 1 root root 10 Feb 20 22:33 hdd -> /media/hdd
drwxr-xr-x 1 root root 609 Feb 4 03:44 lib
drwxr-xr-x 1 root root 77 Dec 30 04:22 media
lrwxrwxrwx 1 root root 6 Feb 20 22:33 mnt -> /media
dr-xr-xr-x 48 root root 0 Jan 1 1970 proc
drwxr-xr-x 1 root root 0 Dec 30 04:22 root
drwxr-xr-x 1 root root 397 Feb 4 03:30 sbin
drwxr-xr-x 1 root root 124 Dec 30 04:22 share
drwxrwxrwt 2 root root 0 Feb 26 08:52 tmp
drwx------ 16 root root 0 Feb 26 21:06 var
drwx------ 16 root root 0 Feb 26 21:06 var_flash
drwxr-xr-x 1 root root 100 Dec 30 04:22 var_init
The image works great
but i don´t get gSUB to work
2SUB: FT_New_Face failed: Operation not permitted, for font: /share/fonts/pakenham.ttf
2SUB: FTC_Manager_Lookup_Face failed with Errorcode 0x00
2SUB: Probably because font was not found:/share/fonts/pakenham.ttf
but bullstext work.
Re: Compiling Dropbear for DM500 #30
Posted 28 February 2008 - 16:53
You could add the symbolic link /.ssh to the image before flashing.
But I did it by just changing the home directory for the user "root", which is normally "/", to "/var". Just edit the /var/etc/passwd so, that the first line looks like this:
root:[some encrypted password]:0:0::/var:/bin/sh
But I did it by just changing the home directory for the user "root", which is normally "/", to "/var". Just edit the /var/etc/passwd so, that the first line looks like this:
root:[some encrypted password]:0:0::/var:/bin/sh
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users