[Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

[marvin]

The screen brightness cannot be changed.

In 16.04, I could change the brightness via:
xrandr --output eDP-1 --brightness 0.7

WORKAROUND: Execute at a terminal:
xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8

WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/

---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: marvin 1768 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
MachineType: LENOVO 20FRS2M600
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/23/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET41W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FRS2M600
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 1st
dmi.product.name: 20FRS2M600
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1768208

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[marvin (mrueppel)]

apport information

[penalvch (penalvch)]

marvin, please address the all of the following:

1. When using 16.10, were you able to adjust the brightness via keyboard key press, or you could only adjust the brightness via xrandr?

2. In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[marvin (mrueppel)]

kernel-bug-exists-upstream-v4.17-rc6

Tested with v4.17-rc6 (771c577c23bac90597c685971d7297ea00f99d11) generic

Screen brightness canot be adapted in any way.

problem persists. If you have any lead, let me know what to test.

[marvin (mrueppel)]

Hi

1. When using 16.10, were you able to adjust the brightness via keyboard
key press, or you could only adjust the brightness via xrandr?

I could only adjust it with the terminal and xrandr

2. In order to allow additional upstream mainline kernel developers to
examine the issue, at your earliest convenience, could you please test the
latest mainline kernel available from http://kernel.ubuntu.com/
~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:

after testing the kernel the bug still exists. Not quite clear where to add
the flag though.

kernel-bug-exists-upstream-v4.17-rc6

the grub issue I had is fixed. (not related to this bug)

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Sun, May 20, 2018 at 12:49 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> marvin, please address the all of the following:
>
>
>
> 2. In order to allow additional upstream mainline kernel developers to
> examine the issue, at your earliest convenience, could you please test the
> latest mainline kernel available from http://kernel.ubuntu.com/~kern
> el-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
> 1) The one to test is at the very top line at the top of the page (not the
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually
> was released upstream.
> 4) Install instructions are available at https://wiki.ubuntu.com/Kernel
> /MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you
> couldn't boot into the OS) please make a comment in your report about this,
> and continue to test the next most recent kernel version until you can test
> to the issue. Once you've tested the mainline kernel, please comment on
> which kernel version specifically you tested. If this issue is not
> reproducible in the mainline kernel, please add the following tags by
> clicking on the yellow circle with a black pencil icon, next to the word
> Tags, located at the bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the issue is reproducible with the mainline kernel, please add the
> following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> It is most helpful that after testing of the latest mainline kernel is
> complete, you mark this report Status Confirmed.
>
> Lastly, to keep this issue relevant to upstream, please continue to test
> the latest mainline kernel as it becomes available.
>
> Thank you for your help.
>
> ** Tags added: bios-outdated-1.36 regression-potential
>
> ** Changed in: linux (Ubuntu)
> Impo...

[penalvch (penalvch)]

marvin:

1) When you state "I could only adjust it with the terminal and xrandr", what terminal command and what do you do with xrandr precisely?

2) To clarify, were you able to adjust the screen brightness prior to Ubuntu 16.10? If so, which specifically and how?

3) To advise, when changing the Status you don't have to change the Target Package as linux is a reasonable culprit. Having an empty Package when changing Status is for reports where the the root cause package isn't known, and nobody has any idea what to do with it.

[marvin (mrueppel)]

ok. Now Im on my 16.10 system again.

1. this is the comand I use for 70% it also works for numbers higher than 1
down to 0

xrandr --output eDP-1 --brightness 0.7

for this current system
Linux X1-16 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I have not used it prior to 16.10 but I think it worked. All systems newer
than 16.10 so far failed to Support my screen.

something like this discussion.
https://forums.lenovo.com/t5/Linux-Discussion/X-1-Yoga-OLED-brightness-control-under-linux/td-p/3948282
https://ubuntuforums.org/showthread.php?t=2337478

This looks like a solution to me, but I have not tried it because before
ubuntu 18 there was several other issues that made it unrunnable on my
machine.
https://github.com/udifuchs/icc-brightness

