Xcore x2500 - new CF won't boot
-
Recently I had my 4GB SandDisk Ultra CF card, I believe, die. That is one day my network was down and I couldn't get into webui regardless of efforts. So I purchased a new CF on Amazon - a 8GB SanDisk extreme. My problem is that after flashing the same 2.1 nanobsd build I got up and running intially I'm met with the same behavior every time I get console output (see attached screenshot). I also have a 64GB ide drive I was able to get connected and it's giving the same the behavior. So I would be lookign to the community on whether or not this would be a hardware failure as that's what I'm leaning towards. any insight whatsoever would be appreciated though.
-
Looks like the wrong baud rate at the console. That's where it changes to whatever speed is set in loader.conf(.local).
Steve
-
So the baud is 9600 and it has been saved in Putty since I set this up initially back about a year and a half ago. I attached a screenshot with all the settings. What baud should I be using?
-
115200 is the default baud rate for current images. I'm uncertain exactly when then changed but definitely try that.
That device is now very old though. It might be a hardware issue.
Steve
-
No dice on the 115200 rate - just get a blinking cursor and never any text in console. I waited about 20 minutes too. Truthfully I was leaning towards hardware issue when I posted this but was hoping it was just something I was doing. As I guess my final question on this matter - would you have any other suggestions on what I could look for to ultimately rule this as hardware?
-
I definitely could be hardware, I no longer have any x-core boxes that still POST. But where it's stopping seems like a config issue.
Are you sure you used the correct Nano image and not a Nano+VGA image?
I would try this image: https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.5-RELEASE-4g-i386-nanobsd.img.gz
That should boot up with a console at 115200.
Steve
-
Forgot to post back on this but I belive it to indeed be a hardware issue - look at those caps. From additional reading I'm finding these capacitors are prone to fail on these boards. Do you think it would be worth a shot trying to replace them?
-
@jlibs Forgot to post back on this but I belive it to indeed be a hardware issue - look at those caps. From additional reading I’m finding these capacitors are prone to fail on these boards. Do you think it would be worth a shot trying to replace them?
I've seen people replace the capacitors, like these on ATX motherboards before. I would suspect that there are more capacitors other than those that are bad (shorted).
I would say, it depends on how bad you want to salvage that motherboard as to whether it is worth the time or not. Also need to make sure you can find capacitors that are of equal value, size and voltage. I have some ATX motherboards with capacitors like that, that I need to throw in the trash. They are old and too power hungry. Not worth the effort for me.
-
To be honest - I really don't have much to lose. Unfortunately this particular model of Firebox is the only one that will fit in my very short depth wall rack. So if I thought it might work and run for another 5 or so years I would easily spend more than a few hours trying to replace those. I should mention I'm also fairly decent with a soldering iron. Any suggestions where I might start looking for replacement caps?
-
Probably somewhere like mouser.
-
Yeah. Or since, as you say, this is very common there are often re-cap kits sold on ebay with collections for various specific motherboards. But also some generic stuff.
Bare in mind that those boxes are pretty much antique at this point. You can pick up the whole unit for peanuts if you catch the right auction. Though all of them are going to be prone to similar failure unless they're new old stock or similar.
Our own 1u systems are very short. IJS
Steve
-
Realize this topic is rather old but just wanted to update it that I went ahead and ordered caps from mouser that matched the spec of the ones I pulled off the board and got the old Firebox running again! Was even able to get it booting off a hard drive. Really appreciate all the insight offered!