pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

eth0 not working anymore

Mon Apr 03, 2017 2:26 am

Hi Friends,

I have had a Pi 3 running as a security camera for a while with no issues. It was running Jessie. This week, I lost connection to it. I tried rebooting but still could not connect. So, I took the Pi down and built a new card with Jessie to see if it was something to do with the software on my camera setup.

With a brand new Jessie build on a new card, I still have the same issue. I have tried the usual suspects like changing ethernet cables and changing power connections. I ran the following commands to ensure I was running the latest stuff:

Code: Select all

sudo apt-get update
sudo apt-get upgrade
sudo rpi-update
Currently, the Pi just has a new card and this keyboard/mouse. Ethernet cable is connected. I am working via Wifi right now which is working just fine.

This is what ifconfig gives me:

Code: Select all

eth0      Link encap:Ethernet  HWaddr b8:27:eb:fd:b3:b7  
          inet addr:169.254.41.166  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: fe80::41a7:ccc8:cc81:1af9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:32 dropped:16 overruns:0 frame:32
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:427 (427.0 B)  TX bytes:10149 (9.9 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:200 errors:0 dropped:0 overruns:0 frame:0
          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:a8:e6:e2  
          inet addr:192.168.4.27  Bcast:192.168.4.255  Mask:255.255.255.0
          inet6 addr: fe80::b221:1c6d:abf3:5209/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6099 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4738 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7874088 (7.5 MiB)  TX bytes:513666 (501.6 KiB)
Address 169.254.41.166 is not a real address on my network. My dhcp server dishes out stuff like 192.168.2.xx. I can't ping that address nor can I ssh to it.

This is what lsusb shows:

Code: Select all

Bus 001 Device 005: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I am kinda stuck. Anybody have ideas on what I can try?

Thanks,
PPi

epoch1970
Posts: 5135
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: eth0 not working anymore

Mon Apr 03, 2017 7:50 am

pumpkinpi wrote:Address 169.254.41.166 is not a real address on my network. My dhcp server dishes out stuff like 192.168.2.xx. I can't ping that address nor can I ssh to it.
This is an ipv4ll address, a class reserved for zeroconf networking. It is defined in addition of the regular network address, normally.

Your DHCP server is not dishing out anything it seems, so the Pi only has the zeroconf IP. Or there is a firewall somewhere that blocks the DHCP negotiation from completing.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

User avatar
DougieLawson
Posts: 39157
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: eth0 not working anymore

Mon Apr 03, 2017 6:18 pm

Start by replacing the cable between RPi and router/switch. You get a link-local IPv4 (169.254.xxx.xxx/16) address when your DHCP server is unreachable. The most likely cause for that is a cable failure. Next most likely is a disabled port on your router/switch (so try rebooting it). Least most likely reason is a faulty Raspberry.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

User avatar
elkberry
Posts: 167
Joined: Wed Dec 28, 2016 9:21 pm

Re: eth0 not working anymore

Mon Apr 03, 2017 6:40 pm

eth0 stats (see above) show a lot of errors and overruns. Either the cable is defective, the opposite port is borked, or the Raspberry Pi got beyond its best-before.
From ZX81 to Raspberry Pi, but wait ... where's the 7805 gone?

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 2:18 am

Thanks for all the replies folks.

I don't think the opposite port is borked {word of the day!} since I tried several ways to connect it to my router (through different switches). Three ways so far (with 3 different cables) and I get no response from my router or internet access from the pi.

From my main desktop, this is the reply I get when I ping my router:

Code: Select all

 $ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.490 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.450 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.563 ms
64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.460 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.326 ms
64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=0.453 ms
64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=0.430 ms
64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=0.546 ms
^C
--- 192.168.2.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 6999ms
rtt min/avg/max/mdev = 0.326/0.464/0.563/0.073 ms
In next post I will show results from pi. Something strange here...

Interesting that there are errors there with the packets. I did not see those.

This Pi has been operational for months with no issues and no rebooting. The DHCP server had a reserved address for it (based on the Mac address) and I have not touched the pi (no updating or changing of config). The DHCP server is working fine for the other 15 - 20 computers in the house. Just this one crapped out and lost connection. Nothing has changed with my internal network setup.

I rebooted my DHCP server (firewall) either way just to see if that was the issue. See next post...

PPi
Last edited by pumpkinpi on Tue Apr 04, 2017 2:32 am, edited 1 time in total.

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 2:26 am

Ok, so this is what I see from the Pi when I ping my router and Wifi turned off on the Pi:

Code: Select all

$ ping 192.168.2.1
connect: Network is unreachable
This is my /etc/network/interfaces file:

Code: Select all

 interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
So, I know it is not the cable and not the switch. I deleted the assigned address for the Pi in my router so it should just be requesting one and getting one when it boots.

I just checked my ifconfig and this is what I see now:

Code: Select all

$ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:fd:b3:b7  
          inet6 addr: fe80::41a7:ccc8:cc81:1af9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:220 errors:0 dropped:0 overruns:0 frame:0
          TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:18196 (17.7 KiB)  TX bytes:18196 (17.7 KiB)
There is no IP address there (Wifi was off).

I am still stumped. Any other files I can show you?

PPi

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 2:31 am

This is what dmesg shows us (not sure if this is helpful):

Code: Select all

$ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.19-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #983 SMP Thu Mar 30 14:46:28 BST 2017
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x36800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 225280
[    0.000000] free_area_init_node: node 0, pgdat 80c6ed80, node_mem_map b603a000
[    0.000000]   Normal zone: 1980 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 225280 pages, LIFO batch:31
[    0.000000] percpu: Embedded 14 pages/cpu @b5ff4000 s25600 r8192 d23552 u57344
[    0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 223300
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 871344K/901120K available (7168K kernel code, 483K rwdata, 2012K rodata, 1024K init, 778K bss, 21584K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xb7800000 - 0xff800000   (1152 MB)
    lowmem  : 0x80000000 - 0xb7000000   ( 880 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80800000   (8160 kB)
      .init : 0x80b00000 - 0x80c00000   (1024 kB)
      .data : 0x80c00000 - 0x80c78f54   ( 484 kB)
       .bss : 0x80c7a000 - 0x80d3cb64   ( 779 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000025] Switching to timer-based delay loop, resolution 52ns
[    0.000325] Console: colour dummy device 80x30
[    0.001216] console [tty1] enabled
[    0.001264] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001333] pid_max: default: 32768 minimum: 301
[    0.001693] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001736] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002756] Disabling cpuset control group subsystem
[    0.002949] CPU: Testing write buffer coherency: ok
[    0.003021] ftrace: allocating 22387 entries in 66 pages
[    0.054618] CPU0: update cpu_capacity 1024
[    0.054681] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.054780] Setting up static identity map for 0x100000 - 0x100034
[    0.057018] CPU1: update cpu_capacity 1024
[    0.057026] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.057750] CPU2: update cpu_capacity 1024
[    0.057757] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.058431] CPU3: update cpu_capacity 1024
[    0.058438] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.058521] Brought up 4 CPUs
[    0.058695] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.058724] CPU: All CPU(s) started in HYP mode.
[    0.058751] CPU: Virtualization extensions available.
[    0.059564] devtmpfs: initialized
[    0.070705] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.071021] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.071083] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.071648] pinctrl core: initialized pinctrl subsystem
[    0.072575] NET: Registered protocol family 16
[    0.074858] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.083695] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.083744] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.083911] Serial: AMBA PL011 UART driver
[    0.085943] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.086493] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.155182] bcm2835-dma 3f007000.dma: DMA legacy API manager at b780f000, dmachans=0x1
[    0.157049] SCSI subsystem initialized
[    0.157239] usbcore: registered new interface driver usbfs
[    0.157341] usbcore: registered new interface driver hub
[    0.157457] usbcore: registered new device driver usb
[    0.164179] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-03-30 14:52
[    0.165590] clocksource: Switched to clocksource arch_sys_counter
[    0.212283] VFS: Disk quotas dquot_6.6.0
[    0.212394] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.212626] FS-Cache: Loaded
[    0.212892] CacheFiles: Loaded
[    0.225149] NET: Registered protocol family 2
[    0.226088] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.226225] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.226436] TCP: Hash tables configured (established 8192 bind 8192)
[    0.226550] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.226617] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.226851] NET: Registered protocol family 1
[    0.227282] RPC: Registered named UNIX socket transport module.
[    0.227315] RPC: Registered udp transport module.
[    0.227343] RPC: Registered tcp transport module.
[    0.227370] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.228351] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.230681] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.246776] FS-Cache: Netfs 'nfs' registered for caching
[    0.247785] NFS: Registering the id_resolver key type
[    0.247841] Key type id_resolver registered
[    0.247870] Key type id_legacy registered
[    0.250308] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.250453] io scheduler noop registered
[    0.250484] io scheduler deadline registered (default)
[    0.250763] io scheduler cfq registered
[    0.256493] BCM2708FB: allocated DMA memory f6910000
[    0.256547] BCM2708FB: allocated DMA channel 0 @ b780f000
[    0.308369] Console: switching to colour frame buffer device 228x61
[    0.338980] bcm2835-rng 3f104000.rng: hwrng registered
[    0.339243] vc-cma: Videocore CMA driver
[    0.339364] vc-cma: vc_cma_base      = 0x00000000
[    0.339504] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.339661] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.340030] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    0.355771] brd: module loaded
[    0.364819] loop: module loaded
[    0.364954] Loading iSCSI transport class v2.0-870.
[    0.365751] usbcore: registered new interface driver smsc95xx
[    0.365940] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.592196] Core Release: 2.80a
[    0.592304] Setting default values for core params
[    0.592471] Finished setting default values for core params
[    0.793027] Using Buffer DMA mode
[    0.793134] Periodic Transfer Interrupt Enhancement - disabled
[    0.793300] Multiprocessor Interrupt Enhancement - disabled
[    0.793464] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.793602] Dedicated Tx FIFOs mode
[    0.794073] WARN::dwc_otg_hcd_init:1053: FIQ DMA bounce buffers: virt = 0xb6904000 dma = 0xf6904000 len=9024
[    0.794369] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[    0.794972] dwc_otg: Microframe scheduler enabled
[    0.795022] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058e0a0
[    0.801852] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058e410 length 36
[    0.808545] WARN::hcd_init_fiq:486: MPHI regs_base at 0xb787a000
[    0.815286] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.822022] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.828890] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.835675] Init: Port Power? op_state=1
[    0.842289] Init: Power Port (0)
[    0.849101] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.855764] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.862466] usb usb1: Product: DWC OTG Controller
[    0.869092] usb usb1: Manufacturer: Linux 4.9.19-v7+ dwc_otg_hcd
[    0.875730] usb usb1: SerialNumber: 3f980000.usb
[    0.883254] hub 1-0:1.0: USB hub found
[    0.889952] hub 1-0:1.0: 1 port detected
[    0.897354] dwc_otg: FIQ enabled
[    0.897359] dwc_otg: NAK holdoff enabled
[    0.897364] dwc_otg: FIQ split-transaction FSM enabled
[    0.897377] Module dwc_common_port init
[    0.897624] usbcore: registered new interface driver usb-storage
[    0.904498] mousedev: PS/2 mouse device common for all mice
[    0.912158] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.919123] bcm2835-cpufreq: min=600000 max=1200000
[    0.926109] sdhci: Secure Digital Host Controller Interface driver
[    0.932771] sdhci: Copyright(c) Pierre Ossman
[    0.939653] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[    0.948669] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.955504] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.969565] ledtrig-cpu: registered to indicate activity on CPUs
[    0.976536] hidraw: raw HID events driver (C) Jiri Kosina
[    0.983580] usbcore: registered new interface driver usbhid
[    0.990401] usbhid: USB HID core driver
[    0.998116] vchiq: vchiq_init_state: slot_zero = 0xb6980000, is_master = 0
[    1.007068] Initializing XFRM netlink socket
[    1.014102] NET: Registered protocol family 17
[    1.021102] Key type dns_resolver registered
[    1.028405] Registering SWP/SWPB emulation handler
[    1.036108] registered taskstats version 1
[    1.043383] vc-sm: Videocore shared memory driver
[    1.050457] [vc_sm_connected_init]: start
[    1.057840] [vc_sm_connected_init]: end - returning 0
[    1.070744] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    1.079643] sdhost: log_buf @ b6907000 (f6907000)
[    1.115717] Indeed it is in host mode hprt0 = 00021501
[    1.205619] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.210371] random: fast init done
[    1.221877] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.228996] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.295744] of_cfs_init
[    1.302931] of_cfs_init: OK
[    1.307421] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.309446] mmc0: new high speed SDHC card at address 59b4
[    1.310189] mmcblk0: mmc0:59b4 USDU1 15.1 GiB
[    1.317179] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.318734] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.320283] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.323076] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.325622] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.325791] Indeed it is in host mode hprt0 = 00001101
[    1.387053]  mmcblk0: p1 p2
[    1.409647] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.416801] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.424631] devtmpfs: mounted
[    1.433501] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[    1.481635] mmc1: new high speed SDIO card at address 0001
[    1.565969] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.573040] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.581120] hub 1-1:1.0: USB hub found
[    1.588265] hub 1-1:1.0: 5 ports detected
[    1.730511] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    1.738309] systemd[1]: Detected architecture 'arm'.
[    1.879477] NET: Registered protocol family 10
[    1.888241] systemd[1]: Inserted module 'ipv6'
[    1.897425] systemd[1]: Set hostname to <luther>.
[    1.925650] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.055967] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.063332] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.075062] smsc95xx v1.0.5
[    2.179707] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:fd:b3:b7
[    2.285648] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    2.298556] systemd[1]: Cannot add dependency job for unit regenerate_ssh_host_keys.service, ignoring: Unit regenerate_ssh_host_keys.service failed to load: No such file or directory.
[    2.310155] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    2.318581] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.326620] systemd[1]: Starting Remote File Systems (Pre).
[    2.343476] systemd[1]: Reached target Remote File Systems (Pre).
[    2.351624] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    2.420902] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c52b
[    2.420911] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.420918] usb 1-1.2: Product: USB Receiver
[    2.420925] usb 1-1.2: Manufacturer: Logitech
[    2.674793] fuse init (API version 7.26)
[    2.680829] i2c /dev entries driver
[    2.725722] usb 1-1.5: new low-speed USB device number 5 using dwc_otg
[    2.873933] usb 1-1.5: New USB device found, idVendor=0b38, idProduct=000e
[    2.881624] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.899634] input: HID 0b38:000e as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:0B38:000E.0004/input/input0
[    2.976647] hid-generic 0003:0B38:000E.0004: input,hidraw0: USB HID v1.11 Keyboard [HID 0b38:000e] on usb-3f980000.usb-1.5/input0
[    2.991123] input: HID 0b38:000e as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:0B38:000E.0005/input/input1
[    3.046029] hid-generic 0003:0B38:000E.0005: input,hidraw1: USB HID v1.11 Device [HID 0b38:000e] on usb-3f980000.usb-1.5/input1
[    3.189119] systemd-udevd[145]: starting version 215
[    3.517457] Driver for 1-wire Dallas network protocol.
[    3.528279] w1-gpio onewire@0: gpio pin 4, external pullup pin -1, parasitic power 0
[    3.528314] w1_add_master_device: set_pullup requires write_byte or touch_bit, disabling
[    3.539528] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    3.842276] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.2/input2
[    3.964930] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.973996] usbcore: registered new interface driver brcmfmac
[    4.040235] input: Logitech M325 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:400A.0006/input/input2
[    4.044807] logitech-hidpp-device 0003:046D:400A.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech M325] on usb-3f980000.usb-1.2:3
[    4.128123] brcmfmac: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[    4.586718] systemd-journald[143]: Received request to flush runtime journal from PID 1
[    5.524592] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    5.524621] brcmfmac: power management disabled
[    6.212824] w1_master_driver w1_bus_master1: w1_search: max_slave_count 64 reached, will continue next search.
[    6.233329] uart-pl011 3f201000.serial: no DMA platform data
[    6.314068] Adding 102396k swap on /var/swap.  Priority:-1 extents:4 across:167932k SSFS
[    6.532939] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[    6.726805] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.727107] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.632625] Bluetooth: Core ver 2.22
[   10.632757] NET: Registered protocol family 31
[   10.632765] Bluetooth: HCI device and connection manager initialized
[   10.634080] Bluetooth: HCI socket layer initialized
[   10.634101] Bluetooth: L2CAP socket layer initialized
[   10.634152] Bluetooth: SCO socket layer initialized
[   10.640952] Bluetooth: HCI UART driver ver 2.3
[   10.640965] Bluetooth: HCI UART protocol H4 registered
[   10.640971] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   10.641164] Bluetooth: HCI UART protocol Broadcom registered
[   10.808426] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.808434] Bluetooth: BNEP filters: protocol multicast
[   10.808448] Bluetooth: BNEP socket layer initialized
[   18.568293] random: crng init done
[   57.056195] w1_master_driver w1_bus_master1: Family 0 for 00.800000000000.8c is not registered.

