| lotuspsychje | good morning | 02:05 |
|---|---|---|
| lotuspsychje | !next | 09:38 |
| ubottu | Lunar Lobster is the codename for Ubuntu 23.04. For technical support, see #ubuntu-next. For testing and QA feedback and help, see #ubuntu-quality. | 09:38 |
| luna_ | 23.10 development has not started yet for another couple of weeks | 09:40 |
| lotuspsychje | wont be long luna_ | 09:41 |
| lotuspsychje | toolchain follows up pretty quickly these days | 09:42 |
| luna_ | yeah about 1,5-2 weeks | 09:42 |
| ice9 | if I want to use ubuntu-bug to report an issue with bluetooth, which package to provide? | 09:42 |
| lotuspsychje | ice9: bluez maybe | 09:43 |
| lotuspsychje | https://bugs.launchpad.net/ubuntu/+source/bluez/+bugs?orderby=importance&start=0 | 09:44 |
| ice9 | I'm confused, what's the difference between the driver and the linux-firmware? | 15:12 |
| leftyfb | ice9: my understanding is that linux-firmware loads firmware for devices into memory as opposed to firmware that gets flashed to the device. I might be oversimplifying or even wrong | 15:43 |
| Jeremy31 | leftyfb: some firmware gets loaded into hardware | 21:03 |
| Jeremy31 | ice9: What is the issue with Bluetooth? | 21:03 |
| daftykins | oy it's like softmodems all over again | 21:04 |
| daftykins | :) | 21:05 |
| Jeremy31 | Power off the device and the firmware clears | 21:05 |
| daftykins | not really firmware anymore, then | 21:07 |
| Jeremy31 | Not a permanent thing like flashing a BIOS update | 21:10 |
| daftykins | ugh i was improving some silly Dell all-in-one computers at a client today, dust clearing and thermal paste reapplication... ahead of a RAM upgrade... and saw my predecessor had installed the OS as legacy with secure boot off and TPM off | 21:11 |
| daftykins | what amateurs | 21:11 |
| ice9 | Jeremy31, can't enable bluetooth in gnome settings nor in blueman-manager | 21:30 |
| ice9 | blueman-manager 23.30.04 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available. | 21:30 |
| ice9 | blueman-manager 23.30.04 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting | 21:30 |
| ice9 | this happened right after upgrade from 23.04 | 21:30 |
| Jeremy31 | ice9: post URL from terminal for> (lsusb; dmesg | egrep -i 'blue|firm')|nc termbin.com 9999 | 21:30 |
| ice9 | Jeremy31, https://termbin.com/jpyo | 21:31 |
| Jeremy31 | ice9: What kernel? | 21:33 |
| ice9 | Jeremy31, 6.2.0 | 21:33 |
| * daftykins walks outside the channel and checks the name above the door | 21:35 | |
| Jeremy31 | ice9: File a bug against package linux as it is a kernel issue | 21:36 |
| ice9 | Jeremy31, how are sure it's the kernel not the driver or the firmware? | 21:36 |
| Jeremy31 | ice9: Because the kernel is responsible for loading correct firmware, that chipset might need a flag in btusb because of this error "Failed to read MSFT supported features (-110)" | 21:38 |
| Jeremy31 | ice9: you could try copying https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel/ibt-19-0-4.sfi into /lib/firmware/intel/ and do a reboot as that is the newest version | 21:50 |
| ice9 | Jeremy31, I already installed this https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git but didn't help | 21:52 |
| ice9 | I mean I installed all firmware there | 21:52 |
| Jeremy31 | So you have the latest/greatest firmware that Intel has made available | 21:53 |
| daftykins | maybe TJ's old ACPI OSI trickery could be worth a go? | 21:54 |
| daftykins | for fun if nothing else | 21:54 |
| ice9 | Jeremy31, maybe I install the old firmware that was on 22.10? | 21:55 |
| daftykins | although perhaps support should be pursued in support channels y'know, just saying... | 21:55 |
| Jeremy31 | ice9: Did you try it on 22.04? | 21:55 |
| ice9 | Jeremy31, 22.04 and 22.10 was working fine | 21:55 |
| Jeremy31 | So it must be the kernel | 21:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!