Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Ian Goldberg 
On Mon, Sep 12, 2016 at 08:45:19PM -0400, Roger wrote:
> kernel 3.16
> http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
> 
> kernel 3.19 patch
> http://hauppauge.lightpath.net/software/linux/hvr-9x5-19x5-22x5-kernel-3.19-2015-07-10-v2.patch.tar.xz
> 
> kernel 4.2 (already has) built in support for the WinTV-HVR-955Q.
> 
> At this point, I'm wondering if the drivers also for the HVR-1955/1975 are 
> included within kernel >= 4.2?
> 
> 
> Interesting, does the original poster have access to the Internet, or to 
> hauppauge.com?

Yes, as I said, those are in fact the drivers I'm using (the 3.16
version).  Kernel 4.2+ has drivers in it for the 1950, but not the 1975.

   - Ian
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Roger 

2014.02.26 Hauppauge Press release:
http://www.hauppauge.com/pdfs/pr_hauppauge_wintv-hvr-1975.pdf
"We expect the WinTV-HVR-1975 to be used in Linux based systems for digital 
signage, sports equipment, hospital patient entertainment systems and other TV 
watching and high speed data delivery applications"

"For Linux system builders, Hauppauge has driver support which can be provided 
under NDA."

LinuxTV.org Hauppauge WinTV-HVR-1950
https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1950
Note: As of August 2014, the WinTV-HVR-1955 is sometimes shipped instead of the 
HVR-1950. The HVR-1955 does not, at this time, have a open-source driver 
available.  A source-level driver for Linux is available from Hauppauge after a 
NDA is signed. Hauppauge technical support can be contacted for more details.

>From the above, I'm ascertaining the HVR-1955 is possibly the HVR-1975, or 
similar situation.  Judging by the press release, I'm guessing contacting 
Hauppauge will result in the firmwares being released after a NDA is signed.

I'll take a gander, likely one or two chips (or maybe some of the code for the 
firmware) have questionable disclosures attached during the 
engineering/manufacturing process.  And may or may not be provided openly at a 
later date.  But then I stumble back on this thought, and if it's just the 
firmwares, we should be able to extract them from the Windows' driver package.

