Re: x220 notes

On Wed, Sep 28, 2011 at 12:25 PM, Matt <sendtomatt_at_gmail.com> wrote:
> On 09/28/11 11:52, Garrett Cooper wrote:
>>
>> On Wed, Sep 28, 2011 at 11:48 AM, Matt<sendtomatt_at_gmail.com>  wrote:
>>>
>>> I just picked up an X220 and have been trying to get FreeBSD running
>>> well.
>>>
>>> Some tips
>>> ichsmb
>>> acpi_video (attaches but doesn't work)
>>> aesni
>>> coretemp
>>>
>>> powerd is a must, these processors seem to be designed to run very hot
>>> unless throttled. Somehow my C3 state disappears when on AC, I think
>>> that's
>>> a bios setting?
>>>
>>> acpi_ibm needs "LEN0068" added to the list of ibm ids at the beginning of
>>> /usr/src/sys/dev/acpi_support/acpi_ibm.c...I'd write a patch but that
>>> machine is in a world of ports hurt right now :).
>>> With this many of the sysctls and leds work, still no brightness (w or
>>> wout
>>> intel DRI from Konstantin...thanks Konstantin!!)
>>>
>>> sleep/resume work, but screen is off after resume and cannot be awakened
>>> (even w/ dpms and or acpi_video).
>>
>> This is probably another driver bug. Try kldunloading and kldloading
>> your wlan driver to see if that works, and/or start stripping your
>> kernel of unnecessary options until you find the magic formula for
>> what works, and just apply that to rc.suspend // rc.resume and file a
>> PR for the driver bug if there isn't one already.
>> HTH,
>> -Garrett
>>
>
> Driver bug in wireless can leave the screen off?
> I can for instance type reboot and reboot etc.
>
> I also noticed that acpi_video attaches, but nothing works. Looking at AML
> it appears that the correct "hooks" are present, but lcd0 shows as inactive
> and does not go to "1" in sysctl.
>
> ibm_acpi lcd_brightness hooks do not work either.
>
> debug.acpi.reset_video does VERY bad things, involving a reboot loop and
> flashing thinklight
>
> Is there anything else I can do to turn the damn thing back on?
> Any other logging or things to look at?
>
> I will try a minimal kernel shortly.

A driver bug in general will bring up a blank screen because the
system doesn't fully resume.

Are you using amd64 or i386?

-Garrett