The USB Linux boot would be great.  Ulitmately I would like to boot
without the USB stick but for now I will settle for sticking it.

On Jan 10, 10:29 pm, Robert Baptista <[email protected]> wrote:
> Sure, but I'm not sure which boot operation you're referring to. I do
> not boot the Apple OS. I normally boot with no usb drives attached to /
> dev/sda4 and 5 as shown on this site. But while I'm working on a test
> load I boot from a usb stick to a linux load on said usb stick.  Which
> boot config would you like? The standard linux boot with no usb stick
> (Mythbuntu 9.04), the usb linux boot on the usb stick(Ubuntu 9.10), or
> the usb linux installer boot on my installer stick?
>
> Robert
>
> On Jan 10, 6:47 pm, SchneiderIS <[email protected]> wrote:
>
>
>
> > Hi Robert,
>
> > Would you be willing to post how you setup your boot operations
> > including the contents of the files?
>
> > -Peter
>
> > On Jan 10, 7:26 pm, Robert Baptista <[email protected]> wrote:
>
> > > Apparently my brain is fried today. After looking through the
> > > boot_parser source I found no reference to hd(x,x). So I went back to
> > > my menu.lst file and noticed I had modified another part of the kernel
> > > line without knowing it. It is now fixed up(without an hd(x,x) line
> > > and all is good.
>
> > > My seed file will now take care of making a correct menu.lst file for
> > > Karmic/ATV automatically. Which ofcourse, might not end up being
> > > needed if someone updates the boot_parser to handle Grub2. :)
>
> > > Robert
>
> > > On Jan 10, 5:29 pm, Robert Baptista <[email protected]> wrote:
>
> > > > Nevermind, I figured out my problem. The kexec was happening
> > > > (partially) so it was not the patchstick fs that was read only.
> > > > Apparently hd(x,x) is needed in the menu.lst file for kexec parsing to
> > > > function properly. Was thinking that only kernel and initrd lines were
> > > > required.
>
> > > > Robert
>
> > > > On Jan 9, 6:47 am, SchneiderIS <[email protected]> wrote:
>
> > > > > Hi Robert,
>
> > > > > This is where my newbyism (I still find many things to be a mystery/
> > > > > voodo act so I cannot call myself an expert) holds me back from being
> > > > > of much use.  The only thing I can think of is that SDB needs to be
> > > > > "blessed"?  This is a complete guess though in that I have seen the
> > > > > term used online in order to make a partition available but I am not
> > > > > sure if this is a Apple OS only thing.  It does sound like you need to
> > > > > CHMOD the partition (recursively) at a minimum.
>
> > > > > My use of the third partition was strictly to load the LiveCD files
> > > > > onto and if memory serves me correct it was also a write permissions
> > > > > issue.
>
> > > > > On Jan 8, 9:06 pm, Robert Baptista <[email protected]> wrote:
>
> > > > > > Not sure I understand the use of the third partition. I have the 
> > > > > > boot-
> > > > > > loader installer stick working ok. It boots the ubuntu alternate
> > > > > > installer(/dev/sdb2), which I then install to /dev/sdc2 which is a
> > > > > > second flash drive. The kexec for the install is working ok (I don't
> > > > > > have casper since it's an alternate disk but I've modified kexec
> > > > > > accordingly).
>
> > > > > > When the install is done I remove the installer stick and am just 
> > > > > > left
> > > > > > with the stick that the installed os is on, as displayed below.
> > > > > > /dev/sdb1 HFSplus partition with atvrecv
> > > > > > /dev/sdb2 ext3 partition with the installed version of ubuntu.
>
> > > > > > However when /dev/sdb1 boots for some reason it is read only so the
> > > > > > patchstick cannot mkdir and mount sdb2 to perform the kexec into the
> > > > > > newly installed os. Now I could probably get the built-in hd to 
> > > > > > kexec /
> > > > > > dev/sdb2 but I'm only running this on a flash drive to test 
> > > > > > everything
> > > > > > before I rebuild/upgrade my atv's. I don't want this to happen to 
> > > > > > /dev/
> > > > > > sda when I'm ready to deploy.
>
> > > > > > Robert
>
> > > > > > On Jan 8, 5:05 pm, SchneiderIS <[email protected]> wrote:
>
> > > > > > > Hi Robert,
>
> > > > > > > I am just grabbing some time quickly on my laptop before my wife 
> > > > > > > takes
> > > > > > > over again.  Sorry I haven't replied to your earlier port.
>
> > > > > > > I have installed it from a flash card and I hope the following is 
> > > > > > > what
> > > > > > > you are trying to figure out (namely that I have understood your
> > > > > > > request).  You will need to either reformat the patchstick 
> > > > > > > partition
> > > > > > > or resize it and then create a third partition.  I did the latter 
> > > > > > > and
> > > > > > > had to do it from a linux machine (VirtualBox with Ubuntu 
> > > > > > > installed
> > > > > > > worked perfectly for this and more operations) since it needs to 
> > > > > > > be
> > > > > > > loaded on an ext2 or 3 formatted partition. With the partition in
> > > > > > > place simply take the contents of the Mythbuntu iso and copy it 
> > > > > > > onto
> > > > > > > the new partition.  With this approach I can boot into Ubuntu and 
> > > > > > > run
> > > > > > > the install.
>
> > > > > > > To reboot into the new partition you can use the following kernel
> > > > > > > lines (you may need to adjust the sdb3 to suit).
>
> > > > > > > mkdir /install
> > > > > > > mount /dev/sdb3 /install
>
> > > > > > > kexec --load /install/casper/vmlinuz --initrd=/install/casper/
> > > > > > > initrd.lz --command-line="preseed/ubuntu.seed boot=casper initrd=/
> > > > > > > casper/initrd.lz nosplash vesa video=vesafb"
>
> > > > > > > kexec -e
>
> > > > > > > Hope this helps.
>
> > > > > > > On Jan 8, 5:10 pm, Robert Baptista <[email protected]> wrote:
>
> > > > > > > > Has anyone successfully installed Ubuntu or derivative 9.10 
> > > > > > > > from the
> > > > > > > > alternate iso/cd to the ATV? I am trying to install it to a 
> > > > > > > > secondary
> > > > > > > > flashdrive on one of my Atv's for testing. The install 
> > > > > > > > completes with
> > > > > > > > no problem but after the reboot the atv-bootloader partition on 
> > > > > > > > the
> > > > > > > > flashdrive is read-only and thus cannot not mount and kexec the 
> > > > > > > > new
> > > > > > > > install.
>
> > > > > > > > This procedure worked fine for me using 9.04 and the standard
> > > > > > > > mythbuntu iso. So I'm not sure if it's something with the 
> > > > > > > > alternate
> > > > > > > > install or 9.10 and grub2. I'm installing grub to the MBR of 
> > > > > > > > the flash
> > > > > > > > drive as I believe the standard installer does. I've created a 
> > > > > > > > custom
> > > > > > > > menu.lst for the patchstick parser, but even trying to mount 
> > > > > > > > manually
> > > > > > > > I cannot since the fs is read only.
>
> > > > > > > > When I run gptsync it does say 'Status: Analysis inconclusive, 
> > > > > > > > will
> > > > > > > > not touch this disk' so I'm thinking it's hosing the partitions.
>
> > > > > > > > Any ideas?
> > > > > > > > Robert
-- 
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