** Description changed:
This seems to be a return of an existing bug, in newer hardware and
microcode versions.
Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
Firmware version: 34.0.1
Description:Ubuntu 18.04.1 LTS
Frequent errors as soon as I conn
Public bug reported:
This seems to be a return of an existing bug, in newer hardware and
microcode versions.
Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
Firmware version: 34.0.1
Description:Ubuntu 18.04.1 LTS
Frequent errors as soon as I connect to wifi:
Microc
dmesg output.
Note: lately the perceived effect of this issue seems to have gotten
better. I still see the error in the logs, but wifi performance is
acceptable.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804841/+attachment/5223175/+files/d
It's what Ubuntu 18.04.1 fully updated has... ¯\_(ツ)_/¯
--
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/1804841
Title:
iwlwifi Microcode SW error detected. Restarting 0x200.
@sforshee: No, wifi had been stable on Bionic before that. Somehow it seems
quite stable again now. I got this laptop in September, so I installed Bionic
directly.
I have checked my syslog, and I don't see the microcode loading errors anymore.
--
You received this bug notification because you a
@paelzer: agreed. I also tried getting later firmwares from Intel's git
repository and made no difference. I'll keep an eye out as well.
--
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/b
Public bug reported:
Ubuntu 14.10 installed on Macbook Pro 9,2, with Broadcom 14e4:4331.
Using b43 driver, connection randomly drops, and only way to recover is
shutdown and reboot.
With Mac OSX, same network, connection is absolutely stable.
Network is using WPA2-AES Personal, with Ruckus acces
It seems this is a hardware driver problem. It has been reported to the
upstream kernel in these 2 bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=115631
https://bugzilla.kernel.org/show_bug.cgi?id=120181
It does not look very good. Not much progress...
** Bug watch added: Linux Kernel Bug Trac
Hello,
I have in my hands a slightly different Asus E205SA. This one comes with an
Elan Touchpad.
On the outside it looks exactly the same.
The other E205SA with the malfunctioning touchpad, has vendor id "0b05", which
is:
vendor: 0b05 ("ASUSTek Computer, Inc.")
Could it be that ASUSTek touchpad
Hey, joining the bug.
I have an Asus E205SA, which is a great little device.
I've just tested with Kernel 4.6 from Mainline, and it seems to improve things
somewhat, as the sensitivity of the touchpad is more manageable, but still only
detected as a mouse.
Happy to help test more.
Kernel 4.7rc1 f
10 matches
Mail list logo
