mt352 no more working after suspend to disk
Hi,
if I suspend to disk and next resume I have to manually remove and reload my mt352 driver, otherwise it complains of a lot of i2c errors.
My kernel is suse's 2.6.27.
Is this problem fixed in recent kernels or in hg?
Thanks,
Nico
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi Nico,
Am Montag, den 09.02.2009, 12:33 +0100 schrieb Nico Sabbi:
Quoted 5 lines
Hi,
if I suspend to disk and next resume I have to manually remove and reload my mt352 driver, otherwise it complains of a lot of i2c errors.
Quoted 7 lines
My kernel is suse's 2.6.27.
Is this problem fixed in recent kernels or in hg?
Thanks,
Nico
don't know on what driver you report it, but since I know you also have saa7134 driver devices, nobody claimed so far that dvb is suspend/resume safe.
I recently reported that people have to stay aware after resume, that even without using any dvb app actually during suspend, analog needs to be re-initialized first after that to get the tda10046 in a proper state for DVB-T again, at least on hybrid devices. Unshared DVB-S tuners and demods do stand this already. (medion 8800quad, CTX948, Asus 3in1)
You can suspend to RAM on analog for example with a running tvtime and resume, but dma sound on saa7134-alsa is also not handled yet. Analog sound works.
That is the status as far I have it.
Cheers,
Hermann
I've tried to configure my system for suspends and here are my conclusions, maybe it will be helpful:
Make sure no applications are using drivers that generally make problems after suspend, that means you have to stop/kill them before suspending. I use pm-utils script to stop application before suspend and start applications after that.
Make sure you reload the drivers after resume. pm-utils has a feature to unload modules before suspend and reload them after resume automatically, check the SUSPEND_MODULES configuration. That method works fine for my DVB-S drivers, but don't work for my WiFi card, so I had to reload the driver after resume in my script.
Hope it helps.
Quoted 39 lines · hermann pitton
Hi Nico,
Am Montag, den 09.02.2009, 12:33 +0100 schrieb Nico Sabbi:
Quoted 5 lines
Hi,
if I suspend to disk and next resume I have to manually remove and reload my mt352 driver, otherwise it complains of a lot of i2c errors.Quoted 7 lines
My kernel is suse's 2.6.27.
Is this problem fixed in recent kernels or in hg?
Thanks,
Nicodon't know on what driver you report it, but since I know you also have saa7134 driver devices, nobody claimed so far that dvb is suspend/resume safe.
I recently reported that people have to stay aware after resume, that even without using any dvb app actually during suspend, analog needs to be re-initialized first after that to get the tda10046 in a proper state for DVB-T again, at least on hybrid devices. Unshared DVB-S tuners and demods do stand this already. (medion 8800quad, CTX948, Asus 3in1)
You can suspend to RAM on analog for example with a running tvtime and resume, but dma sound on saa7134-alsa is also not handled yet. Analog sound works.
That is the status as far I have it.
Cheers,
Hermann
Quoted 6 lines
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 13 lines · On Tuesday 10 February 2009 13:39:09 Alex Betis wrote:
I've tried to configure my system for suspends and here are my conclusions, maybe it will be helpful:
Make sure no applications are using drivers that generally make problems after suspend, that means you have to stop/kill them before suspending. I use pm-utils script to stop application before suspend and start applications after that.
Make sure you reload the drivers after resume. pm-utils has a feature to unload modules before suspend and reload them after resume automatically, check theSUSPEND_MODULESconfiguration. That method works fine for my DVB-S drivers, but don't work for my WiFi card, so I had to reload the driver after resume in my script.
Quoted 2 lines
Hope it helps.
it's very useful, thanks a lot
Quoted 1 line · On Tuesday 10 February 2009 13:39:09 Alex Betis wrote:
On Tue, Feb 10, 2009 at 12:16 AM, hermann pitton
Quoted 26 lines · <[email protected]>wrote:
Quoted 26 lines
Hi Nico,
Am Montag, den 09.02.2009, 12:33 +0100 schrieb Nico Sabbi:
Quoted 11 lines
Hi,
if I suspend to disk and next resume I have to manually remove and reload my mt352 driver, otherwise it complains of a lot of i2c errors.My kernel is suse's 2.6.27.
Is this problem fixed in recent kernels or in hg?
Thanks,
Nicodon't know on what driver you report it, but since I know you also have saa7134 driver devices, nobody claimed so far that dvb is suspend/resume safe.
I recently reported that people have to stay aware after resume, that even without using any dvb app actually during suspend, analog needs to be re-initialized first after that to get the tda10046 in a proper state for DVB-T again, at least on hybrid devices. Unshared DVB-S tuners and demods do stand this already. (medion 8800quad, CTX948, Asus 3in1)
Quoted 6 lines
Quoted 6 lines
You can suspend to RAM on analog for example with a running tvtime and resume, but dma sound on saa7134-alsa is also not handled yet. Analog sound works.
That is the status as far I have it.
Hi Hermann,
the only card that gave me problems so was is my Airstar2 PCI card, while my Lifeview Trio worked perfectly after resume
Am Dienstag, den 10.02.2009, 15:11 +0100 schrieb Nico Sabbi:
Quoted 33 lines · On Tuesday 10 February 2009 13:39:09 Alex Betis wrote:
Quoted 1 line
On Tue, Feb 10, 2009 at 12:16 AM, hermann pitton
Quoted 30 lines · <[email protected]>wrote:
Quoted 30 lines
Hi Nico,
Am Montag, den 09.02.2009, 12:33 +0100 schrieb Nico Sabbi:
Quoted 11 lines
Hi,
if I suspend to disk and next resume I have to manually remove and reload my mt352 driver, otherwise it complains of a lot of i2c errors.My kernel is suse's 2.6.27.
Is this problem fixed in recent kernels or in hg?
Thanks,
Nicodon't know on what driver you report it, but since I know you also have saa7134 driver devices, nobody claimed so far that dvb is suspend/resume safe.
I recently reported that people have to stay aware after resume, that even without using any dvb app actually during suspend, analog needs to be re-initialized first after that to get the tda10046 in a proper state for DVB-T again, at least on hybrid devices. Unshared DVB-S tuners and demods do stand this already. (medion 8800quad, CTX948, Asus 3in1)
You can suspend to RAM on analog for example with a running tvtime and resume, but dma sound on saa7134-alsa is also not handled yet. Analog sound works.
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines
That is the status as far I have it.
Hi Hermann,
the only card that gave me problems so was is my Airstar2 PCI card, while my Lifeview Trio worked perfectly after resume
Nico, Alex, thanks.
Fine so far then without a running DVB-S app.
That we don't get trouble with those maybe building high end linux media machines currently, status for me for the other reception methods is as announced above :)
Cheers,
Hermann