For the details of the differences between Commission Test and Deploy I
would have to defer to the MAAS team. I'm using the official maas.io
images only for the tests listed in the document.
I would be happy to provide kernel logs but I do not know how to do this
for the Ephemeral OS. It is under
What is different about Commission, Test and Deploy? What we really need
to know is what kernel, initrd, DTB, firmware and config.txt are in use
for the different stages. We also need kernel logs. Curtin logs are
useless for figuring out why the device is not found.
--
You received this bug
I have added details of the USB devices that I used in the tests here
https://docs.google.com/document/d/1XlTFqijiYvNdWdSfc79N0_-2SdNRzpMZ8L4Z61GYUjg/edit?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a little more information on this. It seems that it affected by
the type of USB drive I am using
https://docs.google.com/document/d/1XlTFqijiYvNdWdSfc79N0_-2SdNRzpMZ8L4Z61GYUjg/edit?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
triaging after discussion with MAAS PM, could well be a curtin bug that
needs shooting. pinging Adam Collard on this one for handling
recommendations.
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
They are completely different. Raw images that you simply copy (dd) to
an SD card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964082
Title:
MAAS deployment to raspberry pi fails for release
Thanks again,
Will I be able to point MAAS at one of these official images or are they
a completely different form?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964082
Title:
MAAS deployment to
Probably. But it's not supported neither by the Pi foundation nor
Canonical.
Regarding the kernel/image: We have dedicated and official Ubuntu raspi
kernels and preinstalled server and desktop images. What you seem to be
using via MaaS is the generic arm64 kernel and image, which are not
Thanks Juerg.
We are using a UEFI 'firmware; for RPI (https://github.com/pftf/RPi4).
I believed that this allowed the RPI to use a generic OS.
Is that not true?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So you're booting the generic kernel/initrd and the generic arm64 image
on Pis? This is in no way supported and quite frankly I'm surprised that
it even works.
** Changed in: linux-raspi (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
Hi Jeurg,
Below is what is reported in the MAAS logs the /image directory comes
from https://images.maas.io/ephemeral-v3/stable/impish/arm64 I assume.
--
Tue, 08 Mar. 2022 20:22:35 User starting deployment - (admin)
Tue, 08 Mar. 2022 20:18:30 HTTP Request -
Where do you get the kernel and initrd for netbooting from?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964082
Title:
MAAS deployment to raspberry pi fails for release 21.10
To manage
Thanks for the rapid response.
You are almost certainly correct about missing kernel modules. I am
using the default 21.10 OS image that MAAS uses when you select the
standard 'mass.io' image source
(https://images.maas.io/ephemeral-v3/stable/impish/arm64).
Since I'm at the ephemeral phase of
dmesg or journal from working and non-working ephemeral environments are
needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964082
Title:
MAAS deployment to raspberry pi fails for release 21.10
It could be missing drivers or firmware, it would be nice to see a dmesg
or lsmod from a working system with said USB disk & the non-working
system.
I.e. to identify if 21.10 is somehow missing some kernel modules, or
firmware.
Note that in 21.10 we have split raspi modules into two packages,
15 matches
Mail list logo
