OpenWrt Forum Archive

Topic: Pogoplug Mobile - Potentially the Best OpenWRT Platform @ $10 shipped

The content of this topic has been archived between 8 Feb 2018 and 30 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.

tmo26 wrote:

@roger: Great that you started a Wiki page about the Pogoplug Mobile! smile

roger_ wrote:

King0fK0ng:
Also if you could take a look and see if the steps on the wiki are correct then that would be great smile

The E02 Image you linked (http://downloads.openwrt.org/snapshots/trunk/kirkwood/) does not work.
As King0fK0ng explained here https://forum.openwrt.org/viewtopic.php … 8#p244418, the generic one (see above) doesn't work. Instead, you have to compile your own image for the Pogoplug E02.

Thanks!

I'm confused; there are E02 builds here: http://downloads.openwrt.org/snapshots/ … -pogo_e02/

How would it be different if you built your own?

roger_ wrote:

I'm confused; there are E02 builds here: http://downloads.openwrt.org/snapshots/ … -pogo_e02/

How would it be different if you built your own?

I think you have to distinguish between the different installation methods.
What I'm trying to do: Boot OpenWRT from SD or USB drive. For that you'd need the rootfs.tar.gz + uImage. I can't find any of that in your above link.

However, I'm new to the Pogoplug and compiling images is not my strong side, thus some help of more experienced users is highly appreciated.

Edit: I think the above link only provides uboot, no firmware image (please correct me if I'm wrong).

(Last edited by tmo26 on 21 Aug 2014, 18:30)

Sorry, this is a bit OT.

Can we use this device like a Raspberry Pi? What I tried to say is if it is possible to do all the Rpi hardware projects using this device. After all, this device also has a USB port.

mazilo wrote:

Sorry, this is a bit OT.

Can we use this device like a Raspberry Pi? What I tried to say is if it is possible to do all the Rpi hardware projects using this device. After all, this device also has a USB port.

No, it definitely does not have the same connectivity. Not the same generation of ARM instructions either.

roger_ wrote:

King0fK0ng:

Can you post your OpenWrt bootlog for the Pogoplug Mobile? I'd like to add it to the wiki page.

Also if you could take a look and see if the steps on the wiki are correct then that would be great smile

Sorry, I'm in the middle of a move and everything is packed up.

mazilo wrote:

Sorry, this is a bit OT.

Can we use this device like a Raspberry Pi? What I tried to say is if it is possible to do all the Rpi hardware projects using this device. After all, this device also has a USB port.

The Pogoplug Mobile can definitely be used versus a Pi in many cases, but it depends on what specifically. Both system runs Arch Linux Arm for instance, so any ArchLinuxArm Pi tutorial would be applicable.

King0fK0ng wrote:

Sorry, I'm in the middle of a move and everything is packed up.


No hurry, whenever you get a chance. Good luck!

(Last edited by roger_ on 26 Aug 2014, 18:17)

King0fK0ng wrote:
mazilo wrote:

Sorry, this is a bit OT.

Can we use this device like a Raspberry Pi? What I tried to say is if it is possible to do all the Rpi hardware projects using this device. After all, this device also has a USB port.

The Pogoplug Mobile can definitely be used versus a Pi in many cases, but it depends on what specifically. Both system runs Arch Linux Arm for instance, so any ArchLinuxArm Pi tutorial would be applicable.

I guess if the project involves with USB and/or net, then it is doable with any PogoPlug Mobile device. If the project involves with GPIO, perhaps this is a different story unless a PogoPlug Mobile also has some built-in GPIO ports.

mazilo wrote:
King0fK0ng wrote:
mazilo wrote:

Sorry, this is a bit OT.

Can we use this device like a Raspberry Pi? What I tried to say is if it is possible to do all the Rpi hardware projects using this device. After all, this device also has a USB port.

The Pogoplug Mobile can definitely be used versus a Pi in many cases, but it depends on what specifically. Both system runs Arch Linux Arm for instance, so any ArchLinuxArm Pi tutorial would be applicable.

I guess if the project involves with USB and/or net, then it is doable with any PogoPlug Mobile device. If the project involves with GPIO, perhaps this is a different story unless a PogoPlug Mobile also has some built-in GPIO ports.

Pretty much that - GPIO and HDMI. The Pogoplug wins out on the ethernet side since it comes with gigabit ethernet making it a much more viable NAS (or anything that is high network I/O).

King0fK0ng wrote:
mazilo wrote:
King0fK0ng wrote:

The Pogoplug Mobile can definitely be used versus a Pi in many cases, but it depends on what specifically. Both system runs Arch Linux Arm for instance, so any ArchLinuxArm Pi tutorial would be applicable.

I guess if the project involves with USB and/or net, then it is doable with any PogoPlug Mobile device. If the project involves with GPIO, perhaps this is a different story unless a PogoPlug Mobile also has some built-in GPIO ports.

Pretty much that - GPIO and HDMI. The Pogoplug wins out on the ethernet side since it comes with gigabit ethernet making it a much more viable NAS (or anything that is high network I/O).

Exactly. For under US $10, this is a steal to turn it into a NAS + an IP PBX System + etc.

Another +20% in price??? I'm seeing 11.99$..

It was great at 7.50$ sad

Maybe too many people buying it now in a rush.
Now that we know that the price can go that deep: Wait until the next occasion.

I got my 2 pieces... smile

Here's my bootlog:

root@OpenWrt:/# reboot
procd: - shutdown -
root@OpenWrt:/# [  657.837606] EXT4-fs (sda1): re-mounted. Opts: (null)
procd: - reboot [  657.847437] reboot: Restarting system


U-Boot 1.1.4 (Oct  1 2011 - 12:21:35) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006918B4

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Unknown command 'usb' - try 'help'

NAND read: device 0 offset 0x100000, size 0x73d0c
474380 bytes read: OK
## Starting application at 0x00800000 ...


U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFD60

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

No Fat FS detected

IDE device 0 not available
.
....
......
............
.
........................
.
.........................
........................
.
.........................
.........................
.

1601190 bytes read
## Booting image at 00800000 ...
   Image Name:   ARM OpenWrt Linux-3.14.16
   Created:      2014-09-02  17:50:15 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1601126 Bytes =  1.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.16 (dp@P5Q-DELUXE) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r41887) ) #1 Tue Sep 2 12:50:02 CDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Cloud Engines Pogoplug E02
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootwait rootfstype=ext3
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 125244K/131072K available (3218K kernel code, 150K rwdata, 912K rodata, 132K init, 181K bss, 5828K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0410d5c   (4132 kB)
[    0.000000]       .init : 0xc0411000 - 0xc0432364   ( 133 kB)
[    0.000000]       .data : 0xc0434000 - 0xc045990c   ( 151 kB)
[    0.000000]        .bss : 0xc045990c - 0xc0486d58   ( 182 kB)
[    0.000000] NR_IRQS:114
[    0.000023] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[    0.000200] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    0.040120] pid_max: default: 32768 minimum: 301
[    0.040281] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040306] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.043251] CPU: Testing write buffer coherency: ok
[    0.043710] Setting up static identity map for 0x11168 - 0x111a4
[    0.046269] pinctrl core: initialized pinctrl subsystem
[    0.047661] regulator-dummy: no parameters
[    0.048380] NET: Registered protocol family 16
[    0.048959] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.052723] cpuidle: using governor ladder
[    0.052810] Kirkwood: MV88F6281-A1.
[    0.053010] Feroceon L2: Enabling L2
[    0.053063] Feroceon L2: Cache support initialised.
[    0.053692] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.070607] bio: create slab <bio-0> at 0
[    0.071430] USB Power: Failed to request enable GPIO29: -517
[    0.071639] reg-fixed-voltage 1.regulator: Failed to register regulator: -517
[    0.071666] platform 1.regulator: Driver reg-fixed-voltage requests probe deferral
[    0.072772] SCSI subsystem initialized
[    0.073833] usbcore: registered new interface driver usbfs
[    0.074041] usbcore: registered new interface driver hub
[    0.074278] usbcore: registered new device driver usb
[    0.076264] Switched to clocksource orion_clocksource
[    0.078768] NET: Registered protocol family 2
[    0.079350] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.079387] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.079415] TCP: Hash tables configured (established 1024 bind 1024)
[    0.079498] TCP: reno registered
[    0.079515] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.079546] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.079781] NET: Registered protocol family 1
[    0.081606] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.082267] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.082281] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.082592] msgmni has been set to 244
[    0.083467] io scheduler noop registered
[    0.083481] io scheduler deadline registered (default)
[    0.085427] kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
[    0.186764] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.188674] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[    0.571410] console [ttyS0] enabled
[    0.577561] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    0.583892] nand: Hynix H27U1G8F2BTR-BC
[    0.587741] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    0.593378] Scanning device for bad blocks
[    0.690446] 4 ofpart partitions found on MTD device orion_nand
[    0.696273] Creating 4 MTD partitions on "orion_nand":
[    0.701396] 0x000000000000-0x000000100000 : "u-boot"
[    0.707866] 0x000000100000-0x000000500000 : "uImage"
[    0.714113] 0x000000500000-0x000002500000 : "pogoplug"
[    0.720584] 0x000002500000-0x000008000000 : "root"
[    0.727655] libphy: orion_mdio_bus: probed
[    0.732644] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    0.817550] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address XX:XX:XX:XX:XX:XX
[    0.826421] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.832923] ehci-pci: EHCI PCI platform driver
[    0.837583] ehci-platform: EHCI generic platform driver
[    0.843042] ehci-orion: EHCI orion driver
[    0.847193] orion-ehci f1050000.ehci: EHCI Host Controller
[    0.852688] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    0.860550] orion-ehci f1050000.ehci: irq 24, io mem 0xf1050000
[    0.886285] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    0.893296] hub 1-0:1.0: USB hub found
[    0.897098] hub 1-0:1.0: 1 port detected
[    0.901766] usbcore: registered new interface driver usb-storage
[    0.910289] TCP: cubic registered
[    0.913598] NET: Registered protocol family 17
[    0.918404] 8021q: 802.1Q VLAN Support v1.8
[    0.924040] regulator-dummy: disabling
[    0.928398] USB Power: 5000 mV
[    0.932125] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.939914] Waiting for root device /dev/sda1...
[    1.216307] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    1.369338] usb-storage 1-1:1.0: USB Mass Storage device detected
[    1.375711] scsi0 : usb-storage 1-1:1.0
[    2.377828] scsi 0:0:0:0: Direct-Access     LEXAR    JD FIREFLY       3000 PQ: 0 ANSI: 0 CCS
[    2.388233] sd 0:0:0:0: [sda] 1014784 512-byte logical blocks: (519 MB/495 MiB)
[    2.396343] sd 0:0:0:0: [sda] Write Protect is off
[    2.401841] sd 0:0:0:0: [sda] No Caching mode page found
[    2.407160] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    2.417467] sd 0:0:0:0: [sda] No Caching mode page found
[    2.422781] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    2.430029]  sda: sda1
[    2.435717] sd 0:0:0:0: [sda] No Caching mode page found
[    2.441050] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    2.447154] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    2.476348] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[    2.484976] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[    2.499712] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    2.507421] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
[    2.514633] Freeing unused kernel memory: 132K (c0411000 - c0432000)
procd: Console is alive
procd: - preinit -
[    2.854142] random: mktemp urandom read with 27 bits of entropy available
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
mounting /dev/root
[    4.958382] EXT4-fs (sda1): re-mounted. Opts: (null)
procd: - early -
procd: - ubus -
procd: - init -
Please press Enter to activate this console.
[    9.806507] NET: Registered protocol family 10
[    9.830193] nf_conntrack version 0.5.0 (1959 buckets, 7836 max)
[    9.855919] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.908134] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.058859] xt_time: kernel timezone is -0000
[   10.079085] PPP generic driver version 2.4.2
[   10.096504] NET: Registered protocol family 24
[   12.652384] random: nonblocking pool is initialized
[   13.049131] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
procd: - init complete -
[   14.902142] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, half duplex, flow control disabled
[   14.912072] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready



