# High packet loss in simple system **URL:** \ **Category:** BotBlox Hardware\ **Tags:** ubiswitch\ **Created:** [November 27, 2024, 8:38am UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353 "2024-11-27T08:38:28Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![peci1](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/peci1/32/32_2.png) [@peci1](https://forum.botblox.org/u/peci1)\ **Post date:** [November 28, 2024, 11:25am UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/22 "2024-11-28T11:25:45Z")
Hmm, what about EEE kicking in? (Energy Efficient Ethernet). Please do on both the PC and RPi: ``` ethtool --show-eee eth0 # or whatever your interface is ``` If you find it turned on, try disabling it: ``` sudo ethtool --set-eee eth0 eee off ``` ---
**Author:** ![Torbjorn246](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Torbjorn246](https://forum.botblox.org/u/Torbjorn246)\ **Post date:** [November 28, 2024, 12:41pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/23 "2024-11-28T12:41:33Z")
Thanks, it looks like that had an effect on the RPi. The PC didn’t have it installed and when I installed it it looks like EEE status was `enabled - inactive`, but `Tx LPI: 17 (us)` is also listed. I tried `tx-lpi off` but that did not work (`netlink error: invalid argument`. However eee off set the status to `disabled`. Have to check if it has any effect on the camera performance, the camera does not have an interface where we can access any eee. ---
**Author:** ![peci1](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/peci1/32/32_2.png) [@peci1](https://forum.botblox.org/u/peci1)\ **Post date:** [November 28, 2024, 12:53pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/24 "2024-11-28T12:53:58Z")
You could theoretically disable EEE for the camera by plugging the gigablox between camera and ubiswitch. Just for a test 🙂 ---
**Author:** ![Torbjorn246](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Torbjorn246](https://forum.botblox.org/u/Torbjorn246)\ **Post date:** [November 28, 2024, 1:39pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/25 "2024-11-28T13:39:19Z")
I can confirm that works for the Pi, but do not have access to the camera right here. Using ethtool is a bit annoying as a permanent solution as it is not persistent after reboots of the Pi, but if that becomes the solution we will find a fix. I suppose there are no ways to configure the switch in this regard. ---
**Author:** ![peci1](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/peci1/32/32_2.png) [@peci1](https://forum.botblox.org/u/peci1)\ **Post date:** [November 28, 2024, 1:51pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/26 "2024-11-28T13:51:21Z")
I guess this could be configured on the switch. But that’s a question on @josh_elijah whether they will and can implement it in the firmware. ---
**Author:** ![Nicke](https://avatars.discourse-cdn.com/v4/letter/n/96bed5/32.png) [@Nicke](https://forum.botblox.org/u/Nicke)\ **Post date:** [November 28, 2024, 2:00pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/27 "2024-11-28T14:00:26Z")
When can we expect to have a SW-fix for this bug, so the switch behaves as it should, so we get what we have paid for? We need to ship products to customer within a day or so. ---
**Author:** ![josh\_elijah](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/josh_elijah/32/568_2.png) [@josh\_elijah](https://forum.botblox.org/u/josh_elijah)\ **Post date:** [November 28, 2024, 2:07pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/28 "2024-11-28T14:07:52Z")
Interesting, so it’s an EEE issue? Turning that off completely solved the issue, right? ---
**Author:** ![josh\_elijah](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/josh_elijah/32/568_2.png) [@josh\_elijah](https://forum.botblox.org/u/josh_elijah)\ **Post date:** [November 28, 2024, 2:13pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/29 "2024-11-28T14:13:59Z")
Thankfully, UbiSwitch has an update over UART feature, so it’s pretty easy to update. What we’ll need to do is add this feature to the command line (something to toggle EEE). I’ll speak with @aaron and we’ll come up with a timeline. It won’t be one day, no company will turnaround a firmware update in a day, but at least we now know you’re issue, we can implement a solution. More info to come. @peci1 , thanks for your incredible investigative skills on this one! ---
**Author:** ![Nicke](https://avatars.discourse-cdn.com/v4/letter/n/96bed5/32.png) [@Nicke](https://forum.botblox.org/u/Nicke)\ **Post date:** [November 28, 2024, 2:26pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/30 "2024-11-28T14:26:17Z")
Thanks for the quick answer. Sorry for all time-questions, but when do you (in reality) think that we can have a new SW. We need to know this, a rough estimation, so we can plan, and know how to proceed. And also, how come that it works good with your Gigablox? ---
**Author:** ![peci1](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/peci1/32/32_2.png) [@peci1](https://forum.botblox.org/u/peci1)\ **Post date:** [November 28, 2024, 2:41pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/31 "2024-11-28T14:41:43Z")
> [@Nicke](#): > > And also, how come that it works good with your Gigablox? My guess is because Gigablox uses a much dumber chip which doesn’t support EEE. ---
**Author:** ![aaron](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/aaron/32/12_2.png) [@aaron](https://forum.botblox.org/u/aaron)\ **Post date:** [November 28, 2024, 3:09pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/32 "2024-11-28T15:09:01Z")
> [@Torbjorn246](#): > > Using ethtool is a bit annoying as a permanent solution as it is not persistent after reboots of the Pi, but if that becomes the solution we will find a fix. One way of achieving this on the RPi/PC is to use your init service in your OS to run a script that runs ethtool to disable EEE. For example, if your OS uses `systemd` you can run a script after startup. [Here’s a guide](https://www.linode.com/docs/guides/start-service-at-boot/) I found to help with that. However, that is no substitution for situations where you don’t have system admin access, like your camera. In this case, we will work on adding EEE config to the UbiSwitch in the latest update of BloxOsLite. > [@Nicke](#): > > And also, how come that it works good with your Gigablox? I want to debug that too! GigaBlox also supports EEE but I’ve seen how differences in silicon differences can cause issues for different PHYs, often requiring errata fixes. ---
**Author:** ![josh\_elijah](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/josh_elijah/32/568_2.png) [@josh\_elijah](https://forum.botblox.org/u/josh_elijah)\ **Post date:** [November 28, 2024, 7:32pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/33 "2024-11-28T19:32:35Z")
So, I’m aware you’ve already emailed us directly but I’m going to answer here for the benefit of others. On the one hand, we’re a small team and we build all our software so we’re usually able to get software updates out quite quickly. This is helped by the fact that BloxOSLite (The firmware running on UbiSwitch and SwitchBlox Industrial) itself runs an “update-over-UART” mechanism, meaning you can update it with the newly released firmware just using the UART port (no need for any of this complicated firmware flashing business that we used to have to do on our older boards). On the other hand, we like to be careful and considered when we release new firmware/software. We need to be sure that we don’t introduce new bugs or significant technical debt with each new release. We also like to stack up features for each release of BloxOSLite. For example, the planned next release includes SFP speed configuration, QoS and now, EEE toggling. This is all to say, it won’t be that we can release the software in a day, but it’s also not months away. We’ll discuss this internally and get back to you on email (and here) regarding our timeline. ---
**Author:** ![josh\_elijah](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/josh_elijah/32/568_2.png) [@josh\_elijah](https://forum.botblox.org/u/josh_elijah)\ **Post date:** [November 28, 2024, 8:24pm UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/34 "2024-11-28T20:24:08Z")
@aaron and I have discussed; we are aiming to release an update to BloxOSLite that adds EEE toggle-ability by the end of this year. We are finishing up some work on [Rugged SOM](https://botblox.io/rugged-som/?showHidden=true&ctk=424319b7-e082-45bb-b4f0-7970843ea350) that will add (R)STP and multicast at present. ---
**Author:** ![josh\_elijah](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.botblox.org/josh_elijah/32/568_2.png) [@josh\_elijah](https://forum.botblox.org/u/josh_elijah)\ **Post date:** [January 28, 2025, 10:15am UTC](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353/35 "2025-01-28T10:15:10Z")
Update to all of this, we’ve now released the latest version of BloxOSLite (Version 0.4.0) which adds the ability to toggle EEE. This should solve your issues. You’ll need to update your UbiSwitch Module over the UART port. Documentation on the new release and the new features is below. Let us know if you have any issues. Binary files: [Release v0.4.0 · botblox/bloxoslite-releases · GitHub](https://github.com/botblox/bloxoslite-releases/releases/tag/v0.4.0) Software update instructions: [Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.](https://botblox.notion.site/Upgrading-1160ca7860eb80a99b64c0bc843a9d3c) CLI usage documentation: [Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.](https://botblox.notion.site/Port-MAC-and-PHY-status-control-fdb543a902374345b10c1a5254666017#1880ca7860eb80cdbaf0cfb4c7116b1d) General getting started guide: [https://store-l0hv1zrcre.mybigcommerce.com/content/UbiSwitch%20CLI%20Guidelines.pdf](https://store-l0hv1zrcre.mybigcommerce.com/content/UbiSwitch%20CLI%20Guidelines.pdf) [Previous page](https://forum.botblox.org/t/high-packet-loss-in-simple-system/353.md?page=1)