I bet the fsck is doing it. Does it provide any feedback as to what is going on? It is had to tell what is going on because it stops at the bottom of my screen, so I can't really read it.
The only file I need is the mach_kernel, right? Scott D. Davilla wrote: >> Hi Scott, >> >> Where is the latest version of the bootloader? The front page points to >> .6 here: >> >> http://atv-bootloader.googlecode.com/files/recovery-0.6.tar.gz >> >> However you provide a link to a newer version that supports vfat here: >> >> http://atvusb-creator.googlecode.com/svn/trunk/atvusb-creator/payloads/atv_recv.7z >> >> Vfat does indeed work fine and now my boot menus also work with this >> image, but I'm wondering if there is still something newer. One thing I >> noticed with this version it it seems to take a while to find the >> boot_linux.sh file. >> > > The latest is the one used in atvusb-creator. It can be used > interchangeably with the atv-bootloader one. Have not had time to > update the atv-bootloader one but sound like I need to queue that > higher for recent distros. > > Not sure why it takes longer to find boot_linux.sh except it is doing > an fsck before mounting partitions. I don't remember if all partition > formats are handled this way. It was aimed at hfsplus partitions and > their nature to mount read-only if dirty. > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/atv-bootloader?hl=en -~----------~----~----~----~------~----~------~--~---
