the lack of usb nic is because the xenial image does not have a "full
kernel" inside it . 14.04 maas images had linux-generic installed. So
if you were commissioning with hwe-t (ie, you had no need for a newer
hwe kernel) then your commissioning would get all the drivers in linux-
generic at its disposal.
We can add drivers/net/usb to the boot-intird and we'd have more drivers
at the disposal.
Can you try using this attached 'boot-kernel' and 'boot-initrd' ?
To do that, on the maas server:
kdir=/var/lib/maas/boot-resources/current/ubuntu/amd64/hwe-x/xenial/daily
for x in boot-initrd boot-kernel; do
[ -f "$kdir/$x.dist" ] || cp "$kdir/$x" "$kdir/$x.dist"
done
tar -C $kdir -xf test-kernel.txz
then restart maas cluster controller and try commission again.
For reference, the diff that produced this in maas-images was just:
http://paste.ubuntu.com/15270144/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1552378
Title:
Xenial doesn't see all cores nor usb network dongle
Status in maas-images:
Triaged
Status in linux package in Ubuntu:
Confirmed
Bug description:
When commissioning intel NUC's with MAAS 1.10 and the 16.04 Xenial image, the
systems report in with only 1 core, on a 4 core system, and the secondary
network interface (usb dongle), doesn't appear at all.
Note: When loading 16.04 desktop onto node0 (control node), all the cores are
seen and both secondary and tertiary usb network dongles are seen by the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1552378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
