trying to screen to Vocore2

ash
 
Posts: 1
Joined: Fri Jun 09, 2017 10:53 pm

trying to screen to Vocore2

Fri Jun 09, 2017 11:00 pm

Hello,

I am new to Vocore2. I was setting it up and for some reason when i try to use my mac to screen command it through terminal it is giving me an error and will not continue.
My command is as such:
screen /dev/tty.usbmodem_____1

The output i receive is as follows:
[ 6.170000] mtk-sd: MediaTek MT6575 MSDC Driver
te
[ 71.050000] efuse_probe: efuse = 10000002
[ 71.050000] net ra0: Direct firmware load for mt7628.eeprom failed with error -2
[ 71.060000] net ra0: Falling back to user helper
[ 72.040000] br-lan: port 1(eth0.1) entered forwarding state
[ 76.660000] tssi_0_target_pwr_g_band = 35
[ 76.660000] tssi_1_target_pwr_g_band = 35
[ 81.670000] <==== rt28xx_init, Status=0
[ 82.730000] device ra0 entered promiscuous mode
[ 82.740000] br-lan: port 2(ra0) entered forwarding state
[ 82.740000] br-lan: port 2(ra0) entered forwarding state
[ 84.740000] br-lan: port 2(ra0) entered forwarding state

I restarted my device and tried again and getting the below only where it stopped:
[ 6.120000] hub 2-0:1.0: USB hub found
[ 6.120rwarding state
[ 25.390000] br-lan: port 1(eth0.1) entered forwarding state
[ 26.690000] efuse_probe: efuse = 10000002
[ 26.900000] tssi_0_target_pwr_g_band = 35
[ 26.910000] tssi_1_target_pwr_g_band = 35
[ 27.390000] br-lan: port 1(eth0.1) entered forwarding state
[ 28.940000] random: nonblocking pool is initialized
[ 33.250000] <==== rt28xx_init, Status=0
[ 34.100000] device ra0 entered promiscuous mode
[ 34.100000] br-lan: port 2(ra0) entered forwarding state
[ 34.110000] br-lan: port 2(ra0) entered forwarding state
[ 36.110000] br-lan: port 2(ra0) entered forwarding state

please let me know what i am doing wrong and how to make it work.

Thanks,

Vonger
 
Posts: 896
Joined: Sun Oct 19, 2014 6:00 am

Re: trying to screen to Vocore2

Mon Jun 12, 2017 5:04 pm

weird, it is possible to be power issue, try reboot, stopped same position?
If it stops randomly, might be power issue.
Or try to use kermit upgrade the firmware.

Return to VoCore2/Lite/Ultimate

Who is online

Users browsing this forum: No registered users and 40 guests