Re: [linux-dvb] SAA 7162 PCI Express support update / NXP semi-"GPL" and copyrights
Steven Ellis wrote: >> Richard Dale wrote: >>> Hi everybody who has asked about SAA7162 drivers in the past. Here's an >>> update on how far I've got. >>> 3. Obtain from NXP a full data sheet of all of the components on the >>> card >>> (every register, line etc.) and ignore their reference driver. >> Working with this for the VP-6090 (QuattroS), driver not ready yet >> > Any idea on an eta of something we can test? Have a driver which is loadable now, doesn't do much now. > Also what cards are you expecting this to support in addition to the > QuattroS? Some 7160 based devices to go ahead initially, if we get this to work. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] SAA 7162 PCI Express support update / NXP semi-"GPL" and copyrights
> Richard Dale wrote: >> Hi everybody who has asked about SAA7162 drivers in the past. Here's an >> update on how far I've got. > >> 3. Obtain from NXP a full data sheet of all of the components on the >> card >> (every register, line etc.) and ignore their reference driver. > > Working with this for the VP-6090 (QuattroS), driver not ready yet > Any idea on an eta of something we can test? Also what cards are you expecting this to support in addition to the QuattroS? Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend DVB-C budget-CI tuning problem
Date: Tue, 29 May 2007 00:15:00 +0100 (BST) From: "Simon Baxter" <[EMAIL PROTECTED]> Subject: [linux-dvb] Technotrend DVB-C budget-CI tuning problem To: linux-dvb@linuxtv.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain;charset=iso-8859-1 > Hello, > Seems my Technotrend DVB-C budget-CI cannot find all the channels under Linux that it finds under Windows > Neither dvbscan nor kaffeine finds anything at a frequency (154 MHz, 6900 syms, 128QAM) where the included windows software does. > Running kernel 2.6.21.2 (Gentoo-sources) on a 64-bit Gentoo system (Core 2 Duo). > I'll help if I can have you tried changing the inversion settings for each transponder? I've had some similar experiences. off-topic question for you. Are you able to decrypt any pay-channels? I have the same hardware, can scan for channels, but have never been able to decrypt under Linux (only Windows) I did not buy the CI interface. It also says in the kernel config that the decoding functionality is not supported ATM. Now, I believe this could have something to do with my problem: http://www.linuxtv.org/pipermail/linux-dvb/2007-May/017722.html Will try a 2.6.19 kernel now, in a 32-bit machine. And to make it clear, I did add the modifications mentioned at http://www.linuxtv.org/wiki/index.php/DVB-C_PCI_Cards for this card. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S- and DVB-S2-streams with TT3200
Am Dienstag, den 29.05.2007, 01:57 +0200 schrieb hermann pitton: > Am Dienstag, den 29.05.2007, 01:34 +0200 schrieb Markus Rechberger: > > On 5/28/07, Peter Magellan <[EMAIL PROTECTED]> wrote: > > > > I just removed those and it worked somehow, still having bad problems> > > > about locking and every time you acan channels it find diffrent ones.> Is > > > it > > > possible to get this TT3200 card work like normal technotrend> budget > > > DVB-S1 > > > card? on windows atleast all technotrends have same> drivers. > > > > > > That's because in Linux, people have nothing better to do than bitch, act > > > I'm-holier-than-thou, > > > and don't spend time designing a good driver/architecture model first > > > before > > > coding spaghetti > > > non-working code. > > > > > > > I wouldn't overall say linux, but I can say that's the truth with v4l > > and dvb at least. > > People who fundamentally want to change something are not welcome here > > since some people who've been with that project for a longer time are > > very closed minded and do not allow changes beside what they think is > > correct, the outcome of such a story are broken drivers, fundamentally > > flawed frameworks and unfriendly discussions which do not help anyone. > > > > Markus > > > > ACKED. > > That is why we have some "who the hell is Mauro currently" ;) > > At least for my little part ... But I can't see, how this should be related to Manu's S2 drivers yet. He takes care to take everything disturbing out. That is the other side of it. Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB Networking Module
Hello Johannes! Johannes Stezenbach wrote: > On Wed, May 16, 2007, Christian Praehauser wrote: > >> The branch is available at >> http://www.cosy.sbg.ac.at/~cpraehaus/hg.cgi/v4l-dvb. >> > > This repository seems to be corrupted: > > $ hg clone http://www.cosy.sbg.ac.at/~cpraehaus/hg.cgi/v4l-dvb > destination directory: v4l-dvb > requesting all changes > adding changesets > adding manifests > adding file changes > abort: consistency error adding group! > transaction abort! > rollback completed > Sorry! Should work now. >> Along with the new dvb-net module, a new version of the dvbnet (DVB network >> interface manager) >> is (required and) available at the repository >> http://www.cosy.sbg.ac.at/~cpraehaus/hg.cgi/dvb-apps. >> It uses a simple command language, example: >> dvbnet addmpe pid 300 >> > > Some people probably use dvbnet in scripts, so if you change > the commandline syntax in a non backwards compatbile way > it's better to give your version a different name and leave > the old one alone. > > So we should keep the original dvbnet tool (with the old syntax) and just adapt it to work with the dvb-net module. OK, sounds reasonable to me. Has anybody a good name for the new version? My suggestions: dvbnetcfg, dvbnetmgr, dvbnetctl Another possibility would be that the new version (2.0.0) of dvbnet supports the commandline options of the old version in a backwards-compatible way. Some examples of using version 2: dvbnet addmpe pid 360 dvbnet listif dvbnet getif iid 0 dvbnet delif iid 0 Commandline options are currently used e.g. for specifying the adapter (-a) or printing help information (-h). >> I would like to discuss here (on the list) >> - whether if it makes sense to this (from your point of view) >> - what should be changed/added/removed >> - any other comments >> - if we should and how we can eventually integrate this into the main >> v4l-dvb and dvb-apps branches >> > > couldn't look at your code, but: > > I think it was a design mistake in the current dvb-core that a card > driver has to add code if it wants to support dvb-net. As soon as a card > driver > registers a demux, dvb-core should add dvb-net automatically, as > there is zero card-specific code involved. > Exactly! As you say, the whole networking thing is not specific to any card. All it needs is a demux. However, I didn't want to touch every driver. That's why I added a compatibility craft in dvb_net.h, so that the dvb-net module can be loaded on-demand. The drawback is that the (inline) code is included by every card driver. I also decided to do this because I tried to change as little in the dvb-core module as possible. For a possible transition phase, I'll probably move the on-demand loading support to dvb-core, and just define stubs for the dvb_net_init/dvb_net_release functions which do nothing. > It is useful to have CONFIG_DVB_NET. > > Yep. That's now included. Thanks for your comments! Best regards, Christian. -- Christian Praehauser <[EMAIL PROTECTED]> || //\\//\\ || Multimedia Communications Group, ||// \/ \\|| Department of Computer Sciences, University of Salzburg http://student.cosy.sbg.ac.at/~cpraehaus/ http://www.network-research.org/ http://www.uni-salzburg.at/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S- and DVB-S2-streams with TT3200
Am Dienstag, 29. Mai 2007 01:34 schrieb Markus Rechberger: > On 5/28/07, Peter Magellan <[EMAIL PROTECTED]> wrote: > > > I just removed those and it worked somehow, still having bad problems> > > > > about locking and every time you acan channels it find diffrent ones.> Is > > it possible to get this TT3200 card work like normal technotrend> budget > > DVB-S1 card? on windows atleast all technotrends have same> drivers. > > > > That's because in Linux, people have nothing better to do than bitch, act > > I'm-holier-than-thou, > > and don't spend time designing a good driver/architecture model first > > before coding spaghetti > > non-working code. > > I wouldn't overall say linux, but I can say that's the truth with v4l > and dvb at least. > People who fundamentally want to change something are not welcome here > since some people who've been with that project for a longer time are > very closed minded and do not allow changes beside what they think is > correct, the outcome of such a story are broken drivers, fundamentally > flawed frameworks and unfriendly discussions which do not help anyone. > > Markus YES! Markus! You got it! Thanks! P. S.: I will start another attempt soon, and I will not stop until the code is there where it belongs to (guess you know what and whom I mean - I will send you another copy of the attempt) > > ___ > 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] DVB-S- and DVB-S2-streams with TT3200
Am Dienstag, den 29.05.2007, 01:34 +0200 schrieb Markus Rechberger: > On 5/28/07, Peter Magellan <[EMAIL PROTECTED]> wrote: > > > I just removed those and it worked somehow, still having bad problems> > > about locking and every time you acan channels it find diffrent ones.> Is it > > possible to get this TT3200 card work like normal technotrend> budget DVB-S1 > > card? on windows atleast all technotrends have same> drivers. > > > > That's because in Linux, people have nothing better to do than bitch, act > > I'm-holier-than-thou, > > and don't spend time designing a good driver/architecture model first before > > coding spaghetti > > non-working code. > > > > I wouldn't overall say linux, but I can say that's the truth with v4l > and dvb at least. > People who fundamentally want to change something are not welcome here > since some people who've been with that project for a longer time are > very closed minded and do not allow changes beside what they think is > correct, the outcome of such a story are broken drivers, fundamentally > flawed frameworks and unfriendly discussions which do not help anyone. > > Markus > ACKED. That is why we have some "who the hell is Mauro currently" ;) At least for my little part ... Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > Sorry if I wasn't clear enough -- I'll try to be more precise here. > > When I use an smp-enabled kernel, I can use kaffeine, mplayer, or > mythtv and they all receive and record just fine for 15-30 minutes. > After that the picture looks like the reception is terrible -- mostly > green, sometimes with pieces of image around the edges and a few small > squares of non-green (maybe signal, maybe noise, hard to tell) through > the middle. The audio is similarly messed up, and the EPG doesn't seem > to download correctly either. The changeover is sudden, but doesn't > seem to happen after a fixed amount of time -- it's usually about > 15-30 minutes. If I record programs in this state the recording looks > exactly the same as the above description. If I play old files > everything is fine, it is only receiving that has problems. Restarting > the X server has no effect. Switching to another player has no effect. > The light on the usb stick stays solid green, ie receiving the signal > fine. It's not flashing as it does when reception is bad. > > Scanning for channels works partially: it picks up one frequency with > 4 channels, but none of the other frequencies that it found when in a > working state. It can still tune to the previously set channels, even > though it can't detect them, although of course the reception is > terrible. > > Unplugging the device, unloading the module, replugging, and reloading > has no effect. Killing the X server and restarting has no effect -- > after both those I still have exactly the same reception issue I > described above. > > I took a shot of the contents of the movie via xine -- you can get it > from http://steelgarden.com/badreception.png > The shot was taken from a saved file that I replayed after rebooting > with an non-smp kernel. > > I have also put my kernel .config file up at > http://steelgarden.com/.config in case there's something relevant in > there. Could it be a problem that I compiled the kernel with the dvb > drivers as module, and then replaced the .ko files? Should I recompile > with no hint of dvb in the kernel itself? > > I hope this is specific enough. If there's any other information I can > provide please tell me. > also does this device work properly in windows? Markus > Thanks for you patience, > Ben > > On 28/05/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > > On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > > > No, nothing at all was printed to dmesg at the moment the reception > > > dropped (or in fact at all since I started receiving). > > > > > > > first of all it should not generate a kernel oops anymore with the > > latest drivers. > > Since it's a usb device, simply replugging it should bring the device > > back to its initial state, if you still get a garbled videooutput your > > XServer/graphic card driver might have a problem, in that case you > > might try to record a video - reboot and try to watch that video > > (before rebooting if you see some garbled image also try to make a > > screenshot/photo). > > Does scanning for DVB-T channels still work when the video is gone? > > > > You should try to post as much information as possible, currently the > > only information I got out of all mails is "crashing with smp" and > > nothing else that might give a hint what happened. > > > > cheers, > > Markus > > > -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > Sorry if I wasn't clear enough -- I'll try to be more precise here. > > When I use an smp-enabled kernel, I can use kaffeine, mplayer, or > mythtv and they all receive and record just fine for 15-30 minutes. > After that the picture looks like the reception is terrible -- mostly > green, sometimes with pieces of image around the edges and a few small > squares of non-green (maybe signal, maybe noise, hard to tell) through > the middle. The audio is similarly messed up, and the EPG doesn't seem > to download correctly either. The changeover is sudden, but doesn't > seem to happen after a fixed amount of time -- it's usually about > 15-30 minutes. If I record programs in this state the recording looks > exactly the same as the above description. If I play old files > everything is fine, it is only receiving that has problems. Restarting > the X server has no effect. Switching to another player has no effect. > The light on the usb stick stays solid green, ie receiving the signal > fine. It's not flashing as it does when reception is bad. > > Scanning for channels works partially: it picks up one frequency with > 4 channels, but none of the other frequencies that it found when in a > working state. It can still tune to the previously set channels, even > though it can't detect them, although of course the reception is > terrible. > > Unplugging the device, unloading the module, replugging, and reloading > has no effect. Killing the X server and restarting has no effect -- > after both those I still have exactly the same reception issue I > described above. > > I took a shot of the contents of the movie via xine -- you can get it > from http://steelgarden.com/badreception.png > The shot was taken from a saved file that I replayed after rebooting > with an non-smp kernel. > > I have also put my kernel .config file up at > http://steelgarden.com/.config in case there's something relevant in > there. Could it be a problem that I compiled the kernel with the dvb > drivers as module, and then replaced the .ko files? Should I recompile > with no hint of dvb in the kernel itself? > > I hope this is specific enough. If there's any other information I can > provide please tell me. > can you attach a dmesg logfile after plugging in the device, and after replugging the device after around ~20 minutes when the error occured (maybe also xorg log might help)? Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S- and DVB-S2-streams with TT3200
On 5/28/07, Peter Magellan <[EMAIL PROTECTED]> wrote: > > I just removed those and it worked somehow, still having bad problems> > about locking and every time you acan channels it find diffrent ones.> Is it > possible to get this TT3200 card work like normal technotrend> budget DVB-S1 > card? on windows atleast all technotrends have same> drivers. > > That's because in Linux, people have nothing better to do than bitch, act > I'm-holier-than-thou, > and don't spend time designing a good driver/architecture model first before > coding spaghetti > non-working code. > I wouldn't overall say linux, but I can say that's the truth with v4l and dvb at least. People who fundamentally want to change something are not welcome here since some people who've been with that project for a longer time are very closed minded and do not allow changes beside what they think is correct, the outcome of such a story are broken drivers, fundamentally flawed frameworks and unfriendly discussions which do not help anyone. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Technotrend DVB-C budget-CI tuning problem
> Hello, > Seems my Technotrend DVB-C budget-CI cannot find all the channels under Linux that it finds under Windows > Neither dvbscan nor kaffeine finds anything at a frequency (154 MHz, 6900 syms, 128QAM) where the included windows software does. > Running kernel 2.6.21.2 (Gentoo-sources) on a 64-bit Gentoo system (Core 2 Duo). > I'll help if I can have you tried changing the inversion settings for each transponder? I've had some similar experiences. off-topic question for you. Are you able to decrypt any pay-channels? I have the same hardware, can scan for channels, but have never been able to decrypt under Linux (only Windows) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Debug messages with cx24110
>>>
>> Sorry - you're absolutely right, I just took a quick lopok at the wrong
>> sources an made a wrong
>> decision :)
>> The problem are the lot of unnecessary printk statements in printk
>> statements in
>> linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c
>> like:
>> printk("cx24108 debug: entering SetTunerFreq, freq=%d\n",freq);
>> printk("cx24108 debug: select vco #%d (f=%d)\n",i,freq);
>> printk("cx24108 debug: pump=%d, n=%d, a=%d\n",pump,n,a);
>>
>
> just replace printk with a dprintk
>
>
Sure I know, but I am not a dvb developer.
This issue was reported over a year ago and is still not fixed in the
repository...
A little bit offtopic:
The user who reports this is using a Pinnacle DVB-S 400i and this card
has very bad receiption on some channels.
Is this as expected with this card or are there any tuning capabiltites ?
--
Helmut Auer, [EMAIL PROTECTED]
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] avermedia e506r mixed success
Hi Markus I had a look at qemu and the pci proxy stuff. Is there any point in me trying to get that to work and dump something that would be useful? We have DVB-T here but I think there might be issues as the card is on a shared IRQ but I could probably just unplug the wireless card while I'm dumping info. Let me know if that would be of any help - maybe there's stuff I could figure out myself but I don't have any experience with this stuff just can read/write C that's all! Thanks, mimo > On 5/27/07, mimo <[EMAIL PROTECTED]> wrote: >> Hi >> >> I have had some success and failure with this card - it identifies as >> 1131:7133 using latest mercurial stuff. >> I have added >> options saa7134 card=117 alsa=1 >> install saa7134 /sbin/modprobe xc3028-tuner; /sbin/modprobe >> --ignore-install >> saa7134; /sbin/modprobe saa7134-dvb; /sbin/modprobe saa7134-alsa >> >> Using firmware_pinnacle.tgz the whole analog part of the card works >> (kernel >> 2.6.20-lowlatency from ubuntu). >> >> Below is my dmsg. The audio works with the sox workaround. DVB-T >> doesn't. I >> also tried card=85 >> (http://www.linuxtv.org/pipermail/linux-dvb/2006-May/010246.html) but >> that >> reported problems. >> >> What are the chances of getting dvb-t working and can I help in some >> way? >> > > the chances are 50:50, I guess there are just some very small changes > missing to get DVB-T work properly. Since I do not have that device I > cannot do anything and someone else has to figure out the outstanding > part. > > Maybe someone who owns that device in Berlin/Leipzig/(Dresden would be > fine in around 1 month when they start to broadcast DVB-T) can contact > me > I cannot guarantee that I can get it work, chances aren't too bad > since I got analogue TV (including audio) and radio already work. > > Markus > >> Thanks, >> >> mm >> >> [12987.596000] pccard: CardBus card inserted into slot 0 >> [12987.767000] saa7130/34: v4l2 driver version 0.2.14 loaded >> [12987.769000] PCI: Enabling device :03:00.0 ( -> 0002) >> [12987.769000] ACPI: PCI Interrupt :03:00.0[A] -> Link [LNKA] -> GSI >> 11 >> (level, low) -> IRQ 11 >> [12987.77] saa7133[0]: found at :03:00.0, rev: 209, irq: 11, >> latency: >> 0, mmio: 0x3c00 >> [12987.77] PCI: Setting latency timer of device :03:00.0 to 64 >> [12987.77] saa7133[0]: subsystem: 1461:f436, board: AVerMedia >> Cardbus >> TV/Radio (E506R) [card=117,insmod option] >> [12987.77] saa7133[0]: board init: gpio is 222 >> [12987.897000] saa7133[0]: i2c eeprom 00: 61 14 36 f4 00 00 00 00 00 00 >> 00 >> 00 >> 00 00 00 00 >> [12987.897000] saa7133[0]: i2c eeprom 10: 00 ff e2 0e ff 20 ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12987.897000] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 01 03 08 ff >> 00 >> ff >> ff ff ff ff >> [12987.898000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12987.898000] saa7133[0]: i2c eeprom 40: ff 65 00 ff c2 1e ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12987.899000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12987.899000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12987.899000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff >> ff >> ff >> ff ff ff ff >> [12988.002000] tuner 0-0061: chip found @ 0xc2 (saa7133[0]) >> [12988.002000] >> /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: >> setting tuner callback >> [12988.002000] tuner 0x61: Configuration acknowledged >> [12988.002000] >> /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: >> setting tuner callback >> [12988.002000] tuner 0x61: Configuration acknowledged >> [12988.002000] >> /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: >> setting tuner callback >> [12988.049000] >> /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/xc3028-tuner.c: >> attach request! >> [12988.049000] >> /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: >> xc3028 tuner successfully loaded >> [12988.074000] saa7133[0]: registered device video0 [v4l2] >> [12988.075000] saa7133[0]: registered device vbi0 >> [12988.075000] saa7133[0]: registered device radio0 >> [12988.08] saa7134 ALSA driver for DMA sound loaded >> [12988.08] saa7133[0]/alsa: saa7133[0] at 0x3c00 irq 11 >> registered >> as >> card -1 >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > > > -- > Markus Rechberger > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
Sorry if I wasn't clear enough -- I'll try to be more precise here. When I use an smp-enabled kernel, I can use kaffeine, mplayer, or mythtv and they all receive and record just fine for 15-30 minutes. After that the picture looks like the reception is terrible -- mostly green, sometimes with pieces of image around the edges and a few small squares of non-green (maybe signal, maybe noise, hard to tell) through the middle. The audio is similarly messed up, and the EPG doesn't seem to download correctly either. The changeover is sudden, but doesn't seem to happen after a fixed amount of time -- it's usually about 15-30 minutes. If I record programs in this state the recording looks exactly the same as the above description. If I play old files everything is fine, it is only receiving that has problems. Restarting the X server has no effect. Switching to another player has no effect. The light on the usb stick stays solid green, ie receiving the signal fine. It's not flashing as it does when reception is bad. Scanning for channels works partially: it picks up one frequency with 4 channels, but none of the other frequencies that it found when in a working state. It can still tune to the previously set channels, even though it can't detect them, although of course the reception is terrible. Unplugging the device, unloading the module, replugging, and reloading has no effect. Killing the X server and restarting has no effect -- after both those I still have exactly the same reception issue I described above. I took a shot of the contents of the movie via xine -- you can get it from http://steelgarden.com/badreception.png The shot was taken from a saved file that I replayed after rebooting with an non-smp kernel. I have also put my kernel .config file up at http://steelgarden.com/.config in case there's something relevant in there. Could it be a problem that I compiled the kernel with the dvb drivers as module, and then replaced the .ko files? Should I recompile with no hint of dvb in the kernel itself? I hope this is specific enough. If there's any other information I can provide please tell me. Thanks for you patience, Ben On 28/05/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > > No, nothing at all was printed to dmesg at the moment the reception > > dropped (or in fact at all since I started receiving). > > > > first of all it should not generate a kernel oops anymore with the > latest drivers. > Since it's a usb device, simply replugging it should bring the device > back to its initial state, if you still get a garbled videooutput your > XServer/graphic card driver might have a problem, in that case you > might try to record a video - reboot and try to watch that video > (before rebooting if you see some garbled image also try to make a > screenshot/photo). > Does scanning for DVB-T channels still work when the video is gone? > > You should try to post as much information as possible, currently the > only information I got out of all mails is "crashing with smp" and > nothing else that might give a hint what happened. > > cheers, > Markus > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Debug messages with cx24110
Helmut Auer wrote:
> Hi Andreas
>> this is the default for static variables. The whole kernel relies on the
>> fact, that they are initialized to zero. How can this change anything?
>> Are you using a broken compiler? Can you try another version?
>>
>> Quoting from the dietlibc FAQ:
>>
>> Q: I see lots of uninitialized variables, like "static int foo;". What
>> gives?
>> A: "static" global variables are initialized to 0. ANSI C guarantees that.
>>Technically speaking, static variables go into the .bss ELF segment,
>>while "static int foo=0" goes into .data. Because .bss is zero
>>filled by the OS, it does not need to be in the actual binary. So it
>>is in fact better to not initialize static variables if the desired
>>initialization value is 0 anyway. The same is true for pointers, by
>>the way. On all platforms supported by the diet libc, numeric zero
>>is also the pointer value for NULL. So not initializing a static
>>pointer yields NULL.
>>
>> Regards,
>> Andreas
>>
> Sorry - you're absolutely right, I just took a quick lopok at the wrong
> sources an made a wrong
> decision :)
> The problem are the lot of unnecessary printk statements in printk statements
> in
> linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c
> like:
> printk("cx24108 debug: entering SetTunerFreq, freq=%d\n",freq);
> printk("cx24108 debug: select vco #%d (f=%d)\n",i,freq);
> printk("cx24108 debug: pump=%d, n=%d, a=%d\n",pump,n,a);
just replace printk with a dprintk
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > No, nothing at all was printed to dmesg at the moment the reception > dropped (or in fact at all since I started receiving). > first of all it should not generate a kernel oops anymore with the latest drivers. Since it's a usb device, simply replugging it should bring the device back to its initial state, if you still get a garbled videooutput your XServer/graphic card driver might have a problem, in that case you might try to record a video - reboot and try to watch that video (before rebooting if you see some garbled image also try to make a screenshot/photo). Does scanning for DVB-T channels still work when the video is gone? You should try to post as much information as possible, currently the only information I got out of all mails is "crashing with smp" and nothing else that might give a hint what happened. cheers, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Debug messages with cx24110
Hi Andreas
>
> this is the default for static variables. The whole kernel relies on the
> fact, that they are initialized to zero. How can this change anything?
> Are you using a broken compiler? Can you try another version?
>
> Quoting from the dietlibc FAQ:
>
> Q: I see lots of uninitialized variables, like "static int foo;". What
> gives?
> A: "static" global variables are initialized to 0. ANSI C guarantees that.
>Technically speaking, static variables go into the .bss ELF segment,
>while "static int foo=0" goes into .data. Because .bss is zero
>filled by the OS, it does not need to be in the actual binary. So it
>is in fact better to not initialize static variables if the desired
>initialization value is 0 anyway. The same is true for pointers, by
>the way. On all platforms supported by the diet libc, numeric zero
>is also the pointer value for NULL. So not initializing a static
>pointer yields NULL.
>
> Regards,
> Andreas
>
Sorry - you're absolutely right, I just took a quick lopok at the wrong sources
an made a wrong
decision :)
The problem are the lot of unnecessary printk statements in printk statements in
linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c
like:
printk("cx24108 debug: entering SetTunerFreq, freq=%d\n",freq);
printk("cx24108 debug: select vco #%d (f=%d)\n",i,freq);
printk("cx24108 debug: pump=%d, n=%d, a=%d\n",pump,n,a);
It was reported over a year ago and no one takes care of these :(
This leads to that syslog:
May 27 21:46:42 [kernel] cx24108 debug: pump=1, n=49, a=5
May 27 21:46:42 [kernel] cx24108 debug: entering SetTunerFreq, freq=1584564
May 27 21:46:42 [kernel] cx24108 debug: select vco #7 (f=1584564)
May 27 21:46:42 [kernel] cx24108 debug: pump=1, n=48, a=31
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1593154
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1593154)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=7
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1582846
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1582846)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=48, a=29
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1594872
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1594872)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=9
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1581128
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1581128)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=48, a=27
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1596590
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1596590)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=11
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1579410
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1579410)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=48, a=26
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1598308
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1598308)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=12
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1577692
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1577692)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=48, a=24
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1600026
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1600026)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=14
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1575974
May 27 21:46:43 [kernel] cx24108 debug: select vco #6 (f=1575974)
May 27 21:46:43 [kernel] cx24108 debug: pump=0, n=48, a=22
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1601744
May 27 21:46:43 [kernel] cx24108 debug: select vco #7 (f=1601744)
May 27 21:46:43 [kernel] cx24108 debug: pump=1, n=49, a=16
May 27 21:46:43 [kernel] cx24108 debug: entering SetTunerFreq, freq=1574256
May 27 21:46:43 [kernel] cx24108 debug: select vco #6 (f=1574256)
May 27 21:46:43 [kernel] cx24108 debug: pump=0, n=48, a=20
May 27 21:46:44 [kernel] cx24108 debug: entering SetTunerFreq, freq=1588000
May 27 21:46:44 [kernel] cx24108 debug: select vco #7 (f=1588000)
--
Helmut Auer, [EMAIL PROTECTED]
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
No, nothing at all was printed to dmesg at the moment the reception dropped (or in fact at all since I started receiving). Thanks, Ben On 28/05/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > > It doesn't generally produce a kernel crash -- generally the device > > just stops working properly, and I get almost random noise on the > > screen, with the occasional glimpse of a picture -- just as if I had > > really bad reception. Rebooting fixes it, but unloading and reloading > > the module does not. I haven't seen a kernel crash since changing > > drivers, but it was fairly occasional anyway. I'll keep trying to see > > if it eventually crashes. Other than that waiting for another crash, > > is there any other way I can try to find the problem? Presumably > > there's no way to use electric fence or valgrind on a kernel module -- > > is there anything else? > > > > does dmesg show up anything which might be related? > > Markus > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-2.6.19 / 20 /21: many drivers missing in make menuconfig?
Em Seg, 2007-05-28 às 19:08 +0200, Zoilo Gomez escreveu: > While trying to compile a new kernel I just noticed that many modules / > drivers seem to be missing in make menuconfig? > > Also the mercurial download does not seem to fix this: only 19 modules > are being linked. Some of the missing stuff includes bt8xx, budget_av etc. > > The software is in the tree, but I cannot select it for compilation. > > This seems to be the case for all kernels from 2.6.19 and on; with > 2.6.18 I do not have this problem. > > Did I miss something, or am I just doing something terribly stupid ? Probably, you've missed some required dependencies (like, for example I2C). You may try to use make xconfig and enable showing all options and showing all debug info. It will show the cross-references symbols, making easier for you to check what's missed. > > Z. > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Debug messages with cx24110
Hello Helmut, Helmut Auer wrote: > Here is a patch against cx24110.c. > Without this one the driver is flooding the kernel log if debug is not set to > off. > > --- v4l-dvb/linux/drivers/media/dvb/frontends/cx24110.c 2007-05-26 > 13:06:19.069094276 +0200 > +++ tmp/cx24110.c 2007-05-28 19:48:43.648017940 +0200 > @@ -45,7 +45,7 @@ > u32 lastesn0; > }; > > -static int debug; > +static int debug = 0; this is the default for static variables. The whole kernel relies on the fact, that they are initialized to zero. How can this change anything? Are you using a broken compiler? Can you try another version? Quoting from the dietlibc FAQ: Q: I see lots of uninitialized variables, like "static int foo;". What gives? A: "static" global variables are initialized to 0. ANSI C guarantees that. Technically speaking, static variables go into the .bss ELF segment, while "static int foo=0" goes into .data. Because .bss is zero filled by the OS, it does not need to be in the actual binary. So it is in fact better to not initialize static variables if the desired initialization value is 0 anyway. The same is true for pointers, by the way. On all platforms supported by the diet libc, numeric zero is also the pointer value for NULL. So not initializing a static pointer yields NULL. Regards, Andreas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Technotrend DVB-C budget-CI tuning problem
Hello, Seems my Technotrend DVB-C budget-CI cannot find all the channels under Linux that it finds under Windows Neither dvbscan nor kaffeine finds anything at a frequency (154 MHz, 6900 syms, 128QAM) where the included windows software does. Running kernel 2.6.21.2 (Gentoo-sources) on a 64-bit Gentoo system (Core 2 Duo). Put all relevant information, dmesg and dvbscan output aswell as a screenshot from the Windows software at http://www.abo.fi/~jskata/ttproblem/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Debug messages with cx24110
Am Montag, 28. Mai 2007 19:51 schrieb Helmut Auer:
> Hello List,
>
> Here is a patch against cx24110.c.
> Without this one the driver is flooding the kernel log if debug is not set
> to off.
>
> --- v4l-dvb/linux/drivers/media/dvb/frontends/cx24110.c 2007-05-26
> 13:06:19.069094276 +0200 +++ tmp/cx24110.c 2007-05-28
> 19:48:43.648017940 +0200
> @@ -45,7 +45,7 @@
> u32 lastesn0;
> };
>
> -static int debug;
> +static int debug = 0;
> #define dprintk(args...) \
> do { \
> if (debug) printk(KERN_DEBUG "cx24110: " args); \
Thank you, Helmut, well done!
Those endless "cx24108 debug" lines are in fact one big mess!
Cheers
Uwe
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Debug messages with cx24110
Hello List,
Here is a patch against cx24110.c.
Without this one the driver is flooding the kernel log if debug is not set to
off.
--- v4l-dvb/linux/drivers/media/dvb/frontends/cx24110.c 2007-05-26
13:06:19.069094276 +0200
+++ tmp/cx24110.c 2007-05-28 19:48:43.648017940 +0200
@@ -45,7 +45,7 @@
u32 lastesn0;
};
-static int debug;
+static int debug = 0;
#define dprintk(args...) \
do { \
if (debug) printk(KERN_DEBUG "cx24110: " args); \
--
Helmut Auer, [EMAIL PROTECTED]
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HVR-4000 szap2 & szap problem
Hello! Some short time ago I have asked the same question. I am using latest drivers from Steven's repository at http://linuxtv.org/hg/~stoth/hvr4000 with patches from this mailing list. Frontend CX24116 is shutting down on exit from szap and szap2. Manu and other guys told me that I must to increase dvb_shutdown_timeout or set it to 0 to avoid frontend shutdown. Today I have tried to set dvb_shutdown_timeout to 0, 1000 and 100 at modprobe.conf, than hardcode it in dvb-core/dvb_frontend.c dvb_shutdown_timeout to 0, 1000, 10 and 100 recompile the drivers for each value few times. Also I was using szap and szap2 to tune up the frontend. The situation was the same in any cases: if frontend was not in use by any running program it was shuts down on exit from szap or any program that was kept frontend in use (like dvbtraffic). When I have tried SS1 timeouts works fine! Is it mystique? -- Vasily Petrushin +7 (916) 605 90 12 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] linux-2.6.19 / 20 /21: many drivers missing in make menuconfig?
While trying to compile a new kernel I just noticed that many modules / drivers seem to be missing in make menuconfig? Also the mercurial download does not seem to fix this: only 19 modules are being linked. Some of the missing stuff includes bt8xx, budget_av etc. The software is in the tree, but I cannot select it for compilation. This seems to be the case for all kernels from 2.6.19 and on; with 2.6.18 I do not have this problem. Did I miss something, or am I just doing something terribly stupid ? Z. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S- and DVB-S2-streams with TT3200
> I just removed those and it worked somehow, still having bad problems> about > locking and every time you acan channels it find diffrent ones.> Is it > possible to get this TT3200 card work like normal technotrend> budget DVB-S1 > card? on windows atleast all technotrends have same> drivers. That's because in Linux, people have nothing better to do than bitch, act I'm-holier-than-thou, and don't spend time designing a good driver/architecture model first before coding spaghetti non-working code. _ Change is good. See what’s different about Windows Live Hotmail. http://www.windowslive-hotmail.com/learnmore/default.html?locale=en-us&ocid=RMT_TAGLM_HMWL_reten_changegood_0507 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] saa7146 64-bit, new kernels & dvbHG?
I'm been trying to get saa7146 errors to go away on an AMD 64-bit Feisty Fawn (7.04) release, and have recompiled to 2.6.21.3, plus tried installing the latest HG code for DVB & V4L - still can't get rid of the errors. Does anyone have any ideas what can fix this? (basically, the video records all choppy with my new skystar card). Tx, bill [mpeg2video @ 0xadc600]concealing 315 DC, 315 AC, 315 MV errors [mpeg2video @ 0xadc600]00 motion_type at 13 0 [mpeg2video @ 0xadc600]00 motion_type at 0 6 [mpeg2video @ 0xadc600]mb incr damaged [mpeg2video @ 0xadc600]00 motion_type at 38 13 [mpeg2video @ 0xadc600]00 motion_type at 18 19 [mpeg2video @ 0xadc600]00 motion_type at 21 25 [mpeg2video @ 0xadc600]ac-tex damaged at 3 26 [mpeg2video @ 0xadc600]00 motion_type at 18 33 [mpeg2video @ 0xadc600]concealing 360 DC, 360 AC, 360 MV errors [mpeg2video @ 0xadc600]00 motion_type at 32 1 [mpeg2video @ 0xadc600]ac-tex damaged at 2 13 [mpeg2video @ 0xadc600]ac-tex damaged at 20 23 [mpeg2video @ 0xadc600]ac-tex damaged at 15 35 uname -a Linux voa-v 2.6.21.3 #1 SMP Mon May 28 16:50:19 EEST 2007 x86_64 GNU/Linux linuxdvb: v4l-dvb-f715da1617df (from today) dmesg initialization: [ 32.640460] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 32.845576] saa7146: register extension 'budget_ci dvb'. [ 32.845890] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 [ 32.845899] ACPI: PCI Interrupt :01:0a.0[A] -> Link [APC2] -> GSI 17 (lev el, low) -> IRQ 17 [ 32.845921] saa7146: found saa7146 @ mem c2022000 (revision 1, irq 17 ) (0x13c2,0x100f). [ 32.845928] saa7146 (0): dma buffer size 192512 [ 32.845931] DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI) [ 32.881696] PM: Adding info for No Bus:i2c-2 [ 32.882550] adapter has MAC addr = 00:d0:5c:6b:4e:2c [ 32.882798] input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/inpu t1 [ 33.121560] DVB: registering frontend 0 (ST STV0299 DVB-S)... [ 33.365762] lp: driver loaded but no devices found ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technisat SkyStar2 HD DVB card support
Hi, On Mon, May 28, 2007 at 04:59:54PM +0200, benco wrote: > Hi everyone, > > is there any success with this card? > > Chipset: SAA7146 + STB0899 > > Drivers: http://jusst.de/manu/stb0899-v4l-dvb.tar.bz2 > > I was able to compile and load kernel modules for the following kernels: > > 2.6.19 > 2.6.20 > 2.6.21.1 > > Unfortunately I see no records in log file regarding to detected card - I > can see only the output from lspci command: > [...] Laasa has developed a patch for this driver. You have to apply it. Please take a look at: http://linuxtv.org/pipermail/linux-dvb/2007-May/018188.html Regards, Artem -- Artem Makhutov Unterort Str. 36 D-65760 Eschborn ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Technisat SkyStar2 HD DVB card support
Hi everyone, is there any success with this card? Chipset: SAA7146 + STB0899 Drivers: http://jusst.de/manu/stb0899-v4l-dvb.tar.bz2 I was able to compile and load kernel modules for the following kernels: 2.6.19 2.6.20 2.6.21.1 Unfortunately I see no records in log file regarding to detected card - I can see only the output from lspci command: lspci -v: 01:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Unknown device 1019 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- http://www.acid.sk/pubkey.asc `- KF = 388E 43D9 7316 A4D4 A0EB C4F2 E769 64EB DEB3 7CF1 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help, How can I add a new tv card driver?
Hi, Everyone I want to develop my tv card driver because Linux kernel don't support my demodulator(a brand new tv demodulator) and tuner now(mt2131). My tv card has the PCI interface to the Linux PC, and it doesn't have any hardware decoder. Could someone give me some advice? Thank you in advance and with all best wishes! Kevin Liu 2007.5.28 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-S- and DVB-S2-streams with TT3200
I found problem it was: 4l-dvb.org/linux/drivers/media/dvb/dvb-core/dvb_frontend.c + memset(&fepriv->fe_info, 0, sizeof (struct dvbfe_info)); + fepriv->fe_info.delivery = DVBFE_DELSYS_DVBS; + fe->ops.get_info(fe, &fepriv->fe_info); I just removed those and it worked somehow, still having bad problems about locking and every time you acan channels it find diffrent ones. Is it possible to get this TT3200 card work like normal technotrend budget DVB-S1 card? on windows atleast all technotrends have same drivers. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
On 5/28/07, ben handley <[EMAIL PROTECTED]> wrote: > It doesn't generally produce a kernel crash -- generally the device > just stops working properly, and I get almost random noise on the > screen, with the occasional glimpse of a picture -- just as if I had > really bad reception. Rebooting fixes it, but unloading and reloading > the module does not. I haven't seen a kernel crash since changing > drivers, but it was fairly occasional anyway. I'll keep trying to see > if it eventually crashes. Other than that waiting for another crash, > is there any other way I can try to find the problem? Presumably > there's no way to use electric fence or valgrind on a kernel module -- > is there anything else? > does dmesg show up anything which might be related? Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend budget tt s-1500 don't work if voltage=0 ?
> Hello, linuxtv.
> Technotrend budget tt s-1500 don't work if voltage=0 ?
>
> example 1
> 4 cards, 1 splitter, vlc, os slackware
> 1 card set vlotage=13 result work
> 2,3,4 set voltage=0 result don't work
> if 1,2,3,4 cards set voltage=13 result don't work (vlc always restart after
> 1-3 seconds and says that can't tune)
> change 4 differents splitters same result
> so it work's only if use splitter 1 out power pass
> so i set on all cards voltage=13 and all cards work
>
> example 2
> 1 card set vlotage=18 result work
> 2,3,4 set voltage=0 result don't work*
> *BUT IF I SET 2,3,4 voltage=18 then stop vlc and then set 2,3,4
> voltage=0 result 2,3,4 begin to work
> *WORK ONLY IF VOLTAGE=18
>
> example 3
> also test on Technotrend Budget S-1401
> 1 card set vlotage=13 result work
> 2,3,4 set voltage=0 result work
>
> i think that card Technotrend budget tt s-1500 don't switch on tuner
> or something else if voltage=0.
my kernel 2.6.21.1
i think the problem somewhere in stv0299.c ...
static int stv0299_set_voltage (struct dvb_frontend* fe, fe_sec_voltage_t
voltage)
{
struct stv0299_state* state = fe->demodulator_priv;
u8 reg0x08;
u8 reg0x0c;
dprintk("%s: %s\n", __FUNCTION__,
voltage == SEC_VOLTAGE_13 ? "SEC_VOLTAGE_13" :
voltage == SEC_VOLTAGE_18 ? "SEC_VOLTAGE_18" : "??");
reg0x08 = stv0299_readreg (state, 0x08);
reg0x0c = stv0299_readreg (state, 0x0c);
/**
* H/V switching over OP0, OP1 and OP2 are LNB power enable bits
*/
reg0x0c &= 0x0f;
if (voltage == SEC_VOLTAGE_OFF) {
stv0299_writeregI (state, 0x0c, 0x00); /* LNB power off!
*/
return stv0299_writeregI (state, 0x08, 0x00); /*LNB
power off! */
}
stv0299_writeregI (state, 0x08, (reg0x08 & 0x3f) |
(state->config->lock_output << 6));
switch (voltage) {
case SEC_VOLTAGE_13:
if (state->config->volt13_op0_op1 == STV0299_VOLT13_OP0)
reg0x0c |= 0x10;
else reg0x0c |= 0x40;
return stv0299_writeregI(state, 0x0c, reg0x0c);
case SEC_VOLTAGE_18:
return stv0299_writeregI(state, 0x0c, reg0x0c | 0x50);
default:
return -EINVAL;
};
}
static int stv0299_send_legacy_dish_cmd (struct dvb_frontend* fe, unsigned long
cmd)
...
for (i=0; i<9; i++) {
if (debug_legacy_dish_switch)
do_gettimeofday (&tv[i+1]);
if((cmd & 0x01) != last) {
/* set voltage to (last ? 13V : 18V) */
stv0299_writeregI (state, 0x0c, reg0x0c | (last ?
lv_mask : 0x50));
last = (last) ? 0 : 1;
}
cmd = cmd >> 1;
...
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dtt200u crashing with smp
It doesn't generally produce a kernel crash -- generally the device just stops working properly, and I get almost random noise on the screen, with the occasional glimpse of a picture -- just as if I had really bad reception. Rebooting fixes it, but unloading and reloading the module does not. I haven't seen a kernel crash since changing drivers, but it was fairly occasional anyway. I'll keep trying to see if it eventually crashes. Other than that waiting for another crash, is there any other way I can try to find the problem? Presumably there's no way to use electric fence or valgrind on a kernel module -- is there anything else? Thanks, Ben On 26/05/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > Hi, > > can you submit a the crash dump with the latest code from linuxtv? > (If you cannot scroll back you might try to patch your kernel with > kdb, it will throw the system into a console management mode which > allows to scroll back, this also won't require a serial cable/second > PC for debugging) > > Markus > > On 5/26/07, ben handley <[EMAIL PROTECTED]> wrote: > > I just tried using fresh drivers built from linuxtv.org source, same > > issue: reception breaks up after about 15 minutes of use, and only > > rebooting fixes it. I unloaded the dvb_pll, dvb_core, dvb_usb, and > > dvb_usb_dtt200u modules with the ones built in the v4l directory. Is > > that everything that I need to replace? > > > > The device was never actually disconnected -- it's been physically > > plugged in all the time. Could the problem be a loose connection that > > makes the computer think it's been disconnected? I tried removing all > > the extra cabling and plugging the usb stick directly into the port, > > but that made no difference either. So far the only thing that's made > > a difference is SMP. > > > > Thanks, > > Ben > > > > On 23/05/07, Markus Rechberger <[EMAIL PROTECTED]> wrote: > > > yes they're significantly out of date, I'm not sure what the status of > > > your device is better try to upgrade to the latest available > > > sourcecode. > > > > > > > > -- > Markus Rechberger > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco DVB-T Hybrid Cardbus (LR502) dosn't work
Hallo Hartmut,
Hartmut Hackmann schrieb:
> H, Ingolf
>
> [EMAIL PROTECTED] schrieb:
>> Hallo,
>>
>> -Original Message-
>> Date: Wed, 23 May 2007 00:57:52 +0200
>> Subject: Re: [linux-dvb] Vivanco DVB-T Hybrid Cardbus (LR502) dosn'twork
>> From: Hartmut Hackmann <[EMAIL PROTECTED]>
>> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>
>>> Hi
>>> [EMAIL PROTECTED] schrieb:
Hallo,
i have a Vivanco DVB-T Hybrid Cardbus (Card=94), it is the samelike
Lifeview DVB-T Hybrid Cardbus.
The Adapter works for a long time, but since two weeks it isnot
possible to use the DVB-T Tuner.
Analog TV and Radio works good.
dmesg show this lines after reboot:
...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: trying to boot from eeprom
tda1004x: found firmware revision 0 -- invalid
tda1004x: waiting for firmware upload...
tda1004x: found firmware revision 29 -- ok
...
>>> Hm, his is not really correct: All Lifeview cards i saw so far
>>> have a firmware eeprom, so download from host should nothappen...
>> I think you are rigth. I used this card some month withoutinstalling any
>> firmware. But now the driver ask for it.
>>
>>> There are tons of slightly different Lifeview designs. I wonder
>>> whether the description is really right...
>>>
I think that looks ok.
But if i start kaffeine i get sometime this:
...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: trying to boot from eeprom
tda1004x: found firmware revision 0 -- invalid
tda1004x: waiting for firmware upload...
tda1004x: found firmware revision 5e -- invalid
tda 1004x: firmware upload failed
...
But then i delete the firmware and reboot and then startkaffeine and
>> do
a channelscan i get an error because the firmware is notfound. Then
>> i
copy the firmware to /lib/firmware (dont leave kaffeine) andstart a
>> new
channelscan and it works. I get then this:
...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: trying to boot from eeprom
tda1004x: found firmware revision 0 -- invalid
tda1004x: waiting for firmware upload...
tda1004x: found firmware revision 29 -- ok
...
and i can scan the chanels, but some times then i switch thechannel
>> or
leave kaffeine and start it again i get the same massage likeabove:
...
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: trying to boot from eeprom
tda1004x: found firmware revision 0 -- invalid
tda1004x: waiting for firmware upload...
tda1004x: found firmware revision 5e -- invalid
tda 1004x: firmware upload failed
...
What is wrong?
My System: SuSe Linux 10.2 kernel 2.6.8, V4L-DVB fromlinuxtv.org
also tested kernel 2.6.21, 2.6.22 with V4L-DVB from linuxtv.orgwith
>> the
same result
>>> Are you able to try some modifications after i gave you
>> someinstructions?
>>> I would guess that the tda01146 GPIO configuration is wrong for
>> yourcard.
>>> (I made changes here to solve another problem).
>>>
>>> Hartmut
>> Yes i can make modifikation in the Sourcecode if yor give me
>> theinstructions.
>>
>> Ingofl
>>
>>
> First: I assume that the card is not autodetected, you forced the
> card type, right?
> LR502 is card type 60, but its a dual card, strange...
> Anyway, dvb-t is configured in
> linux/drivers/media/video/saa7134/saa7134-dvb.c.
> It is shared with another card, the config struct is:
>
> static struct tda1004x_config ads_tech_duo_config = {
> .demod_address = 0x08,
> .invert= 1,
> .invert_oclk = 0,
> .xtal_freq = TDA10046_XTAL_16M,
> .agc_config= TDA10046_AGC_TDA827X,
> .gpio_config = TDA10046_GP00_I,
> .if_freq = TDA10046_FREQ_045,
> .tuner_address = 0x61,
> .request_firmware = philips_tda1004x_request_firmware
> };
>
>
> The most interesting value is:
>
> .gpio_config = TDA10046_GP00_I,
>
> Its a enum, defined in:
> linux/drivers/media/dvb/frontends/tda1004x.h
>
> Please try especially TDA10046_GP10_I, which should invert the
> eeprom address mapping. If GPIO 1 has an impact, it is another
> basic card type.
>
> Can you please try this and report?
>
> Hartmut
>
I have changed the value. But the TDA10046_GP10_I has no effekt. But i
tested some other values and TDA10046_GP10 works perfect.
I can scan the chanels. Can look DVB-T. I think the problem is solved.
Now i must look how to play t
