Re: [Machinekit] Can't install machine kit on Beagle Bone stock image

2018-05-14 Thread Eric 
The exact error message I'm getting after running this command:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 43DDF224

is this:

gpg: keyserver receive failed: No keyserver available

I'm following these instructions from the MachineKit page:

http://www.machinekit.io/docs/getting-started/APT-packages-stretch/

These instructions match the linux distribution I'm using, and the board 
I'm using.

It's probably worth me explaining how I got here:

I was able to successfully install the MachineKit image on my Beaglebone. 
MachineKit fires up just fine. I am not able to get wifi working on the 
MachieKit image however. Since I'm using a Beagelbone wireless, the only 
way to get this board online is through wifi, there's no ethernet port. It 
looks like all the hardware bits are opensource on the BeagleBone wireless, 
including the wifi 
chip: 
http://octavosystems.com/2016/09/27/the-beaglebone-black-wireless-and-beagleboard-compatibility/

Getting wifi up and running on an image I didn't create (and admittedly 
don't fully understand yet) seemed like a pretty hard task. 

So I installed the stock BeagleBone Wireless image on my board and the wifi 
works just fine. According to the machiene kit instructions I linked above, 
not only should I be able to install machinekit from the repository, but I 
should also be able to install the realtime kernel as well. I know this 
might be the harder route to go, but I want to learn how to install Machine 
kit not only on this board, but possibly on some other boards/PCs as I get 
better at this.

So for right now I'd like to get MachineKit up and running on an image 
that's got wifi connectivity. I'm trying both methods just to see what I 
can get to work first... Any help/guidance would be greatly appreciated.

