On Monday 01 September 2008 5:16:44 Tomas Carnecky wrote:
> I just tested suspend/resume with the CDROM drive removed (an empty
> bay). Suspend/resume now works just fine, regardless how I dock/undock
> the laptop.
I'm seeing the exact same things as Tom. Also, in my dmesg I see:
ACPI: \_SB_.PC
On Mon, 01 Sep 2008, Toralf Förster wrote:
> I observed this after running this alias 3 times after I waked up my system
> from suspend-to-ram:
>
> [EMAIL PROTECTED] ~ $ temp
> temperature: 40 C
> temperatures: 40 37 30 41 28 -128 25 -128
> status: enabled
> speed:
On Mon, Sep 01, 2008 at 02:16:44PM +0200, Tomas Carnecky wrote:
> I just tested suspend/resume with the CDROM drive removed (an empty
> bay). Suspend/resume now works just fine, regardless how I dock/undock
> the laptop.
Huh, interesting. We may be doing something wrong with the libata ACPI
call
Henrique de Moraes Holschuh wrote:
> On Mon, 01 Sep 2008, Tomas Carnecky wrote:
>> There is one question though that was never answered: Is there any
>> interaction needed from the userspace when docking/undocking? Something
>
> Yes. umount filesystems on any device in the dock, and issue the "po
On Mon, Sep 01, 2008 at 12:50:36PM +0200, Tomas Carnecky wrote:
> There is one question though that was never answered: Is there any
> interaction needed from the userspace when docking/undocking? Something
> that the acpi daemon would have to do in response to a dock/undock
> event? I'm thinking a
On Mon, 01 Sep 2008, Tomas Carnecky wrote:
> There is one question though that was never answered: Is there any
> interaction needed from the userspace when docking/undocking? Something
Yes. umount filesystems on any device in the dock, and issue the "power off
dock" command (i.e. tell the kernel
