[SOLVED] dbus service failed, fresh base install. NetworkManager also

Exfoliate2600 · 2023-12-29 16:26:56

Scimmia wrote:

The GRUB entry isn't loading it anyway, so it has no effect no matter what.

I think I see what you mean, that and-ucode.img is not referenced in the entry in grub.cfg

I thought I was decent with linux but I am seeing places I have never been before now.

seth · 2023-12-29 17:33:35

I had hoped that the initrams might be damaged (full boo partition) or missing binaries, but it doesn't look this way.
Not sure at hand what's going wrong there, but the journal looks odd and you don't get a system bus from systemd and that's not b/c of an issue w/ the dbus binary itself.

[pondering…]

Exfoliate2600 · 2023-12-29 18:23:27

Could you point out what looks odd in the journal?

So I can read about the associated subjects?

I am far from an expert but can learn.

seth · 2023-12-29 22:00:27

It's less odd looking lines but the absence of things you'd expect to be there.
There was https://bbs.archlinux.org/viewtopic.php?id=290949 - maybe post your /etc/mkintcpio.conf

Last resort: downgrade systemd and rebuild the initramfs.

Exfoliate2600 · 2023-12-29 23:46:33

OK possible systemd bug, I am a brand new Arch user so I assumed it was a lack of knowledge on my end and I did not want to call it a bug, It is still very possible I am doing something wrong.

Other angle I had was drive corruption, this NVME is only a few weeks old and I had not really used this partition of it yet.
sudo fsck /dev/nvme0n1p4
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Arch: clean, 52631/52453376 files, 4042090/209798400 blocks

AHHH, this is where the mysterious "HOOKS" I keep reading about in Arch are! I do not have this file in LMDE. at least not in /etc/

/etc/mkintcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"

Last edited by Exfoliate2600 (2023-12-29 23:47:20)

Exfoliate2600 · 2023-12-30 00:40:57

OK reading https://wiki.archlinux.org/title/Downgrading_packages I looked in /var/cache/pacman/pkg, I have:

systemd-255.2-1-x86.pkg.tar.zst
systemd-libs-255.2-1-x86.pkg.tar.zst
systemd-sysvcompact-255.2-1-x86.pkg.tar.zst

And matching .sig files for all 3 but not an earlier version to fall back on. makes sense, its a fresh install with no history.

I need an old systemd and the old versions of its dependencies correct?

I could delete everythign in this partition and install the Nov 1st version. wouldn't that be the cleanest way to go about that? there is nothing on this install I need yet, haven't even got to the DE yet.

http://mirrors.mit.edu/archlinux/iso/2023.11.01/

http://mirrors.mit.edu/archlinux/iso/20 … x86_64.txt

systemd 254.5-1
systemd-libs 254.5-1
systemd-resolvconf 254.5-1
systemd-sysvcompat 254.5-1

If I can get to a running system I can back it up (in Mint I would use timeshift here, surely Arch has something similar?) and then update and see where the chips fall but at least I will have running system and backups of it to work from?

Last edited by Exfoliate2600 (2023-12-30 00:48:31)

damjan · 2023-12-30 02:27:22

make sure you're not booting the Arch system with the Mint kernel

Exfoliate2600 · 2023-12-30 02:29:13

How would I verifi that?

Edit
uname -srm

LMDE
LINUX 6.1.0-16-amd-64 x86_64

Arch
Linux 6.6.8-arch1-1 x86_64

Last edited by Exfoliate2600 (2023-12-30 02:38:08)

Exfoliate2600 · 2023-12-30 03:35:27

Nov version still pulled down the 255 version of systemd from the mirror, no choice but to continue instalation we will see what it does.....

Scimmia · 2023-12-30 03:37:55

The ISO you use doesn't matter, it always pulls the latest versions of all packages.

Exfoliate2600 · 2023-12-30 04:08:17

I do not know what was wrong all the other times I tried installing, nor do I know why its working now but I sure am glad to have a lot less red on my screen .

2 differences
I used the nov 1st .iso
I deleted the Arch / partition (nvme0n1p4) in LMDE then re-created and formatted it in the Arch installer.

Otherwise letter for letter same commands at install.

Last edited by Exfoliate2600 (2023-12-30 04:15:03)

Exfoliate2600 · 2023-12-30 04:51:19

Something is different about the permissions on this new now working partition,

Before from LMDE I would have to mount the partition in disks (sudo PW) then it would show up in Nemo but I could not click on it there I had to go to /media/user/ and then right click on the mount point and then open as root. (sudo PW again)

Now this new partition shows up on the left bar immediately on boot, not mounted but present, click on it sudo PW, and I can browse all but the /root & /lost+found without opening them as root.

I don't know what this means but something is defiantly different here than before, the old partition briefly held a Ubuntu install, I spent 5 min in it and i just couldn't, looked too much like my old Job, I deleted all the files but where permissions left behind for "/" ? some other sticky Ubuntu residue?

Exfoliate2600 · 2023-12-30 08:03:03

Got Cinnamon up and running, Arch is fast! barren but fast I am trying to stick with the idea of minimal installation.

Thank you all for your help!

Arch Linux

#26 2023-12-29 16:26:56

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#27 2023-12-29 17:33:35

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#28 2023-12-29 18:23:27

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#29 2023-12-29 22:00:27

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#30 2023-12-29 23:46:33

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#31 2023-12-30 00:40:57

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#32 2023-12-30 02:27:22

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#33 2023-12-30 02:29:13

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#34 2023-12-30 03:35:27

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#35 2023-12-30 03:37:55

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#36 2023-12-30 04:08:17

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#37 2023-12-30 04:51:19

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

#38 2023-12-30 08:03:03

Re: [SOLVED] dbus service failed, fresh base install. NetworkManager also

Board footer