6920 works in 32 bit ubuntu 10.04 not in 64 bit 10.04

[thelamer]

I have 2 identical systems with identical drivers built. On the 32 bit the tuner is working;

Code: Select All Code

scan -c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
WARNING: filter timeout pid 0x0011
dumping lists (2 services)
[0001]                   (0x0001) 00: PCR == V   V 0x01f5 A 0x1f41 (eng)
[0002]                   (0x0002) 00: PCR 0x1fff   

On 64 bit;

Code: Select All Code

scan -c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
dumping lists (0 services)
Done.


Dmesg for these devices is identical and all the scanning programs I call upon seem to be able to hit the api they are just not able to lock. Just to test I swapped the hard drives in these systems to rule out system failure or RF issues and the 32 bit drive works in the 64 bit build.

What command line arguments can I use to test these streams ? These are coming out of an ip enscapsulator with the following settings;

Frequency 1259000
FEC 2/3
SymbolRate 13205000
Modulation psk8
Rolloff 0.20

[thelamer]

Update I figures out how to test lock from the command line;

WIth 32 bit I get lock with szap:

Code: Select All Code

szap -n 1
reading channels from file '/root/.szap/channels.conf'
zapping to 1 '[0001]':
sat 0, frequency = 0 MHz H, symbolrate 0, vpid = 0x01f5, apid = 0x1f41 sid = 0x0001
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_SET_FRONTEND failed: Invalid argument
status 1f | signal 0026 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0025 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0025 | snr 00d0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK


While in 64 bit:

Code: Select All Code

szap -n 1
reading channels from file '/root/.szap/channels.conf'
zapping to 1 '[0001]':
sat 0, frequency = 0 MHz H, symbolrate 0, vpid = 0x01f5, apid = 0x1f41 sid = 0x0001
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_SET_FRONTEND failed: Invalid argument
status 00 | signal 0046 | snr 0000 | ber 00000000 | unc 00000000 |
status 00 | signal 0046 | snr 0000 | ber 00000000 | unc 00000000 |


Again I want to emphasize that if I swap the hard drives I get the same result. It cannot be RF or hardware.