Randr query version returned error 1

The provided service files are not functional here. There are two problems:

The provided service files are not functional here. There are two problems:

First one is that the two provided systemd user services stall on the same randr error as described above in the thread:

$ systemctl --user start redshift-gtk.service
$ systemctl --user status redshift-gtk.service
● redshift-gtk.service - Redshift display colour temperature adjustment
   Loaded: loaded (/usr/lib/systemd/user/redshift-gtk.service; disabled)
   Active: failed (Result: start-limit) since mer. 2014-05-21 00:20:49 CEST; 4min 31s ago
     Docs: http://jonls.dk/redshift/
  Process: 10989 ExecStart=/usr/bin/redshift (code=exited, status=1/FAILURE)
 Main PID: 10989 (code=exited, status=1/FAILURE)

mai 21 00:20:49 arch-clevo systemd[1338]: Unit redshift-gtk.service entered failed state.
mai 21 00:20:49 arch-clevo systemd[1338]: redshift-gtk.service holdoff time over, scheduling restart.
mai 21 00:20:49 arch-clevo systemd[1338]: Stopping Redshift display colour temperature adjustment...
mai 21 00:20:49 arch-clevo systemd[1338]: Starting Redshift display colour temperature adjustment...
mai 21 00:20:49 arch-clevo systemd[1338]: redshift-gtk.service start request repeated too quickly, refusing to start.
mai 21 00:20:49 arch-clevo systemd[1338]: Failed to start Redshift display colour temperature adjustment.
mai 21 00:20:49 arch-clevo systemd[1338]: Unit redshift-gtk.service entered failed state.

