need recommendation for a realtime kernel to build for an armhf

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

need recommendation for a realtime kernel to build for an armhf

Gene Heskett-4
Greetings;

I am about to install a stretch on an r-pi-3b. Then let it update to the
latest, with an eye toward a buster update when its released.

But this will be driving a lathe, so it needs the best latency figures
that can be obtained by later linux-rt kernels, prefereably in the
4.19.whatever category.  I have some debs already built that once
installed, should handle that.

Some later:

armhf Stretch is now installed but host file style networking is not
making the transition from local domain to outside network because any
ping to an outside address such as yahoo.com IS NOT coming from the
local domain address, but the avahi-daemon returned address. I my
networking scheme there is no such machine defined anyplace.
Only "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file

A sudo grep -R 169. * returns only those lines I commented out. and
restarted networking each time.

Where the heck is machinename.local, defined as 169.254.x.x coming from,
and more importantly how do I get rid of it once and forever?

ip a shows duplicate inet lines for eth0 and I can't get rid of this one:

   inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
       valid_lft forever preferred_lft forever

ip r returns this:

default dev eth0 proto kernel scope link src 169.254.163.253 metric 202
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.163.253
metric 202
192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12

And obviously I need to make the 3rd line the default.

How do I fix this?

Thanks all.

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Alan Corey
What does just ifconfig (by itself) say?  And route by itself?  What's
your /etc/network/interfaces file like?

I think the 69.254.163.253 is the IP assigned dynamically by your
router.  Or it's your router's IP.  But I think 69.254.163.x is your
outside IP.

I'm not familiar with ip.  Route shows me:
upstairs# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         phone           0.0.0.0         UG    0      0        0 wlan0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.43.0    0.0.0.0         255.255.255.0   U     0      0        0 wlan0
upstairs#

Where phone (in my hosts file as 192.168.43.1) is my default gateway,
I think DHCP ,makes that the default route, maybe I set it manually
(not in a year or more).

You can play with the metric numbers too if you want to assign
priorities.  I'm procrastinating trying to get wifi, dialup and an
ethernet printer working on an XP box.  It thinks the internet is the
printer, it goes nowhere until I disable that interface.

Ah, OK, I cheated and looked it up:
route add default gw {IP-ADDRESS} {INTERFACE-NAME}
from https://www.cyberciti.biz/faq/linux-setup-default-gateway-with-route-command/

You need both "default and "gw" in there.



On 6/15/19, Gene Heskett <[hidden email]> wrote:

> Greetings;
>
> I am about to install a stretch on an r-pi-3b. Then let it update to the
> latest, with an eye toward a buster update when its released.
>
> But this will be driving a lathe, so it needs the best latency figures
> that can be obtained by later linux-rt kernels, prefereably in the
> 4.19.whatever category.  I have some debs already built that once
> installed, should handle that.
>
> Some later:
>
> armhf Stretch is now installed but host file style networking is not
> making the transition from local domain to outside network because any
> ping to an outside address such as yahoo.com IS NOT coming from the
> local domain address, but the avahi-daemon returned address. I my
> networking scheme there is no such machine defined anyplace.
> Only "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file
>
> A sudo grep -R 169. * returns only those lines I commented out. and
> restarted networking each time.
>
> Where the heck is machinename.local, defined as 169.254.x.x coming from,
> and more importantly how do I get rid of it once and forever?
>
> ip a shows duplicate inet lines for eth0 and I can't get rid of this one:
>
>    inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
>        valid_lft forever preferred_lft forever
>
> ip r returns this:
>
> default dev eth0 proto kernel scope link src 169.254.163.253 metric 202
> 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.163.253
> metric 202
> 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12
>
> And obviously I need to make the 3rd line the default.
>
> How do I fix this?
>
> Thanks all.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/gene>
>
>


--
-------------
No, I won't  call it "climate change", do you have a "reality problem"? - AB1JX
Cities are cages built to contain excess people and keep them from
cluttering up nature.
Impeach  Impeach  Impeach  Impeach  Impeach  Impeach  Impeach  Impeach

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

