Bodhi does travel and might not be able to answer right away so you might want to try these to get closer before he can respond. Have you setup the Debian rootfs on a usb stick per Bodhi's instructions? If not go to here and scroll down to: Updated 24 Jul 2017: and follow the instructions skipping step 4. It looks like there was a problem setting the environment variables, folby feas - uBoot
so it came down to a typo in the dtb location? eitherway, glad you are up an runningby feas - Debian
>e. Modify the following u-boot variables using fw_setenv: >Note that setting arcNumber and machid are not necessary if you are booting with FDT kernel 3.17+ in >the latest kernel and rootfs thread. But it's required for non-FDT kernel. >Also note that only some boxes need machid, some don't (so the command fw_setenv machid below clears >them). > Uncompreby feas - Debian
makes me wonder if your sticks are part of the problem as some types seem to cause problems booting reliably.by feas - Debian
Sorry huge and Bodhi, I wanted to clean my mess from my original posting like a big boy.by feas - Debian
huge Wrote: ------------------------------------------------------- > 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. > > > &by feas - Debian
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 good he may want to regen ssh-keys and change passwd.by feas - Debian
yes stop and move on to 4a thenby feas - Debian
huge Wrote: ------------------------------------------------------- > 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. > > > > Vby feas - Debian
huge Wrote: ------------------------------------------------------- > 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_printby feas - Debian
huge Wrote: ------------------------------------------------------- > 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, replby feas - Debian
ok finish the kernel and then finish the u-boot instructions but run "uname -a" and "fw_printenv" and post them to take a look.by feas - Debian
huge Wrote: ------------------------------------------------------- > 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 directby feas - Debian
huge Wrote: ------------------------------------------------------- > >1st USB ... In installing rootfs on 2nd USB I realized that I had the .dtb file that was called for in the >u-boot instructions, so I copied the file to /boot/dts & finished the u-boot steps. I have *not* installed the >new kernel on the 1st USB drive. I was going to wait to do that until I made sure I couldby feas - Debian
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 finish the u-boot install for that stick and writing to your e02. Which will leave you with the current new kernel and aby feas - Debian
give me a min i and rereading your post to understand it all to give responseby feas - Debian
So was I correct to tell Huge to install your latest kernel now and then finish the uboot install from where he is now to get the /boot/dts file for u-boot?by feas - Debian
huge Wrote: ------------------------------------------------------- > feas Wrote: > ------------------------------------------------------- > > do the kernel but don't reboot then continue > with > > u-boot is what i am thinking. > > Great, thanks. I think I'll pick this up tomorrow. > > > I know I've thanked you repeatedly, but I&by feas - Debian
huge Wrote: ------------------------------------------------------- > feas Wrote: > ------------------------------------------------------- > > > > > > You can set the ip address for a system that > would > > act as a ftp server to pull files for booting > and > > or act as the interface for netconsole. This is > > not really needed ifby feas - Debian
do the kernel but don't reboot then continue with u-boot is what i am thinking.by feas - Debian
huge Wrote: ------------------------------------------------------- > Maybe I should just post my printenv output and > see if everything looks OK. Two things that I > notice are: > > dtb_file=/boot/dts/kirkwood-pogo_e02.dtb > > (when I don't have a /boot/dts directory and that > .dtb file does not appear anywhere under / ) > > > And then ipaby feas - Debian
huge Wrote: ------------------------------------------------------- > In the U-Boot instructions, > > I'm in "B. Flashing default u-boot envs image", > sub-step "f. Adjust the DTB name to boot with a > rootfs that has FDT kernel (this is the normal > case): > > > Find your box DTB file in the rootfs /boot/dts > directory and adjusby feas - Debian
huge Wrote: ------------------------------------------------------- > I should have noticed that the very next text > after the mtd0 etc numbers is also confusing to me > ... Bodhi's Uboot instructions: > > > dev: size erasesize name > mtd0: 00100000 00020000 "u-boot" > mtd1: 00400000 00020000 "uImage" > mtd2: 02000000 00020000 &qby feas - Debian
huge Wrote: ------------------------------------------------------- > Much thanks to you both! (Bodhi's post fixed my > LED too of course) > > I may have taken the long road, but I know so > little of this stuff that it's probably just as > well. > > > So the next thing I'm going to try is to install > the new uBoot (2016.05-tld-1) and kby feas - Debian
huge Wrote: ------------------------------------------------------- > I did the next update/upgrade step and all seemed > to go well - a couple of warnings that didn't seem > serious, like "can't delete xxx, directory not > empty", but no Errors and it seemed to finish > normally. > The install doesn't always clean itself very well. no worriby feas - Debian
These are commands that run at system start and are personal preferences. I would select for myself in the new file: TMPTIME=0 # will delete the temporary files on boot DELAYLOGIN=no # Can interrupt incase of issues VERBOSE=yes # I like seeing stuff FSCKFIX=yes # Will repair any issues if not shutdown properly No wrong anby feas - Debian
I am thinking it was the lack of backports that was causing the issue before but glad it is progressing. Sorry for any confusion I caused about using Bodhi's method. I have edited my post to try and make it clearer.by feas - Debian
All small stuff. Going with the defaults is fine. Glad it progressing so far.by feas - Debian
huge Wrote: ------------------------------------------------------- > > > > list the output from the update and upgrade > > commands in entirety. > > > > I'm not sure how to do that. My terminal window > only has the last 100-ish lines saved, and because > I have 3 other Putty/SSH windows open, my > putty.log file is from another more recenby feas - Debian
huge Wrote: ------------------------------------------------------- > > > > list the output from the update and upgrade > > commands in entirety. > > > > I'm not sure how to do that. My terminal window > only has the last 100-ish lines saved, and because > I have 3 other Putty/SSH windows open, my > putty.log file is from another more recenby feas - Debian