Thread: You can't break it, they said. Try, they said.
View Single Post
  #6   Spotlight this post!  
Unread 01-10-2015, 05:42 PM
taichichuan's Avatar
taichichuan taichichuan is offline
Software Mentor
AKA: Mike Anderson
FRC #0116 (Epsilon Delta)
Team Role: Mentor
  
Join Date: Feb 2010
Rookie Year: 2010
Location: Herndon, VA
Posts: 328
taichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud of
Send a message via AIM to taichichuan
Re: You can't break it, they said. Try, they said.
Hmm... OK, assuming you can get to a mode where port 22 works, log in via ssh (e.g., putty on WinDoze) as "admin" with no password. Once you're in, issue the command "dmesg" and capture the output. Then paste that into CD so we can take a look at the output of the boot cycle.

Additionally, do you have the serial port hooked up by any chance? If the serial console is enabled, you should be able to capture the boot sequence via Hyperterm, putty or some similar terminal emulator. That info would be most useful in determining what's going on during the Linux boot cycle. At least with that, we should also be able to see the boot loader code running.
Reply With Quote