i think not. i did it for the second time: all this commands in chroot, will restart and hope for it to work.
edit: yes, it didn’t work this time
it should worked …
so chroot again and post output from:
journalctl --boot=-1 --priority=4 --no-pager
pacman -Qs mesa
Aug 22 10:49:56 flordeibez kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Aug 22 10:49:56 flordeibez kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Aug 22 10:49:56 flordeibez kernel: TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.
Aug 22 10:49:56 flordeibez kernel: #2 #3
Aug 22 10:49:56 flordeibez kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 22 10:49:56 flordeibez kernel: ACPI Error: Needed type [Reference], found [Integer] 00000000f701f3c9 (20210730/exresop-66)
Aug 22 10:49:56 flordeibez kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20210730/dswexec-431)
Aug 22 10:49:56 flordeibez kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20210730/psparse-529)
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:56 flordeibez kernel: pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Aug 22 10:49:57 flordeibez kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Aug 22 10:49:57 flordeibez kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Aug 22 10:49:58 flordeibez kernel: kauditd_printk_skb: 49 callbacks suppressed
Aug 22 10:49:58 flordeibez kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Aug 22 10:49:58 flordeibez kernel: at24 0-0050: supply vcc not found, using dummy regulator
Aug 22 10:50:01 flordeibez kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Aug 22 10:50:01 flordeibez systemd[731]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:02 flordeibez kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Aug 22 10:50:03 flordeibez kernel: kauditd_printk_skb: 186 callbacks suppressed
Aug 22 10:50:05 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:07 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:08 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:08 flordeibez kernel: kauditd_printk_skb: 19 callbacks suppressed
Aug 22 10:50:10 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:12 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:14 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:14 flordeibez kernel: kauditd_printk_skb: 9 callbacks suppressed
Aug 22 10:50:15 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:17 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:19 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:19 flordeibez kernel: kauditd_printk_skb: 8 callbacks suppressed
Aug 22 10:50:21 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:21 flordeibez systemd[1]: lightdm.service: Start request repeated too quickly.
Aug 22 10:50:21 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 22 10:50:21 flordeibez systemd[1]: Failed to start Light Display Manager.
local/glu 9.0.2-3
Mesa OpenGL utility library
local/lib32-glu 9.0.2-3
Mesa OpenGL utility library (32 bits)
local/lib32-libva-mesa-driver 22.1.4-1
VA-API implementation for gallium (32-bit)
local/lib32-mesa 22.1.4-1
An open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-demos 8.5.0-1
Mesa demos (32-bit)
local/lib32-mesa-vdpau 22.1.4-1
Mesa VDPAU drivers (32-bit)
local/lib32-vulkan-intel 22.1.6-1
Intel's Vulkan mesa driver (32-bit)
local/lib32-vulkan-radeon 22.1.6-1
Radeon's Vulkan mesa driver (32-bit)
local/libva-mesa-driver 22.1.4-1
VA-API implementation for gallium
local/mesa 22.1.4-1
An open-source implementation of the OpenGL specification
local/mesa-demos 8.5.0-2
Mesa demos
local/mesa-vdpau 22.1.4-1
Mesa VDPAU drivers
local/vulkan-intel 22.1.6-1
Intel's Vulkan mesa driver
local/vulkan-radeon 22.1.6-1
Radeon's Vulkan mesa driver
edit: sorry i’m not specifing which ones outputted above
but i did both commands. do you need them to be separated?
Ok the display-manager failed here…
Only startx will not work…
startx /usr/bin/xfce4-session
or
startx xfce
The reason: In your ~/.xinitrc file there no predefined session by default.
Normally you can just restart the display-manager:
sudo systemctl restart display-manager.service
sudo systemctl status display-manager.service
Your xorg log looks normal. It just don’t start a session, since none was chosen:
try megavolt commands from the TTY
It failed to restart display-manager.
startx /usr/bin/xfce4-session
This one worked!!
Good, now you know how to get the GUI at least. But the problem with lightdm is not solved…
What says:
journalctl --boot 0 --unit display-manager --no-pager
Or is that enough for you? So no graphical login anymore?
Since it seems it solved your basic needs, I tagged the origin as solution.
it says
-- No entries --
Then please show more information:
sudo systemctl status display-manager -l --no-pager
sudo systemctl status lightdm -l --no-pager
× lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2022-08-22 11:22:52 -03; 39min ago
Duration: 1.540s
Docs: man:lightdm(1)
Process: 1420 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 1420 (code=exited, status=1/FAILURE)
CPU: 411ms
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
ago 22 11:22:52 flordeibez systemd[1]: Stopped Light Display Manager.
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Start request repeated too quickly.
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
ago 22 11:22:52 flordeibez systemd[1]: Failed to start Light Display Manager.
× lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2022-08-22 11:22:52 -03; 39min ago
Duration: 1.540s
Docs: man:lightdm(1)
Process: 1420 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 1420 (code=exited, status=1/FAILURE)
CPU: 411ms
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
ago 22 11:22:52 flordeibez systemd[1]: Stopped Light Display Manager.
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Start request repeated too quickly.
ago 22 11:22:52 flordeibez systemd[1]: lightdm.service: Failed with result 'exit-code'.
ago 22 11:22:52 flordeibez systemd[1]: Failed to start Light Display Manager.
[edicao@flordeibez ~]$
Whats in your config?
cat /etc/lightdm/lightdm.conf
Are there any pacnew/save files?
pacdiff -p -o
config:
[Seat:*]
#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
# dbus-service = True if LightDM provides a D-Bus service to control it
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7 # Setting this to a value < 7 implies security issues, see FS#46799
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
logind-check-graphical=true
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=$XDG_DATA_DIRS/lightdm/greeters:$XDG_DATA_DIRS/xgreeters
#backup-logs=true
#dbus-service=true
#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
#
# type = Seat type (local, xremote)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-config = Config file to pass to X server
# xserver-layout = Layout to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=local
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xmir-command=Xmir
#xserver-config=
#xserver-layout=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
greeter-session=lightdm-gtk-greeter
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
user-session=xfce
#allow-user-switching=true
#allow-guest=true
#guest-session=
session-wrapper=/etc/lightdm/Xsession
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=
#exit-on-failure=false
#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#hostname=
#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8
pacnew/savefiles:
/etc/locale.gen.pacnew
/etc/lightdm/lightdm.conf.pacnew
Ok then you need compare it and merge it… I guess GUI would be nice…
Install meld:
pamac install meld
Compare and merge it with meld:
sudo DIFFPROG=meld pacdiff
i’m not sure what that means…but will do it.
oh it says i have no space to do it, thats another thing i should be asking for you all…
i have a 16gb ssd and a 500gb hard drive.
in installation i selected /boot for the ssd
and /home for the hard drive.
but…how could i save packages in /home?
it asked me to update everything, should i redone all downgrades i did before? the kernel and mesa ones?
It basically means that configurations changes. Since it is rolling release you need to take care of these files… There could be a change which affects you now.
Then please do so… a partially updated systems results mostly in a broken system on a rolling release.
Downgrading was a wrong advice here…
You cannot. Everything what is installed from the package-manager have a static place on the root directory. But what can be done is outsource /usr to another partition and mount it to the root directory under /usr.
it says the files are the same
Maybe it is just the problem of the initialization time…
- Keep sure you are fully updated and have rebooted once.
- Edit mkinitcpio.conf and add
i915
sudo nano /etc/mkinitcpio.conf
Replace/Add MODULES=() → MODULES=( i915 )
- Generate new initcpio images:
sudo mkinitcpio -P
Now the intel driver will load as early as possible. Reboot now if everything looks correct.