OpenWrt Forum Archive

Topic: Missing openwrt-kirkwood-Dockstar-jffs2-128k.img on daily snapshot

The content of this topic has been archived on 24 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

According to this HOWTO, one needs the following three files to flash an OpenWRT firmware to a Seagate DockStar:

    *      openwrt-kirkwood-dockstar-u-boot.bin
    *      openwrt-kirkwood-Dockstar-jffs2-128k.img
    *      openwrt-kirkwood-uImage

Unfortunately, the snapshots directory for kirkwood didn't contain the openwrt-kirkwood-Dockstar-jffs2-128k.img file (as of this writing). sad

I compiled my own dockstar openwrt following Lars HowTo

But something went wrong

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.4 (felix@bflinux) (gcc version 4.3.3 (GCC) ) #1 Tue Sep 7 23:34:10 CEST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Seagate FreeAgent DockStar
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),1M@1M(second_stage_u-boot),3M@2M(kernel),32M@5M(rootfs),219M@37M(data) rw root=/dev/mtdblock3 rw rootfstype=jffs2
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 126972k/126972k available, 4100k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xfe800000   ( 864 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0021000   ( 100 kB)
      .text : 0xc0021000 - 0xc02bd000   (2672 kB)
      .data : 0xc02be000 - 0xc02d5340   (  93 kB)
NR_IRQS:114
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
msgmni has been set to 247
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
5 cmdlinepart partitions found on MTD device orion_nand
Creating 5 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000200000 : "second_stage_u-boot"
0x000000200000-0x000000500000 : "kernel"
0x000000500000-0x000002500000 : "rootfs"
0x000002500000-0x000010000000 : "data"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:10:75:1a:d1:c3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
rtc-mv rtc-mv: internal RTC not ticking
i2c /dev entries driver
cpuidle: using governor ladder
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
VFS: Mounted root (jffs2 filesystem) on device 31:3.
Freeing init memory: 100K
/etc/preinit: line 38: awk: not found
JFFS2 warning: (694) jffs2_do_read_inode_internal: Truncating ino #379 to 11476 bytes failed because it only had 3000 bytes to start with!

Any hints what I did wrong?

Likely cause is that the size of your jffs2 image are larger than what was expected in the instructions. that was the root cause when this message happened to me. But the kernel was up and running, I coul interact etc. That is not obvious from your output.

Try building 'out of the box' first and flashing that. If that works then start customizing.

I am awaiting the application of a patch to do the auto build of jffs2 image.  Add your name to Trac 7886 to get a notification of when this occurs.

Gerrit

z80yyz wrote:

Likely cause is that the size of your jffs2 image are larger than what was expected in the instructions. that was the root cause when this message happened to me. But the kernel was up and running, I coul interact etc. That is not obvious from your output.

Try building 'out of the box' first and flashing that. If that works then start customizing.

I am awaiting the application of a patch to do the auto build of jffs2 image.  Add your name to Trac 7886 to get a notification of when this occurs.

Gerrit

Thx Gerrit...it's working  fine now

Gerrit, does that mean I need to generate the file openwrt-kirkwood-Dockstar-jffs2-128k.img by myself? Isn't there a plain vanilla one I can use, so I can make sure everything works before customizing my root?

Reason I ask is that reading https://dev.openwrt.org/ticket/7886 and https://forum.openwrt.org/viewtopic.php?id=27043 make me feel that file should be available in http://downloads.openwrt.org/snapshots/trunk/kirkwood/. But, I have been wrong before, so... smile

(Last edited by supremedalek on 28 Nov 2010, 18:22)

Hi
The file should be available but for some reason it isn't.
I am away for the next 5 months out of town so can't do much with openwrt. I suggest getting on IRC and asking there. or join the Dev list. User 'jow' is very responsive to questions as well.

Gerrit

z80yyz wrote:

The file should be available but for some reason it isn't.

Agree. Yesterday, I just 'svn up; to r24191 and the build generated the following image files which includes the openwrt-kirkwood-Sheevaplug-jffs2-128k.img fimrware:

md5sums                        openwrt-kirkwood-sheevaplug-u-boot.bin
openwrt-kirkwood-dockstar-u-boot.bin        openwrt-kirkwood-sheevaplug-u-boot.kwb
openwrt-kirkwood-dockstar-u-boot.kwb        openwrt-kirkwood-uImage
openwrt-kirkwood-iconnect-u-boot.bin        packages
openwrt-kirkwood-iconnect-u-boot.kwb        uboot-kirkwood-dockstar
openwrt-kirkwood-rootfs.tar.gz            uboot-kirkwood-iconnect
openwrt-kirkwood-Sheevaplug-jffs2-128k.img  uboot-kirkwood-sheevaplug
openwrt-kirkwood-Sheevaplug-jffs2-64k.img

I am away for the next 5 months out of town so can't do much with openwrt. I suggest getting on IRC and asking there. or join the Dev list. User 'jow' is very responsive to questions as well.

Gerrit, enjoy your vacation.

The buildbots do not build subtargets atm, therfore no Dockstar images, just the generic ones.

Not to thump my own drum, but as I have posted previously (https://forum.openwrt.org/viewtopic.php … 52#p121452), IF you have the lzma-enabled mkfs.jffs2 from a trunk build (not necessary to build images, just the host tools) you can download the buildbot rootfs.tar.gz and build the needed image (openwrt-kirkwood-Dockstar-jffs2-128k.img) yourself:

0) create a new build directory, cd to it, create a directory ram, cd to it, and untar the snapshot file openwrt-kirkwood-rootfs.tar.gz:

mkdir ram
cd ram
tar xzf ../openwrt-kirkwood-rootfs.tar.gz
cd ..

1) run the following:

