Booting directly to crt

Support
#1

Hi All
Two days ago I downloaded a fresh iso cinnamon flavour, I installed it on my old hardware

System:
Kernel: 5.19.1-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1 Desktop: Cinnamon
v: 5.4.10 tk: GTK v: 3.24.34 dm: LightDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop System: Hewlett-Packard product: HP Compaq Elite 8300 MT
CPU: Intel Core i5-3470 bits: 64
Graphics: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Dell U2412M res: 1920x1200 dpi: 94
Network:
Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
Ram :8 GB Ram

During Efi install every thing went normal but when I restart the PC it just loaded the kernel and ask me for user and password on crt screen and that was very fast it did not load any drivers and the list with green Ok on the side
after login I typed startx and cinnamon loads but no network is working I think also no firewall or any kind
I added networkManager manually to the systemctl by typing
sudo systemctl anable NetworkManager.service
and
sudo systemctl start NetworkManager.service
done the same to LighDM
now I can use the PC as normal but I think this is not agood thing to run without any services
all the services are running now are from systemctl status:

dil-hp8300mt
State: running
Units: 411 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Tue 2022-08-23 13:40:11 CAT; 2h 43min ago
systemd: 251.4-1-manjaro
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─NetworkManager.service
│ │ └─663 /usr/bin/NetworkManager --no-daemon
│ ├─accounts-daemon.service
│ │ └─682 /usr/lib/accounts-daemon
│ ├─colord.service
│ │ └─1008 /usr/lib/colord
│ ├─cups.service
│ │ ├─ 5516 /usr/bin/cupsd -l
│ │ └─82738 /usr/lib/cups/notifier/dbus dbus://
│ ├─dbus.service
│ │ └─627 /usr/bin/dbus-daemon --system --address=systemd: --nofork >
│ ├─dhcpcd.service
│ │ ├─631 “dhcpcd: [manager] [ip4] [ip6]”
│ │ ├─632 “dhcpcd: [privileged proxy]”
│ │ ├─633 “dhcpcd: [network proxy]”
│ │ ├─634 “dhcpcd: [control proxy]”
│ │ └─705 “dhcpcd: [BPF ARP] eno1 192.168.1.186”
│ ├─lightdm.service
│ │ ├─674 /usr/bin/lightdm
│ │ └─681 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -n>
│ ├─polkit.service
│ │ └─686 /usr/lib/polkit-1/polkitd --no-debug
│ ├─rtkit-daemon.service
│ │ └─841 /usr/lib/rtkit-daemon
│ ├─systemd-journald.service
│ │ └─234 /usr/lib/systemd/systemd-journald
│ ├─systemd-logind.service
│ │ └─629 /usr/lib/systemd/systemd-logind
│ ├─systemd-networkd.service
│ │ └─252 /usr/lib/systemd/systemd-networkd
│ ├─systemd-resolved.service
│ │ └─624 /usr/lib/systemd/systemd-resolved
│ ├─systemd-udevd.service
│ │ └─udev
│ │ └─246 /usr/lib/systemd/systemd-udevd
│ ├─udisks2.service
│ │ └─1017 /usr/lib/udisks2/udisksd
│ ├─upower.service
│ │ └─1009 /usr/lib/upowerd
│ └─wpa_supplicant.service
│ └─701 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant
└─user.slice
└─user-1000.slice
├─session-2.scope
│ ├─ 863 lightdm --session-child 12 19
│ ├─ 885 cinnamon-session --session cinnamon
│ ├─ 928 csd-keyboard
│ ├─ 929 csd-automount
│ ├─ 931 csd-xsettings
│ ├─ 932 csd-a11y-settings
│ ├─ 933 csd-media-keys
│ ├─ 938 csd-background
│ ├─ 939 csd-housekeeping
│ ├─ 943 csd-screensaver-proxy
│ ├─ 955 csd-color
│ ├─ 957 csd-wacom
│ ├─ 958 csd-clipboard
│ ├─ 964 csd-power
│ ├─ 966 csd-print-notifications
│ ├─ 1002 /usr/lib/cinnamon-settings-daemon/csd-printer
│ ├─ 1098 cinnamon-launcher
│ ├─ 1101 cinnamon --replace
│ ├─ 1145 /usr/lib/caribou
│ ├─ 1150 parcellite
│ ├─ 1158 nemo-desktop
│ ├─ 1159 msm_notifier
│ ├─ 1160 /usr/bin/telegram-desktop -workdir /home/adil/.local/>
│ ├─ 1161 nm-applet
│ ├─ 1164 pamac-tray
│ ├─ 1165 /usr/bin/python /usr/sbin/blueman-applet
│ ├─ 1166 cinnamon-killer-daemon
│ ├─ 1171 /usr/lib/geoclue-2.0/demos/agent
│ ├─ 1173 /usr/lib/polkit-gnome/polkit-gnome-authentication-age>
│ ├─ 1411 conky -c /home/adil/.conky/conkyrc0old
│ ├─ 1736 /usr/bin/python3 /usr/share/system-config-printer/app>
│ ├─172009 /usr/lib/firefox/firefox
│ ├─172176 /usr/lib/firefox/firefox -contentproc -parentBuildID >
│ ├─172223 /usr/lib/firefox/firefox -contentproc -childID 1 -isF>
│ ├─172350 /usr/lib/firefox/firefox -contentproc -childID 2 -isF>
│ ├─172424 /usr/lib/firefox/firefox -contentproc -childID 3 -isF>
│ ├─172432 /usr/lib/firefox/firefox -contentproc -childID 4 -isF>
│ ├─172465 /usr/lib/firefox/firefox -contentproc -childID 5 -isF>
│ ├─173897 /usr/lib/firefox/firefox -contentproc -childID 6 -isF>
│ ├─174130 /usr/lib/firefox/firefox -contentproc -childID 7 -isF>
│ ├─174776 /usr/lib/firefox/firefox -contentproc -childID 8 -isF>
│ ├─174957 /usr/lib/firefox/firefox -contentproc -childID 9 -isF>
│ ├─175339 /usr/lib/firefox/firefox -contentproc -childID 10 -is>
│ ├─176114 /usr/lib/firefox/firefox -contentproc -childID 11 -is>
│ ├─176184 /usr/lib/firefox/firefox -contentproc -parentBuildID >
│ ├─176207 /usr/lib/firefox/firefox -contentproc -parentBuildID >
│ ├─195844 cinnamon-settings
│ ├─213569 mate-terminal
│ ├─213591 bash
│ ├─215007 systemctl status
│ └─215008 less
└─user@1000.service
├─app.slice
│ ├─at-spi-dbus-bus.service
│ │ ├─910 /usr/lib/at-spi-bus-launcher
│ │ ├─916 /usr/bin/dbus-daemon --config-file=/usr/share/defaul>
│ │ └─919 /usr/lib/at-spi2-registryd --use-gnome-session
│ ├─dconf.service
│ │ └─978 /usr/lib/dconf-service
│ ├─gnome-keyring-daemon.service
│ │ └─880 /usr/bin/gnome-keyring-daemon --foreground --compone>
│ ├─obex.service
│ │ └─1275 /usr/lib/bluetooth/obexd
│ ├─xdg-desktop-portal-gnome.service
│ │ └─1382 /usr/lib/xdg-desktop-portal-gnome
│ ├─xdg-desktop-portal-gtk.service
│ │ └─1403 /usr/lib/xdg-desktop-portal-gtk
│ └─xdg-permission-store.service
│ └─1371 /usr/lib/xdg-permission-store
├─init.scope
│ ├─870 /usr/lib/systemd/systemd --user
│ └─871 “(sd-pam)”
└─session.slice
├─dbus.service
│ ├─ 884 /usr/bin/dbus-daemon --session --address=systemd: →
│ ├─1060 /usr/lib/goa-daemon
│ ├─1067 /usr/lib/goa-identity-service
│ └─7637 /usr/bin/python3 /usr/share/system-config-printer/s>
├─gvfs-afc-volume-monitor.service
│ └─1085 /usr/lib/gvfs-afc-volume-monitor
├─gvfs-daemon.service
│ ├─ 896 /usr/lib/gvfsd
│ ├─ 901 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f
│ └─1245 /usr/lib/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/e>
├─gvfs-goa-volume-monitor.service
│ └─1056 /usr/lib/gvfs-goa-volume-monitor
├─gvfs-gphoto2-volume-monitor.service
│ └─1080 /usr/lib/gvfs-gphoto2-volume-monitor
├─gvfs-metadata.service
│ └─1322 /usr/lib/gvfsd-metadata
├─gvfs-mtp-volume-monitor.service
│ └─1069 /usr/lib/gvfs-mtp-volume-monitor
├─gvfs-udisks2-volume-monitor.service
│ └─982 /usr/lib/gvfs-udisks2-volume-monitor
├─pipewire.service
│ └─1332 /usr/bin/pipewire
├─pulseaudio.service
│ ├─ 994 /usr/bin/pulseaudio --daemonize=no --log-target=jou>
│ └─1092 /usr/lib/pulse/gsettings-helper
├─xdg-desktop-portal.service
│ ├─1364 /usr/lib/xdg-desktop-portal
│ └─1398 /usr/lib/pxgsettings org.gnome.system.proxy org.gno>
└─xdg-document-portal.service
├─1368 /usr/lib/xdg-document-portal
└─1377 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_u>
│ ├─ 901 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f
│ └─1245 /usr/lib/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
├─gvfs-goa-volume-monitor.service
│ └─1056 /usr/lib/gvfs-goa-volume-monitor
├─gvfs-gphoto2-volume-monitor.service
│ └─1080 /usr/lib/gvfs-gphoto2-volume-monitor
├─gvfs-metadata.service
│ └─1322 /usr/lib/gvfsd-metadata
├─gvfs-mtp-volume-monitor.service
│ └─1069 /usr/lib/gvfs-mtp-volume-monitor
├─gvfs-udisks2-volume-monitor.service
│ └─982 /usr/lib/gvfs-udisks2-volume-monitor
├─pipewire.service
│ └─1332 /usr/bin/pipewire
├─pulseaudio.service
│ ├─ 994 /usr/bin/pulseaudio --daemonize=no --log-target=journal
│ └─1092 /usr/lib/pulse/gsettings-helper
├─xdg-desktop-portal.service
│ ├─1364 /usr/lib/xdg-desktop-portal
│ └─1398 /usr/lib/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks
└─xdg-document-portal.service
├─1368 /usr/lib/xdg-document-portal
└─1377 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal – /run/user/1000/doc

