bodhi Wrote: ------------------------------------------------------- > hughe, > > Glad you've resolved it! let me know how it goes > with flashing new u-boot and envs images. All went fine - I was pleased that (thanks to your buckets of help on other devices) I was able to get this one up and running with ONLY THIS ONE stupid question (that I figured out before you couldby huge - uBoot
OK ... likely I'm being dense ... can I just ignore this and skip to extracting the uBoot archive?by huge - uBoot
I apologize because I'm pretty sure I've dealt with this issue before, but I can't remember the (probably trivial) way around it: Stock PogoPlug V4, I managed to enable SSH via serial connection and am just starting to try to install uBoot. I downloaded the (current, I believe) U-boot flashing utilities and get the following error on fw_printenv: /tmp # fw_printeby huge - uBoot
bingo! I created a 411M swap partition on my rootfs SD card, stumbled around figuring out how to activate/enable it, but now apt-show-versions & webmin are installed without error. Now I'll have to educate myself about swap files - in poking around I saw that bodhi prefers a swap file to a partition, and I also saw indication that the best medicine of all is running zswap... Tby huge - Debian
Pogo V4 running Debian 4.13.5, trying to install webmin which requires apt-show-versions, logged in as root: I've read various threads elsewhere (and one here) about the same problem but the primary suggestion I've found: apt-get -o Acquire::GzipIndexes=false update doesn't seem to help me: root@debian:/tmp# apt-get -o Acquire::GzipIndexes=false update Ign:1 http://ftp.by huge - Debian
ARRRGGHHH ... Well, I'm glad I got my fun little moment of pointing out to you that the Mobile only had one USB port, not two ... I've been messing around with my 3 Mobiles so much that I completely forgot that my V4 had a pop-off top with a USB (& SATA) port. Like I said, it's been just sitting there running off of an SD card for well over a year. It boots fine off the saby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > Nothing will go wrong! Keyboard will tell if this > device is enumerated. Execute > > usb start Sadly the results of various USB commands are all unpromising (with the USB stick plugged in to the top port and a keyboard in the bottom, after failing to boot from the USB stick). It certainly does look like itby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > you can use the top USB slot in Debian? > Yes. Following is with two rootfs USB sticks plugged in (after booting from mmc/SDcard: root@debian:~# root@debian:~# root@debian:~# fdisk -l Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physicaby huge - uBoot
Perhaps should have posted printenv output: root@debian:~# fw_printenv arcNumber=3960 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_by huge - uBoot
bodhi Wrote: ------------------------------------------------------- > > means that it's choking on my USB stick, or > > failing to properly communicate with the USB > port? > > > > It is choking on your USB stick only. The port is > fine. > It looks like either there is something wrong with the port or (maybe more likely?) something going wroby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > huge, > > But your bootlog showed it is not OK with the USB > drive: > > > scanning usb for storage devices... 0 Storage > Device(s) found > > So the USB drive is not recognized by u-boot. > > If this is the Pogo V4 (not Pogo Mobile) then you > must use the top USby huge - uBoot
I'm trying to upgrade to the new uBoot (and rootfs) on my Pogoplug V4, previously on an older Debian kernel/rootfs & older uBoot. This is the first time I've been upgrading uBoot from something older than the 2016 release, so I had to go through the extra "step 8" nandwrite. I'm hoping that's the source of my (hopefully simple) problem. I have been booting frby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > huge, > > You have serial console, so there is no need to > set up netconsole now. You can always wait until > after the system has been up and running well. > > Quote10. Set up netconsole. It's important to > set up neconsole if you don't already have > serial console connectedby huge - uBoot
Having contributed some humor in my last post, now I have a question or two... I have two Pogoplug Mobiles that I currently can't make serial connections to. They both seem to have the little blob of solder missing from the GND connector on the circuit board (the other three dots all have a little bit of solder bulging up from the board). I don't have a soldering iron so I'veby huge - Off-Topic
Submitted for your amusement: Check out the date on this "Knowledge Base" entry on how to enable SSH access on Pogoplug.com. Did they really post these instructions a week ago? https://support.pogoplug.com/hc/en-us/articles/202307860-How-do-I-enable-SSH- In case they delete it, it has the old "enable SSH over the internet" instructions, which as far as I know stopped woby huge - Off-Topic
Thank you thank you thank you... I've gone through most of the process without apparent problem or too much confusion. I'm just up to "12. Set up netconsole". I've looked at my env's & found several that needed changing (dtb_file, ipaddr, serverip, ethaddr, others) So I'm going to post my env's now before I go to bed. Tomorrow I'll set upby huge - uBoot
I'll list the steps as you have them numbered under "Flashing Instruction"... 1. uBoot envs config and mtd partitions must be defined as followed in your rootfs cat /etc/fw_env.config # cat /etc/fw_env.config /dev/mtd0 0x00100000 0x20000 0x20000 My fw_env.config file looks as you expect, but I'm assuming I need to edit it on my USB stick, changing mtd0 to mtd1,by huge - uBoot
bodhi Wrote: ------------------------------------------------------- > huge, > > > # cat /proc/mtd > > dev: size erasesize name > > mtd0: 08000000 00020000 "NAND 128MiB 3,3V > 8-bit" > > mtd1: 00e00000 00020000 "boot" > > mtd2: 07200000 00020000 "rootfs" > > This is stock mtds definition. It is basicallyby huge - uBoot
Great, thank you. I installed the USB rootfs on another Pogo (log posted below, but all seemed fine). I went to start the u-boot install on my Pogo Classic, but I got different contents in /proc/mtd than your instructions called for. I'm guessing this is a function of my particular setup, but I don't know whether it makes any difference in the following steps. Your instructions: cby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > On Pogo V4 (must have IP 192.168.222.164), try > > > > > > nc -lup 6666 192.168.222.168 6666 > > Success, thank you! Actually that exact command got me an error message, but that led me to a post (from yby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > huge, > > There should be no problem with Pogo E02 > netconsole. You probably have some wrong envs. I'm noticing a couple of differences between current envs and what I posted back in the vast E02 install thread last week. The old ones look possibly more robust using variables instead of static addresby huge - uBoot
feas Wrote: ------------------------------------------------------- > your serverip for the Pogo V4 > "serverip=192.168.222.164" is correct and you have > started netconsole on it before booting the E02? Yes ... I think I have that part right: V4 IP address (== serverip on E02): .222.164 E02 IP address (== ipaddr on E02): .222.168 And on the V4 I type root@Pby huge - uBoot
I hope this is the right place to post this - I'm mostly concerned about U-Boot issues... I have an old Pogo-Classic (B01) running ArchLinux that I installed years ago. It was my first Pogoplug (almost my first linux experience) - I installed Samba, got it booting from a 3TB SATA drive, and used the rest of the drive as a server for my home network (mostly without problems, kind of miracuby huge - uBoot
I got netconsole to work for a while (though read-only - I did not get the background process to work for read-write access), but now after upgrading to the new (2017) uboot I can't see any console output. My "desktop" is a Pogo V4, the device I want to watch is a Pogo E02. Here's the netconsole output from two reboots when it was working: root@PogoV4Debian:/boot# nby huge - uBoot
bodhi Wrote: ------------------------------------------------------- > huge, > > > > root@PogoV4Debian:/temp# ./kwboot -t -B 115200 > > /dev/ttyUSB0 -b > > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > > > > > > When it stuck here, it might mean that your serial > connection is not solid. At this point u-boot has > not started yet,by huge - uBoot
Hi bodhi - I'm bbaaaaaacckkk (hopefully this won't be as epic a journey as with my E02 from a few days ago, and thanks again for all the help there by the way). I have a Pogoplug Mobile which I must have messed up some time ago - it won't boot, but when I connect via serial I see some envs that look like they belong with an E02 and not a V4/Mobile. I'm trying now to &quoby huge - uBoot
huge Wrote: > I assume the only/last thing left to do before > starting to actually use the thing is to upgrade > to the 4.13.5 kernel? > Oops, not so fast. After upgrading to 4.13.5 I get the dreaded "EHCI timed out on TD" & "ext4fs_devread read error", consistently. I found various threads about these errors, most of which point to lower-quality USby huge - Debian
bodhi Wrote: ------------------------------------------------------- > hughe, > > Everything looks good! > WOOHOO! > And you don't have to turn on netconsole, if you > intend to keep the serial console connected. > > fw_setenv preboot > > When you want to turn on netconsole (i.e. removing > serial console for other duty), you can turn it >by huge - Debian
I used to know something about "systemd" (when I was playing with Arch on my Pogo-B01) but it is gone from my brain now. Can you instruct me in what to do, if anything, with the following instructions from the end of rootfs install? Feel free to tell me to figure it out for myself if it's just a matter of preference. Note2: To boot with systemd, add parameter init=/bin/sysby huge - Debian
Looking back through the thread I found this request for info/posting, which I seem to have overlooked. bodhi Wrote: ------------------------------------------------------- > > Check system state: > > uname -a > dpkg -l | grep linux-image > ls -lart /lib/modules/ -d > cat /proc/mtd > dmesg | grep -i bad > mount > > > Now given you have instby huge - Debian