Re: [opensuse-arm] cubox-i -> boot from e-sata
Hi guys, thank you both for your help. My partition resize to create a separated home partition must have broken something in the process. Indeed, I dd'ed the image on the hard disk and immediately after I booted the cubox-i. It was sufficient to launch the following commands: setenv boot_targets sata0 boot And it booted from eSATA just fine. Thank you again. Alessio Il giorno mer 14 ago 2019 alle ore 10:32 Guillaume Gardet ha scritto: > > Hi, > > > -Original Message- > > From: Miklos Vajna > > Sent: 10 August 2019 15:37 > > To: Alessio Adamo > > Cc: OS-arm > > Subject: Re: [opensuse-arm] cubox-i -> boot from e-sata > > > > Hi Alessio, > > > > On Thu, Aug 08, 2019 at 11:19:26PM +0200, Alessio Adamo > > wrote: > > > So I thought I would just dd the cubox-i image on the hard disk and > > > boot it via 'run bootcmd_sata' or something like that (I'm going by > > > heart now), but it looks like u-boot scanning doesn't find any > > > bootable partition. The same image works on mmc. > > > Do you know why is that? > > It should work ok by dd'ing the raw image to the hard disk. I used that on a > Beglebone Black with internal emmc a while ago. > Maybe the boot_targets value in u-boot would need to be updated to re-order > the boot list, if you want to boot from sata first and and just use mmc as a > fallback? > > Cheers, > Guillaume > > > > > I'm not sure about the details, but I have a similar setup (openSUSE Leap > > 15.0, > > cubox-i, and not e-sata but USB disk as a root partition), and /boot has to > > be on > > mmc that way, too. > > > > Perhaps you can use the same trick (mount the mmc as /boot), to work around > > this problem, at least then you don't have to copy around the kernel / > > initrd after > > an update. > > > > Regards, > > > > Miklos > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] cubox-i -> boot from e-sata
Hi,
> -Original Message-
> From: Miklos Vajna
> Sent: 10 August 2019 15:37
> To: Alessio Adamo
> Cc: OS-arm
> Subject: Re: [opensuse-arm] cubox-i -> boot from e-sata
>
> Hi Alessio,
>
> On Thu, Aug 08, 2019 at 11:19:26PM +0200, Alessio Adamo
> wrote:
> > So I thought I would just dd the cubox-i image on the hard disk and
> > boot it via 'run bootcmd_sata' or something like that (I'm going by
> > heart now), but it looks like u-boot scanning doesn't find any
> > bootable partition. The same image works on mmc.
> > Do you know why is that?
It should work ok by dd'ing the raw image to the hard disk. I used that on a
Beglebone Black with internal emmc a while ago.
Maybe the boot_targets value in u-boot would need to be updated to re-order the
boot list, if you want to boot from sata first and and just use mmc as a
fallback?
Cheers,
Guillaume
>
> I'm not sure about the details, but I have a similar setup (openSUSE Leap
> 15.0,
> cubox-i, and not e-sata but USB disk as a root partition), and /boot has to
> be on
> mmc that way, too.
>
> Perhaps you can use the same trick (mount the mmc as /boot), to work around
> this problem, at least then you don't have to copy around the kernel / initrd
> after
> an update.
>
> Regards,
>
> Miklos
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
N�r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�Ǩ�
Re: [opensuse-arm] cubox-i -> boot from e-sata
Hi Alessio, On Thu, Aug 08, 2019 at 11:19:26PM +0200, Alessio Adamo wrote: > So I thought I would just dd the cubox-i image on the hard disk and > boot it via 'run bootcmd_sata' or something like that (I'm going by > heart now), but it looks like u-boot scanning doesn't find any > bootable partition. The same image works on mmc. > Do you know why is that? I'm not sure about the details, but I have a similar setup (openSUSE Leap 15.0, cubox-i, and not e-sata but USB disk as a root partition), and /boot has to be on mmc that way, too. Perhaps you can use the same trick (mount the mmc as /boot), to work around this problem, at least then you don't have to copy around the kernel / initrd after an update. Regards, Miklos signature.asc Description: Digital signature
