i've been screwing with my Receptor for HOURS. Finally, after remembering a bizarre situation where my MacBook Pro's bluetooth will fail to work, requiring not a reboot but a power cycle to fix, i decided to unplug the Receptor from the electrical mains. When i plugged it back in, i powered it on again, where the first initial start stuttered. It actually started and then shut off and then started again, without my intervention. It was very quick. Upon getting to a booted state, i configured the network settings to use Crossover, and for the first time in hours, it worked fine.
WHY would removing the power affect this at all? This was only a random thought. When i power cycle the Mac to solve the Bluetooth, i'm not removing the power supply or battery, just power cycling the machine. Power cycling the Receptor did not help.
Explanation Requested: Why would ethernet port fail until after power removed from Receptor?
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRist
- 76 posts since 17 Jun, 2004
I can't give you a proper explanation seeing as how I'm not sure what the initial issue was. It is unlikely the ethernet ports failed, the easiest way to see this is simply to look at the the port with the ethernet cable plugged in. If there is a light, it's working but maybe not making a connection. If the Receptor was set to auto and you connected it directly to your computer then this is why it could not make a connection originally. Setting the network settings to Crossover allows the Receptor to make a direct ethernet connection to your computer.
-Nick
-Nick
-
- KVRAF
- Topic Starter
- 6113 posts since 7 Jan, 2005 from Corporate States of America
The original problem was zero network connectivity. I tried all different settings. Crossover would not stick. It would default back to manual. It would not get an IP via DHCP either, ending up with all zeros or a self-assigned IP. Manual IP didn't work either (yes, I added it to the router end as well).
I tried with four known good ethernet cables. Sometimes the Ethernet port lights would come on upon plugging in, and sometimes they wouldn't (all zero IP with no lights, self-assigned IP with lights). When they did light up, the amber activity light was a constant, consistent, rapid blink, without variation. I've only ever seen that before on a suspected bad cable, but that's not what the problem was here.
Nothing networking worked right until after I removed the power cable and started over again. All was fine after that. Crossover and DHCP both work fine now.
...
Of course, now the hard drive is making a LOT of constant activity noise. It sounds like a drive making a LOT of small and rapid accesses of many sectors, not a large block of data. But i doubt it's actually accessing data. I have an external LaCie drive that does the same thing, even when not plugged into a data port (USB or FireWire; it just needs to be powered on) and no one anywhere can offer any suggestion as to what it is doing. As with the LaCie, the Receptor will stop doing this briefly if something on the drive is accessed intentionally (loading a plugin or a bank). Otherwise it just constantly grinds away for no apparent reason.
I have no idea if this is related to the previous issue on the network socket.
By the way, this Receptor has never gone anywhere. It sits in a rack barely being used, plugged into a protected power source. So it's not been subjected to any abuse whatsoever. Well, neglect maybe.
I tried with four known good ethernet cables. Sometimes the Ethernet port lights would come on upon plugging in, and sometimes they wouldn't (all zero IP with no lights, self-assigned IP with lights). When they did light up, the amber activity light was a constant, consistent, rapid blink, without variation. I've only ever seen that before on a suspected bad cable, but that's not what the problem was here.
Nothing networking worked right until after I removed the power cable and started over again. All was fine after that. Crossover and DHCP both work fine now.
...
Of course, now the hard drive is making a LOT of constant activity noise. It sounds like a drive making a LOT of small and rapid accesses of many sectors, not a large block of data. But i doubt it's actually accessing data. I have an external LaCie drive that does the same thing, even when not plugged into a data port (USB or FireWire; it just needs to be powered on) and no one anywhere can offer any suggestion as to what it is doing. As with the LaCie, the Receptor will stop doing this briefly if something on the drive is accessed intentionally (loading a plugin or a bank). Otherwise it just constantly grinds away for no apparent reason.
I have no idea if this is related to the previous issue on the network socket.
By the way, this Receptor has never gone anywhere. It sits in a rack barely being used, plugged into a protected power source. So it's not been subjected to any abuse whatsoever. Well, neglect maybe.
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud