hi bodi thanks for your contributions. Im a novice and maybe this is a dumb question, but.... why can't we install this in a similar manner as the archlinux install. then have the rootfs on a usb drive.

ok well i have the 3.14 kernel and the 3.12 rootfs. everything boots and runs fine except the wifi, I have installed many wifi systems uver the years and my feeling is this instance does not work. Can anyone comment on their experience with this wifi environment. thanks

gp Wrote:
-------------------------------------------------------
> ok well i have the 3.14 kernel and the 3.12
> rootfs. everything boots and runs fine except the
> wifi, I have installed many wifi systems uver the
> years and my feeling is this instance does not
> work. Can anyone comment on their experience with
> this wifi environment. thanks
>
> gp

Do you have rt28xx.dat file in your system somewhere? what do you see when you have auto wlan0 in your /etc/network/interfaces?

ALARM uses a different driver, iirc. If you have serial console, I think you might see error during the time the driver loads the settings. Wireless/ra2 does not seems to be a correct directory. I'm not at home so I can't check my old log for you. You could ask this at Arch site in this thread: http://archlinuxarm.org/forum/viewtopic.php?f=55&t=6193

I just compiled kref's linux-oxnas using Bodhid's .config as base. I added usb audio and a few usb wireless modules.
However I can't use the internal (RT3090) card. With Bodhi's .config it couldn't do a scan (iwconfig just gave me no wireless extensions).
With my .config (based on bodhi's using kernel 3.12.13) it was able to be recognized by iwconfig. However iwlist scan gave me no result.
With an usb wireless dongle I had no problem using wpa_supplicant with my .config (it didn't work with bodhi's).
Attached is my .config for the mentioned 3.12.13 kernel.

thanks so much for your post! I have spent hours and hours trying to make the wifi work and as I suspected it wont. I guess i will just give up on the pogoplug pro..............................................

gp Wrote:
-------------------------------------------------------
> how can that be ??? why would the ar9285 drivers
> be in a pogoplug build???

Any thing you want to use on a Linux computer, if it can be installed hardware-wise, chances is that it will have supports in the kernel. As matter of fact, people usually do just what fsonnlei did to increase wifi performance.

oh man.... i guess i wasnt clear enough. i meant to say "why would the ar9285 drivers be in THIS build". "This build" being the one in the original post and the topic title. I think that is what we are discussing in this thread. I am trying to download the kernel and files system and make my pogoplug wifi work. I don't think i am smart eneough to do my own builds. thanks

Presumably the last row does not violate precondition "4. Be sure there is no bad block in the first 1M of your NAND (check dmesg)." ?

But for all the rest, I see the contradictions highlighted in bold above (also between the various instructions and over time) and I am not sure how to proceed now to update (without risk of bricking) to your latest uboot + Debian (wheezy) kernel (while putting as much as possible into the NAND so as not to depend more than necessary on the USB stick).

P.S. while I have seen you refer to http://projects.doozan.com/uboot/ in http://forum.doozan.com/read.php?3,14,15083#msg-15083 it is not clear to me which versions of uboot are defined as old or new and how this should be checked, as well as whether and which (if any) changes they or the above fw_env require on the Pogo-P24 (currently running "Linux alarm 3.1.10-13-ARCH #1 PREEMPT Mon Aug 20 15:46:18 UTC 2012 armv5tel GNU/Linux" as specified to be installed first in this forum).

Jeff's initial post in that thread being from 2010, I suppose the netconsole could be enabled through his fw_setenvs there for the presently installed uboot already (though you hint at "u-Boot netconsole has been buggy up until the latest u-Boot :) [...] Still, there were reports about intermittent problems with it"), or should http://projects.doozan.com/uboot/install_uboot_mtd0.sh be run even inside Arch first (and does it require or make any changes to the NAND partitioning as seen in bold from the previous post, or render Arch unbootable)?

Either way, is "fw_setenv ipaddr 192.168.1.100" supposed to be the same IP address the Pogoplug is going to use later on for ssh etc., or are there any reasons for using a different one at the uboot stage (where it has to be hardcoded/static for lack of DHCP of course)?