[Commotion-discuss] Initial results of installing on unsupported Routerboards

[Andy Gunn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think that makes sense, as long as the file doesn't change very often?

Can we link directly to the proper file on the Downloads page? We can
put a footnote in at the bottom of the MikroTik table that this file
comes from OpenWRT.


On 11/05/2014 11:29 AM, Josh King wrote:
> Sure, I can do that. Though in this case, I think it makes the
> most sense just to remove the netboot image from the downloads page
> and update the documentation to direct them to download it from
> OpenWRT's website, unless you think there's a need to mirror the
> file.
> 
> On 11/05/2014 11:00 AM, Andy Gunn wrote:
>> That makes sense to me Josh. Can you update the website /
>> downloads page with the proper image? I will need to update the
>> installation documentation and test again.
>> 
>> 
>> On 11/05/2014 10:55 AM, Josh King wrote:
>>> It may make sense for us just to update the documentation to 
>>> recommend using the stock netboot image rather than our own. 
>>> Although Commotion can run in 32 MB of RAM, it does make sense
>>> that that amount of memory might not be able to hold the
>>> netboot filesystem, all of its Commotion processes, AND the
>>> install image. Since there's no real reason that the netboot
>>> image has to be Commotion, it could save some trouble.
>> 
>>> On 11/05/2014 10:20 AM, Josh King wrote:
>>>> 
>>>> 
>>>> On 11/04/2014 11:09 AM, Andy Gunn wrote:
>>>>> Hey Adam - thanks for the note about this. We might need
>>>>> to modify our installation instructions for the RB411 - we
>>>>> only have a RB411/AH in house, so we didn't catch that
>>>>> problem. I will make sure to get some vanilla 411 boards to
>>>>> test.
>>>>> 
>>>>> Glad to hear the 433 boards are working. One bug we have 
>>>>> noticed about the MikroTik radio cards is that dual band
>>>>> cards only show 2.4GHz in the Commotion setup wizard. There
>>>>> is an issue in on this: 
>>>>> https://github.com/opentechinstitute/commotion-router/issues/149
>>>>>
>>>>>
>>>>>
>>
>>>>> 
Keep us posted on the MikroTik testing!
>>>>> 
>>>>> 
>>>>> On 11/03/2014 09:30 PM, Adam Steele wrote:
>>>>>> I've spent the evening tinkering around with Commotion
>>>>>> and getting it installed on Mikrotik devices other than
>>>>>> the RB411AH (since I don't own one).
>>>>> 
>>>>>> So far I've tried the RB433, RB433AH and RB411.
>>>>> 
>>>>>> No trouble with the RB433 or RB433AH. Installed and
>>>>>> running. I've not poked around enough to determine
>>>>>> stability but it seems to be all there.
>>>>> 
>>>>>> The RB411 was a bit harder. The issue with the device is
>>>>>> that it only has 32MB of RAM. When trying to install the
>>>>>> usual way it runs out of RAM during the wget2nand
>>>>>> process. The stock
>>>>> 
>>>>>> My work around was to boot the stock OpenWRT image and 
>>>>>> wget2nand from there with the Commotion kernel/rootfs
>>>>>> files. Again, I've not poked around enough to figure out
>>>>>> if Commotion will be stable on only 32MB RAM but I'll
>>>>>> find out and report back.
>>>>> 
>>>>> 
>>>>>> -Adam
>>>>> 
>>>>> 
>>>>> 
>>>>>> _______________________________________________ 
>>>>>> Commotion-discuss mailing list 
>>>>>> Commotion-discuss at lists.chambana.net 
>>>>>> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>>>>>
>>>>>
>>>>>
>>>>>>
>>
>>>>>> 
_______________________________________________
>>>>> Commotion-discuss mailing list 
>>>>> Commotion-discuss at lists.chambana.net 
>>>>> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>>>>>
>>>>
>>
>>
>>
>
>>>>> 
- -- 
Andy Gunn, Field Engineer
Open Technology Institute, New America Foundation
andygunn at opentechinstitute.org | 202-596-3484

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUWlDaAAoJEO7c3Fzx1WU8H1QH/2yN6cFX4bbt6rlitscwGp6W
S7Qj6Blu2pAfuSkSpvi3ThtWf2abTaSeVVNaPzuuRl61w4quUB6k1WXqrd8vXrA/
N8RfBKGEddYbLlVPLmyB1fqgpH8nE7WG0zMi4eu2L9ONY9gM0QUKby/nOLnsCne3
uN82ANXXyd+2JxrgoWlXq/A3sRApjFWBYrfxHA0vmTcVl6ZWOcTokC9OCuSHknCj
jTjDltCzvGEs3txqE9qg9TPGB95iJzku5te/lvTisCNo7mAxrz55CUgoZwWApROt
QQf3n56mp+UDsqBOR4VMPy4rdBqC3mg7MTsqnhA2KdsIpwS4CUarGBVbw9Ekkhw=
=nv8/
-----END PGP SIGNATURE-----