FAQ & Troubleshooting - Revision history

Bpringle: /* How many devices are supported in a system? */

2010-07-25T22:03:25Z

How many devices are supported in a system?

← Older revision		Revision as of 22:03, 25 July 2010
Line 22:		Line 22:
	In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].		In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].

-	'''Udev''' can be used to maintain a persistent order. ~~The file 'linux/Documentation/dvb/udev.txt' has more information on this, but is still not completely helpful.~~ [http://www.mythtv.org/wiki/Device_Filenames_and_udev MythTv] has extensive information on this.	+	'''Udev''' can be used to maintain a persistent order. [http://www.mythtv.org/wiki/Device_Filenames_and_udev MythTv] has extensive information on this. The simplest way is to use the '''adapter_nr''' option available for most top level DVB modules.

	==Troubleshooting==		==Troubleshooting==

Bpringle: /* How many devices are supported in a system? */

2010-07-25T14:46:07Z

How many devices are supported in a system?

← Older revision		Revision as of 14:46, 25 July 2010
Line 22:		Line 22:
	In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].		In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].

-	'''Udev''' can be used to maintain a persistent order. The file 'linux/Documentation/dvb/udev.txt' has more information on this, but is still not completely helpful.	+	'''Udev''' can be used to maintain a persistent order. The file 'linux/Documentation/dvb/udev.txt' has more information on this, but is still not completely helpful. [http://www.mythtv.org/wiki/Device_Filenames_and_udev MythTv] has extensive information on this.

	==Troubleshooting==		==Troubleshooting==

Bpringle: /* How many devices are supported in a system? */

2010-07-25T14:42:58Z

How many devices are supported in a system?

← Older revision		Revision as of 14:42, 25 July 2010
Line 21:		Line 21:
	In respect to DVB devices, see [http://marc.info/?l=linux-dvb&m=120214129911811&w=2 this thread]. There is also a [http://linuxtv.org/hg/v4l-dvb/rev/496b71d9a1c0 patch] that has been submitted that will allow one to configure the max adapters defined.		In respect to DVB devices, see [http://marc.info/?l=linux-dvb&m=120214129911811&w=2 this thread]. There is also a [http://linuxtv.org/hg/v4l-dvb/rev/496b71d9a1c0 patch] that has been submitted that will allow one to configure the max adapters defined.
	In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].		In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].
		+
		+	'''Udev''' can be used to maintain a persistent order. The file 'linux/Documentation/dvb/udev.txt' has more information on this, but is still not completely helpful.

	==Troubleshooting==		==Troubleshooting==

Devin.heitmueller: Reverted edits by Jamesm113 (Talk) to last version by CityK

2009-09-16T17:02:40Z

Reverted edits by Jamesm113 (Talk) to last version by CityK

← Older revision		Revision as of 17:02, 16 September 2009
Line 14:		Line 14:
	===I have the DVB drivers loaded. Now how can I test it?===		===I have the DVB drivers loaded. Now how can I test it?===
	Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].		Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].
-
-	~~===I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but there is no frontend0 so i can't use scan, whats wrong?===~~
-	?

	===How do I tune my TV-channels? Where do I get the frequencies from?===		===How do I tune my TV-channels? Where do I get the frequencies from?===

Jamesm113: /* I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but no frontend, whats wrong? */

2009-09-15T17:18:43Z

I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but no frontend, whats wrong?

← Older revision		Revision as of 17:18, 15 September 2009
Line 15:		Line 15:
	Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].		Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].

-	===I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but no ~~frontend~~, whats wrong?===	+	===I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but there is no frontend0 so i can't use scan, whats wrong?===
	?		?

Jamesm113: /* General */ added questions

2009-09-15T17:08:34Z

General: added questions

← Older revision		Revision as of 17:08, 15 September 2009
Line 14:		Line 14:
	===I have the DVB drivers loaded. Now how can I test it?===		===I have the DVB drivers loaded. Now how can I test it?===
	Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].		Check if you have files in /dev/dvb/adapter0/. Then, see the steps in [[Testing your DVB device]].
		+
		+	===I have the DVB drivers loaded and I have /dev/dvb/adapter0/ but no frontend, whats wrong?===
		+	?

	===How do I tune my TV-channels? Where do I get the frequencies from?===		===How do I tune my TV-channels? Where do I get the frequencies from?===

CityK: /* How many devices are supported in a system? */ note max adapters patch

2009-09-07T17:16:06Z

How many devices are supported in a system?: note max adapters patch

← Older revision		Revision as of 17:16, 7 September 2009
Line 19:		Line 19:

	===How many devices are supported in a system?===		===How many devices are supported in a system?===
-	In respect to DVB devices, see [http://marc.info/?l=linux-dvb&m=120214129911811&w=2 this thread].	+	In respect to DVB devices, see [http://marc.info/?l=linux-dvb&m=120214129911811&w=2 this thread]. There is also a [http://linuxtv.org/hg/v4l-dvb/rev/496b71d9a1c0 patch] that has been submitted that will allow one to configure the max adapters defined.
	In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].		In respect to analog devices, see [http://marc.info/?l=linux-video&m=119955906907915&w=2 this thread].
-

	==Troubleshooting==		==Troubleshooting==

Dominique: /* S-Video input in black and white */

2009-08-16T10:43:22Z

S-Video input in black and white

← Older revision		Revision as of 10:43, 16 August 2009
Line 46:		Line 46:

	Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB card or the latency value of other PCI cards. Acoustic and image interferences can appear after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.		Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB card or the latency value of other PCI cards. Acoustic and image interferences can appear after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.
		+
		+	=== S-Video input in black and white ===
		+
		+	When you are watching the signal coming through the S-Video input of your card, the picture is in black and white, that even when the source is in colour. This is basically what will append when you are connecting a composite source to a S-Video input. They are relatively expensive box to deal with this on the market, but it is an alternative solution that will work well in most cases. See [[Composite to S-Video]].

Bear97 at 16:59, 5 May 2009

2009-05-05T16:59:13Z

← Older revision		Revision as of 16:59, 5 May 2009
Line 45:		Line 45:
	=== Hardware compatibility issues ===		=== Hardware compatibility issues ===

-	Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB-C card or the latency value of other PCI cards. Acoustic and image interferences can appear after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB-C playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.	+	Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB card or the latency value of other PCI cards. Acoustic and image interferences can appear after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.

Bear97 at 12:46, 5 May 2009

2009-05-05T12:46:26Z

← Older revision		Revision as of 12:46, 5 May 2009
Line 45:		Line 45:
	=== Hardware compatibility issues ===		=== Hardware compatibility issues ===

-	Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB-C card or the latency value of other PCI cards. Acoustic and image interferences can ~~appeared~~ after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB-C playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.	+	Some motherboard chipsets are known for hardware incompatibilities with several PCI cards. Depending on motherboard chipset, BIOS, driver versions and connected PCI cards, it could be necessary to change the PCI latency of the DVB-C card or the latency value of other PCI cards. Acoustic and image interferences can appear after 10 to 30 minutes playback. Kernel error messages like "timed out waiting for end of xfer" can occure in /var/log/syslog when the PCI latency is too low. But there are also acoustic and image interferences possible when the PCI latency is too high. The current PCI latency can be shown via command "lspci -v". The PCI latency value can be set via command setpci (see manual page of setpci, example: setpci -v -s 03:06.0 latency_timer=96 ). The appropriate value depends on the specific hardware configuration. Play around with the value and restart DVB-C playback. Otherwise, you can try to swap PCI cards or a different motherboard with a different chipset.