How can I help with thinkpad x220 issues?

[Natacha Porté]

Hello,

I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
recent thread here I gather it almost works with FreeBSD, and the
remaining problems are screen brightness and screen left unpowered at
resume. Is that right?

So my question is, how can I help make progress in any of these area?
(though I admit I'm more interested in having the brightness problem
solved than the resume one)

I don't know anything about ACPI or about FreeBSD or Linux internals,
but I'm quite proficient in C and somewhat used to navigate in unknown
huge code bases.

So I guess the first steps to help would be to first learn stuff.

However I don't have much time available. I guess FreeBSD 11 would reach
end-of-life before I could reach a level of understanding I find
satisfying (though I admit I have high standards there), so I would have
to prioritize. So my question is rather *what* should I learn to provide
help as soon as possible?

For example, if the brightness issue is just a matter of extracting the
right numbers from linux kernel code and plug them into FreeBSD, I
probably won't need to learn anything more about ACPI than what I would
gather looking at the code. I guess if it was that simple someone would
have already done it, but that illustrate well my point about
prioritizing learning.

Or is the barrier of entry too high for me to be of any use?


Thanks in advance for your advice,
Natacha Porté
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Любомир Григоров]

Well, brightness works with the command line, sooo.... I think it has to be
mapped to the hardware keys. There is a long thread where I discussed this
with a couple other members (toward the bottom for the recent brightness
discussion).
http://comments.gmane.org/gmane.os.freebsd.current/135827

Good news is that Konstantin's latest patch works with FreeBSD 9-STABLE so
no longer need to run HEAD. I would love to see resume work, though.

Cheers.



--
Lyubomir Grigorov (bgalakazam)
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Ian Smith-12]

On Wed, 23 May 2012 10:05:28 -0700, ??????? ???????? wrote:

 > Good news is that Konstantin's latest patch works with FreeBSD 9-STABLE so
 > no longer need to run HEAD. I would love to see resume work, though.

I don't suppose your Thinkpad maybe one of those that resumes properly,
from X or from a VTY, with sysctl hw.syscons.sc_no_suspend_vtswitch=1 ?

cheers, Ian
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Любомир Григоров]

> I don't suppose your Thinkpad maybe one of those that resumes properly,
> from X or from a VTY, with sysctl hw.syscons.sc_no_suspend_vtswitch=1 ?
>
> cheers, Ian
>

No. I got my X220 AFTER the suspend/resume was broken. There was a point, I
hear, during which it worked properly. I guess we are getting there.
FreeBSD 10 has some hopes for me, including Intel GEM/KMS patch in code and
some other goodies.

--
Lyubomir Grigorov (bgalakazam)
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Kevin Oberman-3]

On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]> wrote:

> Hello,
>
> I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
> recent thread here I gather it almost works with FreeBSD, and the
> remaining problems are screen brightness and screen left unpowered at
> resume. Is that right?
>
> So my question is, how can I help make progress in any of these area?
> (though I admit I'm more interested in having the brightness problem
> solved than the resume one)
>
> I don't know anything about ACPI or about FreeBSD or Linux internals,
> but I'm quite proficient in C and somewhat used to navigate in unknown
> huge code bases.
>
> So I guess the first steps to help would be to first learn stuff.
>
> However I don't have much time available. I guess FreeBSD 11 would reach
> end-of-life before I could reach a level of understanding I find
> satisfying (though I admit I have high standards there), so I would have
> to prioritize. So my question is rather *what* should I learn to provide
> help as soon as possible?
>
> For example, if the brightness issue is just a matter of extracting the
> right numbers from linux kernel code and plug them into FreeBSD, I
> probably won't need to learn anything more about ACPI than what I would
> gather looking at the code. I guess if it was that simple someone would
> have already done it, but that illustrate well my point about
> prioritizing learning.
>
> Or is the barrier of entry too high for me to be of any use?

If it has not been committed, the minor fix to make acpi_ibm work on
modern ThinkPads needs to be committed. Once done, the issues
mentioned need to be addressed.This includes getting brightness to be
setable from both the keypad hot-keys and from applications. ATM, I
can set the brightness, but making the hot-keys work will require the
ability to extract the current level so that it may be adjusted
plus/minus one.

The other issue is volume control keys don't work. I suspect it will
be similar to brightness, but I don't know just how to figure it out.

I should also mention that I don't have an X220. I have a T520, but
the issues seem to be identical, so fixing one will probably fix a lot
of recent ThinkPads.
--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Lars Engels-2]

On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:

> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]> wrote:
> > Hello,
> >
> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
> > recent thread here I gather it almost works with FreeBSD, and the
> > remaining problems are screen brightness and screen left unpowered at
> > resume. Is that right?
> >
> > So my question is, how can I help make progress in any of these area?
> > (though I admit I'm more interested in having the brightness problem
> > solved than the resume one)
> >
> > I don't know anything about ACPI or about FreeBSD or Linux internals,
> > but I'm quite proficient in C and somewhat used to navigate in unknown
> > huge code bases.
> >
> > So I guess the first steps to help would be to first learn stuff.
> >
> > However I don't have much time available. I guess FreeBSD 11 would reach
> > end-of-life before I could reach a level of understanding I find
> > satisfying (though I admit I have high standards there), so I would have
> > to prioritize. So my question is rather *what* should I learn to provide
> > help as soon as possible?
> >
> > For example, if the brightness issue is just a matter of extracting the
> > right numbers from linux kernel code and plug them into FreeBSD, I
> > probably won't need to learn anything more about ACPI than what I would
> > gather looking at the code. I guess if it was that simple someone would
> > have already done it, but that illustrate well my point about
> > prioritizing learning.
> >
> > Or is the barrier of entry too high for me to be of any use?
>
> If it has not been committed, the minor fix to make acpi_ibm work on
> modern ThinkPads needs to be committed. Once done, the issues
> mentioned need to be addressed.This includes getting brightness to be
> setable from both the keypad hot-keys and from applications. ATM, I
> can set the brightness, but making the hot-keys work will require the
> ability to extract the current level so that it may be adjusted
> plus/minus one.
>
> The other issue is volume control keys don't work. I suspect it will
> be similar to brightness, but I don't know just how to figure it out.
>
> I should also mention that I don't have an X220. I have a T520, but
> the issues seem to be identical, so fixing one will probably fix a lot
> of recent ThinkPads.