Take a further look at a mailing list post by dheitmueller at kernellabs on Mar 
7, 2016, 7:39 AM (Post #9 of 15)
http://www.gossamer-threads.com/lists/mythtv/users/597124

I think dheitmueller did a good job explaining some of the material.

(I prefer to copy the material here, but think I've wrote enough already.)

Of course that list ends up recently asking this list for further information!  

But as dheitmueller stated within his post, or somebody immediately following 
his post, the Linux HVR-1955/1975 drivers are posted on this page.
http://www.hauppauge.com/site/support/linux.html

kernel 3.16
http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz

kernel 3.19 patch
http://hauppauge.lightpath.net/software/linux/hvr-9x5-19x5-22x5-kernel-3.19-2015-07-10-v2.patch.tar.xz

kernel 4.2 (already has) built in support for the WinTV-HVR-955Q.

At this point, I'm wondering if the drivers also for the HVR-1955/1975 are 
included within kernel >= 4.2?


Interesting, does the original poster have access to the Internet, or to 
hauppauge.com?


> On Mon, Sep 12, 2016 at 05:35:17PM -0500, is...@isely.net wrote:
> (snip)
>I know basically nothing about the HVR-1975.  Again sorry, been out of this 
>too long.  Is it even compatible?  (If you bought the '1950 but got this then 
>it's probably reasonably close.)  Has anyone else successfully used this 
>model?  Frankly I figured after all this time and with the world moving to 
>digital video streams that this technology from 2003 would be fading away...  
>But as I said, I've been away too long and am not up to speed.
>
>  -Mike

Off-topic, most digital streams (including satellite subscription TV) are 
compressed video & audio.  Your over-the-air broadcast TV is of slightly better 
quality and it's free.  One just needs to know how to install an antenna, 
cabling, etc...  I've even experience broadcast TV having superior quality 
audio versus Cable TV, but that was a few years ago.

-- 
Roger
http://rogerx.freeshell.org/
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Ian Goldberg 
On Tue, Sep 13, 2016 at 12:37:25AM +, Gary Buhrmaster wrote:
> On Mon, Sep 12, 2016 at 10:35 PM,   wrote:
> 
> > I know basically nothing about the HVR-1975.
> 
> As I understand it, the HVR-1975 is essentially
> a "one size fits all" redesign of the basic HVR-1900
> and the HVR-1950/1955 which is compatible with
> both US and DVB standards [mostly for commercial
> embedded solutions that want one SKU for either
> location (it actually contains two demods)].
> 
> Hauppuage (last I knew) reportedly offered an out
> of tree driver on their website for the HVR-1975,
> but (again, last I knew) it was never submitted
> upstream (it was reported some of the code
> included non-GPL copyright, and I presume
> it could not be re-licensed).

Yes, that's the driver I'm using.
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Gary Buhrmaster 
On Mon, Sep 12, 2016 at 10:35 PM,   wrote:

> I know basically nothing about the HVR-1975.

As I understand it, the HVR-1975 is essentially
a "one size fits all" redesign of the basic HVR-1900
and the HVR-1950/1955 which is compatible with
both US and DVB standards [mostly for commercial
embedded solutions that want one SKU for either
location (it actually contains two demods)].

Hauppuage (last I knew) reportedly offered an out
of tree driver on their website for the HVR-1975,
but (again, last I knew) it was never submitted
upstream (it was reported some of the code
included non-GPL copyright, and I presume
it could not be re-licensed).
___
pvrusb2 mailing list
pvrusb2@isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Re: [pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread isely 

The driver is getting upset because it can't load "firmware2", which is 
the firmware needed for the mpeg2 encoder IC in the device.  Without 
that firmware, the encoder can't run and basically you won't be able to 
get any mpeg data at all from the device.

Looking at the function in question, it appears that the pvrusb2 driver 
did in fact locate the expected firmware file name and that the firmware 
file passed basic sanity (size must be multiple of 4 bytes).  However, 
after sending the image, the mpeg encoder refused to wake up and start 
running, thus the failure.  It's possible that either the mpeg2 encoder 
firmware image for an HVR-1975 is different than other models (which 
would be a first), or that the firmware image file installed on your 
system (part of that patch?  I really don't know) is corrupted.

I know basically nothing about the HVR-1975.  Again sorry, been out of 
this too long.  Is it even compatible?  (If you bought the '1950 but got 
this then it's probably reasonably close.)  Has anyone else successfully 
used this model?  Frankly I figured after all this time and with the 
world moving to digital video streams that this technology from 2003 
would be fading away...  But as I said, I've been away too long and am 
not up to speed.

  -Mike



On Mon, 12 Sep 2016, Ian Goldberg wrote:

> Hi, all.
> 
> I recently purchased two Hauppauge WinTV HVR-1975 devices (well, I
> purchased 1950s, but you know how it is), for use with my MythTV box.
> 
> The machine is running Mythbuntu 14.04, and I downloaded
> linux-lts-utopic_3.16.0-77.99~14.04.1 and applied the patch
> http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
> (and it applied perfectly cleanly).
> 
> I've booted into that kernel, and *some* bits work, but video doesn't.
> There's an lirc0 device, and I can control the computer using the
> Hauppauge remote, so that's good.  There are video0 and video1 devices,
> but if I do "cat /dev/video0", I get in kern.log:
> 
> Sep 12 17:52:04 brennan kernel: [84445.104528] pvrusb2: Clearing driver error 
> statuss
> Sep 12 17:52:04 brennan kernel: [84445.569299] pvrusb2: firmware2 upload 
> transfer failure
> Sep 12 17:52:04 brennan kernel: [84445.570010] pvrusb2: Clearing driver error 
> statuss
> Sep 12 17:52:05 brennan kernel: [84446.037511] pvrusb2: firmware2 upload 
> transfer failure
> 
> (Oddly, I just noticed that if I do "cat /dev/video1", I get in
> kern.log:
> 
> Sep 12 17:51:39 brennan kernel: [84420.310628] cx25840 8-0044: loaded 
> v4l-cx25840.fw firmware (16382 bytes)
> Sep 12 17:51:39 brennan kernel: [84420.389304] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:39 brennan kernel: [84420.389663] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> Sep 12 17:51:40 brennan kernel: [84420.763169] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:40 brennan kernel: [84420.763578] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> Sep 12 17:51:40 brennan kernel: [84421.122188] 
> silabs_tercab_set_analog_params: [8-0060] using video_sys 
> Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
> Sep 12 17:51:40 brennan kernel: [84421.122540] 
> silabs_tercab_set_analog_params: [8-0060] silabs_tercab_set_analog_params(): 
> initializing tuner type Si2177
> 
> and then a bunch of data actually does come out, but it's just an mpg of
> snow.  Maybe the proper input isn't selected?)
> 
> There's also no /dev/lirc1, and when I try to irsend to /dev/lirc0,
> lircd throws an error.  The strace is:
> 
> ioctl(7, IPMICTL_SET_MY_LUN_CMD or LIRC_SET_SEND_CARRIER, 0x7ffe88ab4a1c) = 0
> write(7, "\5\0N\0", 4)  = -1 EINVAL (Invalid argument)
> 
> so I can't use the blasters for some reason.
> 
> Any thoughts about the firmware upload failure and the lack of blasting
> ability?
> 
> The kernel log when attaching a device is below.
> 
> Thanks,
> 
>- Ian
> 
> 
> 
> 
> Sep 12 17:42:38 brennan kernel: [83878.440917] usb 2-4: new high-speed USB 
> device number 15 using xhci_hcd
> Sep 12 17:42:38 brennan kernel: [83878.573024] usb 2-4: New USB device found, 
> idVendor=2040, idProduct=7510
> Sep 12 17:42:38 brennan kernel: [83878.573031] usb 2-4: New USB device 
> strings: Mfr=1, Product=2, SerialNumber=3
> Sep 12 17:42:38 brennan kernel: [83878.573035] usb 2-4: Product: WinTV
> Sep 12 17:42:38 brennan kernel: [83878.573038] usb 2-4: Manufacturer: 
> Hauppauge
> Sep 12 17:42:38 brennan kernel: [83878.573041] usb 2-4: SerialNumber: 
> 7300-00-F08E07DC
> Sep 12 17:42:38 brennan kernel: [83878.573647] pvrusb2: Hardware description: 
> WinTV HVR-1975 Model 16
> Sep 12 17:42:39 brennan kernel: [83879.575404] pvrusb2: Device 
> microcontroller firmware (re)loaded; it should now reset and reconnect.
> Sep 12

[pvrusb2] WinTV HVR-1975 (with official drivers) failing to load firmware

2016-09-12 Thread Ian Goldberg 
Hi, all.

I recently purchased two Hauppauge WinTV HVR-1975 devices (well, I
purchased 1950s, but you know how it is), for use with my MythTV box.

The machine is running Mythbuntu 14.04, and I downloaded
linux-lts-utopic_3.16.0-77.99~14.04.1 and applied the patch
http://hauppauge.lightpath.net/software/linux/linux-ubuntu-14-04-2.tar.xz
(and it applied perfectly cleanly).

I've booted into that kernel, and *some* bits work, but video doesn't.
There's an lirc0 device, and I can control the computer using the
Hauppauge remote, so that's good.  There are video0 and video1 devices,
but if I do "cat /dev/video0", I get in kern.log:

Sep 12 17:52:04 brennan kernel: [84445.104528] pvrusb2: Clearing driver error 
statuss
Sep 12 17:52:04 brennan kernel: [84445.569299] pvrusb2: firmware2 upload 
transfer failure
Sep 12 17:52:04 brennan kernel: [84445.570010] pvrusb2: Clearing driver error 
statuss
Sep 12 17:52:05 brennan kernel: [84446.037511] pvrusb2: firmware2 upload 
transfer failure

(Oddly, I just noticed that if I do "cat /dev/video1", I get in
kern.log:

Sep 12 17:51:39 brennan kernel: [84420.310628] cx25840 8-0044: loaded 
v4l-cx25840.fw firmware (16382 bytes)
Sep 12 17:51:39 brennan kernel: [84420.389304] silabs_tercab_set_analog_params: 
[8-0060] using video_sys Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
Sep 12 17:51:39 brennan kernel: [84420.389663] silabs_tercab_set_analog_params: 
[8-0060] silabs_tercab_set_analog_params(): initializing tuner type Si2177
Sep 12 17:51:40 brennan kernel: [84420.763169] silabs_tercab_set_analog_params: 
[8-0060] using video_sys Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
Sep 12 17:51:40 brennan kernel: [84420.763578] silabs_tercab_set_analog_params: 
[8-0060] silabs_tercab_set_analog_params(): initializing tuner type Si2177
Sep 12 17:51:40 brennan kernel: [84421.122188] silabs_tercab_set_analog_params: 
[8-0060] using video_sys Si2158_ATV_VIDEO_MODE_PROP_VIDEO_SYS_M
Sep 12 17:51:40 brennan kernel: [84421.122540] silabs_tercab_set_analog_params: 
[8-0060] silabs_tercab_set_analog_params(): initializing tuner type Si2177

and then a bunch of data actually does come out, but it's just an mpg of
snow.  Maybe the proper input isn't selected?)

There's also no /dev/lirc1, and when I try to irsend to /dev/lirc0,
lircd throws an error.  The strace is:

ioctl(7, IPMICTL_SET_MY_LUN_CMD or LIRC_SET_SEND_CARRIER, 0x7ffe88ab4a1c) = 0
write(7, "\5\0N\0", 4)  = -1 EINVAL (Invalid argument)

so I can't use the blasters for some reason.

Any thoughts about the firmware upload failure and the lack of blasting
ability?

The kernel log when attaching a device is below.

Thanks,

   - Ian




Sep 12 17:42:38 brennan kernel: [83878.440917] usb 2-4: new high-speed USB 
device number 15 using xhci_hcd
Sep 12 17:42:38 brennan kernel: [83878.573024] usb 2-4: New USB device found, 
idVendor=2040, idProduct=7510
Sep 12 17:42:38 brennan kernel: [83878.573031] usb 2-4: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Sep 12 17:42:38 brennan kernel: [83878.573035] usb 2-4: Product: WinTV
Sep 12 17:42:38 brennan kernel: [83878.573038] usb 2-4: Manufacturer: Hauppauge
Sep 12 17:42:38 brennan kernel: [83878.573041] usb 2-4: SerialNumber: 
7300-00-F08E07DC
Sep 12 17:42:38 brennan kernel: [83878.573647] pvrusb2: Hardware description: 
WinTV HVR-1975 Model 16
Sep 12 17:42:39 brennan kernel: [83879.575404] pvrusb2: Device microcontroller 
firmware (re)loaded; it should now reset and reconnect.
Sep 12 17:42:39 brennan kernel: [83879.607515] usb 2-4: USB disconnect, device 
number 15
Sep 12 17:42:39 brennan kernel: [83879.607831] pvrusb2: Device being rendered 
inoperable
Sep 12 17:42:40 brennan kernel: [83881.362419] usb 2-4: new high-speed USB 
device number 16 using xhci_hcd
Sep 12 17:42:41 brennan kernel: [83881.558203] usb 2-4: New USB device found, 
idVendor=2040, idProduct=7510
Sep 12 17:42:41 brennan kernel: [83881.558216] usb 2-4: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Sep 12 17:42:41 brennan kernel: [83881.558222] usb 2-4: Product: WinTV
Sep 12 17:42:41 brennan kernel: [83881.558227] usb 2-4: Manufacturer: Hauppauge
Sep 12 17:42:41 brennan kernel: [83881.558232] usb 2-4: SerialNumber: 
7510-00-F08E07DC
Sep 12 17:42:41 brennan kernel: [83881.559375] pvrusb2: Hardware description: 
WinTV HVR-1975 Model 16
Sep 12 17:42:41 brennan kernel: [83881.590937] pvrusb2: Binding 
ir_rx_z8f0811_haup to i2c address 0x71.
Sep 12 17:42:41 brennan kernel: [83881.590969] pvrusb2: Binding 
ir_tx_z8f0811_haup to i2c address 0x70.
Sep 12 17:42:41 brennan kernel: [83881.590996] pvr2_hdw_setup_low(): resetting 
160xxx demod
Sep 12 17:42:41 brennan kernel: [83881.628064] cx25840 8-0044: cx25843-24 found 
@ 0x88 (pvrusb2_b)
Sep 12 17:42:41 brennan kernel: [83881.637105] pvrusb2: Attached sub-driver 
cx25840
Sep 12 17:42:41 brennan kernel: [83881.638222] silabs_tercab_autodetection: 
silabs_tercab_autodetection(): i2c addr=0x60  clock mode=0  en_xou=0
Sep 12 17:42:41 brennan kernel: