Boots atvusb, but fails to find patchstick.sh and then looks for telnet

[GoogleCodeExporter]

What steps will reproduce the problem?
1. boot from atvusb
2. loads tux on ATV
3. get to looking for patchstick.sh then fails

What is the expected output? What do you see instead?
Expected it to load the packages.  Failed to load patchstick.sh

What version of the product are you using? On what operating system?
1.0b13
160GB Apple TV running newest software
MacBook Pro 13" running 10.6.3
Using a 1GB Sandisk Cruzer

Please provide any additional information below.
I downloaded 1.0.b.13 and it seems to have installed on the USB drive fine.  I 
then boot my ATV 
from the drive and I get tux on the ATV, then it starts to read down the list 
of commands until it 
gets to looking for patchstick.sh, then it fails.  It then goes into looking 
for telnet and discovery 
mode.  Almost like it is looking for an IP address.  It then gives me the eth0 
with no useable info 
and then the last line sits at penlinux or penbuntu and goes no further.

I erased the USB drive, re-formatted mac os x extended (journaled), re ran the 
installer and then 
booted from the USB and it stalls at the items I mention above.

The output on the USB drive looks exactly like the screenshot on the frontpage.

I'm an IT guy by trade and this is frustrating to get stuck on something that 
should be simple, 
HELP! 

Is this due to a non-compatible USB drive.  It boots fine, but then goes no 
further.  Really would 
like some help/ideas.

Thanks!

Original issue reported on code.google.com by ivone...@gmail.com on 24 Apr 2010 at 7:00

[GoogleCodeExporter]

Sometimes the detection of patchstick.sh is too quick. Try a different USB, or 
wait 
for telnetd to start (plug in an ethernet cable), telnet in and run 
patchstick.sh 
that way.

Original comment by Sam.Nazarko on 24 Apr 2010 at 5:13

[GoogleCodeExporter]

Thanks for the ideas.

I did plug in the ethernet, got an address and then was able to telnet into it 
and use root/root.

I found 4 partitions that after reading on the Issues (#14) that these are what 
I am seeing, and nothing else.

EFI -> /dev/sda1
Recovery-> /dev/sda2
OSBoot -> /dev/sda3
Media -> /dev/sda4

From Issue #14 I gather this is just the internal system info.  It does not 
seem to recognize my drive at all.  I 
assume just use another USB drive?  What's weird is how it will boot and get so 
far and then just crap out...

You suggest telnet then run patchstick.sh How would I do that, I am no computer 
newb, but definitely not a 
linux/command line guy.

Thanks!

Original comment by ivone...@gmail.com on 24 Apr 2010 at 7:07

[GoogleCodeExporter]

Try a different USB if you think telnet is uncomfortable. 

If your on Windows:

Start > (Run*) > telnet.exe
type 'o'
enter IP of aTV - on the tv
enter the command "./patchstick.sh"
pull out usb when done
reboot

* = < Windows Vista only

Tell me how that goes.

Original comment by Sam.Nazarko on 25 Apr 2010 at 5:01

[GoogleCodeExporter]

I had the exact same problem with the same 1GB Sandisk Cruzer.  I tried a 4GB 
Gigaware USB Drive and it solved the problem .

Original comment by moabm...@gmail.com on 3 Oct 2010 at 2:21