Thanks Zoran, I have tools to test it, I'll try it, it will be a long
journey though.
Thank you.
- jupter
On 7/16/19, Zoran Stojsavljevic wrote:
> Hello Jupiter,
>
> I actually continued this topic initiated by Moritz, to find out how
> you and me and somebody else also can build the yocto buil
Hello Jupiter,
I actually continued this topic initiated by Moritz, to find out how
you and me and somebody else also can build the yocto build system
with bundled rescue kernel into the rootfs.
My target architecture I am playing with is armv7 A8 (BBB), since I am
experimenting with it.
I actua
Hi Zoran,
On 7/12/19, Zoran Stojsavljevic wrote:
> Moritz,
>
> Thank you very much for this reply. It makes it very clear... What is
> the current State of Affairs for the topic.
>
> Let us see if there will be the improvement to this topic. I'll
> document this on one of my private GitHubs. And
Hey,
On 13.07.19 13:53, JH wrote:
Hi Moritz,
Thanks for your explanation, I know the copy from your script is for
an example, Did you get the zImage-initramfs? I'll double check to
follow your and Zoran documents.
Yes I have a working initramfs now. As I said the main problem for me
was that I
Hi Moritz,
Thanks for your explanation, I know the copy from your script is for
an example, Did you get the zImage-initramfs? I'll double check to
follow your and Zoran documents.
Thank you.
- jupiter
--
___
yocto mailing list
yocto@yoctoproject.org
h
On Fri, 12 Jul 2019 at 15:38, Moritz Porst wrote:
> If I use the .wic image, APPEND is ignored. You need to write your own
> kickstart file for this and include --append option. This usually means
> copy what you need from existing files (check license compliance) and
> add what you need. See the
Hey Jupiter,
you seem to confuse a few concepts, at least as far as I understand
Am 12.07.2019 um 14:53 schrieb JH:
Hi Moritz,
On 7/12/19, Moritz Porst wrote:
Hey
On 12.07.19 10:05, JH wrote:
BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwa
Hi Moritz,
On 7/12/19, Moritz Porst wrote:
> Hey
>
> On 12.07.19 10:05, JH wrote:
>>> BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
>> break=premount quiet rootwait rootwait rootfstype=ext4
>> console=ttyS0,115200 console=tty0
>>
>> Which file did you add kernel boot comm
Hello Scott (Rifenbark),
Could you, please, document somewhere (YOCTO-Mega-Manual for example)
this topic (booting to YOCTO initramfs rescue shell), as we are
discussing it?
It would be very beneficial to YOCTO WWW audience, don't you agree?
Thank you,
Zoran
___
On Fri, Jul 12, 2019 at 10:1
Hey
On 12.07.19 10:05, JH wrote:
BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
console=ttyS0,115200 console=tty0
Which file did you add kernel boot command for bootargs, bootcmd, etc?
I use meta-freescale, but I c
> BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwait rootwait rootfstype=ext4
console=ttyS0,115200 console=tty0
Which file did you add kernel boot command for bootargs, bootcmd, etc?
I use meta-freescale, but I could not find BOOT_IMAGE is defined
Hi Moritz,
I could not find zImage-initramfs:
$ grep zImage tempfile
ARCH_DEFAULT_KERNELIMAGETYPE="bzImage"
KERNEL_IMAGETYPE="bzImage"
KERNEL_IMAGETYPES="bzImage"
QB_DEFAULT_KERNEL="bzImage"
$ grep zImage-initramfs tempfile
$ grep INITRAMFS_IMAGE_BUNDLE tempfile
# $INITRAMFS_IMAGE_BUNDLE
INIT
Forgot to CC Jupiter and the most important thing:
PACKAGE_INSTALL += "initramfs-module-debug" (To my understanding this
enables the rescue shell)
On 12.07.19 08:22, Moritz Porst wrote:
Hey,
The only thing I can add to what I already said is my
"core-image-minimal-initramfs.bbappend":
PACKAG
Hey,
The only thing I can add to what I already said is my
"core-image-minimal-initramfs.bbappend":
PACKAGE_INSTALL += "\
busybox \
base-files \
base-passwd \
bash \
util-linux-
Moritz,
Thank you very much for this reply. It makes it very clear... What is
the current State of Affairs for the topic.
Let us see if there will be the improvement to this topic. I'll
document this on one of my private GitHubs. And archive this email.
Zoran
___
On Thu, Jul 11, 2019 at 12:
Hello Zoran, Jupiter and list
The configuration you sent seems to be correct.
As I already said initramfs seems overly complicated in yocto. the most
important thing to note is that 2 kernel images are created, one is
called bzImage (in my case) an the other bzImage-initramfs. However only
the b
Hello Moritz,
I need here some help from you. I'll try to reconstruct the parts of
the local.conf you are using, so I (and Jupiter) can understand what
should we do to also bundle kernel image with initramfs, to end up in
Dracut/rescue shell.
Here is what I anticipate after reading several YOCTO
Hello,
I think I found the issue. ( see below )
On 01.07.19 15:57, Zoran Stojsavljevic wrote:
Hello Moritz,
Too hot here, in Belgrade... Where I am resting for the Time being
(actually, this message given to my invisible spying security "angels"
on this list)... :-) Projected +38C degrees toda
Hello Moritz,
Too hot here, in Belgrade... Where I am resting for the Time being
(actually, this message given to my invisible spying security "angels"
on this list)... :-) Projected +38C degrees today. Too hot for this
too old Siberian untouchable bobcat!
> I started from the core-image-minimal
Hey,
So I have proceeded a tiny bit.
What I did was to copy the core-image-minimal-initramfs.cpio.gz to my
/boot partition and boot using (EFI grub):
linux /bzimage
initrd /initramfs.cpio.gz
This way the boot process starts and at some point it says "can't find
rootfs.img, dropping to a shell".
Hello Zoran,
thanks for your answer
On 28.06.19 14:26, Zoran Stojsavljevic wrote:
> INITRAMFS_IMAGE = /*"core-image-minimal-initramfs"*/
> INITRAMFS_IMAGE_BUNDLE = "1"
...
> You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I
Some hints...
[1] Kernel command line: BOOT_IMAGE=/
> INITRAMFS_IMAGE = *"core-image-minimal-initramfs"*
> INITRAMFS_IMAGE_BUNDLE = "1"
...
> You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I
Some hints...
[1] Kernel command line: BOOT_IMAGE=/bzImage
root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f
break=premount quiet rootwai
Hello,
I currently try to deploy a single rootfs update mechanism for my
embedded device. I can't boot to initramfs using either "break" or
"break=premount" (without quotes...). I tried this in systemd-boot and
grub-efi (always efi boot) but the boot process just continues normally.
If I insert at
23 matches
Mail list logo