grumpy-2
In reply to this post by Gene Heskett-4
On Sat, 15 Jun 2019, Gene Heskett wrote:

> Greetings;
>
> I am about to install a stretch on an r-pi-3b. Then let it update to the
> latest, with an eye toward a buster update when its released.
>
> But this will be driving a lathe, so it needs the best latency figures
> that can be obtained by later linux-rt kernels, prefereably in the
> 4.19.whatever category.  I have some debs already built that once
> installed, should handle that.
>
> Some later:
>
> armhf Stretch is now installed but host file style networking is not
> making the transition from local domain to outside network because any
> ping to an outside address such as yahoo.com IS NOT coming from the
> local domain address, but the avahi-daemon returned address. I my
> networking scheme there is no such machine defined anyplace.
> Only "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file
>
> A sudo grep -R 169. * returns only those lines I commented out. and
> restarted networking each time.
>
> Where the heck is machinename.local, defined as 169.254.x.x coming from,
> and more importantly how do I get rid of it once and forever?
>
> ip a shows duplicate inet lines for eth0 and I can't get rid of this one:
>
>   inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
>       valid_lft forever preferred_lft forever
>
> ip r returns this:
>
> default dev eth0 proto kernel scope link src 169.254.163.253 metric 202
> 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.163.253
> metric 202
> 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12
>
> And obviously I need to make the 3rd line the default.
>
> How do I fix this?
>

systemctl stop avahi-daemon
systemctl disable avahi-daemon

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Gene Heskett-4
On Saturday 15 June 2019 06:00:10 pm [hidden email] wrote:

> On Sat, 15 Jun 2019, Gene Heskett wrote:
> > Greetings;
> >
> > I am about to install a stretch on an r-pi-3b. Then let it update to
> > the latest, with an eye toward a buster update when its released.
> >
> > But this will be driving a lathe, so it needs the best latency
> > figures that can be obtained by later linux-rt kernels, prefereably
> > in the 4.19.whatever category.  I have some debs already built that
> > once installed, should handle that.
> >
> > Some later:
> >
> > armhf Stretch is now installed but host file style networking is not
> > making the transition from local domain to outside network because
> > any ping to an outside address such as yahoo.com IS NOT coming from
> > the local domain address, but the avahi-daemon returned address. I
> > my networking scheme there is no such machine defined anyplace. Only
> > "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file
> >
> > A sudo grep -R 169. * returns only those lines I commented out. and
> > restarted networking each time.
> >
> > Where the heck is machinename.local, defined as 169.254.x.x coming
> > from, and more importantly how do I get rid of it once and forever?
> >
> > ip a shows duplicate inet lines for eth0 and I can't get rid of this
> > one:
> >
> >   inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
> >       valid_lft forever preferred_lft forever
> >
> > ip r returns this:
> >
> > default dev eth0 proto kernel scope link src 169.254.163.253 metric
> > 202 169.254.0.0/16 dev eth0 proto kernel scope link src
> > 169.254.163.253 metric 202
> > 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12
> >
> > And obviously I need to make the 3rd line the default.
> >
> > How do I fix this?
>
> systemctl stop avahi-daemon
> systemctl disable avahi-daemon
+ a systemctl restart networking.  Had no effect.

ip a:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
    link/ether b8:27:eb:d3:47:2d brd ff:ff:ff:ff:ff:ff
    inet 192.168.71.12/24 brd 192.168.71.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7e94:f0c7:8cec:ce84/64 scope link
       valid_lft forever preferred_lft forever
ip r:
pi@picnc:~ $ ip r
default dev eth0 proto kernel scope link src 169.254.163.253 metric 202
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.163.253
metric 202
192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12

So I'm still confused.

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Gene Heskett-4
In reply to this post by Alan Corey
On Saturday 15 June 2019 04:07:36 pm Alan Corey wrote:

