happydiy Wrote: ------------------------------------------------------- > pm4888 Wrote: > ------------------------------------------------------- > > Just want to add that OpenWrt 21.02 works on > E02 > > just follow the top post. > > > > Thanks a lot. > > Do you mean the first post from chessplayer / How > to install OpenWrt on Kirkwood boxeby pm4888 - Rescue System
happydiy Wrote: ------------------------------------------------------- > pm4888 Wrote: > ------------------------------------------------------- > > Just want to add that OpenWrt 21.02 works on > E02 > > just follow the top post. > > > > Thanks a lot. > > Do you mean the first post from chessplayer / How > to install OpenWrt on Kirkwood boxeby pm4888 - Rescue System
I believe you can safely ignore this package removal step.by pm4888 - Debian
moonman @ alarm forum is super informative. The clue is this Unsupported feature found (64bit, possibly metadata_csum), not mounting And the workaround is this mkfs.ext4 -O ^64bit,^metadata_csum -t ext4by pm4888 - Debian
Mijzelf Wrote: ------------------------------------------------------- > > Exactly as you point out, the chef build adds > modules to rootfs instead of integrating them into > kernel so it's no good. > That is a consequence of OpenWrt. It's designed to > run on devices which are sparse in memory and > storage. So everything which is not needed to > bringby pm4888 - Rescue System
Hope this is useful: fw_printenv(difference between default debian uboot and mine): mtdparts=mtdparts=orion_nand:1M(uboot),-(ubi) bootubi=echo Trying to boot from NAND ...; ubi part ubi; ubi read 0x800000 kernel; setenv bootargs console=ttyS0,115200 ${mtdparts}; bootm 0x800000 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootubi dmesg [ 0.6082by pm4888 - Rescue System
Just want to add that OpenWrt 21.02 works on E02 just follow the top post. Thanks a lot.by pm4888 - Rescue System
Mijzelf Wrote: ------------------------------------------------------- > pm4888 Wrote: > ------------------------------------------------------- > > Ok Openwrt for E02 has different MTD structure, > > but it is not a big deal when usb boot is used, > > right? > As long as you don't actually flash it, it doesn't > matter. > > > What'by pm4888 - Rescue System
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/boot/uboot-kirkwood/Makefile;h=d9cb10ce13affd100f71f81c7bc8389d9ee090a4;hb=HEAD PKG_VERSION:=2020.04 What's the difference say between uboot for kirkwood and uboot for rockchip? Is it just the env variables settings, or the source code of uboot needs change to support each hw line of devices?by pm4888 - Rescue System
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/boot/uboot-kirkwood/patches/140-pogoplug_e02.patch;h=53ad98291ca123078167d8b1098327be1e8fa680;hb=HEAD https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/kirkwood/patches-5.10/110-pogo_e02.patch;h=fc384d3521f960c6add3bb155457412342891994;hb=HEAD +CONFIG_MTDPARTS_DEFAULT="mtdparts=orion_nand:0xe0000@0x0(uboby pm4888 - Rescue System
Mijzelf Wrote: ------------------------------------------------------- > An initramfs kernel doesn't need to support usb or > ext4 in order to be booted from usb. It's the > bootloader who reads it from usb, and starts it. > However, if you need to access the usb filesystem > from your running OpenWrt, you can create a custom > image here: > https://chef.lby pm4888 - Rescue System
droidbox Wrote: ------------------------------------------------------- > bodhi, it rocks perfect. Now I can boot into the > Alpine Linux. Great. > > One more question ;-) > > How can I disable this message at the boot? > 1 Storage Device(s) found > Unknown command 'ide' - try 'help' > Unknown command 'mmc' - try 'help'by pm4888 - Debian
Is this why there are tutorials about installing to flash but not usb? Seems like one needs to roll own kernel at the very least to make this happen. root@OpenWrt:~# cat /proc/filesystems nodev sysfs nodev tmpfs nodev bdev nodev proc nodev cgroup nodev cgroup2 nodev debugfs nodev sockfs nodev bpf nodev pipefs nodev ramfs nodev devpts squashfs nodev jffs2 nodev overlay nodevby pm4888 - Rescue System
$ ssh root@192.168.1.x BusyBox v1.33.2 (2022-04-16 12:59:34 UTC) built-in shell (ash) _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------by pm4888 - Rescue System
bodhi Wrote: ------------------------------------------------------- > I've updated the u-boot installation post to > include Dropbox links for everything. Looks like I > will have to stop using bitly from now on. I need > to find a better shortening service. It's all good. I'm now on the latest uboot, and rebuild a rootfs on a ext4 partition on usb storage. Iby pm4888 - Debian
Found it! Google rocks. https://www.dropbox.com/s/vgbshmiq3o14btp/uboot.2017.07-tld-1.pogo_e02.bodhi.tarby pm4888 - Debian
For PogoE02 device.by pm4888 - Rescue System
Quotebodhi don't do it from scratch if you can avoid it. Yep. Also, I was browsing the forum last night and someone mentioned that they put Alpine on but there was not detail on how it was done. OpenWrt is also interesting but is there way to install to USB than flash? Thanks very much for your great work.by pm4888 - Debian
bodhi Wrote: ------------------------------------------------------- > pm4888, > > You could just create the rootfs > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > and use it. bodhi, To clarify I was able to get debian running on Pogoplug E02 with alarm uboot and your debian rootfs by following mlitke's post. The problem I ran into was I think that alarm uby pm4888 - Debian
like this? what's next? root@debian:/# apt install debootstrap root@debian:/# mkdir /bullseye root@debian:/# /usr/sbin/debootstrap stable /bullseye/ http://deb.debian.org/debian/by pm4888 - Debian
I still have alarm rescue in the flash so I'll keep the alarm uboot for now. Normally with debootstrap to prepare a disk and a boot loader it's good to go to setup a system. However I dont know how to approach these devices especially when kernel needs to be customized and dts files are involved. E.g. what it takes to prepare a debian11 system? I think it's an alarm uboot limby pm4888 - Debian
ext3 it is. This really catches me by surprise. Now that I check my alarm again it's also ext3. Perhaps alarm uboot doesnt support ext4 I wonder. I didn't give "finalized" much thought and use "sync" before reboot, because of ext4 and the journal/cache. Do you also replace alarm uboot with debian uboot, and alarm rescue with openwrt? debian uboot supports ext4by pm4888 - Debian
Any hint on what went wrong below? I followed mlitke's post, changed the dtb to pogoplug_e02 and used ext4. (rescue)# mount | grep sda /dev/sda1 on /mnt type ext4 (rw,relatime,data=ordered) (rescue)# cat uEnv.txt bootdir=/boot bootfilem=uImage fdtdir=/boot/dts fdtfile=kirkwood-pogo_e02.dtb rdfile=uInitrd root=LABEL=rootfs loadimage=load ${devtype} ${bootpart} ${loadaddr} ${booby pm4888 - Debian