Sorry for being inconcise yesterday - I was kind of in a hurry...
Details:
Suspending with the sleep.sh script works but breaks the network-connections after resume (as I suppose it should...) while everything else seems to resume fine. Suspend over HAL via pm-suspend does work as well as does resuming (with working network).
Hardware: Radeon Mobility x1600 (in a LG S1 Dual Pro)
Kernel: image 2.6.24-12.22 generic, restricted modules 2.6.24.11-12.31 generic, fglrx 7.1.0-8-3+2.6.24-11-12.31
Being no linux-crack, I have a few questions:
1. I assume the "acpi-support" config file in /etc/default is not read/considered by pm-suspend - is that correct?
2. In what way does the gnome-power-manager define what to do at shutdown?
3. Which package/package maintainer would be the correct one to address with this problem, since the kernel itself doesn't seem to be responsible for the breakage?
Sorry for being inconcise yesterday - I was kind of in a hurry...
Details:
Suspending with the sleep.sh script works but breaks the network-connections after resume (as I suppose it should...) while everything else seems to resume fine. Suspend over HAL via pm-suspend does work as well as does resuming (with working network).
Hardware: Radeon Mobility x1600 (in a LG S1 Dual Pro) 3+2.6.24- 11-12.31
Kernel: image 2.6.24-12.22 generic, restricted modules 2.6.24.11-12.31 generic, fglrx 7.1.0-8-
Being no linux-crack, I have a few questions:
1. I assume the "acpi-support" config file in /etc/default is not read/considered by pm-suspend - is that correct?
2. In what way does the gnome-power-manager define what to do at shutdown?
3. Which package/package maintainer would be the correct one to address with this problem, since the kernel itself doesn't seem to be responsible for the breakage?