3) thx. what would you change it to then? Or leave it empty? Its my first
real bug report and I am happy to help.

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Wed, May 23, 2018 at 6:39 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> marvin:
>
> 1) When you state "I could only adjust it with the terminal and xrandr",
> what terminal command and what do you do with xrandr precisely?
>
> 2) To clarify, were you able to adjust the screen brightness prior to
> Ubuntu 16.10? If so, which specifically and how?
>
> 3) To advise, when changing the Status you don't have to change the
> Target Package as linux is a reasonable culprit. Having an empty Package
> when changing Status is for reports where the the root cause package
> isn't known, and nobody has any idea what to do with it.
>
> ** Package changed: ubuntu => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - OLED X1 yoga lenove, screen ubuntu, brightness issue
> + [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> ** Tags removed: regression-potential
> ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v4.17-rc6
> regression-release
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> As with all the proceeding distros from ubuntu 16.10 the brightness of
> the OLED screen canot be set. Since xrander is no more present there is
> also no hack around this problem anymore. This bug is a killer for using
> the system as full brightness drains the battery quickly.
> OLED screens have no backlight, thus this might be the issue.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-20-generic 4.15.0-20.21
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Tue May 1 10:45:56 2018
> SourcePackage: linux-signed
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.20.9-0ubuntu7
> ...

[marvin (mrueppel)]

Sorry. 16.04 not 16.10. I am on the LTS version

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Thu, May 24, 2018 at 3:47 PM, Marvin Rueppel <email address hidden> wrote:

> ok. Now Im on my 16.10 system again.
>
> 1. this is the comand I use for 70% it also works for numbers higher than
> 1 down to 0
>
> xrandr --output eDP-1 --brightness 0.7
>
> for this current system
> Linux X1-16 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> I have not used it prior to 16.10 but I think it worked. All systems newer
> than 16.10 so far failed to Support my screen.
>
> something like this discussion.
> https://forums.lenovo.com/t5/Linux-Discussion/X-1-Yoga-
> OLED-brightness-control-under-linux/td-p/3948282
> https://ubuntuforums.org/showthread.php?t=2337478
>
> This looks like a solution to me, but I have not tried it because before
> ubuntu 18 there was several other issues that made it unrunnable on my
> machine.
> https://github.com/udifuchs/icc-brightness
>
> 3) thx. what would you change it to then? Or leave it empty? Its my first
> real bug report and I am happy to help.
>
>
>
> Best Regards
> Marvin Rueppel
>
> Mobile: [phone]
> Email : <email address hidden>
>
> On Wed, May 23, 2018 at 6:39 PM, Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> marvin:
>>
>> 1) When you state "I could only adjust it with the terminal and xrandr",
>> what terminal command and what do you do with xrandr precisely?
>>
>> 2) To clarify, were you able to adjust the screen brightness prior to
>> Ubuntu 16.10? If so, which specifically and how?
>>
>> 3) To advise, when changing the Status you don't have to change the
>> Target Package as linux is a reasonable culprit. Having an empty Package
>> when changing Status is for reports where the the root cause package
>> isn't known, and nobody has any idea what to do with it.
>>
>> ** Package changed: ubuntu => linux (Ubuntu)
>>
>> ** Changed in: linux (Ubuntu)
>> Status: Confirmed => Incomplete
>>
>> ** Summary changed:
>>
>> - OLED X1 yoga lenove, screen ubuntu, brightness issue
>> + [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>>
>> ** Tags removed: regression-potential
>> ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v4.17-rc6
>> regression-release
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1768208
>>
>> Title:
>> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>>
>> Status in linux package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> As with all the proceeding distros from ubuntu 16.10 the brightness of
>> the OLED screen canot be set. Since xrander is no more present there is
>> also no hack around this problem anymore. This bug is a killer for using
>> the system as full brightness drains the battery quickly.
>> OLED screens have no backlight, thus this might be the issue.
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 18.04
>> Package: linux-image-4.15.0-20-generic 4.15.0-20.21
>> ProcVersionSignature: Ubuntu 4.15.0-20.21-generi...

[penalvch (penalvch)]

marvin:

Regarding xrandr, one may use it in 18.04 as per below. Were you stating that when you attempt to use the command that it worked in 16.04, but the same command doesn't work in 18.04?

xrandr
Screen 0: minimum 320 x 200, current 1288 x 703, maximum 16384 x 16384
VGA-1 connected primary 1288x703+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1288x703 59.93*+
   2560x1600 59.99 59.97
   1920x1440 60.00
   1856x1392 60.00
   1792x1344 60.00
   2048x1152 60.00
   1920x1200 59.88 59.95
   1920x1080 60.00
   1600x1200 60.00
   1680x1050 59.95 59.88
   1400x1050 59.98 59.95
   1600x900 60.00
   1280x1024 60.02
   1440x900 59.89 59.90
   1280x960 60.00
   1366x768 59.79 60.00
   1360x768 60.02
   1280x800 59.81 59.91
   1280x768 59.87 59.99
   1280x720 60.00
   1024x768 60.00
   800x600 60.32 56.25
   848x480 60.00
   640x480 59.94

[marvin (mrueppel)]

Ah, thank you very much. It works. I think before I was using wayland thus
why it didnt work.

This command did it.
 xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8

Using the scaling option also helped solve the scaling issue I had.
However, it showed another bug. When I use this scaling command (no matter
if fractional or not), then the mouse can still not move outside the 1x1
area. Meaning that if I scale such as

 xrandr --output eDP-1 --scale 2x2

then my mouse has only a quarter of the screen left for usage. Should I
file another bug report?

Best Regards
Marvin Rueppel

On Thu, May 24, 2018 at 6:34 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> marvin:
>
> Regarding xrandr, one may use it in 18.04 as per below. Were you stating
> that when you attempt to use the command that it worked in 16.04, but
> the same command doesn't work in 18.04?
>
> xrandr
> Screen 0: minimum 320 x 200, current 1288 x 703, maximum 16384 x 16384
> VGA-1 connected primary 1288x703+0+0 (normal left inverted right x axis y
> axis) 0mm x 0mm
> 1288x703 59.93*+
> 2560x1600 59.99 59.97
> 1920x1440 60.00
> 1856x1392 60.00
> 1792x1344 60.00
> 2048x1152 60.00
> 1920x1200 59.88 59.95
> 1920x1080 60.00
> 1600x1200 60.00
> 1680x1050 59.95 59.88
> 1400x1050 59.98 59.95
> 1600x900 60.00
> 1280x1024 60.02
> 1440x900 59.89 59.90
> 1280x960 60.00
> 1366x768 59.79 60.00
> 1360x768 60.02
> 1280x800 59.81 59.91
> 1280x768 59.87 59.99
> 1280x720 60.00
> 1024x768 60.00
> 800x600 60.32 56.25
> 848x480 60.00
> 640x480 59.94
>
> ** Description changed:
>
> - As with all the proceeding distros from ubuntu 16.10 the brightness of
> the OLED screen canot be set. Since xrander is no more present there is
> also no hack around this problem anymore. This bug is a killer for using
> the system as full brightness drains the battery quickly.
> - OLED screens have no backlight, thus this might be the issue.
> + The screen brightness cannot be changed.
>
> - ProblemType: Bug
> - DistroRelease: Ubuntu 18.04
> - Package: linux-image-4.15.0-20-generic 4.15.0-20.21
> - ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> - Uname: Linux 4.15.0-20-generic x86_64
> - ApportVersion: 2.20.9-0ubuntu7
> - Architecture: amd64
> - CurrentDesktop: ubuntu:GNOME
> - Date: Tue May 1 10:45:56 2018
> - SourcePackage: linux-signed
> - UpgradeStatus: No upgrade log present (probably fresh install)
> - ---
> + In 16.04, I could change the brightness via:
> + xrandr --output eDP-1 --brightness 0.7
> +
> + ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (...

[marvin (mrueppel)]

Ah ok. I could solve the mouse issue with

xrandr --output eDP-1 --auto --scale 1.5x1.5 --brightness 0.8 --panning
2560x1440

but then the screen looks terrible

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Mon, May 28, 2018 at 9:03 AM, Marvin Rueppel <email address hidden> wrote:

> Ah, thank you very much. It works. I think before I was using wayland thus
> why it didnt work.
>
> This command did it.
> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
> Using the scaling option also helped solve the scaling issue I had.
> However, it showed another bug. When I use this scaling command (no matter
> if fractional or not), then the mouse can still not move outside the 1x1
> area. Meaning that if I scale such as
>
> xrandr --output eDP-1 --scale 2x2
>
> then my mouse has only a quarter of the screen left for usage. Should I
> file another bug report?
>
>
> Best Regards
> Marvin Rueppel
>
>
> On Thu, May 24, 2018 at 6:34 PM, Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> marvin:
>>
>> Regarding xrandr, one may use it in 18.04 as per below. Were you stating
>> that when you attempt to use the command that it worked in 16.04, but
>> the same command doesn't work in 18.04?
>>
>> xrandr
>> Screen 0: minimum 320 x 200, current 1288 x 703, maximum 16384 x 16384
>> VGA-1 connected primary 1288x703+0+0 (normal left inverted right x axis y
>> axis) 0mm x 0mm
>> 1288x703 59.93*+
>> 2560x1600 59.99 59.97
>> 1920x1440 60.00
>> 1856x1392 60.00
>> 1792x1344 60.00
>> 2048x1152 60.00
>> 1920x1200 59.88 59.95
>> 1920x1080 60.00
>> 1600x1200 60.00
>> 1680x1050 59.95 59.88
>> 1400x1050 59.98 59.95
>> 1600x900 60.00
>> 1280x1024 60.02
>> 1440x900 59.89 59.90
>> 1280x960 60.00
>> 1366x768 59.79 60.00
>> 1360x768 60.02
>> 1280x800 59.81 59.91
>> 1280x768 59.87 59.99
>> 1280x720 60.00
>> 1024x768 60.00
>> 800x600 60.32 56.25
>> 848x480 60.00
>> 640x480 59.94
>>
>> ** Description changed:
>>
>> - As with all the proceeding distros from ubuntu 16.10 the brightness of
>> the OLED screen canot be set. Since xrander is no more present there is
>> also no hack around this problem anymore. This bug is a killer for using
>> the system as full brightness drains the battery quickly.
>> - OLED screens have no backlight, thus this might be the issue.
>> + The screen brightness cannot be changed.
>>
>> - ProblemType: Bug
>> - DistroRelease: Ubuntu 18.04
>> - Package: linux-image-4.15.0-20-generic 4.15.0-20.21
>> - ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>> - Uname: Linux 4.15.0-20-generic x86_64
>> - ApportVersion: 2.20.9-0ubuntu7
>> - Architecture: amd64
>> - CurrentDesktop: ubuntu:GNOME
>> - Date: Tue May 1 10:45:56 2018
>> - SourcePackage: linux-signed
>> - UpgradeStatus: No upgrade log present (probably fresh install)
>> - ---
>> + In 16.04, I could change the brightness via:
>> + xrandr --output eDP-1 --brightness 0.7
>> +
>> + ---
>> ApportVersion: 2.20.9-0ubuntu7
>> ...

[Kai-Heng Feng (kaihengfeng)]

What's the output of `find /sys/class/backlight`?

[marvin (mrueppel)]

marvin@marvin-X1-18:~$ find /sys/class/backlight
/sys/class/backlight
/sys/class/backlight/intel_backlight

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Mon, May 28, 2018 at 9:22 AM, Kai-Heng Feng <email address hidden>
wrote:

> What's the output of `find /sys/class/backlight`?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> The screen brightness cannot be changed.
>
> In 16.04, I could change the brightness via:
> xrandr --output eDP-1 --brightness 0.7
>
> ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-20-generic N/A
> linux-backports-modules-4.15.0-20-generic N/A
> linux-firmware 1.173
> Tags: bionic
> Uname: Linux 4.15.0-20-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 06/23/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: N1FET41W (1.15 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 20FRS2M600
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: None
> dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:
> pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:
> rvrNotDefined:cvnLENOVO:ct10:cvrNone:
> dmi.product.family: ThinkPad X1 Yoga 1st
> dmi.product.name: 20FRS2M600
> dmi.product.version: ThinkPad X1 Yoga 1st
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1768208/+subscriptions
>

[penalvch (penalvch)]

marvin:

1) Regarding the scaling and mouse issues, these are outside the scope of this report. Hence, feel free to file a separate report about each one by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information via a terminal:
ubuntu-bug xorg

2) Regarding the scope of this report, could you please provide the missing information from https://wiki.ubuntu.com/Kernel/Debugging/Backlight?

[marvin (mrueppel)]

Ok. Here the result:

assuming you only need the log files.

Executed as stated:

   -

   ls /sys/class/backlight > backlight
   -

   grep -r . /proc/acpi > acpi
   -

   sudo acpidump -o acpidump.txt
   -

   acpixtract acpidump.txt
   - Please note this must be done after the prior command, as it uses the
      newly created acpidump.txt, in order to produce the files to attach
      DSDT.dat, SSDT1.dat, SSDT2.dat, and SSDT3.dat.
   -

   iasl -d DSDT.dat
   - Please note this must be done after the prior command, as it uses the
      newly created DSDT.dat to create the file to attach DSDT.dsl.
   -

   sudo fwts > fwts
   -

   sudo fwts method > fwts_method
   -

   sudo dmidecode > dmidecode.log

On Mon, May 28, 2018 at 9:43 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> marvin:
>
> 1) Regarding the scaling and mouse issues, these are outside the scope of
> this report. Hence, feel free to file a separate report about each one by
> ensuring you have the package xdiagnose installed, and that you click the
> Yes button for attaching additional debugging information via a terminal:
> ubuntu-bug xorg
>
> 2) Regarding the scope of this report, could you please provide the
> missing information from
> https://wiki.ubuntu.com/Kernel/Debugging/Backlight?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> The screen brightness cannot be changed.
>
> In 16.04, I could change the brightness via:
> xrandr --output eDP-1 --brightness 0.7
>
> WORKAROUND: Execute at a terminal:
> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
> ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-20-generic N/A
> linux-backports-modules-4.15.0-20-generic N/A
> linux-firmware 1.173
> Tags: bionic
> Uname: Linux 4.15.0-20-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 06/23/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: N1FET41W (1.15 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 20FRS2M600
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: None
> dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23...

[marvin (mrueppel)]

https://extensions.gnome.org/extension/1222/oled-dimmer/

Found a smoother work around. Including keys it works out of the box.

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Thu, May 31, 2018 at 4:15 PM, Marvin Rueppel <email address hidden> wrote:

> Ok. Here the result:
>
>
> assuming you only need the log files.
>
> Executed as stated:
>
> -
>
> ls /sys/class/backlight > backlight
> -
>
> grep -r . /proc/acpi > acpi
> -
>
> sudo acpidump -o acpidump.txt
> -
>
> acpixtract acpidump.txt
> - Please note this must be done after the prior command, as it uses
> the newly created acpidump.txt, in order to produce the files to attach
> DSDT.dat, SSDT1.dat, SSDT2.dat, and SSDT3.dat.
> -
>
> iasl -d DSDT.dat
> - Please note this must be done after the prior command, as it uses
> the newly created DSDT.dat to create the file to attach DSDT.dsl.
> -
>
> sudo fwts > fwts
> -
>
> sudo fwts method > fwts_method
> -
>
> sudo dmidecode > dmidecode.log
>
>
>
>
>
>
>
>
>
> On Mon, May 28, 2018 at 9:43 PM, Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> marvin:
>>
>> 1) Regarding the scaling and mouse issues, these are outside the scope of
>> this report. Hence, feel free to file a separate report about each one by
>> ensuring you have the package xdiagnose installed, and that you click the
>> Yes button for attaching additional debugging information via a terminal:
>> ubuntu-bug xorg
>>
>> 2) Regarding the scope of this report, could you please provide the
>> missing information from
>> https://wiki.ubuntu.com/Kernel/Debugging/Backlight?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1768208
>>
>> Title:
>> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>>
>> Status in linux package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> The screen brightness cannot be changed.
>>
>> In 16.04, I could change the brightness via:
>> xrandr --output eDP-1 --brightness 0.7
>>
>> WORKAROUND: Execute at a terminal:
>> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>>
>> ---
>> ApportVersion: 2.20.9-0ubuntu7
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
>> CurrentDesktop: ubuntu:GNOME
>> DistroRelease: Ubuntu 18.04
>> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
>> MachineType: LENOVO 20FRS2M600
>> Package: linux (not installed)
>> ProcFB: 0 inteldrmfb
>> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
>> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>> RelatedPackageVersions:
>> linux-restricted-modules-4.15.0-20-generic N/A
>> linux-backports-modules-4.15.0-20-generic N/A
>> linux-firmware 1.173
>> Tags: bionic
>> Uname: Linux 4.15.0-20-generic x86_64
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>> _MarkForUpload: True
>>...

