I've got a trinity that has been acting funny for a couple of years. It seems to take forever for the network interface to come up. I first noticed it about 2 years ago on wifi. It was like it was asleep or something. So I ran a cable and tried it that way. Pretty much the same result. I thought it was just not pulling a DHCP address, so I typed one in thought it was working......
Here's a history of what has been done to this box.
I bought it used like 3 years ago when my previous coolrunner modded box overheated for the last time (skyrim) and was beyond what I wanted to do to resurrect it. I hastilly moved the coolrunner to this trinity and it was fine on the network, I had it hardwired and it was happy. About a year later I did some updates to FSD, Dashlaunch, and I updated the dash so some of the newer games would load. It was around this time that I noticed that the network connection seemed "stuck". I have since upgraded to the CR4, and installed a Demon, with a rebuilt retail NAND because my backup copies were lost. I've been going blind reading up on this and I'm wondering if maybe there's some leftover junk on the rebuilt NAND.
Here's what it is doing now. When I boot the console about half the time it won't be able to connect to the local network or the internet. Most of the time FSD will show the manually entered IP info, and sometimes although rare it will show a 169.x.x.x address there. What works to get it back online is to exit to the NXE dash and go into the network settings and just edit and save and it seems fine. I can reach it from my PC then, and it goes online fine to grab title updates and cover art and passes the connection test to link.
Now I mentioned I have a Demon installed. It does it on both nands. The one on the console is the rebuilt retail, and the demon nand is the CR4 enabled nand. When I switch between them I also swap out the hard drive. I've got one drive that has only seen the retail image and the other has only seen the CR4 enabled nand. When I switch between images I notice that my system time and date reset to 6:00am and the year is 2005. When that happens the network connection is just flat down. It doesn't seem to want to pull an IP from DHCP and it basically ignores the manually entered settings. On the rebuilt retail NAND it seems to wake up if I repeatedly try to sign onto live. It gives me errors about the network being down for the first few tries, but then it just seems to start working. I can also wake it up by going into the network settings and just opening all the settings up like I'm going to edit them and then hit save.
So, any ideas?
Here's a history of what has been done to this box.
I bought it used like 3 years ago when my previous coolrunner modded box overheated for the last time (skyrim) and was beyond what I wanted to do to resurrect it. I hastilly moved the coolrunner to this trinity and it was fine on the network, I had it hardwired and it was happy. About a year later I did some updates to FSD, Dashlaunch, and I updated the dash so some of the newer games would load. It was around this time that I noticed that the network connection seemed "stuck". I have since upgraded to the CR4, and installed a Demon, with a rebuilt retail NAND because my backup copies were lost. I've been going blind reading up on this and I'm wondering if maybe there's some leftover junk on the rebuilt NAND.
Here's what it is doing now. When I boot the console about half the time it won't be able to connect to the local network or the internet. Most of the time FSD will show the manually entered IP info, and sometimes although rare it will show a 169.x.x.x address there. What works to get it back online is to exit to the NXE dash and go into the network settings and just edit and save and it seems fine. I can reach it from my PC then, and it goes online fine to grab title updates and cover art and passes the connection test to link.
Now I mentioned I have a Demon installed. It does it on both nands. The one on the console is the rebuilt retail, and the demon nand is the CR4 enabled nand. When I switch between them I also swap out the hard drive. I've got one drive that has only seen the retail image and the other has only seen the CR4 enabled nand. When I switch between images I notice that my system time and date reset to 6:00am and the year is 2005. When that happens the network connection is just flat down. It doesn't seem to want to pull an IP from DHCP and it basically ignores the manually entered settings. On the rebuilt retail NAND it seems to wake up if I repeatedly try to sign onto live. It gives me errors about the network being down for the first few tries, but then it just seems to start working. I can also wake it up by going into the network settings and just opening all the settings up like I'm going to edit them and then hit save.
So, any ideas?
