Moderator Control Panel ]

Future of the Linux-Driver

Re: Future of the Linux-Driver

Postby sami8519 » Thu May 12, 2011 5:51 am

Thanks a lot Mike.

Best regards,
Sami
sami8519
 
Posts: 40
Joined: Fri Jun 18, 2010 2:08 pm

Re: Future of the Linux-Driver

Postby stevellion » Thu May 12, 2011 6:30 am

krajok Wrote:I think my problem should be my Ubuntu is amd64 because header of v4l2-compat-ioctl32.c is about 32bit and 64bit conversion.
Tomorrow I will reinstall my OS with Ubuntu x86 (32bit)

/*
* ioctl32.c: Conversion between 32bit and 64bit native ioctls.
* Separated from fs stuff by Arnd Bergmann <arnd@arndb.de>
*
* Copyright (C) 1997-2000 Jakub Jelinek (jakub@redhat.com)
* Copyright (C) 1998 Eddie C. Dost (ecd@skynet.be)
* Copyright (C) 2001,2002 Andi Kleen, SuSE Labs
* Copyright (C) 2003 Pavel Machek (pavel@suse.cz)
* Copyright (C) 2005 Philippe De Muyter (phdm@macqel.be)
* Copyright (C) 2008 Hans Verkuil <hverkuil@xs4all.nl>
*
* These routines maintain argument size conversion between 32bit and 64bit
* ioctls.
*/


I had this issue too (Kubuntu 64-bit) - I've replaced the v4l2-compat-ioctl32.c with this one that I found with google.
It seems as though this file is a fairly standard file and isn't specifically modified for the TBS card.
http://lxr.free-electrons.com/source/drivers/media/video/v4l2-compat-ioctl32.c
The make has just completed, so I'm about to install and reboot .. My fingers are crossed.
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Thu May 12, 2011 7:05 am

Well - after the above, it Makes, boots and loads.. now to see if I can make it work with MythTV...
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby krajok » Thu May 12, 2011 8:09 am

stevellion Wrote:Well - after the above, it Makes, boots and loads.. now to see if I can make it work with MythTV...


Thank you very much.
I will try to build with your suggestion on Ubuntu 11.04 amd64 first.
krajok
 
Posts: 5
Joined: Wed May 11, 2011 7:43 am

Re: Future of the Linux-Driver

Postby stevellion » Thu May 12, 2011 8:32 am

OK - No "Error" messages, but not finding any channels.
This is my first time with DVB, so could be doing something wrong.
It's the same problem shown earlier on page 1, but solved by a IOMMU flag relating to XEN. I'm just running Kubuntu Natty AMD-64 with my updated v4l2-compat-ioctl file

So - any suggestions on the messages below?

Code: Select All Code
sudo scan-s2 -v -a 0 dvb-s/Astra-28.2E
API major 5, minor 1
scanning dvb-s/Astra-28.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  10773000 H 22000000 5/6 AUTO AUTO
initial transponder DVB-S2 10773000 H 22000000 5/6 AUTO AUTO
initial transponder DVB-S  11778000 V 27500000 2/3 AUTO AUTO
initial transponder DVB-S2 11778000 V 27500000 2/3 AUTO AUTO
----------------------------------> Using DVB-S
>>> tune to: 10773:hC56S0:S0.0W:22000:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 18V, loband (index 1)
DVB-S IF freq is 1023000
>>> tuning status == 0xFFFF8800
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
>>> tune to: 10773:hC56S0:S0.0W:22000: (tuning failed)
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 18V, loband (index 1)
DVB-S IF freq is 1023000
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
----------------------------------> Using DVB-S2
>>> tune to: 10773:hC56S1:S0.0W:22000:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 18V, loband (index 1)
DVB-S IF freq is 1023000
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
>>> tune to: 10773:hC56S1:S0.0W:22000: (tuning failed)
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 18V, loband (index 1)
DVB-S IF freq is 1023000
>>> tuning status == 0x01
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x03
>>> tuning status == 0x01
WARNING: >>> tuning failed!!!
----------------------------------> Using DVB-S
>>> tune to: 11778:vC23S0:S0.0W:27500:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1178000
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
>>> tune to: 11778:vC23S0:S0.0W:27500: (tuning failed)
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1178000
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
----------------------------------> Using DVB-S2
>>> tune to: 11778:vC23S1:S0.0W:27500:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1178000
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
>>> tune to: 11778:vC23S1:S0.0W:27500: (tuning failed)
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1178000
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x03
>>> tuning status == 0x01
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Fri May 13, 2011 2:39 am

Still no luck - and no real ideas now... Anyone have any suggestions?

I'm considering reloading the machine with 32-bit.. but would prefer to keep it at 64-bit really..

Ideally, of course, TBS should be releasing an updated kernel driver against the current version of Ubuntu... :shock:
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Fri May 13, 2011 3:29 am

Hmm.. messing with frequencies,, some scanning works.. Just I don't really understand how to use Scan-s2.. but it's found channels.. Maybe I don't need to reload :).. will update.
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Fri May 13, 2011 4:26 am

OK, I have Lock... szap-s2 works.. - Kubuntu Natty AMD64

Problem is, I don't really understand the channels/frequencies/tuning, or how to watch the channel it's locked on to (just for testing) or then, how to configure MythTV to work with these cards.
Here's the lock output - some help would be great. - Please help with the next step for a newbie... :P

PS - Just to confirm my procedure.

1) Download/untar the driver files from TBS
2) Apply the patch
3) Overwrite the v4l2-compat-ioctl.c - only needed in linux/drivers/media/video with the one in my previous post (just the current one for 2.6.38 I think)
4) Make and install.
5) Mess about with some black-art stuff about frequencies etc.???

Code: Select All Code
szap-s2 -n 001
reading channels from file '~/.szap/channels.conf'
zapping to 1 'Channel 4;BSkyB':
delivery DVB-S, modulation QPSK
sat 0, frequency 10714 MHz H, symbolrate 22000000, coderate 5/6, rolloff 0.35
vpid 0x090b, apid 0x090c, sid 0x090e
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal bf4c | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4b | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4c | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4c | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4c | snr e4b0 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4d | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf4d | snr e2fb | ber 00000000 | unc 00000000 | FE_HAS_LOCK
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Fri May 13, 2011 4:27 pm

OK - Next bit - HELP please!
I've got this output from MythTV as I try to scan from there - something about DiSEQ setting.
snapshot1.png
Snapshot of MythTV output as it tries to Scan.

All I know is that I've unplugged my Sky+ box and plugged in the TBS card instead. I believe I have a quad LNB... (but just 2 cables coming in to the house)
Logically I don't have rotors etc, but not sure what switches if anything I need.

Scan and Szap still works - no changes since last night.
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

Re: Future of the Linux-Driver

Postby stevellion » Fri May 13, 2011 5:19 pm

More progress.. I set an LNB in MythTV - just a Europe Universal with pre-set settings.. MythTV is scanning now, finding plenty of channels. Woo-hoo.
stevellion
 
Posts: 20
Joined: Tue May 10, 2011 4:03 am

PreviousNext

Return to Linux

Who is online

Users browsing this forum: No registered users and 3 guests