About the key:

Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
"cat /var/run/devd.pipe" and then press the keys. Does anything show up?

[Kevin Oberman-3]

On Wed, May 23, 2012 at 11:55 PM, Lars Engels <[hidden email]> wrote:

> On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:
>> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]> wrote:
>> > Hello,
>> >
>> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
>> > recent thread here I gather it almost works with FreeBSD, and the
>> > remaining problems are screen brightness and screen left unpowered at
>> > resume. Is that right?
>> >
>> > So my question is, how can I help make progress in any of these area?
>> > (though I admit I'm more interested in having the brightness problem
>> > solved than the resume one)
>> >
>> > I don't know anything about ACPI or about FreeBSD or Linux internals,
>> > but I'm quite proficient in C and somewhat used to navigate in unknown
>> > huge code bases.
>> >
>> > So I guess the first steps to help would be to first learn stuff.
>> >
>> > However I don't have much time available. I guess FreeBSD 11 would reach
>> > end-of-life before I could reach a level of understanding I find
>> > satisfying (though I admit I have high standards there), so I would have
>> > to prioritize. So my question is rather *what* should I learn to provide
>> > help as soon as possible?
>> >
>> > For example, if the brightness issue is just a matter of extracting the
>> > right numbers from linux kernel code and plug them into FreeBSD, I
>> > probably won't need to learn anything more about ACPI than what I would
>> > gather looking at the code. I guess if it was that simple someone would
>> > have already done it, but that illustrate well my point about
>> > prioritizing learning.
>> >
>> > Or is the barrier of entry too high for me to be of any use?
>>
>> If it has not been committed, the minor fix to make acpi_ibm work on
>> modern ThinkPads needs to be committed. Once done, the issues
>> mentioned need to be addressed.This includes getting brightness to be
>> setable from both the keypad hot-keys and from applications. ATM, I
>> can set the brightness, but making the hot-keys work will require the
>> ability to extract the current level so that it may be adjusted
>> plus/minus one.
>>
>> The other issue is volume control keys don't work. I suspect it will
>> be similar to brightness, but I don't know just how to figure it out.
>>
>> I should also mention that I don't have an X220. I have a T520, but
>> the issues seem to be identical, so fixing one will probably fix a lot
>> of recent ThinkPads.
>
> About the key:
>
> Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
> "cat /var/run/devd.pipe" and then press the keys. Does anything show up?

After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI
event when pressing either button, but I do get regular key press
events:
KeyPress event, serial 30, synthetic NO, window 0x4600001,
    root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750),
    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x4600001,
    root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750),
    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x4600001,
    root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629),
    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x4600001,
    root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629),
    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

I can set these up as hot keys and issue a command, but I have no idea
what I can set to adjust the hardware volume. But I will also need to
read out the current volume so I know what value to which is should be
set. (Same issue as with brightness.)
--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Pierre-Luc Drouin]

On Friday, May 25, 2012, Kevin Oberman wrote:

> On Wed, May 23, 2012 at 11:55 PM, Lars Engels <[hidden email]<javascript:;>>
> wrote:
> > On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:
> >> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]<javascript:;>>
> wrote:
> >> > Hello,
> >> >
> >> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
> >> > recent thread here I gather it almost works with FreeBSD, and the
> >> > remaining problems are screen brightness and screen left unpowered at
> >> > resume. Is that right?
> >> >
> >> > So my question is, how can I help make progress in any of these area?
> >> > (though I admit I'm more interested in having the brightness problem
> >> > solved than the resume one)
> >> >
> >> > I don't know anything about ACPI or about FreeBSD or Linux internals,
> >> > but I'm quite proficient in C and somewhat used to navigate in unknown
> >> > huge code bases.
> >> >
> >> > So I guess the first steps to help would be to first learn stuff.
> >> >
> >> > However I don't have much time available. I guess FreeBSD 11 would
> reach
> >> > end-of-life before I could reach a level of understanding I find
> >> > satisfying (though I admit I have high standards there), so I would
> have
> >> > to prioritize. So my question is rather *what* should I learn to
> provide
> >> > help as soon as possible?
> >> >
> >> > For example, if the brightness issue is just a matter of extracting
> the
> >> > right numbers from linux kernel code and plug them into FreeBSD, I
> >> > probably won't need to learn anything more about ACPI than what I
> would
> >> > gather looking at the code. I guess if it was that simple someone
> would
> >> > have already done it, but that illustrate well my point about
> >> > prioritizing learning.
> >> >
> >> > Or is the barrier of entry too high for me to be of any use?
> >>
> >> If it has not been committed, the minor fix to make acpi_ibm work on
> >> modern ThinkPads needs to be committed. Once done, the issues
> >> mentioned need to be addressed.This includes getting brightness to be
> >> setable from both the keypad hot-keys and from applications. ATM, I
> >> can set the brightness, but making the hot-keys work will require the
> >> ability to extract the current level so that it may be adjusted
> >> plus/minus one.
> >>
> >> The other issue is volume control keys don't work. I suspect it will
> >> be similar to brightness, but I don't know just how to figure it out.
> >>
> >> I should also mention that I don't have an X220. I have a T520, but
> >> the issues seem to be identical, so fixing one will probably fix a lot
> >> of recent ThinkPads.
> >
> > About the key:
> >
> > Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
> > "cat /var/run/devd.pipe" and then press the keys. Does anything show up?
>
> After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI
> event when pressing either button, but I do get regular key press
> events:
> KeyPress event, serial 30, synthetic NO, window 0x4600001,
>    root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750),
>    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
> same_screen YES,
>    XLookupString gives 0 bytes:
>    XmbLookupString gives 0 bytes:
>    XFilterEvent returns: False
>
> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>    root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750),
>    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
> same_screen YES,
>    XLookupString gives 0 bytes:
>    XFilterEvent returns: False
>
> KeyPress event, serial 33, synthetic NO, window 0x4600001,
>    root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629),
>    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
> same_screen YES,
>    XLookupString gives 0 bytes:
>    XmbLookupString gives 0 bytes:
>    XFilterEvent returns: False
>
> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>    root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629),
>    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
> same_screen YES,
>    XLookupString gives 0 bytes:
>    XFilterEvent returns: False
>
> I can set these up as hot keys and issue a command, but I have no idea
> what I can set to adjust the hardware volume. But I will also need to
> read out the current volume so I know what value to which is should be
> set. (Same issue as with brightness.)
> --
> R. Kevin Oberman, Network Engineer
> E-mail: [hidden email] <javascript:;>

You should be able to bind these keys to commands such as mixer vol +5 amd
mixer vol -5

> _______________________________________________
> [hidden email] <javascript:;> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "[hidden email]<javascript:;>
> "
>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Lars Engels-2]

On Fri, May 25, 2012 at 08:25:47PM -0700, Kevin Oberman wrote:

> On Wed, May 23, 2012 at 11:55 PM, Lars Engels <[hidden email]> wrote:
> > On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:
> >> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]> wrote:
> >> > Hello,
> >> >
> >> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
> >> > recent thread here I gather it almost works with FreeBSD, and the
> >> > remaining problems are screen brightness and screen left unpowered at
> >> > resume. Is that right?
> >> >
> >> > So my question is, how can I help make progress in any of these area?
> >> > (though I admit I'm more interested in having the brightness problem
> >> > solved than the resume one)
> >> >
> >> > I don't know anything about ACPI or about FreeBSD or Linux internals,
> >> > but I'm quite proficient in C and somewhat used to navigate in unknown
> >> > huge code bases.
> >> >
> >> > So I guess the first steps to help would be to first learn stuff.
> >> >
> >> > However I don't have much time available. I guess FreeBSD 11 would reach
> >> > end-of-life before I could reach a level of understanding I find
> >> > satisfying (though I admit I have high standards there), so I would have
> >> > to prioritize. So my question is rather *what* should I learn to provide
> >> > help as soon as possible?
> >> >
> >> > For example, if the brightness issue is just a matter of extracting the
> >> > right numbers from linux kernel code and plug them into FreeBSD, I
> >> > probably won't need to learn anything more about ACPI than what I would
> >> > gather looking at the code. I guess if it was that simple someone would
> >> > have already done it, but that illustrate well my point about
> >> > prioritizing learning.
> >> >
> >> > Or is the barrier of entry too high for me to be of any use?
> >>
> >> If it has not been committed, the minor fix to make acpi_ibm work on
> >> modern ThinkPads needs to be committed. Once done, the issues
> >> mentioned need to be addressed.This includes getting brightness to be
> >> setable from both the keypad hot-keys and from applications. ATM, I
> >> can set the brightness, but making the hot-keys work will require the
> >> ability to extract the current level so that it may be adjusted
> >> plus/minus one.
> >>
> >> The other issue is volume control keys don't work. I suspect it will
> >> be similar to brightness, but I don't know just how to figure it out.
> >>
> >> I should also mention that I don't have an X220. I have a T520, but
> >> the issues seem to be identical, so fixing one will probably fix a lot
> >> of recent ThinkPads.
> >
> > About the key:
> >
> > Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
> > "cat /var/run/devd.pipe" and then press the keys. Does anything show up?
>
> After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI
> event when pressing either button, but I do get regular key press
> events:
> KeyPress event, serial 30, synthetic NO, window 0x4600001,
>     root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750),
>     state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>     root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750),
>     state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyPress event, serial 33, synthetic NO, window 0x4600001,
>     root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629),
>     state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>     root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629),
>     state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
> same_screen YES,
>     XLookupString gives 0 bytes:
>     XFilterEvent returns: False

Hmm, okay, that's not too bad. At least the keys are recognized.


>
> I can set these up as hot keys and issue a command, but I have no idea
> what I can set to adjust the hardware volume. But I will also need to
> read out the current volume so I know what value to which is should be
> set. (Same issue as with brightness.)

Do you have dev.acpi_ibm.0.lcd_brightness and .volume?

If you cou can write a script that raises / lowers the values with
sysctl.

