After a more close look and some work we got a big step.
Now the TV can be watched and the radio can be listened.
Kaffeine has been able to tune the channels correctly.
Still the driver needs to be cleaned and tested further.
And probably developed a bit further.
But this is a big step!
Hope that there will be time soon to post the update so you can check it soon in linuxtv.org wiki.
----- Mensaje original ----
De: "linux-dvb-request@xxxxxxxxxxx" <linux-dvb-request@xxxxxxxxxxx>
Para: linux-dvb@xxxxxxxxxxx
Enviado: sábado, 28 de julio, 2007 0:22:19
Asunto: linux-dvb Digest, Vol 30, Issue 69
De: "linux-dvb-request@xxxxxxxxxxx" <linux-dvb-request@xxxxxxxxxxx>
Para: linux-dvb@xxxxxxxxxxx
Enviado: sábado, 28 de julio, 2007 0:22:19
Asunto: linux-dvb Digest, Vol 30, Issue 69
Send linux-dvb mailing list submissions to
linux-dvb@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
or, via email, send a message with subject or body 'help' to
linux-dvb-request@xxxxxxxxxxx
You can reach the person managing the list at
linux-dvb-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of linux-dvb digest..."
Today's Topics:
1. Re: [PATCH] Fix Hauppauge Nova-T 500 USB disconnects (Soeren Moch)
2. Re: Hauppauge WinTV Nova-S-Plus - multiple read accesses
impossible (Fabian F?rg)
3. linux-dvb LifeView FlyDVB-Trio PC-Card Change the Frontend to
DVB-S (TDA10086) (Roland Caillet)
4. Re: Hauppauge WinTV Nova-S-Plus - multiple read accesses
impossible (Simon Santoro)
5. Re: Sloth HVR-4000 with DVB-T (Simon Santoro)
6. Re: Sloth HVR-4000 with DVB-T (Simon Santoro)
7. Re: PATCH: extra switch for zap (developers?) (P. van Gaans)
8. Re: linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086) (hermann pitton)
9. Hauppauge dec2540-t (Kees Stoop)
10. linux-dvb LifeView FlyDVB-Trio PC-Card Change the Frontend to
DVB-S (TDA10086) (Roland Caillet)
----------------------------------------------------------------------
Message: 1
Date: Fri, 27 Jul 2007 16:18:00 +0200
From: Soeren Moch <Soeren.Moch@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] Fix Hauppauge Nova-T 500 USB
disconnects
To: jareguero@xxxxxxxxxxxxxx
Cc: linux-dvb@xxxxxxxxxxx
Message-ID:
<200707271421.l6RELr8g026951@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
>>> Respect the patch, it works for me. I have not any disconnect in some
>>> days, althought it is dificult to say that the problem is 100% solved,
>>> because disconnects are random.
Some days ago I wrote a patch for the Nova-T-Stick (see thread
"dib0700 problems (nova-T usb stick)" ). As I could see there,
disconnects are not random, they can only occur directly after a
streamon firmware call. The dib0700 bridge seems to write unintentionally
to the usb bus (or at least driving current into D+/D- or switching
pull-up/down resistors on/off or doing similar strange things) after a
streamon firmware call, usually causing protocol errors (not a real
problem, maybe only for running isochronous transfers to other devices
on the bus), but causing a usb disconnect when accidentally hitting a SOF
packet. So avoiding streamon firmware calls will decrease the disconnect
rate. This is the same idea as in your patches.
>> Relying on device name seems somewhat hackish, however, and doesn't fix
>> anything for nova-t stick ;)
>
> There are other form to do the same, more easily, for all the dibcom
devices,
> but there is a problem: streaming state don't go off when closing the
device,
> althought perphaps that is not important.
> See the atached patch.
This new patch will not help for a Nova-T stick due to the "i2c gating
problem" I have seen there (see thread mentioned above). When simply
starting usb streaming and leaving it on all the time, you are not able
set new tuning parameters, which of course makes this stick useless.
My hope was that Patrick (or some guy at dibcom) will come along with
a real solution for the dib0700 misbehavior after a streamon call.
A new aspect may be, that the disconnect and i2c gating problems might not
be caused by the same source, since the Nova-T 500 seems to have the
disconnect problem, but no i2c gating problem.
S:oren
------------------------------
Message: 2
Date: Fri, 27 Jul 2007 18:09:01 +0200
From: Fabian F?rg <fabian.foerg@xxxxxx>
Subject: Re: Hauppauge WinTV Nova-S-Plus - multiple read
accesses impossible
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA189D.9060406@xxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Fabian F?rg wrote:
> Hello,
>
> in newer kernel releases multiple read accesses on the Hauppauge WinTV
> Nova-S-Plus are impossible.
> Thus, the command line femon is for example unable to open the DVB
> device when VDR is running:
>
> $ fuser -v /dev/dvb/adapter0/frontend0
>
> USER PID ACCESS COMMAND
> /dev/dvb/adapter0/frontend0:
> myuser 5073 F.... vdr
>
> $ femon
> using '/dev/dvb/adapter0/frontend0'
> opening frontend failed: Device or resource busy
>
> I encounterd this issue with kernel 2.6.22.1 and the current Ubuntu
> feisty kernel (2.6.20.x).
> Older kernels allowed multiple accesses. However, I can't test which
> ones, because I replaced
> my system board some time ago, and older kernels don't contain the
> necessary drivers for the board.
>
> Greets,
> Fabian
>
Today I tested it with the newest v4l-sources - also no multiple read
accesses possible.
Any suggestions?
Fabian
------------------------------
Message: 3
Date: Fri, 27 Jul 2007 18:25:34 +0200
From: Roland Caillet <waldgeist@xxxxxxxxxx>
Subject: [linux-dvb] linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086)
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA1C7E.30907@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Hello together,
How i can change the Frontend for my DVB-Card from TDA1004x to TDA10086?
My Card is a LiveView FlyDVB Trio PC-Card.
Here is my "lsmod | grep saa" output:
lsmod | grep saa
saa7134_alsa 17184 1
saa7134_dvb 19084 0
video_buf_dvb 8580 1 saa7134_dvb
tda1004x 18180 2 saa7134_dvb
saa7134 146900 2 saa7134_alsa,saa7134_dvb
video_buf 29700 4
saa7134_alsa,saa7134_dvb,video_buf_dvb,saa7134
compat_ioctl32 11136 1 saa7134
ir_kbd_i2c 11920 1 saa7134
ir_common 38916 2 saa7134,ir_kbd_i2c
videodev 31232 1 saa7134
v4l2_common 22144 4 tuner,saa7134,compat_ioctl32,videodev
v4l1_compat 14980 2 saa7134,videodev
snd_pcm 92808 6
saa7134_alsa,snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss,snd_usb_audio
i2c_core 26496 9
i2c_ec,tda827x,saa7134_dvb,tda1004x,tuner,saa7134,ir_kbd_i2c,nvidia,i2c_viapro
snd 68904 23
saa7134_alsa,snd_via82xx,snd_mpu401_uart,snd_seq_oss,snd_via82xx_modem,snd_seq,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_usb_audio,snd_pcm,snd_rawmidi,snd_seq_device,snd_timer,snd_hwdep
can anyone help me?
thx and greetings roland
------------------------------
Message: 4
Date: Fri, 27 Jul 2007 19:08:14 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Hauppauge WinTV Nova-S-Plus - multiple read
accesses impossible
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271908.15163.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 18:09:01 Fabian F?rg wrote:
> Fabian F?rg wrote:
> > Hello,
> >
> > in newer kernel releases multiple read accesses on the Hauppauge WinTV
> > Nova-S-Plus are impossible.
> > Thus, the command line femon is for example unable to open the DVB
> > device when VDR is running:
> >
> > $ fuser -v /dev/dvb/adapter0/frontend0
> >
> > USER PID ACCESS COMMAND
> > /dev/dvb/adapter0/frontend0:
> > myuser 5073 F.... vdr
> >
> > $ femon
> > using '/dev/dvb/adapter0/frontend0'
> > opening frontend failed: Device or resource busy
> >
> > I encounterd this issue with kernel 2.6.22.1 and the current Ubuntu
> > feisty kernel (2.6.20.x).
> > Older kernels allowed multiple accesses. However, I can't test which
> > ones, because I replaced
> > my system board some time ago, and older kernels don't contain the
> > necessary drivers for the board.
> >
> > Greets,
> > Fabian
>
> Today I tested it with the newest v4l-sources - also no multiple read
> accesses possible.
> Any suggestions?
I don't know if this ever worked, but just to help you a bit, I tested it on
my 2.6.20 kernel, and I get the same.
root@black:/home/mythtv# fuser /dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/frontend0: 5266
root@black:/home/mythtv# femon
using '/dev/dvb/adapter0/frontend0'
opening frontend failed: Device or resource busy
root@black:/home/mythtv#
------------------------------
Message: 5
Date: Fri, 27 Jul 2007 19:14:51 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Sloth HVR-4000 with DVB-T
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271914.51355.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 13:37:35 Moudry, Mipam wrote:
> From the linuxtv.org
> site it is extremely hard to see what is the current state of the
> driver.
Analog, DVB-T and DVB-S with kernel up to 2.6.19 and Stevens driver works.
On kernel 2.6.20 and above, Stevens driver does not compile, and the card does
not work.
DVB-T and Analog should work without compiling Stivens driver with a vanilla
kernel, but I tested it and nothing works (kernel 2.6.20 with stock Ubuntu
feisty).
------------------------------
Message: 6
Date: Fri, 27 Jul 2007 19:18:09 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Sloth HVR-4000 with DVB-T
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271918.09855.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 19:14:51 Simon Santoro wrote:
> On Friday 27 July 2007 13:37:35 Moudry, Mipam wrote:
> > From the linuxtv.org
> > site it is extremely hard to see what is the current state of the
> > driver.
>
> Analog, DVB-T and DVB-S with kernel up to 2.6.19 and Stevens driver works.
> On kernel 2.6.20 and above, Stevens driver does not compile, and the card
> does not work.
> DVB-T and Analog should work without compiling Stivens driver with a
> vanilla kernel, but I tested it and nothing works (kernel 2.6.20 with stock
> Ubuntu feisty).
Sorry, I was writing about the HVR-3000, NOT the HVR-4000.
------------------------------
Message: 7
Date: Fri, 27 Jul 2007 21:39:51 +0200
From: "P. van Gaans" <w3ird_n3rd@xxxxxxx>
Subject: Re: [linux-dvb] PATCH: extra switch for zap (developers?)
To: Uwe Bugla <uwe.bugla@xxxxxx>
Cc: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA4A07.1000405@xxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Uwe Bugla wrote:
> Am Freitag, 27. Juli 2007 04:27:59 schrieben Sie:
>> P. van Gaans wrote:
>>> Uwe Bugla wrote:
>>>> Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie:
>>>>> Uwe Bugla wrote:
>>>>>> Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans:
>>>>>>> I don't call myself a programmer (I've never seen any C guide), but
>>>>>>> somehow I figured out how to add an extra switch to tzap to make it
>>>>>>> print the status in (human-readable) decimal instead of hex. It is
>>>>>>> attached. It would be really nice if this would make it into the
>>>>>>> dvb-apps on linuxtv..
>>>>>>>
>>>>>>> Talking about that, could anybody tell me the minimal and maximal
>>>>>>> and/or
>>>>>>> possible values for status, signal, snr, ber and uncorrected? If I
>>>>>>> would
>>>>>>> know them I could try to make the numbers more human-readable (eg
>>>>>>> signal
>>>>>>> ranging from 0 to 99 or so).
>>>>>> Could you please redo that:
>>>>>> - in patch format (=only the additions)
>>>>>> - equally for tzap, czap, szap and femon?
>>>>>>
>>>>>> Thus everybody could take advantage from that idea.
>>>>>> Would be a pleasure for us all if you did!
>>>>>>
>>>>>> My idea for further enlargement (a quite old idea of mine):
>>>>>> route the human readable numbers into a speech recognition engine
>>>>>> (festival) to make them auditable and thus real usable for DVB-S dish
>>>>>> tuning f. ex.
>>>>>>
>>>>>> Note: If the DVB-S dish is far away from the machine (card), auditable
>>>>>> signals are necessary.
>>>>>>
>>>>>> _______________________________________________
>>>>>> linux-dvb mailing list
>>>>>> linux-dvb@xxxxxxxxxxx
>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>> In patch format.. Oh please.. I have no idea how to produce that! I
>>>>> installed xxdiff, it perfectly shows what I've changed but I don't see
>>>>> an option to save it to a patch file!
>>>>>
>>>>> You're lucky I've got a satellite dish so I should also be able to
>>>>> patch szap and femon. I'll also produce a patched version of czap but
>>>>> my cable card is not installed ATM and I don't feel like doing so
>>>>> (cable provider is crap) but I'll probably get someone else on this
>>>>> list to test it.
>>>>>
>>>>> Please do not try to add the switch yourself without asking me if I'm
>>>>> still working on it. Nobody needs double work.
>>>>>
>>>>> If somebody can tell me how to produce the so much wanted .diff files
>>>>> I'll start working on it.
>>>> A. Take the latest kernel patch (i. e. 2.6.21.1) as an example.
>>>> B. format is as follows:
>>>> --- a/(file to be changed)
>>>> +++ b/(file to be changed)
>>>> @@ -(starting line number),(total number of lines starting from the
>>>> beginning line before the change) +(starting line number),(total
>>>> number of lines starting from the beginning line after the change)
>>>> (3 context lines starting with a space)
>>>> (additions start with plus)
>>>> (deletions start with minus)
>>>> (3 context lines starting with a space)
>>>>
>>>> If this explanation still is too abstract, have a look at the example
>>>> again.
>>>> Don't forget to test the patch!
>>>> No fuzz factors, no rejections please.
>>>> For testing purposes keep the original file to be patched in a
>>>> separate directory please.
>>>> Now please give it a try - for sure you gonna make it!
>>> I've got an idea of how the .diff is constructed, but I simply refuse to
>>> write them by hand. I've bought a computer NOT to do any more boring
>>> repetitive work ;-).
>>>
>>> diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily.
>>>
>>> Tzap was patched already.
>>> Szap patched, compiles, tested and OK.
>>> Czap patched, compiles without errors, untested because I hate my cable
>>> provider and the box I would have to install the cable card in is really
>>> noisy and unstable. Whoever wants to test: please report results, czap
>>> looks a little different from szap and tzap but I'm pretty certain it'll
>>> work straightaway. I assume this is OK, you couldn't expect all linuxtv
>>> developers to own cards for all DVB-systems anyway..
>>> Femon patched in a different way: Femon already has a "human readable"
>>> switch, I just made BER and uncorrected show up as decimal instead of
>>> hex in human readable mode. Adding another switch sounds pointless to me.
>>>
>>> The numbers/output seem to differ between devices and between szap and
>>> tzap greatly so for now I'm not going to try to make them more
>>> human-readable because of the possibility of breaking something.
>>>
>>> Everything attached.
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@xxxxxxxxxxx
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>> There was some confusion cause of Uwe, but will my switch ever make it
>> to the dvb-apps on linuxtv? Or is there something wrong with it?
>
> I did not want to cause any confusion at all, but I just transformed your work
> into a patch format that is expected everywhere in the linux world if you
> want your stuff to be merged.
>
> As it was refused as a whole (patched dvb-apps) I decided to resend it to
> Christoph Pfister CCing you.
>
> Everybody's waiting for Christoph Pfister now.
>
> Cheers
>
> Uwe
>
Yes, I saw that mail a little later after my reply was already sent.
It seems the "patch format" is just all my diff files following up each
other in one file? If that's the expected format, good to know.
------------------------------
Message: 8
Date: Fri, 27 Jul 2007 22:00:48 +0200
From: hermann pitton <hermann-pitton@xxxxxxxx>
Subject: Re: linux-dvb LifeView FlyDVB-Trio PC-Card Change
the Frontend to DVB-S (TDA10086)
To: Roland Caillet <waldgeist@xxxxxxxxxx>
Cc: linux-dvb@xxxxxxxxxxx
Message-ID: <1185566448.4587.3.camel@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain
Hi,
Am Freitag, den 27.07.2007, 18:25 +0200 schrieb Roland Caillet:
> Hello together,
> How i can change the Frontend for my DVB-Card from TDA1004x to TDA10086?
> My Card is a LiveView FlyDVB Trio PC-Card.
> Here is my "lsmod | grep saa" output:
[snip]
>
> can anyone help me?
> thx and greetings roland
try "modinfo saa7134-dvb".
"modprobe -vr saa7134-dvb"
"modprobe -v saa7134-dvb use_frontend=1"
Cheers,
Hermann
------------------------------
Message: 9
Date: Fri, 27 Jul 2007 22:11:33 +0200
From: Kees Stoop <kees@xxxxxxxxxxxxxxxx>
Subject: Hauppauge dec2540-t
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA5175.5090105@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello,
Has anyone been able to get this device working under linux ?
I am have some trouble with it.
When I switch the device on, the correct modules get loaded (ttusb_dec
and ttusbdecfe), firmware gets loaded and I do not get any weird
messages, so far so good. dmesg gives me:
[74969.803277] DVB: registering new adapter (DEC2540-t)
[74969.803409] DVB: registering frontend 0 (TechnoTrend/Hauppauge
DEC2000-t Frontend)...
However when I run tzap, I get lines like this:
status 00 | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
status 1f | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
FE_HAS_LOCK
status 1f | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
FE_HAS_LOCK
The signal-field always reads 0001 and snr is always 0000. I would
expect a much higher value for signal then 0001 isn't it ?
I can get a channel list, so part of the driver must be working, but
mplayer does not work.
I use: mplayer dvb://"Nederland 1" -vo x11
The error message that mplayer gives me is:
....
Playing dvb://Nederland 1.
dvb_tune Freq: 618000000
ERROR IN SETTING DMX_FILTER 7011 for fd 4: ERRNO: 38ERROR, COULDN'T SET
CHANNEL 0: Failed to open dvb://Nederland 1.
I am using MPlayer 2:1.0~rc1-0ubuntu9.1 on ubuntu feisty (kernel
2.6.20), and with the latest v4l-dvb modules.
Any help is appreciated.
Kees Stoop.
------------------------------
Message: 10
Date: Fri, 27 Jul 2007 23:21:47 +0200
From: Roland Caillet <waldgeist@xxxxxxxxxx>
Subject: linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086)
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA61EB.4090604@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
hello hermann,
THX for fast answer. Your solution running, but now the next problem.
I loading the modules with /etc/modprobe.d/saa7134, found in the web.
Here the printout:
"options i2c-algo-bit bit_test=1"
"install saa7134 /sbin/modprobe --first-time --ignore-install saa7134 &&
/sbin/modprobe saa7134-alsa"
"options saa7134 card=84 noninterlaced=1"
"options saa7134_alsa index=1"
1. How i can bring your solution in this file for loading correctly?
2. I can scan the Astra 19.2 Satelite with Kaffeine and become nearly
300 free tv-programms, but Kaffeine don't let me look anyone of tv-programm.
I can clicking to ZDF, ARD, RTL or somewhere but the screen stay
dark like a night without moon. Why?
Maybe you can help me once more
THX and greetings from switzerland, roland
------------------------------
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
End of linux-dvb Digest, Vol 30, Issue 69
*****************************************
linux-dvb@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
or, via email, send a message with subject or body 'help' to
linux-dvb-request@xxxxxxxxxxx
You can reach the person managing the list at
linux-dvb-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of linux-dvb digest..."
Today's Topics:
1. Re: [PATCH] Fix Hauppauge Nova-T 500 USB disconnects (Soeren Moch)
2. Re: Hauppauge WinTV Nova-S-Plus - multiple read accesses
impossible (Fabian F?rg)
3. linux-dvb LifeView FlyDVB-Trio PC-Card Change the Frontend to
DVB-S (TDA10086) (Roland Caillet)
4. Re: Hauppauge WinTV Nova-S-Plus - multiple read accesses
impossible (Simon Santoro)
5. Re: Sloth HVR-4000 with DVB-T (Simon Santoro)
6. Re: Sloth HVR-4000 with DVB-T (Simon Santoro)
7. Re: PATCH: extra switch for zap (developers?) (P. van Gaans)
8. Re: linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086) (hermann pitton)
9. Hauppauge dec2540-t (Kees Stoop)
10. linux-dvb LifeView FlyDVB-Trio PC-Card Change the Frontend to
DVB-S (TDA10086) (Roland Caillet)
----------------------------------------------------------------------
Message: 1
Date: Fri, 27 Jul 2007 16:18:00 +0200
From: Soeren Moch <Soeren.Moch@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] Fix Hauppauge Nova-T 500 USB
disconnects
To: jareguero@xxxxxxxxxxxxxx
Cc: linux-dvb@xxxxxxxxxxx
Message-ID:
<200707271421.l6RELr8g026951@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
>>> Respect the patch, it works for me. I have not any disconnect in some
>>> days, althought it is dificult to say that the problem is 100% solved,
>>> because disconnects are random.
Some days ago I wrote a patch for the Nova-T-Stick (see thread
"dib0700 problems (nova-T usb stick)" ). As I could see there,
disconnects are not random, they can only occur directly after a
streamon firmware call. The dib0700 bridge seems to write unintentionally
to the usb bus (or at least driving current into D+/D- or switching
pull-up/down resistors on/off or doing similar strange things) after a
streamon firmware call, usually causing protocol errors (not a real
problem, maybe only for running isochronous transfers to other devices
on the bus), but causing a usb disconnect when accidentally hitting a SOF
packet. So avoiding streamon firmware calls will decrease the disconnect
rate. This is the same idea as in your patches.
>> Relying on device name seems somewhat hackish, however, and doesn't fix
>> anything for nova-t stick ;)
>
> There are other form to do the same, more easily, for all the dibcom
devices,
> but there is a problem: streaming state don't go off when closing the
device,
> althought perphaps that is not important.
> See the atached patch.
This new patch will not help for a Nova-T stick due to the "i2c gating
problem" I have seen there (see thread mentioned above). When simply
starting usb streaming and leaving it on all the time, you are not able
set new tuning parameters, which of course makes this stick useless.
My hope was that Patrick (or some guy at dibcom) will come along with
a real solution for the dib0700 misbehavior after a streamon call.
A new aspect may be, that the disconnect and i2c gating problems might not
be caused by the same source, since the Nova-T 500 seems to have the
disconnect problem, but no i2c gating problem.
S:oren
------------------------------
Message: 2
Date: Fri, 27 Jul 2007 18:09:01 +0200
From: Fabian F?rg <fabian.foerg@xxxxxx>
Subject: Re: Hauppauge WinTV Nova-S-Plus - multiple read
accesses impossible
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA189D.9060406@xxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Fabian F?rg wrote:
> Hello,
>
> in newer kernel releases multiple read accesses on the Hauppauge WinTV
> Nova-S-Plus are impossible.
> Thus, the command line femon is for example unable to open the DVB
> device when VDR is running:
>
> $ fuser -v /dev/dvb/adapter0/frontend0
>
> USER PID ACCESS COMMAND
> /dev/dvb/adapter0/frontend0:
> myuser 5073 F.... vdr
>
> $ femon
> using '/dev/dvb/adapter0/frontend0'
> opening frontend failed: Device or resource busy
>
> I encounterd this issue with kernel 2.6.22.1 and the current Ubuntu
> feisty kernel (2.6.20.x).
> Older kernels allowed multiple accesses. However, I can't test which
> ones, because I replaced
> my system board some time ago, and older kernels don't contain the
> necessary drivers for the board.
>
> Greets,
> Fabian
>
Today I tested it with the newest v4l-sources - also no multiple read
accesses possible.
Any suggestions?
Fabian
------------------------------
Message: 3
Date: Fri, 27 Jul 2007 18:25:34 +0200
From: Roland Caillet <waldgeist@xxxxxxxxxx>
Subject: [linux-dvb] linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086)
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA1C7E.30907@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Hello together,
How i can change the Frontend for my DVB-Card from TDA1004x to TDA10086?
My Card is a LiveView FlyDVB Trio PC-Card.
Here is my "lsmod | grep saa" output:
lsmod | grep saa
saa7134_alsa 17184 1
saa7134_dvb 19084 0
video_buf_dvb 8580 1 saa7134_dvb
tda1004x 18180 2 saa7134_dvb
saa7134 146900 2 saa7134_alsa,saa7134_dvb
video_buf 29700 4
saa7134_alsa,saa7134_dvb,video_buf_dvb,saa7134
compat_ioctl32 11136 1 saa7134
ir_kbd_i2c 11920 1 saa7134
ir_common 38916 2 saa7134,ir_kbd_i2c
videodev 31232 1 saa7134
v4l2_common 22144 4 tuner,saa7134,compat_ioctl32,videodev
v4l1_compat 14980 2 saa7134,videodev
snd_pcm 92808 6
saa7134_alsa,snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss,snd_usb_audio
i2c_core 26496 9
i2c_ec,tda827x,saa7134_dvb,tda1004x,tuner,saa7134,ir_kbd_i2c,nvidia,i2c_viapro
snd 68904 23
saa7134_alsa,snd_via82xx,snd_mpu401_uart,snd_seq_oss,snd_via82xx_modem,snd_seq,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_usb_audio,snd_pcm,snd_rawmidi,snd_seq_device,snd_timer,snd_hwdep
can anyone help me?
thx and greetings roland
------------------------------
Message: 4
Date: Fri, 27 Jul 2007 19:08:14 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Hauppauge WinTV Nova-S-Plus - multiple read
accesses impossible
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271908.15163.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 18:09:01 Fabian F?rg wrote:
> Fabian F?rg wrote:
> > Hello,
> >
> > in newer kernel releases multiple read accesses on the Hauppauge WinTV
> > Nova-S-Plus are impossible.
> > Thus, the command line femon is for example unable to open the DVB
> > device when VDR is running:
> >
> > $ fuser -v /dev/dvb/adapter0/frontend0
> >
> > USER PID ACCESS COMMAND
> > /dev/dvb/adapter0/frontend0:
> > myuser 5073 F.... vdr
> >
> > $ femon
> > using '/dev/dvb/adapter0/frontend0'
> > opening frontend failed: Device or resource busy
> >
> > I encounterd this issue with kernel 2.6.22.1 and the current Ubuntu
> > feisty kernel (2.6.20.x).
> > Older kernels allowed multiple accesses. However, I can't test which
> > ones, because I replaced
> > my system board some time ago, and older kernels don't contain the
> > necessary drivers for the board.
> >
> > Greets,
> > Fabian
>
> Today I tested it with the newest v4l-sources - also no multiple read
> accesses possible.
> Any suggestions?
I don't know if this ever worked, but just to help you a bit, I tested it on
my 2.6.20 kernel, and I get the same.
root@black:/home/mythtv# fuser /dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/frontend0: 5266
root@black:/home/mythtv# femon
using '/dev/dvb/adapter0/frontend0'
opening frontend failed: Device or resource busy
root@black:/home/mythtv#
------------------------------
Message: 5
Date: Fri, 27 Jul 2007 19:14:51 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Sloth HVR-4000 with DVB-T
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271914.51355.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 13:37:35 Moudry, Mipam wrote:
> From the linuxtv.org
> site it is extremely hard to see what is the current state of the
> driver.
Analog, DVB-T and DVB-S with kernel up to 2.6.19 and Stevens driver works.
On kernel 2.6.20 and above, Stevens driver does not compile, and the card does
not work.
DVB-T and Analog should work without compiling Stivens driver with a vanilla
kernel, but I tested it and nothing works (kernel 2.6.20 with stock Ubuntu
feisty).
------------------------------
Message: 6
Date: Fri, 27 Jul 2007 19:18:09 +0200
From: Simon Santoro <simon.santoro@xxxxxxxxx>
Subject: Re: Sloth HVR-4000 with DVB-T
To: linux-dvb@xxxxxxxxxxx
Message-ID: <200707271918.09855.simon.santoro@xxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 27 July 2007 19:14:51 Simon Santoro wrote:
> On Friday 27 July 2007 13:37:35 Moudry, Mipam wrote:
> > From the linuxtv.org
> > site it is extremely hard to see what is the current state of the
> > driver.
>
> Analog, DVB-T and DVB-S with kernel up to 2.6.19 and Stevens driver works.
> On kernel 2.6.20 and above, Stevens driver does not compile, and the card
> does not work.
> DVB-T and Analog should work without compiling Stivens driver with a
> vanilla kernel, but I tested it and nothing works (kernel 2.6.20 with stock
> Ubuntu feisty).
Sorry, I was writing about the HVR-3000, NOT the HVR-4000.
------------------------------
Message: 7
Date: Fri, 27 Jul 2007 21:39:51 +0200
From: "P. van Gaans" <w3ird_n3rd@xxxxxxx>
Subject: Re: [linux-dvb] PATCH: extra switch for zap (developers?)
To: Uwe Bugla <uwe.bugla@xxxxxx>
Cc: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA4A07.1000405@xxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Uwe Bugla wrote:
> Am Freitag, 27. Juli 2007 04:27:59 schrieben Sie:
>> P. van Gaans wrote:
>>> Uwe Bugla wrote:
>>>> Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie:
>>>>> Uwe Bugla wrote:
>>>>>> Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans:
>>>>>>> I don't call myself a programmer (I've never seen any C guide), but
>>>>>>> somehow I figured out how to add an extra switch to tzap to make it
>>>>>>> print the status in (human-readable) decimal instead of hex. It is
>>>>>>> attached. It would be really nice if this would make it into the
>>>>>>> dvb-apps on linuxtv..
>>>>>>>
>>>>>>> Talking about that, could anybody tell me the minimal and maximal
>>>>>>> and/or
>>>>>>> possible values for status, signal, snr, ber and uncorrected? If I
>>>>>>> would
>>>>>>> know them I could try to make the numbers more human-readable (eg
>>>>>>> signal
>>>>>>> ranging from 0 to 99 or so).
>>>>>> Could you please redo that:
>>>>>> - in patch format (=only the additions)
>>>>>> - equally for tzap, czap, szap and femon?
>>>>>>
>>>>>> Thus everybody could take advantage from that idea.
>>>>>> Would be a pleasure for us all if you did!
>>>>>>
>>>>>> My idea for further enlargement (a quite old idea of mine):
>>>>>> route the human readable numbers into a speech recognition engine
>>>>>> (festival) to make them auditable and thus real usable for DVB-S dish
>>>>>> tuning f. ex.
>>>>>>
>>>>>> Note: If the DVB-S dish is far away from the machine (card), auditable
>>>>>> signals are necessary.
>>>>>>
>>>>>> _______________________________________________
>>>>>> linux-dvb mailing list
>>>>>> linux-dvb@xxxxxxxxxxx
>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>> In patch format.. Oh please.. I have no idea how to produce that! I
>>>>> installed xxdiff, it perfectly shows what I've changed but I don't see
>>>>> an option to save it to a patch file!
>>>>>
>>>>> You're lucky I've got a satellite dish so I should also be able to
>>>>> patch szap and femon. I'll also produce a patched version of czap but
>>>>> my cable card is not installed ATM and I don't feel like doing so
>>>>> (cable provider is crap) but I'll probably get someone else on this
>>>>> list to test it.
>>>>>
>>>>> Please do not try to add the switch yourself without asking me if I'm
>>>>> still working on it. Nobody needs double work.
>>>>>
>>>>> If somebody can tell me how to produce the so much wanted .diff files
>>>>> I'll start working on it.
>>>> A. Take the latest kernel patch (i. e. 2.6.21.1) as an example.
>>>> B. format is as follows:
>>>> --- a/(file to be changed)
>>>> +++ b/(file to be changed)
>>>> @@ -(starting line number),(total number of lines starting from the
>>>> beginning line before the change) +(starting line number),(total
>>>> number of lines starting from the beginning line after the change)
>>>> (3 context lines starting with a space)
>>>> (additions start with plus)
>>>> (deletions start with minus)
>>>> (3 context lines starting with a space)
>>>>
>>>> If this explanation still is too abstract, have a look at the example
>>>> again.
>>>> Don't forget to test the patch!
>>>> No fuzz factors, no rejections please.
>>>> For testing purposes keep the original file to be patched in a
>>>> separate directory please.
>>>> Now please give it a try - for sure you gonna make it!
>>> I've got an idea of how the .diff is constructed, but I simply refuse to
>>> write them by hand. I've bought a computer NOT to do any more boring
>>> repetitive work ;-).
>>>
>>> diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily.
>>>
>>> Tzap was patched already.
>>> Szap patched, compiles, tested and OK.
>>> Czap patched, compiles without errors, untested because I hate my cable
>>> provider and the box I would have to install the cable card in is really
>>> noisy and unstable. Whoever wants to test: please report results, czap
>>> looks a little different from szap and tzap but I'm pretty certain it'll
>>> work straightaway. I assume this is OK, you couldn't expect all linuxtv
>>> developers to own cards for all DVB-systems anyway..
>>> Femon patched in a different way: Femon already has a "human readable"
>>> switch, I just made BER and uncorrected show up as decimal instead of
>>> hex in human readable mode. Adding another switch sounds pointless to me.
>>>
>>> The numbers/output seem to differ between devices and between szap and
>>> tzap greatly so for now I'm not going to try to make them more
>>> human-readable because of the possibility of breaking something.
>>>
>>> Everything attached.
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@xxxxxxxxxxx
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>> There was some confusion cause of Uwe, but will my switch ever make it
>> to the dvb-apps on linuxtv? Or is there something wrong with it?
>
> I did not want to cause any confusion at all, but I just transformed your work
> into a patch format that is expected everywhere in the linux world if you
> want your stuff to be merged.
>
> As it was refused as a whole (patched dvb-apps) I decided to resend it to
> Christoph Pfister CCing you.
>
> Everybody's waiting for Christoph Pfister now.
>
> Cheers
>
> Uwe
>
Yes, I saw that mail a little later after my reply was already sent.
It seems the "patch format" is just all my diff files following up each
other in one file? If that's the expected format, good to know.
------------------------------
Message: 8
Date: Fri, 27 Jul 2007 22:00:48 +0200
From: hermann pitton <hermann-pitton@xxxxxxxx>
Subject: Re: linux-dvb LifeView FlyDVB-Trio PC-Card Change
the Frontend to DVB-S (TDA10086)
To: Roland Caillet <waldgeist@xxxxxxxxxx>
Cc: linux-dvb@xxxxxxxxxxx
Message-ID: <1185566448.4587.3.camel@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain
Hi,
Am Freitag, den 27.07.2007, 18:25 +0200 schrieb Roland Caillet:
> Hello together,
> How i can change the Frontend for my DVB-Card from TDA1004x to TDA10086?
> My Card is a LiveView FlyDVB Trio PC-Card.
> Here is my "lsmod | grep saa" output:
[snip]
>
> can anyone help me?
> thx and greetings roland
try "modinfo saa7134-dvb".
"modprobe -vr saa7134-dvb"
"modprobe -v saa7134-dvb use_frontend=1"
Cheers,
Hermann
------------------------------
Message: 9
Date: Fri, 27 Jul 2007 22:11:33 +0200
From: Kees Stoop <kees@xxxxxxxxxxxxxxxx>
Subject: Hauppauge dec2540-t
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA5175.5090105@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello,
Has anyone been able to get this device working under linux ?
I am have some trouble with it.
When I switch the device on, the correct modules get loaded (ttusb_dec
and ttusbdecfe), firmware gets loaded and I do not get any weird
messages, so far so good. dmesg gives me:
[74969.803277] DVB: registering new adapter (DEC2540-t)
[74969.803409] DVB: registering frontend 0 (TechnoTrend/Hauppauge
DEC2000-t Frontend)...
However when I run tzap, I get lines like this:
status 00 | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
status 1f | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
FE_HAS_LOCK
status 1f | signal 0001 | snr 0000 | ber b7f8a858 | unc b7f8ab38 |
FE_HAS_LOCK
The signal-field always reads 0001 and snr is always 0000. I would
expect a much higher value for signal then 0001 isn't it ?
I can get a channel list, so part of the driver must be working, but
mplayer does not work.
I use: mplayer dvb://"Nederland 1" -vo x11
The error message that mplayer gives me is:
....
Playing dvb://Nederland 1.
dvb_tune Freq: 618000000
ERROR IN SETTING DMX_FILTER 7011 for fd 4: ERRNO: 38ERROR, COULDN'T SET
CHANNEL 0: Failed to open dvb://Nederland 1.
I am using MPlayer 2:1.0~rc1-0ubuntu9.1 on ubuntu feisty (kernel
2.6.20), and with the latest v4l-dvb modules.
Any help is appreciated.
Kees Stoop.
------------------------------
Message: 10
Date: Fri, 27 Jul 2007 23:21:47 +0200
From: Roland Caillet <waldgeist@xxxxxxxxxx>
Subject: linux-dvb LifeView FlyDVB-Trio PC-Card Change the
Frontend to DVB-S (TDA10086)
To: linux-dvb@xxxxxxxxxxx
Message-ID: <46AA61EB.4090604@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
hello hermann,
THX for fast answer. Your solution running, but now the next problem.
I loading the modules with /etc/modprobe.d/saa7134, found in the web.
Here the printout:
"options i2c-algo-bit bit_test=1"
"install saa7134 /sbin/modprobe --first-time --ignore-install saa7134 &&
/sbin/modprobe saa7134-alsa"
"options saa7134 card=84 noninterlaced=1"
"options saa7134_alsa index=1"
1. How i can bring your solution in this file for loading correctly?
2. I can scan the Astra 19.2 Satelite with Kaffeine and become nearly
300 free tv-programms, but Kaffeine don't let me look anyone of tv-programm.
I can clicking to ZDF, ARD, RTL or somewhere but the screen stay
dark like a night without moon. Why?
Maybe you can help me once more
THX and greetings from switzerland, roland
------------------------------
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
End of linux-dvb Digest, Vol 30, Issue 69
*****************************************
Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
