[ATrpms-users] DVB-T USB stick OK under FC5, not under CentOS 5

Axel Thimm Axel.Thimm at ATrpms.net
Sun Dec 9 19:59:11 CET 2007


On Sun, Dec 09, 2007 at 01:21:59PM +0000, John Pilkington wrote:
> On Sat, 2007-12-08 at 15:18 +0000, John Pilkington wrote:
> > On Sat, 2007-12-08 at 10:10 +0200, Axel Thimm wrote: 
> > > On Fri, Dec 07, 2007 at 11:37:37PM +0000, John Pilkington wrote:
> > > > On Fri, 2007-12-07 at 22:58 +0200, Axel Thimm wrote:
> > > > > Hi,
> > > > > 
> > > > > On Fri, Dec 07, 2007 at 06:45:30PM +0000, John Pilkington wrote:
> > > > > > But my main problem is that the DVB-T stick that works quite well in FC5
> > > > > > seems unusable in Centos.  I have Axel's v4l and its kmdl of 20070731
> > > > > > installed and maybe the problem will go away when the more recent
> > > > > > releases arrive (and I get back to the system).
> > > > > 
> > > > > does that mean you have 20070731 on both FC5 and CentOS5 and it only
> > > > > works on FC5?
> > > > 
> > > > I'm afraid I'm away from home at present and can't say exactly what the
> > > > FC5 system has. I think it was fully updated when the FC5 packages were
> > > > dropped, and it hasn't been changed since, so the answer is probably
> > > > 'yes'.  But IIRC FC5 had the video stuff in the kernel and didn't need
> > > > the v4l packages.  I've tried Centos without them but then dvbscan and
> > > > Mythtvsetup wouldn't run.
> > > 
> > > When you get back home check out with modinfo foo | head or modprobe
> > > -nv foo to see which modules are being loaded (use the modprobe before
> > > they have been loaded) and then use rpm -qf on the filename to see
> > > what packages provide them.
> > 
> > Axel, thanks for this suggestion.  I shan't be able to try it
> > immediately, but if the problem is still there after any upcoming
> > updates I'll report back eventually.  
> > 
> > I should have added that in Centos the hardware monitor identified the
> > usb receiver as (again IIRC) an Avermedia device - and after an
> > unplug/replug sequence reported two of them.  In the FC5 HWM it appears
> > as Wideview/Typhoon, as it does in dmesg on both systems.  Might a
> > suitable modprobe correct this?
> > 
> Hi again: According to this wiki
>  
> http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices
> 
> my device is fully supported - it's the Freecom Rev3 version, the Rev4
> is apparently not - and needs dvb-usb.ko, dvb-usb-dtt200u.ko and
> probably mt352.ko.  They all appear in 
> 
> rpm -q -p video4linux-kmdl-2.6.18-8.1.15.el5-20070731-81.el5.i686.rpm -l

and what about FC5, which was working? Were these also taken from a
video4linux-kmdl? Also check with modprobe/modinfo on FC5 what is
being loaded.

> so please how do I override what seems to be a device misidentification,
> and how ought it to be prevented?
> 
> Grateful thanks as always, 
> 
> John Pilkington
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20071209/84180ca5/attachment.bin 


More information about the atrpms-users mailing list