-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network bonding does not work on resinOS for the raspberry pi #812
Comments
@josephroberts I know you narrowed down the problem. Could you add a comment here about your findings? |
@agherzan pretty sure it's just a case of updating the |
agherzan
added a commit
to agherzan/meta-raspberrypi
that referenced
this issue
Sep 14, 2017
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested proved to fix this prolem (see balena-os/meta-balena#812). The version Raspbian is prividing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
agherzan
added a commit
to agherzan/meta-raspberrypi
that referenced
this issue
Sep 14, 2017
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested proved to fix this prolem (see balena-os/meta-balena#812). The version Raspbian is prividing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
agherzan
added a commit
to agherzan/meta-raspberrypi
that referenced
this issue
Sep 14, 2017
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested, proved to fix this problem (see balena-os/meta-balena#812). The version Raspbian is providing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
Will be fixed when balena-os/balena-raspberrypi#121 gets fixed (firmware updated). |
agherzan
added a commit
to agherzan/meta-raspberrypi
that referenced
this issue
Sep 21, 2017
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested, proved to fix this problem (see balena-os/meta-balena#812). The version Raspbian is providing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
agherzan
added a commit
to agherzan/meta-raspberrypi
that referenced
this issue
Oct 2, 2017
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested, proved to fix this problem (see balena-os/meta-balena#812). The version Raspbian is providing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested, proved to fix this problem (see balena-os/meta-balena#812). The version Raspbian is providing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
The version of this firmware provided by linux-firmware is 7.45.41.26. This version seems to have connectivity issues when bonding interfaces. Raspbian included an updated version (7.45.41.46) which tested, proved to fix this problem (see balena-os/meta-balena#812). The version Raspbian is providing is not yet in linux-firmware as they have it directly from Cypress (see RPi-Distro/repo#88). Besides the issue described above, it fixes various other issues including a broadpwn fix. Hopefully this version, or a newer one, will end up in upstream soon. In order to catch when that happens and stop overwriting this firmware, a check is added in the racipe based on the md5sum of the current shipped firmware. In terms of ditribution license, we got an informal one in the github thread mentioned above. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once a network bonding connection has been configued the wlan0 interface constantly changes state between up and down.
the wlan0 interface also does not start correctly on boot
To reproduce, run the following commands from the hostOS and look at the dmesg/journalctl logs
I noticed that the brcmfmac firmware versions are different
resinOS
brcmfmac: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab
Raspbian
brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
This is fixed by copying the contents of
/lib/firmware
from a raspbian image into/resin-rootA/lib/firmware
on a resinOS image. Specifically these files get overwrittenYou can test the bond interface is working correctly with
watch -d -n1 cat /proc/net/bonding/test
The text was updated successfully, but these errors were encountered: