Re: [linux-dvb] Bad TS from dvb-t recording?

[Måns Rullgård]

Greg 'groggy' Lehey <[EMAIL PROTECTED]> writes:

> [Format recovered--see http://www.lemis.com/email/email-format.html]
>
> Output lines unwrapped.
>
> On Thursday,  8 March 2007 at 17:03:40 +0100, Torbjrn Lundquist wrote:
>> Hi,
>>
>> I'm trying to make a recording from my dvb-t card (Avermedia). I do like
>> this:
>>
>>> tzap -r -c channels.conf -t 5 -o test.ts SVT24
>>
>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>> reading channels from file 'channels.conf'
>> tuning to 52200 Hz
>> video pid 0x04e1, audio pid 0x04e0
>> status 00 | signal 58cf | snr  | ber  | unc  | copied 
>> 1708168 bytes (333 Kbytes/sec)
>> status 1f | signal f1cf | snr c0c0 | ber  | unc  | 
>> FE_HAS_LOCK
>>
>> But then I cannot view the file in VLC for instance. If I run dvbsnoop on it
>> I receive some errors, for instance:
>>
>> MPEG-DescriptorTag: 63 (0x3f)  [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
>>Descriptor_length: 199 (0xc7)
>>  > ERROR: unimplemented descriptor (mpeg context), Report!
>
> This sounds like vlc's way of saying "I don't understand MPEG TS".

No, VLC understands MPEG TS, although it's sometimes a bit fussy about
the timestamps.  That error message is saying that the stream has
(probably in the PMT) a descriptor with tag 63.  This value is
reserved in ISO 13818-1, meaning that it may not be used in extensions
for specific applications, such as DVB.  Refusing to play the stream
only because of this strikes me as somewhat unfriendly, though.

>> I live in Sweden and receive the signal from the Motala-tranciever.
>
> I don't think that this is related to the transmitter.

It could be, in the sense that different broadcasters use different
encoding parameters.

>> What am I doing wrong? Or can I use some other program for recording (I
>> tried mencoder without success)?
>
> I do almost exactly this and view the result with mplayer, which

MPlayer will play almost any transport stream, even without a PMT, in
which case it assumes MPEG2 video and MPEG1 audio.

> recognizes it without problems.  Note that the timing information in
> the stream can be crazy (here, for some reason, it wraps around about
> every 26½ hours).  I've done a few patches to mplayer to try to
> display saner times, but they don't work all the time.

The wraparound happens simply because the timestamps are measured at
90kHz and stored in 33 bits.  That happens to last for about 26.5
hours.  DVB streams can contain packets with actual calendar time, but
they might not be present on all multiplexes.

-- 
Måns Rullgård
[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Greg 'groggy' Lehey]

On Thursday,  8 March 2007 at 17:24:22 +0100, Andrea Venturi wrote:
> Torbjörn Lundquist wrote:
>> Hi,
>>
>> I'm trying to make a recording from my dvb-t card (Avermedia). I do like
>> this:
>>
>>> tzap -r -c channels.conf -t 5 -o test.ts SVT24
>>
>> ..
>>
>> But then I cannot view the file in VLC for instance. If I run dvbsnoop
>> on it I receive some errors, for instance:
>
> i just try a guess. i don't use tzap.
>
> maybe tzap doesn't dump the relevant tables (PAT PMT) so VLC can't
> reconstruct the service.  i see indeed only video and audio pids in
> the log.

tzap is just a tuning utility, so indeed it doesn't dump any tables.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key.
See complete headers for address and phone numbers.


pgpBmriikH2C3.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Greg 'groggy' Lehey]

[Format recovered--see http://www.lemis.com/email/email-format.html]

Output lines unwrapped.

On Thursday,  8 March 2007 at 17:03:40 +0100, Torbjrn Lundquist wrote:
> Hi,
>
> I'm trying to make a recording from my dvb-t card (Avermedia). I do like
> this:
>
>> tzap -r -c channels.conf -t 5 -o test.ts SVT24
>
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file 'channels.conf'
> tuning to 52200 Hz
> video pid 0x04e1, audio pid 0x04e0
> status 00 | signal 58cf | snr  | ber  | unc  | copied 
> 1708168 bytes (333 Kbytes/sec)
> status 1f | signal f1cf | snr c0c0 | ber  | unc  | FE_HAS_LOCK
>
> But then I cannot view the file in VLC for instance. If I run dvbsnoop on it
> I receive some errors, for instance:
>
> MPEG-DescriptorTag: 63 (0x3f)  [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
>Descriptor_length: 199 (0xc7)
>  > ERROR: unimplemented descriptor (mpeg context), Report!

This sounds like vlc's way of saying "I don't understand MPEG TS".

> I live in Sweden and receive the signal from the Motala-tranciever.

I don't think that this is related to the transmitter.

> What am I doing wrong? Or can I use some other program for recording (I
> tried mencoder without success)?

I do almost exactly this and view the result with mplayer, which
recognizes it without problems.  Note that the timing information in
the stream can be crazy (here, for some reason, it wraps around about
every 26½ hours).  I've done a few patches to mplayer to try to
display saner times, but they don't work all the time.

Greg
--
When replying to this message, please take care not to mutilate the
original text.
For more information, see http://www.lemis.com/email.html
Finger [EMAIL PROTECTED] for PGP public key.
See complete headers for address and phone numbers.


pgpjC40gv0ej2.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [PATCH] v4l-dvb: add $DESTDIR support

[Trent Piepho]

On Thu, 8 Mar 2007, Ludwig Nussel wrote:
> Trent Piepho wrote:
> > > Following patch adds $DESTDIR support so one can install the kernel
> > > modules into a directory other than / as non-root user. That's
> > > useful when building an rpm or compiling for a different machine.

> > > -print OUT "\t/sbin/depmod -a \${KERNELRELEASE}\n\n";
> > > +print OUT "\tif [ -w / ]; then /sbin/depmod -a \${KERNELRELEASE}; 
> > > fi\n\n";
> >
> > This doesn't seem correct.  Shouldn't it be:
> > print OUT "\t/sbin/depmod -a \$(KERNELRELEASE) \$(if \$(DESTDIR),-b 
> > \$(DESTDIR))\n\n";
>
> One needs to run depmod when the modules get installed to their final 
> location.
> $DESTDIR is incomplete so it doesn't make sense to run depmod here already.

When compiling an RPM package DESTDIR may not be the final location, but
that is not the only reason one might want to use DESTDIR.  One could
repair a mounted root fs after booting from a rescue CD or be trying to
create a bootable MythTV image.

If I can write to /, then the modules go to DESTDIR but depmod is run on /.
That doesn't seem consistent.  And if I can't write to / (say it's read
only) but can write to the module install directory, then depmod isn't run,
even if I plan to boot a system with those modules.

Also, the kernel's "modules_install" target will run depmod on with "-b
$(INSTALL_MOD_PATH)" if the modules are being installed to a directory other
than the root.  I think it makes sense to be consistent with the kernel's
behavior.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Anubis Electronics "Lifeview"(0x10fd:0x1513)

[Hartmut Hackmann]

Hi, Pierre

Pierre Willenbrock schrieb:
> Hi Hartmut,
> 
> Hartmut Hackmann schrieb:
>> Hi, Pierre
>>
>> Pierre Willenbrock schrieb:
>>> Hartmut Hackmann schrieb:
 Hi,

 Aapo Tahkola schrieb:
> On Sat, 3 Mar 2007 03:10:41 +0200
> Aapo Tahkola <[EMAIL PROTECTED]> wrote:
>
>> On Fri, 02 Mar 2007 23:06:15 +0100
>> Pierre Willenbrock <[EMAIL PROTECTED]> wrote:
>>
>>> Michael Krufky schrieb:
 Pierre Willenbrock wrote:
> Hi list,
>
> I am owner of a "MSI DIGIVOX mini-II". I got it to work using the
> attached patch and firmware. The patch and firmware are the
> result of analyzing some usb logs from windows.
>
> The patch breaks all users of tda10046, as i don't understand how
> that chip is supposed to work. The same goes for my driver
> implementation of the Philips 8275a.
>
> So this mess needs to be fixed before it can go into the
> repository.
>
> The patch is against a fresh hg checkout from
> http://linuxtv.org/hg/v4l-dvb at 2007-02-22 21:00 UTC.
>
> Regards,
>   Pierre
 Pierre-

 I am very happy to hear that you got this device working...
 Interestingly enough, we have already created a new tda827x dvb fe
 module, which might be better for your device...  This new tda827x
 module has not yet been merged into the master v4l-dvb repository,
 but it will be soon.  Could you try to use the code located in:

 http://linuxtv.org/hg/~hhackmann/v4l-dvb

 The tda827x module will be able to detect the difference between
 the tda8275 and the tda8275a ...  You do not have to fill the
 callback functions in the config struct -- that is really meant as
 a hack for some required GPIO handling in the saa7134-dvb driver
 for input switching.

 If you can generate a new patch against the repository above, it
 would make it _much_ easier to integrate your patch into the
 sources.   After you get that done, we can work out the tda1004x
 differences.

 You might also want to speak to aett and friedrich, regulars of
 the #linuxtv irc chat room on irc.freenode.net ... aet is the
 author of the m920x driver, and friedrich has the same device
 that you have. They have been working on it, but haven't yet
 gotten successful results.

 Good work!  Hopefully we can clean this up after you generate a
 new patch using the tda827x module from hhackmann's repository.

 Regards,

 Mike Krufky

>>> Hi Mike and Hartmut,
>>>
>>> this time, the patch does not change tda827x.c at all. I fiddled
>>> with the PHY2 value in tda1004x.c and found it to be related to the
>>> IF(there seems to be some factor between the IF and PHY2 introduced
>>> somewhere else). This leaves some differences in tda1004x.c. I don't
>>> know what to do with these, so i would be glad to get any hints.
>> Updated patch. I'm fine with these m920x changes.
>>
> Signed-of-by: Aapo Tahkola <[EMAIL PROTECTED]>
>
 PHY2 indeed defines the IF frequency relative to the sampling frequency.
 If you need a different value here, the reason most probably is the
 following:
 In some countries, i.e. Britain, France and Australia, the tranmitters
 are +/- 166kHz off the channel center frequency. This isn't documented.
 You can compensate this by simply tuning to the actually used channel
 center frequency.

>>> The windows driver used an IF of 4.75MHz for UHF, so i resorted to
>>> hardcoding it to 4.75MHz in tda827x.c, while using PHY2, WREF and the
>>> other settings from an usb log. After changing PHY2 the hack in
>>> tda827x.c is no longer needed. This leaves me with these settings for
>>> UHF(cannot test VHF -- i don't get any channels in that range):
>>>
>>> CONFPLL2=7 //52MHz sampling clock?
>> yes
>>
>>> FREQ_PHY2=0xc4f
>>> TIME_WREF1..5=0x5b, 0x02, 0xd0, 0x2d, 0x03
>>>
>> This gives a IF center frequency of 5.0MHz and a bandwidth of 8MHz.
>>
 A note: Some channel decoders can compensate this offset automatically.
 The tda10046 needs assistance from the driver for this. This is not
 built in yet.

 Hartmut
>>> Regards,
>>>   Pierre
>>>
>> The only difference is that you use a sampling clock of 52MHz while the
>> original driver uses 48MHz. This btw is the same as the Philips default
>> driver for windows uses.
>> We could have a long discussion now about ideal sampling frequencies but
>> believe me: as long as your board does not have a weird interference
>> problem, 48MHz is the better choice for the sampling clock and adding a
>> additional one would only make life more difficult.
> 
> I thought i checked that it does not easily

Re: [linux-dvb] Bad TS from dvb-t recording?

[Peter Fassberg]

> dvbstream -f 522000 -o -tm 8 0 1248 1249 5180 > recordings/test.ts

The PMT for thje specific channel is probably 1240:

dvbstream -f 522000 -o -tm 8 0 1240 1248 1249 > recordings/test.ts

... and "-tm 8" is probably not needed, most of the params is automatic.


-- Peter


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Nova-T 500 user experience

[Richard Lithvall]

Arnold Schulz wrote:

A new survey to Nova-T 500 owners: how many USB-hubs do you have in your
system?...


Strange - am I the only one those Nova-T-500 has 3 (!) USB host adapters?


It's the same USB-hub but looks like three (one USB2 and two USB1.1)
In my system I have not compiled support for UHCI (USB1.1) so my lsusb 
only show the EHCI (USB2) hub.


lspci:

:01:07.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 
1.1 Controller (rev 61)
:01:07.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 
1.1 Controller (rev 61)

:01:07.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)


lsusb -v|grep iProduct:

  iProduct2 WinTV Nova-DT
  iProduct2 EHCI Host Controller


/Richard

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Nova-T 500 user experience

[Juha Ruotsalainen]

While surfing, or clutching, at straws, I found a thread related to Nova-T
500 on a Finnish forum (DVDPlaza). Someone mentioned there that his Nova-T
500 was fully working. His box is running KnoppMyth. I posted a query for
this guy, let's see what his answer is.

On 3/8/07, Juha Ruotsalainen <[EMAIL PROTECTED]> wrote:


I don't think so. Running lsusb gives me similar results. Could the 3rd
host adapter be the remote control (which is, AFAIK, currently not working
in Linux).

On 3/8/07, Arnold Schulz <[EMAIL PROTECTED]> wrote:
>
> > A new survey to Nova-T 500 owners: how many USB-hubs do you have in
> > your
> > system?...
>
> Strange - am I the only one those Nova-T-500 has 3 (!) USB host
> adapters?
>
> You may check my "lsusb -v" listing at
> http://ats.dyn.bawue.de/arny/lsusb-v
>
> Summary:
>
> Bus 001 Dev 001 EHCI host controller on Nova-T-500 (PCI :00:0d.2)
> Bus 001 Dev 003 "Hauppauge" device
> (not Dev 002 any longer due to disconnect bug)
>
> Bus 002 Dev 001 UHCI host controller on motherboard (PCI 00:04.2)
>
> Bus 003 Dev 001 UHCI host controller on motherboard (PCI 00:04.3)
> Bus 003 Dev 003 Canon Printer
> (not Dev 002 any longer due to manual disconnect/reconnect)
>
> Bus 004 Dev 001 UHCI Nova-T-500, apparently unused (PCI 00:0d.0)
> Bus 005 Dev 001 UHCI Nova-T-500, apparently unused (PCI 00:0d.1)
>
>
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>


Cheers,
--
jussi



--
jussi
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Torbjörn Lundquist]

Hmm. So this should do it:

dvbstream -f 522000 -o -tm 8 0 1248 1249 5180 > recordings/test.ts

But VLC does not play that file (mplayer does). I tried to add almost all
pids in the stream but with no luck with VLC.

Here are the pids I got from dvbsnoop:

dvbsnoop -s pidscan
dvbsnoop V1.4.00 -- http://dvbsnoop.sourceforge.net/

-
Transponder PID-Scan...
-
PID found:0 (0x)  [SECTION: Program Association Table (PAT)]
PID found:1 (0x0001)  [SECTION: Conditional Access Table (CAT)]
PID found:   18 (0x0012)  [SECTION: Event Information Table (EIT) - other
transport stream, present/following]
PID found:   41 (0x0029)  [SECTION: DVB CA message section (EMM/ECM)]
PID found:   57 (0x0039)  [SECTION: DVB CA message section (EMM/ECM)]
PID found:  870 (0x0366)  [SECTION: Program Map Table (PMT)]
PID found:  871 (0x0367)  [SECTION: MHP- Application Information Table
(AIT)]
PID found:  872 (0x0368)  [SECTION: DSM-CC - Download Data Messages (DDB)]
PID found:  878 (0x036e)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found:  879 (0x036f)  [PES: ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
PID found:  880 (0x0370)  [SECTION: Program Map Table (PMT)]
PID found: 1002 (0x03ea)  [SECTION: DSM-CC - Download Data Messages (DDB)]
PID found: 1004 (0x03ec)  [PES: private_stream_1]
PID found: 1010 (0x03f2)  [SECTION: Program Map Table (PMT)]
PID found: 1011 (0x03f3)
PID found: 1012 (0x03f4)  [SECTION: DSM-CC - Download Data Messages (DDB)]
PID found: 1016 (0x03f8)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found: 1017 (0x03f9)  [PES: private_stream_1]
PID found: 1018 (0x03fa)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found: 1019 (0x03fb)  [PES: ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
PID found: 1021 (0x03fd)  [SECTION: MHP- Application Information Table
(AIT)]
PID found: 1022 (0x03fe)  [SECTION: DSM-CC - Download Data Messages (DDB)]
PID found: 1026 (0x0402)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found: 1027 (0x0403)  [PES: private_stream_1]
PID found: 1028 (0x0404)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found: 1029 (0x0405)  [PES: ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
PID found: 1241 (0x04d9)  [SECTION: MHP- Application Information Table
(AIT)]
PID found: 1242 (0x04da)  [SECTION: DSM-CC - U-N messages (DSI or DII)]
PID found: 1248 (0x04e0)  [PES: ISO/IEC 13818-3 or ISO/IEC 11172-3 audio
stream]
PID found: 1249 (0x04e1)  [PES: ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
PID found: 1280 (0x0500)  [SECTION: Program Map Table (PMT)]
PID found: 1290 (0x050a)  [SECTION: Program Map Table (PMT)]
PID found: 5050 (0x13ba)  [SECTION: Program Map Table (PMT)]
PID found: 5070 (0x13ce)  [SECTION: Program Map Table (PMT)]
PID found: 5180 (0x143c)  [SECTION: Program Map Table (PMT)]
PID found: 8191 (0x1fff)



2007/3/8, Måns Rullgård <[EMAIL PROTECTED]>:


Peter Fassberg <[EMAIL PROTECTED]> writes:

>> But how do I record a specific program in a mux? If I point out the
video
>> and sound pids for a program with
>>
>> dvbstream -f 522000 -o -tm 8 1249 1248 > recordings/test.ts
>>
>> The stream does not play in VLC.
>
> Exact.  That is not a "true" TS as some mandatory PID's is missing.
> PAT/PMT/SDT/NIT/SID ...  I'm sure there is someone who can explain
> exactly what PIDs you need to get i compliant TS.

You need the PAT, PMT, and whatever audio and video belong to your
program.  The PAT always has PID 0, and lists the PID of the PMT for
each program in the mux.  The PMT then lists the PIDs of each
audio/video stream in the program.  The NIT, SDT etc. only contain
meta-information not necessary for playback.

--
Måns Rullgård
[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Nova-T 500 user experience

[Arnold Schulz]

A new survey to Nova-T 500 owners: how many USB-hubs do you have in 
your

system?...


Strange - am I the only one those Nova-T-500 has 3 (!) USB host 
adapters?


You may check my "lsusb -v" listing at 
http://ats.dyn.bawue.de/arny/lsusb-v


Summary:

Bus 001 Dev 001 EHCI host controller on Nova-T-500 (PCI :00:0d.2)
Bus 001 Dev 003 "Hauppauge" device
   (not Dev 002 any longer due to disconnect bug)

Bus 002 Dev 001 UHCI host controller on motherboard (PCI 00:04.2)

Bus 003 Dev 001 UHCI host controller on motherboard (PCI 00:04.3)
Bus 003 Dev 003 Canon Printer
   (not Dev 002 any longer due to manual disconnect/reconnect)

Bus 004 Dev 001 UHCI Nova-T-500, apparently unused (PCI 00:0d.0)
Bus 005 Dev 001 UHCI Nova-T-500, apparently unused (PCI 00:0d.1)



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Måns Rullgård]

Peter Fassberg <[EMAIL PROTECTED]> writes:

>> But how do I record a specific program in a mux? If I point out the video
>> and sound pids for a program with
>>
>> dvbstream -f 522000 -o -tm 8 1249 1248 > recordings/test.ts
>>
>> The stream does not play in VLC.
>
> Exact.  That is not a "true" TS as some mandatory PID's is missing.
> PAT/PMT/SDT/NIT/SID ...  I'm sure there is someone who can explain
> exactly what PIDs you need to get i compliant TS.

You need the PAT, PMT, and whatever audio and video belong to your
program.  The PAT always has PID 0, and lists the PID of the PMT for
each program in the mux.  The PMT then lists the PIDs of each
audio/video stream in the program.  The NIT, SDT etc. only contain
meta-information not necessary for playback.

-- 
Måns Rullgård
[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Peter Fassberg]

> But how do I record a specific program in a mux? If I point out the video
> and sound pids for a program with
>
> dvbstream -f 522000 -o -tm 8 1249 1248 > recordings/test.ts
>
> The stream does not play in VLC.

Exact.  That is not a "true" TS as some mandatory PID's is missing.
PAT/PMT/SDT/NIT/SID ...  I'm sure there is someone who can explain
exactly what PIDs you need to get i compliant TS.

You need to include some more PIDs, or use another player.

I use mplayer which is more "forgiving".  http://www.mplayerhq.hu/



-- Peter


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Torbjörn Lundquist]

That solved it! Thanks.

But how do I record a specific program in a mux? If I point out the video
and sound pids for a program with

dvbstream -f 522000 -o -tm 8 1249 1248 > recordings/test.ts

The stream does not play in VLC.

Regards
/Torbjörn


2007/3/8, Peter Fassberg <[EMAIL PROTECTED]>:



> Ok, I've installed dvbstream but the frequency seems wrong. Here is one
row
> from channels.conf generated with dvbscan
>
>
>
SVT24:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_
> INTERVAL_1_8:HIERARCHY_NONE:1249:1248:5180
>
> So, I assume 52200 is the frequency? But when I run:

Correct.  Mux 1 is on 522 MHz in Motala.


> dvbstream -f 52200 -o -tm 8 8192 > recordings/test.ts
>
> I got an empty file and this:
> dvbstream v0.5 - (C) Dave Chapman 2001-2004
> Released under the GPL.
> Latest version available from http://www.linuxstb.org/
> Using DVB card "Zarlink MT352 DVB-T"
> tuning DVB-T (in United Kingdom) to -1986010112 Hz
> polling
> Getting frontend event
> FE_STATUS:
> polling
> Getting frontend event
> FE_STATUS: FE_HAS_SIGNAL
>
> The frequency seems wrong?

Yes, it seems...

Try using kHz anyway (522000).


I'm using another version of dvbstream:

[EMAIL PROTECTED]:~$ dvbstream -f 73000 1018 1019
dvbstream v0.6 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Tuning to 73000 Hz
Using DVB card "DST DVB-T", freq=73000
tuning DVB-T (in United Kingdom) to 73000 Hz, Bandwidth: 8
Getting frontend status
Event:  Frequency: 73000
Signal strength: 25088
SNR: 20480
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI
FE_HAS_SYNC


// Peter


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Peter Fassberg]

> Ok, I've installed dvbstream but the frequency seems wrong. Here is one row
> from channels.conf generated with dvbscan
>
>
> SVT24:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_
> INTERVAL_1_8:HIERARCHY_NONE:1249:1248:5180
>
> So, I assume 52200 is the frequency? But when I run:

Correct.  Mux 1 is on 522 MHz in Motala.


> dvbstream -f 52200 -o -tm 8 8192 > recordings/test.ts
>
> I got an empty file and this:
> dvbstream v0.5 - (C) Dave Chapman 2001-2004
> Released under the GPL.
> Latest version available from http://www.linuxstb.org/
> Using DVB card "Zarlink MT352 DVB-T"
> tuning DVB-T (in United Kingdom) to -1986010112 Hz
> polling
> Getting frontend event
> FE_STATUS:
> polling
> Getting frontend event
> FE_STATUS: FE_HAS_SIGNAL
>
> The frequency seems wrong?

Yes, it seems...

Try using kHz anyway (522000).


I'm using another version of dvbstream:

[EMAIL PROTECTED]:~$ dvbstream -f 73000 1018 1019
dvbstream v0.6 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Tuning to 73000 Hz
Using DVB card "DST DVB-T", freq=73000
tuning DVB-T (in United Kingdom) to 73000 Hz, Bandwidth: 8
Getting frontend status
Event:  Frequency: 73000
Signal strength: 25088
SNR: 20480
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC


// Peter


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Torbjörn Lundquist]

Ok, I've installed dvbstream but the frequency seems wrong. Here is one row
from channels.conf generated with dvbscan


SVT24:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_
INTERVAL_1_8:HIERARCHY_NONE:1249:1248:5180

So, I assume 52200 is the frequency? But when I run:

dvbstream -f 52200 -o -tm 8 8192 > recordings/test.ts

I got an empty file and this:
dvbstream v0.5 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Using DVB card "Zarlink MT352 DVB-T"
tuning DVB-T (in United Kingdom) to -1986010112 Hz
polling
Getting frontend event
FE_STATUS:
polling
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL

The frequency seems wrong?

Hope you can help me.
/Torbjörn



2007/3/8, Peter Fassberg <[EMAIL PROTECTED]>:



Hi!

I'm also using dvbstream with great success.


>   dvbstream -f 522000 -o -tm 8 8192 > /tmp/test.ts

When using DVB-T the frequency should be given in Hz, 52200.




-- Peter Fassberg


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Adjusting drivers for slow CPUs - buffer overruns suspected

[Tim Hewett]

I am wondering if there are ways to adjust the DVB drivers to suit a  
slow CPU.


The background is that I have two Technisat SkyStar2 DVB-S cards in a  
PIII 550MHz PC. If I try to record an entire transport stream the  
recording suffers from drops and gaps, something which doesn't happen  
when recording one video and audio PID, presumably because their five  
hardware PID filters are doing the hard work.


Before upgrading to the 2.6 kernel (ages ago) the same PC would  
happily record an entire transport stream concurrently on each card  
without any data loss, so it doesn't seem as if the PC is  
fundamentally running out of steam. Something changed in the DVB  
drivers for the 2.6 kernel which started causing problems it seems.


Now I've added a Twinhan VP-1025, which has no hardware filters at  
all apparently, I'm getting data drops whether I record an entire  
transport stream or just one audio and video PID, I guess because the  
filtering is done in the CPU.


So I'm wondering if there are tweaks which I can make to the DVB  
drivers, maybe to increase buffer sizes, or some other adjustment, to  
try to stop these drops happening.


Any ideas?

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Peter Fassberg]

Hi!

I'm also using dvbstream with great success.


>   dvbstream -f 522000 -o -tm 8 8192 > /tmp/test.ts

When using DVB-T the frequency should be given in Hz, 52200.




-- Peter Fassberg


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Bad TS from dvb-t recording?

[Andrea Venturi]

Torbjörn Lundquist wrote:
> Hi,
>  
> I'm trying to make a recording from my dvb-t card (Avermedia). I do like
> this:
>  
>> tzap -r -c channels.conf -t 5 -o test.ts SVT24
>  
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file 'channels.conf'
> tuning to 52200 Hz
> video pid 0x04e1, audio pid 0x04e0
> status 00 | signal 58cf | snr  | ber  | unc  |
> copied 1708168 bytes (333 Kbytes/sec)
> status 1f | signal f1cf | snr c0c0 | ber  | unc  |
> FE_HAS_LOCK
>  
> But then I cannot view the file in VLC for instance. If I run dvbsnoop
> on it I receive some errors, for instance:
>  
> MPEG-DescriptorTag: 63 (0x3f)  [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
> Descriptor_length: 199 (0xc7)
>   > ERROR: unimplemented descriptor (mpeg context), Report!
>  
> I live in Sweden and receive the signal from the Motala-tranciever.
>  
> What am I doing wrong? Or can I use some other program for recording (I
> tried mencoder without success)?
>  

i just try a guess. i don't use tzap.

maybe tzap doesn't dump the relevant tables (PAT PMT) so VLC can't
reconstruct the service.
i see indeed only video and audio pids in the log.

can you try to dump the complete transport stream using maybe dvbstream

you can try with the one available in your linux distro, but if it does
not work well you can try from the cvs source:

  http://sourceforge.net/projects/dvbtools/

get the code straight from the cvs because it's newer then the (old)
release,

when you have a binary, give this command:

  dvbstream -f 522000 -o -tm 8 8192 > /tmp/test.ts

then after some time, break the application with CTRL-C.

beware, this should be a 24Mbps stream, so it will waste some space in
the disk!

then feed it with vlc

  vlc /tmp/test.ts

and if it works you can switch on every service of the mux with the menu
Navigation.

hope it helps.

bye

andrea venturi

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Anubis Electronics "Lifeview"(0x10fd:0x1513)

[Pierre Willenbrock]

Hi Hartmut,

Hartmut Hackmann schrieb:
> Hi, Pierre
> 
> Pierre Willenbrock schrieb:
>> Hartmut Hackmann schrieb:
>>> Hi,
>>>
>>> Aapo Tahkola schrieb:
 On Sat, 3 Mar 2007 03:10:41 +0200
 Aapo Tahkola <[EMAIL PROTECTED]> wrote:

> On Fri, 02 Mar 2007 23:06:15 +0100
> Pierre Willenbrock <[EMAIL PROTECTED]> wrote:
>
>> Michael Krufky schrieb:
>>> Pierre Willenbrock wrote:
 Hi list,

 I am owner of a "MSI DIGIVOX mini-II". I got it to work using the
 attached patch and firmware. The patch and firmware are the
 result of analyzing some usb logs from windows.

 The patch breaks all users of tda10046, as i don't understand how
 that chip is supposed to work. The same goes for my driver
 implementation of the Philips 8275a.

 So this mess needs to be fixed before it can go into the
 repository.

 The patch is against a fresh hg checkout from
 http://linuxtv.org/hg/v4l-dvb at 2007-02-22 21:00 UTC.

 Regards,
   Pierre
>>> Pierre-
>>>
>>> I am very happy to hear that you got this device working...
>>> Interestingly enough, we have already created a new tda827x dvb fe
>>> module, which might be better for your device...  This new tda827x
>>> module has not yet been merged into the master v4l-dvb repository,
>>> but it will be soon.  Could you try to use the code located in:
>>>
>>> http://linuxtv.org/hg/~hhackmann/v4l-dvb
>>>
>>> The tda827x module will be able to detect the difference between
>>> the tda8275 and the tda8275a ...  You do not have to fill the
>>> callback functions in the config struct -- that is really meant as
>>> a hack for some required GPIO handling in the saa7134-dvb driver
>>> for input switching.
>>>
>>> If you can generate a new patch against the repository above, it
>>> would make it _much_ easier to integrate your patch into the
>>> sources.   After you get that done, we can work out the tda1004x
>>> differences.
>>>
>>> You might also want to speak to aett and friedrich, regulars of
>>> the #linuxtv irc chat room on irc.freenode.net ... aet is the
>>> author of the m920x driver, and friedrich has the same device
>>> that you have. They have been working on it, but haven't yet
>>> gotten successful results.
>>>
>>> Good work!  Hopefully we can clean this up after you generate a
>>> new patch using the tda827x module from hhackmann's repository.
>>>
>>> Regards,
>>>
>>> Mike Krufky
>>>
>> Hi Mike and Hartmut,
>>
>> this time, the patch does not change tda827x.c at all. I fiddled
>> with the PHY2 value in tda1004x.c and found it to be related to the
>> IF(there seems to be some factor between the IF and PHY2 introduced
>> somewhere else). This leaves some differences in tda1004x.c. I don't
>> know what to do with these, so i would be glad to get any hints.
> Updated patch. I'm fine with these m920x changes.
>
 Signed-of-by: Aapo Tahkola <[EMAIL PROTECTED]>

>>> PHY2 indeed defines the IF frequency relative to the sampling frequency.
>>> If you need a different value here, the reason most probably is the
>>> following:
>>> In some countries, i.e. Britain, France and Australia, the tranmitters
>>> are +/- 166kHz off the channel center frequency. This isn't documented.
>>> You can compensate this by simply tuning to the actually used channel
>>> center frequency.
>>>
>> The windows driver used an IF of 4.75MHz for UHF, so i resorted to
>> hardcoding it to 4.75MHz in tda827x.c, while using PHY2, WREF and the
>> other settings from an usb log. After changing PHY2 the hack in
>> tda827x.c is no longer needed. This leaves me with these settings for
>> UHF(cannot test VHF -- i don't get any channels in that range):
>>
>> CONFPLL2=7 //52MHz sampling clock?
> 
> yes
> 
>> FREQ_PHY2=0xc4f
>> TIME_WREF1..5=0x5b, 0x02, 0xd0, 0x2d, 0x03
>>
> This gives a IF center frequency of 5.0MHz and a bandwidth of 8MHz.
> 
>>> A note: Some channel decoders can compensate this offset automatically.
>>> The tda10046 needs assistance from the driver for this. This is not
>>> built in yet.
>>>
>>> Hartmut
>> Regards,
>>   Pierre
>>
> The only difference is that you use a sampling clock of 52MHz while the
> original driver uses 48MHz. This btw is the same as the Philips default
> driver for windows uses.
> We could have a long discussion now about ideal sampling frequencies but
> believe me: as long as your board does not have a weird interference
> problem, 48MHz is the better choice for the sampling clock and adding a
> additional one would only make life more difficult.

I thought i checked that it does not easily work with 48MHz, but
obviously i did not. The reception part works now perfectly without any
modifications.

This leaves me with a last difference:

CONF_TRIS

[linux-dvb] Bad TS from dvb-t recording?

[Torbjörn Lundquist]

Hi,

I'm trying to make a recording from my dvb-t card (Avermedia). I do like
this:


tzap -r -c channels.conf -t 5 -o test.ts SVT24


using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file 'channels.conf'
tuning to 52200 Hz
video pid 0x04e1, audio pid 0x04e0
status 00 | signal 58cf | snr  | ber  | unc  |
copied 1708168 bytes (333 Kbytes/sec)
status 1f | signal f1cf | snr c0c0 | ber  | unc  |
FE_HAS_LOCK

But then I cannot view the file in VLC for instance. If I run dvbsnoop on it
I receive some errors, for instance:

MPEG-DescriptorTag: 63 (0x3f)  [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
   Descriptor_length: 199 (0xc7)
 > ERROR: unimplemented descriptor (mpeg context), Report!

I live in Sweden and receive the signal from the Motala-tranciever.

What am I doing wrong? Or can I use some other program for recording (I
tried mencoder without success)?

/Torbjörn
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Linux DVB + PCI bus extender (Magma) - Anyone?

[Mark Buechler]

Thanks for the info. I was a bit worried about bandwidth but I figured not
many cards are going to be streaming the full transport - certainly not all
at once, anyway, so I think I'm safe there. The only analog capture cards I
own are mpeg ones so that should be good.

Thanks, Mark.

On 3/7/07, timecop <[EMAIL PROTECTED]> wrote:


Magma cases, while having their own PCI bridge, still route through a
single slot.
Which means, as long as you're not pushing the 133meg/second PCI limit
- you will be fine. A typical 40mbit full transponder is ~5meg/second,
so even with 4 cards tuning there shouldn't be a problem.

Note, this is only for DVB cards, when you're dealing with analog
capture (non-mpeg) boards sending uncompressed video, PCI bandwidth
gets used up real quick.

-t

On 3/8/07, CityK <[EMAIL PROTECTED]> wrote:
> Mark Buechler wrote:
> > I suppose nobody has a comment or suggestion on this.. I guess I'm on
> > my own.
> >
> > - Mark.
> >
> > On 3/6/07, *Mark Buechler* < [EMAIL PROTECTED]
> > > wrote:
> >
> > I'm looking to purchase a PCI bus extender by Magma to use with my
> > Nexus-S, SkayStar2 and Twinhan cards. Before I spend the money,
> > however, I wanted to cover my bases and make sure I'm not going to
> > run into any latency or timing issues with slots in the extender.
> > Has anyone has success using one of these with any DVB cards under
> > Linux?
> >
> > Thanks in advance, Mark.
> >
>
> - Probably not a lot of people with first hand experience with such a
> setup.  Second, the other problem is that the typical end user doesn't
> hang around here -- users tend to ask a question to a problem that they
> have and then, once they receive an answer, are never to be heard from
> again on the list
> - there are few developers here, and their time is tight ... so giving
> one days allowance is not necessarily indicative that you are on your
> own.sometimes you have to be patient
>
> In any regard, I don't know if you would run into similar problems with
> an extender, but it might be worthwhile to browse through these threads
> dealing with a problem related to using a pci riser:
> http://www.linuxtv.org/pipermail/linux-dvb/2007-February/016027.html
> which stems from this thread:
> http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015936.html
>
> If that strikes you as a possibility, then consider searching (google
> works well) the achieves for other incidences with extenders or risers.
>
>
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Linux DVB + PCI bus extender (Magma) - Anyone?

[Mark Buechler]

Thanks for your reply. Actually, I've posted a few questions and rarely get
a response even after several weeks. I needed feedback on this question
quickly though or I loose the opportunity to purchase the unit.

I don't believe those posts have anything to do with my question but you
never know. They'll be a good reference should I run into issues.

Thanks, Mark.

On 3/7/07, CityK <[EMAIL PROTECTED]> wrote:


Mark Buechler wrote:
> I suppose nobody has a comment or suggestion on this.. I guess I'm on
> my own.
>
> - Mark.
>
> On 3/6/07, *Mark Buechler* < [EMAIL PROTECTED]
> > wrote:
>
> I'm looking to purchase a PCI bus extender by Magma to use with my
> Nexus-S, SkayStar2 and Twinhan cards. Before I spend the money,
> however, I wanted to cover my bases and make sure I'm not going to
> run into any latency or timing issues with slots in the extender.
> Has anyone has success using one of these with any DVB cards under
> Linux?
>
> Thanks in advance, Mark.
>

- Probably not a lot of people with first hand experience with such a
setup.  Second, the other problem is that the typical end user doesn't
hang around here -- users tend to ask a question to a problem that they
have and then, once they receive an answer, are never to be heard from
again on the list
- there are few developers here, and their time is tight ... so giving
one days allowance is not necessarily indicative that you are on your
own.sometimes you have to be patient

In any regard, I don't know if you would run into similar problems with
an extender, but it might be worthwhile to browse through these threads
dealing with a problem related to using a pci riser:
http://www.linuxtv.org/pipermail/linux-dvb/2007-February/016027.html
which stems from this thread:
http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015936.html

If that strikes you as a possibility, then consider searching (google
works well) the achieves for other incidences with extenders or risers.



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Re: Nova-T 500 Channel scanning + EIT + Kernel oops...

[Antti P Miettinen]

"Eduard Huguet" <[EMAIL PROTECTED]> writes:
>I don't know if kernel oops is related to USB disconnection.

Just look for "USB disconnect" in /var/log/kern.log* or dmesg output.

> However, it
> seems reasonable to suspect that the EIT reception has something to do with
> this problems, as I never experienced problems with this card before.

Could be. I've tried to look at the usbmon logs I've taken from the
disconnects and it seems that there is always a control message just
before the first failing (EPIPE) transaction (always bulk). The EPROTO
failure can happen either for bulk or control transaction after the
EPIPE failure.

I made an async version of the halt clearing but it still does not
prevent disconnects. I put a diff at

  http://brigitte.dna.fi/~apm/t500-stall-clear-async.diff

but as with the sync diff, not intented to be applied, just for
looking at :)

It does sometimes prevent a disconnect, e.g. here:

c359a7c0 1970475991 S Co:002:00 s 40 03   0006 6 = 0314000b ab20
f7629440 1970476114 C Bi:002:03 -32 40448 = 471fff10    
   
f7546ec0 1970476132 S Co:002:00 s 02 01  0083  0
c359a7c0 1970476607 C Co:002:00 0 6 >
f7546ec0 1970476618 C Co:002:00 0 0

But not always. Here's a sample where we have REQUEST_ENABLE_VIDEO
just before the EPIPE and the EPROTO happens for a bulk transaction:

f79380c0 582051665 S Co:002:00 s 40 0f   0004 4 = 0f101300
f79380c0 582051830 C Co:002:00 0 4 >
f74acdc0 582053974 C Bi:002:03 -32 40448 = 4701311e 4527d078 77ad90fa 0c6c2255 
353a8670 ebe754f4 34a7631f 0b869dc8
f74acbc0 582053986 S Co:002:00 s 02 01  0083  0
f77413c0 582054733 C Bi:002:02 -71 6144 = 47d9c4fe dad86b80 f3dbcf65 6d258bd4 
23eb3d04 58fd9791 29741794 e87cbb16

and here we have REQUEST_I2C_WRITE before the EPIPE and the EPROTO
failure happens for a control transaction (the I2C write):

f79c1cc0 2568107515 S Co:002:00 s 40 03   0006 6 = 03140006 0019
f755f140 2568107736 C Bi:002:03 -32 40448 = 47023110 26e11251 26435261 0ce78c29 
44235a42 35b08108 94a956b2 f58cb55d
f7546ec0 2568107748 S Co:002:00 s 02 01  0083  0
f79c1cc0 2568108697 C Co:002:00 -71 6 >

So what triggers the failures could be related to how control
transactions get interleaved with streaming transactions, but then
again there is obviously a lot of interleaved streaming/control
activity that proceeds just fine. I haven't figured out any difference
in the patterns that trigger the failure and patterns that do not. I
have couple of gigs of logs if someone wants to analyze them :-)

Hmm.. would some little test program be useful? I.e. cause those
control transfers via some ioctls? Or would it be possible to use some
existing tool?

--
http://www.iki.fi/~ananaza/


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Nova-T 500 user experience

[Eduard Huguet]

Subject:
Hi there, again,

A new survey to Nova-T 500 owners: how many USB-hubs do you have in your
system? My system has three: USB 1.1 integrated on motherboard, USB 2.0 on
PCI-slot (for Nebula's USB DVB), and Nova-T 500. My reasoning: could this
really be a USB-problem, that only manifests itself with these kinds of
setups.

Slaínte,
--




Only the integrated USB of my motherboard (apart from the card itself). This
is an ASUS P1-AH2 barebone PC, which has only 4 USB  ports, 2 in front and 2
backwards. I don't know if they belong to the same 'host', though (probably
not).

Cheers
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [PATCH] v4l-dvb: add $DESTDIR support

[Ludwig Nussel]

Trent Piepho wrote:
> > Following patch adds $DESTDIR support so one can install the kernel
> > modules into a directory other than / as non-root user. That's
> > useful when building an rpm or compiling for a different machine.
> >
> > Signed-off-by: Ludwig Nussel <[EMAIL PROTECTED]>
> >
> > diff -r 44676649301d v4l/scripts/make_makefile.pl
> > --- a/v4l/scripts/make_makefile.pl  Tue Mar 06 19:15:19 2007 +0100
> > +++ b/v4l/scripts/make_makefile.pl  Wed Mar 07 14:35:40 2007 +0100
> > @@ -134,12 +134,12 @@ print OUT "[EMAIL PROTECTED] --strip-debug \$(in
> >
> >  while (my ($dir, $files) = each %instdir) {
> > print OUT "[EMAIL PROTECTED] -e \"\\nInstalling \$(KDIR26)/$dir 
> > files:\"\n";
> > -   print OUT "[EMAIL PROTECTED] -d \$(KDIR26)/$dir\n";
> > +   print OUT "[EMAIL PROTECTED] -d \$(DESTDIR)\$(KDIR26)/$dir\n";
> > print OUT "[EMAIL PROTECTED] i in ", join(' ', keys %$files), ";do ";
> > print OUT "if [ -e \"\$\$i\" ]; then echo -n \"\$\$i \";";
> > -   print OUT " install -m 644 -c \$\$i \$(KDIR26)/$dir; fi; done; 
> > echo;\n\n";
> > +   print OUT " install -m 644 -c \$\$i \$(DESTDIR)\$(KDIR26)/$dir; fi; 
> > done; echo;\n\n";
> >  }
> 
> This part looks ok.
> 
> > -print OUT "\t/sbin/depmod -a \${KERNELRELEASE}\n\n";
> > +print OUT "\tif [ -w / ]; then /sbin/depmod -a \${KERNELRELEASE}; fi\n\n";
> 
> This doesn't seem correct.  Shouldn't it be:
> print OUT "\t/sbin/depmod -a \$(KERNELRELEASE) \$(if \$(DESTDIR),-b 
> \$(DESTDIR))\n\n";

One needs to run depmod when the modules get installed to their final location.
$DESTDIR is incomplete so it doesn't make sense to run depmod here already.

> >  # Creating Remove rule
> >  print OUT "media-rminstall::\n";
> 
> Seems like the rminstall rule should use DESTDIR too.

It's not that useful there as you can just rm -rf $DESTDIR. Anyways here's a
patch that includes rminstall:

diff -r f71d56dfeb0d v4l/scripts/make_makefile.pl
--- a/v4l/scripts/make_makefile.pl  Wed Mar 07 12:28:33 2007 -0200
+++ b/v4l/scripts/make_makefile.pl  Thu Mar 08 08:59:11 2007 +0100
@@ -134,12 +134,12 @@ print OUT "[EMAIL PROTECTED] --strip-debug \$(in
 
 while (my ($dir, $files) = each %instdir) {
print OUT "[EMAIL PROTECTED] -e \"\\nInstalling \$(KDIR26)/$dir 
files:\"\n";
-   print OUT "[EMAIL PROTECTED] -d \$(KDIR26)/$dir\n";
+   print OUT "[EMAIL PROTECTED] -d \$(DESTDIR)\$(KDIR26)/$dir\n";
print OUT "[EMAIL PROTECTED] i in ", join(' ', keys %$files), ";do ";
print OUT "if [ -e \"\$\$i\" ]; then echo -n \"\$\$i \";";
-   print OUT " install -m 644 -c \$\$i \$(KDIR26)/$dir; fi; done; 
echo;\n\n";
+   print OUT " install -m 644 -c \$\$i \$(DESTDIR)\$(KDIR26)/$dir; fi; 
done; echo;\n\n";
 }
-print OUT "\t/sbin/depmod -a \${KERNELRELEASE}\n\n";
+print OUT "\tif [ -w / ]; then /sbin/depmod -a \${KERNELRELEASE}; fi\n\n";
 
 # Creating Remove rule
 print OUT "media-rminstall::\n";
@@ -149,13 +149,13 @@ while ( my ($dir, $files) = each(%instdi
print OUT "[EMAIL PROTECTED] -e \"\\nRemoving old \$(KDIR26)/$dir 
files:\"\n";
print OUT "[EMAIL PROTECTED]'", join(' ', keys %$files), "'; ";
 
-   print OUT "for i in \$\$files;do if [ -e \$(KDIR26)/$dir/\$\$i ]; then 
";
+   print OUT "for i in \$\$files;do if [ -e 
\$(DESTDIR)\$(KDIR26)/$dir/\$\$i ]; then ";
print OUT "echo -n \"\$\$i \";";
-   print OUT " rm \$(KDIR26)/$dir/\$\$i; fi; done; ";
+   print OUT " rm \$(DESTDIR)\$(KDIR26)/$dir/\$\$i; fi; done; ";
 
-   print OUT "for i in \$\$files;do if [ -e \$(KDIR26)/$dir/\$\$i.gz ]; 
then ";
+   print OUT "for i in \$\$files;do if [ -e 
\$(DESTDIR)\$(KDIR26)/$dir/\$\$i.gz ]; then ";
print OUT "echo -n \"\$\$i.gz \";";
-   print OUT " rm \$(KDIR26)/$dir/\$\$i.gz; fi; done; echo;\n\n";
+   print OUT " rm \$(DESTDIR)\$(KDIR26)/$dir/\$\$i.gz; fi; done; 
echo;\n\n";
 }
 
 # Print dependencies of Makefile.media

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\   SUSE Labs
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: Nova-T 500 user experience

[Richard Lithvall]

Juha Ruotsalainen wrote:
A new survey to Nova-T 500 owners: how many USB-hubs do you have in your 
system?


Just the one integrated on the Nova-T 500 (I've disabled the motherboard 
USB-hub).


/Richard

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Re: Nova-T 500 user experience

[Juha Ruotsalainen]

Hi there, again,

A new survey to Nova-T 500 owners: how many USB-hubs do you have in your
system? My system has three: USB 1.1 integrated on motherboard, USB 2.0 on
PCI-slot (for Nebula's USB DVB), and Nova-T 500. My reasoning: could this
really be a USB-problem, that only manifests itself with these kinds of
setups.

Slaínte,
--
jussi
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb