Upgrade to 7.1.0-1-resolute from 7.0.12-1-resolute introduced some errors on my setup

[marcelovbcfilho]

I recently decided to update my system as Discovery keeps saying that there are updates available, after that it asked me to restart my computer(as a new kernel version was installed) and from that point on I started having a few issues, upower service randomly stops working and I need to restart it manually which solves the problem for a while and them the system just crashes, also 2 services refuse to work after the upgrade for some unknown reason.
I'm going to attach the logs I know where to get and some system info as well as the packages Discovery upgraded before the issues started to appear.

Device Specs

Operating System: Kubuntu 26.04 LTS
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 7.1.0-1-t2-resolute (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz
Memory: 15,5 GiB of usable RAM
Graphics Processor 1: Intel® UHD Graphics 630
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: Apple Inc.
Product Name: MacBookPro16,1
System Version: 1.0

What was upgraded

➜  ~ grep " upgrade " /var/log/dpkg.log
2026-06-16 22:09:23 upgrade ca-certificates:all 20260223 20260601~26.04.1
2026-06-16 22:09:27 upgrade cups-daemon:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:29 upgrade cups:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:31 upgrade libcupsimage2t64:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:32 upgrade cups-ipp-utils:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:34 upgrade cups-core-drivers:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:35 upgrade cups-bsd:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:36 upgrade cups-client:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:37 upgrade libcups2t64:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:38 upgrade libcups2t64:i386 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:39 upgrade cups-common:all 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:39 upgrade cups-ppdc:amd64 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:41 upgrade cups-server-common:all 2.4.16-1ubuntu1.2 2.4.16-1ubuntu1.3
2026-06-16 22:09:51 upgrade libfreerdp-client3-3:amd64 3.24.2+dfsg-1ubuntu1 3.24.2+dfsg-1ubuntu1.1
2026-06-16 22:09:52 upgrade libfreerdp3-3:amd64 3.24.2+dfsg-1ubuntu1 3.24.2+dfsg-1ubuntu1.1
2026-06-16 22:09:52 upgrade libwinpr3-3:amd64 3.24.2+dfsg-1ubuntu1 3.24.2+dfsg-1ubuntu1.1
2026-06-16 22:09:53 upgrade librabbitmq4:amd64 0.15.0-1build2 0.15.0-1ubuntu0.26.04.1
2026-06-16 22:10:24 upgrade linux-t2:amd64 7.0.12-1-resolute 7.1.0-1-resolute

Failed services and logs

➜  ~ systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION                                    
● battery-charge-limit.service loaded failed failed Set Apple SMC battery charge limit
● t2fanrd.service              loaded failed failed T2FanRD daemon to manage fan curves for t2 macs

➜  ~ journalctl -u t2fanrd.service -f        
Jun 16 23:05:35 kubuntu-i9 systemd[1]: t2fanrd.service: Scheduled restart job, restart counter is at 4.
Jun 16 23:05:35 kubuntu-i9 systemd[1]: Starting t2fanrd.service - T2FanRD daemon to manage fan curves for t2 macs...
Jun 16 23:05:35 kubuntu-i9 systemd[1]: Started t2fanrd.service - T2FanRD daemon to manage fan curves for t2 macs.
Jun 16 23:05:35 kubuntu-i9 t2fanrd[3563]: Error: Fan not found
Jun 16 23:05:35 kubuntu-i9 systemd[1]: t2fanrd.service: Main process exited, code=exited, status=1/FAILURE
Jun 16 23:05:35 kubuntu-i9 systemd[1]: t2fanrd.service: Failed with result 'exit-code'.
Jun 16 23:05:36 kubuntu-i9 systemd[1]: t2fanrd.service: Scheduled restart job, restart counter is at 5.
Jun 16 23:05:36 kubuntu-i9 systemd[1]: t2fanrd.service: Start request repeated too quickly.
Jun 16 23:05:36 kubuntu-i9 systemd[1]: t2fanrd.service: Failed with result 'exit-code'.
Jun 16 23:05:36 kubuntu-i9 systemd[1]: Failed to start t2fanrd.service - T2FanRD daemon to manage fan curves for t2 macs.

➜  ~ journalctl -u battery-charge-limit.service -f
Jun 16 23:03:06 kubuntu-i9 systemd[1]: Starting battery-charge-limit.service - Set Apple SMC battery charge limit...
Jun 16 23:03:06 kubuntu-i9 sh[1963]: /bin/sh: 1: cannot create /sys/bus/acpi/drivers/applesmc/APP0001:00/battery_charge_limit: Directory nonexistent
Jun 16 23:03:06 kubuntu-i9 systemd[1]: battery-charge-limit.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 16 23:03:06 kubuntu-i9 systemd[1]: battery-charge-limit.service: Failed with result 'exit-code'.
Jun 16 23:03:06 kubuntu-i9 systemd[1]: Failed to start battery-charge-limit.service - Set Apple SMC battery charge limit.

➜  ~ journalctl -u upower.service      
Jun 16 22:15:19 kubuntu-i9 systemd[1]: Starting upower.service - Daemon for power management...
Jun 16 22:15:20 kubuntu-i9 systemd[1]: Started upower.service - Daemon for power management.
Jun 16 22:30:58 kubuntu-i9 systemd[1]: Stopping upower.service - Daemon for power management...
Jun 16 22:32:28 kubuntu-i9 systemd[1]: upower.service: State 'stop-sigterm' timed out. Killing.
Jun 16 22:32:28 kubuntu-i9 systemd[1]: upower.service: Killing process 1742 (upowerd) with signal SIGKILL.
Jun 16 22:33:37 kubuntu-i9 systemd[1]: upower.service: Main process exited, code=killed, status=9/KILL
Jun 16 22:33:37 kubuntu-i9 systemd[1]: upower.service: Failed with result 'timeout'.
Jun 16 22:33:37 kubuntu-i9 systemd[1]: Stopped upower.service - Daemon for power management.

➜  ~ journalctl -b -p er
Jun 16 23:02:55 kubuntu-i9 kernel: ERROR: Unable to locate IOAPIC for GSI 34
Jun 16 23:02:55 kubuntu-i9 kernel: integrity: Reading UEFI Secure Boot Certs is not supported on T2 Macs.
Jun 16 23:02:56 kubuntu-i9 kernel: intel-lpss INT34BA:00: error -EINVAL: IRQ index 0 not found
Jun 16 23:02:56 kubuntu-i9 kernel: intel-lpss INT34BA:00: probe with driver intel-lpss failed with error -22
Jun 16 23:02:56 kubuntu-i9 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4
Jun 16 23:02:56 kubuntu-i9 kernel: spi-nor spi0.0: unrecognized JEDEC id bytes: f4 0c 58 12 03 00
Jun 16 23:02:56 kubuntu-i9 kernel: hid_sensor_rotation HID-SENSOR-20008a.1.auto: failed to setup common attributes
Jun 16 23:02:56 kubuntu-i9 kernel: hid_sensor_rotation HID-SENSOR-20008a.1.auto: probe with driver hid_sensor_rotation failed with error -22
Jun 16 23:02:56 kubuntu-i9 kernel: Bluetooth: hci0: BCM: failed to write update baudrate (-16)
Jun 16 23:02:56 kubuntu-i9 kernel: Bluetooth: hci0: Failed to set baudrate
Jun 16 23:02:56 kubuntu-i9 kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried:
Jun 16 23:02:56 kubuntu-i9 kernel: Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
Jun 16 23:03:00 kubuntu-i9 kernel: brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
Jun 16 23:03:00 kubuntu-i9 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/4 wl0: Jul 26 2024 22:36:01 version 9.30.514.0.32.5.94 FWID 01-68d7ff80
Jun 16 23:03:00 kubuntu-i9 kernel: ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
Jun 16 23:03:00 kubuntu-i9 wpa_supplicant[1298]: Failed to create interface p2p-dev-wlp5s0: -52 (Invalid exchange)
Jun 16 23:03:00 kubuntu-i9 wpa_supplicant[1298]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp5s0
Jun 16 23:03:00 kubuntu-i9 kernel: ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
Jun 16 23:03:00 kubuntu-i9 kernel: ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp5s0 type 10 failed: err=-52
Jun 16 23:03:01 kubuntu-i9 systemd[1]: Failed to start t2fanrd.service - T2FanRD daemon to manage fan curves for t2 macs.
Jun 16 23:03:03 kubuntu-i9 kernel: [drm:dm_helpers_read_local_edid [amdgpu]] *ERROR* EDID err: 2, on connector: eDP-2
Jun 16 23:03:03 kubuntu-i9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* No EDID read.
Jun 16 23:03:04 kubuntu-i9 (udev-worker)[1753]: card0: /etc/udev/rules.d/30-amdgpu-pm.rules:1 ATTR{device/power_dpm_force_performance_level}="low": Could not chase sysfs attribute "/sys/d>
Jun 16 23:03:04 kubuntu-i9 (udev-worker)[1753]: card0: /etc/udev/rules.d/30-amdgpu-pm.rules:1 ATTR{device/power_dpm_force_performance_level}="low": Could not chase sysfs attribute "/sys/d>
Jun 16 23:03:06 kubuntu-i9 systemd[1]: Failed to start battery-charge-limit.service - Set Apple SMC battery charge limit.
Jun 16 23:03:25 kubuntu-i9 org_kde_powerdevil[2338]: [  2338] Error(s) opening ddc devices
Jun 16 23:03:25 kubuntu-i9 org_kde_powerdevil[2338]: [  2338] Error EACCES(-13): Permission denied opening /dev/i2c-1
Jun 16 23:03:25 kubuntu-i9 org_kde_powerdevil[2338]: [  2338] Error EACCES(-13): Permission denied opening /dev/i2c-2
Jun 16 23:03:25 kubuntu-i9 org_kde_powerdevil[2338]: [  2338] Error EACCES(-13): Permission denied opening /dev/i2c-3
Jun 16 23:03:25 kubuntu-i9 org_kde_powerdevil[2338]: [  2338] Error EACCES(-13): Permission denied opening /dev/i2c-4

I noticed that this 7.1 versions upgraded the AppleSMC driver not sure if it is related, but on the logs I see a few issues related to AppleSMC.

Reverting back to the older kernel can solve this or the upgrade is not related to these issues?

[marcelovbcfilho]

Using the older kernel 7.0.12-1-resolute resulted in both failing services working again and just for reference the battery-charge-limit service was created by me using what was said in this issue as reference.

[FrostBird347]

I am also experiencing issues with the battery and sensors in 7.1.0-1-resolute.

• plasma-systemmonitor can't find any temperature sensors for the logic board, nor can it find the fan's RPM
• With acpi_osi=!Darwin acpi_osi=Linux in the grubfile the battery doesn't get detected by KDE at all, and when they are removed it lists the correct charge percent but it also lists the health at 0%
• I have also been randomly getting notifications claiming my battery is at 0% and warning of imminent shutdown, and charging also intermittently disconnects for a minute
• Finally, I am also using a startup script to modify the charge limit and it has also stopped working in the latest version because applesmc was replaced with macsmc (and I have no idea how to set the limit in the new system)

[FrostBird347]

And here's a comparison of the sensors before and after upgrading:

Before	After

[AdityaGarg8]

The SMC driver has been changed in 7.1. All ways to limit battery, modify fan speeds is now changed.

[AdityaGarg8]

@marcelovbcfilho could you share ls /sys/class/power_supply

[AdityaGarg8]

Also, the new kernel seems to be faulty. I've put the fixed kernel on compiling. After around 3 hours of this message, it should be available and can be installed by a simple apt upgrade.

[bitboss-ca]

Same or very similar issue on noble for me this morning. A stanrdard apt update that included linux-image-7.1.0-1-t2-noble and linux-headers-7.1.0-1-t2-noble prevented my MacBookAir9,1 from booting after the update. I was able to work around by pressiing esc at boot, choosing advanced options and the previous kernel.

At the time when this screenshot was taken, the caps lock key was still responding, i.e. it would still toggle on and off, but eventually, the screen just went black and the caps lock became unresponsive.

[marcelovbcfilho]

@marcelovbcfilho could you share ls /sys/class/power_supply

Hey sorry for the delay here is what you asked for:

This is with the older kernel 7.0.12-1-t2-resolute

➜  ~ ls /sys/class/power_supply
ADP1  BAT0
➜  ~ ls /sys/class/power_supply/ADP1
device  extensions  hwmon0  online  power  subsystem  type  uevent  wakeup44
➜  ~ ls /sys/class/power_supply/BAT0
alarm     charge_full         charge_now   current_now  device      hwmon4        model_name  present  subsystem   temp  uevent              voltage_now
capacity  charge_full_design  current_avg  cycle_count  extensions  manufacturer  power       status   technology  type  voltage_min_design  wakeup67

This is with the new kernel 7.1.0-2-t2-resolute

➜  ~ ls /sys/class/power_supply/         
macsmc-ac  macsmc-battery
➜  ~ ls /sys/class/power_supply/macsmc-ac 
current_now  device  extensions  hwmon4  online  power  power_now  subsystem  type  uevent  voltage_now  wakeup63
➜  ~ ls /sys/class/power_supply/macsmc-battery 
capacity                      charge_full                  constant_charge_voltage  device      hwmon3   scope      temp               type                voltage_now
capacity_level                charge_now                   current_now              extensions  power    status     time_to_empty_now  uevent              wakeup62
charge_control_end_threshold  constant_charge_current_max  cycle_count              health      present  subsystem  time_to_full_now   voltage_min_design

Out of my curiosity should this kind of new/experimental drivers be pushed to the LTS(26.04) version of Ubuntu? I noticed that the wiki still needs to be update on how to do things with this new driver(at least the fan part that I was using).

[marcelovbcfilho]

Also noticed that it appears to have crashed again even with the new hotfix version it is not detecting when I plug my charger and kde is showing as connected and charging even without the cable plugged in, BUT this time even after restarting upower service did not make it start working again.

On another note I noticed that my monitoring plugin due to not existing a BAT0 anymore just stopped working not sure this is solvable on this end though...
I'm using the Kvitals and even after setting the new macsmc-battery as the battery device did not solve the issue.

[AdityaGarg8]

@marcelovbcfilho could you share ls /sys/class/power_supply

Hey sorry for the delay here is what you asked for:

This is with the older kernel 7.0.12-1-t2-resolute

➜ ~ ls /sys/class/power_supply
ADP1 BAT0
➜ ~ ls /sys/class/power_supply/ADP1
device extensions hwmon0 online power subsystem type uevent wakeup44
➜ ~ ls /sys/class/power_supply/BAT0
alarm charge_full charge_now current_now device hwmon4 model_name present subsystem temp uevent voltage_now
capacity charge_full_design current_avg cycle_count extensions manufacturer power status technology type voltage_min_design wakeup67
This is with the new kernel 7.1.0-2-t2-resolute

➜ ~ ls /sys/class/power_supply/
macsmc-ac macsmc-battery
➜ ~ ls /sys/class/power_supply/macsmc-ac
current_now device extensions hwmon4 online power power_now subsystem type uevent voltage_now wakeup63
➜ ~ ls /sys/class/power_supply/macsmc-battery
capacity charge_full constant_charge_voltage device hwmon3 scope temp type voltage_now
capacity_level charge_now current_now extensions power status time_to_empty_now uevent wakeup62
charge_control_end_threshold constant_charge_current_max cycle_count health present subsystem time_to_full_now voltage_min_design
Out of my curiosity should this kind of new/experimental drivers be pushed to the LTS(26.04) version of Ubuntu? I noticed that the wiki still needs to be update on how to do things with this new driver(at least the fan part that I was using).

The driver was tested quite significantly. There has to be a line where we have to release software to the public. It was my mistake in this case that I didn't compile the kernel properly.

[AdityaGarg8]

Same or very similar issue on noble for me this morning. A stanrdard apt update that included linux-image-7.1.0-1-t2-noble and linux-headers-7.1.0-1-t2-noble prevented my MacBookAir9,1 from booting after the update. I was able to work around by pressiing esc at boot, choosing advanced options and the previous kernel.

At the time when this screenshot was taken, the caps lock key was still responding, i.e. it would still toggle on and off, but eventually, the screen just went black and the caps lock became unresponsive.

Upgrade to 7.1.0-2. I've fixed the kernel there.

[AdityaGarg8]

@marcelovbcfilho update your battery service you use to write the limit percentage to /sys/class/power_supply/macsmc-battery/charge_control_end_threshold

[AdityaGarg8]

Also noticed that it appears to have crashed again even with the new hotfix version it is not detecting when I plug my charger and kde is showing as connected and charging even without the cable plugged in, BUT this time even after restarting upower service did not make it start working again.

Basically you mean it shows not charging when plugged in, and charging when not plugged in?!

On another note I noticed that my monitoring plugin due to not existing a BAT0 anymore just stopped working not sure this is solvable on this end though... I'm using the Kvitals and even after setting the new macsmc-battery as the battery device did not solve the issue.

BAT0 has been removed. You need to use macsmc-battery.

[marcelovbcfilho]

Also noticed that it appears to have crashed again even with the new hotfix version it is not detecting when I plug my charger and kde is showing as connected and charging even without the cable plugged in, BUT this time even after restarting upower service did not make it start working again.

Basically you mean it shows not charging when plugged in, and charging when not plugged in?!

On another note I noticed that my monitoring plugin due to not existing a BAT0 anymore just stopped working not sure this is solvable on this end though... I'm using the Kvitals and even after setting the new macsmc-battery as the battery device did not solve the issue.

BAT0 has been removed. You need to use macsmc-battery.

The battery when using the 7.1.0-2-t2-resolute show as ALWAYS charging no matter if the charger is plugged or not.

In this video you can see how it behaves with 7.1.0-2-t2-resolute(I plug and unplug the charger and there is no icon change and sound)

temp2.mp4

And in this video you can see how it WAS working with 7.0.12-1-t2-resolute(I plug the charger the icon changes and there is a sound indicating that the charger was plugged and unplugged)

temp1.mp4