Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
multiple large (>1TB) usb hard drives over a slow USB 2.0 connection #1134
I had an issue when connecting multiple large (>1TB) usb hard drives over a slow USB 2.0 connection.
I describe my solution in this thread:
My modified initrd.gz (for tahrpup 6.0.6) cab be found at:
*Note that, one might want to make further speed optimizations before incorporating this into Wolf-CE.
The following is a copy of my post in the forum:
There is a problem with the "wait4usb" script in woof-ce,
Have you tried a patch like the following:
`--- /0initrd/init 2018-01-22 13:16:55.268537361 +1000
You first solution just adds a delay. While this would work, it would slow down the boot in instances where this isn't needed. As a minimum the delay should be configurable as a boot parameter, which I did.
I set the default delay to 3 seconds because that is what Barry did in his "wait4usb" function.
However, a default of 1 second may be preferred if my second boot parameter is tried
Which is how many times to try the wait4usb function. The loop will exit when the partition is found that one specified as a boot parameter.
If waitdev defaults for one (1) then maybe usb_tries should default to six (6). However, I think there is an issue with doing for this. The wait4usb function may take longer then one second (1s) even with the delay removed. I think that some of the code in wait4usb is for debugging purposes and or legacy compatibility and could be bypassed based on boot parameters.
Now regarding your second solution. This may also work but it will slow down booting in instances where it isn't needed, since code will be re-executed, that may not need to be.
Hi s243a, you might want to perform your tests in Lxpupsc
or Artfulpup (see the forum, i don't have links)
The current lxpupsc release is
apply this delta to update it to a version that was uploaded 9 hours ago according to SF
The only possible issue is that peebee is constantly using cutting edge kernels and apps and the results with older kernels and stuff may vary, you can change kernel of course.,,, if you want to test the latest changes in woofce without building an iso yourself, take a look at lxpupsc. Switch to the jwm desktop, or the rox desktop to be precise if you feel like
Sometimes there are bursts of activity that basically means i'm bored with nothing else to do, when major and large changes can happen in a couple of days, and that's when trying to contribute something can be a headache as some scripts differ too much, that's why you and everyone who wants to test the latest release have to download peebee's latest builds and interim deltas.