Hello,
I wanted to ask if anyone else has power supply issue with using Hauppauge WinTV solo TV tuner sticks?
I’ve set them up on a Raspberry PI 2 running TVHeadend on the OSMC platform (latest update). Software wise it’s all good with streaming live and recorded Tv. The 2 TV sticks are linked to the Pi via a Powered USB hub. I also use a local portable HDD too.
But within a month or so the TV server will randomly (semi) freeze, ie show up on a scan of IP addresses but will not allow access to TV Streams for the Client boxes.
I discovered it was down to the USB hub, or sticks, in that if I I unplug the hub from the raspberry pi and power off the sticks, the raspberry pi comes back to life. After a few moments I plug the tuner sticks back in an off we go with no trouble.
I’ve tried multiple powered hubs (pi hut, belkin 1mA units and OSMC) but all have the same issue ie within a month the PI freezes. The TV sticks all of different ages 2016-2018. The Raspberry Pi is powered off an OSMC power supply.
Being in Australia I just use the DVB-T component. I’m just wondering though.
A) should I be looking to shutdown the TV server once per week to allow the TV tuners to cool down.
B) change the technology eg go with HDHomerun connect Quattro (when it arrives here in Aus)
C) is there something that I’m missing re software setting?
Many thanks
Hi, if I understand it right you have a Pi2+OSMC power supply with a powered hub connected (hopefully not a one with power feedback by its upstream port).
At the usb hub you have connected 2 TV sticks + 1 portable hdd.
Perhaps, your issue does not relate to USB power at all, so a log set immediately after the “freeze” could help to better understand the problem.
The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
So, in simple steps
- activate the logging
- reboot the Pi
- when the system freezes again, do your steps to correct the issue (disconnect the usb hub and plug-in again) and immediately transfer the logs using either the
log uploader in MyOMSC in the GUI or login via ssh, user osmc, password osmc and invoke grab-logs -A
- in both cases the returned URL is what you should publish here in this thread
- also helpful would be to install the
usbutils package and provide the output us the lsusb -v command with usb hub, sticks and hdd connected
Don’t hesitate to ask if you need help for one of the steps above.
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Thanks Jim,
The hardware description you have is correct, which as far as I can see is a text book arrangement. I’ll set up the log system as discussed and then it’s a wait for it to freeze again, which might be sometime, or not.
I think it’s a heat related issue as with the same hardware arrangement but in a more confined space (poor airflow) the raspberry pi would freeze more frequently. But as you note the logs should be better source of information.
Kind regards
Dave
Hello,
I’m just following up the request for logs. This morning 23rd April circa 8:30 am there was a general power blip, as seen by my Vero 4k, rebooted and the raspberry pi acting as the TV server (the unit subject to this thread) froze up.
https://paste.osmc.tv/wujotuyagi
Please find below the output of lsusb -v below.
osmc@TVServer:~$ lsusb -v
Bus 001 Device 005: ID 1058:07ba Western Digital Technologies, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1058 Western Digital Technologies, Inc.
idProduct 0x07ba
bcdDevice 10.07
iManufacturer 1
iProduct 2
iSerial 5
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Bus 001 Device 007: ID 2040:0264 Hauppauge
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0x0264
bcdDevice 1.00
iManufacturer 3
iProduct 1
iSerial 2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Bus 001 Device 006: ID 2040:0264 Hauppauge
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0x0264
bcdDevice 1.00
iManufacturer 3
iProduct 1
iSerial 2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1a40 Terminus Technology Inc.
idProduct 0x0101 Hub
bcdDevice 1.11
iManufacturer 0
iProduct 1
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0xec00 SMSC9512/9514 Fast Ethernet Adapter
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 2 TT per port
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0x9514 SMC9514 Hub
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.14
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Apr 23 14:09:21 TVServer kernel: Under-voltage detected! (0x00050005)
Apr 23 14:09:25 TVServer kernel: Voltage normalised (0x00000000)
...
Apr 23 14:20:52 TVServer kernel: Under-voltage detected! (0x00050005)
Apr 23 14:20:58 TVServer kernel: Voltage normalised (0x00000000)
...
Apr 23 14:26:14 TVServer kernel: Under-voltage detected! (0x00050005)
Apr 23 14:26:20 TVServer kernel: Voltage normalised (0x00000000)
...
Apr 23 14:47:23 TVServer kernel: Under-voltage detected! (0x00050005)
Apr 23 14:47:27 TVServer kernel: Voltage normalised (0x00000000)
...
Apr 23 19:06:48 TVServer kernel: Under-voltage detected! (0x00050005)
Apr 23 19:06:52 TVServer kernel: Voltage normalised (0x00000000)
...
[20282.442434] Under-voltage detected! (0x00050005)
[20286.602404] Voltage normalised (0x00000000)
[20973.003624] Under-voltage detected! (0x00050005)
[20979.243411] Voltage normalised (0x00000000)
[21295.403994] Under-voltage detected! (0x00050005)
[21301.643848] Voltage normalised (0x00000000)
[22564.205293] Under-voltage detected! (0x00050005)
[22568.365188] Voltage normalised (0x00000000)
[38128.864143] Under-voltage detected! (0x00050005)
[38133.024066] Voltage normalised (0x00000000)
Apr 23 08:31:14 TVServer kernel: usb 1-1.5: new high-speed USB device number 5 using dwc_otg
Apr 23 08:31:14 TVServer kernel: usb 1-1.5: New USB device found, idVendor=1058, idProduct=07ba
Apr 23 08:31:14 TVServer kernel: usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Apr 23 08:31:14 TVServer kernel: usb 1-1.5: Product: My Passport 07BA
Apr 23 08:31:14 TVServer kernel: usb 1-1.5: Manufacturer: Western Digital
Looks like your Pi has some serious power problems, summary:
- as you can see several undervoltage events are tracked
- also, it looks like the Western Digital external HDD is connected to the Pi instead of the USB hub … not sure about the USB path I see in the journal???
- I’m missing the option
max_usb_current=1 in the Pi2 config which should allow to give max usb current to the Pi’s ports; give max_usb_current a try in this forum or the internet
Does this mean you have had some kind of power outage which affected both the Pi and the Vero?
Not needed anymore, this is set by default for long time now
1 Like
Hello,
Following the original post i plugged the HDD into the PI directly. The auto-mount function seemed to work better.
Anyway following your post above, I installed a second USB hub and connected the HDD to the USB hub. So to confirm the current profile.
Raspberry PI
Belkin Hub - 2 x USB Hauppage TV tuners
Belkin Hub - 1 x WD HDD
Re the power to the house. The Vero 4k unit and the Raspberry Pi (TV server) are on separate wall sockets, both in the lounge. So in principal when we had a power blip, both had issues (the Vero rebooted mid show, and the raspberry pi (TV server froze).
The power supply for the raspberry pi (TV server) is a new OSMC power supply. I’m not sure though, is it the Hauppage units pulling more power than the USB hub ican provide or a general household power supply units?
I reformatted your lsusb output in your post above; the only info I can read from this is that each Hauppauge device tells a connected USB port to have the max power current of 500 mA which is the maximum a single USB port can deliver.
So, it depends on the used USB hub whether it is able to provide 3 x 500 mA for HDD and the Hauppauge devices.
Thanks
I’m using two hubs with each providing 1000mA so it’s borderline but should be okay.
I’ll keep an eye on the issue going forward.
I’ve just been struggling with powered hubs they seem to “burn out” but perhaps this is the issue being close to the output limit.
Indeed 2x500mA to an 1A USB hub could be a bit too short.
Do you have experience with the OSMC hubs? I bought one recently to work with three Hauppauge TV sticks, one of which is a dual tuner (hence pulls a little more current). But in theory should be 1500 mA so okay
It appears that the USB hubs didn’t last long, one day before I started getting power supply issues off the raspberry pi. I tried the same hub to just power up a HDD and there was no communication - no auto mount, albeit everything looked lit up.
No worries thought I would ask though
Try the hub on a PC or another device
I’ve tried the hub on a different Vero4K unit and no joy. Just to make sure I’ll try my laptop tomorrow.
When the hub is powered, the blue light will shine when you press the switch.
hello Sam,
I tried in my PC and it worked great. I then plugged the hub back into the Vero4k and the Raspberry Pi and it worked a treat. So sorry for raising the issue. Not sure why there was an issue in the first place, probably me.
1 Like