[pvrusb2] pvrusb2 and 2.6.27 - No device

devsk funtoos at yahoo.com
Fri Oct 17 20:04:38 CDT 2008


I am running vanilla 2.6.27 as well.

-devsk



----- Original Message ----
From: Mike Isely <isely at isely.net>
To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
Sent: Friday, October 17, 2008 1:33:36 PM
Subject: Re: [pvrusb2] pvrusb2 and 2.6.27 - No device

On Fri, 17 Oct 2008, Bent Lykkebo wrote:

> On Thu, 16 Oct 2008, Mike Isely wrote:
> > On Thu, 16 Oct 2008, devsk wrote:
> >> > Mike,
> >> > 
> >> > It seems like 2.6.27 has a version of pvrusb2 which doesn't work anymore. The module loads but no device is file is created in /dev/v4l. I am using sys-fs/udev-130-r1.
> >> > 
> >> > Only thing seen in dmesg on loading of the module is
> >> > 
> >> > [   14.918314] usbcore: registered new interface driver pvrusb2
> >> > [   14.918317] pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version
> >> > [   14.918320] pvrusb2: Debug mask is 31 (0x1f)
> >>    
> >
> > Those messages appear when the module gets loaded.  And only at that 
> > time.
> >
> > But that's different than the act of associating the module with the 
> > device.  That association step is outside the control of the driver.  
> > The USB core (likely in cooperation with udev) uses a database of known 
> > USB IDs mapped to module names.  Each such module (e.g. pvrusb2) 
> > logically gets its "own" USB IDs registered when that module is 
> > depmod'ed from userspace.  If that database is messed up, then the USB 
> > core can't know to associate the pvrusb2 driver.  I've seen this happen 
> > if "depmod -a" hasn't been run after the kernel's module tree is updated 
> > / changed.  However if you are just running a vanilla kernel with 
> > pvrusb2 built as part of it, then all that setup should have been taken 
> > care of when you installed the kernel in your system.
> >
> > I haven't tried the new 2.6.27 here yet.  This weekend I'll grab the 
> > new source tree and take a look.
> >
> >  
> ....snip....
> 
> I think it's a USB Core problem, because if I attach my pvrusb2 I get 
> the same as devsk, the firmware is not loaded and it's not working! If I 
> then disconnect it, I can't use any USB devices anymore, because the USB 
> connect or disconnect doesn't work anymore, the USB core seems to be 
> locked. I have seen the problem in Ubuntu 8.10 beta and Mandriva2009, 
> both using the 2.6.27 kernel. Made a bug report to Ubuntu kernel team a 
> long time ago, but no luck yet, so maybe we will not be able to use our 
> pvrusb2 devices in the upcoming Ubuntu 8.10 ;-(

Well now that the misbehavior has been seen in the vanilla kernel maybe 
I can chase it down.  I'll post if I figure anything out.

  -Mike


-- 

Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
_______________________________________________
pvrusb2 mailing list
pvrusb2 at isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


More information about the pvrusb2 mailing list