Tinwclouds, I did not see Wifi capability anywhere on that page?by bodhi - Debian
Nope. It does not seems to work booting old mach-types while the Device Tree is enable in the kernel.by bodhi - Debian
I think there must be a wireless chip built in, but disable somehow. The hard part is to find out how to enable it.by bodhi - Debian
@davygravy, Do you have any plan to upgrade uBoot to support Device-Tree? It seems Kurlon has done a lot of works to get device tree for some Kirwood devices into kernel 3.6.x. It would be nice if we can start migrating there to get quite a bit of kernel improvements. I'm going to test kernel 3.6.x to see if we can still boot the old Dockstar, Pogo E02/V4/Mobile and GoFlexHome uBoot.by bodhi - Debian
ingmar_k Wrote: ------------------------------------------------------- > @shv: > As long as the kernel has SATA-support compiled > into it, booting the kernel from NAND, with rootfs > on SATA should work, like with any other SCSI > storage device. > But, I didn't try it yet personally. So, just a > theory of mine, before anyone asks. @shv, I meant what inby bodhi - uBoot
@hyena, I'm not sure I understand. What files did you get on your /boot ? did you get /boot/initrd.img-3.5.0-hyena-iconnect /boot/vmlinuz-3.5.0-hyena-iconnect If you did, then ignore the error, it was caused by flash-kernel, and you don't really need it to automatically generate your uImage and uInitrd.by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Makes me think to move to Raspberry Pi , the > kernel is older on Pogo Pro , several issues with > systemd changes not available for OXNAS You will miss the Gbit Ethernet, if using it to serve files. Also the Raspi needs the connecting USB HDD to provide its own separate power (or any device that draws more powby bodhi - uBoot
varkey Wrote: ------------------------------------------------------- > Ah ok, thanks! blparam, now I remember, its been a > while since I used all that. I knew you've done this before, just need to jog the memory a bit :)by bodhi - Debian
I think dinjo want to boot with 2 or more USB drives. So I suggested if 1 SATA drive connecting to the internal SATA port is used for boot drive instead, then there would be no need (hopefully :) to force it. I've tried playing with uBoot envs a couple times but not successful. Because I think what happened was the kernel image in the stock uBoot kept hanging when it tried to mount rootfby bodhi - uBoot
Varkey, To change envs on the stock uBoot, you would need blparam instead of fw_printenv/fw_setenv. As described in here: Booting Debian with Arch Linux ARM uBoot I have not done this and reserve the existing rootfs, so I can't say. You could nanddump mtd4 in case you need to reflash it back to stock! -bodhiby bodhi - Debian
Hi Varkey, The mtd partitions layout is defined in the original uBoot envs. And can be reset as: # fw_setenv mtdparts 'mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)' # fw_printenv mtdparts mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root) If you know the actual size of the rootfs in mtd4 (for example, 72M) tby bodhi - Debian
Did you try to intall ralink suite? apt-get install firmware-ralinkby bodhi - Debian
If it's bricked, did you try UART booting? see here: http://forum.doozan.com/read.php?3,7852by bodhi - Debian
You will have a pretty good probability that the SATA HDD will get recognized first. Other than that, no other way with this uBoot.by bodhi - uBoot
Varkey, I have not looked closely at the board, like twinclouds perhaps did :) did not see any port/opening for wifi when I open it to plug in the serial console. It would be great if somehow we can hack it!by bodhi - Debian
chessplayer Wrote: ------------------------------------------------------- > I know these two: > Hack247 > A Google+ > contribution 2nd one is WarheadsSE's page.by bodhi - uBoot
Twinclouds got me curious, so I looked at dmesg: <4>[ 8.800000] rtusb init rt2870 ---> <6>[ 8.810000] usbcore: registered new interface driver rt2870by bodhi - Debian
You could use SATA for boot drive in a multiple drive configuration. You don't even have to use Warhead's method to bypass uBoot with SATA, just put the rootfs on a SATA drive in an eSATA enclosure, and connect it with SATA to eSATA cable. The PogoPro is quite easy to open, plug in the cable, route it through the gap at the bottom front.by bodhi - uBoot
restamp Wrote: ------------------------------------------------------- > I see. Thanks syong and bodhi for the > information. The only thing the > "machid=dd6"-knowledgeable kernel buys you is the > ability to control the green LED, right? If this > is the case, I think I'll just wait until wheezy > incorporates the Pogo line. (Heck, most of the > mby bodhi - Debian
Yeah, they mis-labeled these for certain lots of production (I guess, or worse, did it on purpose because for regular customers they all function the same way), and people have discovered that some Pogo Pinks with a particular UPC are really E02 inside.by bodhi - Off-Topic
syong Wrote: ------------------------------------------------------- > bodhi, > > Thank you for your kernel as it works perfectly on > my two e02s for a while now. > > I just wonder why symlink vmlinuz and initird.img > in the last step as I removed them on one of my > e02 and seems does not make any difference. > > Cheers, > > Yong Hi Yong,by bodhi - Debian
syong Wrote: ------------------------------------------------------- > restamp, > > To my understanding, machid=dd6 and the new > arcNumber only work for the kernel that supports > it. > > That kernel is bodhi's 3.2.28-kirkwood-tld. > > So, after dist-updating to wheezy, you might need > to install bodhi's kernel before setting machid > anby bodhi - Debian
The sure way to have a consistent booting PogoPro is to use the Sata port inside.by bodhi - uBoot
The grays one are E02 for sure. Sometine you get unlucky with the pink ones, they turn out to be Oxnas and without wifi.by bodhi - Off-Topic
See this post:http://forum.doozan.com/read.php?2,11601,11627#msg-11627by bodhi - Debian
Dinjo, I don't think we can manipulate the uBoot envs to make the PogoPro choose the correct drive! I've looked, the current uBoot version is too limited.by bodhi - uBoot
lincomatic, I've uploaded this module here: r8712u.ko. Download and copy it to your directory /lib/modules/3.x.x/ (if it was downloaded as r8712.ko.txt then remove the .txt extension). And then run modprobe r8712u If it loads OK and the wifi is activated (iwconfig), then add this modprobe command to your /etc/rc.local so that it will load during kernel booting up. -bodhiby bodhi - Debian
Let's see your output of fw_printenv!by bodhi - Debian
Twinclouds, did you try swapping Tx and Rx?by bodhi - Debian
Dinjo, I have not play with it much. But I planned to take a look at the uBoot envs. Will let you know. Do you have serial console? - bodhiby bodhi - uBoot