Is this still true?
With Linux 5.10 (Debian bullseye), I can have:
$ fgrep console /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 TZ=:UTC"
GRUB_TERMINAL='console serial'
$ cat /sys/class/tty/con
Cannot reproduce this on any recent MAAS.
--
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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kernel panic
S
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.2
InstallationDate: Installed on 2021-04-17 (124 days ago)
InstallationMedia: Linux Mint 20.1 &quo
l 5.13
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5Ch
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
me seconds.
This will also happen with Kernel 5.13
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorste
roblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
ortVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux
PID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.2
InstallationDate: Installed on 2021-04-17 (124 days ago)
Installat
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
l 5.13
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5Ch
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
y after some seconds.
This will also happen with Kernel 5.13
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
l 5.13
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5Ch
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
Cu
Thx n greez
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
rsion: 2.20.11-0ubuntu27.18
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: thorsten 1292 F pulseaudio
+ /dev/snd/controlC0: thorsten 1292 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: thorsten 1292 F pulseaudio
/dev/snd/controlC0: thorsten 1292 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesk
I ran into this issue in Xubuntu 20.04 (5.4 and 5.8 kernel) aswell.
Changing wifi.powersave from default 3 to 0 (no override = off in my
case) solves it.
Thanks for the info, @Christian.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1887124
Title:
[UBUNTU 20.04] DIF and DIX support in zfcp
My Lenovo T440p (with optimus - i915, nouveau) running 20.04 (Kernel 5.4.0-33)
is also affected.
If I connect an external monitor (Dell U2515H) to it via Displayport it freezes
at boot.
As workaround I switched from GDM to LightDM. With LightDM it boots
straight to the login screen.
--
You rec
Hi,
have a look on:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7/
5.7.0-050700_5.7.0-050700.202005312130
without "nomodeset"
--
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/1877889
T
My e595 is my main develop machine, qt dev, lots of ssh connections, virtualbox
+ many firefox tabs with sometime youtube vids and many thunderbird imap
accounts.
And with the freeze is not even sysreq+"reisub" possible.
The e595 not have a rs232 so i cannot console to second machine, what i wo
please keep an eye on freezes after random time, for me "nomodeset" do
not fix freezes during operation especially in battery mode.
--
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/1877889
T
please keep an eye on freezes, i had such with 5.7.0-994.202005112208
--
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/1877889
Title:
Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
after more hours of testing i do not get any more freeze with
5.7.0-994.20200511220
--
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/1873594
Title:
sporadic black screen freeze on lenovo e
try kernel 5.7.0-994.20200511220
see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594
--
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/1877889
Title:
Intermittent hangs on bo
after a few hours(aprox. 3h) with 5.7.0-994.20200511220 i got a freeze.
--
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/1873594
Title:
sporadic black screen freeze on lenovo e595 Ryzen 37
first boot with 5.7.0-994.202005112208 ok (not use "nomodeset")
[1.808856] [drm] amdgpu kernel modesetting enabled.
[1.813781] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15D8
0x17AA:0x5124 0xC1).
--
You received this bug notification because you are a member of Kernel
Packages
Also freeze occurs with "nomodeset" -> So it is NOT valid workaround.
More freezes if i am on battery only.
--
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/1873594
Title:
sporadic black
Also workaround kernel on 20.4: 5.3.18-050318-generic #201912181133
--
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/1873594
Title:
sporadic black screen freeze on lenovo e595 Ryzen 3700U
Public bug reported:
Hi,
i have sporadic black screen freeze on my lenovo e595 3700U during reboot.
The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT
Problem occure also on
linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64
and
linux-image-unsig
@s: Yes, I have a model with nfc typ: 20KGS03900
@Kai-Heng Fen: I didn’t need the nosleep workaround (second patch). The
first patch from Aaron (https://lkml.org/lkml/diff/2019/2/20/700/1) was
sufficient. (The nosleep option has only been necessary for the kernels
provided by Aaron which were
I do not just claim that, I am just sharing what helped me... With older
kernels my touchpad hardly survived 5 suspends. With 5.3 it just works
(4 weeks without a dead touchpad with at least 50 suspends). Okay the
trackpoint issue is still there but i give a ...
Before that I had to build my own k
The touchpad problem seems to be solved (for me) using linux 5.3. The
trackpoint sometimes still dies but the touchpad keeps working. Luckily,
i don't care about the trackpoint...
I was using mainline 5.3 since 4 weeks on ubuntu 19.04 and i am now
using 19.10 (uses 5.3 by default) since a week and
but is there any update on this 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/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
S
Hi AaronaMa,
I‘ve seen that Dmitry Torokhov has some concerns about your patch and
would like to try another way of fixing it. I just wanted to let you
know that i am still here and able to test your patches :)
best regards
@alinuxuser: the issue is still present for me using the newest
bios/fir
any news? Is the patch submission ignored? This bug is still present in
5.1.6 :/ I am using your patch since you published it and it is working
great, no issues at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Hi, please make sure you have followed all the steps posted by AaronMa
(#94):
1. ensure that the i2c-i801 is loaded! Ubuntu currently blacklists this module
by default in /etc/modprobe.d/blacklist.conf - Thus, the patches won’t have any
effect.
2. ensure that your touchpad AND trackpoint firmwar
@ALinuxUser: the patches are not yet upstream and thus one has to build
a patched kernel yourself. You can follow the upstream process in the
links posted from aaronma.
For some people it is working because they have a different touchpad.
But according to the above discussion even the patches prob
i am now using 5.0.x with your patches and it is working great!
--
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/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on
small update: i am using 4.20.11 with your patches on top since Friday
without any issue! I don't even need the nosleep option.
For others ensure that blacklist i2c_i801 is removed from
/etc/modprobe.d/blacklist.conf ...
--
You received this bug notification because you are a member of Kernel
Pa
Okay, thanks a lot!
--
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/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
Status in linux pack
@Aaron Ma: Thanks for upstreaming! Have you also found time to look into
the crash-on-resume with your kernel, which I reported in #121. Is this
somehow related? I have not encountered a crash with 4.20.x from
mainline.
--
You received this bug notification because you are a member of Kernel
Pack
@AaronMa: Would be really nice if you could post your patch here, so we
could build our own kernels until your patch lands upstream. This would
also allow users of other distros to provide feedback. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which i
Unfortunately, I have to report a strange resume: the screen remained black
after opening the lid. I pressed the powerbutton and after a few seconds and
flickering the screen came back.
The log shows a Kernel Call Trace but also a gnome-shell crash. Thus, I
appended my complete journalctl log. (
thanks for doing this! Could you please also add the debug kernel
parameter which AronaMa requested in #94: rmi_core.debug_flags=0x7 (it
is missing according to your log). Maybe thats also the reason why the
other two logs are empty.
--
You received this bug notification because you are a member
I think you should try it again, even if wireguard is not working. Just
for testing and creating a log of your issue, which would probably be
very helpful for AaronMa and thus for all of us if this damn bug is
finally resolved. Just try somehow to get "journalctl -b 0 -k >
journal.log" after a resu
hi, more feedback from me: i am now running this kernel since sa morning
without any issue with at least 20 suspend/resumes. Just in case, i
appended my journalctl log (but without the debug kernelparameter).
@ALinuxUser: do you see any output when typing journalctl -b 0 -k?
** Attachment added:
Hi, I have performed 11 suspend/resumes and no issue! Big thanks for
looking into it and fixing it!
nosleep mode sounds like a mitigation so that the bug cannot occur but
is not actually fixing it? Is the issue then in the firmware/bios and we
have to contact lenovo or is it still there in the ker
Hi, here is the journalctl log
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5230010/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
I added the kernel parameter and did a suspend/resume and attached the
dmesg log. Btw I never noticed that the trackpoint didn’t survived
suspend/resume (which occasional also happens with 4.19.x)
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+at
I now have performed 5 suspend/resumes and the first 4 times the
touchpad did work 5-40s after the resume. However, after the 5th resume
the touchpad didn’t wake up again (waited 8min).
I also noticed that I can use the touchpad to perform clicks even if the
cursor is not moving (not by using the
Ugh, i think i was wrong, it is working. But directly after a resume the
touchpad is not working and can it can take quite an amount to work
(more than 30s)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Hi, the trackpoint worked well but the touchpad did not after the first
suspend/resume (I really did try to use it). However, I will test it
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
thanks for looking into this issue and trying to fix it. I've installed your
kernel, however, the issue is still there (at least for me). I've attach my
dmesg log. The first suspend/resume at ~122 causes that the touchpad is not
working anymore. There is also
"[ 122.097687] psmouse serio1: Fai
Hi, thanks for the reply. The touchpad stopped working and was
completely unresponsive and was reactivated by the subsequent
suspend/resume. (The trackpoint was working all the time) Is there an
advanced logging which i could activate?
--
You received this bug notification because you are a membe
oky i could reproduce it with psmouse.synaptics_intertouch=0. Here my
dmesg. As above the last suspend/resume restored the touchpad and the
last but one deactivated it.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5222385/+files/dmesg
-
*more info: i am using ubuntu 18.04.1, 4.19.9 from mainline, libinput 1.12.1,
attached is my dmesg, the last but one suspend/resume deactivated the touchpad
and the last one restored it.
i had psmouse.synaptics_intertouch=1, i am now testing
psmouse.synaptics_intertouch=0
** Attachment added:
oky, i now also experienced the issue a couple of times but it only
occurs in 1 out of 10 times and i resolved by an additional
suspend/resume.
In dmesg i see:
psmouse serio1: Failed to disable mouse on isa0060/serio1
--
You received this bug notification because you are a member of Kernel
Packa
Hi, I also have the :00:1f.4 and the nfc model (20KG-S03900) and I
don’t have this issue. Even my trackpoint now survives resumes/suspends
since using 4.19.1 and upgrading all firmware (using windows)
(touchpad/trackpoint/bios/thunderbolt).
I can just repeat the steps, which where necessary fo
Hi, i did a complete new installation with the ubuntu 18.04.1 iso and
the touchpad was always working after suspend/resume only the
trackpoints gets lost. Does it make a difference if s3 is available
during installation?
The only modification i had to do was to remove the blacklist of i2c_i801 in
a small update: the tlp settings have no effect and are thus not
necessary... Even with the settings the trackpoint is sometimes not
working after resume. However, an additional suspend/resume does
activate the trackpoint again!
So removing the blacklist of i2c_i801 (which is a critical bug: #1786
Hi, for me the following combination for ubuntu 18.04 using x1c6 with
nfc (20KG) seems to be working:
- touchpad and trackpoint both enabled in bios
- nfc disabled in bios (because i dont need it, dont know if it would work)
- linux (s3) sleep in bios
- upgrading to the newest kernel, i am using 4
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-firmware (Ubuntu)
** Summary changed:
- busybox sh preseed/late_command
+ Bionic: busybox sh preseed/late_command
** Tags added: netinstall
** Description changed:
- 1) lsb_release -rd
+
Public bug reported:
1) lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
2) apt-cache policy busybox
busybox:
Installed: 1:1.27.2-2ubuntu3
3+4) preseed installation on Bionic, late_command almost the same in
Xenial and there is working
preseed.c
*** This bug is a duplicate of bug 1751266 ***
https://bugs.launchpad.net/bugs/1751266
In Bionic the firmware is in linux-firmware version 1.173
** This bug has been marked a duplicate of bug 1751266
Missing firmware in linux-image-4.15.0-10-generic
--
You received this bug notification
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
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/1761228
Title:
bnx2 firmware
Status in linux
Linux 4.14 is getting rid of its in-kernel firmware/ tree.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b38923a068c10fc36ca8f596d650d095ce390b85
So it will probably be like Debian that you can load missing firmware
during the installation
The GIT repo https://git
I noticed weird network problems on this system aswell, when plugging in
a USB3 external harddisk and on Friday even when I just plugged in my
mobile phone just to load the battery.
Don't know if this is connected in some way. Yesterday I updated the
UEFI/BIOS and will watch if this is still happe
Still present in (X)ubuntu 17.10 with kernel 4.13.0-32-generic.
The trigger is the onboard Realtek network chip on my Gigabyte GA-AB350
Gaming 3 (AMD Ryzen) mainboard:
+-01.3-[01-05]--+-00.0 Advanced Micro Devices, Inc. [AMD] USB 3.1 XHCI
Controller
| +-00.1 Advanced M
(sry for the second post)
then
sudo update-grub
and reboot
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from
hi, thanks a lot! I'm now using 4.13 with this parameter at it is
working fine!
For others you have to edit the file /etc/default/grub and change the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash psmouse.synaptics_intertouch=0"
then
--
Yo
hi, this is also working fine for me
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from suspend
Status in linux packa
Hi, this one is working fine for me!
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from suspend
Status in linux packa
hi, this kernel has the bug
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from suspend
Status in linux package in Ubu
Hi, thanks for the kernels. Unfortunately both are working fine :/ Was
there another commit touching the psmouse-base.c between the good and
bad commit (since i couldn't revert the commit easily)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Hi, i have some problems reverting the commit. This is what i did:
$ git checkout 03b22057e8ed
$ git revert 0ab3fa57425023f42e8822a293d9b87a3ad4e2b3
error: could not revert 0ab3fa574250... Input: psmouse - implement fast
reconnect option
hint: after resolving the conflicts, mark the corrected p
Hi, so i have tried it again with much more testing etc. However, i got
some problems and i had to abort bisecting
so the last good commit was a71c9a1c779f
and the last bad commit was 03b22057e8ed
The amount of commits between these two hashes:
git rev-list ^a71c9a1c779f 03b22057e8ed --count
58
@ kaihengfeng
So i did the bisecting as you described (thanks for that!) and I hope that i
did everything right. For the questions during the config i always just pressed
enter so that the default choice is used.
It's the first time i did this so please be skeptical with my findings!
So after
so i tested some kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline/
and found:
4.11.12 -- working
4.12-rc1 -- bug occurs
i tested it by installing a specific kernel and first verified that two finger
scrolling is working and then tested if it is still working after a
suspend/resume.
W
also occurs on fedora:
https://bugs.freedesktop.org/show_bug.cgi?id=103149
** Bug watch added: freedesktop.org Bugzilla #103149
https://bugs.freedesktop.org/show_bug.cgi?id=103149
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
also affects me! I am using thinkpad t440s
--
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/1722478
Title:
Two-finger scrolling no longer works after resuming from suspend
Status in linux
> Given that and assuming it still has the large performance improvement on
> newer kernel
> I think it's worth an attempt to submit upstream along with the test data.
Did anyone do this and can point me to the discussion in the archives?
FWIW, from *a quick look* it seems the patch that was app
Actually, this doesn't seem to be an error in the kernel itself.
It affects 16.04 and 14.04.5 with kernel 4.4.0-45 and is related to the
propritary Nvidia driver later than 361.42.
Solution: go back to 361.42 which let's flux change the color
immedieately after restarting lightdm.
See: https://g
Is the ability to repro a hold-up on this issue? I can spend time to
provide STRs on an EC2 instance using the latest official 16.04 image,
but I don't want to go through the effort if repro isn't really a hold-
up.
--
You received this bug notification because you are a member of Kernel
Packages
This problem is being triggered every time I don't shutdown cleanly.
Here's my disk layout:
/boot ext4
/ btrfs
One workaround seems to be: booting a CD or USB stick and repairing the
root fs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
For me all works fine since Kubuntu 14.04
But I had to choose 'reset to factory defaults' and restore my changes in BIOS.
(Changing BT / WLAN / other Hardwere settings didn't work.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez i
1 - 100 of 101 matches
Mail list logo
