No GEM-E on Network Scan

Post by **Teken** » Tue Nov 18, 2014 7:01 pm

OK, before you get started down this path I would ask you to perform the *shorting* to the Ethernet module again. At that point the GEM should be in its default state using what ever IP address is listed in the users manual.

Once this is done (newer) laptops can auto config to *cross over* and mimic using a cross over cable. The intent is we want to remove any other elements from connecting to the GEM.

In your laptop you will configure a static address for the computer using the same subnet and using one octal number higher than what the GEM is using. Once done, connect to the GEM directly with a cable to your laptop.

Please confirm that it connects and if so please try to ping the GEM. Report back if the GEM replies back because if it doesn't (this assumes) your laptop can in fact auto cross over. If not you need a cross over cable to connect to a GEM with out a router in place.

If it doesn't work then connect the GEM to the router and see if its listed at all. If its not, please do the same thing before and assign (reserve) the MAC address in the router for the GEM. Reboot the router, then the GEM and see if it shows up in the router device list.

TaltosDM · Post by **TaltosDM** » Tue Nov 18, 2014 7:07 pm

In the ethernet config manual it says for a direct connection to set the windows server as gateway 192.168.2.1 and dns 192.168.2.1
In the firmware config manual for ethernet it says for a direct connection to set the windows server as gateway 192.168.2.2 and dns 192.168.2.2
Which of these is correct or does it matter?

TaltosDM · Post by **TaltosDM** » Tue Nov 18, 2014 7:37 pm

If I do a direct connection with the computer set to 192.168.2.1 and gateway of 2.1 or 2.2 the interface keeps bouncing. This is in regular mode and not recovery mode.

Enabled -> Identifying -> Unidentified network -> Network cable unplugged

I also tried with the computer as 2.3 with gateway of 2.1 or 2.2 or 2.3 and same result.

The chipset is a

http://www.realtek.com.tw/products/prod ... ProdID=239

which says it handles RTL8111E

Supports pair swap/polarity/skew correction
Crossover Detection & Auto-Correction

I am off to bowling but will be back in three hours.

daswafford · Post by **daswafford** » Wed Nov 19, 2014 1:52 am

Hey Taltos,

Take a look at my last two posts on http://www.brultech.com/home/community/ ... 7223#p7223. I'm almost positive that we are both hitting the same bug / issue. My unit was only two weeks old and bricked itself after being power cycled, which sounds just like what you did too.

I just finished restoring mine through a bunch of steps. But the highlight that you should know is that the SW1 based reset is actually setting a static IP of 192.168.11.2/ 255.255.255.0 to the GEM, so it won't attempt to DHCP an address during that.

But anyway, I wrote out all of the steps I took in that last post. Best of luck!
david.

daswafford · Post by **daswafford** » Wed Nov 19, 2014 1:54 am

Oh and a crossover is not actually necessary. To make my life easier I did patch the GEM and my PC into a separate switch (not a router, just a switch on it's own) -- simply to make Wireshark easier to follow.

daswafford · Post by **daswafford** » Wed Nov 19, 2014 1:58 am

Oh, I saw that same behavior -- The bouncing interface that was. I think that's indicative of a crash loop. Mine got stuck and went into this state where it was bouncing the NIC every 1 second or so. I literally watched the GEM flash in a loop like that. I fixed mine w/ a power cylce.

The trigger to that crash loop for me was attempting to open a browser session to 192.168.11.2:5000, which is what it set as the default. I tried this before discovering the mismatched serial settings from the GEM and the Wiznet module (57600 instead of 115200). You can fix that w/ the Wiznet tool Ben Mentions in my post / link.

TaltosDM · Post by **TaltosDM** » Wed Nov 19, 2014 9:56 am

Great, I will try these steps tonight and post the results.

I had googled last night and came across the 11.2 stuff but I thought it was a typo and had ignored it.

I also do not think I was shorting the nic sufficiently.

TaltosDM · Post by **TaltosDM** » Thu Nov 20, 2014 2:55 pm

I moved the discussion over to the daswafford thread where he had resolved his very similar issue.

http://brultech.com/home/community/view ... 9&start=30

Just in case anyone comes and looks at this in a few months and it isn't obvious what happened.

No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan

Re: No GEM-E on Network Scan