Quote: Originally Posted by
skeurton 
i'm having the same problem. i bought a new GPS receiver thinking that the heat killed my old one, but i'm still having problems with the new one (holux gr-213). on moderately warm to hot days, the pc will boot up just fine with all usb devices working (using powered hub). but streetdeck comes up with a message saying it can't find my GPS receiver. on cool days or at night, it boots up just fine.
right now, the receiver is mounted on the rear deck. i don't have any window tinting, so the thing is in direct sunlight. i had no problems with my previous microsoft/pharos receiver being there for 3 years, that is until recently. i'm not quite sure how to solve this problem. i tried mounting it on the underside of the rear deck, but it wouldn't pick up a signal.
anyone have any ideas?
The operating temperature for the Holux (same one I have) is up to 80C, which is about 175F. Mine was coming pretty close to this temperature when it sat in direct sunlight for hours (also, outside air temp has been 90F+)..
I considered powering the hub with a Point-of-Load supply.... but in one of my tests I plugged the hub into a wall outlet (extension cord dragged from my garage) so the 5V extra juice was not from the PC PS.... didn't make a difference. For some reason, the GPS still being connected to the PC power line (through USB) was enough to still cause problems.
I wonder... can you use a USB hub that is connected ONLY to the data I/O connections (i.e. cover/remove power terminals from cable) and just use the external power (from a POL or similar isolated supply)?
Oh, another something I had wondered. What are the chances that the GPS, being hot and possibly malfunctioning, is just spitting garbage at the PC through its USB IO and it causes it to freeze. I was beginning to think that my PC was possibly trying to read that input code as a boot device and getting confused. I would have disabled USB Legacy support to try to test this... but I need to find a PS2 keyboard to recover from that test (been using a USB keyboard). Thoughts on that? I know it's pretty far-fetched but I'm trying to consider anything here.
UPDATE: been reading around tonight.. and if you search more in general online, this problem exists across the board for many devices. I'm really thinking that the reason it freezes before detecting IDE drives is because it is trying to check all the USB devices for boot capabilities (and the GPS is causing issues here). A common fix seems to be disabling USB legacy support. This way, the BIOS will ignore USB device functionality completely. Of course if you intend on changing anything after that you will need a PS2 keyboard handy. I'm going to try this out tomorrow to see what kind of results I get. Actually, I need to find a PS2 keyboard first but I'm sure I have one lying around here somewhere :-p
Update Update:
Couple things learned today (friday)
USB Legacy Support (Disabled): Makes PC absolutely FLY through POST. Boot-ups are super fast and I don't have any startup problems.
Lilliput Monitors: A warning to all (2k1Toaster, I saw you had this problem too!). Do not, under any circumstance use the auto-adjust button. Great idea... baaaaaad situation. My 800x600 functionality is fried. Yeah. SUCKS! fkljasdfl;kjslakfjlskaj
So now I run in 1024x768 which I don't love but it works. Thank you roadrunner for scaling easily.
At least everything is working now, but of course something had to break in the process!