Show all posts by user

Re: Pogoplug B04 (OXNAS 820) - unable to boot. - 10 years ago

smi, If you have installed new u-boot then there is no need to append DTB. Since you have serial console, it is safe to follow section A (quote below). It is stuck there because either bootargs or the uImage. If you do want to keep it simple, and run with DTB embbeded, then post the output of printenv in serial console and the bootlog here and I'll take a look. Kernel thread QuoteT

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

SomeoneOnLine Wrote: ------------------------------------------------------- > Is it possible to get USB read/write status on any > of the LEDs? Not currently. But there is an upcoming kernel patch that will have triggers just like for SATAs. I have not tried to backport it, but it seems doable to incorporate into the kernel 3.17.

by bodhi - Debian

Re: Debian Pogoplug V4 Dropping WIFI - 10 years ago

@Peter, > I don't think the pogoplug was designed with very > good heat management in mind, which is totally > acceptable considering the price. You'd bet! the Dockstar and the Pogo V4/Mobile are running very hot. I have silicon feet that raise them higher 1/4" above the flat surface, that seems to help reducing the temperature down quite a bit.

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

nibre Wrote: ------------------------------------------------------- > Can I upgrade the system to Debian Jessie just by > editing sources.list or would that create > problems? You could. Update source list and then apt-get update, apt-get upgrade. But usually securiy updates are lagging in Testing, comparing to Stable, so that should be considered. And please remember backup y

by bodhi - Debian

Re: Debian Pogoplug V4 Dropping WIFI - 10 years ago

@Peter, Kernel log is in /var/log/dmesg, so it migth have something in there too. But if you don't have var/log/message file, it is probably because you're logging to RAM. If your rootfs is based on my uploaded basic rootfs, then it is logging to RAM. To temporarily switch to logging to disk, comment out the option as below and restart (it's been a while so I'm not 100%

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

SomeoneOnLine, > Is there much benefit with 3.17 over 3.16 > on the nsa325? I think it's really individual case where the new features would be beneficial to update. You could look at the general kernel changes log (link in the 1 post). I would update the kernel to get any bug fixes that come with it. > > I was thinking about updating my uboot but too > chicken il

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

@SomeoneOnLine, With stock u-boot the last kernel version that you can use that kills the watchdog is 3.16.0-kirkwood-tld-2. So you should use the 3.16.0-kirkwood-tld-2 rootfs. QuoteThe 1st post Updated 28 Sept 2014: Kernel 3.16.0-kirkwood-tld-3 package was uploaded. The only change in this version from 3.16.0-kirkwood-tld-2 is to incorporate the fix for the NSA325 watchdog. NOT

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

@nibre, Your bootargs looks OK, and other u-boot envs are OK, too. So now it points to your rootfs and the uImage. - Did you recreate the uImage file with embedded DTB? if you did, then restore the orginal uImage from the basic rootfs (it needs to be one without embedded DTB). - If the above was already checked out, then it's better to recreate the basic rootfs from scratch using an E

by bodhi - Debian

Re: Pogoplug to TOR plug - 10 years ago

Gravelrash Wrote: ------------------------------------------------------- > ? No takers ? ok I am interested. But no time to collaborate :) please let us know your progress. Fyi, CloudEngines is selling the SafePlug (it's a TOR box) but afaict it's not that safe!

by bodhi - Debian

Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) - 10 years ago

nibre Wrote: ------------------------------------------------------- > For me cat /proc/mtd returns > mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" > mtd1: 00e00000 00020000 "boot" > mtd2: 07200000 00020000 "rootfs" > > So should I change mtd0 in the commands to mtd1? No need to, but if you are running new u-boot then yes. Change it so

by bodhi - uBoot

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

Addy, Oops, typos in the if statements :) But you get the idea? hdd1 and hdd2 were the old settings. Corrected commands should be: Quoteif [ -d /sys/class/leds/nsa325:green:sata1 ]; then echo ide-disk1 > /sys/class/leds/nsa325:green:sata1/trigger fi if [ -d /sys/class/leds/nsa325:green:sata2 ]; then echo ide-disk2 > /sys/class/leds/nsa325:green:sata2/trigger fi

by bodhi - Debian

Re: Debian Pogoplug V4 Dropping WIFI - 10 years ago

@Peter, Look in your log file var/log/message to see if dhcp re-attempt to connect? if you log to ram then use logread.

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

@addy, Try execute it at command line: echo default-on > /sys/class/leds/nsa325:green:sata2/trigger echo none > /sys/class/leds/nsa325:green:sata2/trigger Do you see the SATA2 LED light turned on/off with these 2 commands?

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

@nibre, Usually you will see the message: Quote## Flattened Device Tree blob at 62c00000 Booting using the fdt blob at 0x62c00000 Starting kernel ... This behavior points to your u-boot envs problem, most likely bootargs. Please interrupt netconsole during the count down and get the listing of the envs and post here. > printenv

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

@nibre, Yes. stock u-boot does not boot USB drive. You'll need to either install new u-boot, or boot with tftp. - For new u-boot see: http://forum.doozan.com/read.php?3,16017 - For tftp booting , see section Updated 29 Oct 2014, kernel installation section B in the first post.

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

