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
Hi everybody, Like million users around the world, I'm using the best media player ever :) But lately, this World News Live plugin (my favorite) has been mostly non-functioning: Forum: XBMC/Kodi World News Live Repo: WNL repository - k3oni WNL repository - moneymaker If anybody who is good with Python, and interested in internet media streaming, please help. I'd really apby bodhi - Off-Topic
pocket, BTW, I think we've covered the kernel/rootfs installation topic at this point. Any other problem/questions, you should start a new Debian thread!by bodhi - Debian
pocket Wrote: ------------------------------------------------------- > bodhi > > i have made new dist-upgrade he found 189 packages > do upgrade after this is recomend to install again > the sysvinit?? > Yes, do this after the first dist-upgrade to jessie. When in doubt, you can do it again, no problem. > i have remove the older kernell and seems to be ok &gby bodhi - Debian
As I've mentioned, the 3.14 and 3.16 rootfs might not work because of missing envs. If you can't get it boot then try 3.18 rootfs. If neither works then serial console will solve it.by bodhi - uBoot
Jean, > But what I really want to do is > to install Debian on my new USB stick, so that I > can have many more space for all the stuffs I > need. What are the steps I need to follow in order > to achieve a working installation of the latest > Debian release on my Dockstar ? The only thing you need to do is to create the USB rootfs following instruction for the versioby bodhi - Debian
pengu, > but there is another problem, wich rises now: > > Is there something wrong with the USB 3.0 port? > > when connecting different usb sticks when running > debian, the rootfs will go away after a while, > only reboot helps ;-( Did you look at the sys log for clues when this happened? I'd not be too surpirsed to see certain USB 3.0 drive cause some kby bodhi - Debian
pocket , Correct. Purge all others but keep the current kernel. > i have update the sources list with the jeesie > sources and have run the command They look OK. But the sysvinit reinstall should be after the dist-upgrade, not before Remember to always check your uImage and uInitrd after massive upgrade like this.by bodhi - Debian
After you're all done, you might want to remove all old kernels so that they won't interfer with future upgrade. dpkg -l | grep linux-image and then use dpkg --purge to purge each one.by bodhi - Debian
Also need to regenerate uImage for 4.1.0, too. Update: no I was mistaken. Look like it is your appended DTB uImage, so it is OK.by bodhi - Debian
You need to regenerate uInitrd for 4.1.0 -rw-r--r-- 1 root root 5409997 Aug 4 23:16 uInitrd -rw-r--r-- 1 root root 5743803 Aug 6 09:44 initrd.img-4.1.0-kirkwood-tld-1by bodhi - Debian
Did you check your initramfs whether it was regenerated? cd /boot ls -lart See if you uInitrd is newer than initramfs. If it is then do a few syncs and reboot. Also doublecheck uImage, it should be newer then vmlinuz.by bodhi - Debian
pocket, > root@debian:/boot# apt-get install sysvinit-core > sysvinit sysvinit-utils You only need to do this after upgrading to jessie.by bodhi - Debian
bobafetthotmail, I've released a new u-boot for NSA325. It solved all little problems that have been nagging us.by bodhi - Debian
pocket, Is the source in /etc/apt/sources.list pointing to jessie now? After apt-get update apt-get dist-upgrade Try apt-get update apt-get install sysvinit-core sysvinit sysvinit-utilsby bodhi - Debian
Good work osa :) I was able to bring the link up fine in the new kernel after a shutdown. I'm going to add either kernel config options (or device tree node parsing) to execute this PHY fixup only in Zyxel boxes with this Ethernet 88E1318/S chip, and then release new kernel version tld-2. Would you like to look into moving it to the PHY subsystem? pls let me know either way!by bodhi - Debian
newhope, You don't need to select anything regarding system type. It's already done in the released config file in the tarball. You can build using the exact same config that I have. And then later, add in whaterver you need using make menuconfig.by bodhi - Debian