@Don, I've been using the Pogos cluster mostly as compile farm for home use. As far as other distributed processing researches using these, I'm afraid that I can't discuss.by bodhi - Debian
Mark, Very good serial console instruction by varkey (it's for a GoFlex Net, but should give you an idea in general for how to unbrick these pogoplugs). You might have to do some soldering if your plug does not have a header. http://varkey.in/seagate-goflex-net-serial-connection/ The link you posted above is very good, too. Which plug do you have? If you decide to purchase and cby bodhi - Debian
@restamp, >Since it broke the uBoot, I'm presuming that it > somehow altered the uBoot bootcmd environment > variable). Yes, I think there must have been other envs that were set incorrectly this way. We can't tell for sure because Mark did not list them. The wrong command above would create a variable "bootcmd=usb" and assigned "start;" to it. So aby bodhi - Debian
Mark, It should be /usr/sbin/fw_setenv bootcmd 'usb start; usb stop; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset'by bodhi - Debian
habibie, > > I plan to create an env image that default to > > booting FDT kernel (like the one available > right > > now for non-FDT). > > > Do you have an ETA on that? No I don't have an ETA. I'm really busy with year-end stuff so not sure when I can do this. In the mean time, you can flash the existing default envs, and then you set up FDT booby bodhi - uBoot
enavarrocu, I don't have the NSA320. Perhaps other who has can post the orginal envs. If you connect serial console, it'll be easier to see the problem.by bodhi - Debian
Buttzy, Do you have a boot log? Yes, this is the NSA320 u-boot. It has been tested by gaogao: http://forum.doozan.com/read.php?3,12381,16787#msg-16787by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > Bodhi, > > Is there any works/plans in progress update uboot > to support envs for FDT kernel? I plan to create an env image that default to booting FDT kernel (like the one available right now for non-FDT).by bodhi - uBoot
@Neptune, One more thing! I've noticed that your USB drive is a little slow coming up. It did not affect the boot process, though. However, if you'd like to be a little more sure about booting, add this env to your u-boot env (15 is number of seconds u-boot takes to detect the drive before timing out): fw_setenv usb_ready_retry 15 My u-boot build has an extra timeout period fby bodhi - Rescue System
Neptune Wrote: ------------------------------------------------------- > I was not able to capture the whole log earlier. > Anyways, here is the complete log > > http://pastebin.com/GEaVNyf4 Everything looks great!by bodhi - Rescue System
enavarrocu Wrote: ------------------------------------------------------- > Hello guys, > > I'm trying to get back my NSA320 to it original > firmware because I want to sell it. I don't > remember exactly which configuration I made > because was a while ago. I get back the original > kernel from upgrade firmware file but it get > frozen after: > &by bodhi - Debian
habibie, > is it still necessary to perform both steps #6 and > #7 before step B (Flashing default u-boot envs > image)? Yes, from stock you will need to flash the default envs in 6 and 7.by bodhi - uBoot
@Stephan, Sorry I could not find it! :) I should have saved them somewhere when I found them. I was so sure I remember where they are ... in my 12 plugs!!! However, if you are running Arch install from way back, then everything is still in NAND (stock u-boot and kernel). All you need to do is to run the oxnas-revese script to set the envs back to boot stock. And you can do this in Arch. Isby bodhi - Off-Topic
Herb, If you have other plugs running 3.17, do you see this on them? these type of notification should be in dmesg too. If you do then it's perhaps it's your network. I don't see this in any of my boxes (but I don't have the NSA320).by bodhi - Debian
@Stephan, Sure I will shortly.by bodhi - Off-Topic
Is there a problem? or were you booting normally? it's hard to tell without seeing the entire serial console log. You can just copy and paste what on the screen to a text file. You can also connection serial console with picocom. Install picom with apt-get (or on Arch, pacman). And to run it: picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0by bodhi - Rescue System
Reset this to disable netconsole start fw_setenv preboot When you want to activate netconsole (when serial is not connected), set this in Debian before rebooting: fw_setenv preboot 'run preboot_nc'by bodhi - uBoot
nohud Wrote: ------------------------------------------------------- > Yes, this should add the support needed to the > kernel so the stock wifi will work with > wpa_supplicant and other wireless utilities. > > CONFIG_CFG80211_WEXT=y Thanks nohud. I've missed this from the Kirkwood kernel. I will add it to the next OXNAS release.by bodhi - Debian
effendi, In Debian, please get the listing of u-boot envs and post here: fw_printenvby bodhi - uBoot
effendi, > ## Error: "preboot_c" not defined This is part of the netconsole starting command: preboot_nc=run if_netconsole start_netconsole If you want to start netconsole (which is probably not needed, since you have serial console), then the preboot env should be: preboot=run preboot_ncby bodhi - uBoot
effendi Wrote: ------------------------------------------------------- > > dmesg | grep -i 'bad' > [ 5.490000] Scanning device for bad blocks > [ 5.540000] Bad eraseblock 379 at > 0x000002f60000 > [ 6.170000] UBI: number of bad PEBs: 1 > [ 6.210000] UBI: number of PEBs reserved for > bad PEB handling: 9 > > > Hi, @bohdi.by bodhi - uBoot
Here is the rootfs label setup: http://forum.doozan.com/read.php?3,12381,18781#msg-18781 Note that the rootfs should be lowercase or upcase consistently, in the disk pattion and the u-boot env.by bodhi - uBoot
TheDoo, In addition to the good advices from graymanforhire above, > I figured it might be the Uboot parameters, > unfortunately I can't ssh into just the pogoplug > to update them. Or I'm missing something. You need to use the rootfs label for the usb rootfs, and setup u-boot envs to mount rootfs with label, while booting multiple disks. I've just posted thisby bodhi - uBoot
mikeh49 Wrote: ------------------------------------------------------- > I'm preparing to update a Pogo P21 with the new > u-boot to use the new kernel and Debian file > system. The bad blocks check returns the > following: > > > /$ dmesg | grep -i 'bad' > [ 1.710000] Scanning device for bad blocks > [ 1.780000] Bad eraseblock 981 at &by bodhi - uBoot
suo_jian, It's a strange behavior from serial console (repeating prompt). If you'd like to confirm your booting process, please power up, interrupt serial console and then list the envs, I will take a look. printenvby bodhi - uBoot
habibie, To do what you plan to setup NFS booting: 1. Setup NFS v3 share on the GoFlex Net first, and make sure you can mount it on the other boxes. This is a little bit time consuming. 2. Once you can mount NFS v3 shares and use it on the other boxes, then install u-boot on the other boxes, make sure you can run normally with USB drive, as before. 3. Download the latest rootfs (3.14, 3.by bodhi - uBoot
gunjae, > But, I believe it is out of 1M area for uboot. > Right? Right, it is way out, higher than 1M. Besides, your u-boot in NAND has booted until after the kernel was loaded successfully, and solid green LED means kernel was loaded and starting. So it is not u-boot. The remaining possible problems are bootargs and rootfs mounting. And your bootargs look OK. So for whatever reasby bodhi - uBoot
gunjaekoo, Does the LED lit solid green? do you use static IP address? netconsole only shows that much, nothing more, unless you set it up further. All I can suggest is: - Take the USB to another box and do fsck to make sure there is no file system error. - If there was no error, perhaps try rootfs label approach: 1. Take the USB to another Linux box, mount it and label the rootfs (iby bodhi - uBoot
@nohud, > Enabling the following in the next kernel compile > should fix the issues with wireless: > > Old > # CONFIG_CFG80211_WEXT is not set > > New > CONFIG_CFG80211_WEXT=y > > > See > https://github.com/raspberrypi/linux/issues/171 Which wireless issue? with the stock wifi ?by bodhi - Debian
Neptune Wrote: ------------------------------------------------------- > Ok, I downloaded and installed the Archlinux and > here is the output. > I am unable to get the env output. > > # cat /etc/fw_env.config > cat: /etc/fw_env.config: No such file or > directory > # > Create this file and copy the content above to it. > > And here is the compby bodhi - Rescue System