On Tuesday 06 April 2004 16:08, Valsecchi Patrick wrote: > I'm using the stv0299 driver. For the ID as printed on the device itself, I > guess you want what's printed on the actual chip (I had to open the > tinbox): STV0299B > J147BEK > J22210204 > MALTA > > On the tinbox, I have a sticker with "Hauppauge WinTV NEXUS version 2.1"
Thanks. I'm sorry for hassling you with that; I see from an earlier posting you have a BSRU6/TDQB-500x tuner, I should have checked back further in the list :( > I tried with dvb_shutdown_timeout=0 and I had that bug. So you get the *same* problem as when it was non-zero?! That is weird; I've not seen anything like that myself.. although I am using a budget card here with an stv0299 based tuner. Once it has gone into that bad state, how do you get it out of it again? Does it need a reboot, or a reload of the drivers....? Is this still with the "DVB drivers from an un-patched 2.6.4 kernel"; 'cos there have been an awful lot of changes (hopefully improvements :) to the frontend code since then. Can I maybe send you a recent snapshot since you don't have CVS access? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
