FWIW, I did the following:
$ git clone git://kernel.ubuntu.com/ubuntu/linux-firmware.git
...
$ cd linux-firmware
$ git checkout bionic
...
$ sudo cp ath10k/QCA6147/hw3.0/* /lib/firmware/ath10k/QCA6147/hw3.0/
The new firmware seems to drop my connections much more infrequently.
Perhaps upgrading
I have had almost identical behavior with a completely different wifi
setup. My card is the following:
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
--
You received this bug notification because you are a member of Kernel
Packages, which is
And FWIW, I did try the generic upstream kernel. Exact same behavior.
Also found this: https://askubuntu.com/questions/967355/wifi-unstable-
after-17-10-update/969282#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: Here's another dmesg.txt with ubuntu kernel version
3.19.0-25-generic #26
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475729/+attachment/4439081/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
The following appeared in dmesg after I got that last dmesg.txt:
[ 831.299129] Raw EDID:
[ 831.299132] 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12
[ 831.299133] 15 13 14 1f 20 23 09 1f 07 83 01 00 00 02 3a 80
[ 831.299134] 18 71 38 2d 40 58 2c 45 00 81 91 21 00
Is it possible to run that kernel with the wl wireless driver? Dell
stupidly ships this laptop with a wireless nic that requires a
proprietary driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I am using the Dell XPS 13 9343. When I plug into a Dell U3014 monitor,
there is a lot of funky behavior. In dmesg I see a ton of backtraces.
I've attached a dmesg output with the traces.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-22-generic
Thanks for that info Seth. I guess I am suffering from multiple issues.
Is there any work on the BCM4352 in the linux kernel right now? This
proprietary driver is a black box.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in
Public bug reported:
I've included a dmesg from after a point when the wireless is no longer
working. Also, I experience frequent panics (caps lock blinking). I
don't know if that is related since I haven't yet been able to get any
information after such a crash. When it crashes that way, I
Okay, so I did some further research. I found that my linux-firmware
package was not upgrading. It was stuck at some ancient version. That is
why I didn't have the updated firmware. The weird thing was that apt-
get dist-upgrade was not showing is as a package that needed upgrading.
However,
FWIW, I can't figure out how to close 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/1395553
Title:
iwlwifi contiually crashes
Status in linux package in Ubuntu:
Invalid
I installed the 3.17 from the mainline kernels from that wiki page. Here's the
uname -a:
Linux braindead 3.17.4-031704-generic #201411211317 SMP Fri Nov 21 18:18:15 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
It fails in a similar way:
[ 167.366951] iwlwifi :02:00.0: Microcode SW error
Oh yeah, this works a million times better with firmware v9 on the
utopic kernel. The V8 firmware appears to be broken with my setup. Is
there any chance that the v9 firmware for the 7620 at
http://wireless.kernel.org/en/users/Drivers/iwlwifi/ can be added to
linux-firmware?
Also, why isn't
It seems to work much better with firmware version 9 on the mainline
3.17.4. I don't see any of the firmware SW error messages. I will reboot
now and try the normal utopic kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I do get this message with the utopic kernel with the v9 firmware:
[ 394.569319] [ cut here ]
[ 394.569358] WARNING: CPU: 0 PID: 1290 at
/build/buildd/linux-3.16.0/drivers/net/wireless/iwlwifi/mvm/tx.c:191
iwl_mvm_set_tx_params+0x5da/0x6d0 [iwlmvm]()
[ 394.569361] Got
There is a performance impact in that my WIFI sometimes drops out with
no seeming cause. I usually have to stop networking and restart it in
the network manager menu. I don't know if this is related to the
microcode software.
I know that I was having some issues in 14.04. However, I don't know if
Public bug reported:
I am getting Microcode SW error detected constantly in my dmesg
output. As a result, I am getting a lot of apport popups. However, the
apport popups are not launching a browser when I say to report the bug.
I am filing this bug with ubuntu-bug linux. Hopefully, all the needed
I am getting the following still.
# docker run -i -t ubuntu /bin/bash
set apparmor profile docker-default: no such file or directory2014/10/13
11:05:41 Error response from daemon: Cannot start container
7981801146ab1771470fd72bc97e6582ff573fa159199f6cb86afaa7eaa74ea9: set apparmor
profile
Just so you know, here's the docker.io package version also:
ii docker.io 1.2.0~dfsg1-1ubuntu1 amd64Linux container runtime
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also tried the 3.17.0-031700-generic #2001410060605 linked above. It
also does not work on that kernel.
# docker run -i -t ubuntu /bin/bash
Unable to find image 'ubuntu' locally
Pulling repository ubuntu
1357f421be38: Download complete
511136ea3c5a: Download complete
1de2bd7201a2: Download
I just found that the apparmor profile for docker was disabled for some
reason. After removing the symlink from /etc/apparmor.d/disable/docker,
it works. I don't remember ever adding docker to the apparmor disable
links.
--
You received this bug notification because you are a member of Kernel
So, it seems like the kernel problem is solved. Now, where do I file a
bug about crappy behavior of the touchscreen in Xorg (and Unity as a
result)? I don't want to clutter this bug with that info.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Just rebooted into this kernel. Seems to be working so far.
wt
On Thu, May 15, 2014 at 12:12 PM, Kent Baxley 1305...@bugs.launchpad.netwrote:
Also tested acelan's kernels with an XPS15 (model 9530) which has the
same touchscreen but a non i2c synaptics touchpad. The touchscreen and
So I loaded the module, there are no messages generated in dmesg as a
result.
Also, I ran this in another window while loading the module just to make sure:
# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the
Here's the logs just after reboot. I also added a uname -a to make
sure that it's clear which kernel version is being used.
FWIW, when I rebooted the laptop, it locked up on the dell bios screen.
I had to cold boot to get it to boot into ubuntu. This probably was more
prevalent before the latest
Here are logs for the above linked kernel.
Uname for reference:
$ uname -a
Linux braindead 3.13.0-24-generic #46 SMP Tue Apr 22 09:25:58 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
** Attachment added: requested logs for 3.13.0-24-generic kernel
I just realized that this kernel has broken my touchscreen. Is that
expected?
--
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/1265885
Title:
regression: SynPS/2 touchpad detected as
Is this fix expected to break my touchscreen?
--
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/1305522
Title:
Backport Synaptics HID touchpad driver for 14.04
Status in “linux” package
I just wanted to report in and say this is still working great. Thanks
for the hard work on this. This will be great for anyone else using the
same hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is probably going to be fixed when bug 1265885 is. There is a
working kernel that was linked to the other bug. I don't know if the
patch has made it to a stable kernel yet.
FWIW, this bug may just be a dupe of bug 1265885.
--
You received this bug notification because you are a member
Great news! With the new kernel, everything seems to work like when I
don't blacklist the driver. The devices are named differently though.
wt@braindead:~$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer
Do you want me to install that kernel? Or are you talking to Janus?
--
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/1265885
Title:
regression: SynPS/2 touchpad detected as DLL060A:00
This bug doesn't appear to exist in the new Trusty release.
--
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/1263219
Title:
kernel panics with BUG
Status in “linux” package in Ubuntu:
What is the fix that was released? Do I still need to blacklist in
trusty?
--
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/1265885
Title:
regression: SynPS/2 touchpad detected as
The latest proposed kernel fails even worse than my original report. The
conditions when it fails (that is when the iwlwifi module is loaded) is
the same. However, now blacklisting iwlwifi and then manually modprobing
it after logging in locks up the system such that I cannot capture the
dmesg.
Okay, I am booted into the kernel @http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-saucy/. It works just fine. This seems to be a
mainline 3.11 kernel. Does that help close the gap for where the problem
showed up?
--
You received this bug notification because you are a member of Kernel
I am just curious. Is saucy going to be updated? It might be a shocker
to someone when they can't get a network connection on saucy?
--
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/1263219
I can confirm that that kernel version v3.13.1 from the above line still
has the bug. I can also confirm that blacklisting i2c_hid makes the
touchpad work in that kernel version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The version 3.13.1-031301-generic also seems to work without issues.
--
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/1263219
Title:
kernel panics with BUG
Status in “linux” package in
Work with regard to the iwlwifi module, that is.
--
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/1263219
Title:
kernel panics with BUG
Status in “linux” package in Ubuntu:
Incomplete
The iwlwifi module works fine with a kernel based on Linus' tree that I
compiled this morning.
--
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/1263219
Title:
kernel panics with BUG
With code based on linus' tree in a git clone that I git pulled this
morning, I get the same results. I have attached the dmesg.
** Attachment added: dmesg from linux-3.14.beforerc1
There are all kinds of ACPI errors in the dmesg.
--
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/1265885
Title:
regression with respect touchpad
Status in “linux” package in Ubuntu:
I just tried another of the generic kernel. Here's some info:
wt@braindead:~/Documents$ cat linux-3.9.0-030900.has_touchpad_controls.txt
uname -a
Linux braindead 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep syn
[ 10.221126]
Bah, I guess that was expected since the 3.11 series of kernels worked.
--
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/1265885
Title:
regression with respect touchpad
Status in “linux”
This bug is appears to be a duplicate of bug 1263319. However, I have
not reinstalled. I would really like to help make sure this issue is
handled properly so that other don't upgrade into this state like I
did.
--
You received this bug notification because you are a member of Kernel
Packages,
Here's another data point as I just tried another of the generic
kernels. Version 3.12.0-031200-generic #201311071835 has no problems
with the iwlwifi AFAICT.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I just tried the kernel you pointed me to (version
3.12.0-031200-generic #201311071835) does not show the touchpad
controls. And just for the record, I don't see any of the messages I
posted above shortly after boot. Here's proof:
wt@braindead:~$ dmesg | grep syn
wt@braindead:~$
--
You received
I am sorry. I have been extremely busy these past couple weeks. I'll try
to make some progress soon.
--
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/1263219
Title:
kernel panics with BUG
I am sorry. I have been extremely busy these past couple weeks. I'll try
to make some progress soon.
--
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/1265885
Title:
regression with
FTR, there is a crash with 3.11.0-15.16. It looked different though. It
happened after I saw the message about searching for Btrfs filesystemss.
I don't have any more info at this time. I want to try the 3.11.0-15.22
kernel and maybe the latest trusty kernels. Where do I find them?
--
You
Okay, so I found 3.11.0-15.23. Is that the one you'd like me to test at
this time?
I found it: at http://archive.ubuntu.com/ubuntu/ubuntu/pool/main/l/linux
/linux-image-3.11.0-15-generic_3.11.0-15.23_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages,
Okay. I loaded the trusty linux-image+extras (3.12.0-8-generic) into
saucy. There are no problems with wifi in this version. Dmesg is clean.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Okay. I loaded the trusty linux-image+extras (3.12.0-8-generic) into
saucy. There are still no input settings for my touchpad in the system
settings.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@jsalisbury, I only see 15.16...where do I get that one from?
@Christopher. I'll see what I can do as this is my work laptop.
--
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/1263219
FWIW, a new issue has cropped up with the new kernel. It looks like my
touchpad disappears after resume from suspend for the night.
--
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/1263219
Well, I see the touchpad in the xinput list. It's just that the options
for the touchpad are gone in the System Settings.
--
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/1263219
Title:
Is there a bug for the suspend? I have additional information I don't
want to pollute this bug with.
--
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/1263219
Title:
kernel panics with BUG
For the record, the problem doesn't to be related to resuming after
suspend, I have the same touchpad problem after reboot with the new
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
This regression occurs somewhere between 3.11.0-14-generic (latest on
saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier
kernel, I actually get settings for setting up my touchpad in the unity
interface. With the updated kernel, those options disappear. I
Filed new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885
--
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/1263219
Title:
kernel panics with BUG
Status in “linux”
This kernel BUG does not occur on kernel version 3.12.6-031206-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/1263219
Title:
kernel panics with BUG
Status in “linux” package
This regression is present in kernel version 3.12.6-031206-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/1265885
Title:
regression with respect touchpad
Status in “linux”
I am just warning you that this problem may existing in what will become
trusty. Is this not a valid bug to file in that case?
--
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/1265885
Sorry for the delay...holidays and all. I installed version
3.13.0-031300rc6-generic, which is beyond what was listed above. I hope
that is okay. Everything seems to work just fine in this kernel. No
panics and no BUGS during boot. Dmesg is also clean.
** Tags added: kernel-fixed-upstream
--
FTR, here's the kernel version that's failing to boot:
$ dpkg -s linux-generic | grep Version
Version: 3.11.0.14.15
I see a number of other kernels associated with saucy in the list at
http://kernel.ubuntu.com/~kernel-ppa/mainline/. Are there updates that
haven't made it to saucy yet?
--
You
Public bug reported:
I have a Dell Sputnik 3 that I just got and upgraded it to
12.10-13.04-13.10. On boot the kernel crashes with a BUG. I can
prevent the crash by blacklisting the iwlwifi module and I can cause the
BUG by manually loading the module. I will attach a dmesg output from
after the
Here is the dmesg output.
This info is a little tricky to collect since I can't bring up my
network (or shutdown my computer normally) after the BUG occurs. I have
to boot into a 13.04 kernel to actually post this info. :) Does the
apport store the output locally somewhere that will survive a
68 matches
Mail list logo
