[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VeZSkYZotboNhz8Pvu7uwytZtR0N4k2Bx+WgTdoLjGLtw@mail.gmail.com>
Date: Mon, 2 Oct 2017 16:17:31 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Pali Rohár <pali.rohar@...il.com>
Cc: "Gabriel M. Elder" <gabriel@...gnowsys.com>,
Gabriele Mazzotta <gabriele.mzt@...il.com>,
"dvhart@...radead.org" <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mario Limonciello <Mario.Limonciello@...l.com>
Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
On Mon, Oct 2, 2017 at 4:15 PM, Pali Rohár <pali.rohar@...il.com> wrote:
> On Monday 02 October 2017 13:06:46 Mario.Limonciello@...l.com wrote:
> Ok! Gabriel, can you provide us your DMI information about your machine?
>
> They are included in following files:
> /sys/class/dmi/id/sys_vendor
> /sys/class/dmi/id/product_name
>
> Beware that they may contain whitespace characters and it is important.
I would usually suggest to run dmidecode and attach an output somewhere.
(Just my 2 cents :-) )
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists