Note: the error was *not* the same when booting from the 6.8.9 kernel, replace all of the 6.8.9 from the previous message with 6.8.10. So, when in 6.8.10, it complains about the 6.8.9, when on 6.8.9, it complains about .10 I'm a bit confused. On Wed, Jul 17, 2024 at 10:19 PM murph nj <murphnj+fedora@xxxxxxxxx> wrote: > > Progress: > > I've added mirrors.fedoraproject.org and mirror.math.princeton.edu to > my /etc/hosts, and can do some dnf work: > > When I do a dnf distro-sync I get an error: > > package kernel-modules-extra-6.8.9-300.fc.x86_64 from @System requires > kernel-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the providers > can be installed > package kernel-6.8.9-300.fc.x86_64 from @System requires > kernel-core-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the > providers can be installed > package kernel-6.8.9-300.fc.x86_64 from @System requires > kernel-modules-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the > providers can be installed > all with --conflicting requests > > (These are are retyped from the other machine, so don't panic if I > made a typo somewhere) > > The system is booted from a 6.8.10 kernel, but got the same error when > I tried to boot from the 6.8.9 kernel as well. > > Suggestions? > > On Wed, Jul 17, 2024 at 9:40 PM murph nj <murphnj+fedora@xxxxxxxxx> wrote: > > > > When I try to start nmcli, I get the following error: "Error: Could > > not create NMClient object: Could not Connect: Connection refused" > > > > In journalctl -xe: > > nothing but some pam_systemd failed to connect to system bus: > > Connection refused > > Didn't see anything related to networking > > journalctl -u network.service shows: nothing from today's boot, > > strangely. It shows information from booting yesterday, i see lots of > > failures for wireless networks on every SSID from the past. > > > > I did manage to get the network up with ifup enp4s0f2, but I do not > > have name resolution, resolvectl status gives me: "sd_bus_open_system: > > Connection refused" > > > > Still working on it, hints woudl be welcome. If I can get name > > resoluction working, I might be able to try to run updates again. > > > > > > On Tue, Jul 16, 2024 at 6:51 PM Samuel Sieb <samuel@xxxxxxxx> wrote: > > > > > > On 7/16/24 3:27 PM, murph nj wrote: > > > > I had not used my Fedora partition on my old laptop for a few weeks. > > > > Came back to a lot of updates that needed running. In the midst of > > > > updating, an overlooked intemittent (thermal) hardware problem cropped > > > > up, locking the machine. I had to hard boot it. > > > > > > > > Now, it will not boot correctly. I can get past the prompt for the > > > > encrypted disks, but as the boot proceeds, there are a ton of errors, > > > > aming the services that fail to start, we have: > > > > power-profiles-daemon, dbus-broker, thermald, abrtd, and various dependencies. > > > > > > > > The last two failed lines are: rtsx_pci VPD access failed, It is > > > > likely a firmware bug on the device. and r8169 0000:04:00.0 Invalid > > > > VPD tag .... assume missing EEPROM. > > > > > > > > The hardware (other than intermittent overheating) is OK. I booted > > > > from a Debian ssd, and it came up just fine, network and all. (That > > > > also gives me a reasonable way to get data on/off the Fedora disks.) > > > > > > > > I can boot to the command-line by specifying "3" from the grub menu, > > > > and I am able to log in, but my attempts to re-run the updates are > > > > stymied by the network not starting. > > > > > > > > But I can get in, and I'll be digging into the logs. Any suggestions > > > > as to where to start? > > > > > > Check the journal to find out why the network isn't starting. > > > > > > -- > > > _______________________________________________ > > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > > > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
