SDRTrunk USB I/O Error while submitting transfer buffers (Ubuntu)

[justdmbobbo]

I recently had my windows machine have a complete HD Failure - so I grabbed a spare drive off the shelf and spun up a copy of Linux/Ubuntu.

I have 5- RTL-SDR's in an external powered hub that worked without any issue on windows with the same guts (motherboard, memory etc). - only difference is now running Linux and not Windows.
Installed SDRTrunk and back up and running the same way I had the Windows version set up.
3-systems - 5 dongles

I seem to only be able to run things for 20-30 mins before I get USB I/O errors on one tunner... then it errors out... then a second and it errors out.
3-sticks always seem to stay solid.... but every time I restart, eventually 2 of 5 error out "USB ERROR"

I stumbled across this old thread here:

SDRTrunk - SDRTrunk errors using 4x RTL-SDR receivers on Linux

I'm trying to monitor a few P25 systems with channels that are not closely spaced, requiring multiple RTL-SDR receivers to cover. I've found that when the 4th receiver is used (not a specific receiver, just the 4th simultaneous one to be brought up), I get USB errors such as: 23:20:44.861...

forums.radioreference.com

but I'm not quite following what adjustments I can make and the code to do so.

Can anyone give me a dummied down version of that thread or any suggestions?

 

[CC-Scanner-Guy]

Can anyone give me a dummied down version of that thread or any suggestions?

The "for dummies" version of that thread's solution for increasing the limit on memory available for USB devices:

Open a terminal window and run

sudo su

(type your password if asked, then run: )

echo 1024 > /sys/module/usbcore/parameters/usbfs_memory_mb

That's it!

But if you reboot you'll have to run those commands again for it to take effect again (unless you use one of the "permanent solution" methods in that thread)

 

[justdmbobbo]

The "for dummies" version of that thread's solution for increasing the limit on memory available for USB devices:

But if you reboot you'll have to run those commands again for it to take effect again (unless you use one of the "permanent solution" methods in that thread)

From this dummy to your genius, thank you very much.
Now I may I never need to reboot again!