BusyBox v1.22.1 (2014-09-02 12:43:14 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r42401)
-----------------------------------------------------
  * 1 1/2 oz Gin            Shake with a glassful
  * 1/4 oz Triple Sec       of broken ice and pour
  * 3/4 oz Lime Juice       unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup
-----------------------------------------------------
root@OpenWrt:/#


roger_ wrote:

King0fK0ng:

Can you post your OpenWrt bootlog for the Pogoplug Mobile? I'd like to add it to the wiki page.

Also if you could take a look and see if the steps on the wiki are correct then that would be great smile

vector108 wrote:

Here's my bootlog:


Thanks, added it.

vector108 wrote:

Here's my bootlog:]

Has this been pushed to the latest trunk?

mazilo wrote:
vector108 wrote:

Here's my bootlog:]

Has this been pushed to the latest trunk?

I don't think there is anything to "push". You just need to build the firmware yourself and use Kirkwood->Pogoplug E02 as the targeted system.

What we are waiting for is for the OpenWRT developers/maintainers to include the "Kirkwoork->Pogoplug E02" target into the nightly build and/or include it in Barrier Breaker RC4/Final. Currently only "Kirkwood->Generic" is included, which doesn't work on the Mobile/Series4.

King0fK0ng wrote:

I've requested that BB (Kirkwood->Pogoplug E02) to be included in the next BB release (RC4 or Final).