epoch1970
Posts: 5135
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: eth0 not working anymore

Tue Apr 04, 2017 10:35 am

Curious that even ipv4ll quits now, yet you do have an eth0 interface.
From dmsg I surmise you have a few USB device connected. Perhaps reboot with none of these to see if there is some interaction between eth and the devices?
If there is a firewall *anywhere* (server, Pi, etc.) along the path, check its logs or get rid of it for testing.
If there is a "green" switch along the path, make sure it doesn't disable the port thinking the Pi is not active. I've seen that, and not only with Pis.
Also if available, I would look at the DHCP log on the server. Perhaps the server refuses to give out an address for some reason (but ipv4ll should still work.)
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

mattmiller
Posts: 2243
Joined: Thu Feb 05, 2015 11:25 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 10:46 am

Prob not the culprit but to KISS redo your sd card with latest image but don't run

sudo rpi-update

as that is there for people who like living on the edge :)

I'd actually recommend not even doing apt-get upgrade until the issue of the ethernet not working is resolved - just on the minor off-chance that an update in last 2 days is causing your problem (very unlikely of course)

whitecatboard
Posts: 2
Joined: Tue Apr 04, 2017 4:17 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 4:22 pm

We have some RPI3's working as LoRa gateways on 4 of them eth0 stop working after some time and need to return these boards to the provider, after deinstall the gateway from the roof, etc...

