I've uploaded the latest rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Please see 1st post for download link.by bodhi - Debian
tilator, I've just remember this. Which u-boot are you running? the version I've released has SNTP, but the RTC clock driver was commented out, since the Pogo V3 does not have it. You could take a look at the source code in my GitHub. And see if you can put it back, and use SNTP to query the datetime, and that hopefully will update RTC during boot. However, I am not sure if our cby bodhi - Debian
bobafetthotmail, > I know. My point still stands. Adding letters > after names is silly and should be avoided. I do agree. > Sorry but there isn't any clear indication on the > box nor on the board. no V1 or V2 or V3 or > nothing. > But obviously the above was probably the reason for the DTS author to have named them that way? We know what's in the kiby bodhi - Debian
notoneofmyseeds, For step 1. If you run Windows PC and have Acronis True Image, I would recommend using that and be done quickly. If you do it as instructed in a Linux box, then the drive letters need to be adjusted to whatever being mounted in your box. Sometime the drive is mounted using its parttion label, or using a special name (which is your situation). So in this thread: http://by bodhi - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > >So please list the model and DTS file names > here. > > Can you explain a bit more in detail? What do you > want me to do? :) > I need to describe the difference between the 3rd version of the DTS and the exisiting 2 DTS. And how would users determine if they should use this 3rd versby bodhi - Debian
tilator, > Sounds like rootfs will be corrupted several times > more before file system drivers are OK. I think we are safer to stay with kernel 4.1 Oxnas and not try to test using real rootfs until we figure out the reason. The puzzle is why Kirkwood 4.4 rootfs is working fine with Ext4 but not the Oxnas 4.4 rootfs? something in the Oxnas-specific code must have triggered this bug.by bodhi - Debian
vaidyasr, You can try creating 2 USB rootfs (versions 3.16 and 3.18.5). See this kernel/rootfs thread: http://forum.doozan.com/read.php?2,12096 Look for these 2 tarballs in 2 sections: Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2 QuoteUpdated 02 Sept 2014 (rootfs): Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.16.0-kirkwoby bodhi - Debian
I did some testing with what we already have. Using an Ext4 rootfs. The interesting behavior of Ext4 driver: Booting with kernel 4.1, there is no problem running it for a while. And then, booting with kernel 4.4 caused an error: [ 26.608547] EXT4-fs error (device sda1): ext4_get_branch:170: inode #409672: block 1684366702: comm mv: invalid block After booting back to kernel 4.1, thiby bodhi - Debian
> > It would just be "nice" to have the device still > alive and updated. It's not easy to find other > similar devices with internal sata, esata, > two usbs, passive cooling, small footprint > and so on. Yeah, I plan to revisit this so we can upgrade the kernel. Just need to find more time... or a good hint from mr google :) or perhaps from someone whoby bodhi - Debian
> Thats the same model as mine then: lm85 and red > USB LED. > Would be nice if bodhi can provide a third variant > of the dts file along with the next kernel > release. > So far I can live without the red USB LED but got > the fan tamed :) Sure I will :) But before doing that I would like you guys to post the definitive info about the variants. Currently NAS Centralby bodhi - Debian
tilator Wrote: ------------------------------------------------------- > Can you tell me one more thing. > > Compiling u-boot 2014.10 does make u-boot binary, > but not SPL. What might I do wrong? Nothing wrong. You can build u-boot separately, which is what I do normaly (there is no need to rebuild SPL, 2013 version works just fine). If you want to rebuild SPL, then use theby bodhi - Debian
sLOID, Here you go, use this u-boot image for LaCie ns2l to run kwboot with option -p: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.ns2l.mtd0.kwb -pby bodhi - Debian
Damien Wrote: ------------------------------------------------------- > Bodhi, > > I must say I'm starting to be a bit mystified by > these issues. I'm going to revert to 3.18-5 on > Jessie and see how it goes. So far, these are the > tests I've done with my cheapo-chinese-Wifi: > > 1- Debian 7 wheezy w/ kernel 3.18-5 with kernel > driver =by bodhi - Debian
Damien, The configuration for RTL8192CU did not change in 4.4, it is the same as in 3.14. Does the kernel driver in 4.4 cause the same problem? have you let it run for a while?by bodhi - Debian
fido95, > My pogoplug indicator doesn't blink green or red, > with nor without sd card. > Is connecting via serial converter to load uboot > the only solution to connect with my pogoplug ? Yes, connect serial is the only way. Yes those should work. But also read this thread before buying: http://forum.doozan.com/read.php?8,13263by bodhi - uBoot
sLOID, > i tried your workaround but without success. i'll > give your actual u-boot a try Don't flash :) they are not built for the LaCie! do only UART booting see if it works.by bodhi - Debian
sLOID, It is a classical problem with ntpd and ntpdate resource fighting. Sep 4 10:14:56 LaCie daemon.err ntpd[1502]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Our member restamp did a really good job with his explanation: http://forum.doozan.com/read.php?2,20817,20828#msg-20828 If you were running one of my new u-boot images, then SNTP prby bodhi - Debian
tilator Wrote: ------------------------------------------------------- > I have it all. Do you want it? It is a little old, > though ;) I could have used this long ago :) I don't see the need for this now. Except if we need to find out what it does with the RTC driver m41t00. I think you should try to resolve the shutdown problem first (perhaps it is related to the RTC problemby bodhi - Debian
sLOID, Which rootfs are you running? if you are running my 3.18.5 rootfs then your ntpd should be running. Could you post the whole dmesg output and logread output here or pastebin them. I don't think I can guess the problem without seeing the whole picture. > is > there a way to set the rtc over the > serial-connection after interrupting the boot > sequence ?? Not liby bodhi - Debian
Woow. I did not know we have GPL for this?! is that from Oxnas? do you have the whole GPL package or just a few files?by bodhi - Debian
tilator, > There must be some reset routine somewhere in the > old kernel Apparently so. I agreed, seems like it needs to be more than what being done in the 4.1 driver. Wonder what's in 4.4 or 4.5-rc?by bodhi - Debian
sLOID, Yes dmesg for kernel messages and also use logread to print out Debian messages (this log file is normally in var/log/messages, but we are logging to RAM so logread will print it)..by bodhi - Debian
sLOID Wrote: ------------------------------------------------------- > hi bodhi, > > it's the "LaCie Networkspace 2 lite". I include > the specified name of the dtb-file in the DTS > folder while building the image. > (kirkwood-ns2lite.dtb). Everything went without > errors, so it should be the right one. > > sLOID Now this is a puzzle, it&by bodhi - Debian
steve1987, > 2. I used the latest roots I found, is there any > newer I can use? Unfortunately, no. The latest rootfs is 3.18.5. > fw_setenv reboot 'run preboot_nc' (overwritten > previous value) There is a typo here. fw_setenv preboot 'run preboot_nc' For netconsole, because there are many versions of netcat in different OS, you'll hby bodhi - uBoot
Waynosan, Cool :) > Do I still need to go through part D. Add uEnv.txt > to /boot directory? No need to. Only if you want to play with the envs for some purpose and don't want to mess up the boot envs. BTW, I have a backup blog: bodhi's corner.by bodhi - uBoot
Oh I forgot this about Arch: bootargs also needs modification because there is no uInitrd file. I've updated the above instruction.by bodhi - uBoot
Waynosan, At this point, to boot Debian USB rootfs: Power up, interrupt serial console and: setenv dtb_file /'boot/dts/kirkwood-pogo_e02.dtb' boot And to boot Arch rootfs, setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts $custom_params' setenv dtb_file /'boot/dtbs/kirkwood-pogo_e02.dtb' boot See iby bodhi - uBoot
sLOID, This mtd0 will not work with the current /etc/fw_env.config. So definitely fw_printenv/setenv will not work. The above link pointed to u-boot images, so I really can't tell what the correct settings should be. However, we've strayed far from original topic! Getting back to the RTC, what is the exact name of this Lacie DTB?by bodhi - Debian
steve1987, 1. The LED behavior might indicate that the kernel file was not the right one to boot with the current setings of u-boot envs. Which u-boot you have installed? version ? 2. The rootfs 3.18.5 did not yet support the NSA320S kernel. QuoteUpdated 16 April 2015: Kernel 4.0.0-kirkwood-tld-1 package has been uploaded. The following features were added: 1. This FDT kernel nowby bodhi - uBoot
sLOID, > yeah, i did. while playing around i found other > frightened stuff: commands like: > > fw_setenv bootdelay=5 > This should be fw_setenv bootdelay 5 But it is not related to the error below. > end up with: > > Warning: Bad CRC, using default environment > MTD erase error on /dev/mtd0: Invalid argument No worry. This only means that the aby bodhi - Debian