imfatant / test

64 stars 22 forks source link

Unable to install future #12

Closed 7st4r closed 5 years ago

7st4r commented 5 years ago

Hi i am unable to install future, any idea how i can fix it? Here is the log

debian@beaglebone:~$ sudo pip install future Collecting future Downloading https://files.pythonhosted.org/packages/90/52/e20466b85000a181e1e144fd8305caf2cf475e2f9674e797b222f8105f5f/future-0.17.1.tar.gz (829kB) 100% |################################| 829kB 113kB/s Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/tmp/pip-build-PRquLf/future/setup.py", line 181, in **setup_kwds File "/usr/lib/python2.7/distutils/core.py", line 111, in setup _setup_distribution = dist = klass(attrs) File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/setuptools/dist.py", line 225, in init _Distribution.init(self,attrs) File "/usr/lib/python2.7/distutils/dist.py", line 287, in init self.finalize_options() File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/setuptools/dist.py", line 258, in finalize_options ep.load()(self, ep.name, value) File "/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/pkg_resources.py", line 2065, in load raise ImportError("%r has no %r attribute" % (entry,attr)) ImportError: <module 'setuptools.dist' from '/usr/local/lib/python2.7/dist-packages/distribute-0.6.45-py2.7.egg/setuptools/dist.pyc'> has no 'check_specifier' attribute

----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-PRquLf/future/ debian@beaglebone:~$

imfatant commented 5 years ago

I manually re-checked the whole ArduPilot install from scratch, with no problem. Have you followed the entire guide?

7st4r commented 5 years ago

Jah i did,

These are the challenges I faced.

Would it have been possible to do a youtube version of the install og running process? I know many would have appraciated it.

Best regards


From: imfatant notifications@github.com Sent: Sunday, November 4, 2018 11:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

I manually re-checked the whole ArduPilot install from scratch, with no problem. Have you followed the entire guide?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/imfatant/test/issues/12#issuecomment-435718592, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aqqy0oZpgJRBZrwFSuwD08Mvk7_chbvxks5ur3dagaJpZM4YNNsn.

imfatant commented 5 years ago

Hi,

I've never made a YouTube video before. That would take a bunch of time...

Like I said, I verified the guide completely yesterday. It works perfectly. I don't understand where you are going wrong if you follow it exactly.

The guide is intended as a bare bones installation using a console image, so that there's a minimum or processes running. This makes it easier to see what's going on should one want to look at problems like boot time etc. When you say that you couldn't get the console image to work, what precisely do you mean? Perhaps starting there would be the best approach.

The IoT image already has ArduPilot, so you shouldn't need the guide.

-- Anthony

On Mon, Nov 5, 2018 at 6:43 AM 7st4r notifications@github.com wrote:

Jah i did,

These are the challenges I faced.

  • The console image wouldn't work at all so i hade to use the iot version.

  • Future wouldn't install and as a result waf wouldn't work.

  • I installed it on one occasion to work but didn't have any indication if it was running as it wouldn't connect Qgroundcontroll or APM planer.

Would it have been possible to do a youtube version of the install og running process? I know many would have appraciated it.

Best regards


From: imfatant notifications@github.com Sent: Sunday, November 4, 2018 11:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

I manually re-checked the whole ArduPilot install from scratch, with no problem. Have you followed the entire guide?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/imfatant/test/issues/12#issuecomment-435718592>, or mute the thread< https://github.com/notifications/unsubscribe-auth/Aqqy0oZpgJRBZrwFSuwD08Mvk7_chbvxks5ur3dagaJpZM4YNNsn

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435770222, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af0rmiaB4nL-l3f_XRk4EiwnMa63Oks5ur932gaJpZM4YNNsn .

7st4r commented 5 years ago

I installed the console image on micro sd, tried booting from there. I get Blue LED flashing but i cant connect to the board with ssh or claud9. I tried with IOT image and i was able to connect and follow all the instructions in your giude. I will give it a try this evening again.

Thank you for your respons.