[Kevin Oberman-3]

On Fri, May 25, 2012 at 10:10 PM, Pierre-Luc Drouin
<[hidden email]> wrote:

>
>
> On Friday, May 25, 2012, Kevin Oberman wrote:
>>
>> On Wed, May 23, 2012 at 11:55 PM, Lars Engels <[hidden email]>
>> wrote:
>> > On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:
>> >> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]>
>> >> wrote:
>> >> > Hello,
>> >> >
>> >> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
>> >> > recent thread here I gather it almost works with FreeBSD, and the
>> >> > remaining problems are screen brightness and screen left unpowered at
>> >> > resume. Is that right?
>> >> >
>> >> > So my question is, how can I help make progress in any of these area?
>> >> > (though I admit I'm more interested in having the brightness problem
>> >> > solved than the resume one)
>> >> >
>> >> > I don't know anything about ACPI or about FreeBSD or Linux internals,
>> >> > but I'm quite proficient in C and somewhat used to navigate in
>> >> > unknown
>> >> > huge code bases.
>> >> >
>> >> > So I guess the first steps to help would be to first learn stuff.
>> >> >
>> >> > However I don't have much time available. I guess FreeBSD 11 would
>> >> > reach
>> >> > end-of-life before I could reach a level of understanding I find
>> >> > satisfying (though I admit I have high standards there), so I would
>> >> > have
>> >> > to prioritize. So my question is rather *what* should I learn to
>> >> > provide
>> >> > help as soon as possible?
>> >> >
>> >> > For example, if the brightness issue is just a matter of extracting
>> >> > the
>> >> > right numbers from linux kernel code and plug them into FreeBSD, I
>> >> > probably won't need to learn anything more about ACPI than what I
>> >> > would
>> >> > gather looking at the code. I guess if it was that simple someone
>> >> > would
>> >> > have already done it, but that illustrate well my point about
>> >> > prioritizing learning.
>> >> >
>> >> > Or is the barrier of entry too high for me to be of any use?
>> >>
>> >> If it has not been committed, the minor fix to make acpi_ibm work on
>> >> modern ThinkPads needs to be committed. Once done, the issues
>> >> mentioned need to be addressed.This includes getting brightness to be
>> >> setable from both the keypad hot-keys and from applications. ATM, I
>> >> can set the brightness, but making the hot-keys work will require the
>> >> ability to extract the current level so that it may be adjusted
>> >> plus/minus one.
>> >>
>> >> The other issue is volume control keys don't work. I suspect it will
>> >> be similar to brightness, but I don't know just how to figure it out.
>> >>
>> >> I should also mention that I don't have an X220. I have a T520, but
>> >> the issues seem to be identical, so fixing one will probably fix a lot
>> >> of recent ThinkPads.
>> >
>> > About the key:
>> >
>> > Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
>> > "cat /var/run/devd.pipe" and then press the keys. Does anything show up?
>>
>> After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI
>> event when pressing either button, but I do get regular key press
>> events:
>> KeyPress event, serial 30, synthetic NO, window 0x4600001,
>>    root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750),
>>    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
>> same_screen YES,
>>    XLookupString gives 0 bytes:
>>    XmbLookupString gives 0 bytes:
>>    XFilterEvent returns: False
>>
>> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>>    root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750),
>>    state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
>> same_screen YES,
>>    XLookupString gives 0 bytes:
>>    XFilterEvent returns: False
>>
>> KeyPress event, serial 33, synthetic NO, window 0x4600001,
>>    root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629),
>>    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
>> same_screen YES,
>>    XLookupString gives 0 bytes:
>>    XmbLookupString gives 0 bytes:
>>    XFilterEvent returns: False
>>
>> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>>    root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629),
>>    state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
>> same_screen YES,
>>    XLookupString gives 0 bytes:
>>    XFilterEvent returns: False
>>
>> I can set these up as hot keys and issue a command, but I have no idea
>> what I can set to adjust the hardware volume. But I will also need to
>> read out the current volume so I know what value to which is should be
>> set. (Same issue as with brightness.)
>> --
>> R. Kevin Oberman, Network Engineer
>> E-mail: [hidden email]
>
>
> You should be able to bind these keys to commands such as mixer vol +5 amd
> mixer vol -5

Actually, to get it to work I had to bind to "/usr/sbin/mixer vol
+5:+5" and "/usr/sbin/mixer vol -5:-5" Just doing +5 set the volume to
5% (absolute) and -5 did nothing. Slightly odd, but I do have it
working, now, t least when Gnome is being used.

Thanks!
--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Kevin Oberman-3]

On Sat, May 26, 2012 at 5:45 AM, Lars Engels <[hidden email]> wrote:

