new install stop in kbd_backlight

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

new install stop in kbd_backlight

Postby scanray » May 22nd, '20, 21:47

Hi all,

I just installed MGA 7.1 on a Dell Inspiron mini laptop (2012 ??). The installation works fine, but when I reboot, the system stops at:
Code: Select all
Starting Load/Save Screen Backlight Brightness of Leds:dell::kbd_backlight..

I have found a solution with mint, which is to install an old version and then upgrade to the new one.

Is there any solution for this in Mageia?
I would not like to change distro, so I ask.

I would appreciate any help
scanray
 
Posts: 32
Joined: Feb 5th, '14, 08:53

Re: new install stop in kbd_backlight

Postby doktor5000 » May 23rd, '20, 16:07

And you didn't add some customisations yet?

That is probably due the specifics of your hardware and how the driver for the keyboard is implemented. For the options see e.g. https://www.kernel.org/doc/Documentatio ... ell-laptop
I'd say that init script hasn't been adapted to systemd or it's running into some sort of race condition during shutdown.

Can you please show the output as root from

Code: Select all
ls -alR /sys/class/leds/dell::kbd_backlight
systemctl --all|grep -iE "dell|backlight"
journalctl -ab-1|grep -iE "dell|backlight"


If it's something like previous issues (e.g. https://forum.archlabslinux.com/t/solve ... error/2015 or https://ubuntuforums.org/showthread.php?t=2394672 ) you might be able to workaround it with
Code: Select all
systemctl mask systemd-backlight@leds\:dell\:\:kbd_backlight.service

Because there's no setting to prevent it from storing the backlight state during shutdown, only to prevent restore the state during boot - see man systemd-backlight@.service
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: new install stop in kbd_backlight

Postby scanray » May 23rd, '20, 20:54

HI doctor5000,
And you didn't add some customisations yet?

No, I can't load the system.

I have mounted the partitions with usb recovery
Code: Select all
ls -alR /sys/class/leds/dell::kbd_backlight
/mnt/sys/class/leds/del::kbd_backlight -> ../../devices/platform/dell-laptop/leds/dell::kbd_backlight/

The other 2 commands are for a running system; I don't think there is much point in running them from the rescue.

Thanks
scanray
 
Posts: 32
Joined: Feb 5th, '14, 08:53

Re: new install stop in kbd_backlight

Postby doktor5000 » May 23rd, '20, 21:25

Ahh, so this is during boot, I thought you meant that it stops during the reboot (so during shutdown after install).
Does the system boot in failsafe mode, or does it also hang?

You can try if the kernel boot option helps:
Code: Select all
systemd.restore_state=0

Have a look at https://wiki.mageia.org/en/How_to_set_u ... t_Loader_2 on how to do that.

If that doesn't help, you can try to move away the systemd unit from your USB recovery, it should be located at
/mnt/usr/lib/systemd/system/systemd-backlight@.service (if the / filesystem is mounted below /mnt)
Also from the USB recovery, check if you have this file, if so just remove it:
/mnt/var/lib/systemd/backlight/platform-dell-laptop:leds:dell::kbd_backlight

Although I can't tell you where the instantiated one would be stored, or if that's generated during boot.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: new install stop in kbd_backlight

Postby scanray » May 25th, '20, 00:18

Hi, Doctor5000,
Ahh, so this is during boot, I thought you meant that it stops during the reboot (so during shutdown after install)

that's right.
When I started in normal mode this would come out and not continue:
rw,noatime

When I booted into rescue mode it came out:
...kbd_backlight

booting into rescue mode with the command worked and loaded the desktop.
I did a reboot and it worked without putting the option in the grub, I also did the updates and there were no problems.
I am going to reinstall the system and see if it works. I made several changes before this and I want to see if they were not necessary.

Thanks for the help, I am really grateful
scanray
 
Posts: 32
Joined: Feb 5th, '14, 08:53

Re: new install stop in kbd_backlight

Postby doktor5000 » May 25th, '20, 16:13

scanray wrote:booting into rescue mode with the command worked and loaded the desktop.
I did a reboot and it worked without putting the option in the grub, I also did the updates and there were no problems.
I am going to reinstall the system and see if it works. I made several changes before this and I want to see if they were not necessary.

So if I understood correctly, you only had to use systemd.restore_state=0
as grub boot option once, and you did nothing else and the subsequent reboots were working normally ?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: new install stop in kbd_backlight

Postby scanray » May 25th, '20, 18:55

Yes, it is correct, but I will clarify the steps for you.

1) I reinstalled everything and booted with the option in the grub. In rescue mode, in normal it does not work.
2) I made the updates and rebooted. It didn't work.
3) I activated the tainted and made some updates. rebooted
4) booted normal, without putting anything in the grub

At the moment it is working, a little slow but it works. I'm going to check the installed drivers well because it is faster in win7, well, that's another topic.

Thanks for the help

PD:I did everything 2 times. The first time I did the updates when it finished installing. It didn't start. The tainted may have updated something that was not in the other repositories.
scanray
 
Posts: 32
Joined: Feb 5th, '14, 08:53


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron