great!  have fun!

Dwezzel wrote:
> Ok now...I can boot with MythBuntu 8.10.  I found what my problem
> was...a corrupted USB drive...
>
> Thx all for your help and patience !! =)
>
> Dwe
>
> On Mar 18, 5:07 pm, Dwezzel <[email protected]> wrote:
>   
>> Thx for your Help...
>>
>> I've tried with Mythbuntu 8.10, 8.04.1...always the same
>> results..maybe tonight I will try with a fresh copy...just to be
>> sure...
>>
>> Dwe =)
>>
>> On 18 mar, 16:58, Derek Keefe <[email protected]> wrote:
>>
>>     
>>> well then I don't know what to tell you.  my feeling is the contents of
>>> /dev/sdb3 are not complete and/or you have an issue with the kexec command.
>>>       
>>> try recopying the iso contents over again.  you are trying mythbuntu
>>> 8.04, right?
>>>       
>>> I'll see if I can find my boot_linux.sh script tonight if I get a chance.
>>>       
>>> Dwezzel wrote:
>>>       
>>>> Yep...everything is there !!
>>>>         
>>>> casper, .disk, ...
>>>>         
>>>> Dwe
>>>>         
>>>> On 18 mar, 16:51, Derek Keefe <[email protected]> wrote:
>>>>         
>>>>> ok.  so when you mount /dev/sdb3 do you see vmlinuz and initrd.gz in
>>>>> casper/?
>>>>>           
>>>>> Dwezzel wrote:
>>>>>           
>>>>>> AHHH   Ok...Yeah, it is set to none...so, I'm able to boot from my
>>>>>> USB...and telnet into it..to launch my kexec line...
>>>>>>             
>>>>>> Dwe
>>>>>>             
>>>>>> On 18 mar, 16:39, Derek Keefe <[email protected]> wrote:
>>>>>>             
>>>>>>> there is a file on the recovery part called boot.com.plist or something
>>>>>>> like that.  you need to set the atv boot parameter to manual or none if
>>>>>>> you want it to boot to the telnet prompt.
>>>>>>>               
>>>>>>> Dwezzel wrote:
>>>>>>>               
>>>>>>>> boot.com.... file set to   ????????  What is that ??  I didn't see
>>>>>>>> that anywhere on the howtos...
>>>>>>>>                 
>>>>>>>> Dwe
>>>>>>>>                 
>>>>>>>> On 18 mar, 16:06, Derek Keefe <[email protected]> wrote:
>>>>>>>>                 
>>>>>>>>> does the atv boot to the atv-bootloader login prompt?  can you telnet 
>>>>>>>>> to
>>>>>>>>> it?  what do you have the boot.com.... file set to?
>>>>>>>>>                   
>>>>>>>>> Dwezzel wrote:
>>>>>>>>>                   
>>>>>>>>>> This is what I've done 
>>>>>>>>>> fromhttp://code.google.com/p/atv-bootloader/wiki/BootingLiveCD
>>>>>>>>>> but adapted for Mythbuntu and my sdb3 partition :
>>>>>>>>>>                     
>>>>>>>>>> # mount the iso
>>>>>>>>>> mkdir iso
>>>>>>>>>> mount -o loop ubuntu-8.04-desktop-i386.iso iso
>>>>>>>>>>                     
>>>>>>>>>> # mount your USB flash drive with
>>>>>>>>>> #   atv-bootloader on 1st partition,
>>>>>>>>>> #   empty ext3 on 2nd partition.
>>>>>>>>>> mkdir usb
>>>>>>>>>> mount /dev/sdb2 usb
>>>>>>>>>>                     
>>>>>>>>>> # copy selected contents of the iso into the flash
>>>>>>>>>> # ".disk" is important as this is what "casper" the
>>>>>>>>>> # Ubuntu initrd used to find valid iso contents
>>>>>>>>>> #
>>>>>>>>>> cd iso
>>>>>>>>>> cp -rf casper dists install pics pool preseed .disk ../usb
>>>>>>>>>> cp isolinux/isolinux.cfg md5sum.txt README.diskdefines ../usb
>>>>>>>>>> cp casper/vmlinuz casper/initrd.gz install/mt86plus ../usb
>>>>>>>>>>                     
>>>>>>>>>> # cd into the usb and make some changes
>>>>>>>>>> cd ../usb
>>>>>>>>>> mv isolinux.cfg syslinux.cfg
>>>>>>>>>> sed -i -e 's:/casper/::g' -e 's:/cdrom/::g' -e 's:/install/::g'
>>>>>>>>>> syslinux.cfg
>>>>>>>>>>                     
>>>>>>>>>> # Now after atv-bootloader boots, telnet in and
>>>>>>>>>>                     
>>>>>>>>>> mkdir tmp
>>>>>>>>>>                     
>>>>>>>>>> mount /dev/sdb2 tmp
>>>>>>>>>>                     
>>>>>>>>>> kexec --load tmp/casper/vmlinuz --initrd=tmp/casper/initrd.gz --
>>>>>>>>>> command-line="preseed/ubuntu.seed boot=casper 
>>>>>>>>>> initrd=/casper/initrd.gz
>>>>>>>>>> nosplash vesa video=vesafb"
>>>>>>>>>>                     
>>>>>>>>>> kexec -e
>>>>>>>>>>                     
>>>>>>>>>> And bingo into the Ubuntu LiveCD.
>>>>>>>>>>                     
>>>>>>>>>> Dwe
>>>>>>>>>>                     
>>>>>>>>>> On 18 mar, 15:54, Derek Keefe <[email protected]> wrote:
>>>>>>>>>>                     
>>>>>>>>>>> did you just copy the .iso file to sdb3 or did you actually copy the
>>>>>>>>>>> _contents_ of the iso to sdb3?
>>>>>>>>>>>                       
>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>                       
>>>>>>>>>>>> I have only 3 partitions on my USB drive.
>>>>>>>>>>>>                         
>>>>>>>>>>>> sdb is the drive
>>>>>>>>>>>> sdb1 = recovery bootable
>>>>>>>>>>>> sdb2 = my backup from my original ATV
>>>>>>>>>>>> sdb3 = my ISO image prepared to launch with Kexec
>>>>>>>>>>>>                         
>>>>>>>>>>>> On 18 mar, 15:47, Derek Keefe <[email protected]> wrote:
>>>>>>>>>>>>                         
>>>>>>>>>>>>> why do you have 4 partitions on your usb drive?
>>>>>>>>>>>>>                           
>>>>>>>>>>>>> you mount /dev/sdb3
>>>>>>>>>>>>>                           
>>>>>>>>>>>>> I only use 2 and mount /dev/sdb1 (I think).
>>>>>>>>>>>>>                           
>>>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>>>                           
>>>>>>>>>>>>>> Hi Derek,
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> yes, I copied the .disk/ too...I just followed the Howto that I 
>>>>>>>>>>>>>> wrote
>>>>>>>>>>>>>> on the first post of this thread :
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> http://code.google.com/p/atv-bootloader/wiki/BootingLiveCD
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> Maybe I mist something....I really don't know...
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> On 18 mar, 14:12, Derek Keefe <[email protected]> wrote:
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>>> Have you gotten any version linux to boot on your atv?
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>> Did you copy over the .disk/ stuff too?
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>> I don't use the .cfg files.  I'm guessing that is your problem.
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>>> Maybe my problem is in the "isolinux.cfg / syslinux.cfg" 
>>>>>>>>>>>>>>>> files.  I
>>>>>>>>>>>>>>>> really don't know...
>>>>>>>>>>>>>>>>  For Derek : No, the # is only because i Cut and Paste 
>>>>>>>>>>>>>>>> something from
>>>>>>>>>>>>>>>> me telnet session...
>>>>>>>>>>>>>>>>                                 
>>>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>>>                                 
>>>>>>>>>>>>>>>> On 18 mar, 09:45, Dwezzel <[email protected]> wrote:
>>>>>>>>>>>>>>>>                                 
>>>>>>>>>>>>>>>>> I've tried that too....same results....All the "kexec" config 
>>>>>>>>>>>>>>>>> line on
>>>>>>>>>>>>>>>>> one line....same as before....so, it's not that too...
>>>>>>>>>>>>>>>>>                                   
>>>>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>>>>                                   
>>>>>>>>>>>>>>>>> On 18 mar, 09:41, Derek Keefe <[email protected]> wrote:
>>>>>>>>>>>>>>>>>                                   
>>>>>>>>>>>>>>>>>> also, delete the "\"
>>>>>>>>>>>>>>>>>>                                     
>>>>>>>>>>>>>>>>>> it needs to be on one line.
>>>>>>>>>>>>>>>>>>                                     
>>>>>>>>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>>>>>>>>                                     
>>>>>>>>>>>>>>>>>>> Yeah...that's why I used 2 different versions of 
>>>>>>>>>>>>>>>>>>> Mythbuntu...and got
>>>>>>>>>>>>>>>>>>> the same results....Weird isn't it ??
>>>>>>>>>>>>>>>>>>>                                       
>>>>>>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>>>>>>                                       
>>>>>>>>>>>>>>>>>>> On 18 mar, 09:32, Derek Keefe <[email protected]> wrote:
>>>>>>>>>>>>>>>>>>>                                       
>>>>>>>>>>>>>>>>>>>> ethernet isn't your problem then.
>>>>>>>>>>>>>>>>>>>>                                         
>>>>>>>>>>>>>>>>>>>> it sounds like it can't find the initrd image or it is 
>>>>>>>>>>>>>>>>>>>> corrupted.
>>>>>>>>>>>>>>>>>>>>                                         
>>>>>>>>>>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>>>>>>>>>>                                         
>>>>>>>>>>>>>>>>>>>>> Hi Derek,
>>>>>>>>>>>>>>>>>>>>>                                           
>>>>>>>>>>>>>>>>>>>>> I don't know if my ethernet works...I can't have any X 
>>>>>>>>>>>>>>>>>>>>> server coming
>>>>>>>>>>>>>>>>>>>>> up...So, I can't install have Mythbuntu to be install...
>>>>>>>>>>>>>>>>>>>>> Kind of weird....
>>>>>>>>>>>>>>>>>>>>>                                           
>>>>>>>>>>>>>>>>>>>>> All I got is a prompt "initramfs)" and I can type "help" 
>>>>>>>>>>>>>>>>>>>>> and a list of
>>>>>>>>>>>>>>>>>>>>> command that I can type appears.  And that's 
>>>>>>>>>>>>>>>>>>>>> all...nothing else...
>>>>>>>>>>>>>>>>>>>>>                                           
>>>>>>>>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>>>>>>>>                                           
>>>>>>>>>>>>>>>>>>>>> On 18 mar, 08:37, Derek Keefe <[email protected]> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>                                           
>>>>>>>>>>>>>>>>>>>>>> does your ethernet work?
>>>>>>>>>>>>>>>>>>>>>>                                             
>>>>>>>>>>>>>>>>>>>>>> I get the same warning and ethernet works fine.  you can 
>>>>>>>>>>>>>>>>>>>>>> ignore it.
>>>>>>>>>>>>>>>>>>>>>>                                             
>>>>>>>>>>>>>>>>>>>>>> Dwezzel wrote:
>>>>>>>>>>>>>>>>>>>>>>                                             
>>>>>>>>>>>>>>>>>>>>>>> Hi All...it's me again.
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> Here what I found when I tried with the "quiet" option 
>>>>>>>>>>>>>>>>>>>>>>> for the Kexec
>>>>>>>>>>>>>>>>>>>>>>> line.  It gave me something that I wasn't abale to see 
>>>>>>>>>>>>>>>>>>>>>>> at first...too
>>>>>>>>>>>>>>>>>>>>>>> much lines.  Here it is :
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> 8139cp 0000:03:03:0: This (id 10ec:8139 rev10) is not a 
>>>>>>>>>>>>>>>>>>>>>>> 8139C+
>>>>>>>>>>>>>>>>>>>>>>> compatible chip
>>>>>>>>>>>>>>>>>>>>>>> 8139cp 0000:03:03:0: Try the "8139too" driver instead.
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> Now that I know that, can I do something to use this ?? 
>>>>>>>>>>>>>>>>>>>>>>>  Is it
>>>>>>>>>>>>>>>>>>>>>>> something that Mythbuntu does not have ?  Is it related 
>>>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>>>> Mythbuntu ?  Or is it related with my ATV ?
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> I will try with a Ubuntu version...just in case....or 
>>>>>>>>>>>>>>>>>>>>>>> if someone habe
>>>>>>>>>>>>>>>>>>>>>>> an idea with this issue...
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> Dwe
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>> On Mar 17, 5:16 pm, Dwezzel <[email protected]> wrote:
>>>>>>>>>>>>>>>>>>>>>>>                                               
>>>>>>>>>>>>>>>>>>>>>>>> It's me again...
>>>>>>>>>>>>>>>>>>>>>>>>                                                 
>>>>>>>>>>>>>>>>>>>>>>>> I've tried with Mythbuntu-8.04.1...same 
>>>>>>>>>>>>>>>>>>>>>>>> results...Still getting back
>>>>>>>>>>>>>>>>>>>>>>>> to a prompt "initramfs)" or something like that...I 
>>>>>>>>>>>>>>>>>>>>>>>> can't be precise
>>>>>>>>>>>>>>>>>>>>>>>> because my
>>>>>>>>>>>>>>>>>>>>>>>>                                                 
>>> ...
>>>       
>>> plus de détails »
>>>       
>>     
> >
>   

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to