bodhi Wrote: ------------------------------------------------------- > Apparently, I've screwed up :) with kernel > 3.14.0-kirkwood-tld-2 regarding the NSAxx sensors. Bodhi, you sure? I tried a diff on the 2 files: colordiff config-3.14-kirkwood-tld-1 config-3.14-kirkwood-tld-2 33c33 < CONFIG_LOCALVERSION="-tld-1" --- > CONFIG_LOCALVERSION="-tld-2"by davidedg - Debian
gabor Wrote: ------------------------------------------------------- > Can i clone the config from the current kernel? > Did i have to write a new uboot? I'll try to summarize how I do it 0. Ensure you have a cross-compiling system (I use CodeSourcery, but any will do) 1. Download and extract kernel sources (3.14.3 works fine) 2. download Bodhi's patches (http://foruby davidedg - Debian
Greg, I think I've read something similar on this: http://archlinuxarm.org/forum/viewtopic.php?f=27&t=3851 Does it change behaviour if eth cable is plugged or not and if switch is 100Mbps or 1Gbps ? Also, I derived my kernel config for my Debian install both from Bodhi's (for the patches) and from Arch's (for the config), trying to leave out all not strictly needed.by davidedg - Debian
Thanks to your wonderful work, I got my new NSA325v2 working within 2 weeks! I set up a repo on github to document the whole process, in case someone needs it :D https://github.com/davidedg/NAS-NSA325-mod Thank you again all.by davidedg - Debian
WarheadsSE Wrote: ------------------------------------------------------- > IIRC either the 320, or the 325 was never actually > intended to talk to the OS, and merely does its > own thing. You mean that I can ignore those errors since the fan will be piloted from the driver and not from userspace? Also, regarding the FDT kernel for NSA325, I am trying https://github.com/pkby davidedg - Debian
Hi, I'm using 3.14.0-kirkwood-tld-2 and rootfs from bodhi http://forum.doozan.com/read.php?2,12096,page=1 Sensors do not seem to be working: root@debian:~# cat /sys/class/hwmon/hwmon0/device/temp1_input [ 396.131910] nsa3xx-hwmon nsa3xx-hwmon: Failed to read MCU data 0 root@debian:~# cat /sys/class/hwmon/hwmon0/device/fan1_input [ 401.391909] nsa3xx-hwmon nsa3xx-hwmon: Failedby davidedg - Debian
Found the error, I had CONFIG_MTD_BLOCK=y Confirmed also by this: if I use your kernel, initrd and rootfs and I modprobe mtdblock, it gives same errors. Now I have another problem, always using 3.14.0-kirkwood-tld-2 and your rootfs, I cannot seem to have sensors working: root@debian:~# cat /sys/class/hwmon/hwmon0/device/temp1_input [ 396.131910] nsa3xx-hwmon nsa3xx-hwmon: Failedby davidedg - Debian
bodhi Wrote: ------------------------------------------------------- > It does not ring a bell! it is strange that your initramfs would look for the kernel in NAND. I think that's where the stock kernel resides? if it looks for mtdblock6 then it would not be that weird. Actually, my initramfs is a very simple one, based upon busybox. The operation that triggers the error is "fiby davidedg - Debian
davidedg Wrote: ------------------------------------------------------- > bodhi, > > I've used your kernel patches to derive a minimal > compiling config. > It gave me some problems about > kirkwood_pm_init(void) symbol not present, had to > forcefully disable CONFIG_PM_RUNTIME, I'd expect > #ifdefs should have take care of it. > I hope it will bootby davidedg - Debian
bodhi, I've used your kernel patches to derive a minimal compiling config. It gave me some problems about kirkwood_pm_init(void) symbol not present, had to forcefully disable CONFIG_PM_RUNTIME, I'd expect #ifdefs should have take care of it. I hope it will boot, nas should arrive tommorrow or so :D Regarding FDT, I've read Kurlon post and it does not seem rocket science, prby davidedg - Debian
bodhi Wrote: ------------------------------------------------------- Quotebodhi > > - Since there is still no .dts file in mainline > kernel, does it mean that no FDT Kernel can > actually be built ? > True. You'll have to find the NSA325 dts or create > one. Maybe the question is naive - is it that difficult to actually build one? Maybe we can request more infoby davidedg - Debian
Hello! I just bought a pair of NSA325v2 and am going to mod them (as soon as they're delivered), trying to preserve both original nand and stock u-boot. I've already read: http://forum.doozan.com/read.php?2,14351 http://forum.doozan.com/read.php?3,12381 and this thread (this one not completely) What is still unclear to me is: - If I want to compile my own 3.14.2 kernel, shoby davidedg - Debian
Ingmar, it worked like a charm! Kernel Config: CONFIG_CMDLINE="console=ttyS0,115200 root=LABEL=rootusb usb-storage.delay_use=0 rootdelay=10 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root) :::DB88FXX81:egiga0:none" CONFIG_CMDLINE_FORCE=y U-Boot Env: setenv uImageAddr '0xa00000' setenv uInitramfsAddr '0xf00000' setenv prepboot_from_nanby davidedg - uBoot
bodhi Wrote: ------------------------------------------------------- > Now the good news :) the DNS325 is supported in > the latest uBoot, so I might be able to built it. bodhi, thank you for taking time to check. Actually I already rebuilt U-boot 2014.01 and there multiboot works flawlessly (with if statements ofc) I wanted to try to use just stock u-boot mainly as an exercise, andby davidedg - uBoot
But I need to change bootargs, too, depending on which device I'm booting from. But being unable to use "if" or "test" commands, if I just execute them in order, the last one will win Since nand is always available, I may reverse order: load nand uImage; load hdd uImage; load usb uImage So if present, the last one will overwrite the previous one. But how can I do wby davidedg - uBoot
Hello. I am trying to do conditional booting (USB -> HDD -> NAND) using *only* original U-boot. I tried this: setenv uImageAddr 0xa00000; setenv uInitramfsAddr '0xf00000' # from USB setenv usb_root 'LABEL=rootusb' setenv usb_opts 'usb-storage.delay_use=0 rootdelay=10' setenv usb_load_uImage 'ext2load usb 0:1 ${uImageAddr} /boot/uImage'by davidedg - uBoot
Buttzy10169 Wrote: ------------------------------------------------------- > No no soldering on mine anyway it already had > pins. > > And for uboot its risky compileing and flashing a > new one unless you can get uart booting to work or > have a jtag. I think its possible with the default > uboot but I'm unsure of how an if is written in > uboot. Can youby davidedg - Debian
@Buttzy: is the serial a TTL 3.3V one? @Bodhi, that's clear, and I admit I kinda already knew this, but ignorantly thought it was available only in custom compiled u-boot - thank you for reminding me the obvious :D So it seems I have a viable option now. I saw your signature post (latest uboot builds): are you an u-boot dev or, simpler, do you know if latest u-boots (from official site)by davidedg - Debian
Buttzy10169 Wrote: ------------------------------------------------------- > I think I seen someone before who had some kind of > if statement in uboot but you would have to check > on that I forget where I seen it was when I first > started with goflex net. Oh no problem with that, I just mean: is it possible with its stock u-boot or I should compile a new one? > As forby davidedg - Debian
Buttzy10169 Wrote: [...] > Install debian package "acpid" [...] > And the following python script lets you do something with the copy button: [...] > If anyone know's a better or more responsive way > to use the copy button let me know as to use the > buttons at the moment i have to keep them pressed > for a second or 2 Hi, You may try the "esekeby davidedg - Debian