On Monday, May 14, 2018 at 9:56:43 AM UTC-4, Schooner wrote:
>
>
> On 14/05/18 12:39, Eric wrote:
>
> Ahh, ok so that got me farther, but now I'm getting a "no keyserver 
> available" error... 
>
>
> Unless you detail what you did and exactly what the error was, no-one will 
> be able to help
>
> If you search for gpg 'no keyserver available' errors you will see there 
> can be a variety of reasons, from 
> the dirmngr program having problems with the DNS server you use,  to 
> trying to do this behind a proxy.
>
> I think you are going about this all wrong.
>
> Instead of getting your wireless NIC recognised and module and firmware 
> installed for it in the Machinekit image,
> (which incidently we don't produce and queries about it would best 
> addressed to RCN's site where you probably downloaded it from)
> you are now trying to install Machinekit into an image which does not have 
> a RT kernel, so won't run Machinekit as is.
>
> Wifi modules are not built in to kernels normally, they are loaded as 
> required.
> Some of it is non-free and not in distributions for legal reasons, but it 
> is available all the same.
>
> The first action, identify your wifi chipset
> Internet search will 
> find https://www.cyberciti.biz/faq/linux-find-wireless-driver-chipset/ 
> for example
>
>
> On Monday, May 14, 2018 at 1:33:23 AM UTC-4, Bas de Bruijn wrote: 
>>
>>
>>
>> > On 14 May 2018, at 01:29, Eric  wrote: 
>> > 
>> > Ok, so if you've seen my other posts you're probably figuring out that 
>> I'm new to pretty new to Linux. I've fooled around with Pis so I have some 
>> base knowledge, but that's about it. 
>> > 
>> > I'm trying to use a stock BeagleBone wireless image that I'm running. 
>> The image I have on it is this: https://beagleboard.org/latest-images 
>> (Stretch LXQT) 
>> > 
>> > I've been trying to use these commands to install MachineKit: 
>> > 
>> > http://www.machinekit.io/docs/getting-started/APT-packages-stretch/ 
>> > 
>> > I keep getting "failed to start the dirmngr 
>> '/tmp/apt-key-gpdhome.ck58yIIcSL/S.dirmngr' failed: No such file or 
>> directory" 
>> > 
>> > What's going on here? 
>>
>> Use: 
>> Sudo apt update 
>> Sudo apt install dirmngr 
>>
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+...@googlegroups.com .
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Can't install machine kit on Beagle Bone stock image

2018-05-14 Thread 'schoone...@btinternet.com' via Machinekit 

  
  

On 14/05/18 12:39, Eric wrote:


  Ahh, ok so that got me farther, but now I'm
getting a "no keyserver available" error... 
  


Unless you detail what you did and exactly what the error was,
no-one will be able to help

If you search for gpg 'no keyserver available' errors you will see
there can be a variety of reasons, from 
the dirmngr program having problems with the DNS server you use,  to
trying to do this behind a proxy.

I think you are going about this all wrong.

Instead of getting your wireless NIC recognised and module and
firmware installed for it in the Machinekit image,
(which incidently we don't produce and queries about it would best
addressed to RCN's site where you probably downloaded it from)
you are now trying to install Machinekit into an image which does
not have a RT kernel, so won't run Machinekit as is.

Wifi modules are not built in to kernels normally, they are loaded
as required.
Some of it is non-free and not in distributions for legal reasons,
but it is available all the same.

The first action, identify your wifi chipset
Internet search will 
find
https://www.cyberciti.biz/faq/linux-find-wireless-driver-chipset/ 
for example


  
On Monday, May 14, 2018 at 1:33:23 AM UTC-4, Bas de Bruijn
wrote:

  
  
  > On 14 May 2018, at 01:29, Eric 
  wrote:
  
  > 
  > Ok, so if you've seen my other posts you're probably
  figuring out that I'm new to pretty new to Linux. I've fooled
  around with Pis so I have some base knowledge, but that's
  about it.
  
  > 
  > I'm trying to use a stock BeagleBone wireless image that
  I'm running. The image I have on it is this: https://beagleboard.org/latest-images
  (Stretch LXQT)
  
  > 
  > I've been trying to use these commands to install
  MachineKit:
  
  > 
  > http://www.machinekit.io/docs/getting-started/APT-packages-stretch/
  
  > 
  > I keep getting "failed to start the dirmngr
  '/tmp/apt-key-gpdhome.ck58yIIcSL/S.dirmngr' failed: No
  such file or directory"
  
  > 
  > What's going on here?
  
  
  Use:
  
  Sudo apt update
  
  Sudo apt install dirmngr
  

  
  -- 
  website: http://www.machinekit.io
  blog: http://blog.machinekit.io
  github: https://github.com/machinekit
  --- 
  You received this message because you are subscribed to the Google
  Groups "Machinekit" group.
  To unsubscribe from this group and stop receiving emails from it,
  send an email to machinekit+unsubscr...@googlegroups.com.
  Visit this group at https://groups.google.com/group/machinekit.
  For more options, visit https://groups.google.com/d/optout.


  




-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Can't install machine kit on Beagle Bone stock image

2018-05-14 Thread Eric 
Ahh, ok so that got me farther, but now I'm getting a "no keyserver 
available" error... 

On Monday, May 14, 2018 at 1:33:23 AM UTC-4, Bas de Bruijn wrote:
>
>
>
> > On 14 May 2018, at 01:29, Eric  
> wrote: 
> > 
> > Ok, so if you've seen my other posts you're probably figuring out that 
> I'm new to pretty new to Linux. I've fooled around with Pis so I have some 
> base knowledge, but that's about it. 
> > 
> > I'm trying to use a stock BeagleBone wireless image that I'm running. 
> The image I have on it is this: https://beagleboard.org/latest-images 
> (Stretch LXQT) 
> > 
> > I've been trying to use these commands to install MachineKit: 
> > 
> > http://www.machinekit.io/docs/getting-started/APT-packages-stretch/ 
> > 
> > I keep getting "failed to start the dirmngr 
> '/tmp/apt-key-gpdhome.ck58yIIcSL/S.dirmngr' failed: No such file or 
> directory" 
> > 
> > What's going on here? 
>
> Use: 
> Sudo apt update 
> Sudo apt install dirmngr 
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: DE10-DE0-Nano - Invitation to collaborate

2018-05-14 Thread Michael Brown 
Great
Thanks for the feedback.

On Sun, May 13, 2018, 22:36 mugginsac  wrote:

> I could say well it used to work, but the truth is that I forgot that I
> had added another router/switch into my network and I forgot to take that
> into account. Now it is working. Thanks for the help.
>
> Alan
>
> On Wednesday, May 9, 2018 at 4:26:29 PM UTC-7, Michael Brown wrote:
>>
>> Ok. The DHCP fix must be in the updated image.
>> If you are only able to ssh by using the ip address this can be due to
>> DNS server setup on your local lan router.
>>
>>
>> On Thu, May 10, 2018, 00:34 mugginsac  wrote:
>>
>>> I see two addresses. One for the ethernet 10.xx.xx.xx and 127.0.0.1 for
>>> local.
>>>
>>> On Tuesday, May 8, 2018 at 9:02:28 AM UTC-7, Michael Brown wrote:

 Ups forgot reply all:
 Honestly I do not remember and I may have made a typo in the package
 name.
 What matters first is:
 When you run the ifconfig command how many up addresses do you see ?
 ..:-)
 BTW.
 You can also look in the leases list on the DHCP server on your local
 network.

 On Tue, May 8, 2018, 00:02 mugginsac  wrote:

> Michael,
>
> I tried your suggestion but apt reported dhcpcd5 not found. Did you
> take it out before you built the last uSD image?
>
> Thanks,
> Alan
>
> On Sunday, May 6, 2018 at 4:09:36 AM UTC-7, Michael Brown wrote:
>>
>> I found 1 quirk in the image:
>> If you do a ifconfig in the image you will probably see more than 1
>> ip address which gives strange
>>  login behavior. the solution to this is to remove the dhcpcd5
>> package.
>>
>> sudo apt purge dhcpcd5
>>
>>
>>
>>

 --
> website: http://www.machinekit.io blog: http://blog.machinekit.io
> github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Machinekit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/machinekit/BPRQpoyvFm8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> machinekit+...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> website: http://www.machinekit.io blog: http://blog.machinekit.io
>>> github: https://github.com/machinekit
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Machinekit" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/machinekit/BPRQpoyvFm8/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> machinekit+...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/machinekit.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io github:
> https://github.com/machinekit
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Machinekit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/machinekit/BPRQpoyvFm8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.