edinger, > I installed your rootfs > Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > on another usb stick and with that I was able to > set ethaddr. Could it be that my Debian wheezy > installation is somehow too old? No. As I said, your DTB is too old: root@nas:~# ls -l /boot/dts/kirkwood-dockstar* -rw-r--r-- 1 root root 10180 Feb 6 2015 /boot/dts/kirkwood-doby bodhi - uBoot
Boot into Debian and fw_setenv bootcmd_exec 'if run load_uimage; then; 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_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi' Reboot. Interrupt serial console and removeby bodhi - Rescue System
edinger, > Ok, I will proceed with this and keep you > informed. > Here > the description differs. There is no 4a or 4b, > just4 and I skipped it. > > 4. Create uImage with embedded DTB for booting > with older u-boots (2012 or earlier). Skip this > step if you have installed the latest U-Boot for > Kirkwood (or are installing this u-boot at the > saby bodhi - uBoot
Yes. Your u-boot envs need some further setup. Let me write a new env to do that shortly.by bodhi - Rescue System
edinger Wrote: ------------------------------------------------------- > I unpacked the dts files, build uImage with the > following commands (as described in Step 4) again > and rebooted. > Same problem. > Should I build it without dts file? It was unclear > how, because when I skip step 4 I have no uImage > file. This indicated that you have not installed the kerby bodhi - uBoot
Quoteif i am on LEDE i cant do a reboot (soft reboot) - cold reboot unplug - plug again works perfect. What you do get when you do a reboot from LEDE? please post the entire serial console log for this case.by bodhi - Rescue System
jgkempen Wrote: ------------------------------------------------------- > Thanks for your help. I got it working again Cool!by bodhi - Debian
edinger, You're running the latest kernel 4.14.1, but you did not install the latest DTB in step 2 during kernel installation: Quote2. Extract the kernel and the DTB files in the archive: cd /boot tar -xjf linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2 tar -xf linux-dtb-4.14.1-kirkwood-tld-1.tarby bodhi - uBoot
edinger Wrote: ------------------------------------------------------- > reboot worked, but i get same error when setting > ethaddr after booting into debian. > I also tried with /boot/uEnv.txt. No effect. > Then with update to newest kernel: > > root@nas:~# uname -a > Linux nas 4.14.1-kirkwood-tld-1 #1 PREEMPT Wed Nov > 22 23:38:14 PST 2017 armv5tel GNU/Linuxby bodhi - uBoot
jgkempen Wrote: ------------------------------------------------------- > I am pretty sure the problems are unrelated to my > samba installation, but for the drive I was using > for samba had its partitions resized using gparted > on Lubuntu on an X86 machine. That drive was > formatted in NTFS as I needed to maintain the > ability to plug it into a windows machine ifby bodhi - Debian
Seems like your serial pins were probably damaged from the wrong connection before. Can you use a magnifier and look at the pinouts to see if it was shorted/blacken... anything that is not normal color?by bodhi - Debian
edinger Wrote: ------------------------------------------------------- > I have a dockstar and had an older version of your > uboot - I assume from 2011. > I installed this version. > All steps worked including the writing of the > environment except setting ethaddr > root@nas:~/tmp# fw_setenv ethaddr > '00:10:75:1A:DD:17' > Can't overwrite "etby bodhi - uBoot
ljm90 > The device itself doesn't show that it's powered > on except that the ethernet port is lit up, and > that the HDD I have setup is lit for a few minutes > and then turns off. The main LED does nothing when > I boot it up without the serial console. How were the serial console wires connected? TXD-TXD, RXD-RXD, GND-GND ?by bodhi - Debian
metric, Power up, interrupt serial console and enter the rescue envs, and then printenv boot Post the entire serial console log here.by bodhi - Debian
Olivier Wrote: ------------------------------------------------------- > Hi. > Can we get usbip support as a module for the next > kernel release if it ever happens please? > From the kernel config file, it is unset, meaning > it is probably not available. > I am too lazy to recompile on the dockstar > itself. > > Thanks for the great work on the rootfs/kerneby bodhi - Debian
alphaprime Wrote: ------------------------------------------------------- > Hi Bodhi, > > Now my pogo boot with U-boot & Debian so far > running normally on MMC drive. > Thank you for your support > > I'll play a while with this, I'll ask again if I > don't know how to solve it > I'm sorry if I disturb you > > Thank youby bodhi - uBoot
maldridge Wrote: ------------------------------------------------------- > Cool, so I have now functioning u-boot on there > and all seems well again. To recap, here's what I > noted through this process: > > One of the scripts dd's some things to ${disk}1 > which corrupts the partition and makes it > unbootable. > > The default env vars in the shby bodhi - uBoot
ljm90 Wrote: ------------------------------------------------------- > bodhi, > > I get a whole lot of failed packets. Pinging the > device doesn't do anything, it isn't appearing in > my router, and I can't ssh into it, > unsurprisingly. > > The device itself doesn't show that it's powered > on except that the ethernet port is litby bodhi - Debian
maldridge Wrote: ------------------------------------------------------- > Holy sysvinit batman, its booted! > > I'll go ahead and try to do a firmware reflash > from here and see if I can get back to a state I > can boot from the NAND. Super :)by bodhi - uBoot
Damn :) another rampant spam flood! I've notified Jeff.by bodhi - Off-Topic
maldridge, > I think that something is wrong with the disk > layout, but I may be very much wrong there. I'm > not particularly familiar with systemd so I'm not > sure the best way to tell it exec in after > manually mounting things: Cool! No, I am not using systemd in any of the released rootfs. It's sysvinit. And we just need to tell the kernel to moby bodhi - uBoot
Interrupt serial console and setenv dt_sata_boot 'ext2load ide 0:1 $uimage_addr /boot/uImage; ext2load ide 0:1 $uinitrd_addr /boot/uInitrd; ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb ; run dt_bootm' bootby bodhi - uBoot
maldridge Wrote: ------------------------------------------------------- > So this drive actually has the new filesystem on > it. It looks like the u-boot environment is hard > coded to select the obsolete kernel: > > > dt_sata_boot=ext2load ide 0:1 $uimage_addr > /boot/uImage_2.6.31.14_OX820_1.2_shv.Pro; bootm > $uimage_addr > > > I altered the varby bodhi - uBoot
alphaprime, Quote> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 > -0700) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > DRAM: 128 MiB > WARNING: Caches not enabled > NAND: 128 MiB > MMC: MVEBU_MMC: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > Net: egiga0 > Hit anyby bodhi - uBoot
ljm90, Everything was checked out OK! I can't see why it would not boot without serial console. Try this: 1 Unplug serial console. 2. On another linux box ping 192.168.1.37 3. Power up the Pog E02 and watch the ping responses for 1 to 5 minutes. If you see it consistently output successful responses for 30 seconds, then you know it has booted.Terminate the ping commby bodhi - Debian
Hey all :) Be it may. Whatever we feel like posting is great. I was just trying to steer it back to Net Neutrality because it is quite an interesting subject. But the OP decides where the thread goes :)by bodhi - Off-Topic
jgkempen, > I shut down the pogo plug and used another linux > box to change the partition on the samba drive. What type of Linux box? x86 or ARM? what OS? .... do you have the log of how you change the partition? > > I plug everything back into the pogo plug an > powered on. Seemed to take a long time to boot, > but eventually it connected to the next work andby bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,45239by bodhi - Debian
toddcscar, I am not sure what is your question? please post the entire serial bootlog (if you have it), or the entire dmesg output. And states what help you need, or what you want to do.by bodhi - uBoot
alphaprime, With the Pogo V4, it does not matter if you have messed up mtd0 or not. You can recover with serial console using kwboot. Download the Pogo V4 u-boot from the installation thread: https://forum.doozan.com/read.php?3,12381 Quoteuboot.2017.07-tld-1.pogo_v4.bodhi.tar md5 e2c2b4927dcd8189f0c97dd81b72ad7e sha256 18f856d2106aabe6029331358fb06f053ea9257ad896e2d382f4f096f9by bodhi - uBoot