Confirmed on Linx 1010b on LinuxMint 20.3
Added options snd-intel-dspcfg dsp_driver=2 to /etc/modprobe.d/alsa-base.conf
reboot into 5.13
spd-say "Talking too slowly"
shut down
go to bios and save
reboot into 5.13
spd-say "That'll do nicely"
Works in 5.14, plus it seems to still be good in 5.11.
FWIW:
dmesg | grep -Pi "alsa|pulse|sound|audio"
... for 5.11 and 5.14 differ.
5.11.0-46-generic (works)
[0.136592] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[3.051445] i915 :00:02.0: [drm] HDaudio controller not detected, using
LPE audio instead
[ 10.791703] input: Intel HDMI/DP
Same thing for me: Dell XPS 13 with QCA6174 wlan card
It often crashes after the laptop suspend
No porblem if I manually switch off the wlan before suspending.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
I've installed 21.10 on a stick and updated the kernel to 5.12.0-27. It
works fine there, so this is probably about kernel >= 5.13 AND NOT dist
=21.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.13 in Ubuntu.
https://b
I live-booted from U 21.10*, which has a 5.13.0-19 kernel.
Bafflingly, sound test worked from the live system, even though alsa-
info shows rt5640,sof-bytcht.
Late now. I'll do it again tomorrow and grab inxi/pactl/alsa-info.
*Lost time making a USB boot stick with 32 bit EFI capability. mkusb t
Public bug reported:
Using the built in speakers on a Linx 1010b. The 5.11 kernel works fine,
but 5.13 and 5.14 fail.
The card, when working is seen in alsa-info as bytcrrt5640,bytcr-rt5640,
whereas in the later (hwe-20.04-edge, oem-20.04d) kernels where it
fails, it is seen as "rt5640,sof-bytcht
Like Hugo Ferreira, switching to the NVIDIA Server Driver instead of the
classic NVIDIA driver finally did the job. Everything I tried before didn't
work.
So it is finally fixed for me, although I don't know if there are any drawbacks
to using the Server driver :)
--
You received this bug noti
kernel 5.0.0-21-generic fixes the issue. Thanks for your help!
** Tags removed: disco verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I obviously can't run apport-collect after a kernel panic, but will be
more than happy to upload any log file that could help troubleshooting.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, w
** Attachment added: "Panic stack trace"
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1829652/+attachment/5264773/+files/panic_stack_trace.txt
** Description changed:
Hi,
I've recently upgraded my system to ubuntu 19.04, and kernel consistently
panics when I boot a virtu
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+attachment/5264783/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Hi,
I'm using the same MSI and I have the same problem. My touchpad doesn't
work when the acpi=off is in the Grub but I can't boot without this
parameter. Without that, my cpu is stuck!
More than 1 years after, is there a standard solution?
BR
--
You received this bug notification because you
It looks like the same issue occurs on Intel Core 2 Duo CPU P9400 @
2.40Ghz with i686 Xubuntu with Kernel linux-image-4.13.0-32-generic.
It loops directly after grub before any kernel print out back to bios.
It boots with the previous kernel 4.10.0-42-generic.
--
You received this bug notificat
over 1 year after last comment... behavior still exists.
ash@CASE:~$ uname -a
Linux CASE 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
ash@CASE:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Releas
Pilot6 : Ok ! Thank you for your patch.
--
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/1542944
Title:
QCA9565 / AR9565 bluetooth not work
Status in linux-firmware package in Ub
Sorry but I don't understand
What is the difference :
- verification-needed-trusty
- verification-needed-vivid
- verification-needed-wily
- verification-needed-xenial
I have 14.04 (trusty ?) and I Have installed prposed kernel 4.2.0-36 and It's
work.
Can I test kernel for others ubuntu distr
tags: added: verification-done-trusty
removed: verification-needed-trusty
--
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/1542944
Title:
QCA9565 / AR9565 bluetooth not work
St
For me, the wifi and the bluetooth work at the same time...
My laptop is connected in wifi and I can listen a webradio to my
bluetooth hifi receiver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.l
Ok.
I have installed manually 4.2.0-36 and blutooth work fine.
--
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/1542944
Title:
QCA9565 / AR9565 bluetooth not work
Status in linu
I have tried :
install "old" generic-lts-trusty (3.13), reboot and select the old
kernel in grub. After the system booted, Launch update. but message says
me that packages are up to date.
What I need to do ?
thanks
--
You received this bug notification because you are a member of Kernel
Package
Yes !
You have says me by mail the february 6 2016 :
"But it will be much more convenient if you upgrade your kernel first by
running
sudo apt-get install linux-generic-lts-wily
and reboot."
How I need to do ? The old 3.19 kernel was removed because my boot
partition is too small.
--
You rec
Hi,
I have enabled the the proposed in update manager and make an update. Then I
have removed the btusb patch sended by Pilot6.
Now, a uname - a return : 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri
Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
an apt-get upgrade -s return 0 package to
Also affects Sony Vaio SVS15 series laptop. Hibernate or suspend no
change in max fan speed. No PWM capability.
--
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/1565864
Title:
Hardware-sp
I used a MicroSDHC with a MicroSD - SD adapter. The card itself is
chinese, brand Xedain. If that matters. I didn't think it would be
important, but I can try with other cards (SDHC, MicroSD, MIcroSDHC) and
brands (real ADATA, Sandisk, Patriot)
It's unfortunate to have to reverse engineer a dri
Hi Olerem,
Thanks for the prompt answer. Unforutnatley, that NULL pointer didn't seem to
help much.
The computer boots and the driver loads, but when I insert a SD-card, the
laptop freezes after about 8-10 seconds. Just enough time to take a picture of
the dmesg:
http://postimg.org/image/6ac
My laptop is a TOSHIBA Satellite L40-D and I'm having the same issue
with the Alcor Card Reader
$ lspci
Unassigned class [ff00]: Device [1aea:6601]
This is running Ubuntu 15.04 on 3.19.0-47
Cards inserted never even get detected by the system. I see no log entry or
error in dmesg.
--
You recei
I'm having the same issue with the Alcor Card Reader
$ lspci
Unassigned class [ff00]: Device [1aea:6601]
This is running Ubuntu 15.04 on 3.19.0-47
Cards inserted never even get detected by the system. I see no log entry or
error in dmesg.
--
You received this bug notification because you are
I forgot to notice that this happens for me on :
Linux daminetreg-laptop 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
for Ubuntu 14.04.1 LTS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I've the issue also on a MacBookPro 11,1. It takes exactly 34,2 seconds
for the system to wakeup.
Strangely dmesg says the wakeup started on second 1864 and ended on 1869
:
[ 1864.618554] smpboot: CPU 7 is now offline
[ 1864.636283] ACPI: Low-level resume complete
[ 1864.636333] PM: Restoring pla
This has seemed to resolve itself with later kernel packages. I no
longer have any resume issues, with either mainline kernel or normal
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Having trouble resuming from suspend. The whole system hangs upon
resume. No mouse, no keyboard input.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-5-generic 3.16.0-5.10
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname:
I am also having this issue in Ubuntu 14.04 and my Lenovo IdeaPad Flex
15 (59387556).
--
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/1264384
Title:
8086:08b2 [Lenovo ThinkPad S3-S440] Wi
I'm not really sure the problem I managed to reproduced on v3.15-rc2 is
the exact same. The symptoms are the same: I can't resume from suspend.
Still, as I don't have sound on v3.15-rc2, I don't think the problems
are related. Please advise on what I can do to help get this bug(s)
fixed.
--
You r
I have a hard time reproducing again. The problem is twofold:
1. the suspend/resume problem does not always happen
2. this kernel does neither have sound nor wifi which makes it inconvenient to
set as my default kernel
Do you think I could configure wifi and sound on the 3.15rc2 kernel?
--
You
Using v3.15-rc2-trusty (3.15.0-031500rc2-generic #201404201435 SMP), I *managed
to reproduce* the suspend/resume problem.
Using this kernel, the wifi is not working: this is problematic because I can't
just report bugs using apport from there. Nevertheless, when the problem
occured again in v3.1
Please find attached the /proc/acpi/wakeup while in v3.15-rc2-trusty. I
didn't follow the "resume-trace debugging procedure" as it looks like it
is related to debugging resume while I think my problem is on suspend:
when I close the lid and the light does not blink, I know the computer
won't resume
Suspend/resume was working fine in 13.10 on the same hardware.
--
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/1328801
Title:
pacmd list failed suspend resume
Status in “linux” package i
Public bug reported:
Here are some details as asked in bug #1305371
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVer
*** This bug is a duplicate of bug 1297961 ***
https://bugs.launchpad.net/bugs/1297961
I have the exact same problem and my system is up-to-date.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** This bug has been marked a duplicate of bug 1297961
[Apple Inc. MacBookPro
*** This bug is a duplicate of bug 1297961 ***
https://bugs.launchpad.net/bugs/1297961
** This bug has been marked a duplicate of bug 1297961
[Apple Inc. MacBookPro9,2] suspend/resume failure [non-free: wl]
--
You received this bug notification because you are a member of Kernel
Packages,
*** This bug is a duplicate of bug 1297961 ***
https://bugs.launchpad.net/bugs/1297961
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
I have a similar problem on the exact same architecture. Nevertheless, I
don't think my problem depends on how long the computer stays suspended.
>From what I can see, as soon as I close the lid I know if resume will
work fine or not:
- if the suspend light starts blinking after a few seconds, the
Public bug reported:
just installed saucy daily from Sep 13th (Australian time)
$ ls -l Downloads/saucy-desktop-amd64.iso
-rw-rw-r-- 1 ddp ddp 873M Sep 13 23:27 Downloads/saucy-desktop-amd64.iso
just closed the lid, and machine seemed to hang - I could hear the fan,
but could not get a respons
43 matches
Mail list logo