Just for completeness, here's the ticket: https://dev.openwrt.org/ticket/17610

Exciting news!

I just picked one of these baby up from Amazon.

Can't wait till this is fully supported.

Thanks!

King0fK0ng wrote:
mazilo wrote:
vector108 wrote:

Here's my bootlog:]

Has this been pushed to the latest trunk?

I don't think there is anything to "push". You just need to build the firmware yourself and use Kirkwood->Pogoplug E02 as the targeted system.

Yes and I see the Pogoplug E02 option under Kirkwood platform. So, if I build the Pogoplug E02, the image will work with a PogoPlug Mobile, right?

Im trying to build this using trunk, anyone who succesfully build this for the Pogo mobile/v4 please share what packages were needed besides default and how i can create an image that can de loaded on a USB/SD for booting (assuming you have uboot installed )

for me it gets stuck on:

Uncompressing Linux... done, booting the kernel.

(Last edited by yoyellow on 14 Sep 2014, 10:58)

Got it working but i kinda cheated on this one tongue

first build an image as described above, and then simply dumped the debian linux on the usbstick (replace /boot basically)

its not pretty and im sure i will find some downsides to this but for now it works...

(Last edited by yoyellow on 14 Sep 2014, 13:12)

yoyellow wrote:

Got it working but i kinda cheated on this one tongue