addy75, There was an extra space in the these 2 commands I posted before! (I've modified the post). pls try again: if [ -d /sys/class/leds/nsa325:green:sys ]; then echo default-on > /sys/class/leds/nsa325:green:sys/trigger echo none > /sys/class/leds/nsa325:orange:sys/trigger fi if [ -d /sys/class/leds/nsa325:green:sata1 ]; then echo ide-disk1 >

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

Hi addy75, > I'm working with kernel 3.17.0-kirkwood-tld-1 and > uboot uboot.2013.10-tld-1. > The system (rootfs) is installed an an ssd, my > data-disk is an 4TB WD Red. > System works goods (little problems with the > mysql-server for owncloud but i will fixit ;-) ) Thanks! these information are very helpful. > I adjusted the settings in rc.local. Yes

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

@addy75, Are you running the new u-boot, or stock? sounds like you overcame the watchdog while using OMV. It would be helpful to other users if you could briefly describe which u-boot image you are using, which kernel version, and what storage devices you are using (USB, HDD, ...) and where is the rootfs resides (USB or HDD).

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 10 years ago

addy75, Check your /sys/class/leds, and your settings of the LEDS. Some of the LED names were changed in 3.17 in DTS. # ls /sys/class/leds/ -1 . .. nsa325:green:copy nsa325:green:sata1 nsa325:green:sata2 nsa325:green:sys nsa325:green:usb nsa325:orange:sys nsa325:red:copy nsa325:red:sata1 nsa325:red:sata2 In 3.16 they were set like this: if [ -d /sys/class/leds/nsa325:green:

by bodhi - Debian

Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile - 10 years ago

denexo, Not exactly! loading the kernel uImage/uInitrd and mounting rootfs are 2 different phases in booting. Just so happen that the rootfs is on an Ext4 partition (therefore uImage and uInitrd are on /boot of that partition). 1. uImage and uInitrd loading: instead of ex2tload, use ext4load, see if it behaves differently: ext4load usb 0:1 /boot/uImage ext4load usb 0:1 /boot/uInitrd

by bodhi - uBoot

Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile - 10 years ago

@denexo, > Is it possible to be able to load > Jeff''s rescue system at NAND when no other rootfs > is found? If it helps, i have kept a backup of fw > boot env config prior installing your U-BOOT. What > i mostly want to ask if setting the following boot > envs (as seen at Jeff's script): > > fw_setenv rescue_installed 1 > fw_setenv set_boota

by bodhi - uBoot

Zyxel NSA540 - 10 years ago

Wow! this is the big motha of the zyxel series ;-) dual-core Freescale! http://www.amazon.co.uk/Zyxel-NSA540-Power-Diskless-1-2GHZ/dp/B00O4FMSNO

by bodhi - Off-Topic

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

@denexo, I've double checked the patch! the patch was applied correctly. So we're out of luck until someone else test this change and confirm one way or the other.

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

@denexo, Let me create the delta patch and confirm that it was good. Among the 3 files in that patch, 2 already in my source tree, so I actualy patched only 1 file.

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

May I suggest we move this to a new thread, specific about performance? @Shv, please start the new thread with your numbers. I think you had the most info so it would be helpful.

by bodhi - Debian

Re: Pogoplug e02 boot from iscsi - 10 years ago

Katsumoto, I don't think u-boot support booting with iScsi. But you can boot the kernel with tftp, providing you can run tftp server on the iscsi NAS. Or boot with nfs if you can run nfs server on that NAS. And I should also add that, if you can set up tftp on the iscsi NAS to boot uImage and uInitrd, then it's possible that the rootfs can be on the iscsi drive. So the end result

by bodhi - uBoot

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

I think we are talking apple and orange here :)) I am sure Shv meant the local HDD speed: QuoteIf you look at my comparision of device performance at http://pogoplug.cwsurf.de/forum/viewtopic.php?f=4&t=13#p75 you will see that you don't reach the highest possible speed with your Pogoplug E02. Moreover you can see that the Goflex Net device can read data from harddrive with 100MB/s fro

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

shv, > What throughput can be reached > with the Debian Kernel on the Zyxel NSA325v2? > Could it be improved if the same or similar > optimizations are used for the Debian kernel? I'm not sure what optimization done were done on Arch and FreeNAS. Do you have some benchmarks that indicate there are differences in performance between Debian & Arch?

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

denexo & others, Here is the kernel 3.17.0-oxnas-tld-2, which incorporated the uvc_video patch. Download at dropbox: linux-3.17.0-oxnas-tld-2.bodhi.tar.bz2 md5: eb088226f869206ebad88036018d89cc Please test and let me know.

by bodhi - Debian

Re: Sata boot failed after 3.17 upgrade. - 10 years ago

robert, > I did follow! :) > All them, sequentially! (It was not clear for me) > > Step 3, has sense, (i mean to me) because this > new kernel is ftd. > It is true. Since you installed u-boot first, I can see why you thought it was necessary to do this first :) in any case, the u-boot envs in the kernel thread are the ones to use.

by bodhi - Debian