[penalvch (penalvch)]

marvin, regarding comment #30:

1)
>"assuming you only need the log files."

Unfortunately, this isn't the case.

2) Regarding attachments, the article requested separate attachments for each command (not combined into one). This is to help developers know what it is they are looking at, versus guessing at what was attached, trying to deduce if something was missed, or figure out why something unexpected happen.

[marvin (mrueppel)]

Ok, Thx for the feedback. Here is what I found so far. I will try and boot
with the different kernel parameter if needed but Ill first have to read up
on how to do that correctly.

1) current Kernel
marvin@marvin-X1-18:~$ uname -a
Linux marvin-X1-18 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

2) ls /sys/class/backlight > "ls sys-class-backlight"
intel_backlight

3) marvin@marvin-X1-18:~$ grep -r . /proc/acpi > "grep -r . proc-acpi"
/proc/acpi/ibm/fan:status: enabled
/proc/acpi/ibm/fan:speed: 0
/proc/acpi/ibm/fan:level: auto
/proc/acpi/ibm/led:status: supported
/proc/acpi/ibm/led:commands: <led> on, <led> off, <led> blink (<led> is
0-15)
/proc/acpi/ibm/wan:status: enabled
/proc/acpi/ibm/wan:commands: enable, disable
/proc/acpi/ibm/beep:status: supported
/proc/acpi/ibm/beep:commands: <cmd> (<cmd> is 0-17)
/proc/acpi/ibm/cmos:status: supported
/proc/acpi/ibm/cmos:commands: <cmd> (<cmd> is 0-21)
/proc/acpi/ibm/light:status: off
/proc/acpi/ibm/light:commands: on, off
/proc/acpi/ibm/driver:driver: ThinkPad ACPI Extras
/proc/acpi/ibm/driver:version: 0.25
/proc/acpi/ibm/hotkey:status: enabled
/proc/acpi/ibm/hotkey:mask: 0xff8c7ffb
/proc/acpi/ibm/hotkey:commands: enable, disable, reset, <mask>
/proc/acpi/ibm/volume:level: unsupported
/proc/acpi/ibm/volume:mute: on
/proc/acpi/ibm/kbdlight:status: 0
/proc/acpi/ibm/kbdlight:commands: 0, 1, 2
/proc/acpi/ibm/bluetooth:status: enabled
/proc/acpi/ibm/bluetooth:commands: enable, disable
/proc/acpi/button/lid/LID/state:state: open
/proc/acpi/wakeup:Device S-state Status Sysfs node
/proc/acpi/wakeup:LID S4 *enabled platform:PNP0C0D:00
/proc/acpi/wakeup:SLPB S3 *enabled platform:PNP0C0E:00
/proc/acpi/wakeup:IGBE S4 *enabled pci:0000:00:1f.6
/proc/acpi/wakeup:EXP9 S4 *disabled
/proc/acpi/wakeup:XHCI S3 *enabled pci:0000:00:14.0

4) sudo acpidump -o acpidump.txt
marvin@marvin-X1-18:~$ sudo acpidump -o acpidump.txt
Target path already exists, overwrite? [y|n] y
marvin@marvin-X1-18:~$ acpixtract acpidump.txt

Intel ACPI Component Architecture
ACPI Binary Table Extraction Utility version 20180105
Copyright (c) 2000 - 2018 Intel Corporation

  DSDT - 77564 bytes written (0x00012EFC) - dsdt.dat
  SSDT - 1027 bytes written (0x00000403) - ssdt1.dat
  SSDT - 612 bytes written (0x00000264) - ssdt2.dat
  SSDT - 1477 bytes written (0x000005C5) - ssdt3.dat
  SSDT - 1807 bytes written (0x0000070F) - ssdt4.dat
  SSDT - 3699 bytes written (0x00000E73) - ssdt5.dat
  SSDT - 6354 bytes written (0x000018D2) - ssdt6.dat
  SSDT - 19978 bytes written (0x00004E0A) - ssdt7.dat
  SSDT - 281 bytes written (0x00000119) - ssdt8.dat
  SSDT - 304 bytes written (0x00000130) - ssdt9.dat
  SSDT - 142 bytes written (0x0000008E) - ssdt10.dat
  SSDT - 281 bytes written (0x00000119) - ssdt11.dat
  SSDT - 1450 bytes written (0x000005AA) - ssdt12.dat
  SSDT - 975 bytes written (0x000003CF) - ssdt13.dat
