Bug 2354594 - i upgraded from fedora 41 silverblue to fedora 42 beta but i find some error when bootup no brightness slider and some other error on boot up
Summary: i upgraded from fedora 41 silverblue to fedora 42 beta but i find some error ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-24 17:47 UTC by fedord
Modified: 2025-03-24 17:47 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description fedord 2025-03-24 17:47:47 UTC
1. Please describe the problem:have upgraded to 42 beta but some bootup systemd issues i found when it was booting
with 41 all was green
And second issue is there is no brightness slider which was present in quick toggle area of 42 version fedora silverblue 

2. What is the Version-Release number of the kernel: 6.14-rc7


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes all was green and works out of the box with fedora 41


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below: turn the system on and look for systemd logs


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``: yes present


6. Are you running any modules that not shipped with directly Fedora's kernel?:no nothing extra.


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.


Some of my logs which are important in my opinion.
```
$ journalctl -b -p 3
Mar 25 02:32:54 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP18.SATA], AE_NOT_FOUND (20240827/dswload2-162)
Mar 25 02:32:54 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Mar 25 02:32:54 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0], AE_NOT_FOUND (20240827/dswload2-162)
Mar 25 02:32:54 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Mar 24 21:03:00 fedora systemd-remount-fs[1116]: /usr/bin/mount for / exited with exit status 32.
Mar 24 21:03:00 fedora systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
Mar 24 21:03:01 fedora kernel: i2c i2c-8: SMBus Timeout!
Mar 24 21:03:01 fedora kernel: i2c i2c-8: Failed reset at end of transaction (01)
Mar 24 21:03:01 fedora kernel: i2c i2c-8: Failed! (01)
Mar 24 21:03:01 fedora systemd-remount-fs[1272]: /usr/bin/mount for / exited with exit status 32.
Mar 24 21:03:01 fedora systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
Mar 24 21:03:01 fedora systemd-tmpfiles[1327]: "/home" already exists and is not a directory.
Mar 24 21:03:01 fedora systemd-tmpfiles[1327]: "/srv" already exists and is not a directory.
Mar 24 21:03:01 fedora systemd-tmpfiles[1327]: "/root" already exists and is not a directory.
Mar 24 21:03:03 fedora systemd-homed[1428]: Failed to open /var/cache/systemd/home/: Permission denied
Mar 24 21:03:03 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:04 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:04 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:05 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:05 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:05 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:16 fedora gdm-password][2448]: gkr-pam: unable to locate daemon control file
Mar 24 21:03:17 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:17 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:17 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:18 fedora systemd[2492]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2913.scope - Application launched by gnome-session-binary.
Mar 24 21:03:18 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:18 fedora systemd-logind[1430]: Failed to open '/boot//loader/entries': Remote address changed
Mar 24 21:03:18 fedora polkitd[1424]: Error converting subject to JS object: Process 1838 terminated
```
```
$ systemctl --failed
  UNIT                       LOAD   ACTIVE SUB    DESCRIPTION                         
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.
```


Reproducible: Always


Note You need to log in before you can comment on or make changes to this bug.