• Failed to start Load/Save Screen Backlight Brightness of backlight


    si muchas gracias en verdad son increibles saben todo!!!
    cambiando de tema jajajaja
    tengo otro problema cuando la enciendo se queda trabada y la tengo que apagar vairias veces despues que sale el menu del grub
    y sale algo como esto

    [11.368635] r8169 000:02:00.0 (unnamed net device) (uninitialized): rtl_rxtx
    [FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
    See ´systemctl status systemd-backlight:acpi_video0.service´ for datails.

    que creen que sea?

  • again ;)

    @jmirandda420 said in Help with that!:

    See ´systemctl status systemd-backlight:acpi_video0.service´ for datails.

    systemctl status systemd-backlight:acpi_video0.service

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • @joekamprad out
    :smile:

    Unit systemd-backlight:acpi_video0.service could not be found.

  • https://wiki.archlinux.org/index.php/backlight#systemd-backlight_service
    https://bbs.archlinux.org/viewtopic.php?id=187921

    adding this to boot kernel parameters should do the trick:
    acpi_osi=’!Windows 2012’"

    sudo nano /etc/default/grub

    change the line starting with GRUB_CMDLINE… like this

    GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi=’!Windows 2012’" resume=UUID=…

    save with [Ctrl+X] and rebuild grub.cfg:

    sudo grub-mkconfig -o /boot/grub/grub.cfg

    reboot

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • About these errors before login, I have several, depending on whether I start with kernel-LTS or current kernel.

    Everything depends on the hardware of each user and the way the kernel works on that particular hardware, since for example the backlight error in previous kernels appeared and with the current one it disappeared (until it appears again … surely yes)

    $ journalctl -p 3 -xb -1
    -- Logs begin at Wed 2017-11-08 21:07:52 -03, end at Sat 2017-11-11 09:09:51 -03. --
    nov 11 07:34:05 arch kernel: cgroup: cgroup2: unknown option "nsdelegate"
    nov 11 07:34:09 arch kernel: ERROR @wl_notify_scan_status : 
    nov 11 07:34:10 arch kernel: Bluetooth: hci0 command 0x1003 tx timeout
    nov 11 07:34:11 arch kernel: ata2: exception Emask 0x40 SAct 0x0 SErr 0x40800 action 0x7
    nov 11 07:34:11 arch kernel: ata2: SError: { HostInt CommWake }
    nov 11 07:43:21 arch kernel: ata2: exception Emask 0x40 SAct 0x0 SErr 0x40800 action 0x7
    nov 11 07:43:21 arch kernel: ata2: SError: { HostInt CommWake }
    nov 11 07:56:04 arch kernel: ERROR @wl_notify_scan_status : 
    nov 11 07:56:05 arch kernel: ERROR @wl_notify_scan_status : 
    nov 11 07:56:06 arch kernel: Bluetooth: hci0 command 0x1001 tx timeout
    nov 11 07:56:14 arch kernel: Bluetooth: hci0: BCM: Reading local version info failed (-110)
    nov 11 08:07:08 arch kernel: ata2: exception Emask 0x40 SAct 0x0 SErr 0x40800 action 0x7
    nov 11 08:07:08 arch kernel: ata2: SError: { HostInt CommWake }
    

    This is solved, let’s say not to see it in the boot, just that, because the errors are always … with an entry in the grub: loglevel=3

    Just that.-

Posts 5Views 132
Log in to reply