Public bug reported:
Install zsys on a non ZFS system without the kernel module loaded leaded
to a segfault.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
FYI: the patch "net/mlx5: Fix crash upon suspend/resume" is in v5.7 now
(i.e. today's latest mainline):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.7=8fc3e29be9248048f449793502c15af329f35c6e
--
You received this bug notification because you are a member of
See also: https://www.smartmontools.org/wiki/SAT-with-UAS-Linux
--
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/1810215
Title:
for Seagate USB drive enclosures, SAT (e.g. smartmontools,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1881549
Title:
Upgraded to 20.04 and wifi broke
Status in linux
vmware deve's comment for the issue "blk_update_request: I/O error, dev
sda, sector 3270728 op 0x9 VM ubuntu-20.04-live-server in ESXi 7.0GA" :
I noticed that when it's happening, abnormal kernel log:
[0.00] ? lockdown_lsm_init+0x21/0x25
[0.00] Kernel is locked down from EFI
For more information about this issue, see
https://askubuntu.com/a/1106020/50254
TL;DR: Linux kernel disables 12 and 16 bit SATA Commands over UAS when
used with Seagate HDD enclosures. This usb_storage quirk is "t" instead
of "u" which forces the device into USB BOT mode. The only way to make
I had the same issue with Ryzen 5 3600x and Radeon 5600xt. For a
different mouse flickering issue when using xrandr, I had to set
following xrandr after I set correct resolution and panning.
xrandr --output DisplayPort-2 --scale 0.x0.
DisplayPort-2 is my primary display. With the above
Confirmed as per suggestion in #75 - system boots to login no problem
when quiet-splash is disabled on Lenovo x260 (intel graphics) Kernel
5.4.0-31-generic.
If I return to default (quiet-splash enabled) system hangs on splash
screen.
Thanks
--
You received this bug notification because you are
Dear Daniel,
Thank you for that work-around!
The error message is a bit odd, as it says that it may lead to LESS powersaving.
Even then, once hibernated there is no power draw anyway
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: oem-priority originate-from-1880678 timbuktu
** Tags removed: timbuktu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1881525
Title:
in kernel amdgpu failed
** Also affects: nvidia-graphics-drivers-440-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-418-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development
Public bug reported:
Upgraded to 20.04 and the wifi broke. It was working fine on 18.04.
Tried a variety of things with apw but nada. /var/log attached
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: focal
** Attachment added: "/Var/log"
Hi Mauricio,
I can confirm that your patched kernel fixes the problem for me on
Bionic (kernel 4.15).
Thanks for your help!
-Sebastian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1881549
and then change the status of the bug to 'Confirmed'.
If, due to the
You have been subscribed to a public bug:
When using the HyperX AMP, the microphone is not detected. This is a
known issue with the mainline kernel, however was patched in release
5.7.0. This occurs on Ubuntu 20.04 LTS.
https://lkml.org/lkml/2020/4/4/197
ProblemType: Bug
DistroRelease: Ubuntu
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu)
--
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/1881676
Title:
HyperX Cloud Alpha microphone not detected
Status in linux package
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
@kaifengheng
--
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/1881213
Title:
System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Status in linux package in Ubuntu:
this bug is still not solved in 20.04
--
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/1670041
Title:
Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
1535)
You have been subscribed to a public bug:
The touchpad on my Lenovo Thinkbook is not being detected at all. I have
attached the devices list. I also tried installing ubuntu 20.04 and even
in the latest version touchpad is not detected.
** Affects: linux (Ubuntu)
Importance: Undecided
The following patches weren't necessary because they were already
applied via upstream stable updates:
f2c33ccacb2d PCI/PM: Always return devices to D0 when thawing
Via https://bugs.launchpad.net/bugs/1858427
2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume()
Via
Cover letter for the patchset: https://lists.ubuntu.com/archives/kernel-
team/2020-June/110613.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1880032
Title:
[linux-azure]
** Package changed: ubuntu => linux (Ubuntu)
** Tags removed: tocuhpad
** Tags added: focal touchpad
--
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/1881534
Title:
Touchpad not working
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1881534
and then change the status of the bug to 'Confirmed'.
If, due to the
I can confirm it, Im using Linux Mint 19.3 cinnamon with an AMD/GPU
radeon vega mobile gtx8, and everytime I install the kernel, the laptop
can't seem to shutdown or reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for the update Zakhar, but do we still have other sources that
can help us to fix this one? I wonder. Thank you again.
Marco Blakey
https://andwebtraffic.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Patches:
https://lists.ubuntu.com/archives/kernel-team/2020-June/110635.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1881525
Title:
in kernel amdgpu failed with W5500
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1881638
Title:
touchpad not appearing in
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
BTW I'm glad that those commands helped you. And good job in command
dissection here!
--
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/1850439
Title:
No sound on ASUS UX534FT
Status in
I found it! I found the magic sequence!!!
srgk@zen~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
[sudo] password for srgk:
nid = 0x20, verb = 0x500, param = 0x1b
value = 0x0
srgk@zen:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b
nid = 0x20, verb = 0x477, param = 0x4a4b
value = 0x0
For me just usual reboot is enough. I reboot the notebook, start some
application that plays sound and then execute the commands below. And
everything works as a charm on my UX534FTC.
About reset - try also "alsa force-reload" and maybe the following
command:
hda-verb /dev/snd/hwC0D0 0x51 0x7ff
Public bug reported:
touchpad has been frozen for ~1 hour. Doesn't appear when checking
xinput --list or other lists of hardware connected to the computer.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing
CONFIG_NLS_ASCII in the arm64 kernel build options.
This option is enabled on the other kernel builds but somehow was overlooked on
arm64 appears to affect our ability to access logs via
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
so what is the state of this with ubuntu server 20.20 ?
I added “dtoverlay=dwc2,dr_mode=peripheral“ to
/boot/firmware/usercfg.txt but also never seeing the USB-C ethernet show
up when connected to my Ubuntu 18.04 laptop. Then again I might be
missing the equivalent of “modules-load=dwc2” as noted
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1881643
and then change the status of the bug to 'Confirmed'.
If, due to the
Alsa-info time:
- Ubuntu Live CD in VM after power cycle:
http://alsa-project.org/db/?f=a3bb092b7964d28cc8a206d0619172472653b48b
- Ubuntu Live CD in VM after Windows VM was started:
http://alsa-project.org/db/?f=316d1051a370a045a3e14d2fc456c6d06fd34ae4
--
You received this bug notification
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz
[...]
03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop
objects [FAIL]
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@ Jeremie Tamburini (jeremie2)
Thks mate. It works perfectly.
Did exactly as you said and now my sound card is back on.
--
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/1864871
Title:
I can also confirm that using these 4 commands sound works perfectly
fine on UX533FTC. It seems that the only last 2 commands are needed to
be executed in sequence, but using all 4 commands works fine too (or
maybe I can't tell the difference? lol).
hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=206459
Importance: Unknown
Status: Unknown
--
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/1860284
For me (Asus UX533FTC) sound works fine when I execute those 2 commands
after boot.
However, when I was testing all those commands, sound did not always
worked. These steps fixed it (run either after or before commands, or
even right after boot):
1. Go to pavucontrol --> configuration
2. Change
A bit background on how I figured out those 2 commands. So let's say you
have 6 commands in total:
A command
B command
C command
D command
E command
F command
Start executing commands one by one, from top to bottom (do NOT resort
them). Let's assume your sound starts to work after command E. So
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
The strange thing is that built-in microphones ARE actually working on
my notebook out of the box. At the least sound meter IS moving for
internal microphones in the settings. And I also found out another bug
when the topic starter has internal microphones working perfectly fine:
*** This bug is a duplicate of bug 1879559 ***
https://bugs.launchpad.net/bugs/1879559
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Nice. One more thing - if you can't get sound to work, then you need to:
1. Completely shutdown the laptop
2. Unplug charger
3. Wait few seconds
4. (optional) plug charger back
5. power on and apply commands. Sound works.
Is there something else we are missing? Like power reset command or
Gentle bump to raise visibility. In more information is needed please
let me know.
Thank you!
--
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/1875199
Title:
[NUC8CCHK][HDA-Intel - HDA
Dumped all the coefficients when the sound is working and without any
distortions: http://alsa-
project.org/db/?f=79b20740c9abbd7427f166208b5a6a2e6449a174.
NOTE: Dumping coefficients can be enabled via
echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef
--
You received this bug
Similar problem with:
- Ubuntu 20.04 LTS
- Fujitsu LifeBook A530
- $ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
THE PROBLEM:
No sound. Gnome audio system settings shows "Dummy Audio" as output device.
Trying with
It looks like it doesn't happen with 5.7.0-050700rc7-generic. I cannot
be 100% sure as it happened randomly. I have got, however, something
suspiciously similar that has never happened before. It has happened
several times already, as randomly as when I got a kernel panic before.
Screen hangs for
** No longer affects: apparmor (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
--
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/1645037
Title:
apparmor_parser hangs indefinitely
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
-
Another, shorter sample with warning (?) audio clip (play from terminal
when there is nothing more to do).
** Attachment added: "Sound sample - noisy sound from speakers 2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379388/+files/noisy_sound_notification.m4a
--
Pinged in #ubuntu-kernel today for an update. It'd be good to have
groovy signed soon so we can then roll this out to focal users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Here is the behaviour on my UX534FTC:
1. Power cycle.
2. Execute two commands from the Erikas' comment.
3. Start youtube video with sound.
Actual result: No sound from speakers.
4. Execute two commands again while the video is playing.
Actual result: Sound appears with the same quality as in my
Headphones are not working - there is nothing beyond some "alien" sounds
from headphones' speakers.
** Attachment added: "Alien noises from headphones"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379389/+files/headphone_not_working.m4a
--
You received this bug
The sound has a strange digital whistle (?) in it. This whistle be head
clearly with higher-pitch sounds.
** Attachment added: "Sound sample - noisy sound from speakers"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379380/+files/noisy_sound_speech_sample.m4a
--
Public bug reported:
Hey there!
I am encountering a bug in Bluetooth menu in drop down menu at top right
corner.
Whenever i turn off my Bluetooth there is no option to turn on there. It
shows two option turn off and Bluetooth setting. After I open setting
and try to turn it on from there it
Public bug reported:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source: boot-assets/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Attachment removed: "/Var/log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379236/+files/syslog
--
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/1881549
These seem to be bare minimum of commands to get audio working on my
Asus Zenbook UX533FTC:
hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74
For anyone wondering where to get "hda-verb" utility - install "alsa-
tools".
--
You received this bug notification
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: apparmor (Ubuntu Xenial)
** No longer affects: apparmor (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd
can confirm its effecting my 20.04 install as well
--
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/1873325
Title:
update-initramfs complains of missing amdgpu firmware files
Status in
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
-
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-drivers-common (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I encountered the same issue and was able to solve it by adding
i8042.reset=1 to the kernel command line. i8042.nomux was not necessary
for me.
The quirk was committed in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2712c91a54a1058d55c284152b4d93c979b67be6
which
I apologize for the slow reply, a lot of stuff has been going on, and I
hit a snag. The device in question no longer boots reliably. I have not
been able to confirm, but I believe that the internal wifi chip is
failing, and when the device loads the wifi driver in the boot process
it crashes. If I
** Attachment added: "updated /var/log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379257/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I was trying out Ubuntu 20.04 Desktop From a USB Stick on my new Acer
A315-31 model laptop.
Touch Pad is not recognized by Ubuntu.
Tried - cat /proc/bus/input/devices and I don't see any Touchpad devices listed.
How do I fix this?
Thank You.
ProblemType: Bug
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1881600
Title:
Touch Pad not detected on
Add me to the list of those having this issue, but also have a partial
fix. I am running a Thinkpad P50 with Nvidia display adapter. 18.04
was great, never any issues with suspend or resume. I upgraded to 20.04
a couple of weeks ago and immediately began encountering the reboot on
resume issue.
Public bug reported:
As it tries to calibrate how many samples will take more than 5 seconds
to execute, it may end up picking up a number of samples that take 10
(but up to 12) seconds. As the calibration will take double that time,
it takes around 20 seconds. Then, it executes the whole thing
** Description changed:
- As it tries to calibrate how many samples will take more than 5 seconds
- to execute, it may end up picking up a number of samples that take 10
- (but up to 12) seconds. As the calibration will take double that time,
- it takes around 20 seconds. Then, it executes the
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
** Attachment added: "updated /var/log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379273/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [SRU Justfication]
+
[Impact]
+ amdgpu is always failed on bionic 5.4 kernel.
+
+ Since bionic's kernel will upgrade to 5.4 in the future,
+ but bionic's linux-firmware didn't support navi14.
+ So if a user update kernel to 5.4,
+ he/she still can't use the related
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I have a skull canyon NUC as my daily driver and the fan is running much
higher than it should, even when the machine is completely idle.
This happened with the 5.3 kernel and also with the 5.4 kernel during
focal development cycle. It was fixed somewhere along the way prior
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1880049
Title:
Using Lakka with Intel GVT-g freezes the host system
Dear Sirs,
Please feel free to close out this Bug.
The Solution as mentioned above was to run with the 4.15.0 Nucleus.
The problem was probably caused by the fact that my Computer System was 10+
years old
and so it couldn't support the new HWE code in the 5.x Series.
Thank you everyone who took
Patches submitted to the SRU cycle:
https://lists.ubuntu.com/archives/kernel-team/2020-June/110609.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110610.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110611.html
I tried all 4.16 (1 to 18), none of them work. Should I bisect from
4.16-rc7 to 4.17 or to 4.16.1?
--
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/1879276
Title:
Esata port is dead after
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1881675
Title:
iwlwifi Microcode SW Error
Dear Sir,
I wish to thank you for your suggestion about using a different
and older Nucleus.
I didn't understand initially about the difference between the
4.x and 5.x Versions.
After I did research on them, I installed the 4.15.0 release.
It has been running perfectly for the past week so I
Public bug reported:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline commits
are:
64caea53e07f ("HID: hyperv: Add a module description
I looked at this again. The GPU does scale down sometimes. But still the
power consumption has without any doubt degraded a lot between 51 and 53
minor versions. The difference is immediately seen by either by looking
at powertop or the power consumption or expected battery time in freshly
booted
Public bug reported:
Sometimes, this bug happens and keep logging as long as I do not not
shut down the computer. Internet becomes irresponsive, and the whole
computer is slowed. It will keep logging until saturating the hard
drive. I had to format the hard drive and reinstall to be able to use
This still happens on a fresh Focal install using linux-
image-5.4.0-26-generic version 5.4.0-26.30
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: bionic
** Tags added: focal
--
You received this bug notification because you are a member of
Testing PPA:
https://launchpad.net/~shanelin/+archive/ubuntu/linux-firmware-amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1881525
Title:
in kernel amdgpu failed with
Confirm affecting Ubuntu 20.04:
---
Processing triggers for initramfs-tools (0.136ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic
W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module
amdgpu
W: Possible missing firmware
1 - 100 of 127 matches
Mail list logo
