With 19 more months of support for 16.04 (and the 4.4 kernel), consider the
8723bs drivers in the
trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/
trusty-chestersmill public)
These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API
change broke many
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the
8723bs drivers in the
trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/
trusty-chestersmill public)
These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API
change broke many
The bluetooth firmware load (hci0) below from a working device on a 4.19 kernel
is missing from the
above posted dmesg output (firmware versions identical). There are new
firmware versions in 20.04, so that may be contributing cause to the loading
problem.
7.768840] RTL8723BS: rtl8723bs v4.
Delete the above observation of a later version of the firmware being
available, the
rtl8723bs v4.4.1_17245.20160325_BTCOEX20151223-654a is actually the original
Intel version.
on the Ubuntu 14.04 supplied on the Intel Compute Stick.
--
You received this bug notification because you are a memb
On an Intel Compute Stick the Xubuntu 18.04 upgrade to 20.04 resulted in
a working rtl8723bs bluetooth (and wifi) for a 5.4.0-29 kernel. Before
upgrade, a 5.3 kernel was tested and three additional modules needed to
be loaded manually (the first time) to make the Bluetooth work: hidp,
btbcm, and r
I am having trouble loading the rtl8723bs firmware for a 5.5 kernel on
AntiX 19, (a Debian 10 sans systemd/Gnome). This bug on a 20.04
install with the 5.4 kernel may indicate early issues, but I withdrew my
"does this affect me" checkoff since the 5.4 kernel is working for me.
--
You received
The working 5.4 kernel on Lubuntu 20.04, on Intel compute Stick STCK1A8LFC with
the rtl8723bs hw.
$ cat btm-54.dmesg
Lubuntu 20.04
$ uname -a
Linux xleef 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
Previously connected generic Bluetooth 2.4G mouse
I confirm that Bluetooth now works on the Intel Compute Stick STCK1A8LFC
with the rtl8723bs hardware for the 5.7.0-050700 #202005312130 kernel
from the above link. dmesg showed the expected Bluetooth firmware
loading, and all necessary modules were automatically loaded.
--
You received this bug
Did you scan the dmesg output for firmware loading errors? Try dmesg
|grep -i firm and dmesg | grep 8821 and report results here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/185366
On a Lenovo W520, kernel 4.15.0-33, changing the UEFI Settings for the
Security Chip to "disabled" from "ignore" eliminated both this mei-me
error, and the tpm error , both of which were appearing on the black
screen which appeared briefly after a resume.BIOS revision 8BET62WW
(1.42 ), Firmware rev
After a few weeks running the 4.15.0-33 kernel, I have seen the hbm...
message twice, much less frequently than before turning off the security
chip, but it's not totally gone.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
*** This bug is a duplicate of bug 1385113 ***
https://bugs.launchpad.net/bugs/1385113
** This bug has been marked a duplicate of bug 1385113
hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
--
You received this bug notification because you are a member of Kernel
Packages, which
Ubuntu 18.04 still has the "unknown main item tag", occurring on a Thinkpad
W520 after a suspend, but the Bluetooth Microsoft Sculpt Comfort Mouse now
reconnects successfully.
dmesg grep ...
[34731.172621] hid-generic 0005:045E:07A2.0013: unknown main item tag 0x0
[34731.172743] input: Microsoft
Ubuntu 18.04 running bluez 5.37-0ubuntu5.1 has fixed the 16.04 problem
of bluetooth not running after a suspend. My mouse has successfully
reconnected 100+ times. The USB inputxx is still incrementing at each
resume, so that may not have been related to the problem.
--
You received this bug not
After the 4.15.0-124 kernel update, I started noticing the mei_me error
messages at the initial startup screen (which usually only had tpm errors),
although othing fails to work.
$ dmesg |fgrep mei
[ 2022.278241] mei_me :00:16.0: hbm: properties response: wrong status = 1
CLIENT_NOT_FOUND
Two weeks of running kernel 4.0.15-23 did not produce the error when
returning from suspend. After the kernel update to 4.0.15-29, the error
appears nearly every return from suspend, much more frequent than with
the 4.0.15-24 kernel. Again, no adverse effects are seen from the
error.
--
You rec
The bluetooth failure to resume after a suspend seems USB related. The failure
happens
about 50% of the time, and when it does, disabling bluetooth and restarting
fixes
it.
On a Lenovo W520, Ubuntu 16.04, 64 bit, kernel 4.4.0-98-generic, Microsoft
Sculpt
Comfort BT mouse.
Looking at dmesg|tail
On Lenovo w520, Ubuntu 16.04, kernel 4.4.0-57-generic, bluez 5.37-0ubuntu5,
unity desktop.
Same error messages relating to "Not enough free handles to register service".
Resuming from suspend results in bluetooth icon in title bar grayed out,
bluetooth switch is OFF, and bt mouse non-functional.
Ubuntu 16.04 patched to date.
Below is the sequence of re-enabling the bluetooth mouse after suspend. Note
that
either of two different things being blocked, tpacpi_bluetooth_sw, and hci0,
will
keep the mouse from working.
After a resume from suspend, the title bar bluetooth icon is greyed out.
Ubuntu 14.04.1 using the open source firmware in /lib/firmware/b43-open,
without the /lib/firmware/b43 files no longer displays the 60 second
delay on shutdown (on the same hardware with the original problem).
Looks like this has been fixed sometime in the last two years.
--
You received this bug
The last update of Ubuntu 16.04 (kernel 4.4.0-36 to 4.4.0-38) reduced
the failure to reconnect of my Microsoft Sculpt Comfort BT mouse from
90% to 15%. Something improved a lot. The fix I have been using was to
pull up the settings/bluetooth, turn off bluetooth (it says on when the
window is star
Downloaded the Sept 20 desktop 64 bit ISO, and on a Secure Boot UEFI
laptop running 13.04, created USB install media, and installed to
another USB set up with gpt and an EFI partition. Booting the target
USB worked in secure mode, with the signed kernel being used, but the
symlink for the kernel i
BIOS Insyd 6.60
EFI version 2.31 by INSYDE
Firmware 6.10
Toshiba Satellite S955, UEFI with Secure boot disabled.
OS 64 bit Ubuntu 14.04.2, running kernel 3.19.8-992-generic
Dual boot with Windows 8.1
After a Windows 8.1 update 7/8/2015 (two important updates, all optional (2)
ignored, the EFI boo
After the Software Updater run of 7/9/2015, a new 3.13.0-57 kernel
(signed and unsigned) was added, and something added the "Boot,
ubuntu, shim" bootloader entry again, at the first position (where it
originally was). I did nothing explicit to add this shim entry, and the
machine is running wi
And yet to me, it looks like things will just work if gcc-12 is simply
installed, not as the default.
Checking some file dates, I see my gcc-12 was brought (by something) in last
April, and has been just sitting around. My /bin/gcc and /bin/cc links are
years old (and link to gcc-11). The
/lib/
Testing was done with the Ubuntu 22.04.1 ISO, booted off disk, no persistence.
The Nvidia GPU was an RTX 3080 (mobile).
The gcc-12 and the generic hwe packages were installed, then the Nvidia
driver 535 selected in the Software & Updates/Additional Drivers tab. Clicked
the apply button, and the nv
A just finished test install of the (same) Ubuntu 22.04.1 Desktop ISO
now resulted in the gcc-12 being automatically installed, and the Nvidia
545 driver modules successfully compiling. After a fresh install, set up
wireless, installed build-essential, and then used software &
Updates/Additional dr
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1990750
Title:
Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15,
now hanging with blinking cursor after update to Kernel
Note that the Nvidia packaging does not play well with phased updates.
For kernel 519.0-35, the Nvidia 525-76.. driver got removed, but then
phasing held back some nvidia 525-85 packages necessary to rebuild the
nvidia modules -- leaving the currently running kernel without an Nvidia
driver. A day
Yesterday, running the 5.19.0-35 kernel and Nvidia 525.76... driver, an
update held back several Nvidia 525 packages (the 525.85.05 versions).
That in itself was not a problem, but the existing Nvidia modules for
that kernel got deleted! Rebooting, the laptop was running off the intel
GPU. The Soft
30 matches
Mail list logo
