> I wonder what the motive is behind it - there's > nothing here that steps on anyone's toes. It is not this site particularly at all. The forum is hosted by commercial provider servers in Atlanta. Their servers have been under DDoS attack most of Saturday. Perhaps someone is practicing for their real DDoS attack somewhere else later.by bodhi - Off-Topic
Damn these eBay vendors :) just had "another one bite the dust"! May be I bought the one that Gravelrash returned? :)). Got the box, this time I did not even open it yet (I want to observe the LEDs ligh behavior), just plugged in the power supply, turned on, and .... nothing, no power came into the board, completely dead. Please either PM me or post the link to eBay that you bought tby bodhi - Debian
> Will send a PR to LEDE soon with this fix and if > they don't accept it I'm going to find and > slaughter all their kittens. > :))by bodhi - uBoot
There was a massive DDoS attack on the server provider host in Atlanta.by bodhi - Off-Topic
I'd like to point out this fact for general consumption: FIT image and uImage are just the same kernel files inside being packaged a different way. The main advantage with FIT is you can sign your image, so it is more secure. But when it comes down to maintainability for us is no more or less works. - So there are drawback when you're hacking such as: less convenient when you'reby bodhi - uBoot
Quotebodhi Wrote: > You can now proceed to install u-boot if you feel > like doing. But if the rootfs is RO then you need > to copy u-boot image and uboot env image to the > USB drive first, offline. Chuck, install new u-boot for real. No need for any temporary measure.by bodhi - uBoot
Joey, > @ bodhi here's Test 1 MON > > U-Boot 2016.05-tld-2.6 (Sep 02 2016 - 01:00:09 > -0700) > Cisco ON100_K9 > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNING: Caches not enabled > NAND: 512 MiB > MMC: kwsdio: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serialby bodhi - Debian
jlovell, This is the problem: QuoteNSA-jaynas01-console-boot-early-root-md-with-broken-eth.txt (18.4 KB) [ 0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instructionby bodhi - Debian
> That's plain wrong, they still support many > devices with bootloaders that can only boot > uImage, and their toolchain still has the code and > tools to make uImages. :) that did not seem to register when I told habibie this.by bodhi - uBoot
mike, > loading envs from mmc 0 ... > 98 bytes read in 1089 ms (0 Bytes/s) > > no IDE devices available > importing envs ... > ## Info: input data size = 284 = 0x11C > ** Bad device usb 0 ** > ** Bad device usb 0 ** > Wrong Image Format for bootm command > ERROR: can't get kernel image! > resetting ... Looks like you have installed u-boot inby bodhi - uBoot
Please try this 2.6 version. I've mistyped some numbers in the code last time. Test 1: with ethernet cable connected to MON port Boot with kwboot, interrupt serial console version setenv ipaddr <IP address of the ON100> setenv ethaddr <the MAC address of the MON port> ping <your router IP> Test 2: with ethernet cable connected to LAN port Boot with kwboot,by bodhi - Debian
Was rootfs still mounted as RO? if it was, shutdown and bring this USB drive to your Ubuntu and check for error (if it was assigned sdb1) umount /media/sdb1 e2fsck /dev/sdb1 Also, pls attach serial console log while Linux is booting (entire serial console log is better). dmesg only shows the kernel messages, not everything. IOW, hacking Linux, there are things you can only see in serial cby bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > I've been sick for the last week, so just now > getting caught up with forum posts. I'll try the > latest version on my ON100 tomorrow night. > > Ray Glad you feel better! we need you to resume the party here :)by bodhi - Debian
> Remove the reset command from the end of your > dt_bootcmd_usb and it should proceed to run the > bootcmd_stock. > > Ray Right! there should be only one reset at the end of bootcmd.by bodhi - uBoot
Try this: Stop the booting process in serial console or netconsole: setenv bootcmd 'run bootcmd_uenv; if run dt_bootcmd_usb; then echo "booting Debian..."; else echo "booting stock..."; run bootcmd_stock; fi; reset' boot If this works, boot with USB or HDD into Debian, and set it for real: fw_setenv bootcmd 'run bootcmd_uenv; if run dt_bootcmd_uby bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > I can somewhat understand a BIOS for allocating > video memory (such as the ThinClient I'm typing > on), where 128MB or 256MB can be absolutely spoken > for from the RAM allocation for video use, but as > for little Android boxes, I'm not sure about > anything when there doesnby bodhi - Off-Topic
Mr Dini Wrote: ------------------------------------------------------- > Thanks a lot! I'm in finish! :) The machine booted > up successfuly and it is working fast and stable. > > Awesome! Cool!by bodhi - Debian
Mike231 Wrote: ------------------------------------------------------- > Hello, > First of all, I would like to thank you for your > great contribution to pogoplug support. > I need your help. > My pogoplug is unfortunately bricked. > I can connect to my pogoplug mobile only via > serial port: ./kwboot -t -B 115200 > /dev/ttyUSB0 -b > uboot.2016.05-tld-1.pogo_by bodhi - uBoot
Chuck99 Wrote: ------------------------------------------------------- > Did kwboot as usual. Stop at PPV4> prompt. Did > copy paste this: setenv set_bootargs_usb 'setenv > bootargs console=$console root=$usb_root > rootdelay=$rootdelay rootfstype=ext3 $mtdparts' > boot > > no errors. also did a saveenv. Since uboot was > running in RAM I suppose tby bodhi - uBoot
red9r Wrote: ------------------------------------------------------- > Hmmm... It seems that they removed the header > shown in the picture of the linked thread. I guess > I'll have to break out the old soldering iron. Cool. So I forgot that damacc did post the serial pinouts!by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > > Also tried to change memory address for loading > > and starting, same results. > > > > Have you tried the standard memory address? > > > load_initrd_addr=0x1100000 > load_uimage_addr=0x800000 > > > This is way too low > > > NSA310> bootz 0x8000by bodhi - uBoot
I would not trust this uImage. QuoteBut it does not end here. I tried also with other uImages+appended-dtb generated by LEDE build system. NSA310> fatload usb 0 0x8000 lede-kirkwood-dockstar-uimage reading lede-kirkwood-dockstar-uimage 1871076 bytes read in 89 ms (20 MiB/s) NSA310> bootm 0x8000 Wrong Image Format for bootm command Error occured, error code = 112 ERROR: can'by bodhi - uBoot
> Also tried to change memory address for loading > and starting, same results. > Have you tried the standard memory address? load_initrd_addr=0x1100000 load_uimage_addr=0x800000 This is way too low NSA310> bootz 0x8000by bodhi - uBoot
Ah. I see. 1. Here is the reason you can't write to the rootfs: the rootfs was mounted as RO: root@debian:/boot# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=14202,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,modby bodhi - uBoot
> I have a serial console but due to the lack of > identifiable markings on the board, I haven't > attempted to hook anything up yet. Search at OpenWrt or Nas-Central for serial pinouts. Or look at this thread: http://forum.doozan.com/read.php?2,22623,22623#msg-22623. You might want to PM damacc asking for this info, hope he will come back and post in the forum.by bodhi - Debian
Mr Dini, > Marvell>> ext2load usb 0:1 0xf00000 /boot/uInitrd > Wrong addres, should be ext2load usb 0:1 0x1100000 /boot/uInitrd If you like, interrupt serial console after it booted and get the liting of envs and post here and I'll take a look. The rootfs label needs to be in the bootargs. printenv Or you can searchby bodhi - Debian
Chuck99 Wrote: ------------------------------------------------------- > running sudo gtkterm with Ubuntu trying to cp -a > uImage.orig uImage and cp -a > zImage-4.4.0-kirkwood-tld-1 zImage.fdt it says > "read-only file system". tried chown and chmod. > what now? Boot into Debian on the Pogo V4, and do this in the live system. What you did was on Ubuntu itseby bodhi - uBoot
Joey, > Ahh sorry man, ow. I was so worried about a wire > whacking everything (one pin is for sure loose) I > edited like I would almost any document. That one > I can't recover. Nah. You've helped a lot. I know MMC works now thanks to your test. > I can get a Sandisk Ultra 16 GB USB 3 stick for > $2. My E02 sure loves USB3 sticks even if they're &gby bodhi - Debian
kwboot serial console log starts with : U-Boot 2016.05-tld-2.5 (.....) Cisco ON100_K9 SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 512 MiB MMC: kwsdio: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0, egiga1 That's OK Joey! I will receive my box soon, hopefully. I will continueby bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Test 1 - MON then LAN > > > U-Boot 2016.05-tld-2.5 (Aug 28 2016 - 22:15:30 > -0700) > Cisco ON100_K9 > gcc (Debian 4.9.2-10) 4.9.2 > GNU ld (GNU Binutils for Debian) 2.25 > ON100_K9> setenv ipaddr 192.168.178.111 > ON100_K9> setenv ethaddr 64:00:F1:20:FF:B7 > ON100by bodhi - Debian