Hey Paul,
The appliance-tools image I made gets stuck on a black screen
at startup. I'm using a raspberry pi 3b, and we've been building
these images inside of mock chroots natively on the rpi.
~Christopher Odom
On Fri, Nov 8, 2019 at 1:26 PM Paul Whalen <pwhalen(a)redhat.com> wrote:
>
> Hi Christopher,
>
> For armhfp we use appliance-tools, for aarch64 image-factory.
>
> What happened when you tried to boot the image made using
> appliance-tools?
>
> Paul
>
> ----- Original Message -----
> > Any updates on this? I found a bunch of Koji build configs, but I'm
> > not exactly sure how to replicate them.
> >
> > On Fri, Nov 1, 2019 at 11:56 AM Christopher Odom
> > <christopher.r.odom(a)gmail.com> wrote:
> > >
> > > Hello,
> > >
> > > I'm currently in the process of trying to generate a new image with
some
> > > custom kickstarts for the raspberry pi. I'm basing these off of the
> > > fedora-arm-minimal kickstart and I've sunk a bunch of time chasing
> > > anaconda errors, I'm wondering if anyone has any insight into what I
might
> > > be doing wrong? Here's the output from livemedia-creator:
> > >
> > > ```
> > > <mock-chroot> sh-5.0# . ./generate_raw_xz.sh flat-fedora.ks 30
> > > 2019-11-01 10:45:51,965: livemedia-creator v30.19-1
> > > 2019-11-01 10:45:51,967: selinux is Disabled
> > > 2019-11-01 10:45:52,642: disk_img = /var/lmc/lmc-disk-_fnubs4g.img
> > > 2019-11-01 10:45:52,643: Using disk size of 1994MiB
> > > 2019-11-01 10:45:52,648: Running anaconda.
> > > 2019-11-01 10:46:06,824: Starting installer, one moment...
> > > 2019-11-01 10:46:06,826: terminal size detection failed, using default
> > > width
> > > 2019-11-01 10:46:06,827: anaconda 30.25.6-4.fc30 for Linux 29
(pre-release)
> > > started.
> > > 2019-11-01 10:46:06,828: /var/run/anaconda.pid already exists, exiting
> > > 2019-11-01 10:46:07,324: Running anaconda failed: process
'['unshare',
> > > '--pid', '--kill-child', '--mount',
'--propagation', 'unchanged',
> > > 'anaconda', '--kickstart',
'/home/rpi/fedora-kickstarts/flat-fedora.ks',
> > > '--cmdline', '--loglevel', 'debug',
'--image',
> > > '/var/lmc/lmc-disk-_fnubs4g.img', '--remotelog',
'127.0.0.1:58155']'
> > > exited with status 1
> > > 2019-11-01 10:46:52,779: Install failed: novirt_install failed
> > > 2019-11-01 10:46:52,781: ERROR: Image creation failed: novirt_install
> > > failed
> > > 2019-11-01 10:46:52,782: Image creation failed: novirt_install failed
> > > <mock-chroot> sh-5.0#
> > > ```
> > >
> > > I've also looked at other ways of going about this process including:
> > >
https://fedoraproject.org/wiki/Architectures/ARM/Creating_Remixes
> > > Which produced an image, but I wasn't able to get it to boot.
> > >
> > > ~Christopher Odom
> > _______________________________________________
> > arm mailing list -- arm(a)lists.fedoraproject.org
> > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> >
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> >
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> >
>