Booting on Pi4 Mate - this now has a 1,5 minute delay

[MichaIng]

What did not work with the echo command? Any error message? It would be needed to prevent the upgrade to the RPi Ltd build of the lightdm package.

[thxstr]

unfortunately the text cannot shown better in an easy way - limitations, different networks and systems,…

The Echo command was telling something about rights-permission (elimated the image already, cannot check this further in the moment).

[Joulinar]

@thxstr

The Echo command was telling something about rights-permission

something you would need to do as user root or using sudo command

[thxstr]

sure, but the message was the same - maybe I can reproduce again later.

I’m facing now the problem with my changes, that the sound is killed. - It seems so, so I will check the

1. apt install --reinstall --allow-downgrades lightdm=1.26.0-8
2. systemctl mask dev-dri…

ways again with this.

[Joulinar]

@MichaIng

echo -e 'Package: src:lightdm\nPin: origin archive.raspberrypi.com\nPin-Priority: -1' > /etc/apt/preferences.d/dietpi-lightdm
apt update
apt install --reinstall --allow-downgrades lightdm=1.26.0-8

@MichaIng
this is working fine. Just did the switch to Debian package and start time is back to “normal”

graphical.target @12.196s
└─lightdm.service @12.090s +103ms
  └─systemd-user-sessions.service @12.050s +22ms
    └─network.target @12.007s

[thxstr]

Please check the sound - mine was gone. Definitely in both ways

[Joulinar]

I don’t use sound on this device. It’s just a demo SBC

[thxstr]

Checked again and reconfigured afterwards via dietpi-config the sound again. Rebooted. And it seems to be correct with that then. Will try more to confirm.
If the sound-management from mate is used in between everything is muted again. Reboot it works again. Strange.

[mohammadazeemwani]

just wanted to say that recently I was having issues with sound with hdmi, the fix was

1. check alsa is configured in dietpi-config audio settings and set the mode to auto detect hdmi or 3.5mm jack output
2. hurtful: my monitor volume was zero: so check that xD.
3. in /boot/config.txt,
   uncomment :

hdmi_drive=2
hdmi_force_hotplug=1

and change

dtoverlay=vc4-kms-dpi

after that I was good to go

[net-cat]

I ran into the same issue. At firtst I was thinking X11 wouldn’t start or it’s an issue due to my NFS boot but apparntly it is the missing dri.

The downgrade of lightdm to 1.26.0-8 fixed it for me. (Similar to thxstr I just downgraded first and did not install the debian variant)

I have a hunch there is a similar issue in Raspbian. But I can’t fully confirm that because I was faffing around with different kernel’s and TFTP and I’m pretty sure Raspbian didn’t work because I had something else messed up. If there is some interest in exploring this theory, I can try to find some time but at the moment I’m just glad it works!

[The_Raven]

I’m glad I found this post. I’ve been having the same problem on an RPI4 for a few months now, but I haven’t had time to investigate it further. So I can’t say if the fix works or not. BTW: At first I thought it had something to do with Wayland. But it doesn’t look like it. I will report if and what fixed my problem.
Edit:
Masking “dev-dri-card0.device” and “dev-dri-renderD128.device” solved my problem! I use XFCE with lightdm by the way and don’t have the option “dtoverlay=vc4-kms-v3d” in “/boot/config.txt”. The Problem came with an update but i can not remember when. Affected is a Pi4 and a Pi400.