turtlebacon Posted December 29, 2015 Share Posted December 29, 2015 (edited) So I was just using my nano (have put a lot of use on it in last 48 hours) .. then randomly it quit working. I had it in the case so I couldn't check the lights.. but after pulling it out and etc. no matter how I try to power it I can't get it to turn on. I had PineAP running and was doing a tcpdump when it crashed. I've tried the USB cable provided on multiple computers - also tried the pineapple juice battery which worked on day 1 and is fully charged + on.. and it's not turning the device on either. Any thoughts? Can you help? Edited December 29, 2015 by turtlebacon Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted December 29, 2015 Share Posted December 29, 2015 No LED what so ever? This is our first report of one borking. What happens if you plug the NANO into a linux box? Do you get anything from dmesg? What about if you power the NANO from the Pineapple Juice then run a USB data cable from its USB host port to an Android -- does it charge the phone? Does the WiFi Pineapple Connector app detect the device? Quote Link to comment Share on other sites More sharing options...
turtlebacon Posted December 29, 2015 Author Share Posted December 29, 2015 No LED, not showing up in any combination of tests described above. =/ Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted December 30, 2015 Share Posted December 30, 2015 What does dmesg or lsusb show? Quote Link to comment Share on other sites More sharing options...
turtlebacon Posted December 30, 2015 Author Share Posted December 30, 2015 (edited) Doesn't show up in lsusb at all - dmesg below 70.947379] usb 2-2: new high-speed USB device number 3 using ehci-pci [ 71.097842] usb 2-2: New USB device found, idVendor=0b95, idProduct=772a [ 71.097846] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 71.097847] usb 2-2: Product: AX88x72A [ 71.097848] usb 2-2: Manufacturer: ASIX Elec. Corp. [ 71.097849] usb 2-2: SerialNumber: 8D7C15 [ 73.223960] asix 2-2:1.0 eth2: register 'asix' at usb-0000:02:03.0-2, ASIX AX88772 USB 2.0 Ethernet, 00:c0:ca:8d:7c:0d [ 73.223996] usbcore: registered new interface driver asix [ 73.249048] asix 2-2:1.0 eth2: link down [ 74.970005] asix 2-2:1.0 eth2: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 78.621604] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [ 92.438578] asix 2-2:1.0 eth2: link down [ 92.456837] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready [ 95.570729] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready [ 95.577774] asix 2-2:1.0 eth2: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 100.196839] asix 2-2:1.0 eth2: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 393.453289] usb 2-2: USB disconnect, device number 3 [ 393.455833] asix 2-2:1.0 eth2: unregister 'asix' usb-0000:02:03.0-2, ASIX AX88772 USB 2.0 Ethernet [ 394.218281] usb 2-2: new high-speed USB device number 4 using ehci-pci [ 394.371282] usb 2-2: New USB device found, idVendor=0b95, idProduct=772a [ 394.371287] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 394.371290] usb 2-2: Product: AX88x72A [ 394.371292] usb 2-2: Manufacturer: ASIX Elec. Corp. [ 394.371293] usb 2-2: SerialNumber: 8D7C15 [ 399.746057] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to send software reset: ffffff92 [ 404.749608] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 414.756167] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 419.759179] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 429.765962] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 434.769794] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 444.775466] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 449.778517] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 459.785205] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 464.788499] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 474.795238] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 479.798199] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 489.805187] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 494.808236] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 504.814810] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 509.818031] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 519.824589] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 524.828673] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 534.835212] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 539.838617] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 549.843989] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 554.847994] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 564.868457] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 569.893414] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 579.900384] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 584.903219] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access [ 594.910118] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable hardware MII access [ 599.913254] asix 2-2:1.0 (unnamed net_device) (uninitialized): Failed to enable software MII access Edited December 30, 2015 by turtlebacon Quote Link to comment Share on other sites More sharing options...
Foxtrot Posted December 30, 2015 Share Posted December 30, 2015 (edited) What kernel are you using on Linux? Some googling shows that some version of the ASIX driver is bad. Might not be the issue if the problem exists on multiple computers. Edited December 30, 2015 by Foxtrot Quote Link to comment Share on other sites More sharing options...
turtlebacon Posted December 30, 2015 Author Share Posted December 30, 2015 kali 2.0 Quote Link to comment Share on other sites More sharing options...
R718D Posted December 30, 2015 Share Posted December 30, 2015 One more reason too hold on in ordering the Nano 1 Quote Link to comment Share on other sites More sharing options...
m40295 Posted December 30, 2015 Share Posted December 30, 2015 This is why they do a dev model to make sure it's functioning This should not make you choose not to get one but if you want stable wait for the release Quote Link to comment Share on other sites More sharing options...
Foxtrot Posted December 30, 2015 Share Posted December 30, 2015 (edited) One more reason too hold on in ordering the Nano This is why they do a dev model to make sure it's functioning This should not make you choose not to get one but if you want stable wait for the release Faulty devices will always happen. It happens with anything. Regardless of "development release" or final product. Edited December 30, 2015 by Foxtrot 2 Quote Link to comment Share on other sites More sharing options...
Ret0n Posted December 30, 2015 Share Posted December 30, 2015 Faulty devices will always happen. It happens with anything. Regardless of "development release" or final product. You beat me to it. Quote Link to comment Share on other sites More sharing options...
cheeto Posted December 30, 2015 Share Posted December 30, 2015 Well, it is my understanding that there will be no hardware change. This may be the Evaluation version but as for hardware it's a final version. The only changes we'll see from here on out will be firmware updates. Cheers Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted December 30, 2015 Share Posted December 30, 2015 The hardware has gone through rigorous testing and has passed 99% of the required certification. That should be 100% in a few weeks. The hardware shouldn't be failing. That said, it clearly has in this case. turtlebacon - email us at support@hak5.org with your order # so that we may coordinate an exchange. We'll get the replacement shipped out to you ASAP and email you a return shipping label. At this point we'll be gathering every possible detail of usage that brought a previously working unit to this state and conducting failure analysis on the device to ensure this doesn't become a trend. Once we have the board back in our hands we can hook it up via serial and other means to diagnose the fault. It's really important in this early stage that we gather as much information on the unit as possible. I'm very sorry it stopped working and I assure you we'll get it solved. 1 Quote Link to comment Share on other sites More sharing options...
cheeto Posted December 30, 2015 Share Posted December 30, 2015 No need for alarm. I'm sure the hardware is good on almost all of these devices. Unfortunately things do happen like every product that exist. Rest assured you'll have your issue resolved. The guys @ Hak5 really prioritize quality & service. Cheers Quote Link to comment Share on other sites More sharing options...
turtlebacon Posted December 30, 2015 Author Share Posted December 30, 2015 Thanks for the great support Darren. I'm not sure what caused the failure and if I could tell you more I would. Some additional details.. I know I was running PineAP + tcpdump and bridged ethernet to my mac. I was using a powered USB hub to power the nano since my macbook doesn't have two native ports next to each other. Worked great for hours and then randomly the AP disappeared, eth2 disappeared, and I was unable to get the device to work after that. Looking forward to continued usage and development of the nano. I'm sure this was just a fluke / early development issue. The product was working VERY well until the hiccup. Sincerely turtlebacon Quote Link to comment Share on other sites More sharing options...
turtlebacon Posted January 12, 2016 Author Share Posted January 12, 2016 This is now en route to you guys. Curious to find out what went wrong. Quote Link to comment Share on other sites More sharing options...
sotiria Posted February 1, 2016 Share Posted February 1, 2016 Turtle, did anyone get back to you on this as to what was the root cause? I'm having the same issues you did Quote Link to comment Share on other sites More sharing options...
Sharp Posted June 7, 2017 Share Posted June 7, 2017 On 12/29/2015 at 10:57 PM, turtlebacon said: So I was just using my nano (have put a lot of use on it in last 48 hours) .. then randomly it quit working. I had it in the case so I couldn't check the lights.. but after pulling it out and etc. no matter how I try to power it I can't get it to turn on. I had PineAP running and was doing a tcpdump when it crashed. I've tried the USB cable provided on multiple computers - also tried the pineapple juice battery which worked on day 1 and is fully charged + on.. and it's not turning the device on either. Any thoughts? Can you help? Ive just had the same experience, i was using mine to set up my landing page for the next day, next morning test to see if i can make any last minuet changes and it wouldn't power on. No power would travel through the UBS port on either side of the device no matter what i tried DX any help anyone? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.