> On Fri, May 25, 2012 at 08:25:47PM -0700, Kevin Oberman wrote:
>> On Wed, May 23, 2012 at 11:55 PM, Lars Engels <[hidden email]> wrote:
>> > On Wed, May 23, 2012 at 03:19:14PM -0700, Kevin Oberman wrote:
>> >> On Wed, May 23, 2012 at 8:13 AM, Natacha Porté <[hidden email]> wrote:
>> >> > Hello,
>> >> >
>> >> > I happen to be the owner of a brand new Lenovo Thinkpad X220. From a
>> >> > recent thread here I gather it almost works with FreeBSD, and the
>> >> > remaining problems are screen brightness and screen left unpowered at
>> >> > resume. Is that right?
>> >> >
>> >> > So my question is, how can I help make progress in any of these area?
>> >> > (though I admit I'm more interested in having the brightness problem
>> >> > solved than the resume one)
>> >> >
>> >> > I don't know anything about ACPI or about FreeBSD or Linux internals,
>> >> > but I'm quite proficient in C and somewhat used to navigate in unknown
>> >> > huge code bases.
>> >> >
>> >> > So I guess the first steps to help would be to first learn stuff.
>> >> >
>> >> > However I don't have much time available. I guess FreeBSD 11 would reach
>> >> > end-of-life before I could reach a level of understanding I find
>> >> > satisfying (though I admit I have high standards there), so I would have
>> >> > to prioritize. So my question is rather *what* should I learn to provide
>> >> > help as soon as possible?
>> >> >
>> >> > For example, if the brightness issue is just a matter of extracting the
>> >> > right numbers from linux kernel code and plug them into FreeBSD, I
>> >> > probably won't need to learn anything more about ACPI than what I would
>> >> > gather looking at the code. I guess if it was that simple someone would
>> >> > have already done it, but that illustrate well my point about
>> >> > prioritizing learning.
>> >> >
>> >> > Or is the barrier of entry too high for me to be of any use?
>> >>
>> >> If it has not been committed, the minor fix to make acpi_ibm work on
>> >> modern ThinkPads needs to be committed. Once done, the issues
>> >> mentioned need to be addressed.This includes getting brightness to be
>> >> setable from both the keypad hot-keys and from applications. ATM, I
>> >> can set the brightness, but making the hot-keys work will require the
>> >> ability to extract the current level so that it may be adjusted
>> >> plus/minus one.
>> >>
>> >> The other issue is volume control keys don't work. I suspect it will
>> >> be similar to brightness, but I don't know just how to figure it out.
>> >>
>> >> I should also mention that I don't have an X220. I have a T520, but
>> >> the issues seem to be identical, so fixing one will probably fix a lot
>> >> of recent ThinkPads.
>> >
>> > About the key:
>> >
>> > Did you try loading "acpi_ibm", "sysctl dev.acpi_ibm.0.events=1",
>> > "cat /var/run/devd.pipe" and then press the keys. Does anything show up?
>>
>> After adding LEN0068 ti the ACPI IDs, I tried this and I get no ACPI
>> event when pressing either button, but I do get regular key press
>> events:
>> KeyPress event, serial 30, synthetic NO, window 0x4600001,
>>     root 0x121, subw 0x0, time 166670035, (96,121), root:(100,750),
>>     state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
>> same_screen YES,
>>     XLookupString gives 0 bytes:
>>     XmbLookupString gives 0 bytes:
>>     XFilterEvent returns: False
>>
>> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>>     root 0x121, subw 0x0, time 166670185, (96,121), root:(100,750),
>>     state 0x0, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),
>> same_screen YES,
>>     XLookupString gives 0 bytes:
>>     XFilterEvent returns: False
>>
>> KeyPress event, serial 33, synthetic NO, window 0x4600001,
>>     root 0x121, subw 0x0, time 166927339, (98,0), root:(102,629),
>>     state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
>> same_screen YES,
>>     XLookupString gives 0 bytes:
>>     XmbLookupString gives 0 bytes:
>>     XFilterEvent returns: False
>>
>> KeyRelease event, serial 33, synthetic NO, window 0x4600001,
>>     root 0x121, subw 0x0, time 166927451, (98,0), root:(102,629),
>>     state 0x0, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
>> same_screen YES,
>>     XLookupString gives 0 bytes:
>>     XFilterEvent returns: False
>
> Hmm, okay, that's not too bad. At least the keys are recognized.
>
>
>>
>> I can set these up as hot keys and issue a command, but I have no idea
>> what I can set to adjust the hardware volume. But I will also need to
>> read out the current volume so I know what value to which is should be
>> set. (Same issue as with brightness.)
>
> Do you have dev.acpi_ibm.0.lcd_brightness and .volume?
>
> If you cou can write a script that raises / lowers the values with
> sysctl.

Unfortunately newer Lenovo systems no longer play correctly with the
acpi_ibm module. Some things do work, but brightness, volume, and fan
speed control don't use the same ACPI methods as older units.
Brightness now uses /VBRC instead of /_BCL and can be accessed via the
call_acpi port do do raw ACPI operations.

See http://lists.freebsd.org/pipermail/freebsd-current/2012-March/032511.html

Of course, you need to add LEN0068 to the list of IDs to get acpi_ibm
to work at all. Guess I need to open a PR to get this "fix" added, but
the proper one would be to fork off acpi_lenovo to use the ACPI
methods now used by ThinkPads. (I wonder if the ID is the only things
needed to detect the switch?)

--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Natacha Porté]

Hello,

on Wednesday 23 May 2012 at 10:05, Любомир Григоров wrote:
> Well, brightness works with the command line, sooo.... I think it has to be
> mapped to the hardware keys. There is a long thread where I discussed this
> with a couple other members (toward the bottom for the recent brightness
> discussion).
> http://comments.gmane.org/gmane.os.freebsd.current/135827

Thanks a lot for pointing this discussion, I found there information
more up-to-date than what I previously found.

