View Full Version : A new 360 problem: am I in for another 5 week repair?
Poorfamily
03-19-2008, 01:14 PM
Well I can't get my 'new' replacement 360 (had it maybe 4 weeks) to recognize any peripherals. It won't recognize any of my Rock Band instruments connected via USB. I can turn the console on with the wireless controller but the ROL never spins on the console so it seems it's not trying to connect. Turning off the console also turns off the wireless controller. Syncing does no good. Pressing the two sync buttons causes both ROL to flash together (console and controller) but then the console just stops trying.
Any suggestions besides yet another repair job?
Poorfamily
03-19-2008, 02:00 PM
Solving my own problem: Could it be that I need to have the TV on first? I'm connected via HDMI and with the TV off the console won't recognize anything. Turn on the TV and MAGIC! It now recognizes both wireless and USB ports.
Pardon my attitude, but that is one STRANGE little quirk that needs to be reconsidered.
skaar
03-19-2008, 02:05 PM
That is a weird one. The 360 is weird for the video dependancy - same thing when you're *ahem* working on one - you can't boot it up without a video connection.
Poorfamily
03-19-2008, 02:08 PM
Well considering I'll most likely need several more warranty repairs in the future I won't be 'working' on the 360. :) Has anybody else tried to start the console without turning on your TV? I suppose the problem is HDMI dependent?
marcus12024
03-19-2008, 02:59 PM
Well considering I'll most likely need several more warranty repairs in the future I won't be 'working' on the 360. :) Has anybody else tried to start the console without turning on your TV? I suppose the problem is HDMI dependent?
It definitely won't come on properly without detecting a video device and hand-shaking, when connecting via HDMI. I noticed the same thing once I got my Elite and a new HDMI-equipped receiver - I would turn on the 360, and it would start, but not completely (you could tell it was doing something, but wouldn't actually light up with the ring of light) until the receiver and TV were turned on. I even tried waiting a few minutes one time and - sure enough - it would work fine once it detected the TV.
I'm guessing that they've set it up so that, if it can't handshake with something properly via HDMI, then why bother starting up? It's also likely that this handshake has to occur before the videocard and/or video memory can be initialized (or something else in the system), or else it would likely have to reboot once it detected the display device.
To test something, try disconnecting the HDMI cable at one end while you are using the system and your TV is on - if you plug the cable back in, it won't recognize anything and you'll have to reboot your system (at least that's how mine works). I'm sure someone else out there has a better explanation for this behavior...mine's just an educated guess, at best! :)
Trebuken
03-19-2008, 03:10 PM
Mine does something similar but I am not using HDMI.
I'll turn it on and it does what you describe, I then turn it off and on again and it works fine. Does this most of the time, but not all of the time.
Sometimes I need to unplug the component cables to get the video output to be 1080 rather than 480i as well. The two hiccups do resemble yours.
I have a launch model and it has been doing this for quite some time...but it works...