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 conby huge - Debian
OK ... I'll get back to fixing those before I reboot. For now I have to sleep and then I'll be away from my computer for tomorrow. Thank you so so so much for all your help and patience. -hugeby huge - Debian
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 theby huge - Debian
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.by huge - Debian
bodhi Wrote: ------------------------------------------------------- > > That's why I showed above how to get a complete > serial console input/output back without having to > clear preboot env for netconsole. And also asked > hughe for the envs so I can adjust them. You posted this right as I was finishing my eventual success story. Here's fw_printenv, let meby huge - Debian
bodhi Wrote: ------------------------------------------------------- > > Either the booting envs or the kernel > files on USB are incorrect. In this case, it > looks like the envs. Because the rootfs is OK, if > that was all you did in this post: > https://forum.doozan.com/read.php?2,29068,39664#msg-39664 > > > Power up, interrupt serial console and >by huge - Debian
OK, I finally pried the case apart and connected the serial cable. Here is the screen output from trying to boot with the most recent USB stick I created (freshly formatted ext3, installed latest rootfs: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: sby huge - Debian
OK, tried again with a freshly-formatted USB stick, same result. Here is the log of my screen installing the Debian Stretch Kirkwood rootfs. If you see anything missing or wrong, let me know. If not I'm happy to try to wrangle a serial cable connection... # # # fdisk /dev/sdb Welcome to fdisk (util-linux 2.23.1). Changes will remain in memory only, until you decide to write theby huge - Debian
feas Wrote: ------------------------------------------------------- > makes me wonder if your sticks are part of the > problem as some types seem to cause problems > booting reliably. I know I've used one of them before (successfully) to boot other Pogos, but the other two are cheap and/or old.by huge - Debian
bodhi Wrote: ------------------------------------------------------- > By the way, > > This is a good example of how much time we waste > because there is no serial console :) If there > were a serial console connected, most booting > problems can be solved in minutes. I actually think I can get a serial connection working, if I'm right that the E02 has a littleby huge - Debian
bodhi Wrote: ------------------------------------------------------- > huge, > > > (by commenting out the > > extra lines for tmpfs, swap file, devpts) > > Sorry, that's not what I intended to say! I meant > the rootf device must be like: > > LABEL=rootfs / ext2 > noatime,errors=remount-ro 0 1 > > You can leave theby huge - Debian
I didn't really think these would work (and they didn't) but I tried the following changes one at a time before power-cycling my E02 and checking for a router connection: 1. Gave my first USB stick the "rootfs" label 2. edited the fstab files in each USB stick to look exactly like yours (by commenting out the extra lines for tmpfs, swap file, devpts) 3. tried the fronby huge - Debian
bodhi Wrote: ------------------------------------------------------- > @feas, > > > Sorry huge and Bodhi, I wanted to clean my mess > > from my original posting like a big boy. > > Nah, nothing to sorry about. I've checked out > everything, and it's all looking good :) there is > nothing wrong that I can tell from hughe post > above. >by huge - Debian
Well, I tried power-cycling & starting again with the same USB, then powering up with the 2nd USB - same result of fast blinking LED followed by steady LED but no connection to router (my router assigns it a static/reserved ip address, and even if that didn't work I can always tell if a new device has connected, so I knew pinging debian.local wouldn't work but I tried it anyway). Tby huge - Debian
D'OH!! The LED blinked and then went solid just like it should, but after about ten minutes it still hasn't made a connection to my router (and I checked to see if it somehow grabbed another IP address). I assume the only thing I can do now is (A) power-cycle it and try again (maybe leaving it powered down for a few minutes), (B) try the other USB stick and then, gasp, (C) try crby huge - Debian
OK, will do! Amusingly, right when your post came in, I was finally able to make a serial connection to my unresponsive Pogo Mobile using (don't laugh) bare wires and masking tape (OK you can laugh) because I don't have a soldering iron. I was about to ask you how to recover it when I found your response 3 years ago to someone in a very similar situation telling him You are runninby huge - Debian
sda1 is the first USB stick I used to go through feas' long-way process of updating from kernel to kernel, but now should have the latest kernel installed. I realize that his is the one you are evaluating for consistency. This is the one that is Ext2 - I'm guessing that's OK? sda2 is my 2nd USB stick with which I basically followed your instructions. On this one I installed theby huge - Debian
Is it OK that my USB stick is ext2? (I made the second one ext3 but I must have just forgot with the first one)by huge - Debian
OK, ready or not, here it comes: debian:/boot# debian:/boot# debian:/boot# uname -a Linux debian 3.16.0-4-kirkwood #1 Debian 3.16.48-1 (2017-09-28) armv5tel GNU/Linux debian:/boot# debian:/boot# debian:/boot# dpkg -l | grep linux-image ii linux-image-2.6-kirkwood 3.2+46 armel Linux for Marvell Kirkwood (dummy package) rc linux-image-2.6.3by huge - Debian
bodhi Wrote: ------------------------------------------------------- > feas Wrote: > ------------------------------------------------------- > > I am concerned that uname -a is still showing > old > > kernel. is it old man pill time again? > > That's OK. It is still running the old kernel. THAT'S WHAT I THOUGHT!!!! lol ... joking ... you guys areby huge - Debian
feas Wrote: ------------------------------------------------------- > I am concerned that uname -a is still showing old > kernel. is it old man pill time again? > Other than that I think he is set if you wouldn't > mind checking his fw_printenv. > > Side note he does not have serial cable and may > need to download netconsole for windows, then if > all is goby huge - Debian
uname -a still reports old kernel (I had thought it wouldn't report the new one until after I had rebooted, but your concern has to mean that was wrong) posting a couple of commands before uname and fw_printenv since they seemed potentially relevant: debian:/boot# debian:/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.13.5-kirkwood-tld-1 -d vmlby huge - Debian
Running dkpg again I got the following screen (not surprising, but I don't know whether I can ignore it or not): │ You are attempting to install a kernel image (version 4.13.5-kirkwood-tld-1) However, the directory /lib/modules/4.13.5-kirkwood-tld-1/kernel still exists. If │ │ this directory belongs to a previous linux-image-4.13.5-kirkwood-tld-1 package, and if you have deselby huge - Debian
feas Wrote: ------------------------------------------------------- > > ok, it looks like you have finished section > "C" to "DONE" > > If that is correct you need go back up to "step > 9" to continue. > > Verify your E02 ipaddress and the system you will > use as the serversip. > > Don't reboot till your repost fby huge - Debian
feas Wrote: ------------------------------------------------------- > > yes you need to update as the instructions say > since this hasn't been done yet OK now after running those, my fw_printenv: debian:/boot# debian:/boot# debian:/boot# fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $by huge - Debian
*WITHOUT* running those fw_setenv lines in question, printenv looks like this: debian:/media/sdb1/boot# debian:/media/sdb1/boot# debian:/media/sdb1/boot# fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uby huge - Debian
Roger that. With this instruction: - Set U-Boot envs for booting. The u-boot envs below are for 1st time upgrading, you don't need to do this step if you've installed the latest U-Boot for Kirkwood. Just make sure the DTB file is the correct one for your box, replace kirkwood-goflexnet.dtb below with the correct DTB name for your box. fw_setenv load_dtb 'ext2load usb 0:1by huge - Debian
feas Wrote: ------------------------------------------------------- > you can run "uname -a" to see the running kernel > to verify. I still haven't finished updating kernel so uname -a still returns: Linux debian 3.16.0-4-kirkwood #1 Debian 3.16.48-1 (2017-09-28) armv5tel GNU/Linuxby huge - Debian
I'm guessing the "Hmm" and "no arrays" messages are not a concern? debian:/boot# dpkg -i linux-image-4.13.5-kirkwood-tld-1_1.0_armel.deb Selecting previously unselected package linux-image-4.13.5-kirkwood-tld-1. (Reading database ... 31003 files and directories currently installed.) Preparing to unpack linux-image-4.13.5-kirkwood-tld-1_1.0_armel.deb ... Done. Unpaby huge - Debian
feas Wrote: ------------------------------------------------------- > ok, to be honest I am getting confused with you > jumping between doing two usb's at the same time. > So lets do one then the other. > > 1st usb > > From where you were when we left off you needed to > install the new kernel which will give you the > correct files to append to it to fby huge - Debian