Failed to start SDDM

Yes sir…I did install it

Ok, not sure. Install also the video-modesetting
sudo mhwd -i pci video-modesetting

I can’t see in your inxi, but do you use also some custom kernel boot parameters as described here?

Or maybe will work as described here by another forum member

I did run the command you just said and here is the output:

sudo mhwd -i pci video-nodesetting
Isudo] password for rocktim:
> Installing video modesetting.
Sourcing etcnhud-x86_64.conf
Has link support: true
Sourcing warvlib/mhud-db.pet-graphic_driversuideo-nodesetting-MHWDCONFIG
Processing classid: 0300
Sourcing parvlib/nhud scripts include_0900
> Successfully installed uideo-nodesetting

ps : I am using a image to text (OCR)to write this logs here in the forum so there may he some typos here but know that I am typing the right commands in my laptop

You will have to reboot the system now:
systemctl reboot

If is not working, do not panic, the links i provided have also instructions how to remove a driver and try something else.

It didn’t work. So which specific instructions I have to follow now?

sudo mhwd -r pci video-modesetting

ok so I did run that and it removed video-modesetting and now I should run
sudo mhwd -f -i pci video-linux ??
This will install video-linux ? I already have video-hybrid-amd-nvidia-450xx-prime . Should I not remove it first then install video-linux ?

No, it seems you need both and in that particular order, according to the other forum member that got his laptop working that way. SO, because i do not have my hands on such device, i can rely a bit on their experience. :slight_smile:
Also, make sure the system is updated:
sudo pacman-mirrors -f && sudo pacman -Syyu

Once you installed the drivers just reboot. If you are faced again in TTY only, then run:
systemctl stop sddm
systemctl disable sddm
systemctl enable sddm
then again
systemctl reboot

Also Quick question before I proceed on doing these. Doesn’t my laptop need wifi connection for installing these ? I mean can my system even use internet at this state ?

It could be connected in that state, yes. A way to test is if you get errors at update. :slight_smile:
Otherwise just test:
ping www.google.com

1 Like

Yes. But only sudo pacman-mirrors -f && sudo pacman -Syyu requires interenet connection.

1 Like

Ok I am trying to ping google and its not working also I am checking my mobile hotspot It’s only connected to 1 device which is my old laptop ,which I am using to write here.So my other laptop is definitely not connected to internet. When it was normal it required to put my password in some wallet to connect to wifi so how do I connect here ?

holy moly. I did some research and was able to connect to my wifi with nmcli command

nmcli d wifi list

nmcli d wifi connect <WiFiSSID> password <WiFiPassword> iface <WifiInterface>

Now I am downloading mirrors, will update when it’s done.

1 Like

So I did all of the steps from Installing mirror to upgrading system and adding the drivers.Nothing worked. So what can be done here now ?

We have to see where is failing.
systemctl status sddm
Did it failed the same way as before or something else?
What happens if you run from TTY
startplasma-x11

Sorry I went to sleep yesterday.it was too late. Man I am so bummed out , I got my new laptop and now I can’t even use it,
anyway this is what systemctl status sddm logs

systemctl status sdam
sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systend/system/sddm.service; enabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Tue 2020-09-08 09:15:03 IST; 1min 3s ago
Docs: man sddm(1)
man sddm.conf (5)
Process: 1113 ExecStart=/usr/bin/sddm (code=dumped, signal=ABRT)
Main PID: 1113 (code=dumped, signa l=ABRT)
Sep 08 09:15:03 rockt im systemd[1]: sddm.service: Scheduled restart job, restart counter is at 5
Sep 08 09:15:03 rocktin systemd[1]: Stopped Simple Desktop Display Manager.
Sep 08 09:15:03 rockt in systemd[1]: sddm.service: Start request repeated too quickly.
Sep 08 09:15:03 rocktim systemd[1]: sddm.service: Failed with result 'core-dump'.
Sep 08 09:15:03 rockt im systemd[1]: Failed to start Simple Desktop Display Manager,

and startplasma-x11 logs this

$DISPLAY is not set or cannot connect to the X server.

Do you have inside the ~/.xinitrc
the line
DEFAULT_SESSION=startplasma-x11
and at the end something like
exec $(get_session)
or
exec startplasma-x11
?

To me that coredump from sddm is a sign of partial update to be honest, but if you say the system worked just with video-linux then try that again.
Share then the proper inxi -Fxza --no-host (without the OCR thing, but from withing the installed system) and try some ACPI kernel boot parameters as mentioned in the other link.

Easiest option would to be to fresh install once again. once you get GUI install video-linux then Hybrid amd-nvidia driver then do reboot. I don’t whether video-modesetting is required or not.

So I did a fresh installation and it’s working now . But I did notice an error while booting that says:

[FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0

So after I got to the GUI I checked the backlight status with

systemctl status systemd-backlight@backlight:acpi_video0.service

and here is the log:

● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen Backlight Brightness of backlight:acpi_video0
     Loaded: loaded (/usr/lib/systemd/system/systemd-backlight@.service; static; vendor preset: disabled)
     Active: failed (Result: exit-code) since Tue 2020-09-08 13:08:02 IST; 14min ago
       Docs: man:systemd-backlight@.service(8)
    Process: 831 ExecStart=/usr/lib/systemd/systemd-backlight load backlight:acpi_video0 (code=exited, status=1/FAILURE)
   Main PID: 831 (code=exited, status=1/FAILURE)

Sep 08 13:08:02 rocktim systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Sep 08 13:08:02 rocktim systemd-backlight[831]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Sep 08 13:08:02 rocktim systemd[1]: systemd-backlight@backlight:acpi_video0.service: Main process exited, code=exited, status=1/FAILURE
Sep 08 13:08:02 rocktim systemd[1]: systemd-backlight@backlight:acpi_video0.service: Failed with result 'exit-code'.
Sep 08 13:08:02 rocktim systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.

I also looked for the journal entry for that specific PID with

journalctl -b _PID=831

and it outputs:

-- Logs begin at Tue 2020-09-08 13:08:01 IST, end at Tue 2020-09-08 13:31:50 IST. --
Sep 08 13:08:02 rocktim systemd-backlight[831]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device

[ps: It’s just a warning wheen booting everytime, But it’s not stopping the booting process, Still I would like to know what’s up]

Disable it:
sudo systemctl disable systemd-backlight@.service