feas Wrote: ------------------------------------------------------- > give me a min i and rereading your post to > understand it all to give response lol no problem, you can take more than a minby huge - Debian
bodhi Wrote: ------------------------------------------------------- > > When hughe installs the new kernel, the DTS > directory will be populated by the tar command to > extract DTB files. And then install u-boot right > away (don't reboot), which will populate the new > default envs. The new default envs tells u-boot to > boot the new kernel, which already hasby huge - Debian
feas Wrote: ------------------------------------------------------- > huge Wrote: > ------------------------------------------------------- > > > > I know I've thanked you repeatedly, but I'll > keep > > doing it - you're being really helpful, thanks. > > i feel bad for setting you down a round about way > with my post. i did it beforby huge - Debian
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'll keep doing it - you're being really helpful, thanks.by huge - Debian
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 if you are not doing that. It's > is a good idea to set the system ip for > consistency. I would check that yourby huge - Debian
feas Wrote: > > I believe the instructions are for coming from > installing his latest kernel first which includes > the dtb directory in /boot. > > I think you could do that then continue here. Do you mean pause in the U-Boot instructions & install the latest kernel? Or just dig around and find the one .dtb file I need and copy it to /boot/dts?by huge - Debian
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 ipaddr / serverip are set to 192.168.0.231 / 192.168.0.220, whereas I use a different 192.168.xxx.yyy in my home network. This boxby huge - Debian
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 adjust the env to it. Can/should I just ignore this step? I don't have a /boot/dts directory, and the only .dtb filesby huge - Debian
Cool, thanks ... sounds like I can move forward with what I have ... sorry for the paranoiaby huge - Debian
bodhi Wrote: ------------------------------------------------------- > > The above mtd definition is correct for Pogo E02. > The last mtd3 is irrelevant. When we install new > u-boot, mtd0 is what count. The rest you can > safely ignore. Woohoo! Thanks (and it's OK that my fw_env.config only has one line in it?)by huge - Debian
No that's all I have (which, yeah, is another level of confusion that I only have one line): debian:/tmp# debian:/tmp# debian:/tmp# cat /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundant # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR. # MTby huge - Debian
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 "rootfs" mtd3: 0db00000 00020000 "data" If you don't have /etc/fw_env.config file in yourby huge - Debian
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 kernel (4.13.5-kirkwood-tld-1) on another USB stick. Right away I'm confused about something that probably should beby huge - Debian
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. Then I thought something was wrong after reboot - the LED on the front of my Pogoplug did not come on and I did not see it in the list of connected devices on my router, Iby huge - Debian
Maybe this doesn't matter, but I took a closer look at the versions of /etc/default/rcS and found that the one installed during dist-upgrade is entirely commented out: # # /etc/default/rcS # # Default settings for the scripts in /etc/rcS.d/ # # For information about these variables see the rcS(5) manual page. # # This file belongs to the "initscripts" package. # deleteby huge - Debian
feas Wrote: ------------------------------------------------------- > All small stuff. Going with the defaults is fine. > Glad it progressing so far. dist-upgrade finished without nasty errors this time (there are a couple of warnings but they don't look serious to me). For completeness' sake I'll post the rest of the output... Installing new version of config fiby huge - Debian
I followed both of your suggestions (removing nfs-common & adding the backports line to sources.list) Output from update: debian:~# apt-get update Get:1 http://security.debian.org wheezy/updates Release.gpg [1,554 B] Hit http://security.debian.org/ wheezy/updates/contrib Translation-en Ign http://security.debian.org/ wheezy/updates/contrib Translation-en_US Hit http://security.debiaby huge - Debian
I went ahead and ran the update / upgrade / dist-upgrade commands again, this time separately, but of course now that most of the work has been done there's not so much output to look at. But just in case it's helpful: debian:~# apt-get update Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://ftp.us.debian.org/debian/ wheezy/contrib Translation-en Ign http://ftp.us.debiby huge - Debian
> > 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 recent screen. I have the term.log file which I think covers everything from the last reboot, but looking at it doesn'by huge - Debian
feas Wrote: ------------------------------------------------------- > huge Wrote: > ------------------------------------------------------- > > feas Wrote: > > > ------------------------------------------------------- ... > > > usually after an error as you mentioned it will > say to run "sudo apt-get -f install" to force the > install &by huge - Debian
feas Wrote: ------------------------------------------------------- > your doing this from an previously unmolested > E-02? didn't it prompt to run apt-get -f install? > or try aptitude and see the resolver > recommendation. I believe I may have secured SSH access on my E02 a couple of years ago, but I think that's the most it's been molested. I could be wrong tby huge - Debian
I've been running through these instructions with my Pogoplug E02 - a few minor bumps in the road but now I've run into something that seems more serious (this happens after I add wheezy repos, update keys & update the system) Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Failed The following packages have unby huge - Debian
november17 Wrote: ------------------------------------------------------- > ... > > Really though, I got the stuff I needed to > establish a serial connection for about $5 total > and didn't even bother soldering, just taped the > pins on.Its not that complicated. Sorry to reply to an old thread, but can you (or anyone) describe how you did it with tape? My soldby huge - Off-Topic
bodhi Wrote: ------------------------------------------------------- > @huge, > > No, you don't need to install kernel. You only > need to create Debian rootfs following this > section: > > > Updated 02 Sept 2014 (rootfs): > > Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. > This rootfs is to keep in sync with kernel > Linux-3.16.0-kirby huge - Debian
bodhi Wrote: ------------------------------------------------------- > huge, > > > - I can do all this on my Pogoplug running Arch > > right? (I don't have to use my Ubuntu box?) > > - I just format the USB stick as Ext3, with one > > partition, correct? > > Yes, any Linux system is fine. Arch Linux uses the > same commands. > Hi boby huge - Debian
Thanks bodhi! Since I'm not grasping a fair amount of the language in the two (or more) threads I'm trying to follow, can you sanity-check what I think I'm about to do? 1. Connect new USB stick for Debian boot to a linux box ... ok wait, I already have questions (!): - I can do all this on my Pogoplug running Arch right? (I don't have to use my Ubuntu box?) - I justby huge - Debian
bodhi Wrote: ------------------------------------------------------- > Hi huge, > > Welcome to forum! Thanks for your quick reply - really appreciate the help > Are you booting Arch > Linux on you Pogo E02? pls post then entire dmesg > log. I need to know what u-boot you are running, > and which kernel you are running. Yes I am successfully (I think) bootinby huge - Debian
I was about to open a new thread but this looks so close to my situation I thought I should just reply here... I'm a near-noob (installed Arch&SAMBA on a Pogo-B01 over a year ago but have forgotten most of what I learned then) wanting to run Debian on my new Pogo-E02. I tried to follow a couple of different tutorials for Debian Squeeze & Wheezy on kirkwood devices, but (A) ran inby huge - Debian