> What does just ifconfig (by itself) say?  And route by itself?  What's
> your /etc/network/interfaces file like?
>
> I think the 69.254.163.253 is the IP assigned dynamically by your
> router.  Or it's your router's IP.  But I think 69.254.163.x is your
> outside IP.
>
Theres a missing 1 in front of the 69's above.  The router ip from this
side is 192.168.71.1, and 149.$$.$$.$$ from the outside world. ping my
web page for it. While there with a browser, note the lcnc uspace builds
of linuxcnc-2.9.0-pre0 for your experimental pleasure on your pi 3b's.  
Works well on my pi when the jessie card is plugged in.

> I'm not familiar with ip.

Get familiar with it Alan, despite our objections, both ifconfig and
route have been expunged from the stretch and newer repo's. I haven't
figured it out either. And the man pages may as well have been written
in swahili or navajo. Even the so-called examples can't be made to work.

> Route shows me:
> upstairs# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref  
> Use Iface default         phone           0.0.0.0         UG    0    
> 0        0 wlan0 192.168.0.0     0.0.0.0         255.255.255.0   U    
> 0      0        0 eth0 192.168.43.0    0.0.0.0         255.255.255.0  
> U     0      0        0 wlan0 upstairs#
>
> Where phone (in my hosts file as 192.168.43.1) is my default gateway,
> I think DHCP ,makes that the default route, maybe I set it manually
> (not in a year or more).
>
> You can play with the metric numbers too if you want to assign
> priorities.  I'm procrastinating trying to get wifi, dialup and an
> ethernet printer working on an XP box.  It thinks the internet is the
> printer, it goes nowhere until I disable that interface.
>
> Ah, OK, I cheated and looked it up:
> route add default gw {IP-ADDRESS} {INTERFACE-NAME}
> from
> https://www.cyberciti.biz/faq/linux-setup-default-gateway-with-route-c
>ommand/
>
> You need both "default and "gw" in there.
>
> On 6/15/19, Gene Heskett <[hidden email]> wrote:
> > Greetings;
> >
> > I am about to install a stretch on an r-pi-3b. Then let it update to
> > the latest, with an eye toward a buster update when its released.
> >
> > But this will be driving a lathe, so it needs the best latency
> > figures that can be obtained by later linux-rt kernels, prefereably
> > in the 4.19.whatever category.  I have some debs already built that
> > once installed, should handle that.
> >
> > Some later:
> >
> > armhf Stretch is now installed but host file style networking is not
> > making the transition from local domain to outside network because
> > any ping to an outside address such as yahoo.com IS NOT coming from
> > the local domain address, but the avahi-daemon returned address. I
> > my networking scheme there is no such machine defined anyplace. Only
> > "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file
> >
> > A sudo grep -R 169. * returns only those lines I commented out. and
> > restarted networking each time.
> >
> > Where the heck is machinename.local, defined as 169.254.x.x coming
> > from, and more importantly how do I get rid of it once and forever?
> >
> > ip a shows duplicate inet lines for eth0 and I can't get rid of this
> > one:
> >
> >    inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
> >        valid_lft forever preferred_lft forever
> >
> > ip r returns this:
> >
> > default dev eth0 proto kernel scope link src 169.254.163.253 metric
> > 202 169.254.0.0/16 dev eth0 proto kernel scope link src
> > 169.254.163.253 metric 202
> > 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12
> >
> > And obviously I need to make the 3rd line the default.
> >
> > How do I fix this?
> >
> > Thanks all.
> >
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > If we desire respect for the law, we must first make the law
> > respectable. - Louis D. Brandeis
> > Genes Web page <http://geneslinuxbox.net:6309/gene>


Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Paul Wise via nm
On Sun, Jun 16, 2019 at 10:52 AM Gene Heskett wrote:

> Get familiar with it Alan, despite our objections, both ifconfig and
> route have been expunged from the stretch and newer repo's. I haven't
> figured it out either. And the man pages may as well have been written
> in swahili or navajo. Even the so-called examples can't be made to work.

