PixL Posted July 26, 2018 Share Posted July 26, 2018 I was having performance issues with firmeare 2.2.0 where CPU load would stay very high and the tetra would have a delay to change pages on the interface. I decided to do a firmware recovery by holding the reset and browsing to 192.168.1.1 and uploading a .bin. Every time I do this the tetra never self resets and just sits with a yellow light.. i'm not sure what to do now. Link to comment Share on other sites More sharing options...
Irukandji Posted July 27, 2018 Share Posted July 27, 2018 Make shore you have plunged it into the wall. Link to comment Share on other sites More sharing options...
Just_a_User Posted July 27, 2018 Share Posted July 27, 2018 13 hours ago, PixL said: browsing to 192.168.1.1 and uploading a .bin. was it the factory version? should be this one https://www.wifipineapple.com/files/tetra_factory.bin maybe you flashed the normal one? just checking. Otherwise connect to the tetras serial connection and use screen to watch output as it comes up., there maybe clues in there. Link to comment Share on other sites More sharing options...
PixL Posted July 27, 2018 Author Share Posted July 27, 2018 3 hours ago, Just_a_User said: was it the factory version? should be this one https://www.wifipineapple.com/files/tetra_factory.bin maybe you flashed the normal one? just checking. Otherwise connect to the tetras serial connection and use screen to watch output as it comes up., there maybe clues in there. Fantastic, I was indeed using the wrong .bin It is now working but I did have to try 3 times as the eth1 connection via usb kept dropping. Link to comment Share on other sites More sharing options...
Foxtrot Posted July 27, 2018 Share Posted July 27, 2018 16 minutes ago, PixL said: Fantastic, I was indeed using the wrong .bin It is now working but I did have to try 3 times as the eth1 connection via usb kept dropping. Likely to actually be your Network Manager interfering with your manual assignment of 192.168.0.1 on that interface Link to comment Share on other sites More sharing options...
PixL Posted July 27, 2018 Author Share Posted July 27, 2018 27 minutes ago, Foxtrot said: Likely to actually be your Network Manager interfering with your manual assignment of 192.168.0.1 on that interface It could be, i'm using Mint Linux and just used ifconfig as below: ifconfig enx001337a630e6 down ifconfig enx001337a630e6 up 192.168.1.2 Also don't ask me why Ubuntu based distributions have different interface names. Link to comment Share on other sites More sharing options...
Foxtrot Posted July 27, 2018 Share Posted July 27, 2018 Those names are based on the MAC address of the interface. It's the 'new' predictable systemd network names. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.