I ran it, and I see nothing talking on port 67. I do see some other stuff
but as
soon as I disconnect the wired port the wifi goes down and tcpdump drops
the whole thing reporting the port as closed.
If I do not plug the ethernet cable back in within a few seconds it will
not come
back up either,
>
> Here is the syslog of when I disconnect the RJ-45 connector:
>
> Oct 19 14:09:18 WxPi dhcpcd[464]: eth0: carrier lost
> Oct 19 14:09:18 WxPi rsyslogd-2007: action 'action 17' suspended, next
> retry is Wed Oct 19 14:09:48 2016 [try http://www.rsyslog.com/e/2007 ]
> Oct 19 14:09:18 WxPi kernel:
Woops... I sent the trace to the list, yes it starts up OK as long as the
wired
side is plugged in, If the wired side is not plugged in it will not start
up. With
the mods, now the wired side will at times restart (not always, once it
stops
and refuses to restart you have to reboot) I tried to star
Here is the syslog of when I disconnect the RJ-45 connector:
Oct 19 14:09:18 WxPi dhcpcd[464]: eth0: carrier lost
Oct 19 14:09:18 WxPi rsyslogd-2007: action 'action 17' suspended, next
retry is Wed Oct 19 14:09:48 2016 [try http://www.rsyslog.com/e/2007 ]
Oct 19 14:09:18 WxPi kernel: [ 131.168314
> "Chuck" == Chuck Hast writes:
Chuck> Weird, I did all of that and I am getting the same thing. If I
Chuck> start the RPi it will pull IP's for both eth0 and wlan0, as soon
Chuck> as I unplug eth0 both of them go away.
Chuck> The dhcpcd file has clientid available and duid as #duid so it is
Oh yes, I did a update and upgrade to the RPi, before I did that it was
running
like a champ. Indeed I had upgraded WeeWx on it a while back and did a gen-
eral update/upgrade to every thing back then. So something came down the
pipe that broke this thing and I am not sure what as it has been runni
Weird, I did all of that and I am getting the same thing. If I start the
RPi it will
pull IP's for both eth0 and wlan0, as soon as I unplug eth0 both of them go
away.
The dhcpcd file has clientid available and duid as #duid so it is not
visible. But
looking at the syslog trace it looks like it may
On 10/19/2016 01:57 PM, Dick Steffens wrote:
Sorry about that. Wrong recipient.
--
Regards,
Dick Steffens
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
--
Regards,
Dick Steffens
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
>
> Folks,
> I just did a update to a RPi B+. Before I did the update all was working
> just fine, after doing so I lost my network connection (wifi) I can see the
> interfaces but no IP. I plug in a ethernet cable, but do not see the dhcp
> client pulling an address, I reboot the RPi, and then I g
On Wed, 19 Oct 2016, Robert Citek wrote:
> The 'file' command may be helpful also:
>
> $ file /usr/lib/grub/i386-pc/kernel.img
> /usr/lib/grub/i386-pc/kernel.img: ELF 32-bit LSB executable, Intel
> 80386, version 1 (SYSV), statically linked, stripped
Robert,
As Ben noted, everything in /usr/
On Wed, 19 Oct 2016, Ben Koenig wrote:
> Use the ldd command.
> ldd $BINARY
> Libraries that the specified file links to will be printed to the screen.
> Libraries in /usr/lib are 32bit.
Thanks, Ben. I didn't think of ldd. I think the process is to copy those
to a list and subtract the same p
The 'file' command may be helpful also:
$ file /usr/lib/grub/i386-pc/kernel.img
/usr/lib/grub/i386-pc/kernel.img: ELF 32-bit LSB executable, Intel
80386, version 1 (SYSV), statically linked, stripped
Regards,
- Robert
On Wed, Oct 19, 2016 at 7:55 AM, Ben Koenig wrote:
> Use the ldd command.
>
Use the ldd command.
ldd $BINARY
Libraries that the specified file links to will be printed to the screen.
Libraries in /usr/lib are 32bit.
On Oct 19, 2016 7:50 AM, "Rich Shepard" wrote:
In preparation for replacing my still-reliable 32-bit (AMD Athlon(tm) II
X2 255 Processor) server/workst
In preparation for replacing my still-reliable 32-bit (AMD Athlon(tm) II
X2 255 Processor) server/workstation with a much newer 64-bit word-size host
I would like to identify 32-bit-only applications and tools. Over the past
couple of decades I've installed and used non-distributional (and
non-S
Folks,
I just did a update to a RPi B+. Before I did the update all was working
just fine, after doing so I lost my network connection (wifi) I can see the
interfaces but no IP. I plug in a ethernet cable, but do not see the dhcp
client pulling an address, I reboot the RPi, and then I get addresses
16 matches
Mail list logo