-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to LEDE 17.01.1 and Node 6.10.3 #72
base: master
Are you sure you want to change the base?
Conversation
SSH password auth is disabled, but LEDE stil complains about it.
@kevinmehall this is amazing !! |
Sorry, did not mean to change the review state at all. I have no idea how to undo the review request from @jiahuang. Sorry for the noise :( |
I'm really excited about this :) |
Me too, me too : ^ ) |
--shared-zlib \ | ||
--shared-openssl \ | ||
--prefix=/usr \ | ||
--with-intl=none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This will take a bit of time, but shouldn't be problematic. cc @reconbot |
Here's how I confirmed this build:
|
The existing binaries are only key on node version, not toolchain version. We'll need to make another breaking change with the urls. We'll also want to consider supporting the newer and older tool chains. All doable. Do we have a a concept of "version" for the Tessel OS? That might make sense tracking in package releases. |
Due to firewall ? At Ubuntu, I need to allow Tessel IP address for all ports. Dont know which one for mdns. |
@huseyinkozan ah, it's very possible that something is amiss with the network at this office... I heard through the grapevine here that there has been configuration problems. I will try again from another network as soon as I get out from under this test262 work that I'm doing |
I'm on a different, but very reliable network today and I'm noticing that Tessel 2 with LEDE is dropping the connection a lot |
Check this out... (The Tessel with LEDE)
Compared to: (The Tessel with OpenWrt)
Notice the bitrate discrepancy? LEDE @ 6500 vs OpenWrt @ 57800 Honestly, I know very little about network device admin, so that might be meaningless. |
And... just as I posted that, I saw this go by:
(I'm connected to the board via serial) And now...
|
@rwaldron Maybe |
@huseyinkozan will do... I had a meeting I had to jump into |
@rwaldron And other, maybe not related bugs : |
FWIW, there have been several deauthentications since I posted that pastebin https://pastebin.com/UVnYreNR |
Nope
I'll have a look, thanks |
Dont know but can this be the problem Ok. Good luck |
No, I'm not running anything with node at the moment, I'm just watching the serial dmesg logs go by I also found this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992 |
Any progress ? |
@huseyinkozan until there's a solution to the network deauth'ing issue, this can't move forward (which is really disappointing) |
I've done some long-running tests where I simply connect my Tessel 2 w/ Lede to a network and monitor the connection over long periods of time. I'm not seeing the deauth issue now, but the bitrates are still much lower than the Tessel 2 w/ Openwrt |
This build may break existing LED functionality (the 4 connected to OpenWRT). I put this build on a board and I could no longer control any of the LEDs through the JavaScript API. It may be just a beaten up T2 though so someone else should confirm. |
I am trying to build node with inspector support, but getting the error below. To enable inspector I needed to enable icu support (https://github.com/nodejs/node/blob/v6.x/configure#L1291). I found this : https://github.com/openwrt/packages/tree/master/libs/icu and successfully built with It seems uClibc is causing this. After some digging, could not find a patch for this error. Any idea ?
|
LEDE is a fork of OpenWrt. The projects may soon re-merge.
This updates the kernel and all software, so all functionality should be thoroughly tested.
The updated LEDE patches have moved to the tessel/lede repo. We should get some of these into upstream LEDE.
Depends on Fixes for LEDE upgrade t2-firmware#234 (Note: This PR bumps the t2-firmware dependency version, which also brings in other t2-firmware changes)
I disabled the bootloader (uboot) build, since it fails to compile with the updated toolchain; I did not investigate. uboot is only needed for factory install or
t2 restore
, and you can use the existing binaries.LEDE switches the libc to musl, which fixes the issues we had with Node on uclibc. This also makes it simpler to build Rust programs, as
mipsel-unknown-linux-musl
is available throughrustup target add mipsel-unknown-linux-musl
, instead of needing to build libstd.The Node binary package builds will need to be updated to use the SDK with the updated toolchain.
Test build: Sysupgrade | SDK