lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1187823357.7104.25.camel@gaivota>
Date:	Wed, 22 Aug 2007 19:55:57 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Manuel Reimer <Manuel.Spam@...fuerspam.de>
Cc:	Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	v4l-dvb-maintainer@...uxtv.org
Subject: Re: TV card detected wrongly by the kernel. Any chance to get this
	fixed?


Manuel,

> > I have a BT878 based TV card (was sold by a german discounter some years 
> > ago).
> >
> > Unfortunately this card gets detected wrongly and so I'm unable to watch 
> > tv, if I allow the kernel to auto-detect the card.
> >
> > If I unload the module and reload it using the right "card=" value,
> then 
> > anything works well. So one of the first steps, I do if I install a
> new 
> > version of my distribution, is to place the "unload module and
> reload with 
> > the right value" code to my "rc.local" file.
> >
> > Is there any chance to get this card added to the kernel, so the
> right 
> > value gets auto-loaded?
> 
> It might be possible, but the driver maintainer (Cc'ed) should know
> best.

Most cheap bt8xx boards don't have eeprom or other means for properly
detecting the board internals. For such boards, you need to specify
card=<nr>, otherwise the driver will use a generic "default" that may
not work.

The proper way for handling this is by adding at /etc/modprobe.conf
(or /etc/modules, depending on your distro) a line like:

options bttv card=<nr>

This way, every time the module will load, the modprobe tools will use
the proper options.

If your board have an unique PCI ID, we may add it to the driver,
avoiding this need. For this, we will need the results of the following
command:

lspci -vv -nn

Cheers,
Mauro

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