The net-tools package is still available:

$ apt-file search --regex 'bin/(ifconfig|route)$'
net-tools: /sbin/ifconfig
net-tools: /sbin/route

--
bye,
pabs

https://wiki.debian.org/PaulWise

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Alan Corey
In reply to this post by Gene Heskett-4
On 6/15/19, Gene Heskett <[hidden email]> wrote:
> On Saturday 15 June 2019 04:07:36 pm Alan Corey wrote:
>

> Get familiar with it Alan, despite our objections, both ifconfig and
> route have been expunged from the stretch and newer repo's. I haven't
> figured it out either. And the man pages may as well have been written
> in swahili or navajo. Even the so-called examples can't be made to work.
-------------

Bah, if that happens I'm going to netbsd.  I'm on the netbsd-arm
mailing list so I see what they're chatting about.  Last time I tried
it the Pi support wasn't very good but that was at least a year ago,
now they're into fancier stuff than I care about.  No real experience
with netbsd but openbsd borrows/steals a lot from them and I used that
for 15 years or so.  Linux gets on my nerves after a while.
Especially everything being deprecated and having to learn a new way
to do something because somebody had a bright idea.  systemctl?  Yuck.
Just let me do it the old way I learned years ago and get out from
underfoot.  Stability is my highest priority, they probably call that
stagnation.

But more stuff compiles under Linux and the BSDs are a little slower
and don't have fancy stuff like realtiime kernels.

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Ian Campbell-5
In reply to this post by Paul Wise via nm
On Sun, 2019-06-16 at 12:11 +0800, Paul Wise wrote:

> On Sun, Jun 16, 2019 at 10:52 AM Gene Heskett wrote:
>
> > Get familiar with it Alan, despite our objections, both ifconfig and
> > route have been expunged from the stretch and newer repo's. I haven't
> > figured it out either. And the man pages may as well have been written
> > in swahili or navajo. Even the so-called examples can't be made to work.
>
> The net-tools package is still available:
>
> $ apt-file search --regex 'bin/(ifconfig|route)$'
> net-tools: /sbin/ifconfig
> net-tools: /sbin/route

Possibly it is no longer part of the base install though? It's hard to
tell, neither of:
        https://packages.debian.org/unstable/net-tools
        https://tracker.debian.org/pkg/net-tools
seem to list the priority.
https://tracker.debian.org/media/packages/n/net-tools/control-1.60git20180626.aebd88e-1
suggests it is "important" but I think there can be overrides to that
from the ftp-master end.

If it really isn't installed by default it might be worth someone[0]
filing a bug against tasksel to ensure it is pulled in by the "standard
Unix system" task? Deprecated or not it certainly seems like it fits
that description.

Ian.

[0] specifically someone who is bothered by its absence and cares to
argue for its inclusion...

Reply | Threaded
Open this post in threaded view
|

Re: need recommendation for a realtime kernel to build for an armhf

Paul Wise via nm
On Wed, Jun 19, 2019 at 5:04 PM Ian Campbell wrote:

> Possibly it is no longer part of the base install though?

Quite likely yes.

> suggests it is "important" but I think there can be overrides to that
> from the ftp-master end.

$ apt-cache show net-tools | grep Priority
Priority: optional

> If it really isn't installed by default it might be worth someone[0]
> filing a bug against tasksel to ensure it is pulled in by the "standard
> Unix system" task? Deprecated or not it certainly seems like it fits
> that description.

IIRC the "standard Unix system" task is determined by package
priority, not by any hardcoded list of packages in tasksel. Between
Debian jessie and stretch, net-tools switched from priority important
to priority optional. I can't see anything in the package changelog
but the change happened in the source package so presumably it was
deliberate.

https://sources.debian.org/src/net-tools/jessie/debian/control
https://sources.debian.org/src/net-tools/stretch/debian/control

--
bye,
pabs

https://wiki.debian.org/PaulWise