trying to putty in

jd2157 Wrote:I'd try to find another ssh client to run. One option that comes to mind is Cygwin. It's kind of overkill, but if you install it (with the ssh packages available during install) then it'll give you another way to run an ssh client... and a lot more.

Guess you could always download a copy of putty, remove the old one and try a reinstall... shouldn't fix anything but it often does in Windows.

I installed tunnelier and tried to ssh into it and it gave me an error.. however I did get access via sftp and can see the files etc.. I jsut cant get into ssh to run any commands.

rflores2323 Wrote:I installed tunnelier and tried to ssh into it and it gave me an error.. however I did get access via sftp and can see the files etc.. I jsut cant get into ssh to run any commands.

Hadn't heard of tunnelier before, nice find. I tried it out, here's some detail:

Login tab: entered my atv2's IP as Host, user = root, pass = alpine (store pass in profile), initial method of password
Options tab: unchecked open SFTP

Then I clicked login and it opened the SSH terminal as expected. Maybe if you share the error that'll give some idea of what's going wrong. If you get any prompts re: being able to trust the host say yes.

I have a similar problem with one of my Apple TV2's. I connect with Putty and the window just closes after entering the password. On my other ATV2 it works fine.

There was some discussion as to whether it was caused by having initially jailbroken with the original tethered jailbreak and then re-jailbreaking with the untethered version. The one that fails with Putty was done that way. I purchased my other ATV2 after the untethered jailbreak was out so I just used that from the start.

I had a similar problem, and it was definitely related to doing a tethered jailbreak and then an un-tethered on top (which is not recommended, but hey, I'm lazy ).

If you can connect with WinSCP, then you should be able to rectify the situation. WinSCP allows you to send commands without actually starting a shell, and, for me at least, the problem was with bash. You can confirm this pretty easily by using your SFTP program (or WinSCP, or something similar), and viewing /var/log/syslog after attempting to log in. I saw something like this:

Quote:Apr 15 22:27:36 Apple-TV ReportCrash[93]: Formulating crash report for process sh[90]
Apr 15 22:27:36 Apple-TV sshd[89]: DEAD_PROCESS: 90 ttys001
Apr 15 22:27:37 Apple-TV ReportCrash[93]: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/sh_2011-04-15-222736_Apple-TV.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0

You can then view the crash report to see exactly what happened:

Quote:Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000
Crashed Thread: 0

Thread 0 Crashed:
0 libncurses.5.dylib 0x000c9312 0xb0000 + 103186
1 libncurses.5.dylib 0x000cc242 0xb0000 + 115266
2 libncurses.5.dylib 0x000cc49c 0xb0000 + 115868
3 libncurses.5.dylib 0x000c88d6 0xb0000 + 100566
4 sh 0x0006b650 0x1000 + 435792
5 sh 0x00056f6a 0x1000 + 352106
6 sh 0x0003a86a 0x1000 + 235626
7 sh 0x0000b71a 0x1000 + 42778
8 sh 0x000044b0 0x1000 + 13488
9 sh 0x000062a0 0x1000 + 21152
10 sh 0x00008914 0x1000 + 30996
11 sh 0x0000bc32 0x1000 + 44082
12 sh 0x000040a6 0x1000 + 12454
13 sh 0x00004162 0x1000 + 12642
14 sh 0x00004288 0x1000 + 12936
15 sh 0x00003e78 0x1000 + 11896
16 sh 0x0000202c 0x1000 + 4140

This suggests the problem is an incompatibility between ncurses and the shell (bash) that you are using when logging in. This can probably be fixed by rebuilding ncurses or bash.... but I took the easy way out and installed zsh (again, WinSCP allows you to connect and run commands without running a shell, so you can do apt-get install zsh), and then changed my default shell by editing /etc/master.passwd, and editing the line for 'root' (and mobile if you log in as mobile) so that the log in shell is /bin/zsh rather than /bin/sh.

I know exactly what the jailbreaks install, but installing one on top of the other has introduced some kind of incompatibility -- which I am sure could be fixed, but I didn't bother spending any more time on it... I'm not doing any scripting or anything on it, so zsh is just fine.

Hope this long winded post helps more than it confuses!

ahhh so that is what happen. I did have this atv2 tethered and then did the untethered jailbreak on top of it. SO that must be it. Will try to install zsh to see if that works or do you think this is necessary? I already have nito and xbmc installed. what else would I need the command line for?

how do I install zsh thru winscp?

If you connect using WinSCP you can click the Open Terminal button (ctrl-t), which allows you to enter commands. Then enter the command:

apt-get install zsh


After that, you will need to edit /etc/master.passwd, which you can do in WinSCP in the GUI.

I have been using WinSCP to send commands on the rare occasions that I need to. I figured I would just wait until all the bugs with the latest iOS are ironed out, the jailbreaks that go with it and then the XBMC code that will sit on top of it. Once all that is stable I'll restore the ATV2 with the latest firmware and go through the setup process again which would fix it.

ascl_ Wrote:I had a similar problem, and it was definitely related to doing a tethered jailbreak and then an un-tethered on top (which is not recommended, but hey, I'm lazy ).

If you can connect with WinSCP, then you should be able to rectify the situation. WinSCP allows you to send commands without actually starting a shell, and, for me at least, the problem was with bash. You can confirm this pretty easily by using your SFTP program (or WinSCP, or something similar), and viewing /var/log/syslog after attempting to log in. I saw something like this:


You can then view the crash report to see exactly what happened:



This suggests the problem is an incompatibility between ncurses and the shell (bash) that you are using when logging in. This can probably be fixed by rebuilding ncurses or bash.... but I took the easy way out and installed zsh (again, WinSCP allows you to connect and run commands without running a shell, so you can do apt-get install zsh), and then changed my default shell by editing /etc/master.passwd, and editing the line for 'root' (and mobile if you log in as mobile) so that the log in shell is /bin/zsh rather than /bin/sh.

I know exactly what the jailbreaks install, but installing one on top of the other has introduced some kind of incompatibility -- which I am sure could be fixed, but I didn't bother spending any more time on it... I'm not doing any scripting or anything on it, so zsh is just fine.

Hope this long winded post helps more than it confuses!

Maybe I'm missing something but why wouldn't you just backup your XBMC/userdata folder and jailbreak again rather than try to get zsh on the atv2?

There's no telling what other incompatibilities have been caused by jailbreaking a jailbroken atv2. Pretty sure you'd be better off resolving that issue first (i.e. restore iOS and jailbreak again) so your atv2 is in a known good state and going from there.

That would be the safest option, I was simply providing the information on how to get a log in shell working again in case anyone needed it.

(FWIW the system is working fine, but when the next official release of xbmc happens, I'll do exactly what you suggest).