[pvrusb2] Problem in kernel 2.6.27-1 and -2 under Ubuntu Intrepid Ibex.

[Bent Lykkebo]

>
> On Sat, 30 Aug 2008, Mike Isely wrote:
>> > On Sat, 30 Aug 2008, Bent Lykkebo wrote:
>> > 
>>     
>>> > > Hi,
>>> > > 
>>> > > This is maybe not a problem with pvrusb2, but Ubuntu has just upgrade to 
>>> > > kernel 2.6.27 and now I can't boot, it hangs in tarting bluetooth. If I 
>>> > > disconnect my Hauppauge device I can boot.
>>> > > 
>>> > > When I connect it I get and it don't work:
>>> > > Aug 30 08:24:30 kernel: [  158.368083] usb 1-1: new high speed USB 
>>> > > device using ehci_hcd and address 5
>>> > > Aug 30 08:24:30 kernel: [  158.516255] usb 1-1: configuration #1 chosen 
>>> > > from 1 choice
>>> > > Aug 30 08:24:30 kernel: [  159.113531] Linux video capture interface: v2.00
>>> > > Aug 30 08:24:31 kernel: [  159.219274] usbcore: registered new interface 
>>> > > driver pvrusb2
>>> > > Aug 30 08:24:31 kernel: [  159.219857] pvrusb2: Hauppauge WinTV-PVR-USB2 
>>> > > MPEG2 Encoder/Tuner : V4L in-tree version
>>> > > Aug 30 08:24:31 kernel: [  159.219874] pvrusb2: Debug mask is 31 (0x1f)
>>> > > Aug 30 08:24:31 kernel: [  159.221673] firmware: requesting 
>>> > > v4l-pvrusb2-29xxx-01.fw
>>> > > Aug 30 08:24:31 kernel: [  159.289029] pvrusb2: Device microcontroller 
>>> > > firmware (re)loaded; it should now reset and reconnect.
>>> > > Aug 30 08:24:31 kernel: [  159.432119] usb 1-1: USB disconnect, address 5
>>> > > Aug 30 08:24:31 kernel: [  159.432797] pvrusb2: Device being rendered 
>>> > > inoperable
>>> > > Aug 30 08:24:32 kernel: [  161.060191] usb 1-1: new high speed USB 
>>> > > device using ehci_hcd and address 6
>>> > > Aug 30 08:24:33 kernel: [  161.265169] usb 1-1: configuration #1 chosen 
>>> > > from 1 choice
>>> > > 
>>> > > Thanks for any advise
>>> > > Bent
>>> > > 
>>>       
>> > 
>> > The messages you printed are all normal.  Once the device's 
>> > microcontroller firmware is loaded, it has to disconnect then reconnect 
>> > to the host.  The messages you printed are those steps happening.  The 
>> > last message above comes from the USB core not the pvrusb2 driver.  It 
>> > looks like the pvrusb2 driver hasn't been told yet that the hardware has 
>> > reconnected.  I don't think there's anything in the driver that could 
>> > explain this behavior.
>> > 
>>     
>
> Also, have you verified that the same setup works in 2.6.26 or 2.6.25?  
> One thought is that the FX2 firmware is corrupt (but honestly I think 
> this to be unlikely and even if it were I don't think it's possible for 
> the firmware to screw up the host's USB core).  But if you can verify 
> that the same setup (with the same firmware) works in 2.6.25 or 2.6.26 
> then we'll know the problem is specific to 2.6.27 and not some other 
> cause.
>
>   -Mike
It seems to be a Ubuntu kernel problem! When I boot Linux 2.6.26-5 the 
pvrusb2 load and works, so they "lost" the pvrusb2 in the two latest 
kernel updates 2.6.27-1 and 2.6.27-2, lets hope they (Ubuntu) soon find 
and fix the problem.

Thanks
Bent