Gene. No difference with WiFi on or off. I thought it might have mattered since the Beagle and the PC don't have additional Ethernet. John
> -----Original Message----- > From: Gene Heskett [mailto:ghesk...@shentel.net] > Sent: June-11-21 11:02 AM > To: emc-users@lists.sourceforge.net > Subject: Re: [Emc-users] Pi4 issues with MESA 7i92H > > On Friday 11 June 2021 12:05:38 John Dammeyer wrote: > > > Sam, > > Here's the ifconfig output generated from putty running on my WIN-7 > > workstation via remote desktop from my WIN-10 ZBook. Ethernet cable > > from Pi4 to 7i92 is 2' long. > > > > And with or without LinuxCNC running this is what I get: > > pi@linuxcnc:~ $ cd mesaflash > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid > > lbp16_access.send_packet: Operation not permitted > > Aborted > > > > John > > > > pi@linuxcnc:~ $ ifconfig > > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.1.1 netmask 255.255.255.0 broadcast > > 192.168.1.255 ether dc:a6:32:1e:30:f1 txqueuelen 1000 (Ethernet) > > RX packets 29442387 bytes 2826463726 (2.6 GiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 58886151 bytes 1122489823 (1.0 GiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > > inet 127.0.0.1 netmask 255.0.0.0 > > inet6 ::1 prefixlen 128 scopeid 0x10<host> > > loop txqueuelen 1000 (Local Loopback) > > RX packets 595 bytes 40144 (39.2 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 595 bytes 40144 (39.2 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.0.97 netmask 255.255.255.0 broadcast > > 192.168.0.255 inet6 fe80::9d66:1b85:f539:da50 prefixlen 64 scopeid > > 0x20<link> ether dc:a6:32:1e:30:f2 txqueuelen 1000 (Ethernet) > > RX packets 11119 bytes 3535970 (3.3 MiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 3108 bytes 415864 (406.1 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > I see one possibility, Ralph. > > This doesn't show the default route. But "ip r" will. You are eth0 at > 192.168.1.x and wlan0 at 192.168.0.x. If the default route is thru > wlan0, mesaflash will probably fail. > > I'm using a 7i90 over spi, so my eth0 or whatever name its using this > week is free for normal use, but that's just one of the reasons I keep > the #@%## radios turned off, once avahi gets it in its mind to use the > radio, ip can't or won't fix it, so you have to manually nuke the avahi > executable and reboot. In your case, rename it to rumplestiltskin or > whatever so you can restore it if I'm wrong. > > Take care and stay well. > > [...] > > 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> > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
