The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: module-init-tools (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Ping, this migt be causing issue when using the mlx4 driver today.
Ubuntu 16.04 Xenial
4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64
x86_64 GNU/Linux
The following file is no longer needed, mlx4_core and mlx4_en will be loaded
properly automatic
cat /etc/modprobe.
Must have had a brain freeze or something, I rebuild my initramfs with belo and
it worked after boot.
update-initramfs -k `uname -r` -c
The point that the default /etc/modprobe.d/mlx4.conf should be removed
still stands, I'll report a new bug to kmod I guess.
--
You received this bug notificati
Hi,
This Fix is for old releases that doesn't include mlx4_en in their initramfs.
Now, that the initrd include the mlx4_en, so no need to creating a mlx4.conf
file with softdep mlx4_core post: mlx4_en
After removing this file we see that mlx4_en loaded after boot due to mlx4_core
request a modul
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: module-init-tools (Ubuntu Quantal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: maas
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To manage notifi
Not sure this deserves a bug on maas at all, actually, since there's
nothing in the maas codebase to change. However, can it be made fix
released now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/111
I'd call this "fix-committed" until we have a 'released' ephemeral image
that contains the changes. You're welcome to dis-agree, but I consider
daily builds kind of like "trunk commits".
** Changed in: maas
Status: Fix Released => Fix Committed
--
You received this bug notification beca
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To manage n
This bug was fixed in the package kmod - 9-2ubuntu7
---
kmod (9-2ubuntu7) raring; urgency=low
* Add /etc/modprobe.d/mlx4.conf for loading mlx4_en when mlx4_core
gets loaded (LP: #1115710).
-- Scott MoserTue, 05 Feb 2013 15:36:49 -0500
** Changed in: kmod (Ubuntu Raring)
** Branch linked: lp:ubuntu/raring-proposed/kmod
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To manage notifications abo
There are now ephemeral images at
http://maas.ubuntu.com/images/ephemeral/daily/raring/20130207/
that should have the mellanox driver inside the initramfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I'm marking maas as 'fix-committed'. the maas ephemeral image builder now:
* works around the lack of mlx4.conf if it is not present (so mlx4_en will be
loaded in initramfs)
* builds initramfs with MODULES=netboot.
daily ephemeral images should start to pick those changes up.
** Changed in: m
raring fix will be in kmod, not in module-init-tools (so invalid for
raring/module-init-tools)
** Also affects: module-init-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: module-init-tools (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects:
Conversation today with infinity in #ubuntu-devel
http://irclogs.ubuntu.com/2013/02/07/%23ubuntu-devel.html .
He suggested removing the auto-loading of the mlx4_ib at least for now. That
avoids pulling infiniband stack into initramfs.
Also, he pointed out that kmod (raring) does not have the is
** Also affects: kmod (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
T
2 other bits of info here
a.) Thanks to entropyworks, someone has actually verified this with hardware
present
b.) after adding or removing /etc/modprobe.d files (or /etc/modules) you really
need to update-initramfs. This is because if the module gets loaded in the
initramfs without the 'instal
** Branch linked: lp:~smoser/maas/maas.ubuntu.com.images-ephemeral
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To manage
OK. so, I basically had 2 choices for modprobe.d auto_loading of
mlx4_en upon usage of mlx4_core. Neither was perfect.
A.) "softdep mlx4_core post: mlx4_en mlx4_ib"
The softdep route hits what it seems to me to be a bug in 12.04 in modprobe
or update-initramfs. The updating of initramfs gives w
** Branch linked: lp:~smoser/maas/maas.ubuntu.com.images-
ephemeral.lp1115710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
** Description changed:
The Mellanox Ethernet card module is not being loaded in the ephemeral
images, which causes enlisting/commissioning to fail to boot the root
image from ISCSI, given that the interface is not loaded.
+
+ Related bugs:
+ * bug 1015339: installer initrd missing kernel
more discussion in IRC, slangasek suggests he'd prefer modprobe.d configuration.
The attached branches do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network
** Branch linked: lp:~smoser/ubuntu/precise/module-init-tools/lp-1115710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To
** Branch linked: lp:~smoser/ubuntu/quantal/module-init-tools/lp-1115710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To
** Branch linked: lp:~smoser/ubuntu/raring/kmod/lp-1115710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115710
Title:
Mellanox mlx4_en network driver is not automatically loaded
To manage notific
Discussion in IRC at [1], with the following pulled from the
"Mellanox OFED Stack for Linux User's Manual" [2]:
| mlx4_core
| Handles low-level functions like device initialization and firmware
| commands processing. Also controls resource allocation so th at the
| InfiniBand and Ethernet func
Hi Guys,
According to the user manual described by smoser:
By default, the mlx4_en (Ethernet) driver is not loaded. To change this, edit
the file /etc/
infiniband/openib.conf and modify the MLX4_EN_LOAD parameter as follows:
# Load MLX4_EN module
MLX4_EN_LOAD=yes
This is for RH though...
Leo
so it seems less straightforward than i had originally thought. the
kernel modules don't automatically load. that seems by design "Mellanox
OFED Stack for Linux User’s Manual" [1]. So i'm not sure how the
installer (or maas) should know that this should happen. The mlx4_core
can be used both by i
28 matches
Mail list logo