- Thinks this weather is great for cuddling with someone special. [Original Tweet] 8 hours 38 min ago
- Has a z/OS final to finish by tomorrow... [Original Tweet] 12 hours 30 min ago
- @purrdeta LOL [Original Tweet] 15 hours 16 min ago
News aggregator
texnofobix: Thinks this weather is great for cuddling with someone special.
texnofobix: Thinks this weather is great for cuddling with someone special.
texnofobix: Has a z/OS final to finish by tomorrow...
texnofobix: Has a z/OS final to finish by tomorrow...
texnofobix: @purrdeta LOL
texnofobix: @purrdeta LOL
texnofobix: @purrdeta did a girl say that or you?
texnofobix: @purrdeta did a girl say that or you?
texnofobix: @pstanoch an a on mq and b on the other
texnofobix: @pstanoch an a on mq and b on the other
texnofobix: @pstanoch i do and that is on my agenda tonight
texnofobix: @pstanoch i do and that is on my agenda tonight
texnofobix: Just finished replacing outlets and switches in two bathrooms
texnofobix: Just finished replacing outlets and switches in two bathrooms
Fuhgetaboutit!
Theft of the Magi
(author unknown)
texnofobix: @purrdeta is it better than cable?
texnofobix: @purrdeta is it better than cable?
texnofobix: Is wondering if anyone likes uverse? Send of a message if you do or don't.
texnofobix: Is wondering if anyone likes uverse? Send of a message if you do or don't.
Biden gets invited on hunting trip…
Biden gets invited on hunting trip… and respectfully declines.
(Dick Cheney, Joe Biden)
picture: dunno source, via our lol builder. lol caption:
LEAD STORY FAIL
LEAD STORY FAIL
Want to see more FAIL? Check out Failblog.org!
picture: dunno source, via our lol builder. lol caption: stupidream
Newly Discovered Planet Totally Looks Like Eye Of Sauron
Newly Discovered Planet Totally Looks Like the Eye Of Sauron from The Lord of the Rings
Submitted by anon
» Think you can do better? Make your own!
ROCKET HARPOONS
ROCKET HARPOONS
Killing space sharks since 2008
What’s going on in the picture? Tell us in the Comments
picture: dunno source, via our lol builder. lol caption: Daniel
and then Pope Benedict kicked it into hyperdrive
and then Pope Benedict kicked it into hyperdrive
(Pope Benedict XVI)
picture: dunno source, via our lol builder. lol caption: firebert7
USB retardedness
I finally fucking figured out why I have had little to no luck with the 2.5" USB external hard drive enclosures that solely use the use the USB port as a power source. I had a Western Digital case (the drive died, but the case keeps on truckin'), a Seagate enclosure, and an Eaglebit enclosure from Micro Center that was on sale for $9.
All of them exhibited a similar issue of randomly powering off and back on, or not powering up at all. I originally blamed this on poor design of the circuit that handles spinning up the drive and the inrush current of ~.5A to 1A caused by the drive spinning up. But after three of them behaving the same way, I started wondering if something else was the issue.
It's the length of the cable.
The cable was just long enough to cause the power to sag below what was required to spin the drive up and the controller to fully power up. This likely caused overload on the host controller as the drive vainly tried to spin up over and over(>500mA). This caused a domino effect of the device drawing too much power from the host, and the host controller sending a reset continuously -- which in turn didn't allow the drive and the controller to fully power up to negotiate unit loads with the host controller.
With a shorter cable, the device is allowed the initial inrush current, which is just under the max of 500mA (technically, this is out-of-spec, more on this later). Once the drive spun up and the controller powered up, the device was able to handshake and agree on 5 load units (500mA) and the host controller allowed the device to continue operating at 5 unit loads.
Some drives ship with a Y-cable with two USB ports that you attach to the host. This is a non-standard technique as you're just simply leaching 5V+ without negotiating unit loads on the secondary connector. Although, on a typical controller this would supply up to 100mA which should be enough to allow both the controller to drive to spin up (a combined draw of roughly 580mA?). Or if it gets lucky, another 500mA. It's a hack though.
Some USB controllers throw out 550mA (+/-10% tolerance) no matter what because of the above standard-breaking phenomenons. This is sort of breaking the USB standard, but there's no harm in doing it. The by-the-books way is a device is to enter a super low power mode (100mA) to make an initial negotiation with the host controller and THEN upon being permitted to operate at 5 load units, the device is allowed to operate at 500mA -- contrary to the hard drive box which demands all 500mA up front.
USB Charging spec allows up to 1.8A to be drawn from a USB port without any negotiation. Hopefully we'll be seeing that in future host controllers. And would solve the problem entirely. At least until we see devices needing more than 1.8A. At which point I question what device needs 1.8A.krhainos@gmail.com
All of them exhibited a similar issue of randomly powering off and back on, or not powering up at all. I originally blamed this on poor design of the circuit that handles spinning up the drive and the inrush current of ~.5A to 1A caused by the drive spinning up. But after three of them behaving the same way, I started wondering if something else was the issue.
It's the length of the cable.
The cable was just long enough to cause the power to sag below what was required to spin the drive up and the controller to fully power up. This likely caused overload on the host controller as the drive vainly tried to spin up over and over(>500mA). This caused a domino effect of the device drawing too much power from the host, and the host controller sending a reset continuously -- which in turn didn't allow the drive and the controller to fully power up to negotiate unit loads with the host controller.
With a shorter cable, the device is allowed the initial inrush current, which is just under the max of 500mA (technically, this is out-of-spec, more on this later). Once the drive spun up and the controller powered up, the device was able to handshake and agree on 5 load units (500mA) and the host controller allowed the device to continue operating at 5 unit loads.
Some drives ship with a Y-cable with two USB ports that you attach to the host. This is a non-standard technique as you're just simply leaching 5V+ without negotiating unit loads on the secondary connector. Although, on a typical controller this would supply up to 100mA which should be enough to allow both the controller to drive to spin up (a combined draw of roughly 580mA?). Or if it gets lucky, another 500mA. It's a hack though.
Some USB controllers throw out 550mA (+/-10% tolerance) no matter what because of the above standard-breaking phenomenons. This is sort of breaking the USB standard, but there's no harm in doing it. The by-the-books way is a device is to enter a super low power mode (100mA) to make an initial negotiation with the host controller and THEN upon being permitted to operate at 5 load units, the device is allowed to operate at 500mA -- contrary to the hard drive box which demands all 500mA up front.
USB Charging spec allows up to 1.8A to be drawn from a USB port without any negotiation. Hopefully we'll be seeing that in future host controllers. And would solve the problem entirely. At least until we see devices needing more than 1.8A. At which point I question what device needs 1.8A.krhainos@gmail.com