In particular, according to what I understand from
http://marc.info/?l=freebsd-current&m=133341372825281&w=2
helping with the brightness seems to require a quite broad understanding
of ACPI and/or EC, and maybe also a good overview of how things work
currently in FreeBSD. Both of these seem to be far beyond anything that
I can reach in a reasonable amount of time :-(

Still, my offer stands, and if anybody can think of anything useful I
can do or learn, please don't hesitate to tell me so.

> Good news is that Konstantin's latest patch works with FreeBSD 9-STABLE so
> no longer need to run HEAD. I would love to see resume work, though.

I'm not sure whether this is the right place to ask for such help, but I
haven't been able to get it working as much as I would like.

More specifically, I checked out 9-STABLE, and merged all 14 commits
listed at the end of http://wiki.freebsd.org/Intel_GPU
I then added WITH_NEW_XORG="YES" and WITH_KMS="YES" to /etc/make.conf
and compiled x11/xorg metaport with default options, except for
KMS=on for graphics/libdrm.

It seems that adding i915kms in /boot/loader.conf freezes the system,
but that's only a minor inconvenience. Now I kldload it just before
starting slim.

The screen resolution is correctly detected, everything in Xorg.0.log
and `dmesg` looks fine, DRI2 is enabled, xdriinfo reports i915 dri
activated for the screen. Well, all in all, as far as I can tell
everything is fine, except I don't see any acceleration : it takes up to
a whole second for my rxvt-unicode to refresh its 80x56 window (whether
scrolling or switching tmux window, and no image background is set),
opaque window moving is very jumpy (but I can live without it), and
armagetron runs at 7-12 fps (to test whether 3D acceleration fared
better than 2D acceleration).

Do you see the same behavior? Would you have any idea on how to diagnose
whatever could be wrong?



Thanks for your help,
Natacha Porté
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Lars Engels-2]

Am 29.05.2012 11:38, schrieb Natacha Porté:

> Hello,
>
> on Wednesday 23 May 2012 at 10:05, Любомир Григоров wrote:
>> Well, brightness works with the command line, sooo.... I think it
>> has to be
>> mapped to the hardware keys. There is a long thread where I
>> discussed this
>> with a couple other members (toward the bottom for the recent
>> brightness
>> discussion).
>> http://comments.gmane.org/gmane.os.freebsd.current/135827
>
> Thanks a lot for pointing this discussion, I found there information
> more up-to-date than what I previously found.
>
> In particular, according to what I understand from
> http://marc.info/?l=freebsd-current&m=133341372825281&w=2
> helping with the brightness seems to require a quite broad
> understanding
> of ACPI and/or EC, and maybe also a good overview of how things work
> currently in FreeBSD. Both of these seem to be far beyond anything
> that
> I can reach in a reasonable amount of time :-(

Oh, what I forgot:
Have you tried x11/xbacklight? You should be able to in- and decrease
the
screen's brightness with it.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Kevin Oberman-3]

On Tue, May 29, 2012 at 2:38 AM, Natacha Porté <[hidden email]> wrote:

> Hello,
>
> on Wednesday 23 May 2012 at 10:05, Любомир Григоров wrote:
>> Well, brightness works with the command line, sooo.... I think it has to be
>> mapped to the hardware keys. There is a long thread where I discussed this
>> with a couple other members (toward the bottom for the recent brightness
>> discussion).
>> http://comments.gmane.org/gmane.os.freebsd.current/135827
>
> Thanks a lot for pointing this discussion, I found there information
> more up-to-date than what I previously found.
>
> In particular, according to what I understand from
> http://marc.info/?l=freebsd-current&m=133341372825281&w=2
> helping with the brightness seems to require a quite broad understanding
> of ACPI and/or EC, and maybe also a good overview of how things work
> currently in FreeBSD. Both of these seem to be far beyond anything that
> I can reach in a reasonable amount of time :-(
>
> Still, my offer stands, and if anybody can think of anything useful I
> can do or learn, please don't hesitate to tell me so.
>
>> Good news is that Konstantin's latest patch works with FreeBSD 9-STABLE so
>> no longer need to run HEAD. I would love to see resume work, though.
>
> I'm not sure whether this is the right place to ask for such help, but I
> haven't been able to get it working as much as I would like.
>
> More specifically, I checked out 9-STABLE, and merged all 14 commits
> listed at the end of http://wiki.freebsd.org/Intel_GPU
> I then added WITH_NEW_XORG="YES" and WITH_KMS="YES" to /etc/make.conf
> and compiled x11/xorg metaport with default options, except for
> KMS=on for graphics/libdrm.
>
> It seems that adding i915kms in /boot/loader.conf freezes the system,
> but that's only a minor inconvenience. Now I kldload it just before
> starting slim.
>
> The screen resolution is correctly detected, everything in Xorg.0.log
> and `dmesg` looks fine, DRI2 is enabled, xdriinfo reports i915 dri
> activated for the screen. Well, all in all, as far as I can tell
> everything is fine, except I don't see any acceleration : it takes up to
> a whole second for my rxvt-unicode to refresh its 80x56 window (whether
> scrolling or switching tmux window, and no image background is set),
> opaque window moving is very jumpy (but I can live without it), and
> armagetron runs at 7-12 fps (to test whether 3D acceleration fared
> better than 2D acceleration).
>
> Do you see the same behavior? Would you have any idea on how to diagnose
> whatever could be wrong?

Have you applied the kernel patches? Installing the new Xorg stuff
after building them with the two lines added to make.conf. only builds
the tools to send the appropriate requests to the kernel, but, without
the patches, the kernel does not know how to deal with them.

The required kernel changes have been committed to HEAD,but not to
9-Stable, so y0ou still need to manually apply these.
--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Natacha Porté]

Hello,

on Tuesday 29 May 2012 at 18:18, Kevin Oberman wrote:
> > Do you see the same behavior? Would you have any idea on how to diagnose
> > whatever could be wrong?
>
> Have you applied the kernel patches?

Yes, I think so, that's what I meant when I wrote:

> On Tue, May 29, 2012 at 2:38 AM, Natacha Porté <[hidden email]> wrote:
> > More specifically, I checked out 9-STABLE, and merged all 14 commits
> > listed at the end of http://wiki.freebsd.org/Intel_GPU

More specifically, here is the sequence of commands I used, extracted
from my shell history:

mkdir STABLE
cd STABLE
svn co svn://svn.freebsd.org/base/stable/9
cd 9/sys
svn merge -c 235356,235359,235362,235365,235366,235372,235375,235776,235782,235783,235846,235847,235859,235925 svn://svn.freebsd.org/base/head/sys
cd ..
vim sys/dev/acpi_support/acpi_ibm.c     # adding "LEN0068"
make buildworld buildkernel
make installworld installkernel
mergemaster -FUi
shutdown -r now

The list of revisions to merge is taken directly from
http://wiki.freebsd.org/Intel_GPU where the patch used to be.
There was only one reported merge conflict, caused by a line a context
from CURRENT that didn't exist in STABLE, but since it was only adding
declaration lines, it was trivially solved.

Now maybe I'm missing some code, maybe I made a mistake copying the
revision numbers (I've only checked them 3 times, but found no mismatch),
maybe the wiki page is wrong. That's why I'm publicly asking for help,
at least for diagnosis.

Or maybe I made no mistake and intel integrated GPU is just that bad
(though performance in Windows does not really hint that way).


Thanks for your help,
Natacha
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Любомир Григоров]

Natacha, have a look at this thread, esp. instructions by Toto:
http://forums.freebsd.org/showthread.php?t=21852&page=5

It worked for me. See also my notes on the next page regarding the latest
patch (only once you have a working STABLE with patch):

update source via csup (same file)
apply patch, remove .rej's
make -j8 buildworld && make installworld
reboot

In either case if you messed up too much I recommend a clean install.
Follow Toto's instructions.

Cheers.

--
Lyubomir Grigorov (bgalakazam)
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Natacha Porté]