first build an image as described above, and then simply dumped the debian linux on the usbstick (replace /boot basically)

its not pretty and im sure i will find some downsides to this but for now it works...

Just remember, debian uses a Linux kernel naming scheme as uImage and OpenWRT uses openwrt-<platform>-uImage. If your device is flashed with a Jeff Doozan u-boot, it will expect a debian naming scheme. As such, you will either need to rename the OpenWRT Linux kernel or make the necessary changes to the u-boot environment settings so that it will recognize OpenWRT Linux kernel naming scheme. The later is a one-time job if you want to definitely use OpenWRT Linux kernel.

yoyellow wrote:

Im trying to build this using trunk, anyone who succesfully build this for the Pogo mobile/v4 please share what packages were needed besides default and how i can create an image that can de loaded on a USB/SD for booting (assuming you have uboot installed )

for me it gets stuck on:

Uncompressing Linux... done, booting the kernel.

I too have been confronting this issue. I do have a build of r42153 that loads over tftp and boots to serial console. The boot image appears to have the Pogo E02 device tree appended to it. Serial and USB appear functional, LEDs and SD socket are not. Buttons and sATA are untested.
I'll build a recent trunk and see how that goes.
<edit>
Success!
Built r42514 with generic Kirkwood config with these changes:

-CONFIG_TARGET_kirkwood_Generic=y
+# CONFIG_TARGET_kirkwood_Generic is not set
-# CONFIG_TARGET_kirkwood_POGOE02 is not set
+CONFIG_TARGET_kirkwood_POGOE02=y
-# CONFIG_TARGET_ROOTFS_INITRAMFS is not set
+CONFIG_TARGET_ROOTFS_INITRAMFS=y
+CONFIG_TARGET_INITRAMFS_COMPRESSION_NONE=y

and

-CONFIG_PACKAGE_kmod-hwmon-lm75=m
+# CONFIG_PACKAGE_kmod-hwmon-lm75 is not set

to work around the build error. Use bin/kirkwood/openwrt-kirkwood-pogoe02-uImage-initramfs

(Last edited by beata on 15 Sep 2014, 01:33)

mazilo wrote:
yoyellow wrote:

Got it working but i kinda cheated on this one tongue

first build an image as described above, and then simply dumped the debian linux on the usbstick (replace /boot basically)

its not pretty and im sure i will find some downsides to this but for now it works...

Just remember, debian uses a Linux kernel naming scheme as uImage and OpenWRT uses openwrt-<platform>-uImage. If your device is flashed with a Jeff Doozan u-boot, it will expect a debian naming scheme. As such, you will either need to rename the OpenWRT Linux kernel or make the necessary changes to the u-boot environment settings so that it will recognize OpenWRT Linux kernel naming scheme. The later is a one-time job if you want to definitely use OpenWRT Linux kernel.





Thank you for this information, i will look into this.

So far what i have found is there is the openwrt-<platform>-uImage and also a alias/symlink to this file called uImage

meaning either files should be found, thou untested so i will take a closer look.


renaming the uImage and zImage doesnt seem to be enough, its Uncompressing Linux... done, booting the kernel. again.

thou from the openwrt buil di only get uImage and zImage, nothing vmlinuz or a .img file, am i missing things..?

refering to:

usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd < that file is not in /boot in openwrt or anywhere else, i assume this is why the boot process hangs..

(Last edited by yoyellow on 14 Sep 2014, 22:32)

Quick'n'dirty:
Build with pogoE02 and initramfs.
Put an *ext3* fs onto USB media. (mkfs.ext3 /dev/whatever - I had trouble with 'unsupported features' causing a kernel panic, with a filesystem made by mke2fs.)
Mount it somewhere.
extract openwrt-kirkwood-pogoe02-rootfs.tar.gz to it.
(mkdir /somewhere/boot)
(cp openwrt-kirkwood-pogoe02-uImage /somewhere/boot/uImage)
Unmount, unplug. Boot. smile

Sorry, posts 51 to 50 are missing from our archive.