On Thursday 02 October 2008, Peng Deng wrote:
> Christian, I guess I wouldn't blacklist the driver if I want to use
> the device, plus I am not sure actually which driver to block (the
> device will load several modules). However, I would try to replace it
> with another em28xx-new driver, which seems more reliable, I just need
> time to compile the latter.
>
> No matter if the device is plugged in or not, sudo pm-suspend behaves
> as the same as from the menu item here.
I meant that you blacklist it from suspend[1], which would mean that the
driver is removed prior suspend and then loaded again. If you don't blacklist
it, then the system tries to suspend the device, which can cause problems if
the device and/or the driver do not properly support it. Thus removing it
before suspend and loading it again afterwards can have a different behavior.
[1] e.g. in /etc/pm/config.d/config:
SUSPEND_MODULES="$SUSPEND_MODULES snd_hda_intel"
Hello P.D.
On Thursday 02 October 2008, Peng Deng wrote:
> Christian, I guess I wouldn't blacklist the driver if I want to use
> the device, plus I am not sure actually which driver to block (the
> device will load several modules). However, I would try to replace it
> with another em28xx-new driver, which seems more reliable, I just need
> time to compile the latter.
>
> No matter if the device is plugged in or not, sudo pm-suspend behaves
> as the same as from the menu item here.
I meant that you blacklist it from suspend[1], which would mean that the
driver is removed prior suspend and then loaded again. If you don't blacklist
it, then the system tries to suspend the device, which can cause problems if
the device and/or the driver do not properly support it. Thus removing it
before suspend and loading it again afterwards can have a different behavior.
[1] e.g. in /etc/pm/ config. d/config: MODULES= "$SUSPEND_ MODULES snd_hda_intel"
SUSPEND_
Kind regards,
Christian