Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> Installation/Setup -> 2.6.18-rc4 not working?
Post new topic  This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic 
2.6.18-rc4 not working?
PostPosted: Thu Aug 17, 2006 2:25 pm Reply with quote
iwantmyhdtv
 
Joined: 05 Jan 2005
Posts: 12




Runnung Gentoo with 2.6.18-rc4 x86_64 kernel:

HD5500 card does not work. I'm assuming that the driver is already included in this kernel, since the card appears to be recognized. dmesg output follows. Every time I run getatsc or dtvsignal, more of the "cx88[0]/2: cx8802_timeout" are printed.

I am upgrading from an HD3000 which was working with the cx88-dvb driver so I'm sure all my user space tools are OK.


Linux video capture interface: v2.00
cx2388x dvb driver version 0.0.6 loaded
CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47,autodetected]
TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
tveeprom 4-0050: Huh, no eeprom present (err=-121)?
PCI: Enabling device 0000:01:05.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:01:05.2[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 217
cx88[0]/2: found at 0000:01:05.2, rev: 5, irq: 217, latency: 32, mmio: 0xe8000000
cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)...
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout
cx88[0]/2: cx8802_timeout


lsmod output:

cx88_dvb 13124 0
cx8802 10180 1 cx88_dvb
cx88xx 59044 2 cx88_dvb,cx8802
ir_common 25924 1 cx88xx
btcx_risc 4360 2 cx8802,cx88xx
tveeprom 15248 1 cx88xx
videodev 22784 1 cx88xx
v4l1_compat 11076 1 videodev
v4l2_common 20736 1 videodev
cx88_vp3054_i2c 4800 1 cx88_dvb
mt352 6724 1 cx88_dvb
dvb_pll 13316 1 cx88_dvb
or51132 9476 1 cx88_dvb
video_buf_dvb 4996 1 cx88_dvb
dvb_core 73136 1 video_buf_dvb
video_buf 20740 4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
nxt200x 13252 1 cx88_dvb
firmware_class 8384 2 or51132,nxt200x
isl6421 2368 1 cx88_dvb
zl10353 5316 1 cx88_dvb
cx24123 12104 1 cx88_dvb
lgdt330x 8412 1 cx88_dvb
cx22702 6148 1 cx88_dvb
zd1211 279376 0
ohci1394 28616 0
ieee1394 84536 1 ohci1394
snd_seq_dummy 3332 0
snd_seq_oss 28544 0
snd_seq_midi_event 6592 1 snd_seq_oss
snd_seq 45440 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6996 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 39200 0
snd_mixer_oss 14656 1 snd_pcm_oss
snd_intel8x0 30632 0
snd_ac97_codec 97880 1 snd_intel8x0
snd_ac97_bus 2624 1 snd_ac97_codec
snd_pcm 70348 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 18952 2 snd_seq,snd_pcm
snd 48232 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 7888 2 snd_intel8x0,snd_pcm
View user's profile Send private message
PostPosted: Thu Aug 17, 2006 3:05 pm Reply with quote
iwantmyhdtv
 
Joined: 05 Jan 2005
Posts: 12




Well, I downgraded to 2.6.15 and the drivers from the website. Seems OK now with this combination. But... I need 2.6.18 for other reasons.
View user's profile Send private message
PostPosted: Thu Aug 17, 2006 8:06 pm Reply with quote
iwantmyhdtv
 
Joined: 05 Jan 2005
Posts: 12




Another update:

I am now running a 32 bit 2.6.18-rc4 kernel, and both a 5500 and a 3000 card. dtvsignal works on the 3000, but not the 5500. getatsc works on both, however. The problem seems specific to the signal strenth interface. I'll check later whether this was also the case with the 64 bit kernel.

Here is some output from azap:

azap with 5500:

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 509028615 Hz
video pid 0x0031, audio pid 0x0034
status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 1f | signal 0000 | snr ff6d | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ff91 | ber 00000000 | unc 0000003d | FE_HAS_LOCK
status 1f | signal 0000 | snr ff7a | ber 00000000 | unc 00000000 | FE_HAS_LOCK

azap with 3000:

using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
tuning to 509028615 Hz
video pid 0x0031, audio pid 0x0034
status 00 | signal be76 | snr f9dd | ber 00000000 | unc 00000000 |
status 1f | signal bc28 | snr f99f | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal ba1b | snr f97b | ber 00000000 | unc 00000000 | FE_HAS_LOCK
View user's profile Send private message
PostPosted: Tue Aug 29, 2006 9:25 pm Reply with quote
pcHDTV_tech
 
Joined: 16 Dec 2004
Posts: 295




Due to some differences of opinion in how things should work, the driver code that made it into kernel 2.6.18 doesn't have the signal strength code that the pcHDTV drivers supply. You could patch the code in your kernel by looking at the differences in lgdt330x.c between the kernel code and pcHDTV's driver.

Rusty
View user's profile Send private message Visit poster's website
PostPosted: Wed Aug 30, 2006 2:06 am Reply with quote
xyzzy
 
Joined: 12 Feb 2006
Posts: 225




pcHDTV_tech wrote:
Due to some differences of opinion in how things should work, the driver code that made it into kernel 2.6.18 doesn't have the signal strength code that the pcHDTV drivers supply. You could patch the code in your kernel by looking at the differences in lgdt330x.c between the kernel code and pcHDTV's driver.

Last I heard the problem was lack of a signed-off-by for the patch. Since the whole SCO fiasco this is very important. There is a change to the way the fix-point logarithms are done now, which the code should be ported to. If I had a HD-5500 and LGDT3303 documentation, proper signal strength would most certainly appear in 2.6.19.
View user's profile Send private message
PostPosted: Wed Aug 30, 2006 8:11 am Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




It looks like more than a sign-off issue. The PCHDTV code takes an error rate measurement and converts it to both an SNR dB value and a signal value. The current kernel code takes the same error rate measurement and converts it to an unscaled SNR value and doesn't provide a signal strength value.

Changing to the PCHDTV method wouldn't actually give you any more information at the user level. Quite possibly the chip doesn't provide actual power levels, hence no signal strength indication. It's easier and just as good to change the user code to use SNR, which is likely what you care about anyway.

However, if you want to change the kernel, the new intlog10 code returns log10(x) * 2^24, whereas the old i10log10 code returns log10(x) * 1000. The rest is pretty straightforward.
View user's profile Send private message
Signal strength
PostPosted: Thu Sep 07, 2006 1:57 pm Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




Xyzzy, is there any reason the signal strength can't be obtained from the AGC values of the TUA6034?
View user's profile Send private message
PostPosted: Thu Sep 07, 2006 5:56 pm Reply with quote
xyzzy
 
Joined: 12 Feb 2006
Posts: 225




What AGC values would those be? There is just a one bit flag that tells you if AGC is active or not.
View user's profile Send private message
PostPosted: Fri Sep 08, 2006 7:34 am Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




Nevermind, I read "ADC" as "AGC".
View user's profile Send private message
2.6.18-rc4 not working?
  pcHDTV Forum Index -> Installation/Setup
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 7 Hours  
Page 1 of 1  

  
  
 Post new topic  This topic is locked: you cannot edit posts or make replies.  


Powered by phpBB © 2001-2003 phpBB Group
Theme created by Vjacheslav Trushkin