marvin@marvin-X1-18:~$ iasl -d DSDT.dat

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180105
Copyright (c) 2000 - 2018 Intel Corporation

Could not open input file: DSDT.dat
Could not get ACPI t...

[Kai-Heng Feng (kaihengfeng)]

Please give latest mainline kernel (v4.19-rc4) another try, thanks!

[marvin (mrueppel)]

Tried it and no change. The brightness is not affected by the system
settings or keys.

To verify my version
marvin@X1-18:~$ uname -r
4.19.0-041900rc4-generic

and xrandr is still working, but only for a short time until the screen
updates again to full bringhtness. Interstingly the nightlight works (color
is adjusted ... brightness seems as well, though I am not sure)
marvin@X1-18:~$ xrandr --output eDP-1 --brightness 0.5

On Tue, Sep 18, 2018 at 4:50 AM Kai-Heng Feng <email address hidden>
wrote:

> Please give latest mainline kernel (v4.19-rc4) another try, thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The screen brightness cannot be changed.
>
> In 16.04, I could change the brightness via:
> xrandr --output eDP-1 --brightness 0.7
>
> WORKAROUND: Execute at a terminal:
> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
> WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/
>
> ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-20-generic N/A
> linux-backports-modules-4.15.0-20-generic N/A
> linux-firmware 1.173
> Tags: bionic
> Uname: Linux 4.15.0-20-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 06/23/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: N1FET41W (1.15 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 20FRS2M600
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: None
> dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
> dmi.product.family: ThinkPad X1 Yoga 1st
> dmi.product.name: 20FRS2M600
> dmi.product.version: ThinkPad X1 Yoga 1st
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+subscriptions
>

[Kai-Heng Feng (kaihengfeng)]

Sorry for not following this - does this still happen?

[marvin (mrueppel)]

Hey. Cool.

Yea. I have a key board combination now which uses the xrander command, so
I have a work around. But the oled screen is not working on linux in
general because of the backlight issue. oled has no backlight.

What I find strange is that lenovo is not doing anything.

For example here. One of many posts.
https://forums.lenovo.com/t5/Other-Linux-Discussions/X-1-Yoga-OLED-brightness-control-under-linux/td-p/3948282

On Wed, Apr 10, 2019 at 5:21 PM Kai-Heng Feng <email address hidden>
wrote:

> Sorry for not following this - does this still happen?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The screen brightness cannot be changed.
>
> In 16.04, I could change the brightness via:
> xrandr --output eDP-1 --brightness 0.7
>
> WORKAROUND: Execute at a terminal:
> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
> WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/
>
> ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-20-generic N/A
> linux-backports-modules-4.15.0-20-generic N/A
> linux-firmware 1.173
> Tags: bionic
> Uname: Linux 4.15.0-20-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 06/23/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: N1FET41W (1.15 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 20FRS2M600
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: None
> dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
> dmi.product.family: ThinkPad X1 Yoga 1st
> dmi.product.name: 20FRS2M600
> dmi.product.version: ThinkPad X1 Yoga 1st
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+subscriptions
>

[Kai-Heng Feng (kaihengfeng)]

Got it.
Basically we need to use ClutterBrightnessContrastEffect in GSD backlight to support brightness change for OLED systems.

[marvin (mrueppel)]

Yea. Interesting. Could be connected to why my screen sometimes resets to
full brightness when using chromium on my X1-18 4.15.0-46-generic

Let me know if I can help in any way.

Best Regards
Marvin Rueppel

Mobile: [phone]
Email : <email address hidden>

On Thu, Apr 11, 2019 at 9:56 AM Kai-Heng Feng <email address hidden>
wrote:

> Got it.
> Basically we need to use ClutterBrightnessContrastEffect in GSD backlight
> to support brightness change for OLED systems.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The screen brightness cannot be changed.
>
> In 16.04, I could change the brightness via:
> xrandr --output eDP-1 --brightness 0.7
>
> WORKAROUND: Execute at a terminal:
> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
> WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/
>
> ---
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: marvin 1768 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
> MachineType: LENOVO 20FRS2M600
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-20-generic N/A
> linux-backports-modules-4.15.0-20-generic N/A
> linux-firmware 1.173
> Tags: bionic
> Uname: Linux 4.15.0-20-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 06/23/2016
> dmi.bios.vendor: LENOVO
> dmi.bios.version: N1FET41W (1.15 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 20FRS2M600
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: None
> dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
> dmi.product.family: ThinkPad X1 Yoga 1st
> dmi.product.name: 20FRS2M600
> dmi.product.version: ThinkPad X1 Yoga 1st
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+subscriptions
>