VoCore2's are shipping as I write, so here are a couple of things to help users get started with their new toy:
I have put together some prebuilt images with a full set of opkg packages available. There are 4 flavors, Bare VoCore2 with 64 meg ram, VoCore2 with 64 meg ram and sdcard using cd polling, Bare VoCore2 with 128 meg ram, VoCore2 with 128 meg ram and sdcard using cd polling,
If you want to build your own or just see the changes from standard OpenWrt the sources for this image are available on github here. I have made this as close to what I think will come on the production units as I can without actually having one.
This image is based on Chaos Calmer 15.05.01 with Linux kernel 3.18.44, uses the proprietary MTK wifi driver, has Vonger's sound drivers, has all available gpios exported and three uarts functional. The packages are available after you connect the VoCore2 to the internet and run opkg update.
If you load without saving current settings the wifi will be on when it boots up, ssid is vocore2, passkey is 12345678, luci and ssh are available with password vocore. Console is on uart2.
I'll put together detailed instructions on my wiki soon.
Getting Started - VoCore2 Code Repo and Package Repo
- noblepepper
- Posts: 240
- Joined: Sat Nov 29, 2014 3:22 pm
Getting Started - VoCore2 Code Repo and Package Repo
Last edited by noblepepper on Wed Nov 23, 2016 10:53 am, edited 1 time in total.
- exquisitus
- Posts: 3
- Joined: Wed Nov 23, 2016 7:18 am
Re: Getting Started - VoCore2 Code Repo and Package Repo
LEDE? as promised.
- exquisitus
- Posts: 3
- Joined: Wed Nov 23, 2016 7:18 am
Re: Getting Started - VoCore2 Code Repo and Package Repo
LEDE? as promised.
- noblepepper
- Posts: 240
- Joined: Sat Nov 29, 2014 3:22 pm
Re: Getting Started - VoCore2 Code Repo and Package Repo
I haven't prioritized Lede or OpenWrt Designated Driver since they use 4.x series kernels and I don't have a MTK proprietary wifi driver for them. The mt76 wifi driver (open source) they use has varying performance depending on which board (probably which mt7628) you use it on. I have seen performance from pretty good to absolutely abysmal. My second comment on this issue has some numbers on this. This is FAR beyond my expertise so I am just waiting on nbd to have time to work on this.
My Lede github repo works if I remember correctly but no sound drivers and you are rolling the dice on wifi performance. If you want to give it a try make sure you pull the VoCore2 branch.
I plan on submitting patches to get VoCore2 into the official Lede and DD code base but no ETA at this time and until nbd can work on mt76 drivers wifi is not good.
My Lede github repo works if I remember correctly but no sound drivers and you are rolling the dice on wifi performance. If you want to give it a try make sure you pull the VoCore2 branch.
I plan on submitting patches to get VoCore2 into the official Lede and DD code base but no ETA at this time and until nbd can work on mt76 drivers wifi is not good.
- noblepepper
- Posts: 240
- Joined: Sat Nov 29, 2014 3:22 pm
Re: Getting Started - VoCore2 Code Repo and Package Repo
A lede repo is now available. Again there are 4 flavors, Bare VoCore2 with 64 meg ram, VoCore2 with 64 meg ram and sdcard using cd polling, Bare VoCore2 with 128 meg ram, VoCore2 with 128 meg ram and sdcard using cd polling. The source is available on github.
After sysupgrade the AP will be up with SSID VoCore2, passkey 12345678. Password for Luci and SSH is vocore.
Known bug- sysupgrade overwrites any modifications to /etc/config/wireless even if you use -c, I plan on fixing this in the next iteration.
It appears the mt76 wifi driver has improved but the speed is still MUCH slower than the MTK proprietary driver.
You can check the speed you are getting like this, please report any resuslts so we can see how the opensource driver works for everyone:
On your host box:
Then on the VoCore2 after it is connected to internet:
After sysupgrade the AP will be up with SSID VoCore2, passkey 12345678. Password for Luci and SSH is vocore.
Known bug- sysupgrade overwrites any modifications to /etc/config/wireless even if you use -c, I plan on fixing this in the next iteration.
It appears the mt76 wifi driver has improved but the speed is still MUCH slower than the MTK proprietary driver.
You can check the speed you are getting like this, please report any resuslts so we can see how the opensource driver works for everyone:
On your host box:
- Code: Select all
$ sudo apt-get install iperf
$ iperf -s -f m -i 10
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 0.08 MByte (default)
------------------------------------------------------------
Then on the VoCore2 after it is connected to internet:
- Code: Select all
root@vocore2:/# opkg update
Downloading http://noblepepper.com/repositories/lede/0_2/targets/ramips/mt7628/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/vocore2_core.
Downloading http://noblepepp
<snip>
ipsel_24kc/luci/Packages.gz.
Updated list of available packages in /var/opkg-lists/vocore2_luci.
Downloading http://noblepepper.com/repositories/lede/0_2/packages/mipsel_24kc/luci/Packages.sig.
Signature check passed.
root@vocore2:/# opkg install iperf
Installing iperf (2.0.9-1) to root...
Downloading http://noblepepper.com/repositories/lede/0_2/packages/mipsel_24kc/base/iperf_2.0.9-1_mipsel_24kc.ipk.
Installing uclibcxx (0.2.4-3) to root...
Downloading http://noblepepper.com/repositories/lede/0_2/packages/mipsel_24kc/base/uclibcxx_0.2.4-3_mipsel_24kc.ipk.
Installing libpthread (1.1.15-1) to root...
Downloading http://noblepepper.com/repositories/lede/0_2/targets/ramips/mt7628/packages/libpthread_1.1.15-1_mipsel_24kc.ipk.
Configuring uclibcxx.
Configuring libpthread.
Configuring iperf.
root@vocore2:/# iperf -c 192.168.3.211 -f m -t 5
------------------------------------------------------------
Client connecting to 192.168.3.211, TCP port 5001
TCP window size: 0.04 MByte (default)
------------------------------------------------------------
[ 3] local 192.168.3.238 port 51534 connected with 192.168.3.211 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 5.0 sec 12.4 MBytes 20.7 Mbits/sec
root@vocore2:/# iperf -c 192.168.3.211 -f m -t 10
------------------------------------------------------------
Client connecting to 192.168.3.211, TCP port 5001
TCP window size: 0.04 MByte (default)
------------------------------------------------------------
[ 3] local 192.168.3.238 port 51536 connected with 192.168.3.211 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.1 sec 22.0 MBytes 18.3 Mbits/sec
root@vocore2:/# iperf -c 192.168.3.211 -f m -t 80
------------------------------------------------------------
Client connecting to 192.168.3.211, TCP port 5001
TCP window size: 0.04 MByte (default)
------------------------------------------------------------
[ 3] local 192.168.3.238 port 51538 connected with 192.168.3.211 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-80.0 sec 213 MBytes 22.4 Mbits/sec
- strahlermann
- Posts: 11
- Joined: Sun Dec 11, 2016 9:34 am
Re: Getting Started - VoCore2 Code Repo and Package Repo
With openwrt-ramips-mt7628-vocore2-128M-sd-squashfs-sysupgrade.bin I constantly get these messages in terminal:
[ 3804.530000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
[ 3827.250000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
[ 3893.240000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
might be related to this ticket https://dev.openwrt.org/ticket/21834 or maybe an issue with my hardware?
[ 3804.530000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
[ 3827.250000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
[ 3893.240000] msdc-1 -> XXX CMD<0> wait_for_completion timeout ARG<0x00000000> <- msdc_command_resp() : L<1078> PID<kworker/u2:2><0x7ee>
might be related to this ticket https://dev.openwrt.org/ticket/21834 or maybe an issue with my hardware?
- noblepepper
- Posts: 240
- Joined: Sat Nov 29, 2014 3:22 pm
Re: Getting Started - VoCore2 Code Repo and Package Repo
I think we are looking at hardware. Flash vonger's image for the ultimate, if you get the same it is definitely hw.
7 posts
Page 1 of 1
Who is online
Users browsing this forum: Bing [Bot] and 72 guests