[mythtvnz] Quality & Damage Question
Steven Mulvay
steven.mulvay at slingshot.co.nz
Fri Sep 5 11:33:43 BST 2008
Hi All,
As I stated in my previous email I have solved the problem of the frame
skipping. However, I have still got a couple of issues to sort out.
The other day I installed a utility called lm-sensors, in order to get
the readout of my cpu temperature. I ran the command sensors-detect .
It found my TV card and was asking if I wanted to scan it to see if it
was a temperature sensor. I interpreted this differently and thought it
was asking whether I wanted the program to see how hot the TV card was
running, so I foolishly said yes. Even more irresponsibly I did not
check to see whether the TV card had stopped recording before I started
the scan with sensors-detect, I suspect it was recording as it was
around the time of a comedy show I had set it to record. After the
scan, realising the mistakes I had made, I decided to test the card by
running watch TV in mythtv (the recording had finished by this stage).
When I pressed watch tv I was just returned to the main menu without
anything happening. When I pressed it again a few moments later, it
seemed to work. My question is, whether you think getting lm sensors to
scan the tv card while it was recording could have damaged the tv card
in any way? The card appears to work all right, but I don't know if
there could be subtle quality differences caused by damage. The output
of the sensors-detect is pasted below, I answered the default
capitalised answer to all the questions in the script:
root at griffen-myth:~# sensors-detect
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801H ICH8
We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
Module loaded successfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: ivtv i2c driver #0 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x1b
Handled by driver `wm8775' (already loaded), chip type `wm8775'
(note: this is probably NOT a sensor chip!)
Client found at address 0x43
Handled by driver `tuner' (already loaded), chip type `tda9887'
(note: this is probably NOT a sensor chip!)
Client found at address 0x44
Handled by driver `cx25840' (already loaded), chip type `cx25840'
(note: this is probably NOT a sensor chip!)
Client found at address 0x50
Handled by driver `tveeprom' (already loaded), chip type `tveeprom'
(note: this is probably NOT a sensor chip!)
Client found at address 0x70
Probing for `Philips Semiconductors PCA9540'... Success!
(confidence 1, driver `pca9540')
Client found at address 0x73
Probing for `FSC Poseidon II'... No
Probing for `FSC Heimdal'... No
Probing for `FSC Heracles'... No
Probing for `FSC Poseidon I'... No
Probing for `FSC Hermes'... No
Probing for `FSC Scylla'... No
Next adapter: SMBus I801 adapter at 0500 (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8718F Super IO Sensors' Success!
(address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `pca9540' (should be inserted):
Detects correctly:
* Bus `ivtv i2c driver #0'
Busdriver `UNKNOWN', I2C address 0x70
Chip `Philips Semiconductors PCA9540' (confidence: 1)
Driver `it87' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `ITE IT8718F Super IO Sensors' (confidence: 9)
Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
To load everything that is needed, add this to /etc/modules:
#----cut here----
# I2C adapter drivers
# modprobe unknown adapter ivtv i2c driver #0
# Chip drivers
# Warning: the required module pca9540 is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
pca9540
it87
coretemp
#----cut here----
Do you want to add these lines automatically? (yes/NO)
root at griffen-myth:~#
Note that even after I answered yes to the modules being inserted
automatically, for some reason I don't think any changes were written to
/etc/modules. This could be a good thing because it means that the tv
card isn't being treated as a temperature sensor by lm-sensors and was
only scanned once by the sensors-detect command.
A copy of /etc/modules is pasted below:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
fuse
lp
rtc
One of the reasons why I wonder whether the TV card is damaged with
diminished quality is that when a tv station puts a banner on screen,
such as the tv one logo with the program name after the ads, there
appears a shakiness about it. Also when I change channels and the OSD
pops up with the program information, the OSD also appears shaky
sometimes. Is this normal? Also occasionally the sceen goes blocky for
half a second, is this normal?
These are monor issues and if they are normal I am not too worried
about them. I just want to make sure that I did not damage my TV card
through foolish mistakes.
Cheers,
Steve :)
More information about the mythtvnz
mailing list