wacke, > I found the barebox project,is there anyway to get > the marvell sdk?I want to get the armada 370 soc w > ith 88e6171 switch working on barebox. > I also found this project: https://github.com/Marv > ellEmbeddedProcessors/u-boot-marvell,is there have > the switch driver? I've looked into the u-boot 88e6171 switch driver before for the EA4500, and stoppedby bodhi - Debian
fortis91, Quote> A couple interesting lines: > [ 0.160991] : /ocp@f1000000/ethe > rnet-controller@72000/ethernet0-port@0: local-mac- > address is not set This is OK, it's normal. Quote[ 0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 [ 0.000000] CPU: Feroceon 88FR131by bodhi - uBoot
This is the chip: QuoteNetwork:88E6161 Switch chip with 5 gigabit port,88E1116 with 1 gigabit aux portby bodhi - Debian
Nirmal_Kumar Wrote: ------------------------------------------------------- > Thanks Bodhi. > > While flashing the UBoot in Pogo V4, i am getting > an error in the SSH, can't fork. How to resolve th > is? I need to see the log of the teminal session to know what error you have encountered. Please post the log of how you flash u-boot.by bodhi - uBoot
fortis91 Wrote: ------------------------------------------------------- > In the process of recreating rootfs and capturing > some logs. I did see some activity from the router > port with a Debian rootfs I created but the USB ma > y have been bad, so using another one. > > Also can't boot without USB so nand be be corrupt? > > U-Boot 2011.12 (Feb 12 2012 -by bodhi - uBoot
youxiaojie, This box uses a different ethernet chip, unlike other Kirkwood boxes. I did not have time to look into building new uboot for it. It would be time quite consuming for me to start this project.by bodhi - Debian
WMLex, 1. Make sure you followed the instruction to create the Debian 4.4 rootfs very closely (being root, label the partion name as rootfs, single ext3 partition...). 2. If after verifying the rootfs creation, it still got stuck as above, try using a different thumb drive.by bodhi - Debian
fortis91, > > For the complete serial console log, I'm kind of n > ew to this but I did use ubuntu terminal(screen /d > ev/ttyUSB0 115200) to capture the logs but I had t > o copy and paste as it scroll. Is there a way to r > edirect the logs? I did see instructions to use pu > tty on windows to save the logs, I'll try that whe > n I get home today. Iby bodhi - uBoot
WMLex, > I did not create anything, I downloaded uImage and > uInitrd. Ah! I see that you're not familiar with kernel installtion procedure. The full GNU/Linux system includes a rootfs and a kernel installed on that rootfs. The USB partition that you're booting with must contain a rootfs. And then it's up to you to install a kernel to run inside that rootfs. Or ifby bodhi - Debian
Thanks twinclouds!by bodhi - Off-Topic
WMLex, > Image Name: debian-installer ramdisk > Created: 2017-04-07 19:08:13 UTC > Image Type: ARM Linux RAMDisk Image (gzip com > pressed) > Data Size: 11680416 Bytes = 11.1 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... Bad Data CRC > Ramdisk image is corrupt or invalid This problem usually is not because of tby bodhi - Debian
fortis91, > I'm running an old uboot: > U-Boot 2011.12 (Feb 12 2012 - 21:33:07) > Seagate FreeAgent DockStar > This u-boot is old, but should work perfectly! > ethaddr=xx:xx:xx:xx:xx:xx > arcNumber=2097 And this arcNumber is OK for a Dockstar, the ethaddr shoudlcontain valid numbers, but I take it that you've blanked out for privacy. So u-boot is nby bodhi - uBoot
feas Wrote: ------------------------------------------------------- > Thanks, > > Was just looking to read the RC release notes. I f > ollow a few items to try and learn more about the > kernel. > > It was frustrating cause all the check if down sit > es I tried said it was up. Makes me wonder what th > e issue is being it has been down for a few days f >by bodhi - Off-Topic
Yes it is amazing looking at the all the forks :) It's free only if everybody in some whichever way contributes a little to keep it that way.by bodhi - Off-Topic
Twinclouds, > I am thinking about first to write a bare-bone sty > le how-to on setup a Asterisk-13 server for Google > Voice. Then a follow up on how to implement Oauth > -2.0 based on other people's work at the DSLReport > /VOIP Tech Chat Forum. Hope there's some interest > here. That would be cool :)by bodhi - Off-Topic
> "memtester" is running fine so this isn't memory r > elated .. perhaps something in the "coherency" sto > ff is going wrong .. Was there a new Ext4 partition in the box when you ran localgen?by bodhi - Debian
> those of us on meds. Been there, done that:)by bodhi - Debian
Jörg, > my Pogo is running on latest debian :-). Everythin > g fine. Cool! glad to hear.by bodhi - uBoot
pengu, > > ethtool -s eth0 wol g > Cannot set new wake-on-lan settings: Operation not > supported > not setting wol That meant you have not applied all the patches. Have you tried running kernel 4.10.9-mvebu-tld-1? > but this new kernel and patch fixes another issue: > > He tried the new uploaded kernel and now it's work > ing as it should. Cooby bodhi - Debian
ming Wrote: ------------------------------------------------------- > cat /proc/mtd > > root@PogoPlug:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00040000 00020000 "stage1" > mtd1: 00160000 00020000 "u-boot" > mtd2: 00040000 00020000 "u-boot-env" > mtd3: 02000000 00020000 "boot" > mtd4: 00020000 00020000 &by bodhi - uBoot
Nirmal_Kumar, Quote1.Uboot Script : Does this script http://projects.doozan.com/uboot will pick up the latest Uboot No, it will install Jeff/davygravy older u-boot. Quoteshould i need to use a different Url. Because bodhi has mentioned to use the latest uBoot package for a better Modern NAS support Currently, the procedure to install new u-boot for Pogo V4 is a manual procedure: httpby bodhi - uBoot
nielsek Wrote: ------------------------------------------------------- > Quotebodhi > At the moment, I think the MAC address stored in t > he NIC itself is the problem (or one of the proble > ms) with WOL. > > I was thinking the same. There's no way how to fi > nd out what is the address and test then? There are several MAC addresses defined in u-boot env. Perby bodhi - Debian
JT, I think you're ritght. The drive itself is failing. After back up this rootfs, you could try an experiment: not replacing uInitrd but rename it to some other name to keep it in place. And create a new uInitrd file, that way it will allocate different disk sectors.by bodhi - Debian
JT, Verifying Checksum ... Bad Data CRC This error usually is the uInitrd was corrpupted (not u-boot). It could be the rootfs file system was corrupted or the uInitrd file itself was corrupted. Have you tried to fsck this USB drive offline using another Linux box? If that does not help, try regenerate uInitrd using mkimage command. And always do a sync after regenerating it.by bodhi - Debian
> Oh'well better go check that I didn't take my meds > twice today and hide my truck keys. ;) Could be :) the kernel upgrade should not affect any of the most customized system scripts such as /etc/network/interfaces.by bodhi - Debian
Hi feas, > Note: It did change the nc server and my ip addres > s but I did a fw_printenv after the first part of > 4a and caught it before rebooting. You meant when you installed u-boot 2016.5-tld-1 at the same time as upgrading the latest kernel? Because kernel installation does not touch u-boot envs for nc server and ip address.by bodhi - Debian
protocold Wrote: ------------------------------------------------------- > But I wasnt planning to use Arch's uboot.. so wher > e should I start? Arch u-boot and my build is almost identical (came from mainline, with some extra patches). Their envs will work the same way. What you can do is to see how their envs are setup for booting UBIFS rootfs on mtd1 and use those. In anyby bodhi - uBoot
WMLex, I have only provided installation instruction from stock OS. Try booting into stock OS and install from there. Not a lot of people have this device, so nobody has remined me to write section B :) It is possible, I just need to refresh my memory again and write it. QuoteA. Installation from stock OS Prerequisites The Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs mby bodhi - Debian
youxiaojie, > 想要使用 fw_printenv 命令的同学 可以新建一个/etc/fw_env.config文件, > 内容如下: > # MTD_device_name Device_offset Env._size Flash_se > ctor_size Number_of_sectors > /dev/mtd0 0xbc000 0x20000 0x4000 0x8 > > from 0xbc000 to 0xdbfff 128k Byte Is there a question you want to ask?by bodhi - Debian
Quoteok. So technically I can mess up anything after the first 1MB and I should still be OK to fix it up?! Exactly. mtd partitions definition is whatever you want it to be. As long as you keep mtd0 (first 1MB) untouched, the rest could be defined using any layout you want to. QuoteI think moonman's procedure rely on arch uboot and not yours.. There was no mention of changes to env at alby bodhi - uBoot