@addy75, :)) no problem. Sometime the more experience we have, the more we tend to overlook something that trivial :))by bodhi - Debian
@addy75, Make sure the permission is correct, does it own by root? Like this -rwxr-xr-x 1 root root 1338 Sep 1 00:52 /etc/rc.localby bodhi - Debian
joey Wrote: ------------------------------------------------------- > i need help with running debian on a ix2-dl > Processor : Feroceon 88FR131 rev 1 (v5l) > BogoMIPS : 1589.24 > Features : swp half thumb fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant : 0x2 > CPU part : 0x131 > CPU revision : 1by bodhi - uBoot
addy75 Wrote: ------------------------------------------------------- > cat /var/log/message > -> Data or directory are not existing Do some research on OMV: where is the log file?by bodhi - Debian
> logread doesn't exist. If i try to install > busybox-rsyslogd (which i've read contains > logread) the system wants to uninstall > openmediavault.... Try logger -s -i "End of rc.local" exit 0 and cat /var/log/messageby bodhi - Debian
addy75, Please post the entire content of /etc/rc.local: cat /etc/rc.local Sometime, if there were error that has stopped rc.local somewhere, then these statements could have been skipped. To see if there was no error in rc.local, log the end of its execution: in /etc/rc.local logger -s -i "End of rc.local" exit 0 Then check it after the system has booted: logread |by bodhi - Debian
addy75, > It works when i typ it in the cli. > Putting it in rc.local doesn't work. > Well, something is wrong in your rc.local! If you post it here, I'll take a look. > Will it be possible (when it works) to make the > led green, and red only when the drive is written > on? Sure /etc/rc.local echo ide-disk1 > /sys/class/leds/nsa325:red:sata1/by bodhi - Debian
addy75, At command line: echo ide-disk1 > /sys/class/leds/nsa325:green:sata1/trigger echo ide-disk2 > /sys/class/leds/nsa325:green:sata2/trigger and try access the disk again.by bodhi - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > ty for the tip. The main partition was dev/sda2 (I > just deleted the /dev/sda1), so it was not 0:1. > did some image-repartition-restore and now it is > /dev/sda1 and boots debian fine. > > It seems it should be able to boot also arch or > linux without uInitrd without making > modiby bodhi - uBoot
Cool! And, btw the $ works fine the same way { does. It really depending where the variable is placed.by bodhi - Debian
Wzl, Narrow down to a minimum set of envs to see it clearly: usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay rootfstype=ext3 $mtdparts $usb_custom_params dt_load_dtb=ext2load usb 0:1 0x1c00000 /dts/kirkwood-pogo_e02.dtb dt_load_initrd=ext2load usb 0:1 0x1100000 /uInitrd dt_load_uimage=ext2load usb 0:1 0x800000 /uImage dt_usb_boot=run dt_lby bodhi - Debian
@ bobafetthotmail, Looks like it failed in loading uImage and uInitrd: sata_load_uimage=ext4load ide $device 0x800000 /boot/uImage sata_load_uinitrd=ext4load ide $device 0x1100000 /boot/uInitrd To troubleshoot this, at serial console: NSA325 > ide reset NSA325> ide info NSA325> ide part NSA325> ext4ls ide 0:1 /boot Please post output of the above commands. The idea iby bodhi - uBoot
Wzl, Your bootcmd should be: bootcmd=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=$bootdelay rootfstype=ext3 $mtdparts; run usb_bootcmd However, the bootargs should be separated from the bootcmd. it will make it easier to read and debug. Btw, Your usb_set_booargs has overided that any way. So you need to change usb_set_bootargs: remove the root=uuid....by bodhi - Debian
Addy, What is the output of cat /sys/class/leds/nsa325:green:sata1/trigger cat /sys/class/leds/nsa325:green:sata2/trigger And try this for testing the HDD access (if it is mounted as sdb1). See if the LED light will flicker. ls -lR /media/sdb1by bodhi - Debian
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 QuoteTby bodhi - Debian
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
@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
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 yby bodhi - Debian
@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
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 ilby bodhi - Debian
@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. NOTby bodhi - Debian
@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 Eby bodhi - Debian
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
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 soby bodhi - uBoot
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 fiby bodhi - Debian
@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
@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
@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. > printenvby bodhi - Debian
@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
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