stef34280, Indeed. That was my typo in the internal default envs :) usually we just flash the default envs image, which has the correct name for Pogo E02, so nobody noticed this yet. Thanks for reporting this. I will make a note and correct it. Yes, you have fixed it with setenv dtb_file kirkwood-pogo_v4.dtbby bodhi - Debian
haridsv, > I only see this current thread under there, but > before my first post here it was completely empty. > All my previous threads are still missing. That's strange. Probably just a coincidence. Try to resubscribe to threads and see if it works.by bodhi - Off-Topic
habibie Wrote: ------------------------------------------------------- > I can understand that. I used to moderate some > forums that was overwhelmed with spam post. The > only way to curb such spam posts is to block the > IP Address, unfortunately. Usually it is easy fo rme to delete the whole spam topic. This case is more severe, because I have to open each thread and remoby bodhi - Off-Topic
> Don't know what exactly you meant by > followed. However, if you meant your posts > on any of the removed spam posts. they also get > removed by the admin/mod unless they get split > before being removed, AFAICT. That only applies to a spam post created by spammer. Not in this case, where the spammer posted a message on existing legit posts. Jeff has blocked this sby bodhi - Off-Topic
nastynas Wrote: ------------------------------------------------------- > Sorry.. I've been trying to follow your > instructions and made another attempt on Debian on > NAS326. > > EDIT: I fixed my issue. Everything's fine. :) Cool!by bodhi - Debian
This one is pretty bad. More than 100 spam messages. I've notified Jeff to see if Jeff can delete all messages form this spam account. It got tiring to delete this son of a b &**%^%$ mesages manually :))by bodhi - Off-Topic
stef34280, > kwboot is working. Had to try a dozen of times > before I got a pogoV4 prompt in console (killing > and restarting kwboot) That's the Pogo V4 quirks. A lot of time you need to control-C and then restart until the handshake occurs. > ~ # cat /proc/mtd > dev: size erasesize name > mtd0: 00200000 00020000 "u-boot" > I do noby bodhi - Debian
I will upload the u-boot-2017.07-tld-1 version for this box shortly, when I have time to update the installation instruction.by bodhi - uBoot
So you dont have a Red USB LED?by bodhi - uBoot
Mike, We have a Wiki thread, where you can learn about serial console: https://forum.doozan.com/read.php?2,23630 Quote> Am I correct in understanding that if I follow the > installation steps 1 thru 5 (upgraded for the Oct > 2017 release) and placed on a fresh 4gig Ext3 > stick (rootfs/boot/uImage) in the front usb port > of the Pogo-P21, that the Pogo-P21's firmwby bodhi - Debian
saschbaer, Quote> Processor : Feroceon 88FR131 rev 1 (v5l) > BogoMIPS : 999.42 > Features : swp half thumb fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant : 0x2 > CPU part : 0x131 > CPU revision : 1 > > Hardware : Feroceon-KW > Revision : 0000 > Serial : 0000000000000000 Yes, it is possible to run Debian on this bby bodhi - Debian
Remember, do not start flashing before I advise you to do that!by bodhi - Debian
stef34280, 1. You do have serial console. So you should try to run kwboot first to make sure you have a rescue path https://forum.doozan.com/read.php?3,12381 QuoteImportant Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should bby bodhi - Debian
stef34280, > 1.010000] Scanning device for bad blocks > [ 1.010000] Bad eraseblock 4 at 0x000000080000 > [ 1.050000] Bad eraseblock 697 at > 0x000005720000 Warning: what I advise below only applicable to your specific configuration (in case other users read this and would make a wrong assumption when their configuration is different). You have the Pogo V4, thereforeby bodhi - Debian
Stephen, > I cannot find any refs to sensors either, which is > odd because lm85 shows up in lsmod and playing > around with the sensors command I can get readings > and using the sysfs interface I can poke fan > speeds, so I guess it's working? Yes it is working as expected. I forgot this sensor driver is a loaded module :) So you are OK. Now we know you have lm85.by bodhi - uBoot
Stephen, I did not see any sensor here. Please reboot without systemd. And post serial bootlog.by bodhi - uBoot
Mike, Do you have serial console? Post the entire boot log here if you do.by bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,40304,40304#msg-40304 Pleas do not post booting problem in this thread.by bodhi - Debian
huge Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > huge, > > > > > > > root@PogoV4Debian:/temp# ./kwboot -t -B > 115200 > > > /dev/ttyUSB0 -b > > > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > > > > > > > > >by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > feas Wrote: > ------------------------------------------------------- > > > https://forum.doozan.com/read.php?3,27280 > > The post start with > > QuoteWhile in stock OS... and I'm not so > I don't know if it applies... The binaries work in both stock OS and any other moby bodhi - uBoot
huge, > root@PogoV4Debian:/temp# ./kwboot -t -B 115200 > /dev/ttyUSB0 -b > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > When it stuck here, it might mean that your serial connection is not solid. At this point u-boot has not started yet, so don't worry about the envs. Check the wires and try again. Serial console might work OK with marginal connections, but kwboot doesby bodhi - uBoot
Maarten, That's a bummer :) BTW, the solder buttons are quite soft, you can use small pins and push them in temporarily to connect. And then later use a JST header instead of just wires.by bodhi - uBoot
Stephen P, IIRC, the rebrand TDC is NSA310a. But you have to try it to verify. It should boot with either one. But the correct one will give you the right sensor. Boot with the NSA310a DTB and then post the bootlog here.by bodhi - uBoot
Mike, Please start a new thread and post your prolem again with serial boot log, or whatever you want me to take a look.by bodhi - Debian
Thanks musv! I'll take a look and incorporate in the next release.by bodhi - Debian
> Make CMD_CLK "great again!" Are you going to have that on your baseball cap? I'm cleaning up my keyboard :))by bodhi - Off-Topic
Check to see you have which of these 2 boxes: http://zyxel.nas-central.org/wiki/Category:NSA-310 And If you have a red USB LED then it's the 3rd variant.by bodhi - uBoot
kralan Wrote: ------------------------------------------------------- > I am still at 4.9.5-tld-8 and am planning to > upgrade to the latest available kernel soon. > Do I gather correctly from the recent posts that > it's better to wait with the upgrade until the > mvneta issue is sorted out? It's really up to you. If your use case is similar to musv then I'by bodhi - Debian
Snarky, 1. Code tags button is the right most button on top of the text box where you type your post (the B button for bold is the left most). 2. You also did not post the log of commands and their output. When I ask for that, you should copy/paste the entire screen to the post. Don't reformat anything. Since you are new with this, you don't know that the log must be shown aby bodhi - uBoot
kirkwood-nsa310.dts This variant is the "original". This has the sensor adt7476: i2c@11000 { status = "okay"; adt7476: adt7476a@2e { compatible = "adi,adt7476"; reg = <0x2e>; }; }; kirkwooby bodhi - uBoot