Re: Xorg and thinkpad x200s

[Pau <vim.unix%googlemail.com@localhost>]

"remote management" ... I didn't have any idea of what this was...

http://www.intel.com/design/servers/ism/rmm.htm

"creeping featuritis", the fatal disease of software

I will happily turn it off in the bios, if I can...

Thanks

2010/1/11 Gary Duzan <gary%duzan.org@localhost>:
> In Message 
> <30c383e71001110521m50a524f3tc7e7b9154108116c%mail.gmail.com@localhost>,
>   Pau <vim.unix%googlemail.com@localhost>wrote:
>
> =>Hello Steven,
> =>
> =>this is NetBSD -current
> =>
> =>I will try the other value tonight (am at work now)
> =>
> =>Thanks a lot
> =>
> =>Pau
>
>   Another thing you can try is turning off remote management in
> the BIOS. It looks like the Intel Management Engine is claiming to
> be an IDE device, and we don't have a specific driver for that
> specific IDE "controller", so you get the generic pciide one, which
> doesn't have power management support. If the management function
> can be disabled in the BIOS, the device should go away, and the OS
> doesn't have to worry about powering it down.
>
>   Otherwise, it seems we'd need a driver for the device in section
> 23.3 of this document:
>
>        http://www.intel.com/Assets/PDF/datasheet/320122.pdf
>
> It might we worth it to try matching it as a PIIX IDE or SATA
> controller.
>
>   Good luck.
>
>                                        Gary Duzan
>
>
>
> =>2010/1/11 Steven Bellovin <smb%cs.columbia.edu@localhost>:
> =>>
> =>> On Jan 11, 2010, at 7:16 AM, Pau wrote:
> =>>
> =>>> Hello,
> =>>>
> =>>> the bios was already on AHCI...
> =>>
> =>> What are the other values? =A0Have you tried one of them?
> =>>>
> =>>> That's really bad. I am looking forward to using NetBSD on this laptop
> =>>> for my production system, and this is a "feature" I would really need.
> =>>>
> =>>> Look at this:
> =>>>
> =>>> # sysctl hw.acpi.supported_states
> =>>> hw.acpi.supported_states =3D S0 S3 S4 S5
> =>>>
> =>>> # dmesg | grep pciide0
> =>>> pciide0 at pci0 dev 3 function 2: vendor 0x8086 product 0x2a46 (rev. 0x0=
> =>7)
> =>>> pciide0: bus-master DMA support present, but unused (no driver support)
> =>>> pciide0: primary channel wired to native-PCI mode
> =>>> pciide0: using ioapic0 pin 18 for native-PCI interrupt
> =>>> atabus0 at pciide0 channel 0
> =>>> pciide0: secondary channel wired to native-PCI mode
> =>>> atabus1 at pciide0 channel 1
> =>>> Devices without power management support: pciide0
> =>>>
> =>>
> =>> The problem is very local: one specific driver (pciide, which is used to =
> =>attach the bus to the PCI bus, doesn't support suspsend/resume. =A0If you u=
> =>se a different disk interface, it may select a different driver.
> =>>
> =>> Beyond that -- someone who knows that driver would have to add power mana=
> =>gement support. =A0It's probably just a matter of saving and restoring a fe=
> =>w registers, but past that I don't know; I've never looked at that driver a=
> =>nd have no knowledge of the device.
> =>>
> =>> The only other thing to do is to try a -current kernel, but I don't even =
> =>know if anyone has been working on it.
> =>>
> =>>
> =>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0--Steve Bellovin, http://www.cs.columbia.e=
> =>du/~smb
> =>>
> =>>
> =>>
> =>>
> =>>
> =>>
>