RPI 3 B+ No network

[tmm72]

I have a RPI 3 B+ device and imaged the syncloud. It boots to the login screen but never gets a DHCP address and tried to static the eth0 with no change in network status. I am using image syncloud-raspberrypi3-18.03.01-sam.img

[cyberb]

Could you flash it again and then show dmesg output?

[tmm72]

Attached are images of what I see

[cyberb]

Could you run: dmesg | grep eth

Also do you have properly working ethernet cable, network led is green on device? Do you get network working if you flash official raspberry pi image?

[tmm72]

Could you run: dmesg | grep eth Returns blank

Also do you have properly working ethernet cable, network led is green on device? I just get the orange light on the right side by the usb but not on the left

Do you get network working if you flash official raspberry pi image? Yes raspian images work on the device

[cyberb]

What aboit: dmesg | grep netw

[tmm72]

That is unfortunately blank also

[cyberb]

Hmm, hard to say, I do not have B+ yet, but other people have said mage is fine. Could take screenshots of every dmesg page by running dmesg | less and then using page down to skip pages ?

[tmm72]

I have attached the screen shots

[cyberb]

Thanks for the log. Starnge there is no network error log. Looks like network driver either not present or cannot detect the device. Probably it is a problem between Syncloud Jessie image and Raspbian Stretch kernel + drivers we merge together. Maybe it is related to this question; https://raspberrypi.stackexchange.com/questions/81725/raspbian-8-on-raspberry-pi-3-b Could you post dmesg log from working raspbian?

[tmm72]

Here is the dmesg from the pi 3 b+ with 2018-03-13-raspbian-strech.img

putty.log

[cyberb]

Thanks! Could you try this image it is based on lite (not desktop) raspberry pi image. http://artifact.syncloud.org/image/syncloud-raspberrypi3-18.04-sam.img.xz

[lil5]

@cyberb a bit off topic but why is the default build built with raspbian desktop?

Seems a little overkill as there's raspbian-lite.

[cyberb]

Agree, no reason just a mistake. We are not really using any rootfs contents from these images, just extracting kernel, drivers and firmware: https://github.com/syncloud/image/blob/master/tools/extract.sh

[tmm72]

cyberb I tried the 18.04 image and it doesn't even boot so not sure but something is missing

[tmm72]

Flashed with Raspbian Lite and it booted

[tmm72]

Here is the lite dmesg log puttylite.log

[cyberb]

Right, kernel command line is a bit different on lite, fixed (boot, not the network) and re-uploaded. Could you try one more time? http://artifact.syncloud.org/image/syncloud-raspberrypi3-18.04-sam.img.xz

My RPi3B+ is on the way so I hope to test myself in few days.

[cyberb]

Tested on my new 3B+ and it works fine, network is there. Could you test please?

[tmm72]

Well I am having no luck on my end. The network is still not working. It is weird that the network works with the raspbian image but not yours.

[cyberb]

Could you run ifconfig on raspbian?

[tmm72]

Yes and that only returns the "lo" interface

[cyberb]

Could you post it? If it has only lo, how can you connect to it? We are talking about raspbian (non Syncloud)

[tmm72]

Here is from the raspbian image

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.88.249 netmask 255.255.255.0 broadcast 192.168.88.255 inet6 fe80::a072:25d3:a41e:5004 prefixlen 64 scopeid 0x20 ether b8:27:eb:ce:0e:24 txqueuelen 1000 (Ethernet) RX packets 144865 bytes 210455556 (200.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 91814 bytes 8027642 (7.6 MiB) 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 loop txqueuelen 1 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[cyberb]

Just in case, what are you using to write an image? Could you try Etcher with verify mode enabled?

[tmm72]

[tmm72]

Those are the settings that have been set from the beginning

[cyberb]

Is it possible to attach dmesg one more time as a text file from Syncloud image? You can run these commands:

dmesg > /dmesg.log
sync

Then shutdown the board and take SD card to a PC with network and mount its second partition to get this file. I will diff it with my dmesg.

[cyberb]

Here is my dmesg with working network: syncloud.rpib3plus.good.dmesg.log

[tmm72]

Well I think after messing around on another network it is something on my network that is having issues I will have to look into more later

[tmm72]

Narrowed it down to my PiHole on the network blocking web access once I figured. Also I put it on a PI 3 not a plus version. So still haven't figured out my issue with Plus box yet

[Lenny5156]

Will you fix this bug, so it will run on a Raspberry Pi 3B+?

[cyberb]

There is no issue with RPi 3B+, I am sure as use one and we sell as well.

If you have a problem please open a new issue and add more details.