From: imfatant notifications@github.com Sent: Monday, November 5, 2018 1:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

Hi,

I've never made a YouTube video before. That would take a bunch of time...

Like I said, I verified the guide completely yesterday. It works perfectly. I don't understand where you are going wrong if you follow it exactly.

The guide is intended as a bare bones installation using a console image, so that there's a minimum or processes running. This makes it easier to see what's going on should one want to look at problems like boot time etc. When you say that you couldn't get the console image to work, what precisely do you mean? Perhaps starting there would be the best approach.

The IoT image already has ArduPilot, so you shouldn't need the guide.

-- Anthony

On Mon, Nov 5, 2018 at 6:43 AM 7st4r notifications@github.com wrote:

Jah i did,

These are the challenges I faced.

  • The console image wouldn't work at all so i hade to use the iot version.

  • Future wouldn't install and as a result waf wouldn't work.

  • I installed it on one occasion to work but didn't have any indication if it was running as it wouldn't connect Qgroundcontroll or APM planer.

Would it have been possible to do a youtube version of the install og running process? I know many would have appraciated it.

Best regards


From: imfatant notifications@github.com Sent: Sunday, November 4, 2018 11:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

I manually re-checked the whole ArduPilot install from scratch, with no problem. Have you followed the entire guide?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/imfatant/test/issues/12#issuecomment-435718592>, or mute the thread< https://github.com/notifications/unsubscribe-auth/Aqqy0oZpgJRBZrwFSuwD08Mvk7_chbvxks5ur3dagaJpZM4YNNsn

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435770222, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af0rmiaB4nL-l3f_XRk4EiwnMa63Oks5ur932gaJpZM4YNNsn .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/imfatant/test/issues/12#issuecomment-435872365, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aqqy0lDk__X8hXCNO72AF8M5mC28GDm2ks5usDxKgaJpZM4YNNsn.

imfatant commented 5 years ago

What OS are you using? Windows or Linux, and if Linux, which distro?

On Mon, Nov 5, 2018 at 2:00 PM 7st4r notifications@github.com wrote:

I installed the console image on micro sd, tried booting from there. I get Blue LED flashing but i cant connect to the board with ssh or claud9. I tried with IOT image and i was able to connect and follow all the instructions in your giude. I will give it a try this evening again.

Thank you for your respons.


From: imfatant notifications@github.com Sent: Monday, November 5, 2018 1:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

Hi,

I've never made a YouTube video before. That would take a bunch of time...

Like I said, I verified the guide completely yesterday. It works perfectly. I don't understand where you are going wrong if you follow it exactly.

The guide is intended as a bare bones installation using a console image, so that there's a minimum or processes running. This makes it easier to see what's going on should one want to look at problems like boot time etc. When you say that you couldn't get the console image to work, what precisely do you mean? Perhaps starting there would be the best approach.

The IoT image already has ArduPilot, so you shouldn't need the guide.

-- Anthony

On Mon, Nov 5, 2018 at 6:43 AM 7st4r notifications@github.com wrote:

Jah i did,

These are the challenges I faced.

  • The console image wouldn't work at all so i hade to use the iot version.

  • Future wouldn't install and as a result waf wouldn't work.

  • I installed it on one occasion to work but didn't have any indication if it was running as it wouldn't connect Qgroundcontroll or APM planer.

Would it have been possible to do a youtube version of the install og running process? I know many would have appraciated it.

Best regards