Hello,

on Wednesday 30 May 2012 at 01:07, Любомир Григоров wrote:
> Natacha, have a look at this thread, esp. instructions by Toto:
> http://forums.freebsd.org/showthread.php?t=21852&page=5

That's actually what I followed, except with merging from current
instead of using external patches.

> In either case if you messed up too much I recommend a clean install.
> Follow Toto's instructions.

That turned out to be the solution. I don't know exactly what was wrong,
but it was somewhere in X: I deleted /usr/local /var/db/ports and
/var/db/pkg and restarted from scratch, and since then video
acceleration.


I still have a few ACPI-related (I think) issues. For each of them,
would you please tell me which ones are supposed to work (and I'm doing
something wrong) and which ones are known not to work (and I'll try to
figure out a solution)?

  *  power button doesn't work: I'm used (on desktops too) to have ACPI
somehow make it so that pressing the power button triggers a clean
system shutdown, but it's not the case on my X220. Pressing the power
button for several seconds does trigger a hard power off, but that's not
what I'm interested in.

  *  "Fn" key is registered as a sleep button: it is interpreted as
XF86Sleep (keycode 150), but even when unbound in X it still triggers a
suspend when pressed for a few seconds. Unintended suspends (e.g. when
missing Ctrl key) are already uncomfortable by themselves, but they are
made even worse by the nonfunctional resume.
     However, when I change sysctl hw.acpi.sleep_button_state to S5
(as a workaround for nonfunctional power button), "Fn" alone has no
longer any effect other than sending XF86Sleep to X, and "Fn"+F4
correctly shuts down the system.

  *  Disk led is never on, even when there is heavy disk activity.
That's a very minor annoyance, but it would still be nice to see it
solved.

  *  "Fn"+"Fsomething" keys don't work, except for "Fn"+F4: I would
consider them as functional if they sent some events to X (like
"Fn"+arrows correctly send XF86AudioPlay, XF86AudioPrev, XF86AudioNext
and XF86AudioStop) or if they were acted upon directly (like "Fn"+PgUp
correctly switches the ThinkLight).

  *  There is no way of selecting a pointing device. That's why I looked
at "Fn"+F8 in the first place, since it's supposed to cycle between
track-point only, touchpad only and both. Usually I'm fine with what I
select from the BIOS, but there has been several times when I wished I
could switch without rebooting. Ideally that would be hooked directly on
"Fn"+F8 and/or through a sysctl, though having it through acpi_call
would already be helpful for me.

  *  The sysctl dev.acpi_ibm.0.wlan is read-only and always 1, no matter
what the position of the physical radio switch is.

  *  Something seems wrong with beeps (system bell): the first beep
after booting sounds normal, but the following ones seem much faster
(higher pitch and shorter), as if the sampling rate was suddenly much
higher.



Thanks for your help,
Natacha Porté
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Erich Dollansky-2]

Hi,

On Tuesday 26 June 2012 16:32:18 Natacha Porté wrote:

I have also an X220. My experience differs a bit.

The machine:

FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Thu Jun 21 14:29:15 WIT 2012