mkfs.jffs2 --little-endian --squash -v -X rtime -X lzma --compression-mode=size -x zlib --pagesize=0x800 --no-cleanmarkers --pad -e 128KiB -o root.jffs2-128 -d ram

2) add header to the intermediary file root.jffs2-128k:

echo -ne '\xde\xad\xc0\xde' >> root.jffs2-128k

3) create the required rootfs image:

dd if=root.jffs2-128k of=openwrt-kirkwood-Dockstar-jffs2-128k.img bs=2048 conv=sync

I have used this technique on two reflashs of my Dockstar and everything works perfectly.

There is a typo here. root.jffs2-128 should be root.jffs2-128k.

yawlhoo wrote:

1) run the following:

mkfs.jffs2 --little-endian --squash -v -X rtime -X lzma --compression-mode=size -x zlib --pagesize=0x800 --no-cleanmarkers --pad -e 128KiB -o root.jffs2-128 -d ram

Thanks.  I have slightly automated this process with a shell script and in posting my previous message there was a slip cutting and pasting the text.  BTW, I have used this at least a couple of more times in reflashing my dockstar and it keeps working perfectly.

yawlhoo wrote:

Thanks.  I have slightly automated this process with a shell script and in posting my previous message there was a slip cutting and pasting the text.  BTW, I have used this at least a couple of more times in reflashing my dockstar and it keeps working perfectly.

Hi, I'm putting openwrt on my dockstar, and I'm fairly certain the only thing that http://downloads.openwrt.org/snapshots/trunk/kirkwood/ is lacking is the jffs2 file, I was wondering if you could provide your openwrt-kirkwood-Dockstar-jffs2-128k.img that you'd generated for the Feb-08 snapshot, thank you!

I managed to get this built (and included some wireless and usb drivers) and flashed it to my openwrt smile thanks for the awesome software!

(Last edited by delirium on 18 Feb 2011, 12:34)

Some time ago delirium wrote (and, I just noticed this posting today):

"I was wondering if you could provide your openwrt-kirkwood-Dockstar-jffs2-128k.img that you'd generated for the Feb-08 snapshot, thank you!"

You can get this here:

http://www.mediafire.com/?sp5e5l8i641d58n

The discussion might have continued from here.