Buck, Dowload the 3.17 kernel tarbal (same thread). Extract the headers from it. Copy it to rootfs /boot and install it from there while system is running. Sorry I forgot, basic rootfs doesnot have headers file on it! I make a note to do that.by bodhi - Debian
BuckNaked Wrote: ------------------------------------------------------- > The linux headers don't appear to be present and > don't appear to be available. Results: > > > root@debian:/etc/apt# cd /boot > root@debian:/boot# > root@debian:/boot# apt-get install > linux-headers-3.17.0-kirkwood-tld-1 > Reading package lists... Done > Building depeby bodhi - Debian
I've noticed you are not at /boot. Have you tried to install linux headers first? cd /boot apt-get install linux-headers-3.17.0-kirkwood-tld-1by bodhi - Debian
BuckNaked, Try cleaning up your dpkg and then execute module-assistant again: apt-get clean dpkg --clear-avail rm /var/lib/apt/lists/* --force dpkg --configure -aby bodhi - Debian
codier, > I followed your instruction but I couldn't boot > into rescue again. Did you have rescue system running before? the u-boot envs setup for rescue system needs to the same as installed by Jeff's script. If you have flashed the new default envs, then the rescue system setup were erased. - interrupt netconsle and get the envs listing: printenv - If you did reby bodhi - uBoot
Waynosan, > As suspected, something is messed up with the > network setup. Not sure what I need to do next to > proceed.... Excellent! and you're right. This systemd problem should be solvable, but Arch rootfs specific. I'd suggest you post this boot log at Arch site, someone there will know what needs to be done.by bodhi - uBoot
Waynosan, QuoteWhat I failed to do was sync after running the tar command so I'm not certain if all the files were written onto the USB drive. This could be the only reason you had problem booting with Arch rootfs. QuoteUnfortunately I didn't keep a log of the installation but I followed the process here: http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray If you raby bodhi - uBoot
bonk1990, Sounds like you are trying to run the new rootfs with stock u-boot? Pls post in this NSA325 thread: http://forum.doozan.com/read.php?2,14351 It's best that someone who runs the NSA325 with stock u-boot and new rootfs would post a listing of their envs, and you can follow that.by bodhi - Debian
@Peacemaker, > @bodhi here is as well my problem, I've no idea > why Uboot doesn't load up the harddrives. If I > choose a newer Uboot (this is the vendors Uboot). > I's not working anything (as the original Stage1 > can't load fat partition or ext4) or only one disk > with only 128mb ram or these sort of thinks As I mentioned, I've lost trackby bodhi - Debian
Waynosan, > With just that USB drive in the pogoplug the front > LED turned green but still no network activity... This is a good sign. It means your u-boot is not corrupted. The kernel has been loaded and it tried to mount rootfs. The problem remained is with the mounting rootfs. When you create Arch rootfs, make sure that: - log in to Linux Mint as root user. During the preparatby bodhi - uBoot
LeggoMyEggo, > I have > my eye on a recycled Intel 5100 300N adapter which > can be picked up for less than $10 shipped. Think > this has support in your 3.17? Not sure if it is (I don't have access to my build environment, ATM).by bodhi - Debian
LeggoMyEggo, > Am I correct that the built in Ralink wireless > adapter is not supported yet in 3.17? Most likely correct. I have not verified this, but others have reported the same thing about stock wifi. > Would it be easier to just get another cheap mini > pci-e adapter that has mainline support? I have > my eye on a recycled Intel 5100 300N adapter which >by bodhi - Debian
Probably a wrong step taken somewhere during 3.17 rootfs creation. With only SD card (with 3.17 kernel) plugged in, power up, interrupt console at count down, excute commands: printenv mmc rescan mmc part Pls post the ouput here!by bodhi - Debian
LeggoMyEggo, Cool! I think the best approach in solving booting problem: most of the time the problem is quite simple, when in doubt, repeat the instruction exactly the same way it was written, for sanity, like you did.by bodhi - Debian
A_Mando Wrote: ------------------------------------------------------- > thrown solid days into this; thought it's worth > asking. > > My Pogo Plug Mobile (single USB) came with a third > party image which successfully replaced through > uart and tftp, etc to have: > > - the latest UBoot and env. > - > Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tarby bodhi - Debian
enki, Yes, you can install new u-boot and then boot with the new rootfs. Please make sure to follow the instruction exactly in the u-boot thread (beware of bad blocks... etc). And keep the entire log of the installtion. If you'd like, post the log here before rebooting with new rootfs.by bodhi - Debian
http://forum.doozan.com/read.php?3,16789,16789#msg-16789by bodhi - uBoot
enki, Jeff has stopped maintaining kirkwood.debian-wheezy.sh. It no longer works reliably. Just use my latest rootfs (3.16 or 3.17) from: http://forum.doozan.com/read.php?2,12096 Since you ran this wheezy script, you have updated u-boot to 2011.x, and it will work fine with the latest rootfs.by bodhi - Debian
@Don, Remove the RAM option for busybox syslog before booting might help: http://forum.doozan.com/read.php?2,18606,18632#msg-18632 Also, even better if you remove systemd from jessie all together.by bodhi - Debian
This basic rootfs is a bare bone system, which serves 2 purposes: - For beginners to learn Linux by installing whatever packages that are needed to make it a full feature OS. Simply "apt-get install" whatever you need. - For advance users, who don't like to have to remove stuff that they don't need (it's a pristine, newly created system that has not been used before).by bodhi - Debian
@WarheadsSE, http://forum.doozan.com/read.php?2,14351,19371#msg-19371by bodhi - uBoot
Adam, Don't try to overthink it. Simply do it in this order: 1. Create new rootfs on new usb stick 2. Update u-boot while in stock Pogo OS 3. Boot with new rootfs usbby bodhi - Debian
@Don, Use logread command to read memory log.by bodhi - Debian
shivahoj, > So if there is no way to return to the factory > delivered software(and its updates), i would > strongly advise against all other > software installations. In my observation, most users looking for latest u-boot and kernel are really not interested in running stock FW. I would say the only times we run stock are a few initial startups to install new SW. That'by bodhi - Debian
balbes150, If only Leggo and you have seen this, but others have not, then it's not related to CONFIG_USB_OHCI_HCD=m CONFIG_USB_UHCI_HCD=mby bodhi - Debian
@ WaheadsSE, I could merge what I have on NSA320/325 into the u-boot-kirkwood (2014.07 branch). And then you can modify it as you see appropriate for mainline, and then PR?by bodhi - Debian
LeggoMyEggo, Most likely you need to log in as root on another Linux box, and extract rootfs to a single Ext3 partition USB drive. And the log can be put in code tag: U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) Boot device: NAND Attempting to set PLLA to 800 MHz ... plla_ctrl0 : 0000030a plla_ctrl1 : 00400000 plla_ctrl2 : 007f0068 plla_ctrl3 : 00000193 PLLA Set U-Boby bodhi - Debian
bonk1990 Wrote: ------------------------------------------------------- > Hey, > i just bought NSA325v2 and I'm new here. > > Please correct me if I'm wrong. > > To install Debian on my device I should: > 1) upgrade u-boot - not necessarily, but have to > if i want FDT? For NSA325, your best course is to install new u-boot. Even though it is not absby bodhi - Debian
nekitip, All your questions/problem are really not related to this kernel / rootfs. They are rather general issues you would encounter in booting u-boot and kernel. I think the topic should be in a new thread. Quotequestion: is it possible to install system on HDD (or some fast usb external disk), and then, when system is done - just copy system (select all the files on ext2) to standard, sby bodhi - Debian
LeggoMyEggo, > Put 3.17 on a flash drive and I am getting much > further however I don't get a Debian prompt. This > is where I get up to now: > > > 2.845634] usb 1-1.2: SerialNumber: > AE7FHE0700000917 > [ 2.853209] usb-storage 1-1.2:1.0: USB Mass > Storage device detected > [ 2.860052] scsi host1: usb-storage 1-1.2:1.0 > [ 2.880by bodhi - Debian