Yes, suspend still works (tried it twice times) without blacklisting the
soc-skl (I did a fresh boot having removed the blacklist lines for it).
Same situation as with prior -40 mainline (builtin speakers still work,
mic still not work). Seems a fix for mic will be targetted at 20.04 from
other
Actually, update: suspend works with following added to /etc/modprobe.d
files on the new kernel (-43 with this patch, as per #5 above), but
audio still does not (didn't test JUST the blacklisted module yet):
line added to blacklist.conf:
blacklist snd_soc_skl
line from alsa-base.conf:
options
Pointed here as possible duplicate from bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867388. Tested the
.deb kernel packages from link in #5 in this bug with my HP Elitebook
830 (which also suspends fine and has audio on 5.3.0-40 but not on later
versions); no change, still fails to
Thought the kern.log from the (tested-above) kernel might be rather
useful too; attached here the last boot (ie. where boot-offset time in
the log becomes [0.0] again).
** Attachment added: "kern.log"
Installed all -43 kernel deb packages from the link in #5 of bug 1866170
and booted with it (after allowing legacy boot, disabling UEFI); cannot
notice any change. Still won't suspend, audio still not recognised.
Tried a few alsa force-reloads with dmic setting/not and mode
specified/not in case
Public bug reported:
Suspend stopped working when upgraded to kernel 5.3.0-41 from -40.
Power-button (narrow slit) LED stays fully lit and front indicator
power/wifi/drive LEDs also lit as though not suspended. Screen went
black but will not respond to keyboard/touchpad input (even Ctrl-Alt-
See https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841108
Title:
Internal Microphone not working on HP EliteBook x360 1040 G5
To
Public bug reported:
Kernel updates for this 16.04 system keep reporting this error but an
apt -f install will fix it. Didn't suffer this problem when on 14.04
previously (upgraded to 16.04 from it)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic (not
Joe, am on cabled network on a desktop and I don't see the new connection
message or other notification that would cause this.
On 8 Mar 2014 17:10, Joe6832 manfred.g...@t-online.de wrote:
The Problem affects me with every start. I think the Wifi-is-Connected
Message could dissolve the focus of
I just discovered that re plugging in my usb mouse via a direct us port
made it work again and I don't get this problem when it is in one of those
ports. It only happens when the mouse is plugged in via a us hub. Maybe
that isn't re initialised properly on resume, it's a cheap unpowered usb2
hub.
Mine is a self-build with AMD Turks graphics card and on-board amd card
I've got disabled in the BIOS, using fglrx, motherboard is an older
Gigabyte GA-MA69G-s3h (AM2 board with AM2+ chip, upgraded BIOS to cope with
it).
'twas a fresh install of 14.04 to a new drive, but I do have an older one
I'm also seeing it semi-regularly in 12.10 when dropping files from
nautilus (think its nautilus, gnome 3 desktop anyway) to Totem. I killed
totem from the terminal and the pointer stayed like that and I couldn't
click on anything else, xkill couldn't even grab the cursor to kill the
Yep, pkill nautilus from a text terminal (press Ctrl+Alt+F1 together
to get a terminal or use an existing one on your desktop if you can via
Alt+Tab/guake/other, once you have one logged in, type the pkill command
mentioned earlier, then use Ctrl+D or type logout(enter) to log out of
terminal;
Public bug reported:
Reproduction + error details
* Reproducible 100% of time.
* I started the game in a regular Ubuntu Terminal window as a normal
(non-root) user.
* It immediately and continuously shows the score in the bottom left corner as
0.06% (with a few spaces indent, a 1, a couple of
Adding i8042.nopnp to the kernel command-line in grub fixed it for my
mouse, on an HP Compaq DX2000 MT.
My PS/2 mouse (but not the PS/2 keyboard) had been broken since I
rebooted for the first time after the upgrade to Hardy desktop, from
Dapper.
For newbies reading this and wanting to try it:
Oops, update-grub will do to update grub's menu.lst with the new
options. dpkg-reconfigure will do it too but more of a sledgehammer for
the nail that needs to be done.
--
PS/2 doesn't work after upgrading to feisty [i8042]
https://bugs.launchpad.net/bugs/95785
You received this bug notification
16 matches
Mail list logo
