theeleaper, Basically, you need to use partition label for booting, if there is more than one devices attached. See this: http://forum.doozan.com/read.php?3,19093by bodhi - uBoot
wzecke Wrote: ------------------------------------------------------- > Thanks for the reply. > > I did now the above steps on an utbuntu 14.04 x86 > system using kirkwood-pogo_e02.dtb. > Still the same problem as above. > It does not boot from usb. > Any further idea, may be my environment is buggy? If this is what actually in the env, then yes: machid=fffffffby bodhi - Debian
Joey, Look in /usr/share/icons. That's the location of your desktop icons. IIRC, you can also install xfce4-goodies to get the desktop themes. If that's youre looking for. Usually, after install themes, you'll have all kinds of nice icons to choose from. In xfce you can select a specific icon for a shortcut that are on your desktop, or a specific icon for drives/files thaby bodhi - Off-Topic
theeleaper, [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sdd1 rootdelay=30 rootfstype=ext3 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) The reason it is not booting is most likely the root device was set to /dev/sdd1. 1. If you have only this USB drive attached [ 13.684757] scsi 0:0:0:0: Direct-Access PNY USB 2.0 FD 1100 PQ: 0 ANSIby bodhi - uBoot
superelchi Wrote: ------------------------------------------------------- > Sorry. No luck at all. > > Called it with: > $ kwboottool/kwboot -t -B 115200 /dev/ttyUSB0 -b > uboot.2014.07-tld-3.nsa310.uart.kwb > > > Stops after sending the image: > . > . > 92 % > [................................................. > .....................] >by bodhi - Debian
pengu, > but it doesn't start Of course, it will not. I hope I'm making sense above :) QuoteThis u-boot image is for the NSA325, so I expected that it will not execute. We need to build new u-boot to run it properly on this SoC. Next week when I have some time I will attempt building one!by bodhi - Debian
wzecke Wrote: ------------------------------------------------------- > Hello, > > my kernel does not boot. See boot log and the > enviorment. Via boot/uEnv.txt is set the machid to > ffffffff > > any suggestion what to do?f > > Regards, It looks like you did not do this section: 4. Create uImage with embbeded DTB (If this is not first time installatiby bodhi - Debian
theliquid, >. But with Kernel 4.1 on my > Pogoplug I get error message like this: PAM > audit_log_acct_message() failed: Operation not > permitted. Please post the full error text in the log.by bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > I installed deluged on my plug cause transmission > daemon wouldn't even connect to peers. Thing is > free memory seems to be always full now. With > transmission daemon running, it was always around > 50% free of 250MB I think. Now it's around 245MB > always. There's just 4-5 MB free noby bodhi - Debian
pengu, > I tried kwboot on NSA320s again > first powered on the device, than it goes off > (watchdog?) Yes, it seems likely to be the watchdog. > right after powering on egain, kwboot is loading > the image but this does not complete several > times It did complete loading the image when you see Sometime if your network is noisy, it could effect the loadingby bodhi - Debian
maihoaomv, Sometime apt-get upgrade will replace your halt script with new version. Take a look at /etc/init.d/halt. Does it still have the echo line that turns off the green LED? similar to the following: if [ -d /sys/class/leds/status:green:health ]; then echo none > /sys/class/leds/status:green:health/trigger fiby bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > the power LED .. first I thought that there is > something wrong .. only the power LED lights up > ... one of the green LEDs lights up a little bit > .. and no serial output after a fiew seconds the > power LED goes off and on again .. then U-Boot is > up .. you meen this? > sometimes this happby bodhi - Debian
Hi Dannii, > My Pogo E02 now works after using this: > > fw_setenv ipaddr '192.168.0.15' > fw_setenv serverip '192.168.0.16' > fw_setenv preboot_nc 'setenv nc_ready 0; for > pingstat in 1 2 3 4 5; do; sleep 1; if run > if_netconsole; then setenv nc_ready 1; fi; done; > if test $nc_ready -eq 1; then run > start_netconsole; fi'by bodhi - uBoot
Hi restamp, > As I remember it, there was a problem with > 2014.07-tld-2 for Pogo E02 involving some missing > code that made the fsload command fail. Bodhi, > you fixed it in tld-3, which is what I have > running on my test Pogo E02 today. (This problem > didn't affect the boot of Debian loads, but did > prevent booting the original OS from the internal >by bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > I think after 5 .. sometimes after 10 seconds > no matter which usb port or hub /extension cable / > usb to ttl cable I use > > sometimes the power on isn't recognized and kwboot > still waits for power on The watchdog starts right away after you press the power button. So did you wait untilby bodhi - Debian
Dannii, > Only choice now is the usb to ttl. I think you definitely should have this. Sometime a problem is so subtle that it is the only way to figure out. So I would use serial console to get netconsole working and so that you can have netconsole for all plugs. > Does it matter what order I install the rescue, > kernel and debian rootfs (should I change to this > ratherby bodhi - uBoot
Dannii Wrote: ------------------------------------------------------- > Spent hours trying all different combinations > found in the forum and elsewhere... via mac, alarm > on the other pogo, no firewall on mac so it wasn't > that, when I install netcat via brew, it installed > the gnu one, still everything I try doesn't work. > Theres two things I can try... reby bodhi - uBoot
pengu, > with without -p .. same result ;-( > > > +xmodem: Protocol error Was the box reset by the watchdog at this point, or was it reset only at a moment later (30 second minus a few seconds)?by bodhi - Debian
Hi Dannii, I've just remember that you have 2 Pogo E02s :) You should try running netconsole one Pogo and connect to the other Pogo using native nc in the Debian rootfs. This is the easiest way to connect. After you've verified your setup is working, then worry about connecting the Mac to the Pogo. Usually, it's the netcat binary that is the problem, but sometime also firewby bodhi - uBoot
pengu, +xmodem: Protocol error Usually this is the synxtax error in the command. Try with -p option, and without -p option. See which one it will take.by bodhi - Debian
pengu, Try kwboot with the nsa325 small u-boot (note the correct command is without -p): http://forum.doozan.com/read.php?2,14351,17193#msg-17193 I expect to see the image loaded, but it won't execute (because it is of a different SoC).by bodhi - Debian
Dannii, > Working from mac. Ah :) on Mac/Ubuntu it's probably netcat bsd and it is problematic. You should use netcat traditional, check which one you are using. And try either: nc -lup 6666 192.168.0.15 6666 or nc -kup 6666 192.168.0.15 6666by bodhi - uBoot
Cool! Netconsole envs: ipaddr=192.168.0.xx serverip=192.168.0.xx These should be real IP (eg. 192.168.0.100, 192.168.0.200,....). So if the static IP of the plug is 192.168.0.100, and the static IP of the server is 192.168.0.200, then ipaddr=192.168.0.100 serverip=192.168.0.200 And from 192.168.0.200, try: nc -lup 6666 192.168.0.100 6666by bodhi - uBoot
Dannii, > anyone point me to 2014.07-tld-3 for Pogo E02, > please? Use 2014.07-tld-2 for Pogo E02. > My E02 is up.... but ssh and every other port is > closed. > > Starting Nmap 6.47 ( http://nmap.org ) at > 2015-07-25 02:44 BST > Nmap scan report for 192.168.0.xx > Host is up (0.00049s latency). > PORT STATE SERVICE > 22/tcp closed ssh &gby bodhi - uBoot
pengu. > working usb is the better solution Did you do anything differently on the NSA310S?by bodhi - Debian
Hi pengu, The NAND bad blocks are OK since they are managed by the filesystem on top in the case of stock OS booting. Your env for USB booting could be improved so that it will short circuit the USB booting sequence if uImage is not found (note that the below is a quick fix, it should be a little more refined): setenv usb_boot 'mw 0x800000 0 1; if run usb_load_uimage; then run usb_lby bodhi - Debian
pengu, 1. Have you tried the port closest to the Ethernet port? When you see this, it is stock u-boot limitation with a very short time out when it scans for USB drives (in the new u-boot, I alleviated this by adding the env usb_ready_retry). I've seen this a few times on the NSA325v2, the work around is instead of one "usb start" command, add multiple "usb restart"by bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > Seems mouth watering, but with linux I think I > would go with that old saying -If it's not broke, > don't mend or something like that. I'll use this > plug as is for a month or two and then decide if > its worth the risk. Thanks a lot for your help > Bodhi. :) You're welcome! Iby bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > Sorry for not replying till now, had been away. > Should I upgrade the uboot or is this old uboot > okay to use for 24 hrs usage? Nothing is wrong with this u-boot. It's just older and does not have new features. It's great for your purpose right now. You can take a look at the description of the nby bodhi - Debian
FYI, netconsole seems to be broken in the latest NSA325 and NSA320 u-boot . I am troubleshooting this problem, and will report back!by bodhi - uBoot