in #28 @hui.wang wrote
>So far, both ucm2 from upstream and ucm from Intel only support 2 speakers,
>for Bass speakers support, the upstream is discussing it, please read this
>thread：
>https://mailman.alsa-project.org/pipermail/alsa-devel/2020-February/162701.html,
> if you have some idea, plea
Public bug reported:
I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but
upon reboot my Dell XPS lost a few peripherals, like the wifi, and the
possibility to use the Dell WD-15 docking station for LAN or external
monitors; USB hub functionality was working though.
After some i
** Attachment added: "ubuntu_lspci_5.4.0-37.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+attachment/5383215/+files/ubuntu_lspci_5.4.0-37.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "ubuntu_lspci_5.4.0-33.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+attachment/5383214/+files/ubuntu_lspci_5.4.0-33.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I'm not sure how to check that, what's the right package to check? I've
tried linux-modules-extra-5.4.0-37-generic, but it's missing for 33 too
$ sudo apt-cache policy linux-modules-extra-5.4.0-37-generic
linux-modules-extra-5.4.0-37-generic:
Installato: (nessuno)
Candidato: 5.4.0-37.41
T
@vicamo Thanks for pointing that out, I was missing linux-generic.
I probably got into some apt or metapackage bug that removed it from my
system, because I'm sure I didn't remove it manually.
I dug into my apt logs and I've found this in the history log:
Start-Date: 2020-05-28 09:32:50
Command
I just upgraded my ubuntu 19.10 and suddenly lost my sound card. Kernel
was updated from 5.3.0-40 to 5.3.0-42. This switched the sound driver
from snd_hda to snd_soc which sounds very promising but it seems a
firmware is missing and it is unclear where we are supposed to get the
firmware from.
```
After enabling selective updates from proposed, I ran
> sudo apt install linux-image-5.3.0-43-generic
> linux-modules-extra-5.3.0-43-generic linux-firmware/eoan-proposed
> libasound2/eoan-proposed
> sudo add-apt-repository ppa:hui.wang/audio-master
> sudo apt-get update
> sudo apt install libaso
Sorry, I forgot to subscribe and didn't get notified.
Attached is my dmesg after a clean reboot, and a screenshot of the
gnome-settings in which I don't get sound notifications
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341395
I encounter a few other issues which appeared since I upgraded to this
setup when using a secondary screen over HDMI and a bose QCII bluetooth
headset.
- output automatically switches to the headset but microphone doesn't
- forcing the microphone to the headset triggers switches to output (says to
** Attachment added: "Screenshot from 2020-03-25 11-13-00.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341396/+files/Screenshot%20from%202020-03-25%2011-13-00.png
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Thanks for the explanations. I'll keep working with pulseaudio+ucm for
now so as to be able to test your fixes. If it becomes too unbearable
I'll revert to dmic_detect=0
>About the issue on google meet, it is a problem, do you also meet the
similar issue on other audio apps?
Regarding the microph
the dmesg with only the chrome attempt
** Attachment added: "dmesg-202003251809.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341612/+files/dmesg-202003251809.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is s
I just installed the latest package from your PPA: it actually makes the
looping issue worse. now the issue occurs as soon as I create a meeting
in meets.google.com with chromium.
I tried right after to create a meeting in firefox and couldnt' get the
headset to work at all. After restarting the h
Hi,
I wanted to give a bit of feedback after a few days using the laptop
with kernel 43 and the experimental libasound packages from Hui's ppa.
As far as I can tell, the microphone works flawlessly.
Sound output to speakers and HDMI works too. With one notable drawback : the
internal speaker vo
The
options snd-hda-intel dmic_detect=0
workaround works, I was able to recover output but of course lost the
microphone in the processe \o/
--
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
Hi,
I received a couple firmware updates through fwupdmgr yesterday and
rebooted this morning. I don't have sound any more (back to dummy output
:( )
here is what dmesg has to say now
[0.261799] ACPI: Added _OSI(Linux-Dell-Video)
[0.261800] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[
Hi,
I received a couple firmware updates through fwupdmgr yesterday and
rebooted this morning. I don't have sound any more (back to dummy output
:( )
here is what dmesg has to say now
[0.261799] ACPI: Added _OSI(Linux-Dell-Video)
[0.261800] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[
As a follow up on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/comments/28 where
I reported that updating the bios on my X1C7 broke the sound with sof/skl :
I checked the bios information as explained in the original description here.
> cat /sys/devices/virtual/dmi/id/bios_vers
Damn sorry about that, I didn't notice the kernel moved from .43 to .45.
I'll try with 46
--
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/1845678
Title:
Lenovo ThinkPad X1 Carbon 7th Gene
under the following configuration the sound and microphone work as
described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/comments/28
ii libasound2:amd64 1.1.9-0ubuntu1.3
amd64shared library for ALSA applications
ii liba
Hello, the kuba-moo / benjarobin driver+patches worked fine until today
when I migrated from Debian Stretch to Debian Buster. I could get wifi
working, but not bluetooth, because the 'bpatch' try to uninstall the
current linux-image and replace it by 5 others packages, which could
break my system.
Thanks you reply, @levgen. But I don't agree with your global
appreciation. I have been using Debian for nearly fifteen years and it
works fine. With the kuba-moo&benjarobin driver my ASUS wifi and
bluetooth have been stable for four years. Your are right that I had to
reinstall only this driver wi
ee my card and wireless
networks, but I can't connect to any network. Authentication issue. Got it
even with free network without security check. Has someone encountered the same
issue ? Solved it ? Thanks
Jean
--
You received this bug notification because you are a member of Kernel
Packa
Hi Zlatan,
Did you use this package https://github.com/lwfinger/mt7630 ? Or the
Mediatek package http://www.mediatek.com/en/downloads/mt7630-pcie/ ?
If installing on 14, the second one is better.
But your kernel seems to be 16, not 14. Then the first package is theorically
better. "Theorically"
The output you sent shows that the load.sh you run is looking for kernel
16 missing modules, not kernel 14 and that the modules built at the run
are invalid. Looks like trying to insert kernel 14 modules into a kernel
16.
--
You received this bug notification because you are a member of Kernel
P
Thank you very much Jakub. Install is very easy and this is the first
time that Wifi is working very fine (I don't know for BT which I dont't
use) on my ASUS K551LN X0401H with Debian Jessie.
Jean
- Mail original -
De: "Jakub Kicinski"
À: jber...@free.fr
Envoyé
unsuccessfully.
I tried the new solution alledgedly fixing the BT issue
https://github.com/neurobin/MT7630E, the "bpatch" included, whithout success
Here is the result of "systemctl status bluetooth" command.
root@pc-jean-debian:/home/jean/Téléchargements/mt7630e/btloader# systemctl
same problem on a fresh ubuntu 14.04 on HP Pavilion 15. it's so
annoying.
--
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/1286552
Title:
No wifi after suspend
Status in linux package in
Hi Dave,
Did you try Jakub Kicinski's update of the driver :
https://github.com/kuba-moo/mt7630e ?
J ean
- Mail original -
> De: "dave"
> À: jber...@free.fr
> Envoyé: Vendredi 23 Octobre 2015 03:10:36
> Objet: [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't
> supported o
Public bug reported:
I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is
equipped with:
* 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8
* Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2))
Since on my first try I was getting a lot of SEGFAULTS, I repeated th
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1943421
Title:
Error while enabling somerville driver: packag
Closing, as I discovered that the root cause was interference from my
antivirus (Sophos).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1943421
Title:
Error while enabling some
Hi everyone,
small progress report :
I tried the pipewire trick and it didn't work out for me, while it initially
seemed to work: auto switch to the HSP/HPF profile didn't work and after a
manual switch the headset would drop out during a conversation.
I reverted to pulseaudio and invested a bi
q/124
pcie-dp"!?
Now it's freezing in the middle of the installing.
I send it to you two pictures of screen shots.
Thanks for the help.
Jean Matau
Le lun. 10 mai 2021 à 04:00, Daniel van Vugt <1927...@bugs.launchpad.net> a
écrit :
> Thanks for the bug report. The
Le lun. 10 mai 2021 à 04:00, Daniel van Vugt <1927...@bugs.launchpad.net> a
écrit :
> Thanks for the bug report. The first thing I notice is your kernel log
> (CurrentDmesg.txt) is showing some kind of repeating hardware failure
> related to 'pcieport'. Was there any release of Ubuntu you have use
Thanks for the answer.
I will bring back computer to the store and look for another one.
Greetings
Jean Matau
Le lun. 10 mai 2021 à 09:30, Daniel van Vugt <1927...@bugs.launchpad.net> a
écrit :
> Thanks. Yes that looks like the same hardware problem. It sounds like
> the faulty comp
If I understand correctly all the discussions, an first step in the
direction of higher quality sound for BT headsets just got merged into
PA
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/440
--
You received this bug notification because you are a member of Kernel
Packages
the next step to get a full fix and improved sound quality for voip
calls over BT headset is coming in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubunt
Public bug reported:
Black screen after reopening lid.
Configuration : laptop TOSHIBA is running with lid closed but when it is
re-opened, the screen still black. Unlocking is impossible.
Last OK (operational) nucleus 4.15.0-46.
Problem with 4.15.0-47 to 4.15.0-51.
Regards.
** Affects: linux (U
Black screen after reopening lid. Unlocking screen is impossible. SO
command in a terminal window: apport-collect 1832715 is impossible.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jean-Bernard (jb-fre
Kernel : 4.4.0-151
-- Logs begin at mer. 2019-06-19 22:32:00 CEST, end at mer. 2019-06-19 22:40:41
CEST. --
juin 19 22:32:01 JB-Notebook kernel: microcode: microcode updated early to
revision 0x60f, date = 2010-09-29
juin 19 22:32:01 JB-Notebook kernel: Linux version 4.15.0-52-generic
(buildd@l
$ lsb_release -rd
Description:Linux Mint 19.3 Tricia
Release:19.3
I'm seeing the same thing (wifi doesn't show up at all in network
manager), here's the kernel messages upon startup:
[7.219871] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
[7.219945] iwlwifi :00
77216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-displ
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
it 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabri
it 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabri
r linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
o
ux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
rd bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
descript
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
ze
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Cont
it 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabriquan
it 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabri
12Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
r linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
o
912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Cont
it 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabri
r linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
o
correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit
Attempted to try v4.17-rc5
got a dependency problem ... linux-base (>=4.5ubuntu1~16.04.1
So the answer of the question "Can you try v4.17-rc3?" is NO because
v4.17-rc5 i386 not vailable
v4.17-rc4 i386 impossible to install
v4.17-rc5 i386 dependecy problem
Regards
Jean C
omment out #linux-check-removal $version
v4.17-rc5 i386 got dependecy problem
linux-base (>=4.5ubuntu1~16.04.1)
Regards
Jean COLIN
> Message du 08/05/18 07:41
> De : "Kai-Heng Feng"
> A : jean.co...@wanadoo.fr
> Copie à :
> Objet : [Bug 1737423] Re: With a
/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
descript
VideoRam 262144 but not
succeeded
For me, the goog thing to do is to be able to recover the information
obtained at hardware level
done lspci
jean@jean-Soisy:~$ lspci -v -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controlle
Found some document about size determination in pci devices
had run lspi
jean@jean-Soisy:~$ sudo lspci -vv -k - -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Control: I/O- Mem+ BusMaster+ SpecCycle
] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname
soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controll
000 rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$
ong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Co
Me also on a Lenovo X1 6 Gen on Debian 9:
dmesg =>
[2.611547] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[2.611547] thinkpad_acpi: http://ibm-acpi.sf.net/
[2.611548] thinkpad_acpi: ThinkPad BIOS N23ET59W (1.34 ), EC unknown
[2.611549] thinkpad_acpi: Lenovo ThinkPad X1 Carbon 6th, mod
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78
Uname: Linux 5.4.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubun
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78
Uname: Linux 5.4.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ub
The latest patch does work when you realize that the skb_put function
has recently changed from (unsigned char*) to (void *) ( see
https://patchwork.ozlabs.org/patch/776580/ for fix).
The lines where appears "*skb_put" need to be changed to "*(u8
*)skb_put". This was enough for me to get my blueto
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
Same problem, "Kernel panic" after 4.4.0-108.131 update.
No way to reboot, even from a network boot.
I can log in rescue, which runs a different kernel in my case (OVH)
4.14.12-mod-std-ipv6-64-rescue
--
Y
The bug affects me as well, same machine. In the mean time, to avoid rebooting,
you can reload the module, as super user:
modprobe -r psmouse
modprobe psmouse
This fix the problem for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
00/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
Using this guide
https://www.dell.com/support/article/ng/en/ngdhs1/sln306440/killer-n1535
-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en and
upgrading to latest firmware for Dell XPS 15 on Ubuntu 17.10 for the
following below solved my wifi frequent connection drop while
NetworkM
Public bug reported:
After update, the system not start with Kernel version
4.10.00-33-generic
[24.544059] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]]
*ERROR* [CRTC:34:pipe 8] flip_done timed out
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You
Posting this in case it would help someone else: I had the same issue
with 15.10 (with kernel 4.2). I upgraded today to 16.04 (with kernel
4.4.0) and the buletooth is working like a charm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bl
I'm having the same problem with my Lenovo Flex 2 with the same
rtl8723be wireless card.
Kernel :
3.13.0-29-generic #52-Ubuntu SMP Wed May 28 12:42:47 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
gets the card to work. Internet works for extended periods of time, but
will require the occasional rebo
.) or in
Firefox since upgrade to 14.04. It would seem there is a high response
time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-
en scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-
Public bug reported:
Hi,
Mouse scrolling is jerky/slow after suspend/resume in files or in
Firefox in Ubuntu 14.04.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-gen
.vendor: HP-Pavilion
** Description changed:
Hi,
Mouse scrolling is slow and jerky after suspend/resume in documents
(.pdf) or in Firefox since upgrade to 14.04.
+
+ Thanks
+
+ Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-
.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse
It would seem there is a high
response time between mouse scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3
there is a high
response time between mouse scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-gene
e to 14.04. It would seem there is a high
response time between mouse scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname
down keys) is jerky
+ after suspend/resume in documents (OpenDocument, .pdf, ...) or in
+ Firefox since upgrade to 14.04. It would seem there is a high response
+ time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package
seem there is a high response
time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic
there is a high response
time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x
croll bar, page up/page down keys) is jerky
after suspend/resume in documents (OpenDocument, .pdf, ...) or in
Firefox since upgrade to 14.04. It would seem there is a high response
time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: U
/page down keys) is jerky
after suspend/resume in documents (OpenDocument, .pdf, ...) or in
Firefox since upgrade to 14.04. It would seem there is a high response
time between scrolling action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Pack
action and screen display.
Thanks
Jean Marc
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture
Hello,
I upgraded to the packages in the PPA mentioned in comment #27. I
removed mi Logitech K810 keyboard using the GUI, then restarted the
computer. I managed to pair my keyboard successfully typing the six
characters on-screen. In fact, the GUI showed progression as I typed the
characters by ma
Public bug reported:
Lenovo Yoga 2 Pro does not come back from sleep.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
Annotation: This occured dur
bug still exist upstream
** Tags added: kernel-bug-exists-upstream
--
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/1294087
Title:
[LENOVO 20266] hibernate/resume failure
Status in “linu
1 - 100 of 607 matches
Mail list logo
