pengu Wrote: ------------------------------------------------------- > it's quite different: > I'm starting kwboot first, then powering on the > device and it loads. > this seems to interrupt the thing mentioned > earler > The NSA320s doesn't go off again as without kwboot > and I don't have to manually power it on again. Sorry I don't quitby bodhi - Debian
pengu Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > ... > >I've started to work on u-boot and think > > it will be a little slower to bring up because > > nobody has brought this SoC up in mainline > u-boot. > > The Medion Life P89634 MD 90221 haby bodhi - Debian
pengu, > Booting debian via USB and TFTP isn't posible with > it, I have do flash the kernel stuff into NAND. > with your NSA310s uart U-Boot, the link is up with > 1000 baseT-FD in and I can boot via TFTP as I did. Did you do the same sequence with my built NSA310s uart U-Boot? meaning starting kwboot so it spinning and waiting, and then press the power button. The linkby bodhi - Debian
slb Wrote: ------------------------------------------------------- > I have brand new Pogoplug v4.3.1 and trying to > follow your guidelines as suggested I checked for > bad sectors and found following: > > /bin/dmesg | grep -i 'bad' > > [ 1.010000 ] scanning device for > bad blocks > [ 1.050000 ] Bad eraseblock 786by bodhi - uBoot
pengu, Thanks for confirming UART booting works! I saw you've responded on the other thread about the "no link" problem with the 320S. So to make sure I understood what you've tested: - Boot with NAND stock u-boot, and Zyxel OS. - Reboot into NAND stock u-boot, Debian 4.1 - shutdown -h now - Start with Power button, let it boot all the ways into Debian 4.1 Aby bodhi - Debian
@pengu, Does the 320s have the same PHY problem?by bodhi - Debian
superelchi, > FYI: UART booting the stock u-boot works here > also. But - as expected - still no link. Thanks! just knowing this give us lot of freedom to hack. I've started to work on u-boot and think it will be a little slower to bring up because nobody has brought this SoC up in mainline u-boot. So I expect I would have to do a lot of testing. I was right :) I have built an iby bodhi - Debian
theeleaper, You can usually find the instruction in the man page: # man fw_setenv Quotefw_setenv(8) fw_setenv(8) NAME fw_setenv - Tool for modifying the environment for the bootloader U-Boot SYNOPSISby bodhi - uBoot
Here is the good place to start. http://forum.doozan.com/read.php?8,22027,22027#msg-22027by bodhi - uBoot
theeleaper Wrote: ------------------------------------------------------- > So i switched to debian rebooted pogoplug and it > booted all the way to root@debian:~# looks like > its working..now to install samba...any tips? Cool! After logging in this rootf the first time, remember to change password and generate new SSH key to make it your own unique rootfs. And also updateby bodhi - uBoot
Joey, > Ignorance is bliss, and of course I'm happy > and time flies by (LOL), but in the wake of my > ToDo list now at "hard drive acquisitions" I've > got to figure out which Pogoplugs do torrents and > which run home NAS. Oh, so if there's a Pogoplug > that's just headless and no GUI shell, and it's > just running Samba from webmby bodhi - Off-Topic
theeleaper, If you don't really have a preference, then try booting with Debian rootfs. It is a little easier to deal with when booting with multiple drives: http://forum.doozan.com/read.php?3,22523,22546#msg-22546by bodhi - uBoot
Hi Johnny, That's what I meant is the good news :) you can boot the box using kwboot where it will run this U-Boot image in memory, without touching what's in NAND. This is how we test new u-boot build on box that has this capability. And this capbility makes the NSA310S almost unbrickable :) Not quite 100% unbrickable, but very close. So this can be used as a rescue mechanism whereby bodhi - Debian
Did it boot? if not, unplug all other drives, and then try to boot with only the rootfs drive. Make sure it boots OK, then worry about booting with multiple drives. Booting with multiple drives: ------------------------------------- And I forgot that you are using Arch! You will need to generate initrd so that you can boot with rootf label. OTOH, if you'd rather not do that, then tby bodhi - uBoot
Good news! My NSA310S arrived today. Here is UART booting with rebuilt stock u-boot-1.1.4: ../kwboot-tool/kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-1.1.4-bodhi.nsa310s.uart.bin Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 1 % [...............................................by bodhi - Debian
theliquid, No idea why! since these are not main line packages, dont know what to make of this. RPi rootfs is a prebuilt heavy rootfs so it has many things installed already.by bodhi - Debian
theeleaper, There are a couple things need adjusted. 1. But first, your boot drive is a Transcend USB stick. It's not a bad drive. But for rootfs purpose, you should use a better brand such as Sandisk, to ensure successful booting. 2. Your booting by label has not been properly set up yet. The root device has to be root=LABEL=rootfs in the bootargs: [ 0.000000] Kernel commanby bodhi - uBoot
Thanks for testing! it's a chicken and egg type of problem for the kernel :)) I think we might have to either patch the kernel or build new nsa310s u-boot that does the PHY fixup. It seems the problem with the current driver is that it is limited about what it can do (either that or I don't know enough DTS tricks to force it).by bodhi - Debian
If this does not work. I think I'll better be working on new u-boot for it :))by bodhi - Debian
Ok guys, I think this should fix the PHY problem without doing the poking stuff! Please try this new DTB. I hope this is the correct PHY to use. And remember to turn off your current script before testing :) PS. This seems to be the problem with the driver. If the PHY ID is somehow not the correct one then it will fail to set the registers from DTS.by bodhi - Debian
maihoaomv, > Do you think it might have something to do with > either the kernel or mtd? I ran tld 1 and wheezy > for a year or so and never had a problem with > getting the green led to turn off and setting the > orange led on at shutdown. Not with the kernel or mtd, since it works fine for other GoFlex Home. > I can't swear to it but it seems that the greenby bodhi - uBoot
maihoaomv, > it looks like in order to get the green led to > turn off with any consistency i have to execute > echo timer > > /sys/class/leds/status:green:health/trigger in > the init.d/ halt file prior to to executing echo > none > > /sys/class/leds/status:green:health/trigger . once > I added that to the file it seems to work. This is interestiby bodhi - uBoot
theeleaper, Basically, you need to use partition label for booting, if there is more than one devices attached. See this: http://forum.doozan.com/read.php?3,19093by bodhi - uBoot
wzecke Wrote: ------------------------------------------------------- > Thanks for the reply. > > I did now the above steps on an utbuntu 14.04 x86 > system using kirkwood-pogo_e02.dtb. > Still the same problem as above. > It does not boot from usb. > Any further idea, may be my environment is buggy? If this is what actually in the env, then yes: machid=fffffffby bodhi - Debian
Joey, Look in /usr/share/icons. That's the location of your desktop icons. IIRC, you can also install xfce4-goodies to get the desktop themes. If that's youre looking for. Usually, after install themes, you'll have all kinds of nice icons to choose from. In xfce you can select a specific icon for a shortcut that are on your desktop, or a specific icon for drives/files thaby bodhi - Off-Topic
theeleaper, [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sdd1 rootdelay=30 rootfstype=ext3 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) The reason it is not booting is most likely the root device was set to /dev/sdd1. 1. If you have only this USB drive attached [ 13.684757] scsi 0:0:0:0: Direct-Access PNY USB 2.0 FD 1100 PQ: 0 ANSIby bodhi - uBoot
superelchi Wrote: ------------------------------------------------------- > Sorry. No luck at all. > > Called it with: > $ kwboottool/kwboot -t -B 115200 /dev/ttyUSB0 -b > uboot.2014.07-tld-3.nsa310.uart.kwb > > > Stops after sending the image: > . > . > 92 % > [................................................. > .....................] >by bodhi - Debian
pengu, > but it doesn't start Of course, it will not. I hope I'm making sense above :) QuoteThis u-boot image is for the NSA325, so I expected that it will not execute. We need to build new u-boot to run it properly on this SoC. Next week when I have some time I will attempt building one!by bodhi - Debian
wzecke Wrote: ------------------------------------------------------- > Hello, > > my kernel does not boot. See boot log and the > enviorment. Via boot/uEnv.txt is set the machid to > ffffffff > > any suggestion what to do?f > > Regards, It looks like you did not do this section: 4. Create uImage with embbeded DTB (If this is not first time installatiby bodhi - Debian