apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1869531/+attachment/5342687/+files/CRDA.txt
--
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/1869531
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1869531/+attachment/5342695/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Public bug reported:
I have cryptoswap set up both with the 2 GB default swap file and an 8
GB swap partition with 8 GB of ram. However, the system does not use
this swap when it should. For example, if I run a little test code
which attempts to allocate 10 GB of memory in 1 GB chuncks, the syst
The code that I used to force failure, memtest.c, is attached to the bug
report.
--
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/1762468
Title:
Cryptoswap not working in Bionic
Status in
It seems that cryptswap is working correctly on 17.10 with the kernel
4.13.0-36-generic on a different machine using the same test as
described above. I tried the same kernel (4.13.0-36) on 18.04 (machine
used in original post) and it still fails. Of course, I checked that
the swap appears in /pr
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of cour
The first kernel on that list that exhibits the bug is the first one:
4.14 Final. Recall: the bug results in a full up hang. The disk stops
swapping (it's audible). I can reboot with sysctl SUB however.
I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
4.11.12-041112-generi
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.
On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final. Recall: the bug results in a full up hang. The disk stop
In response to #7, I don't think this is the same issue. The cryptswap
initiates with no difficulties, timeouts, etc. on boot. When I first
installed Bionic, ubiquity did not correctly install the swap, and I
filed #1759253 on that issue.
--
You received this bug notification because you are a
Some good and bad news: I have been testing this in a running Gnome 3
environment. I decided to start testing on console. On console, all
kernels seem to fail using crypt swap. This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime
condition.
How
In case it is helpful to anyone else, I found a resolution for my
specific case. This askubuntu question helped:
https://askubuntu.com/questions/1018907/ubuntu-installation-stuck-at-
random-crng-init-done . In sum: sudo apt install rng-tools
About 1 week ago, my Ubuntu 18.04 boot time went from ~1
This happens to me with 4.10.0-20 in Zesty KDE. It happens to me with a fresh
install and only when using a fresh firefox profile, with and without flash
enabled (and having a lot of tabs open); it leaves a zombie process after
manually killing it, but then the system locks in about a minute.
If
This seems to be the same problem reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
** Bug watch added: Red Hat Bugzilla #1506339
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
When using with dock, attached monitor is not detected, laptop monitor
remains blank. Requires a reboot
4.4.0-59 works fine. I'm guessing this is due to the i915 patches for
DP.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
Also, and not sure if this is related, Plymouth does not correctly
render the splashscreen on boot up. Part way through, the screen blanks
and only the "dot icons" are visible. Again, this does not occur for
earlier kernels.
--
You received this bug notification because you are a member of Kern
Another thought: I'm using the modesetting driver, not the intel driver.
--
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/1662381
Title:
linux-image-4.4.0-62-generic breaks Lenovo T440s on
I am happy to report that linux-image-4.4.0-63-generic from xenial-
proposed _is_ working correctly with the T440s on and off the dock. So
the bug is gone from the -proposed kernel package.
Thanks for that!
If we could only get the DP audio to work on the dock, sigh. It hasn't
worked since Kern
I think the solution to this bug is
systemctl enable bluetooth
You have to enter your password 4-5 times and then reboot. It worked for
me. can someone else try it to confirm on Asus laptops with this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which
So I think I managed to fix this bug with
systemctl enable bluetooth
then reboot. I don't seem to have the problem anymore.
--
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/1523108
Title:
Public bug reported:
used pm-hiberate. hibernate works in other releases
ProblemType: KernelOops
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-8-generic 4.10.0-8.10
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
Annotation: This occurred
** Tags added: fixed patch-accepted-upstream
** Tags removed: amd64 apport-kerneloops fixed hibernate
patch-accepted-upstream resume zesty
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
I'm pretty sure this happens because we wind up re-computing the same
watermark values for each CRTC multiple times in a single atomic
transaction (once per CRTC involved in the transaction). I'm putting
together some patches that make SKL watermarks play more nicely with
atomic (and eliminate thi
(In reply to Prasad H L Bhat from comment #34)
> I get the same error sometimes on my T460 laptop with Intel HD Graphics 520.
> When it occurs, it freezes the laptop completely (display turns off, no
> virtual terminals work, audio buffer keeps looping if present when freezing).
I don't think the
This series should fix this defect once it gets reviewed and merged:
https://patchwork.freedesktop.org/series/5158/
--
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/1523088
Title:
WARN_
Latest version of the patch series that includes a fix for this is available
here:
https://patchwork.freedesktop.org/series/5158/
--
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/1523088
Note that the series linked above is fully reviewed now, but we probably
want to hold off on merging it until one more issue is fixed.
Apparently some BIOS can setup an unusual/unexpected initial DDB
allocation that causes us problems when we try to inherit it and use it
for subsequent watermark ca
Here's the latest revision of the patch series to fix this bug:
https://patchwork.freedesktop.org/series/6944/
Since I got a few offline questions last time, the patches here are
meant to be applied on top of the drm-intel-nightly branch of
git://anongit.freedesktop.org/drm-intel
--
You recei
Still seeing this in 4.4.0 kernels on Ubuntu 16.04.
$ dmesg | grep -i blk
[5.660121] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 60.473635] b
Works for me with kernel 4.5.0-040500-generic in Mint 17.3
--
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/1514066
Title:
Touchpad not working on ASUS ZenBook UX305CA-FC037T
Status in Li
My problem is, that I doesn*t be able to install ubuntu 14.04 on a T61
IBM Thikpad. The Version 12.04 runs, but 14.04 not!
At the installation the Display stand still. If you press ESC-Button you
can Read: "Check Batary state [OK]", than is end of gecko!
If you press ESC again, the last sequ
It might be useful to look at these Fedora bz entries. Not sure.
https://bugzilla.redhat.com/show_bug.cgi?id=1046935
https://bugzilla.redhat.com/show_bug.cgi?id=1069403
** Bug watch added: Red Hat Bugzilla #1046935
https://bugzilla.redhat.com/show_bug.cgi?id=1046935
** Bug watch added: Red Ha
Summary:
This is fixed in kernel 3.17-rc1.
Detail:
Researching this for my daughter (Ruth Marsden) I've found this issue has been
known on the kernel mailing lists for sometime. See
http://www.spinics.net/lists/linux-input/msg29123.html.
The issue relates to touchpad devices using the ALPS v7
Public bug reported:
I have a Samsung NP870X5G (ativ book 8) notebook with an Intel Wireless
7260 dual band card. As others (e.g.:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305305) I
experience random disconnections. I also have problems connecting to
certain wifi spots that I could pr
During the past week, this issue has reappeared: upon resume from a
system suspend, sytem initially starts, but freezes with blank screen,
and does not respond to Crt-Alt-F1 or any other input. Associated with
this problem, I presume, was a failure the wine software, requiring its
re-installation t
Public bug reported:
Using Ubuntu 14.04. Recently updated to kernel version Ubuntu
3.13.0-30.54-generic 3.13.11.2
I expect brightness of my LCD screen to remain the same and be
controllable after waking from suspend. It doesn't and isn't.
This seems to have only started recently - presumably a
Clarification:
Screen does not always come up dimmed after suspend. Screen comes up
with setting prior to suspend.
If the computer has gone into suspend itself after being unused for a
certain amount of time it comes up dimmed, even if not deliberately set
to this by the user. In these circumst
Upgrade to Ubuntu 3.13.0-30.55-generic 3.13.11.2 does not solve the
problem.
--
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/1338063
Title:
Brightness control lost after suspend screen di
Christopher, thank you for your advice and my apologies for not
following the protocol of first checking for BIOS updates.
I have now updated the BIOS. Results of "sudo dmidecode -s bios-version &&
sudo dmidecode -s bios-release-date" are:
Version 1.80
04/18/2013
so the update has worke
Installed latest upstream mainline kernel: 3.16.0-031600rc4-generic
Unfortunately this failed to solve the problem. Brightness control on
systems settings and via function keys works on initial boot but ceases
to work after a suspend, as before.
Thank you for your help.
** Changed in: linux (
Clarification:
I have gone back to older kernels on my machine to confirm my feeling
that this only started happening recently. The oldest kernel on my
machine is 3.8.0-31-generic. The problem also occurs with when booted
with this kernel so my feeling that this was recent is wrong.
I have edit
.
c) Searched dmesg.txt for "Magic number" and got:
.
[0.864274] Magic number: 6:405:689
[0.864395] rtc_cmos 00:05: setting system clock to 2014-07-09
15:41:36 UTC (1404920496)
.
d) Searched dmesg.txt for "hash mat
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148945/+files/dmesg.txt
--
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/1338063
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148946/+files/Xorg.0.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/13380
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148947/+files/Xorg.0.log.old
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
In answer to "did this problem not occur in a release prior to Trusty?":
I'm sorry, I don't know for sure. I only noticed the problem the day I
first reported it, however my behaviour regarding shutdowns rather than
suspends has recently changed so that may well be why I noticed it. My
wife hadn
In answer to: "if you remove the kernel parameter elevator=noop does this
change anything?"
No it does not change anything. I tried with this kernel parameter removed on
the latest mainline upstream kernel 3.16-rc4.
As requested, tested on Precise 12.04.0 and 12.04.3 both obtained from
http://o
I have a setup with Ubuntu 14.04 LTS server. The /boot is not on a
separate partition. I followed the kdump setup as mentioned in
https://help.ubuntu.com/14.04/serverguide/kernel-crash-dump.html
After triggering the kdump, system panics but system never
comeup/reboot. It get stuck at the call trac
I have tested against the kernel at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.16-rc5-utopic/ and can confirm that the bug as reported
still persists.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-upstream-3.16-rc4
** Tags added: ke
Public bug reported:
The Trusty Tahir Hardware Enablement Stack for Ubuntu 12.04 is available
and being aggressively promoted to existing Ubuntu 12.04 deployments
running now End-of-Life Hardware Enablement Stacks. However, the linux-
cloud-tools packages have not been made available to Precise us
Not sure apport-collect is helpful for this particular bug? It crashes
regardless:
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py cr
Christopher, Thank you for your guidance on this issue. I want to make
sure I report this upstream in the correct way and am unsure of which
upstream list I should be using.
https://wiki.ubuntu.com/DebuggingKernelSuspend mentions says "Suspend and
Resume use facilities within your BIOS called AC
This bug has been quiet for a while by the looks of it so just chipping
in. I can confirm I witnessed this bug last week on an Ubuntu 14.04 x64
VM on a Windows Server 2012 R2 Hyper-V server with dynamic memory
enabled on the guest. I suspect that dynamic memory (aka. memory hot-
add/remove) may be
Reported upstream. See http://marc.info/?l=linux-
acpi&m=140658075422146&w=2.
As requested from upstream am attaching output from acpidump as
acpidump.txt
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4165307/+files/acpidump.txt
Workround provided from upstream dialogue - Thank you Aaron.
See http://marc.info/?l=linux-acpi&m=140686098023199&w=2
In summary:
Switching to use the "intel-backlight" interface rather than the "acpi_video0"
interface makes the controls for brightness work after suspend. This can be
done by
Hi Joe, I just pulled 3.16.0-33.44 from utopic-proposed. The clickpad
functions properly with this kernel and the "stuck click" issue is not
present. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Just found this same abovementioned /.rpmdb directory on my install. It
wasn't there before and hasn't ever been there before this morning. I
did not do anything involving a kernel. Although vmware player uses
dkms when a new kernel is installed, no new kernel was installed today.
When will 4.11.
I have an HP Stream 11 and am also seeing the "stuck click" problem. I
built with the patch in comment #19 and can confirm that the problem is
now fixed. Also I believe bug #1394869 is about the same issue.
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Tags added: kernel-fixed-upstream-3.19-rc1
--
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/1398533
Title:
[HP Stream Notebook - 11-d010nr] clickpad malfunctions after
performing a cl
Public bug reported:
On the HP Stream 11, when the touchpad is physically depressed for a
click (as opposed to a soft-tap) the mouse button down event happens,
but the mouse button up event never happens, making further clicks
impossible. You can observe that this is the case by running:
sudo evt
Hi Joseph, the issue still seems to be present with the test kernel:
> $ uname -a
> Linux stream 3.16.0-30-generic #40~lp1414894v1 SMP Tue Jan 27 19:19:33 UTC
> 2015 x86_64 x86_64 x86_64 GNU/Linux
> $ cat /sys/module/hid_rmi/srcversion
> 19894E2E646AB84E0BCFBED
> $ sudo evtest /dev/input/by-path/
Yes, the latest test kernel resolves the problem:
> $ uname -a
> Linux stream 3.16.0-30-generic #40~lp1414894v2 SMP Wed Jan 28 19:06:42 UTC
> 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> $ cat /sys/module/h
@Jose #56:
lsusb does as you say. There is a bit more with -v. Identical on
Fedora 19.
I don't see the dmesg errors that you see.
I said that touch was working with 12.10 to some extent (I didn't test
much).
Well, it isn't working on 13.04. The first and maybe second click
"work" but after t
How can I "nominate" this for Precise? Quantal? Raring? I've
experienced the symptoms with each (not all the same).
--
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/791833
Title:
Dell S
That is correct. The default raring kernel will be very disappointing
for people that are experiencing the problems outlined in this thread.
It seems that only >3.9.7 has a usable kernel for affected Sandybridge
users (I am using a Lenovo X220). Even then, the bug remains at some
level but it mo
Public bug reported:
I have an ASUS X201E notebook running a manufacturer install of Precise.
I know gnome-panel and the fn keys worked in 3.2.0-52, and have reverted
back to that kernel. Up to this point, everything worked very nicely,
and as of the kernel switch, things started breaking. At GNOM
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812435/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812438/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812442/+files/Lspci.txt
--
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/1223152
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812437/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
apport information
** Attachment added: "Card0.Codecs.codec.3.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812439/+files/Card0.Codecs.codec.3.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812434/+files/AlsaDevices.txt
--
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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812436/+files/CRDA.txt
--
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/1223152
Ti
apport information
** Tags added: apport-collected
** Description changed:
I have an ASUS X201E notebook running a manufacturer install of Precise.
I know gnome-panel and the fn keys worked in 3.2.0-52, and have reverted
back to that kernel. Up to this point, everything worked very nicely,
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812440/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812441/+files/IwConfig.txt
--
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/12
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812444/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812450/+files/RfKill.txt
--
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/1223152
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812451/+files/UdevDb.txt
--
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/1223152
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812452/+files/UdevLog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812448/+files/ProcModules.txt
--
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
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812447/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812445/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812449/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812446/+files/ProcEnviron.txt
--
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
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1223152/+attachment/3812443/+files/Lsusb.txt
--
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/1223152
Public bug reported:
sudo apt-get --reinstall install bcmwl-kernel-source
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 32 not upgraded.
Need to get 0 B/1,301 kB of archives.
After this
I am unsure how to procede.
--
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/1223152
Title:
Kernel 3.2.0-53 gnome-classic/gnome-panel to load slowly, laptop fn
keys not working
Status
Issue was resolved in kernel update 3.2.0-54
--
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/1223152
Title:
Kernel 3.2.0-53 gnome-classic/gnome-panel to load slowly, laptop fn
keys not
I got a Samsung ATIV NP940X3K-K02US which has the Qualcomm atheros
QCA6174 / NFA354 card.
I tried to follow the directions in #201.
1) I have the 4.1.1 kernel working
2) I 'm not sure what all needs to be installed. "all required firmware from
previous posts" was kind of vague. I cloned
https:
$ lspci | grep Network
01:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
$ iwconfig
eth0 no wireless extensions.
lono wireless extensions.
$ ifconfig
eth0 Link encap:Ethernet HWaddr 24:f5:aa:d3:d3:d3
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask
I tried the .deb in #209 but it didn't work for me.
-
Installation seemed okay
-
$ sudo dpkg --install ath10k-dkms_1.0_all.deb
[sudo] password for acampbell:
Selecting
I forgot: That was on a Samsung ATIV NP940X3K-K02US which has the
Qualcomm atheros QCA6174 / NFA354 card. I have tried most of the other
solutions here too, so maybe there was something that came from one of
those that's causing the issue? (that's how I ended up with a 4.1.1
kernel)
--
You receiv
$ dmesg|grep ath10k
[1.316648] ath10k_pci :01:00.0: enabling device ( -> 0002)
[1.319367] ath10k_pci :01:00.0: pci irq msi-x interrupts 8 irq_mode 0
reset_mode 0
[1.521673] ath10k_pci :01:00.0: Direct firmware load for
ath10k/cal-pci-:01:00.0.bin failed with error
I tried the new 1.1 package. It seemed to install okay, but didn't work.
I was on the 4.1.1 kernel, so I removed that (apt-get purge) as well as
the ath10 package. I rebooted into the 3.19 kernel, re-installed the
ath10 1.1 package, and restarted again. Still nothing.
-
Eureka! It works! If you're still having issues and had tried adding the
firmware yourself before, I had to remove it:
1. sudo apt-get -y purge ath10k-dkms
2. rm -rf /lib/firmware/ath10k/
3. sudo dpkg --install ath10k-dkms_1.1_all.deb
4. {restart}
5. {rejoice}
Also of note, I removed my USB wifi
I'm not getting quite as good speeds with this as I can with the same
card on Windows right now. With the Internet I'm at, I'm getting
anywhere from about 30-60mbps up and down with this deb, and I get about
150mbps up and down consistently in Windows. To me, that's perfectly
workable, but I though
*** This bug is a duplicate of bug 1514785 ***
https://bugs.launchpad.net/bugs/1514785
The recent Ubuntu 15.04 kernel update to vmlinuz-3.19.0-37-generic installed
this same bug.
I had to reboot back to vmlinuz-3.19.0-33-generic to avoid the loop.
--
You received this bug notification becau
The recent Ubuntu 15.04 kernel update to vmlinuz-3.19.0-37-generic installed
this same bug.
I had to reboot back to vmlinuz-3.19.0-33-generic to avoid the loop.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
I just got bit by this, too. Was transferring ~40T via rsync to a new
NAS setup... got about 12T in and it just stopped. Eventually realized
the mountpoint was unresponsive. Rebooting and kicking rsync back off
resulted in the same scenario almost immediately. The machine in
question is runnin
I've also gotten bitten by this. Upgrading to Ubuntu 21.10 caused weird
filesystem issues to be present on my ZFS filesystem, with errors on the
command-line such as:
Cannot access 'foobar': No such file or directory
When running ls -l in some directory, I get question marks, like this:
-???
301 - 400 of 434 matches
Mail list logo
