Just bought the above router and after it working flawlessly for over a week it just stopped working, could see it on the wireless network, but not connect. Turning off and on made things worse, no wifi, ethernet not working. Tried USB, not found.
So after a bit of searching noticed a few tools on here to connect, i can use PC Tools to connect via the ADAM2 ftp and been searching for a firmware for this router. I think someone on here had a version from Paradigm? If so any chance of posting this as thier support forms fail when trying to submit for me.
I am thinking of un-bricking and using the Acorp one, or taking the hit using the Routertect 2.3 on here and losing the ethernet switch. Anyone have any ideas before i try and reflash (factory reset button had no effect..)
Also any ideas why it might of "just failed", i've not tried to update the firmware due to the "no ethernet support (its the realtek one)"
Any help appreciated.
Thanks
Ebuyer's GWART2-54125 or PTI-8505g stopped working
I was / am thinking of that but delay in returns = no net at home and slightly concious it could of been me....
Was logged on and in /var/tmp there was a kcore file over 300MB big, so tried to remove that cat /dev/null > kcore and rm kcore (niether of which did anything)...
Then a day after it didn't work..
Was logged on and in /var/tmp there was a kcore file over 300MB big, so tried to remove that cat /dev/null > kcore and rm kcore (niether of which did anything)...
Then a day after it didn't work..
- Shotokan101
- RouterTech Team
- Posts: 4779
- Joined: Thu Jan 26, 2006 3:17 pm
- Location: Glasgow, Scotland
On other systems "kcore" is a pseudo (pretend) device file which actually maps onto the real memory of the computer. Its size is pretend as its not a real file - it just references the machine's memory. It mostly/only used by debuggers for fault finding.
As yours was in /var/tmp its probably one of the things the firmware builds during bootup as it does not have a hard drive to work with...
If its a readonly service then your commands probably did nothing. If its writable then your cat /dev/null might have affected it.
I hope that it only refers to the real ram memory and so should have left the flash intact. If it can affect the flash then you have a door stop.
You need to try either 1) a power off - power on cycle. or 2) a factory reset using the little reset button on it somewhere.
If those don't work you are looking for tools which talk to the bootrom on the device. Search other threads about recovery.
As yours was in /var/tmp its probably one of the things the firmware builds during bootup as it does not have a hard drive to work with...
If its a readonly service then your commands probably did nothing. If its writable then your cat /dev/null might have affected it.
I hope that it only refers to the real ram memory and so should have left the flash intact. If it can affect the flash then you have a door stop.
You need to try either 1) a power off - power on cycle. or 2) a factory reset using the little reset button on it somewhere.
If those don't work you are looking for tools which talk to the bootrom on the device. Search other threads about recovery.