Go Down

Topic: Please upgrade your Yún - latest is 1.3 (Read 56319 times) previous topic - next topic

Jantje


Short version foot note: do you want to avoid wasting time? Set up a Debian VM. It's the only way we can be sure everyone has a successful experience with openwrt-yun.
Longer version foot note: compiling openwrt-yun is not difficult but takes patience. It's highly suggested that you strictly follow the instructions (use a debian wheezy, real or running inside virtualbox or kvm, not your own distro) as many different distributions may need specific tweaks that we are unlikely to document since they will be unsupported.

Wouldn't it be a great service/idea to provide a working correctly setup Debian VM from time to time?  8)
I guess there is one floating around and it is just a matter of sharing.
That would save you quite some time on reading/responding on setup issues  :D

Best reagrds
Jantje
Do not PM me a question unless you are prepared to pay for consultancy.
Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

federicofissore

#61
May 16, 2014, 02:28 pm Last Edit: May 16, 2014, 02:32 pm by Federico Fissore Reason: 1
I fear that would transform setup questions into virtualbox questions :)
And debian issues won't be over anyway, since newer packages would require additional prerequisites. It has already happened when we added node packages

noblepepper

#62
May 16, 2014, 03:43 pm Last Edit: May 17, 2014, 03:13 am by noblepepper Reason: 1
@mytrant - you need v8m if you want node.js, if you don't you can disable all the options under Languages->Node.js and then it will let you disable v8m. Or you can work with the 1.0.0 release (see below) which doesn't have node.js, you should end up with something very close to the prebuilt images.

@federico - I might add to your footnote "even then there may be undocumented changes, prepare to learn!"

This brings to light a fact I did not realize even though it is obvious. When you pull from the git https://github.com/arduino/openwrt-yun you get the latest, greatest, PERHAPS buggiest thing available.

If you want to work with the code at a particular point you can use something like
Code: [Select]
git checkout -b release 1.0.0 right after you clone.

To switch back you can use the copy SHA link by the latest commit. At this exact moment in time that would be:
Code: [Select]
git checkout -b f58425387a0ce96bb709489f526dfaf0dae2e1af
git pull origin f58425387a0ce96bb709489f526dfaf0dae2e1af


I would say somebody needs to improve the OpenWrt tutorial on build root, set up  a tutorial on working with things such as debian VM and linino/Yun on a build root in a VM but I learned long ago that it is best to replace "somebody needs to" with "I cheerfully volunteer to" ;-)

federicofissore


This brings to light a fact I did not realize even though it is obvious. When you pull from the git https://github.com/arduino/openwrt-yun you get the latest, greatest, perhaps buggiest thing available.

Wow! Buggiest!
I know (and sadly accepted) that openwrt build sometime fails, but just really sometime. May you elaborate? Why buggiest?

1.0.0 is different from the latest * only in that it downloads the list of packages from another git repo, https://github.com/arduino/openwrt-packages-yun

* and soon to be become 1.1.0 thanks to your run-avrdude fix

federicofissore

Since I suspect the git thing may be the source of trouble, I switched the feeds URL to svn
https://github.com/arduino/openwrt-yun/commit/8ad03f07d3c11ce2eda7d00c152730c20672ba68

mytrant

Federico

Thank you for your instructions and footnote - the comment on using the same base world makes sense.

Having worked with other buildroot worlds, I should have followed all the notes to a 'T'.

OpenWRT has enough different build practices (different - not a normal use of Makefile, not a clear path to rebuild sections...) that adding any new changes is not to be recommended.

Thanks to all for any assistance given on these forums as well, it is a good community to ask questions in.

sonnyyu

#66
May 16, 2014, 10:29 pm Last Edit: Sep 11, 2015, 02:19 pm by sonnyyu Reason: 1
Using  hypervisor compare with bear metal will lost % performance, and different type hypervisor will be vary.
Worst case you got hit by 80%



http://en.wikipedia.org/wiki/Hypervisor

VMware Workstation and VirtualBox is type 2 hypervisor will be suffer more than type 1 hypervisor.

OpenVZ might be best fit: it does not have the overhead of a true hypervisor, it is very fast and efficient. The disadvantage with this approach is the single kernel. All guests must function with the same kernel version that the host uses. My personal experience only lost 5~10%.

http://en.wikipedia.org/wiki/OpenVZ



mytrant

Oddly enough am now timewasting....

installed Virtualbox, Debian Wheezy and went to run the following:
Code: [Select]

apt-get install git subversion build-essential asciidoc \
    fastjar flex gawk libgtk2.0-dev intltool zlib1g-dev \
    genisoimage libncurses5-dev libssl-dev ruby sdcc unzip \
    bison libboost-dev libxml-parser-perl libusb-dev bin86 \
    bcc sharutils openjdk-7-jdk mercurial cvs bzr npm


Got the result:
Code: [Select]

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: unable to locate package npm


Any thoughts on an attempt to build openwrt-yun on the same world?

noblepepper

While I agree with Federico that using the standard build environment will eliminate many problems, I have had a good experience with Ubuntu. I do have to Google occasionally to find the source of an error but I avoid learning vm's and relearning Debian dogma. I am on the last 13.?? Ubuntu but I expect 14.04 won't be too much trouble.

noblepepper


Wow! Buggiest!
I know (and sadly accepted) that openwrt build sometime fails, but just really sometime. May you elaborate? Why buggiest?

Because it is the latest and greatest! It's the nature of the beast. If you want to be on the bleeding edge you need to be prepared for some issues.

While I envy some of the things you get play with, some of the comments I have seen make me hope you wear asbestos underwear. I am extremely impressed with the yun and what the team has put together.

I also added some emphasis to the perhaps in the original post, it's not ALWAYS the buggiest.

Jantje



Wow! Buggiest!
I know (and sadly accepted) that openwrt build sometime fails, but just really sometime. May you elaborate? Why buggiest?

Because it is the latest and greatest! It's the nature of the beast. If you want to be on the bleeding edge you need to be prepared for some issues.

While I envy some of the things you get play with, some of the comments I have seen make me hope you wear asbestos underwear. I am extremely impressed with the yun and what the team has put together.

I also added some emphasis to the perhaps in the original post, it's not ALWAYS the buggiest.

For the record:
I understood your "perhaps buggiest" remark as "latest and greatest". There is no way to guarantee "regressionless progress".
Best regards
Jantje
Do not PM me a question unless you are prepared to pay for consultancy.
Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

federicofissore


Got the result:
Code: [Select]

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: unable to locate package npm



mytrant, you're absolutely right! I've been fooled by the differences between debian and ubuntu once more.
I've changed the prerequisites section replacing apt-get with a script that does the first setup.

I'm running a build with a fresh debian just now. If everything goes well, I'll report later tomorrow evening

federicofissore


rmagnus

Guys, I want  to report that I tested the bridge using fileio with the downgraded opwnwrt and a 145 kilobyte text file and it worked perfect :)

@Federico: 

1) so without adding any resistors to the yun, what is the best way to know that the linux side has finished booting?
2) has the speed of the bridge been improved in anyway? If not, how can it be?

THANK YOU

Sincerely

Rodolfo Magnus


Jantje


2) has the speed of the bridge been improved in anyway? If not, how can it be?

you kind of like went from windows 7(linino) to xp(openwrt). how can it not be it is faster?
Best regards
Jantje
Do not PM me a question unless you are prepared to pay for consultancy.
Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

Go Up