Public bug reported:
This is more of a feature request for snapcraft. That is to have the
option with the kernel plugin so that we can use a debian package of the
kernel with all customizations done to it so that we don't have to
compile and recompile kernel from source to build the kernel .snap.
Public bug reported:
Please include the OpenNSL GPL modules with the Kernel.
These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
The latest SDK version is 6.5.6.
We would like to have the kernel modules included with the LTS Xenial kernel so
that we can provide these
** Project changed: clouddocs => openstack (Ubuntu)
** Changed in: openstack (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586076
Title:
Single Installer
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628241
Title:
Enable switchdev config parameter for Yakkety
To manage
** Package changed: linux (Ubuntu) => linux-signed (Ubuntu)
** Changed in: linux-signed (Ubuntu)
Milestone: None => ubuntu-16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628241
Title:
Public bug reported:
Hello,
The current packaged systemd for Yakkety does not have the Mellanox netdev udev
naming set for systemd patch installed (commit
4887b656c22af059d4e833de7b56544f24951184 from github.com/systemd/systemd.git).
The current version for zesty does. I installed the ppa for
The naming currently is ethXX where XX is a sequential number that does not
correlate with the port on the front panel. For example, eth0 will sometimes
correlate with port 30, and on the next reboot it will be port 6.
After the patch is installed, the devices are named enp3s0pXX where XX
The naming currently is ethXX where XX is a sequential number that does not
correlate with the port on the front panel. For example, eth0 will sometimes
correlate with port 30, and on the next reboot it will be port 6.
After the patch is installed, the devices are named enp3s0pXX where XX
Removing the mlx4.conf from kmod package is not going to cause a
regression of bug 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/1693503
Title:
Remove mlx4.conf
To manage
** Changed in: kmod (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693503
Title:
Remove mlx4.conf
To manage notifications about this bug go to:
Public bug reported:
We are working on Quanta WB2448 switch which uses Intel Broadwell CPU
complex. We are seeing boot crash when we are using xenial kernel. Below
is the crash log. As a result of this we are not able to mount the disk
and proceed with Linux bootup.
This issue is not seen on
** Changed in: linux-lts-xenial (Ubuntu)
Importance: Undecided => High
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kmod (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693503
Title:
Remove mlx4.conf
To manage notifications about this bug go to:
It has been 2 weeks and no updates. Bumping.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732713
Title:
Ubuntu 16.04.3 LTS KVM guest fails boot on Cavium ARM host
To manage notifications about
** Description changed:
KVM host is a Cavium ARM server running RHEL 7.4
Installing RHEL and Ubuntu 17.10 on KVM host succeeds, however, when
installing Ubuntu 16.04.3, the server hangs when booting up the installation.
Appears to be an issue with intitrd.
This happens with both ISO
Public bug reported:
KVM host is a Cavium ARM server running RHEL 7.4
Installing RHEL and Ubuntu 17.10 on KVM host succeeds, however, when installing
Ubuntu 16.04.3, the server hangs when booting up the installation. Appears to
be an issue with intitrd.
This happens with both ISO boot and PXE
Image of KVM Guest CPU usage during hang.
** Attachment added: "KVM Guest CPU usage"
https://bugs.launchpad.net/ubuntu/+bug/1732713/+attachment/5010039/+files/unnamed%20%281%29.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubuntu => linux-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732713
Title:
Ubuntu 16.04.3 LTS KVM guest fails boot on Cavium ARM host
To manage
Public bug reported:
I upgraded my laptop to Bionic but the display failed to work. I was able to
get into the grub menu on the install media and entered nouveau.modeset=0 which
has worked in previous versions of Ubuntu but with Bionic I get a blank
display. Sound works and I can hear Ubuntu
So I built a kernel from the Upstream LTS (4.17.3) and tried to apply
the patch, which failed. So I removed it and tried a clean build and was
able to get Xenial to boot up with this kernel. I then decided to
install Bionic and install this kernel on my laptop however, I noticed
that when I
I tried testing with the latest RC build of the 4.17 kernel from kernel.org
(Torvald's GIT) and built the kernel following the instructions here [1].
After installing the kernel and headers, it looks like it regressed and the
display did not work (backlight) and I could not switch terminals. I
[1] https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761261
Title:
nouveau/nvidia drivers do not work with display in Bionic on Asus
GL703VD Laptop
Trackpad and Graphics work with the spth-pincntrl-fix.diff patch on the
4.17 kernel, however, the wifi card does not work, and if you close the
lid or it goes to hibernate, the system becomes unresponsive.
I removed this kernel and am working again on the 4.15.0-20 kernel with
the patch.
--
You
** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735271
Title:
Update firmware for netronome SmartNICs
To manage
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719302
Title:
Please include mlx4 and mlx5 InfiniBand modules
To manage
Public bug reported:
Please include the OpenNSL GPL modules with the Kernel.
These modules
are located at https://github.com/Broadcom-Switch/OpenNSL.
The latest
SDK version is 6.5.12.
We would like to have the kernel modules included with the LTS Bionic
kernel so that we can provide these
** Package changed: ubuntu => linux-signed-hwe (Ubuntu)
** Changed in: linux-signed-hwe (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784014
Title:
** Changed in: libibverbs (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783775
Title:
[bionic] qemu-* depends on libibverbs
To manage notifications
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784014
Title:
UBUNTU18.04.1:Observing buffer I/O error while creating a
Correction: 4.15.0-24-generic not 4.15.0-25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775918
Title:
GL703VD Laptop DIsplay not working
To manage notifications about this bug go to:
It looks like the display issue in Bionic on the GL703VD laptop has been
fixed with the release of the 4.15.0-25-generic kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775918
Title:
GL703VD
I had this same problem with my laptop on 17.10. When I upgraded to the kernel
to 4.14 I did not receive the errors in the syslog, but the touchpad
responsiveness and functionality worked fine.
When I upgraded to 18.04 with kernel 4.15.0-24 it looks like it has regressed
and I am back to using
So, I read in a thread that someone was having something similar happen to them
and they built the 4.14 kernel and this fixed the issue. I decided to pull and
build the Bionic kernel from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic and
install that on my Artful laptop and now everything
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of
I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG
display, then flashes purple for a second (Grub menu splash before the Ubuntu
splash logo, which doesn't display on the laptop, but does on the HDMI display)
then goes blank and never comes online. Even pressing
** Description changed:
Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
using 3D) and the installer does not display. I have tried
nouveau.modeset=0 and nomodeset boot options to no avail. I was able to
** Attachment added: "lshw.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101640/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
using 3D) and the installer does not display. I have tried
nouveau.modeset=0 and nomodeset boot options to no avail. I was able to
finally
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101642/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lsmod_nvidia.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101641/+files/lsmod_nvidia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: nvidia-graphics-drivers-390 (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/1761261
Title:
nouveau/nvidia drivers do not work
I have noticed the same thing. I am running on 16.04 with the HWE 17.10 kernel
and monitor works.
I installed the bionic 4.14.0-17 kernel and I was able to still use the laptop
display. I tried the latest Bionic kernel (4.15.0-13) and it does not work.
During testing on another bug (LP:1738263)
It could be a backlight issue. I tried with the latest daily-build
(April 16, 2018) and I boot up with the nouveau.modeset=0 kernel param
and it shows the splash screen, and then I hear the login sound, and if
I turn off the lights in my office and look closely, I can see the
display, but it looks
So I patched the 4.15.0-15-generic kernel from kernel.ubuntu.com with
the supplied patch and then intstalled the kernel on my 16.04 xenail
laptop and everything works as it should. The display came up, the touch
pad is responsive and working normally. I have enclosed my dumps of
lswh, lspci, lsmod
Hello,
I actually installed the patch on my laptop with the latest Artful
kernel and I did not see any difference in the performance of the
touchpad on the laptop. It could be that it is because the patch is for
a different version of the laptop (G752VS) which while similar, it does
have a
This has been an issue ever since I have used this laptop with any distribution
of Linux. Up until 18.10 with touchpad would be non-functional. It would jump
all over the screen and would basicaly be unusable with the laptop. Since
18.10. and kernel 4.17.4 the touchpad works as far as no longer
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801574
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801574
Title:
[cosmic] ipoib ping with large message size failed
To manage
I did figure out a way to start the touchpad to work again after I lock
it up using 5 fingers to lock it up:
sudo modprobe -r hid-multitouch && sudo modprobe hid-multitouch
This will bring the touchpad back online so you can use it. I created a
script with this in it, and then added it as a
So I updated to Disco with the touchpad on the Asus GL702VD and for the
most part, it works, I can right click and left click and use 2 fingers
to scroll, however, while I tail the /var/log/syslog I get a bunch of
the following errors that repeat, where with the 4.18 kernel these are
suppressed:
So the latest Disco Kernel (Bionic HWE 5.0.0-31-generic) seems to have fixed
all the issues with the touchpad. I can now touch the touchpad with all 5
fingers and it doesn't lock up and require me to restart the multitouch-hid
module.
It also seems that this version of the kernel also fixed
** Changed in: linux-signed-hwe-edge (Ubuntu)
Status: New => 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/1775918
Title:
GL703VD Laptop DIsplay not working
To manage
52 matches
Mail list logo