$ journalctl -b --user-unit=redshift-gtk
-- Logs begin at ven. 2014-05-02 15:49:42 CEST, end at mer. 2014-05-21 01:59:06 CEST. --
mai 21 00:20:48 arch-clevo systemd[1338]: Starting Redshift display colour temperature adjustment...
mai 21 00:20:48 arch-clevo systemd[1338]: Started Redshift display colour temperature adjustment.
mai 21 00:20:48 arch-clevo redshift[10979]: `RANDR Query Version' returned error -1
mai 21 00:20:48 arch-clevo redshift[10979]: Initialization of randr failed.
mai 21 00:20:48 arch-clevo systemd[1338]: redshift-gtk.service: main process exited, code=exited, status=1/FAILURE
mai 21 00:20:48 arch-clevo systemd[1338]: Unit redshift-gtk.service entered failed state.
mai 21 00:20:48 arch-clevo systemd[1338]: redshift-gtk.service holdoff time over, scheduling restart.
mai 21 00:20:48 arch-clevo systemd[1338]: Stopping Redshift display colour temperature adjustment...
...(repeats four times)...
mai 21 00:20:49 arch-clevo systemd[1338]: Starting Redshift display colour temperature adjustment...
mai 21 00:20:49 arch-clevo systemd[1338]: redshift-gtk.service start request repeated too quickly, refusing to start.
mai 21 00:20:49 arch-clevo systemd[1338]: Failed to start Redshift display colour temperature adjustment.
mai 21 00:20:49 arch-clevo systemd[1338]: Unit redshift-gtk.service entered failed state.

(it is the same for /usr/lib/systemd/user/redshift.service)
Adding «Environment=DISPLAY=:0» to the service files as suggested by Neburski  (under [Service], above ExecStart) and reloading user daemons ($ systemctl —user daemon-reload) do solve the problem.

However, another problem then arises specifically for redshift-gtk.service: the tray icon doesn’t appear.

It took me some time to figure it out, but actually if you’ve been watchful you might have already spotted what causes this: the redshift-gtk.service provided by Arch contains the wrong binary name.

Instead of having «ExecStart=/usr/bin/redshift-gtk» it contains «ExecStart=/usr/bin/redshift», as can be seen in the first systemctl status. There is a discrepancy between upstream and the Arch package: upstream file (not updated since March 6) and Arch x86_64 package (download and browse the archive to /usr/lib/systemd/user/redshift-gtk.service).
Replacing the binary name (simply adding «-gtk») does correct the issue, the tray icon appears on service start.

After doing those two steps, here’s the output of systemctl status:

$ systemctl --user status redshift-gtk.service
● redshift-gtk.service - Redshift display colour temperature adjustment
   Loaded: loaded (/usr/lib/systemd/user/redshift-gtk.service; disabled)
   Active: active (running) since mer. 2014-05-21 03:27:29 CEST; 17s ago
     Docs: http://jonls.dk/redshift/
 Main PID: 14493 (redshift-gtk)
   CGroup: /user.slice/user-1000.slice/user@1000.service/redshift-gtk.service
           ├─14493 python3 /usr/bin/redshift-gtk
           └─14494 /usr/bin/redshift -v

mai 21 03:27:29 arch-clevo systemd[1338]: Starting Redshift display colour temperature adjustment...
mai 21 03:27:29 arch-clevo systemd[1338]: Started Redshift display colour temperature adjustment.

Bug report is on its way…

Edit: FS#40476 (Arch bug tracker)
Edit 2: upstream bug report

Last edited by Neitsab (2014-05-21 01:33:50)

Источник

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012

Сегодня после загрузки арча, заметил, что яркость стоит 100%, хотя обычно во время загрузки она устанавливалась на 40%. У меня KDE. Полез менять в Power Management ползунок, показывает что яркость изменяется, но на самом деле она все еще 100%. Хоткеи тоже работают (всмысле показывают изменение шкалы яркости) но яркость все время на 100%. Подскажите куда копать.

Medar

#
9 лет, 6 месяцев назад

Темы:

12

Сообщения:

402

Участник с: 08 февраля 2013

Это с новым ядром? Какая видеокарта?

senid

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012

Вроде нет, я загрузился сегодня, вижу — не работает яркость, обновился, как раз ядро новое скачал. После ребута ничего не изменилось. Хотя вчера я тоже обновлялся возможно, мб что-то и поломалось. Только что установил дуал бутом арч с гномом, яркость не работает. У меня nvidia 410m + intel. Но я пользуюсь только видеокартой intel, драйвера только на эту карточку установлены. До этого момента всегда яркость работала.

Medar

#
9 лет, 6 месяцев назад

Темы:

12

Сообщения:

402

Участник с: 08 февраля 2013

А изменения яркости из консоли утилитой xbacklight работает ?

senid

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012 

sudo xbacklight -dec 10
No protocol specified
RANDR Query Version returned error -1

rusooo

#
9 лет, 6 месяцев назад

Темы:

1

Сообщения:

10

Участник с: 21 июля 2013

покажите

sudo find /sys/ | grep backlight

senid

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012

rusooo
покажите

sudo find /sys/ | grep backlight

/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/type
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/brightness
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/control
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/async
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_enabled
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_active_kids
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_active_time
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/autosuspend_delay_ms
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_status
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_usage
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/power/runtime_suspended_time
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/bl_power
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/max_brightness
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/device
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/subsystem
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/uevent
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/actual_brightness
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/type
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/brightness
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/control
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/async
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_enabled
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_active_kids
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_active_time
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/autosuspend_delay_ms
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_status
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_usage
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/power/runtime_suspended_time
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/bl_power
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/max_brightness
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/device
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/subsystem
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/uevent
/sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-LVDS-1/intel_backlight/actual_brightness
/sys/devices/pci0000:00/0000:00:02.0/backlight
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/type
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/brightness
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/control
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/async
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_enabled
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_active_kids
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_active_time
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/autosuspend_delay_ms
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_status
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_usage
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/power/runtime_suspended_time
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/bl_power
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/max_brightness
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/device
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/subsystem
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/uevent
/sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video1/actual_brightness
/sys/class/backlight
/sys/class/backlight/intel_backlight
/sys/class/backlight/acpi_video0
/sys/class/backlight/acpi_video1
/sys/module/video/parameters/use_bios_initial_backlight

Medar

#
9 лет, 6 месяцев назад

Темы:

12

Сообщения:

402

Участник с: 08 февраля 2013

У меня изначально такая проблема была, потом добавил в параметры загрузки ядра такое:

acpi_osi=Linux acpi_backlight=vendor

И все прекрасным образом заработало.

senid

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012

Проблема в обновлении :

[2013-07-26 13:16] [PACMAN] upgraded akonadi (1.10.1-1 -> 1.10.2-1)
[2013-07-26 13:16] [PACMAN] upgraded glib2 (2.36.3-2 -> 2.36.3-3)
[2013-07-26 13:16] [PACMAN] upgraded avahi (0.6.31-9 -> 0.6.31-10)
[2013-07-26 13:16] [PACMAN] upgraded harfbuzz (0.9.18-1 -> 0.9.19-1)
[2013-07-26 13:16] [PACMAN] upgraded libdatrie (0.2.5-1 -> 0.2.6-1)
[2013-07-26 13:16] [PACMAN] upgraded libthai (0.1.18-1 -> 0.1.19-1)
[2013-07-26 13:16] [PACMAN] upgraded linux (3.9.9-1 -> 3.10.2-1)
[2013-07-26 13:16] [PACMAN] upgraded videoproto (2.3.1-2 -> 2.3.2-1)

Откатил все пакеты, включая ядро, на их предыдущие версии. Яркость заработала. Конкретно виновника из этого списка не знаю.

senid

#
9 лет, 6 месяцев назад

senid avatar

Темы:

8

Сообщения:

43

Участник с: 31 декабря 2012

Medar
У меня изначально такая проблема была, потом добавил в параметры загрузки ядра такое:

acpi_osi=Linux acpi_backlight=vendor

И все прекрасным образом заработало.

У Вас была проблема после обновления ядра на 3.10 или до этого?
Источник

background: okay, so it’s been a while since I setup a «brightness» monitor, that just uses xbacklight to set the brightness, and then calls it again to store it in /tmp. DWM manages the «hardware» handling, i.e. it’s who detects the (single) keys being pressed so it can call the script. rest of key handling via DWM still works.

there was a system update yesterday, but a quick grep doesn’t reveal anything related with either xbacklight, or even xrandr (xbackligt’s man suggests it’s related to xrandr). there are a lot of libs updated, but I’m too lazy to check what they do.

on the other hand, this morning it still worked fine. it has only stopped working after I’ve physically cleaned the screen (touch-sensitive) — but it’s not the first time I’ve done so. a reboot (after managing to crash the X after seeing the screen wouldn’t light up, and startx not working) hasn’t helped.

now if I manually call xbacklight, all it does is print this:

>>> xbacklight -set 30
No outputs have backlight property

the hardware is an asus vivobook, intel IGPU, touchscreen (the rest should be irrelevant but correct me if I’m wrong).

note, I’ve seen other solutions for managing brightness — but I don’t like being told «hey, your carefully written scripts don’t work anymore, so go write some new». I know things change, but this seems an illogical change to me.

update: seeing xbacklight has a «display» argument (-d), I just tried to use it, after using xrandr to find which is the monitor’s number. this are the results:

>>> xrandr --listmonitors
Monitors: 1
 0: +LVDS-1 1366/256x768/144+0+0  LVDS-1

>>> xbacklight -d 0 -set 30 
RANDR Query Version returned error -1

>>> xbacklight -d 1 -set 30
RANDR Query Version returned error -1

PS: my full setup is a bit weird — I’m using just DWM without any login manager or any of those fancy things. feel free to ask if you think some of that may be relevant.

EDIT: so, I made xbacklight work again by following this. it was all about forcing the GPU to use the intel driver, via xorg.conf.

Источник

  • #1

I just installed FreeBSD 13.1 AMD64 on a laptop with an Intel CPU and Intel GMA integrated graphics. I cannot change the backlight on the LCD no matter what I try.

I first tried to load acpi_video using kldload acpi_video which did not post any error messages. However, it still wouldn’t let me change the brightness with the appropriate keys on the keyboard (Not even while holding down the Fn key).

Then I tried sysctl hw.acpi.video.lcd.active along with all the other commands starting with sysctl hw.acpi.video.lcd (.levels, .brightness, .fullpower and .economy). All of them resulted in sysctl telling me «sysctl: unknown oid ‘<inputted oid>'»

Then I installed pkg install graphics/intel-backlight. After installation, I tried running any and all commands beginning with backlight but everytime I would receive the error: «backlight: cannot open /dev/backlight/backlight0: No such file or directory»

After that, I tried installing xbacklight. executing xbacklight always returns me the error «RANDR Query Version returned error -1» outside of Xorg. Using the xbacklight command in Xorg (more specifically Xfce that I’m currently using.), the message «No outputs have backlight property» is returned.

Well, that’s everything I tried. Don’t know any other possible solution. Thank you in advance for helping me!

  • #2

Intel GMA integrated graphics

Which one exactly? Execute pciconf -lv | grep -B3 display, post output.

On newer hardware, for the display backlight to work, provided the Intel GPU is supported, a DRM kernel module must be installed and loaded.

Is

graphics/drm-kmod

installed and the i915 driver properly enabled, the user in the «video» group (see pkg info -D drm-510-kmod)? If it is, are there any «drm» error messages (see dmesg(8)).

For older hardware, besides

acpi_video

, there are brand specific hotkeys or OEM driver:

Code: 

/boot/kernel/acpi_asus.ko
/boot/kernel/acpi_asus_wmi.ko
/boot/kernel/acpi_fujitsu.ko
/boot/kernel/acpi_hp.ko
/boot/kernel/acpi_ibm.ko
/boot/kernel/acpi_panasonic.ko
/boot/kernel/acpi_sony.ko
/boot/kernel/acpi_toshiba.ko

For detailed information see the corresponding driver manual.

  • Thread Starter

  • #3

The command pciconf -lv | grep -B3 display tells me that the GPU is a «Mobile GM965/GL960 Integrated Graphics Controller». I successfully installed drm-kmod and pkg info -D drm-510-kmod reports no errors. The line kld_list="i915.kms" is currently present in /etc/rc.conf. dmesg reports a lot so there might be something I’ve missed, but I do spot «[drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19)», and «[drm] Got stolen memory base 0x3f800000, size 0x800000». Neither command kldload acpi_video nor kldload acpi_fujitsu results in any error being displayed (except the fact that they’re already loaded or in kernel, of course). The command sysctl hw.acpi.fujitsu.lcd_brightness returns me «sysctl: unknown oid ‘hw.acpi.fujitsu.lcd_brightness'». All the available commands beginning with sysctl hw.acpi.video.lcd. still return the message «sysctl: unknown oid ‘<inputted oid>'».

  • #4

After the i915 driver is loaded, is there a backlight device node created? Check ls /dev/backlight.

The command sysctl hw.acpi.fujitsu.lcd_brightness returns me «sysctl: unknown oid ‘hw.acpi.fujitsu.lcd_brightness'». All the available commands beginning with sysctl hw.acpi.video.lcd. still return the message «sysctl: unknown oid ‘<inputted oid>'».

There must not necessarily be a sysctl(8) oid for brightness. I have a AMD 5700U integrated «Lucienne» GPU, which doesn’t show those oids either. The amdgpu driver provided by

graphics/drm-510-kmod

, when loaded, creates a backlight device node, which can be configure with backlight(8).

If on your system no backlight device node is created then I’m out of ideas.

  • #5

Not 100% sure about that, may be a number is missing behind ‘lcd’ in your sysctl commands.
Try sysctl -a | grep lcd and watch the output.

On my machine I see this:

Code: 

# sysctl -a | grep lcd
hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
hw.acpi.video.lcd0.economy: 30
hw.acpi.video.lcd0.fullpower: 30
hw.acpi.video.lcd0.brightness: 30
hw.acpi.video.lcd0.active: 0

To change brightness I can use sysctl hw.acpi.video.lcd0.brightness=55

  • Thread Starter

  • #6

I tried inputting ls /dev/backlight before and after loading the i915 driver, but the directory is non-existent. Executing the command sysctl -a | grep lcd doesn’t result in any output; obviously resulting in the «unknown oid» error when trying sysctl hw.acpi.video.lcd0.brightness=55.

Anyway, I wrote the lines:
kld_list=»i915kms»
kld_list=»acpi_video»
in the /etc/rc.conf file. Shouldn’t these drivers autoload whenever I start my machine then, or am I just mistaken? They work fine when I input the kldload commands to load them after booting, however. Probably not relevant to the matter at hand, but I wanted to know regardless.

cracauer@


  • #7

Are the modules actually loaded?

Code: 

kldstat | grep 915
kldstat | grep acpi

cracauer@


  • #8

I tried inputting ls /dev/backlight before and after loading the i915 driver, but the directory is non-existent. Executing the command sysctl -a | grep lcd doesn’t result in any output; obviously resulting in the «unknown oid» error when trying sysctl hw.acpi.video.lcd0.brightness=55.

Anyway, I wrote the lines:
kld_list=»i915kms»
kld_list=»acpi_video»
in the /etc/rc.conf file. Shouldn’t these drivers autoload whenever I start my machine then, or am I just mistaken? They work fine when I input the kldload commands to load them after booting, however. Probably not relevant to the matter at hand, but I wanted to know regardless.

You need to write it like this:

Code: 

kld_list="i915kms acpi_video"

  • Thread Starter

  • #9

The modules are loaded. I checked with kldstat. Also, thank you cracauer@! The modules load automatically on startup every time now! In any case, I’m starting to wonder whether my graphics controller is actually supported by FreeBSD at all. Is there any way to really know for sure?

  • #11

The command pciconf -lv | grep -B3 display tells me that the GPU is a «Mobile GM965/GL960 Integrated Graphics Controller». I successfully installed drm-kmod and pkg info -D drm-510-kmod reports no errors. The line kld_list="i915.kms" is currently present in /etc/rc.conf.

OK.

Neither command kldload acpi_video nor kldload acpi_fujitsu results in any error being displayed (except the fact that they’re already loaded or in kernel, of course).

Both of those need to be loaded before or while booting from /boot/loader.conf — refer mans acpi_video(4) and acpi_fujitsu(4).

Try the more inclusive way of checking sysctls: sysctl -a | grep whatever where whatever is video or lcd or bright or fujitsu …

The command sysctl hw.acpi.fujitsu.lcd_brightness returns me «sysctl: unknown oid ‘hw.acpi.fujitsu.lcd_brightness'». All the available commands beginning with sysctl hw.acpi.video.lcd. still return the message «sysctl: unknown oid ‘<inputted oid>'».

I suspect because of having kldload’d after boot.

You may need to use devd.conf and a script to map brightness keys, but first see if the fujitsu or video modules will work as is.

Also, use apropos(1) to hunt for manual pages .. e.g. that intel-backlight pkg installs intel_backlight(1), note underscore not dash.

Источник
View previous topic :: View next topic  
Author Message
rkx1209
n00b
n00b

Joined: 26 Oct 2015
Posts: 1
Location: Japan
PostPosted: Mon Oct 26, 2015 12:04 pm    Post subject: Lenovo X240 backligh do not work Reply with quote
Hello,

I’m having problems setting up brightness keys (Fn+Home, Fn+End) on my Lenovo thinkpad X240.

When I hit Functional key and Home or End, it does not generate any acpi events.

(Only Fn+f1,f2 and f3 work. )

Code:

# acpi_listen

button/mute MUTE 00000080 00000000 K

button/volumedown VOLDN 00000080 00000000 K

button/volumeup VOLUP 00000080 00000000 K

I can’t also change it by xbacklight because of following errors.

Code:

# xbacklight -set 10%

No protocol specified

RANDR Query Version returned error -1



Code:

# grep BACKLIGHT /boot/config-3.17.8-gentoo-r1

# CONFIG_FB_BACKLIGHT is not set

CONFIG_BACKLIGHT_LCD_SUPPORT=y

CONFIG_BACKLIGHT_CLASS_DEVICE=y

CONFIG_BACKLIGHT_GENERIC=y

CONFIG_BACKLIGHT_APPLE=m

CONFIG_BACKLIGHT_SAHARA=m

CONFIG_BACKLIGHT_ADP8860=m

CONFIG_BACKLIGHT_ADP8870=m

CONFIG_BACKLIGHT_LM3639=m

CONFIG_BACKLIGHT_LV5207LP=m

CONFIG_BACKLIGHT_BD6107=m

CONFIG_LEDS_TRIGGER_BACKLIGHT=m

# grep ACPI /boot/config-3.17.8-gentoo-r1     

# Power management and ACPI options

CONFIG_ACPI=y

CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y

CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y

CONFIG_ACPI_SLEEP=y

CONFIG_ACPI_PROCFS_POWER=y

CONFIG_ACPI_EC_DEBUGFS=y

CONFIG_ACPI_AC=y

CONFIG_ACPI_BATTERY=y

CONFIG_ACPI_BUTTON=y

CONFIG_ACPI_VIDEO=y

CONFIG_ACPI_FAN=y

# CONFIG_ACPI_DOCK is not set

CONFIG_ACPI_PROCESSOR=y

CONFIG_ACPI_HOTPLUG_CPU=y

# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set

CONFIG_ACPI_THERMAL=y

# CONFIG_ACPI_CUSTOM_DSDT is not set

# CONFIG_ACPI_INITRD_TABLE_OVERRIDE is not set

# CONFIG_ACPI_DEBUG is not set

# CONFIG_ACPI_PCI_SLOT is not set

CONFIG_ACPI_CONTAINER=y

# CONFIG_ACPI_SBS is not set

# CONFIG_ACPI_HED is not set

# CONFIG_ACPI_CUSTOM_METHOD is not set

# CONFIG_ACPI_BGRT is not set

# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set

CONFIG_HAVE_ACPI_APEI=y

CONFIG_HAVE_ACPI_APEI_NMI=y

# CONFIG_ACPI_APEI is not set

# CONFIG_ACPI_EXTLOG is not set

CONFIG_X86_ACPI_CPUFREQ=m

CONFIG_X86_ACPI_CPUFREQ_CPB=y

CONFIG_PNPACPI=y

# CONFIG_BLK_DEV_IDEACPI is not set

CONFIG_ATA_ACPI=y

CONFIG_PATA_ACPI=m

CONFIG_ACPI_I2C_OPREGION=y

# ACPI drivers

# ACPI drivers

# CONFIG_SENSORS_ACPI_POWER is not set

CONFIG_ACPI_INT3403_THERMAL=y

# CONFIG_MMC_SDHCI_ACPI is not set

CONFIG_DMA_ACPI=y

CONFIG_THINKPAD_ACPI=m

CONFIG_THINKPAD_ACPI_ALSA_SUPPORT=y

# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set

# CONFIG_THINKPAD_ACPI_DEBUG is not set

# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set

CONFIG_THINKPAD_ACPI_VIDEO=y

CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y

# CONFIG_ACPI_WMI is not set

# CONFIG_ACPI_CMPC is not set



[/code]

Code:

# lspci -k | grep -A3 VGA

00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)

        Subsystem: Lenovo ThinkPad X240

00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)

        Subsystem: Lenovo ThinkPad X240

# ls /sys/class/

ata_device  fc_remote_ports  iscsi_connection  misc           rtc             scsi_generic

ata_link    fc_transport     iscsi_endpoint    net            sas_device      scsi_host

ata_port    fc_vports        iscsi_host        pci_bus        sas_end_device  sound

bdi         firmware         iscsi_iface       pcmcia_socket  sas_expander    spi_host

block       graphics         iscsi_session     phy            sas_host        spi_transport

bsg         hidraw           iscsi_transport   power_supply   sas_phy         tty

dma         hwmon            leds              pps            sas_port        vc

dmi         ieee80211        mdio_bus          ptp            scsi_device     vtconsole

fc_host     input            mem               rfkill         scsi_disk


Code:

# lsmod

Module                  Size  Used by

ctr                     3471  3

ccm                     6846  3

ipv6                  254355  26

coretemp                5084  0

arc4                    1816  2

kvm_intel             121332  0

iwlmvm                119404  0

mac80211              245979  1 iwlmvm

kvm                   233372  1 kvm_intel

snd_hda_codec_realtek    48931  1

iwlwifi                78248  1 iwlmvm

cfg80211              179892  3 iwlwifi,mac80211,iwlmvm

nvram                   5119  0

joydev                  8215  0

e1000e                137102  0

snd_hda_codec_generic    39119  1 snd_hda_codec_realtek

rfkill                 13361  2 cfg80211

serio_raw               3977  0

microcode               7558  0

rtc_cmos                7763  0

pcspkr                  1747  0

snd_hda_intel          16879  3

snd_hda_controller     13921  1 snd_hda_intel

snd_hda_codec          67795  4 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller

snd_hwdep               5373  1 snd_hda_codec

snd_pcm                62983  3 snd_hda_codec,snd_hda_intel,snd_hda_controller

snd_timer              15326  1 snd_pcm

snd                    49675  13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel

xts                     2727  0

gf128mul                5242  1 xts

aes_x86_64              7263  6

cbc                     2456  0

sha512_generic          4728  0

sha256_generic          9620  0

sha1_generic            1830  0

libiscsi               31451  0

scsi_transport_iscsi    60988  1 libiscsi

tg3                   130394  0

libphy                 20623  1 tg3

e1000                  86297  0

fuse                   65858  1

nfs                    98770  0

lockd                  52398  1 nfs

sunrpc                151868  2 nfs,lockd

jfs                   135431  0

btrfs                 659350  0

zlib_deflate           17619  1 btrfs

multipath               5248  0

linear                  3231  0

raid10                 33416  0

raid456                51858  0

async_raid6_recov       1241  1 raid456

async_memcpy            1342  1 raid456

async_pq                3780  1 raid456

async_xor               2801  2 async_pq,raid456

async_tx                1734  5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov

xor                    10248  2 btrfs,async_xor

raid6_pq               89350  3 async_pq,btrfs,async_raid6_recov

raid1                  23352  0

raid0                   6491  0

dm_snapshot            24077  0

dm_bufio               12910  1 dm_snapshot

dm_crypt               14625  0

dm_mirror              10939  0

dm_region_hash          6167  1 dm_mirror

dm_log                  7427  2 dm_region_hash,dm_mirror

dm_mod                 67941  5 dm_log,dm_mirror,dm_bufio,dm_crypt,dm_snapshot

hid_sunplus             1400  0

led_class               2867  1 iwlmvm

hid_samsung             2765  0

hid_pl                  1352  0

hid_petalynx            1897  0

hid_gyration            2035  0

sl811_hcd               8887  0

ohci_pci                2840  0

ohci_hcd               16991  1 ohci_pci

uhci_hcd               18605  0

usb_storage            44221  0

aic94xx                63622  0

libsas                 54174  1 aic94xx

lpfc                  478044  0

crc_t10dif              1031  1 lpfc

crct10dif_common        1252  1 crc_t10dif

qla2xxx               484443  0

megaraid_sas           80035  0

megaraid_mbox          23676  0

megaraid_mm             6768  1 megaraid_mbox

megaraid               33859  0

aacraid                68394  0

sx8                    10844  0

DAC960                 61942  0

cciss                  43739  0

3w_9xxx                29090  0

3w_xxxx                20764  0

mptsas                 32858  0

scsi_transport_sas     21333  3 libsas,mptsas,aic94xx

mptfc                  10188  0

scsi_transport_fc      39365  3 lpfc,qla2xxx,mptfc

mptspi                 11202  0

mptscsih               16081  3 mptfc,mptsas,mptspi

mptbase                54327  4 mptfc,mptsas,mptspi,mptscsih

atp870u                22200  0

dc395x                 26688  0

qla1280                19120  0

imm                     8729  0

parport                26491  1 imm

dmx3191d                9026  0

sym53c8xx              61643  0

gdth                   71653  0

advansys               44056  0

initio                 14876  0

BusLogic               19039  0

arcmsr                 23914  0

aic7xxx               103914  0

aic79xx               108306  0

scsi_transport_spi     17275  5 mptspi,sym53c8xx,aic79xx,aic7xxx,dmx3191d

sg                     21833  0

pdc_adma                5245  0

sata_inic162x           6565  0

sata_mv                23393  0

ata_piix               22567  0

sata_qstor              5028  0

sata_vsc                3977  0

sata_uli                2964  0

sata_sis                3597  0

sata_sx4                7867  0

sata_nv                18226  0

sata_via                7635  0

sata_svw                4285  0

sata_sil24             10055  0

sata_sil                7167  0

sata_promise            9783  0

pata_sl82c105           3597  0

pata_via                8268  0

pata_jmicron            2419  0

pata_marvell            2867  0

pata_sis               10214  1 sata_sis

pata_netcell            2201  0

pata_pdc202xx_old       4414  0

pata_triflex            3127  0

pata_atiixp             4435  0

pata_opti               2761  0

pata_amd               10191  0

pata_ali                9061  0

pata_it8213             3386  0

pata_pcmcia             9724  0

pcmcia                 29243  1 pata_pcmcia

pcmcia_core            10792  1 pcmcia

pata_ns87415            3220  0

pata_ns87410            2760  0

pata_serverworks        5436  0

pata_artop              4838  0

pata_it821x             8349  0

pata_optidma            4465  0

pata_hpt3x2n            5436  0

pata_hpt3x3             2992  0

pata_hpt37x            10896  0

pata_hpt366             4848  0

pata_cmd64x             6802  0

pata_efar               3534  0

pata_rz1000             2701  0

pata_sil680             4529  0

pata_radisys            2914  0

pata_pdc2027x           6227  0

pata_mpiix              2854  0

usbhid                 22361  0

ehci_pci                3240  0

ahci                   23427  2

libahci                18718  1 ahci

libata                140419  49 ahci,pata_pdc202xx_old,sata_inic162x,pata_efar,pata_opti,sata_sil,sata_sis,sata_sx4,sata_svw,sata_uli,sata_via,sata_vsc,pata_marvell,sata_promise,sata_mv,sata_nv,libahci,sata_qstor,sata_sil24,pata_netcell,pata_ali,pata_amd,pata_sis,pata_via,pata_sl82c105,pata_triflex,pata_ns87410,pata_ns87415,libsas,pdc_adma,pata_artop,pata_atiixp,pata_mpiix,pata_cmd64x,pata_hpt3x2n,pata_optidma,pata_hpt366,pata_hpt37x,pata_hpt3x3,pata_it8213,pata_it821x,pata_serverworks,pata_pcmcia,pata_sil680,pata_rz1000,ata_piix,pata_jmicron,pata_radisys,pata_pdc2027x

xhci_hcd               82500  0

ehci_hcd               34587  1 ehci_pci

ptp                     8828  2 tg3,e1000e

usbcore               139230  9 uhci_hcd,usb_storage,ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,usbhid,xhci_hcd,sl811_hcd

usb_common              1512  1 usbcore

pps_core                5672  1 ptp

# service acpid status

 * status: started

What should I do anymore?
Back to top

View user's profile Send private message

chithanh
Developer
Developer

Joined: 05 Aug 2006
Posts: 2156
Location: Berlin, Germany
PostPosted: Fri Oct 30, 2015 3:44 pm    Post subject: Reply with quote
In order to manage the backlight, CONFIG_BACKLIGHT_CLASS_DEVICE=y should give you a /sys/class/backlight directory with the controls inside. This appears to not happen on your system. Check dmesg why.

It may be that CONFIG_THINKPAD_ACPI_VIDEO competes with CONFIG_ACPI_VIDEO over control of the backlight device.
Back to top

View user's profile Send private message

Roman_Gruber
Advocate
Advocate

Joined: 03 Oct 2006
Posts: 3836
Location: Austro Bavaria
PostPosted: Fri Oct 30, 2015 9:59 pm    Post subject: Reply with quote
wikis are your friend. e.g.: https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X240

Debian on Lenovo Thinkpad X240

Quote:
The screen brightness control keys by default didn’t work for me, but there is a fix. You need to load the thinkpad acpi kernel module on boot. So edit /etc/modules file and add:

thinkpad_acpi

Then you’ll need to add this to your /etc/default/grub file and check that your kernel options are as follows:

RUB_CMDLINE_LINUX_DEFAULT=»quiet acpi_osi=!Windows2012 acpi_backlight=vendor»

This will enable the volume, mute, brightness and wireless media keys. I haven’t been able to make the microphone mute button work.

The keyboard backlight works by default using FN+spacebar and it looks nice. It has three states: dim, bright and off.

http://www.ubuntu.com/certification/hardware/201307-14019/

http://www.tfiu.de/x240/
Back to top

View user's profile Send private message

Roman_Gruber
Advocate
Advocate

Joined: 03 Oct 2006
Posts: 3836
Location: Austro Bavaria
PostPosted: Sat Oct 31, 2015 3:48 pm    Post subject: Reply with quote
question to the topic poster: Does this works or not? Feedback appreciated, thank you
Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Источник

Понравилась статья? Поделить с друзьями:
  • Random sampling error
  • Random measurement error
  • Ranch simulator ошибка fatal error
  • Ranch simulator ошибка dx12 is not
  • Ranch simulator fatal error ue4