uInitrd was less than 6MB, so good there. I powered down, moved the SD card to the SD card slot, powered back up and all is good! Thank you VERY much for all your help! Ralphby rsantag - Debian
Ah - that was it! created a swapfile and dpkg ran this time & created my initrd.img-6.6.3-kirkwood-tld-1. Will run mkImage again and see if it will come up off the SD directly.by rsantag - Debian
bodhi Wrote: ------------------------------------------------------- > You have to install the kernel on the Pogo V4 > itself while it is running. Sounds like you are > trying to install it on another Linux host. Right, I'm doing all this on the Pogo V4 that's running Debian 12 from the USB-SD adapter. Downloaded linux-6.6.3-kirkwood-tld-1-bodhi.tar.bz2, extracted it wiby rsantag - Debian
Nope, that didn't help. I did check the md5sum of linux-6.6.3-kirkwood-tld-1-bodhi.tar.bz2 and it is good. The end of stream is apparently because decompress is failing Quoteroot@debian:~# dpkg -i linux-image-6.6.3-kirkwood-tld-1_1_armel.deb (Reading database ... 16869 files and directories currently installed.) Preparing to unpack linux-image-6.6.3-kirkwood-tld-1_1_armel.deb ... Unby rsantag - Debian
I did "dpkg -V linux-image-6.6.3-kirkwood-tld-1_1_armel.deb" to verify it was installed and it said "not installed". I was sure I did the install (shows up in my bash history), but I went ahead and ran it again. Install failed. Didn't notice the errors last time. Assuming that's where initrd.img-6.6.3-kirkwood-tld-1 comes from. Got "cannot copy extractedby rsantag - Debian
OK, thank you! That worked to get it to boot (I used a USB-SD adapter - option 3) I'm now trying to install the 6.6.3 kernel. I'm assuming for the 1st mkImage I'm using linux-6.6.3-kirkwood-tld-1.patch instead of linux-6.6.3-kirkwood-tld-1. For the 2nd mkImage, I don't see initrd.img-6.6.3-kirkwood-tld-1. Doesn't appear to be contained in linux-6.6.3-kirkwood-tld-1by rsantag - Debian
OK, according to note #2, it says /etc/rc.local generates new SSH keys on 1st boot. I mounted the SD on another box and I don't see any /etc/ssh/ssh_host_* files. So maybe it isn't actually coming up?by rsantag - Debian
I've been running the Debian 11 image on my Pogoplug V4 for some time. I saw that there is a Debian 12 image (Nov 1, 2023), so decided to give that a try. I'm using the 2017 U-boot, which I assume should be fine. This device doesn't have any USB 3.0 ports, so not sure the 2023 U-boot would buy me much. I partitioned a 16GB SD card, labeled as "rootfs", created ext3by rsantag - Debian
Note that, since it can't boot off the SD card, it boots up the old Cloud Engines environment, which then mounts the SD card with no problem. Quoteroot@PogoplugMobile:~# df Filesystem 1K-blocks Used Available Use% Mounted on ubi0:rootfs 99432 11768 87664 12% / none 59312 8 59304 0% /tmp /tmp/.cemnt/mmcblk0p1by rsantag - Debian
I'm trying to create a bootable image on a Verbatim SD card (actually, microSD + adapter). I've done this dozens of times with PNY, SD cards, PNY microSD cards and Sandisk microSD cards, but I'm having no luck with a couple of Verbatim cards. All cards are 16GB. I partition the disk, create the file system, label the partition "rootfs" and extract everything from a tby rsantag - Debian
I have a Pogoplug Mobile that I've updated with the latest uboot. It boots debian off the SD card just fine, but I also set these environment variables so it would boot the original Cloud Engines OS if there's no SD card inserted: Quotebootcmd_exec=if run load_uimage; then if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bby rsantag - uBoot
bodhi Wrote: ------------------------------------------------------- > My suggestion: if the box is located at a > non-technical person household, then don't > activate netconsole at all. Yeah, it's at a non-technical person's house. I told him he should log in and clear preboot variable with fw_setenv.by rsantag - Debian
bodhi Wrote: ------------------------------------------------------- > Netconsole stopped at kernel booting, but we can > also enable it in Debian this way: > Oops, misread your reply. Was thinking you answered my last question. So, do you know why it would go from solid green to blinking green after plugging in the Ethernet cable? Was it not really booted up when it was solby rsantag - Debian
bodhi Wrote: ------------------------------------------------------- > Netconsole stopped at kernel booting, but we can > also enable it in Debian this way: > > https://forum.doozan.com/read.php?2,9522 > > So check that to make sure you want it active or > inactive after Debian has run. Thanks! (sorry, didn't see this reply before my last post) rsantagby rsantag - Debian
Thanks Bodhi. So, I'm curious. When it was powered up without network connected and light turned solid green, I assumed it was booted up. But was it instead really still in uboot, waiting for network? And when network was plugged in, it resumed uboot, resulting in the netconsole false positive and blinking green? rsantagby rsantag - Debian
Update: He took his wife's phone off the network and the Pogoplug came right up. So you were right, Bodhi, it WAS netconsole. I would love to know where the netconsole hooks are that apparently tries to enable it after the box is already up. At least, I assume the box was up since light was solid green. rsantagby rsantag - Debian
Interesting. I thought that if it came up with no network connection, the pings in if_netconsole would all fail, so start_netconsole wouldn't run. But there must be another piece of this after it's up and subsequently the network goes active that I'm missing. I know serverip is set on the Pogo to 192.168.1.162, which is what I use for netconsole here, and he DOES have a deviby rsantag - Debian
I have a Pogoplug Mobile that was flashed with Uboot 2017.07. It's running Debian 9 with the 5.8.3 kernel. I can boot it with no problem. Light goes solid green in under a minute, and can log in soon after. So, I sent it to another guy who says it never goes past blinking green. I read a post that netconsole can cause this if serverip isn't active when it comes up, although it doby rsantag - Debian
OK, thanks. Yeah, that worked fine. I also enabled stock recovery environment, as described at https://forum.doozan.com/read.php?4,22570,22570#msg-22570, but did it slightly differently. I changed the "run load_uimage" in bootcmd_exec to "if run load_uimage; then", and added an "else" at the end to run bootcmd_stock, like this: Quotebootcmd_exec=if run loadby rsantag - uBoot
Hello. I just picked up a Pogoplug Pro that is still stock. I'm wanting to set up the Bodhi uboot and rootfs. I'm following https://forum.doozan.com/read.php?3,16017 and it says /proc/mtd should look like this: Quotedev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data" However, mine looks like this: Quoteroot@Pogoplby rsantag - uBoot
Woohoo! It's up! I plugged the SD card into a USB reader and put that into the Pogo. The other stuff I did was set mtdparts and partitions back to the way they were before, and added root=LABEL=rootfs and rootdelay=10 to bootargs. I'm guessing root=LABEL=rootfs may have been key. THANK YOU VERY MUCH! Ralphby rsantag - Debian
OK, I was trying to use rootfs on SD card. I'll try using a USB drive. Ralphby rsantag - Debian
On the outside chance rootfs on MTD1 is OK, and the only reason it wouldn't boot stock OS was because of some environment variable problem (I have no idea what the previous owner did to it before I got it), is there a command/commands I can run from CE uboot to try to boot into the old OS? Ralphby rsantag - Debian
Well, not having a lot of luck getting openwrt to compile... Decided to go ahead and try manual load/boot of bodhi's kernel. Pogo went from blinking green to solid green, but not seeing it come up on the network. Console log is below. Note that I am using an older 3.18.5 kernel that doesn't use a dtb_file. QuoteCE>> tftpboot 0x800000 uImage Using egiga0 device TFTP fromby rsantag - Debian
Bodhi, I've never been able to boot to the original OS on this Pogo. If I manually load and boot your uImage from CE uboot via tftp, will it find the MMC or USB root file system and come up? If not, plan B is to try to recompile openwrt with MTD_WRITEABLE=1. But if you think plan A will work, I'll try that first. Ralphby rsantag - Debian
Hmm, interesting. That explains the permission denied error. How do I boot from USB using the original CE u-boot? I see diskboot command to boot from IDE, but don't see anything for USB. QuoteCE>> help ? - alias for 'help' base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcby rsantag - Debian
Not sure if you need this, but here is console output QuoteCE>> tftpboot 0x800000 uImage Using egiga0 device TFTP from server 192.168.1.162; our IP address is 192.168.1.50 Filename 'uImage'. Load address: 0x800000 Loading: ################################################################# #################################################################by rsantag - Debian
Same error on root file system. Quoteroot@OpenWrt:/mnt/tools# ls -al drwxr-xr-x 2 root root 180 Nov 4 04:45 . drwxr-xr-x 3 root root 60 Nov 4 04:45 .. -rwxr-xr-x 1 root root 1616492 Nov 15 2010 busybox -rwxr-xr-x 1 root root 787036 Jun 20 2011 e2fsck -rwxr-xr-x 1 root root 25632 Jun 30 2014 flash_erase -rw-by rsantag - Debian
Same "not found" error as with the other one I tried. Quoteroot@OpenWrt:/tmp/tools# ls -l -rwxr-xr-x 1 root root 1616492 Nov 15 2010 busybox -rwxr-xr-x 1 root root 787036 Jun 20 2011 e2fsck -rwxr-xr-x 1 root root 25632 Jun 30 2014 flash_erase -rw-r--r-- 1 root root 329 May 17 2016 fw_env.config -rwxr-xr-x 1 rootby rsantag - Debian
Hi Bodhi. I haven't actually flashed your u-boot yet. I was trying to do the flash_erase so I could do that. I'm assuming it's running the Cloud Engines uboot because uboot prompt is "CE>". But not sure everything on this device is still stock - I bought it used and when I got it it wouldn't boot to the original OS. And notice /proc/mtd doesn't look noby rsantag - Debian