saa7134 doesn't work after warm-reboot
My brothers mythTV setup currently consists of one MBE with 2x DVB-T tuners in.
Both tuners are from identical Medion PCs and report the following from dmesg when booted...
mythtv-user@mythBE1:~$ dmesg | grep -i dvb [ 62.626167] saa7134[0] Board has DVB-T [ 63.405856] saa7134[1] Board has DVB-T [ 63.933725] DVB: registering new adapter (saa7134[0]) [ 63.933729] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... [ 66.281192] DVB: registering new adapter (saa7134[1]) [ 66.281197] DVB: registering frontend 1 (Philips TDA10046H DVB-T)...
My brother lives in an area that suffers very short power-outages if there is a storm or whatever and I have noticed that after such an event, he loses the ability to record TV from both tuners and generally only one will work. I am never sure if it is always the same tuner that as busted since I don't know which is dvb0 or dvb1 at any point in time.
To correct this, I remote into the server and issue a 'halt', get him to unplug it from the wall then press the power button on the front of the machine, re-plug it into the wall and boot up the server. Then both tuners are working fine.
I understand the best way around this might be a UPS, but I don't have the ability to get one at the moment, though it will be his next purchase.
In the meantime I was wandering if anyone had any suggestions for getting around this problem. For my tuners that used to suffer a similar problem (but which are different tuners) I had to add some lines to rc.local to remove the dvb modules and then re-insert them and this seemed to work. There are a number of similar posts in the archives like this. I have tried this for the saa7134 modules but to no avail.
The following output is for reference:
mythtv-user@mythBE1:~$ lsmod | grep -i saa saa7134_dvb 21516 0 videobuf_dvb 7812 1 saa7134_dvb dvb_core 80636 2 saa7134_dvb,videobuf_dvb saa7134 143828 1 saa7134_dvb videodev 35072 2 saa7134,tuner compat_ioctl32 2304 1 saa7134 v4l2_common 12672 2 saa7134,tuner videobuf_dma_sg 14980 2 saa7134_dvb,saa7134 videobuf_core 19716 3 videobuf_dvb,saa7134,videobuf_dma_sg ir_kbd_i2c 11152 1 saa7134 ir_common 40580 2 saa7134,ir_kbd_i2c tveeprom 13444 1 saa7134 i2c_core 24832 12 saa7134_dvb,saa7134,tda1004x,tuner_simple,tda9887,tda8290,tuner,v4l2_common,ir_kbd_i2c,tveeprom,i2c_i810,i2c_algo_bit mythtv-user@mythBE1:~$
mythtv-user@mythBE1:~$ cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing.
/sbin/rmmod saa7134_dvb saa7134 videobuf_dvb dvb_core
/sbin/modprobe saa7134_dvb
exit 0
mythtv-user@mythBE1:~$
The machine is a Pentium 4 running Ubuntu Hardy:
mythtv-user@mythBE1:~$ uname -r 2.6.24-24-generic mythtv-user@mythBE1:~$
mythtv-user@mythBE1:~$ modinfo saa7134_dvb filename: /lib/modules/2.6.24-24-generic/updates/dkms/saa7134-dvb.ko license: GPL author: Gerd Knorr <[email protected]> [SuSE Labs] srcversion: C8C85F1BA098BDF283F1975 depends: saa7134,dvb-core,videobuf-dvb,videobuf-dma-sg,i2c-core vermagic: 2.6.24-24-generic SMP mod_unload 586 parm: antenna_pwr:enable antenna power (Pinnacle 300i) (int) parm: use_frontend:for cards with multiple frontends (0: terrestrial, 1: satellite) (int) parm: debug:Turn on/off module debugging (default:off). (int) parm: adapter_nr:DVB adapter numbers (array of short) mythtv-user@mythBE1:~$
Similar bug in launchpad, but no saa7134_also module is loaded for these cards.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/349537
Any help is greatly appreciated.
Regards,
Whytey
Quoted 7 lines · David Whyte
My brother lives in an area that suffers very short power-outages if there is a storm or whatever and I have noticed that after such an event, he loses the ability to record TV from both tuners and generally only one will work. I am never sure if it is always the same tuner that as busted since I don't know which is dvb0 or dvb1 at any point in time.
Quoted 5 lines
To correct this, I remote into the server and issue a 'halt', get him to unplug it from the wall then press the power button on the front of the machine, re-plug it into the wall and boot up the server. Then both tuners are working fine.
Further info, the power outage was for about 10 seconds in the latest incident. Also, there is no need to unplug the PC power from the wall and press the power button etc to recover, you just need to leave the machine powered down for a short while.
Sounds a lot like the issues I have read about where the firmware remains in the tuner card but is corrupt or something. The only way is to clear the firmware and re-upload it, generally by powering down for sometime but I am hoping that you can do this by unloading then loading the modules.
Is this possible? Anyone know which modules in this instance?
Regards,
Whytey
I've seen computer act strangely after such short power outage ( especially when that outage take a few ms ). Usually, the culprit is a low quality power supply, and i solve it by using a better quality one plus a surge protector (when i can't convice to buy a small UPS, at least :) ).
Beyond that suggestion i can't help you.
Quoted 21 lines · David Whyte
Further info, the power outage was for about 10 seconds in the latest incident. Also, there is no need to unplug the PC power from the wall and press the power button etc to recover, you just need to leave the machine powered down for a short while.
Sounds a lot like the issues I have read about where the firmware remains in the tuner card but is corrupt or something. The only way is to clear the firmware and re-upload it, generally by powering down for sometime but I am hoping that you can do this by unloading then loading the modules.
Is this possible? Anyone know which modules in this instance?
Regards,
Whytey
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html