From: imfatant notifications@github.com Sent: Sunday, November 4, 2018 11:25 PM To: imfatant/test Cc: 7st4r; Author Subject: Re: [imfatant/test] Unable to install future (#12)

I manually re-checked the whole ArduPilot install from scratch, with no problem. Have you followed the entire guide?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/imfatant/test/issues/12#issuecomment-435718592>, or mute the thread<

https://github.com/notifications/unsubscribe-auth/Aqqy0oZpgJRBZrwFSuwD08Mvk7_chbvxks5ur3dagaJpZM4YNNsn

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435770222, or mute the thread < https://github.com/notifications/unsubscribe-auth/Ac0af0rmiaB4nL-l3f_XRk4EiwnMa63Oks5ur932gaJpZM4YNNsn

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/imfatant/test/issues/12#issuecomment-435872365>, or mute the thread< https://github.com/notifications/unsubscribe-auth/Aqqy0lDk__X8hXCNO72AF8M5mC28GDm2ks5usDxKgaJpZM4YNNsn

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435884688, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0afwPfAU5lXTx6E9RKj5cRV54ezyAAks5usESLgaJpZM4YNNsn .

7st4r commented 5 years ago

I am using Mac so linux i suppose, i used itche to write the image. Not sure if that answered the info you asked?

7st4r commented 5 years ago

So to be able to connect with q ground control do i only needed to

TELEM1="-C /dev/ttyO1" TELEM2="-A udp::14550" GPS="-B /dev/ttyS2"

with my mac wlan ip adress? Or is there any command that can check if the program is running?

imfatant commented 5 years ago

Yes, there's commands to check that ArduPilot is running (ps aux or systemctl), but it's simpler to see if the red LED is flashing on the BBBlue. This means ArduPilot (arducopter, etc) is running. If it's not on, it's not running.

Use:

TELEM1="-C /dev/ttyO1" TELEM2="-A udp::14550" GPS="-B /dev/ttyS2"

Where you replace with your Mac's IP on your local network.

On Mon, Nov 5, 2018 at 4:13 PM 7st4r notifications@github.com wrote:

So to be able to connect with q ground control do i is the only needed stem to edit TELEM1="-C /dev/ttyO1" TELEM2="-A udp::14550" GPS="-B /dev/ttyS2"

with my mac wlan ip adress? Or is there any command that can check if the program is running?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435933698, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0afzXrp-kMFfrjt0e-SCK_2MvtFjU6ks5usGOygaJpZM4YNNsn .

7st4r commented 5 years ago

The red LED isnt flashing

imfatant commented 5 years ago

Then it ain't running.

On Mon, Nov 5, 2018 at 5:52 PM 7st4r notifications@github.com wrote:

The red LED isnt flashing

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435969801, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af5pCxMEP2_FMQgUjVmoX5C0sff2Tks5usHrXgaJpZM4YNNsn .

imfatant commented 5 years ago

And by the way, I do recommend Etcher for creating images.

On Mon, Nov 5, 2018 at 5:55 PM Imf Atant imfatant@gmail.com wrote:

Then it ain't running.

On Mon, Nov 5, 2018 at 5:52 PM 7st4r notifications@github.com wrote:

The red LED isnt flashing

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435969801, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af5pCxMEP2_FMQgUjVmoX5C0sff2Tks5usHrXgaJpZM4YNNsn .

7st4r commented 5 years ago

i just now created an image with etcher on sd card and and trying to reboot from it but i can ssh the board or claod9 it

imfatant commented 5 years ago

I should also say, that departing from the guide, even in tiny ways, is NOT recommended. I wrote the guide because this is is NOT EASY, and many people struggle. Those who have had problems have departed from the guide.

On Mon, Nov 5, 2018 at 5:57 PM Imf Atant imfatant@gmail.com wrote:

And by the way, I do recommend Etcher for creating images.

On Mon, Nov 5, 2018 at 5:55 PM Imf Atant imfatant@gmail.com wrote:

Then it ain't running.

On Mon, Nov 5, 2018 at 5:52 PM 7st4r notifications@github.com wrote:

The red LED isnt flashing

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435969801, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af5pCxMEP2_FMQgUjVmoX5C0sff2Tks5usHrXgaJpZM4YNNsn .

7st4r commented 5 years ago

ok, i guess i should try it all over again

7st4r commented 5 years ago

have you also treid Mirkos method?

imfatant commented 5 years ago

Mirko's method is effectively the same, once you know what you are doing. My method just formalises his.

I am surprised you can't ssh to the BBBlue. You should be able to do that without any problems if you are using the recommended image. I wonder why you are having trouble...

On Mon, Nov 5, 2018 at 6:06 PM 7st4r notifications@github.com wrote:

have you also treid Mirkos method?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435974404, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af25BHqfGN3NYiE1XvZbpC7KDFXJRks5usH4LgaJpZM4YNNsn .

7st4r commented 5 years ago

My suspiction is the board isnt correctly running the console image.

7st4r commented 5 years ago

Its ok with iot image

7st4r commented 5 years ago

ssh debian@10.0.0.10 ssh: connect to host 10.0.0.10 port 22: Operation timed out

imfatant commented 5 years ago

Can I ask why you aren't connecting using ssh debian 192.168.7.2 ?

On Mon, Nov 5, 2018 at 6:26 PM 7st4r notifications@github.com wrote:

ssh debian@10.0.0.10 ssh: connect to host 10.0.0.10 port 22: Operation timed out

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435981585, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af-c7eh04W12vZimpATB5N3xEcuSBks5usILdgaJpZM4YNNsn .

imfatant commented 5 years ago

I mean debian@192.168.7.2

On Mon, Nov 5, 2018 at 6:42 PM Imf Atant imfatant@gmail.com wrote:

Can I ask why you aren't connecting using ssh debian 192.168.7.2 ?

On Mon, Nov 5, 2018 at 6:26 PM 7st4r notifications@github.com wrote:

ssh debian@10.0.0.10 ssh: connect to host 10.0.0.10 port 22: Operation timed out

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435981585, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af-c7eh04W12vZimpATB5N3xEcuSBks5usILdgaJpZM4YNNsn .

7st4r commented 5 years ago

I treid that too

imfatant commented 5 years ago

But why did you use 10.0.0.10? I'm curious. And since we're trying to track down a problem, I must ask..

On Mon, Nov 5, 2018 at 6:47 PM 7st4r notifications@github.com wrote:

I treid that too

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435988946, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af-uGm8f1cGqaRg49bXtrk1TqAMNhks5usIfKgaJpZM4YNNsn .

imfatant commented 5 years ago

Have you installed the Mac drivers? https://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/installing-drivers-mac

On Mon, Nov 5, 2018 at 6:51 PM Imf Atant imfatant@gmail.com wrote:

But why did you use 10.0.0.10? I'm curious. And since we're trying to track down a problem, I must ask..

On Mon, Nov 5, 2018 at 6:47 PM 7st4r notifications@github.com wrote:

I treid that too

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-435988946, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af-uGm8f1cGqaRg49bXtrk1TqAMNhks5usIfKgaJpZM4YNNsn .

7st4r commented 5 years ago

10.0.0.10 is the beaglebone wireless ip adress. I am able to ssh debian with both 10.0.0.10 and 192.168.6.2, but not with 192.168.7.2 in the ito image. In the console image i cant ssh debain with 10.0.0.10, 192.168.7.2 or 192.168.6.2. I was able to install the network driver but not the serial driver.

imfatant commented 5 years ago

I have no experience of using a Mac. However, I would concentrate upon establishing a connection to 192.168.7.2 using the console image. This is the start of the process outlined in the guide. I don't know what else to suggest.

On Wed, Nov 7, 2018 at 3:40 PM 7st4r notifications@github.com wrote:

10.0.0.10 is the beaglebone wireless ip adress. I am able to ssh debian with both 10.0.0.10 and 192.168.6.2, but not with 192.168.7.2 in the ito image. In the console image i cant ssh debain with 10.0.0.10, 192.168.7.2 or 192.168.6.2. I was able to install the network driver but not the serial driver.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imfatant/test/issues/12#issuecomment-436666912, or mute the thread https://github.com/notifications/unsubscribe-auth/Ac0af3u1QyLBCewX10gbLzdWHEteYfaDks5usv8EgaJpZM4YNNsn .

7st4r commented 5 years ago

I understand, I have requasted for a replacement of BBBlue from the retailer as it might be faulty. Like I mentioned i am able to connect with Iot image but not with console image.