We like to know if this is a general issue or maybe a issue with a batch of boards.
Regards in advance,
Mike

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Tue Apr 04, 2017 11:49 pm

Prob not the culprit but to KISS redo your sd card with latest image but don't run
sudo rpi-update
as that is there for people who like living on the edge
I did try to get a connection with a new install before updating the software but no dice. I may just try it again to make sure.

I'll dig into the other replies and report back.

PPi

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 12:00 am

Ok, so I checked the DHCP logs on the DHCP server and there is no sign of the mac address of the Pi. I see lots of activity from my other machines.

There are no "green" switches in my network.

I have rebooted this thing without USB devices and with USB devices. No difference. No IP address requested or assigned. Obviously, I need to have the USB devices plugged in (keyboard and mouse) to confirm that this is true on the client side, but nothing has appeared in my DHCP logs from this Pi eth0 for the last two days.

I am using a Pi running Openwrt as my Firewall/DHCP server. Have never had any issues with it (many years).

I will try a clean install now.

PPi.

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 12:51 am

Ok, so I built a new card and booted the Pi with no USB interfaces plugged in. Before I did anything, I looked on my DHCP server for any activity of a request for an IP address and there is nothing there at all. I know the mac address of the eth0 and there is no reference to it.

I just plugged in my keyboard and mouse and checked the ifconfig and it shows exactly what it showed before. Nothing for the IP address on eth0.

