Jean BRUDER Wrote: ------------------------------------------------------- > bodhi Wrote: > > > Jean, use the instruction step 4b. You have > older > > u-boot, so 4a will not work. > > Dear -bodhi, > > Following your last instruction, I upgraded the > u-boot too. I now use your last uboot, and it's > working fine, thanks for that. Anyway,by bodhi - Debian
pengu, This one is very similar to the GoFlex Net (except for the RAM). The source is 2012. I'll see if it can be merged into my build.by bodhi - Debian
Kernel linux-4.1.0-kirkwood-tld-2 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > shure but with working uart .. no problem > I don't need the stock OS so it's ok Not stock OS. I meant the Debian-3.18.5-kirkwood-tld-1 USB rootfs should boot with stock u-boot but you need to change that variable.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > @bobafetthotmail > > I've tried this and the compiled U-Boot seems to > work > > > > U-Boot 2012.10-g8aac38e (Aug 10 2015 - 00:17:17) > DNS-325 > > SoC: Kirkwood 88F6281_A1 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 MiB > In: serialby bodhi - Debian
@Jay, Let me check what are the correct envs. In the mean time, you could list your current envs here. I'll be back.by bodhi - uBoot
jay, > if i install your default env: > stock fw dont start. usb stick (wheezy) starts > fine. This is expected. My default u-boot envs don't care about stock FW! > what set of env should i use? Use my default envs. And then adjust the envs to boot stock. You can merge what Jeff's env has that related to booting stock FW to the current bootcmd. For example pby bodhi - uBoot
pengu, Ah! I saw the default envs you've posted. Set this env and then boot mainlineLinux=yesby bodhi - Debian
pengu Wrote: ------------------------------------------------------- > yes this isn't new to me but I thogut it should be > possible with the stuff here. > but it seems that the stock U-Boot doesn't like > boot the kernel. What's your u-boot envs looks like in serial console, stock u-boot?by bodhi - Debian
Jean BRUDER Wrote: ------------------------------------------------------- > Dear -bodhi, > > Following the thread > http://forum.doozan.com/read.php?2,12096, I > finally achieved in reinstalling my dockstar. But > after following the steps to upgrade to the latest > 4.1 kernel using the "a" option of the point 4, I > got it broken again ... > >by bodhi - Debian
luke10050, > edit: dropped my baud rate to 9600 as my dodgy > unshielded cable says no to 115200. looks like a > working os Cool! pls post your config so I can compare to my current one.by bodhi - Debian
I vaguely remembered something peculiar about baud rate. Have you tried a different one?by bodhi - Debian
It looks like you've actually booted into Debian. The serial console putput is too magled to be sure, though. Try hitting the <Return> key many times to see if you get the Debian prompt. And also you have a network problem. It seems eth0 was not up.by bodhi - Debian
Hi luke10050, > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl > 300) > ata2: SATA link down (SStatus 0 SControl 300) > ata1.00: ATA-8: TOSHIBA MK6465GSXN, GH101M, max > UDMA/100 > ata1.00: 1250263728 sectors, multi 16: LBA48 NCQ > (depth 31/32) > ata1.00: configured for UDMA/100 > done. It is very encouraging! it means that the ACHI driver in the kerneby bodhi - Debian
pratikworld, It's time to search the forum, google,... lot of good information is out there.by bodhi - uBoot
pratikworld, Please read the installation instruction for 3.18.5 again.by bodhi - uBoot
pratikworld Wrote: ------------------------------------------------------- > Hahaha. Thats great ot hear finally. Thanks a lot > for the help, bodhi. > > When ethernet is plugged in the Ethernet LED just > stays on orange. Doesnt even flash. > > Also is it ok to give this error right in the > beginning about failing to set Mac Address? > > >by bodhi - uBoot
bobafetthotmail Wrote: ------------------------------------------------------- > Everything you said has been fixed in the new > uboot. :) > > My script recognizes the NAS so I can add specific > envs for nsa 310, 320 and 325 in the right NAS. I'm going to release new Debian kernel that will fix the network link problems for the 310s, 320s, 320, and 325. So there wilby bodhi - Debian
Shadow128, You can still boot back to the Pogo OS if you remove the USB stick. Is that what you want to do? or really going back to stock all the way? Using dd is not optimal, but if you don't have any bad blocks in NAND then it's probably OK to dd them back. However, the best way to go back to stock is to find an original u-boot and flash it back. When you installed using Jeby bodhi - Off-Topic
pratikworld, Congrats! you've done the installation. Everything seems to work fine. So you can log in through serial console and troubleshoot this network error: > [....] Configuring network interfaces...Internet > Systems Consortium DHCP Client 4.3.1 > Copyright 2004-2014 Internet Systems Consortium. > All rights reserved. > For info, please visit > https://by bodhi - uBoot
pratikworld, There are a few things wrong in both 3.14 and 3.18.5. That was because you stopped the installation toward the end. But it was almost completed, so you got to the point when the kernel has started :) which is not too bad. But let's pick one rootfs to work on to get it booting, shelve the other one. With 3.18.5 rootfs on MMC mounted on the other Linux box. 1. Make sure yby bodhi - uBoot
newhope, It could be some thing you've forgot to do such as changing u-boot envs to boot with DTB-appended uImage. It's hard to say because it could be a lot of things. Best is to watch the boot log in serial console, if you have one already set up. I can tell that you want to build your own Preempt RT kernel? been there :) My advice is if you don't have serial console connecby bodhi - Debian
pratikworld, Everything does look OK, the kernel has been started and running. The problem is the kernel could not mount the rootfs. Please interrupt serial console at countdown and printenv , and post the output here.by bodhi - uBoot
newhope, > and, How can I build my own zImage-4.x.x ? because > I want to make fdt-included uImage. You don't need to build it. It was already built during kernel compilation. linux-4.1/arch/arm/boot/zImage Copy this file and rename to zImage-4.1.x.xby bodhi - Debian
@osa, > regs.hour = bin2bcd(tm->tm_hour) | HT1328_24H_BIT; > in ht1382_rtc_set_time > not regs.hour = bin2bcd(tm->tm_hour); HT1328_24H_BIT constant is not in the kernel code. Did you define it somewhere?by bodhi - Debian
pratikworld Wrote: ------------------------------------------------------- > I tried in Putty as well as Ubuntu. The cursor > stops blinking when I plug in the power. But > nothing happens. There is no log. I checked all > the connectors. They are perfectly in place. > The drivers load fine as well. I can change port > numbers and all. > > Do I have a bad conveby bodhi - uBoot
pratikworld, > Now I also have the CP2102 serial cable soldered > on the board. http://bit.ly/1eY1sOL > > Please guide me how to proceed further. Connect the serial console to your PC running WIndows/OSX/Linux. See varkey setup: http://varkey.in/seagate-goflex-net-serial-connection/ - Plug in the current USB rootfs that you created (whether it's 3.14, 3.16 or 3.18,by bodhi - uBoot
bobafetthotmail, > ...could that be done with GPIO register > modification too like the watchdog (sigh)? What > GPIO number is that? What are you trying to do? (there are multiple subjects in this thread!)by bodhi - Debian
pocket Wrote: ------------------------------------------------------- > bodhi sorry to put other question. > > You made my day now all are ok , tanks again > > can i buy a beer to you > > regards Glad you got everything working :) Hope this exercise has been a good source of references for others looking for info to do the same.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > > > > Did you look at the sys log for clues when this > > happened? > > The only thing I've seen is that the (usb 2 > rootfs) stick is gone and so it isn't possible > anymore to read from the filesystem. You can take this stick to another box and look at it there. And reby bodhi - Debian