Public bug reported:
After replacing my USB mouse with a BT mouse, I noticed my machine would
no longer suspend without immediately waking up. i.e. I suspend and see
the light go into the slow fade in and out for one cycle and then goes
solid and the display wakes up again. If I disable BT (via bl
I believe this issue was due to "legacy suspend" rather than "modern
suspend" selected in UEFI. After a couple suspends I am no longer seeing
the problem, but will reopen if it happens again.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
Scratch that; the first couple suspend operations did work, and then
they stopped again. I'll do more testing and report back. I did rule out
mouse movement by using the hardware power switch on the mouse.
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bu
So after some more investigation it's clear that the problem is
inconsistent. Sometimes wake immediately follows suspend, sometimes not.
Sometimes it takes a while to wake up, up to a few minutes, other times
it's immediate. Occasionally, it seems to suspend fine; or maybe I'm not
waiting long enou
If I remove the bluez package there are no issues with suspend.
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1823076
Title
Public bug reported:
After upgrading from xenial to bionic, USB (both MTP and mass storage)
devices will not automount.
syslog shows the usb device is found and recognized as a storage device:
Aug 28 16:49:18 insitu kernel: [ 4412.072025] usb 1-8: new high-speed USB
device number 18 using ehci-
Issue persists in linux 4.19.0-041900rc1-generic
** Tags added: kernel-bug-exists-upstream
** 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
Update: I can now see that USB storage devices are automounted. This was
resolved by installing gvfs:
sudo apt-get install gvfs
[sudo] password for bbogart:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be in
Tried again today and MTP automounts fine. No idea what was wrong
before.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1
Public bug reported:
Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-146-generic 5.4.0-146.163
ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
Uname: Linux 5.4.0-144-generic x86_64
ApportVersion: 2.20.
This issue seems to persist falling back to kernel 5.4.0-144
--
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/2016388
Title:
Kernel Panic on powerdown on NUC8I3BEH1
Status in linux packag
Photo of console showing panic trace using 5.4.0-144
** Attachment added: "Photo of panic trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664275/+files/5.4.0-144_20230415_091831.jpg
--
You received this bug notification because you are a member of Kernel
Pack
hmm. The issue persists going back to 5.4.0-135 also...
Trying 5.4.0-131 next, but if that it's still happening the issue may be
else ware?
I don't reboot or shutdown this machine very often, the last time I can
confirm I shut down without a panic was around March 14th.
** Attachment added: "5.4
Same thing with 131. So I have no idea what's going on. I upgraded the
RAM in this machine around March 14th, which is why I know that was the
last time I rebooted and I believe I would have noticed a panic.
I also confirm it seems all reboots result in the same panic (e.g. "sudo
reboot" and also
Confirmed on 121.
Another thing I realized is that I also updated the BIOS when I upgraded
the RAM. Updated to BE0092. I have no idea what the previous BIOS
version I was using (whatever shipped with the machine initially), but
this one sill seems the most up to date version.
I'll try downgrading
Same thing with BIOS 0090 and kernel 5.4.0-135
** Attachment added: "Photo of panic trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664317/+files/BIOS0090_5.4.0-135_20230415_103355.jpg
--
You received this bug notification because you are a member of Kernel
P
I was unable to go back to an older version of the BIOS; both BE0088 and
BE0089 resulted in the following error:
"Incompatible BIOS version, Update Aborted!"
This happened both using the built in UEFI BIOS update option and
running IFLASH2 in FreeDOS booting in legacy mode.
--
You received this
The issue persists on 5.4.0-163 and 5.15.0-84
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubu
I'm not sure how, but I managed to get to a console and see the panic
trace on 5.15.0-84. (see attachment below) It does not match the same
panic that I've been previously getting with other kernels.
I also confirm the issue persists on 5.15.0-86 and 5.4.0-164
** Attachment added: "Panic call tra
** Attachment added: "Photo of panic call trace for 5.4.0-164"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5710071/+files/20231016_084851.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Issue persists on 5.15.0-117. Even though updating the bios initiated
this issue, I'll try updating to 0095 in the absence of any other
solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Confirmed on 5.15.0-100 and 5.15.0-101
** Attachment added: "Photo of panic call trace for 5.15.0-101"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5759323/+files/20240325_091737.jpg
--
You received this bug notification because you are a member of Kernel
Packages
Confirmed on 5.15.0-102
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confirmed
Bug
Issue confirmed on 5.4.0-170.
** Attachment added: "20240207_103433.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5745140/+files/20240207_103433.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
confirmed on 5.15.0-92
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confirmed
Bug d
** Attachment added: "Kernel panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5756269/+files/20240315_090551.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
This issue persists on 5.15.0-91
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confir
** Summary changed:
- Kernel Panic on powerdown on NUC8I3BEH1
+ Kernel Panic on shutdown / reboot on NUC8I3BEH
--
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/2016388
Title:
Kernel Panic
Confirmed on 5.4.0-147
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confirmed
Bug d
Problem persists using BIOS 0089, trying 0088 next...
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux packag
Issue persists using BIOS 0088 and 0089.
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
I was advised to use a different method of flashing the bios ("BIOS
recovery" by holding down the power on button with USB including BIOS
inserted) on the Intel forum (https://community.intel.com/t5/Intel-
NUCs/Linux-kernel-panics-on-reboot-and-shutdown-on-NUC8I3BEH-
using/m-p/1477101/emcs_t/S2h8ZW
The issue persists with 5.4.0-148
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confi
The issue persists with 5.4.0-152
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confi
the machine totally
locks up now rather than having a panic.
On 2023-07-13 17:49, Kai-Heng Feng wrote:
> Please install later kernel by issuing `sudo apt install linux-generic-
> hwe-20.04` and reboot.
>
--
B. Bogart, PhD
they/them
www.ekran.org
--
You received this bug notificatio
Got a photo of more of the stack trace for 5.15.0-122
** Attachment added: "20241022_164348.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5830931/+files/20241022_164348.jpg
--
You received this bug notification because you are a member of Kernel
Packages, whic
I updated to BIOS 0095 and the issue persists on 5.4.0-196
** Attachment added: "20241001_095233.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5823797/+files/20241001_095233.jpg
--
You received this bug notification because you are a member of Kernel
Packages,
The issue also persists on 5.15.0-122 with BIOS 0095
** Attachment added: "20241001_095102.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5823799/+files/20241001_095102.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment added: "5.4.0-200 kernel panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5835985/+files/20241109_135544.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Confirmed on 5.15.0-122 and 5.4.0-200
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
C
Issue persists on 5.15.0-131-generic
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Co
Confirmed on 5.15.0-134-generic
--
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/2016388
Title:
Kernel Panic on shutdown / reboot on NUC8I3BEH
Status in linux package in Ubuntu:
Confirm
** Description changed:
Dell XPS 15 (9750); it might eventually manage to suspend when the lid
is closed, but more often than not will not wake up again when the lid
is opened. Waking up using the power button often results in a system
that is apparently frozen (graphics displayed are the
ard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.
ackard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.sku: A5Q13EA#ACB
dmi.product.version:
ssis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_
sis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 1
Rebuilt the package against the latest changes:
https://drive.google.com/file/d/1OUkiq3Pt42_U1Pa25uIGITd4iOG7a-
eI/view?usp=sharing
--
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/1849084
T
Currently, unable to use the Bluetooth device at all. In the UI, the
scanning stuck with a spinning loader.
The journal reports the same error reported by the author.
```
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Cod
Hi. Experienced this issue on an HP Envy X360 (Ryzen 2500U) and can
confirm #54 fixed resuming from sleep, it also fixed resuming from
hibernation for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
The fix does not work for me:
uname -r
5.4.0-33-generic
ournalctl -b0 -u rtkit-daemon
-- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05
EEST. --
Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
Jun 04 18:26:06 n552vw systemd[1]: St
It's also worth mentioning that using "EnablePageFlip" "off" causes serious
screen tearing when interacting with the desktop... Switching KWin's
compositing engine to xrender helps the tearing somewhat, but still - this is
terrible.
That platform (Raven Ridge) has been around for over two years
Good news. I was able to work-around this problem by disabling DRI 3:
#nano /usr/share/X11/xorg.conf.d/10-amdgpu.conf
Option "DRI" "2"
I also added:
Option "TearFree" "true"
to mitigate any screen tearing, although that was for purely cosmetic
reasons.
See if this works for you and report back,
Apologies for spamming, guys.
I tried another fix for this bug, as suggested here:
https://gitlab.freedesktop.org/drm/amd/-/issues/695#note_313722
and it seems to be working.
I rebuilt the xserver-xorg-video-amdgpu-hwe-18.04_19.0.1 package with
https://github.com/freedesktop/xorg-xf86-video-
amd
The power-off bug can be fixed by installing .56 kernel. I'm using the
following PPA to get that release until it makes into official repos:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed.
--
You received this bug notification because you are a member of Kernel
Packages, wh
I still see this message on a fully up-to-date Kubuntu 19.10 system.
However the system boots fine and everything seems to be working ok.
This is apparently a non-fatal error message? It sounds pretty bad but
it still seems to have been able to load the initramfs image fine. What
does this really m
Can confirm bug returns moving from kernel 4.15.0-32 to 4.15.0-33,
tested on both 16.04 Server and 18.04 Server. Tested with program using
pcap_inject (libpcap 1.7.4 (16.04) and libpcap 1.8.1 (18.04)), no issues
seen with 4.15.0-32 (or 4.15.0-29), additional 14 bytes being
transmitted with 4.15.0-
Public bug reported:
I am reporting this using the most recent auto updated version of the
kernel linux-image-4.4.0-122-generic. But boot also fails on the two
previous auto updated images linux-image-4.4.0-121-generic and linux-
image-4.4.0-119-generic.
Last bootable kernel was linux-image-4.4.0
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
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/b
Used kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
It boots/works.
Added tag and changed status as requested. 1st time Launchpad user so hope I
did it correctly.
Thanks for the help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Tags added: kernel-fixed-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/1767360
Title:
16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
image-4.4.0-121-gen
I discovered that reducing the BIOS setting for DVMT Pre-Allocated
Memory below 512M gets around the bug. IE: The three problem kernels
listed in this report will boot if DVMT Pre-Allocated is set less then
512M. As mentioned in this report kernels 4.4.0-116 and before worked
fine with DVMT Pre-All
Can confirm that removing xserver-xorg-input-synaptics fixes the issue.
--
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/1760338
Title:
Touchpad hotkey 'functional' but has no effect in 18
I think I encountered the same thing. The screen would not wake up
though I could still ssh to the system, a lot of commands were not
working, they would just hang or do nothing. Had to resort to a hard
reset. The crash just continued to loop over and over again in the logs
4/30/17 11:11 PM
Re: PermissionError: [Errno 1] Operation not permitted:
'/sys/kernel/debug/tracing/../kprobes/blacklist'
This can be fixed by a patch to the bpfcc libs found at:
https://github.com/iovisor/bcc/commit/5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a?branch=5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a&diff=unif
Public bug reported:
Setting drive device/queue_depth to 31 from 32 resolved an issue whereby
I had numerous zpool and ATA errors but only under high load (zpool
scrub) or when trimming the drives. Was able to reduce incidence by
setting to libata.force=noncqtrim, and resolve with libata.force=no
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+attachment/5407656/+files/version.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/bugs/189
Uncomfortable dumping logs I can't view.
** 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/1894230
Title:
Device queue
FYI, the drives are super common:
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron BX/MX1/2/3/500, M5/600, 1100 SSDs
Device Model: Crucial_CT1050MX300SSD1
Serial Number:164914EE5DDD
LU WWN Device Id: 5 00a075 114ee5ddd
Firmware Version: M0CR031
User Capacity:1,050,
Please close this bug. I was wrong about the queue depth being the
source of this issue. Currently I've tried including pci=nomsi at the
kernel command line, and I seem to be the avoiding SATA errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
This problem just appeared on my Spectre x360 for the first time
yesterday. When laptop auto-suspends form lack of activity, the screen
goes black with three messages with this error. It is unresponsive so
only solution is power off and reboot by pressing and holding the power
button to shut down,
Following up, I have made the following changes to my system recently.
Two occurred within the week prior to this problem appearing, but not
immediately before to my knowledge, so it's not certain that any of them
are applicable. They are listed in order of first use.
- Added a 4K monitor on HDMI
Sorry, more info... looking at kern.log, the context is as follows. Note
that this occurred when the machine had auto-suspended with the laptop
open, and the black screen with text was already visible when I came
into the room. It did not suddenly appear as a result of my triggering a
return from s
Hiya - I get this too.
HP 15s-eq0507na:
Ryzen 5 3500U + Vega 8 iGPU
8GB DDR4
256GB M.2 NVME SSD
Always had this problem since the release of 20.04 - tried w/ secure
boot on and off.
Haven't tried the iomu=soft thing yet
Others evidently have this problem (I swear I saw a thread ab this on laun
Hi, my pc has been on win10 for months. Was on VM a couple of month
until I got really tired of maintaining 2 setups so I deleted my VM and
now deperately waiting for a fix because I have projects that require
linux. Please help us. Windows is not better than linux but if in this
case, 8 months wit
Fyi,it seems kmously and vicamo are not assigned on the bug anymore. Not
one is looking at it. What to do next ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Title:
'El
Got this from a manjaro forum , wonder if it will work?
https://wiki.archlinux.org/index.php/Lenovo_IdeaPad_5_15are0#Touchpad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Still not working for me. @janitor can you please explain how to apply
the fix. In your text I dont see the bug number rnding in 610.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/
I found the thread I talked about.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971
the laptop the first poster has a 3500U in it according to google and a
few comments mentioned it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
dpkg: error processing package bcmwl-kernel-source (--configure):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu
Same messages about BAR13 and BAR15 in dmesg with Razer Blade 2016,
Ubuntu 20.04.1. Also available to help.
--
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/1426216
Title:
pci driver messa
I just want to add that I have the same problem on my Asus N552VW. I
have managed to make it work from day 1, so hopefully this can help
someone until the proper bug fix is provided.
I have a laptop and an external monitor plugged via HDMI, everything is
turned off. Simply turn on the laptop and l
@Ferenc: even if it didn't work in my case, thank you for helping us
out. I have a Lebovo thinkbook 15 IIL. I can see ELAN0634 in
/sys/bus/acpi/devices but I have no /sys/bus/i2c/drivers/elan_i2c/
folder. The elan_i2c folder isn't there. also, like Filip I am getting
no elan_i2c in the output of
@Ferenc : You made my day. a true HERO !! It is now working on my Lenovo
Thinkbook 15 IIL with Kernel 5.7-14.1 with Manjaro. Thanks a lot I have
just applied a
$ modprobe elan_i2c
before rebooting which made the elan_i2c appear in my lsmod and my i2c drivers.
Thanks Again !
@Filip : maybe
Also, please note that there is no acpidump in Arch. So these commands
should be used instead to decompile and recompile the acpi tables
-Extract the tables cat /sys/firmware/acpi/tables/DSDT > dsdt.dat`
-Decompile: `iasl -d dsdt.dat`
-Recompile: `iasl -tc dsdt.dsl`
Refer to https://wiki.archlin
Hi, I am experiencing a similar issue with the new Lenovo Yoga 720 15"
that just came out (April 2017)
As far as I can tell the touchpad is not detected. I have tried all of the
option suggested above to no avail. Please let me know if I should file a new
bug or if I can provide any additional
My ubuntu box is frozen and there is nothing I can do (i.e. the keyboard is not
working).
Why the kernel is not killing or pausing the processe(s) that are draining the
resources? On my Mac it always stops them and ask to kill it or keep running.
This is the last time I'm using linux(as my main
4.8.0-29 does/did indeed include the fix but never made it out of
proposed and has since been bumped to -31
On Dec 12, 2016, Scott Cowles Jacobs <1630...@bugs.launchpad.net> wrote:
>>4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6
>
>Is "Michael Bock (michi-bock)" referring to a diff
Like I said, -29 was basically renamed to -31. It HAS been fixed since -29 (now
-31)
On Tuesday, December 13, 2016 11:42:11 PM EST Scott Cowles Jacobs wrote:
> The Linux changelog people seem a bit comfused...
>
> I just received Linux 4.8.0-31.33,
> and ITS changlog says:
>
> " * Yakkety upd
Exact same error message after running a do-release-upgrade from Trusty
to Xerial (inside Virtualbox vm)
--
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/1659563
Title:
whenever i
Using Cascardo's kernel fixes the problem for me.
It was a bit of a hassle to install though because there's no linux-
headers-4.4.0-62_4.4.0-62.83_all.deb at the link and linux-headers-
generic depends on it.
Here's where to find it:
amd64:
https://launchpad.net/ubuntu/xenial/amd64/linux-header
Indeed, today the system worked fine (no freezing) the whole day after
rolling back to kernel 3.19 first thing in the morning, while yesterday
afternoon with the 4.2 kernel my laptop froze at least 4 times.
--
You received this bug notification because you are a member of Kernel
Packages, which i
Sorry, in the above comment I meant to say "when I updated the kernel"
instead of "when I updated the bios" before I listed the command
sudo apt-get install linux-generic-lts-wily
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Hi Christopher,
Thank you for your answer. I did update today from BIOS and I will try
the 4.2 kernel again, just not today because I had more than enough and
unexpected "excitement" for a day with updating the BIOS from Linux...
However, like I said before, when I updated the bios, I just used t
I installed again the 4.2 kernel yesterday after lunch and it happened
again at 16:52:02. You can see the kernel messages at that time in
syslog below:
13143 Mar 8 16:14:44 my-ubuntu compiz: pam_ecryptfs: seteuid error
13144 Mar 8 16:17:01 my-ubuntu CRON[10531]: (root) CMD ( cd / && run-pa
To continue the previous comment here is the output of the requested
command:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for ...:
A09
07/30/2015
It looks so far that the laptop freezes less frequent than before the
BIOS upgrade.
** Changed in: linux
Just happened again exactly 11:06:18 (or few seconds before that) today.
>From syslog:
Mar 9 10:41:54 my-ubuntu AptDaemon.Worker: INFO: Processing transaction
/org/debian/apt/transaction/7ed6916c4f3d431293314f8ed30a7023
224 Mar 9 10:42:11 my-ubuntu AptDaemon.Worker: INFO: Finished transact
I installed yesterday evening
linux-image-4.5.0-040500rc7-generic_4.5.0-040500rc7.201603061830_amd64.deb
linux-headers-4.5.0-040500rc7-generic_4.5.0-040500rc7.201603061830_amd64.deb
and left the laptop on during the night (without suspending) and in the
morning was still not frozen. Usually with
When I restarted my laptop in order to boot on 3.19 kernel so that I can
uninstall the 4.5.0-040500rc7 kernel and install another kernel (like
4.4.5-wily) I got a system freeze: it seemed that it happened right
after the system performed the logout. After starting, here is what I
see in the syslog:
I cannot go to upgrade to that daily image because this is the company's
laptop and I have work to do.
What I can tell more than that is that yesterday after lunch I installed
the kernel 4.4.5-040405-generic (from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.4.5-wily/) and that it did not fre
1 - 100 of 499 matches
Mail list logo
