Yes, I have.
Try the latest video4linux snapshot from bytesex.org. I've been
fiddling with my Avermedia DVB-T (the 761 version).
If you have the 761 card you should be up and running right away, 771
users will need to uncomment a line in 'ir-kbd-gpio.c'
case BTTV_AVDVBT_771:. This hasn't been
Has anybody tried to run linuxdvb
drivers on a small Linux distribution?
Running on a very small harddisk
or compact flash card?
What we tried is:
Mandrake Linux 9.2 is installed in the truly-minimal
configuration mode, we
managed to get it
on a 210 MB harddisk partition, with
Your 'truly-minimal' configuration is probably lacking devfs and sysfs
support in your kernel. Check the kernel options (if they exist on a
minimal configuration) and see if you can tweak them.
On Jun 28, 2004, at 8:50 AM, Irek Defe wrote:
Has anybody tried to run linuxdvb drivers on a small
On Mon, Jun 28, 2004 at 08:22:50AM +0200, Torbjörn Jansson wrote:
Looks like I have forgotten a module while compiling the
kernel (2.6.7)?
I also downloaded the firmware dvb-ttpci-01.fw-261c and copied it
to /usr/lib/hotplug/firmware/dvb-ttpci-01.fw
I tried to use the DVB driver
Hi,
On Mon, 2004-06-28 at 14:50, Irek Defée wrote:
Has anybody tried to run linuxdvb drivers on a small Linux distribution?
Running on a very small harddisk or compact flash card?
I am currently using the drivers in a home maden distribution booting
from a disk-on-chip (about 15MB). Everything
If I try to run vdr I get an error:
vdr: no primary device found - using first device!
What frontend module did you load?
None ^^.
After loading VES1820 everything was working.
As I suspected :-)
How is your reception quality? Lots of errors on some channels? Or maybe
just
Vincent Bernat wrote:
OoO En cette soirée bien amorcée du dimanche 27 juin 2004, vers 22:49,
Vincent Bernat [EMAIL PROTECTED] disait:
In a system with 4 DVB cards, I sometimes get a EOVERFLOW error when
trying to read from the card. I have raised MAX_EVENTS with no
success. How can I prevent
On Mon, Jun 28, 2004 at 04:47:46PM +0200, Torbjörn Jansson wrote:
How is your reception quality? Lots of errors on some channels? Or maybe
just occasionally or none at all?
It looks like you have the same type of card as I have, and I have had lots
of problems with reception quality.
It
Sorry for doing a probably very silly reply (without having had a look
at the source as well):
On Mon, Jun 28, 2004 at 01:09:50AM +0200, Vincent Bernat wrote:
OoO En cette soirée bien amorcée du dimanche 27 juin 2004, vers 22:49,
Vincent Bernat [EMAIL PROTECTED] disait:
In a system with 4
Thanks Marty. I knew I'd searched the archives a few days ago, but
totally forgot about your patch! I'll give it a go over the weekend and
post how I get on.
I applied the patch, tried to tune and got the same results :-(
Any ideas what to try next?
--
Daniel
Wolfgang Thiel wrote:
Sorry for doing a probably very silly reply (without having had a look
at the source as well):
On Mon, Jun 28, 2004 at 01:09:50AM +0200, Vincent Bernat wrote:
OoO En cette soirée bien amorcée du dimanche 27 juin 2004, vers 22:49,
Vincent Bernat [EMAIL PROTECTED] disait:
In
Hello,
I'm currently stuck on making the mt352 driver work with my TechniSat
AirStar2 DVB-T card.
That card uses the mt352 chip with some Samsung tuner.
I came across this forum when I googled a bit:
http://pvrguide.no-ip.com/bbs-old/viewtopic.php?t=3413
This TechniSat card uses the same
Christopher Pascoe wrote:
I tested it again, it doesn't work with the sleep. But less head
sounds good. Does it sleep when I unload the driver again? I could
only load it when needed.
The problem isn't the sleep itself, the problem is that in the CVS code
(at least), the FE_GET_TUNE_SETTINGS
[EMAIL PROTECTED] wrote:
Hello,
I'm currently stuck on making the mt352 driver work with my TechniSat
AirStar2 DVB-T card.
That card uses the mt352 chip with some Samsung tuner.
I came across this forum when I googled a bit:
http://pvrguide.no-ip.com/bbs-old/viewtopic.php?t=3413
This
Hi,
data with the tuner), but I simply don't know if those tuner-dependent
variables work with the Samsung tuner (don't think so after my
If it is the same tuner (network interface module) avermedia uses, then the
tuner-paramters should be correct.
My question now is: Did you get any
Hello,
On Monday 28 June 2004 18:54, [EMAIL PROTECTED] wrote:
Also, I found some oddities when looking at the mt352 driver.
The TechniSat AirStar2 uses a FlexCop IIB b2c2 chip that works with the
SkyStar2 module, but in the linuxtv cvs-tree the skystar2.c has the
following check in
Antonio Mancuso wrote:
Hello,
On Monday 28 June 2004 18:54, [EMAIL PROTECTED] wrote:
Also, I found some oddities when looking at the mt352 driver.
The TechniSat AirStar2 uses a FlexCop IIB b2c2 chip that works with the
SkyStar2 module, but in the linuxtv cvs-tree the skystar2.c has the
Wolfram Joost wrote:
This also works for me and the sleep problem is gone. But I still need
other parts of the diff I sent here before. Patch attached.
I think the parameter validation-code makes the difference. Currently, the
driver in the cvs rejects wrong parameters.
What's the
My preference would be that the driver leaves the values alone. There is
nothing more infuriating than telling the driver FEC_1_2 and finding
out later the driver thinks it's smarter than you and has been silently
correcting the values to FEC_3_4.
In those situations, how do you tell the driver
Bjorn writes:
In mt352.c the read command is contains the following:
struct i2c_msg msg [] = { { .addr = I2C_MT352_ADDR,
.flags = I2C_M_NOSTART,
.buf = b0, .len = 1 },
{ .addr =
Greetings,
It's currently known that these cards use the Conexant CX23883 decoder
with a Samsung TDTC9251DH01C tuner (see
http://www.sem.samsung.com/en/products/productOverview.jsp?categoryID=2C9D98F2-A126-B447-E1B3872409AC4242navi=overview)
and interfaces with the MT352.
Is anyone working on a
21 matches
Mail list logo