so is this enough or should I Do something else?

#2

:dizzy_face:

#3

sorry for inconvenient, I am not native English I tried to give as much information about the problem as I can ! if something not clear ask me and I will try to clear it please!

Lightdm not running after fresh Manjaro Cinnamon install
#4

I guess I need to seek help somewhere else !! :dizzy_face: :pensive:

#5

… or you could read a bit, even if it is difficult for you :wink:
Somewhere else they will have the same problem with the lack of information …

This here below could well be your problem - the display manager wasn’t enabled in a recent Cinnamon iso.

Lightdm not running after fresh Manjaro Cinnamon install

If that is the case for you, simply activate it.

#7

All booting processes we are familiar when booting linux are not loaded
I managed to activate LightDm and networkManager, But I think I am at risk of using my PC because no other services are running and of course I do not know which one I should enable, for the reason It is always enabled by default … services, Daemons, and other thing usually comes on booting with the green [OK] on left of it…

#8

… example?! :wink:
What are you missing that should be there?

… with the exception of the display manager in this case
as this was an error when the iso was created.
… if this is/was the problem that you had.

#9

This is just from an old ISO I have I ran it on VM judt to show you what I mean
not exact the things list here but what ever supposed to be loaded when system start !!

Screenshot from 2022-08-26 11-18-24
Screenshot from 2022-08-26 11-18-241137×823 176 KB

#10

I sort of know what you mean, but:
a picture of the boot process of an older iso
does not say anything about what you are missing now
with the actual iso you installed.

An old “boot log” is not an example for what may be missing now.

Typically, the boot process is silent - to see those messages you have to press some key during boot or change the boot loader configuration to make it permanent.

#11

the boot process is verbose and what is loading now is just networkManager and VMware network and usbloader , and LightDm
you may see the orignal post for the other init or systemd processes running !! I listed all usually if I do this systemd status on other PC it is like 500 lines or more now it is only 140
so what is not there I do not know
some process to check integrity of my Hdd usually are there, some basic firewall settings
all of these are not running

#12

firewall might be installed, but it is not enabled by default - because not everyone has use for it and a user should know what services he/she needs to have

What are you missing
of which you positively know it should be there?
… you can’t go by “feelings” :wink:

and:
you only listed running services in your first post
fsck service, for instance, will not be constantly running

#13

Did you try an install with another ISO? As pointed it can happen a bad ISO is released, maybe retry again with a slightly older ISO, or a newer one if there is one.

As there are automated process building the ISO it is possible you just installed a bad ISO. Its OK if you want to troubleshoot your new install but, as it is a new install, I would reinstall because what you describe on first boot is not a sign that “every thing went normal”.

1 Like
#14

You got my point I feeling this is not right and not enough to run only this few things as It was always hundreds of lines, but now it is 6 or 7 lines with OK tag and then the LightDm starts!!!

#15

But you didn’t get my point:
you can’t go by feelings.

What is missing that you would expect to be there?

… a firewall in an example of something that is, and should remain, a users choice
it isn’t active by default - if it is even installed.

see also what @omano just said - further up I linked to another thread discussing this very issue

#16

you are taking my words literally take the it as whole !! like it should not be just 6 or 7 lines loading it should be more!!

#17

perhaps - but still and again:
What is missing that should be there? :wink:

#18

I just read the other thread, I would recommend to install the ISO Oberon suggested.

See if you have issues there, then just update the system, problem(s) solved.

#19

Thank you downloading the ISO now, but is thier any script that I can run to verfy what is missing and what should be running and fix that?

#20

No I don’t think so.

#21

You can (and probably should) verify the integrity of the iso you downloaded.
Then, what you get is a system as it was intended by the person who put together the software that this edition will install by default.
You can always change that later - you don’t have to live with the defaults.