>   *  power button doesn't work: I'm used (on desktops too) to have ACPI
> somehow make it so that pressing the power button triggers a clean
> system shutdown, but it's not the case on my X220. Pressing the power
> button for several seconds does trigger a hard power off, but that's not
> what I'm interested in.
>
Both behaviours work. When I press the power button shortly, the machine shuts down. When I keep it pressed for a few seconds, the power is switched off.

>   *  Disk led is never on, even when there is heavy disk activity.
> That's a very minor annoyance, but it would still be nice to see it
> solved.
>
Disk led works as expected.

>   *  "Fn"+"Fsomething" keys don't work, except for "Fn"+F4: I would
> consider them as functional if they sent some events to X (like
> "Fn"+arrows correctly send XF86AudioPlay, XF86AudioPrev, XF86AudioNext
> and XF86AudioStop) or if they were acted upon directly (like "Fn"+PgUp
> correctly switches the ThinkLight).

The light seems to be switched by the hardware or BIOS  as it generates no event.

The keys for display brightness up and down also do not generate an event on my machine.
>
>   *  Something seems wrong with beeps (system bell): the first beep
> after booting sounds normal, but the following ones seem much faster
> (higher pitch and shorter), as if the sampling rate was suddenly much
> higher.

I did not notice this.

Erich
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Natacha Porté]

Hello,

on Wednesday 27 June 2012 at 07:38, Erich Dollansky wrote:
> I have also an X220. My experience differs a bit.

Would you have any idea about why you see a better behavior?

I'm using a 9-STABLE with only "LEN0086" addition and Intel_GPU patches
form CURRENT. Could it be caused by new developments in CURRENT? Or have
you modified or configured something?

Would you have any idea on what can be done to further diagnose such
differences in behavior?


For the reference, in case it might help, here are some relevant sysctl:
$ sysctl hw.acpi
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: NONE
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 1
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.thermal.min_runtime: 0
hw.acpi.thermal.polling_rate: 10
hw.acpi.thermal.user_override: 0
hw.acpi.thermal.tz0.temperature: 55.0C
hw.acpi.thermal.tz0.active: -1
hw.acpi.thermal.tz0.passive_cooling: 0
hw.acpi.thermal.tz0.thermal_flags: 0
hw.acpi.thermal.tz0._PSV: -1
hw.acpi.thermal.tz0._HOT: -1
hw.acpi.thermal.tz0._CRT: 99.0C
hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
hw.acpi.thermal.tz0._TC1: -1
hw.acpi.thermal.tz0._TC2: -1
hw.acpi.thermal.tz0._TSP: -1
hw.acpi.battery.life: -1
hw.acpi.battery.time: -1
hw.acpi.battery.state: 7
hw.acpi.battery.units: 1
hw.acpi.battery.info_expire: 5
hw.acpi.acline: 1
$ sysctl dev.acpi_ibm
dev.acpi_ibm.0.%desc: IBM ThinkPad ACPI Extras
dev.acpi_ibm.0.%driver: acpi_ibm
dev.acpi_ibm.0.%location: handle=\_SB_.PCI0.LPC_.EC__.HKEY
dev.acpi_ibm.0.%pnpinfo: _HID=LEN0068 _UID=0
dev.acpi_ibm.0.%parent: acpi0
dev.acpi_ibm.0.initialmask: 2060
dev.acpi_ibm.0.availmask: 134217727
dev.acpi_ibm.0.events: 0
dev.acpi_ibm.0.eventmask: 2060
dev.acpi_ibm.0.hotkey: 1144
dev.acpi_ibm.0.lcd_brightness: 0
dev.acpi_ibm.0.volume: 0
dev.acpi_ibm.0.mute: 0
dev.acpi_ibm.0.thinklight: 0
dev.acpi_ibm.0.bluetooth: 0
dev.acpi_ibm.0.wlan: 1
dev.acpi_ibm.0.fan_speed: 2929
dev.acpi_ibm.0.fan_level: 0
dev.acpi_ibm.0.fan: 1



Thanks for your help,
Natacha Porté
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"

[Erich Dollansky-2]

Hi,

sorry for the late reply. As usual, I have had to travel and did not get a chance to connect to the Internet.

On Thursday, June 28, 2012 05:08:57 PM Natacha Porté wrote:

> Hello,
>
> on Wednesday 27 June 2012 at 07:38, Erich Dollansky wrote:
> > I have also an X220. My experience differs a bit.
>
> Would you have any idea about why you see a better behavior?
>
> I'm using a 9-STABLE with only "LEN0086" addition and Intel_GPU patches
> form CURRENT. Could it be caused by new developments in CURRENT? Or have
> you modified or configured something?
>

let me tell you my experience. I have had a horrible experience with 9. I mean, horrible compared to what I normally experience with FreeBSD. I simply did not get it working at all. As I needed the machine, I installed Fedora 16. At least it worked. I was most happy when I could install FreeBSD 10 and it worked after I did not need that machine that urgent for work anymore.

> Would you have any idea on what can be done to further diagnose such
> differences in behavior?
>
>
> For the reference, in case it might help, here are some relevant sysctl:
> $ sysctl hw.acpi

Let me compare;

> hw.acpi.battery.life: -1

How did you get this value? No battery inserted? The range should be from 0 to 100.

> hw.acpi.battery.time: -1
> hw.acpi.battery.state: 7

I have 0 here.

> hw.acpi.acline: 1

Mine runs currently also on AC.

> $ sysctl dev.acpi_ibm

I do not have anything with IBM or Lenovo.

I also did not load anything specific for the X220 except of the Intel KMS module.

Erich
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[hidden email]"