Unless somebody has other ideas, I am left believing the board went bad like whitecatboard's did.

Thoughts?
PPi

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 1:17 am

Hi PPi,

Please try:

1. Reload the card with the latest Raspbian
2. Disable WLAN interface (based on your information it's currently connected and sending/receiving traffic)
3. Configure eth0 with a static IP address from 192.168.2.0 network
4. Ping the IP address you just assigned to the Pi
5. Try pining your local devices (192.168.2.1 and others)

(Re-)checking/changing the cables also a good idea.

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 1:20 am

buyapidotca wrote:Hi PPi,

Please try:

1. Reload the card with the latest Raspbian
2. Disable WLAN interface (based on your information it's currently connected and sending/receiving traffic)
3. Configure eth0 with a static IP address from 192.168.2.0 network
4. Ping the IP address you just assigned to the Pi
5. Try pining your local devices (192.168.2.1 and others)

(Re-)checking/changing the cables also a good idea.
In the previous post you will see I just did 1 and 2. I have not configured wlan on this new build. I will try #3-5.

I have tried 3 different ethernet cables plugged into 3 different switches on my lan.

Thanks,
PPi

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 1:35 am

Ok, I just did this:
https://www.modmypi.com/blog/how-to-giv ... ess-update

Adding the following in the file (after checking that nothing was using .74):

Code: Select all

interface eth0
static ip_address=192.168.2.74/24
static routers=192.168.2.1
static domain_name_servers=192.168.2.1
And it shows me exactly the same thing after a reboot when I do a if config.

Just for giggles I tried this:

Code: Select all

interface eth0
static ip_address=192.168.2.74/24
static routers=192.168.2.1
static domain_name_servers=8.8.8.8
Then I looked at my DHCP log on my router and there was no activity from b8:27:eb:fd:b3:b7

I tried this from my normal desktop:

Code: Select all

$ ping 192.168.2.74
PING 192.168.2.74 (192.168.2.74) 56(84) bytes of data.
From 192.168.2.60 icmp_seq=1 Destination Host Unreachable
From 192.168.2.60 icmp_seq=2 Destination Host Unreachable
From 192.168.2.60 icmp_seq=3 Destination Host Unreachable
From 192.168.2.60 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.2.74 ping statistics ---
8 packets transmitted, 0 received, +4 errors, 100% packet loss, time 7000ms
pipe 4
From the pi, when I try pinging out, I get "Network is unreachable".

Other ideas?

PPi

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 1:41 am

Ok, I just tried another IP address (.75) and moved the pi {again} to another location and booted. This time the static IP worked and I can ping it.

What is going on?

PPi

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 1:45 am

1. Please post ifconfig after you assign the static IP
2. Please ping that IP address from the Pi

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 1:47 am

Sorry, I was late...

Might be a network (LAN) issue

First thing to check - to make sure the static IP "sticks" and you can ping it from the Pi itself.

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 2:01 am

buyapidotca wrote:1. Please post ifconfig after you assign the static IP
2. Please ping that IP address from the Pi
Ok, so for one (and only one) reboot cycle, I was online with eth0. Then to do what you ask above, I needed to get online from the Pi but I had rebooted already and lost the connection. The ifconfig looked like it should with the 192.168.2.75 IP address assigned. I was able to ping it from my desktop.

But, now I am dead in the water again. I just turned on SSH to see if I can connect that way, but no joy.

.... few minutes later and another reboot ...

Ok, so now I can connect with SSH. This thing is insane. From my ssh terminal, I see this:

Code: Select all

$ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:fd:b3:b7  
          inet addr:192.168.2.75  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::41a7:ccc8:cc81:1af9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:152 errors:0 dropped:4 overruns:0 frame:0
          TX packets:109 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12421 (12.1 KiB)  TX bytes:15287 (14.9 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)
I think you were asking me to ping the pi itself from the pi. If so, this is what I see:

Code: Select all

$ ping 192.168.2.75
PING 192.168.2.75 (192.168.2.75) 56(84) bytes of data.
64 bytes from 192.168.2.75: icmp_seq=1 ttl=64 time=0.137 ms
64 bytes from 192.168.2.75: icmp_seq=2 ttl=64 time=0.097 ms
64 bytes from 192.168.2.75: icmp_seq=3 ttl=64 time=0.046 ms
64 bytes from 192.168.2.75: icmp_seq=4 ttl=64 time=0.082 ms
64 bytes from 192.168.2.75: icmp_seq=5 ttl=64 time=0.106 ms
64 bytes from 192.168.2.75: icmp_seq=6 ttl=64 time=0.056 ms
64 bytes from 192.168.2.75: icmp_seq=7 ttl=64 time=0.104 ms
64 bytes from 192.168.2.75: icmp_seq=8 ttl=64 time=0.092 ms
64 bytes from 192.168.2.75: icmp_seq=9 ttl=64 time=0.050 ms
64 bytes from 192.168.2.75: icmp_seq=10 ttl=64 time=0.098 ms
64 bytes from 192.168.2.75: icmp_seq=11 ttl=64 time=0.109 ms
64 bytes from 192.168.2.75: icmp_seq=12 ttl=64 time=0.051 ms
64 bytes from 192.168.2.75: icmp_seq=13 ttl=64 time=0.083 ms
64 bytes from 192.168.2.75: icmp_seq=14 ttl=64 time=0.095 ms
^C
--- 192.168.2.75 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 12992ms
rtt min/avg/max/mdev = 0.046/0.086/0.137/0.026 ms
Pinging from my desktop, I see this:

Code: Select all

$ ping 192.168.2.75
PING 192.168.2.75 (192.168.2.75) 56(84) bytes of data.
64 bytes from 192.168.2.75: icmp_seq=1 ttl=64 time=0.272 ms
64 bytes from 192.168.2.75: icmp_seq=2 ttl=64 time=0.170 ms
64 bytes from 192.168.2.75: icmp_seq=3 ttl=64 time=0.256 ms
64 bytes from 192.168.2.75: icmp_seq=4 ttl=64 time=0.262 ms
64 bytes from 192.168.2.75: icmp_seq=5 ttl=64 time=0.161 ms
64 bytes from 192.168.2.75: icmp_seq=6 ttl=64 time=0.248 ms
64 bytes from 192.168.2.75: icmp_seq=7 ttl=64 time=0.219 ms
^C
--- 192.168.2.75 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5996ms
rtt min/avg/max/mdev = 0.161/0.226/0.272/0.046 ms
Why is it working then not?

PPi

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 2:08 am

Do you have local/console access the Pi? Is it connected to a monitor and a keyboard?

When you are having the problem I would like to see:

1. ifconfig (after you assign the static IP)
2. pinging the IP address from the Pi itself

When it's working this info is (fortunately) useless :)

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 2:11 am

If you cannot copy/picture this while the PI is offline, then let us know:

1. ifconfig (after you assign the static IP) - does it show the static IP?
2. pinging the IP address from the Pi itself - can you ping the static IP of the Pi (from the Pi itself)?

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 2:14 am

I turned off the static IP address and tried a reboot. I see this on my router:

Code: Select all

Tue Apr  4 22:04:02 2017 daemon.info dnsmasq-dhcp[880]: DHCPDISCOVER(eth0) b8:27:eb:fd:b3:b7 
Tue Apr  4 22:04:02 2017 daemon.info dnsmasq-dhcp[880]: DHCPOFFER(eth0) 192.168.2.33 b8:27:eb:fd:b3:b7 
Tue Apr  4 22:04:07 2017 daemon.info dnsmasq-dhcp[880]: DHCPDISCOVER(eth0) b8:27:eb:fd:b3:b7 
Tue Apr  4 22:04:07 2017 daemon.info dnsmasq-dhcp[880]: DHCPOFFER(eth0) 192.168.2.33 b8:27:eb:fd:b3:b7 
So I tried to SSH into 192.168.2.33 and get "Failed to startup SSH session: No route to host"

So, I flipped back over to the Pi and I see that it has the IP address 169.254.41.166 and there are errors and dropped packets just like there was at the start of my thread.

I am stumped.

Turning the static IP on again.

PPi

buyapidotca
Posts: 17
Joined: Thu Dec 05, 2013 3:16 am

Re: eth0 not working anymore

Wed Apr 05, 2017 2:19 am

You probably shouldn't use DHCP until you confirm the static IP works.

First step would be to make sure the static IP sticks (after reboots) and you can always ping it from the Pi itself. No need to look anywhere else until this is achieved.

pumpkinpi
Posts: 141
Joined: Fri Apr 18, 2014 7:11 pm

Re: eth0 not working anymore

Wed Apr 05, 2017 2:20 am

buyapidotca wrote:If you cannot copy/picture this while the PI is offline, then let us know:

1. ifconfig (after you assign the static IP) - does it show the static IP?
2. pinging the IP address from the Pi itself - can you ping the static IP of the Pi (from the Pi itself)?
Uploading photo. Yes, hard to copy off pi with no internet access.

So, in this picture, it has a static IP, but no internet access. I can't ping it from my desktop.

Image

PPi

Return to “Troubleshooting”