What do you use for netconsole server? another Linux box or Windows/Mac? does the server "see" the Pogo E02 (can ping it). And once you booted into Arch on Pogo E02, can you ping the netconsole server box?by bodhi - uBoot
hachigo Wrote: ------------------------------------------------------- > I've made it all the way through the guide. I > think It has installed, I'm not entirely sure. > > Netconsole setup isn't working, I followed the > directions on Jeff's guide. I'm booting directly > into the Archlinux usb. The pogoplug just blinks > orange without the USby bodhi - uBoot
cristiangutie, Sometime a mirror is offline. You could try again, or check to see which Debian mirror is close to you and use that: http://www.debian.org/mirror/list You can change it in your /etc/apt/sources.list. This is the content of the source list in one of my plugs. deb http://ftp.us.debian.org/debian wheezy main deb http://security.debian.org/ wheezy/updates main contrib non-fby bodhi - Debian
hachigo Wrote: ------------------------------------------------------- > Hi, > > I was reading the guide on how to update the uBoot > for Pogoplug E02. And I've detected bad block. > > 1. What should I do? > 2. Also is it safe to upgrade the uBoot from > Archlinux on usb or do I need to unplug all usbs? > > > > # dmesg | grep -i 'bby bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > Thanks bodhi, > The big_writes option will improved the read speed > too, or only write speed? Should improve both.by bodhi - Debian
addy75, You are running my Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs. You can ignore the bootROM detection. Marvell>> md ff00003c It does not really tell. We've verified that the NSA325 has UART booting. So don't bother with this step. And I see you have tried UART booting above: ./kwboot -t -B 115200 /dev/ttyUSB0 -b ./uboot.2013.10-tld-1.nsa325.uartby bodhi - Debian
@WarheadsSE, Right, it's been so long I forgot what the CE mtd definition looks like! @Newhope, You have not told us what the original nanddump command used to dump NAND, so I can't say what flash_erase and nandwrite commands should be.by bodhi - uBoot
@archon, You should wait for the formal release. But if you want to install it now, then only 2 posts are relevant: - The 1st post of this thread - This post: http://forum.doozan.com/read.php?3,12381,17420#msg-17420 Do you have difficulty understand all the steps in the first post?by bodhi - uBoot
@addy75, So can you boot into Debian with either USB stick or the SSD? which rootfs do you use? uname -a If you can, then keep it that way, you can install new u-boot: http://forum.doozan.com/read.php?3,12381,17420#msg-17420 I have not formally released this new u-boot. So if you have installed u-boot before for another Kirkwood box as described in the instruction in the above link, tby bodhi - Debian
DonCharisma Wrote: ------------------------------------------------------- > I'm getting this in my dmesg : > > > [ 25.630061] EXT2-fs (sda1): warning: mounting > ext3 filesystem as ext2 > > > > Anyone know how to fix it ? I have searched, quite > a lot of Google, and in the forum, didn't find an > answer, yet .. > > It's mby bodhi - Debian
ebbix, > Concerning SPI flash: as far as I read some > Netgear NAS actually has SPI flash onboard. > However, it is used to store its USB 3.0 > controller configuration and is not connected to > the system SPI bus at all. Maybe that's what > happened on early development boards? Do you have > a working stock kernel? If so, you could try > writing some randomby bodhi - uBoot
Almaz Wrote: ------------------------------------------------------- > I don't have setenv option. I can only use > fw_setenv if it makes any difference. > > U-Boot 2011.12 (Feb 20 2012 - 21:21:59) > Pogoplug E02U-Boot test -e won't work in this u-boot version (too old).by bodhi - Debian
Almaz, I gave it a second thought! Actually you don't have to wait until new u-boot release to do this. Do you have netconsole or serial console? if you do, try: 1. In Debian, cd /boot touch boot.txt 2. Reboot, interrupt serial/net console, and execute > setenv test_boot_drive 'if test -e usb 0:1 /boot/boot.txt; then echo Found boot.txt; fi' > run test_booby bodhi - Debian
@Neal, > Specifically I was referring to the method > outlined here: > > http://forum.doozan.com/read.php?3,210,214 > > But that thread is 4 years old and I was just > wondering if it was possible to do something like > that with a newer uboot. > You can try. As I mentioned, it might work due to the way stock Pogo E02 u-boot was built. But chainloadingby bodhi - uBoot
Almaz, > Problem solved by switching > > from > fw_setenv usb_scan_list 1 2 3 4 > > to > fw_setenv usb_scan_list 4 3 2 1 Not a sure thing. It might work for current USB drives and the way you plug them in. As soon as you change the order or brand of USB drives, you might find it get out of wack again :) I will release the next version of u-boot images thatby bodhi - Debian
@Almaz, If both USB drives have rootfs, then u-boot env will need more than rootfs label change. uImage detection also needed to change.by bodhi - Debian
twinclouds Wrote: ------------------------------------------------------- > I guess that's the problem. > Does RPi uses the same processor as Dockstar/Pogo > Mobile? No, RPI is Broadcom. But I think you should attempt to run make_drv. I hope it will prompt you for platform type, then you'll know for sure if it's support or not. Other thought: did you check Reaby bodhi - Debian
Twinclouds, I did not recognize any of the ARM configs in this file that can be used for Marvell Kirkwood.by bodhi - Debian
Twinclouds, I thought the Quick starts show a way to capture only this driver code. See the bold parts at the end. Did you run make_drv script? Section 5 in Quick Start: Integrating Driver Source into Linux Kernel Tree QuoteThis paragraph is for integrating our driver source into Linux kernel tree and building system. If you have no need to do this, simply skip this paragraph. For compounby bodhi - Debian
Your rootfs udev net rules are Ok. That's how they are after modification. The behavior pointed to a copied rootfs, hence my suggestion. You could try to create fresh rootfs from my thread, boot with it. If it works normally, then you know something is wrong in your current rootfs.by bodhi - Debian
Hi twinclouds, I've looked at the driver zip file. In this document: "Quick_Start_Guide_for_Driver_Compilation_and_Installation.pdf". Step 5 shows you how to integrate the driver source into the kernel source tree. This is where you can extract the source for this RTL-8192EU driver. The extracted source will be captured in a folder. If you could do this and post or send me thby bodhi - Debian
@ebbix, Thanks, the DTS works great! I've removed SPI definition, recompiled the DTB and ran it without problem. The only minor thing is the 14 non-existent pinctrl that showed up in dmesg [ 1.019198] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 36 [ 1.019220] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 37 [ 1.019236] kirkwood-pinctrl fby bodhi - uBoot
restamp, > I suspect that the bug > is in nc, but I have not verified this. Concur. It is very likely a bug. I don't particularly like u-boot netconsole driver code. Even though I did patch (i.e. kludge) it to make it work when I consistently lost the 2nd character in the command. The polling logic in the driver is prone to behave badly (i.e. race condition does exist in there).by bodhi - uBoot
It's OK. For sanity, list the envs with fw_printev. If there is no error, go ahead and reboot.by bodhi - uBoot
If you have cloned this rootfs from an existing rootfs which has been running on another box, then udev rules need adjustment (the numbers in file name might be different depending on Linux installation). - Change the white list in this file (Eth*, Wlan*) to remove eth* and wlan* /lib/udev/rules.d/75-persistent-net-generator.rules KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcby bodhi - Debian
Try setenv usb_init 'usb start; setenv usb_root LABEL=rootfs'by bodhi - uBoot
Use the rootfs label to ensure the rootfs is mounted correctly: 1. On a different Linux box, mount the USB rootfs, and set the label of the USB drive to "rootfs". Assuming the USB drive is assigned sda1: # tune2fs -L rootfs /dev/sda1 2. Plug back the USB drive to the NSA325, power up, stop serial console and, set the environment variable usb_init: setenv usb_init "rby bodhi - uBoot
Use the label for rootfs: 1. Set the label of the USB drive to "rootfs" (adjust the name to your liking). Assuming the USB drive is assigned sda1: # tune2fs -L rootfs /dev/sda1 2. Set the booting environment variable usb_init: # fw_setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs" And you root is usb_set_bootargs=setenv bootargs console=$console root=$usby bodhi - uBoot
pepesz, You need to remove machid. It has to match the NSA325 or not defined at all. setenv machid Instruction on 1st page: QuoteAlso note that only some boxes need machid, some don't (so the command fw_setenv machid below clears them).by bodhi - uBoot
pepesz, > the boot images are in the / on first partition, > not in the /boot. Ah! no wonder u-boot can't find it. This is not a very good placement of the boot files. Even though you have 2 separate partitions, the boot partition should have the same directory structure as the rootfs. So I would create a boot directory and move all these files in to that. Of course you can pby bodhi - uBoot