Pogoplug E02 Debian Linux Installation Guide

huge Wrote:
-------------------------------------------------------
> Is there supposed to be a load_db or just
> load_dtb?
>
> I just noticed that I have both, wondering if
> that's me making a typo somewhere along the line
> or a legit env variable.

Never mind - I think I answered my own question, and realize why I thought the load_dtb was reverting back to the wrong value - I must have mistyped the name when doing setenv, which made me think that my change wasn't persisting.

And I see now in the kernel instructions how I could easily have introduced the /dts/dts/ typo.

bodhi Wrote:
-------------------------------------------------------
> hughe,
>
> When you're done, you should post the serial
> console log and with the envs listing.

OK I'm back

I believe I've made all the changes (ie I've fixed all my mistakes) that you suggested. I will post fw_printenv output, followed by my last failed boot attempt in the console log, followed by my first successful boot (though that's before I made the setenv changes, so maybe there will be some weirdness caused by that). Let me know if you want me to post anything else.

I also changed serverip to point to my other debian box on the network (a Pogoplug V4), rather than my Windows desktop. I still haven't used netconsole, but I'm assuming it's easier to run it from a debian device than installing netconsole for Windows - correct?

Oh yeah, after I get done posting this I will find and execute the security measures you (or feas?) brought up (new SSH key & new password if I remember right).

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 back on:

fw_setenv preboot 'run preboot_nc'

And it is true. netconsole works best from another ARM Linux box such as these Kirkwood plugs. Windows is not possible. x86 Linux laptop running Ubuntu is OK, but you need to use the correct netcat binary to make it work.

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/systemd to your u-boot env bootargs.
- For example,
fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd'
- Or, if you are booting with my latest u-boot images you can also use the uEnv.txt capability to do this. In the default envs, custom_params is a variable that allows you to add extra bootargs. So add the following line to uEnv.txt:
custom_params=init=/bin/systemd
If that's still not possible to run systemd, you might want to install it again:
apt-get install systemd

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 USB drives. I'm very willing to believe my drive is not up to the task in some way, but it seems strange that it would work consistently with 4.12.1 and fail consistently with 4.13.5 (or is there something to explain that?).

I also found this thread from @rayvt, reporting that he had found the problem and fixed it. You replied "Therefore I'll merge your patch, but keeping the code about factoring usb_ready_retry env into the max spin time" but I'm not sure if that means rayvt's patch will get merged into a future u-boot or if it's already in the one I downloaded and installed. And of course there is always the high likelihood that I am barking up the wrong tree in complete ignorance - I just wanted to do whatever legwork I could before dumping it on you.

Am Newbie in the Pogo's World
My Pogo E02 boot like a charm with Arch version ArchLinuxARM-kirkwood-latest
I try to install debian on my pogo using the latest uboot.2017.07-tld-1.pogo_e02.bodhi
After update U-boot the actual version are:

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.