Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Help installing PCTV 340e USB tuner (was working in 12.3)

  1. #1

    Default Help installing PCTV 340e USB tuner (was working in 12.3)

    I have this USB tuner and with 12.3 to get it to work I had to copy the firmware file by hand in the /lib/firmware directory but otherwise was fine. I did an upgrade to 13.1 (not a fresh install) and now when I plug the tuner in I get from dmesg the output that the device is recognized, firmware is loaded and finally the messsage "dvb-usb: Pinnacle PCTV 340e HD Pro USB Stick successfully initialized and connected."

    However, no symlinks appear in /dev or /dev/v4l pointing to the device. Note that I have also a webcam that is correctly recognized whose links appear correctly in /dev, so in general v4l seems to be healthy.

    Any clues on how to troubleshoot this?

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,698
    Blog Entries
    1

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Anything useful show up in
    Code:
    dmesg|tail
    after you plug it in?

    From a quick search, I note some references to '/dev/dvb/adapter0/frontend0' (or similar) being created by the driver.

  3. #3

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    This is what I get when I plug the USB stick. Everything seems to be correct, no errors, but no links appear anywhere (such as in /dev/v4l or /dev/videoX)
    Code:
    [  122.496021] usb 1-6: new high-speed USB device number 6 using ehci-pci
    [  122.610926] usb 1-6: New USB device found, idVendor=2304, idProduct=023d
    [  122.610930] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  122.610933] usb 1-6: Product: PCTV 340e
    [  122.610936] usb 1-6: Manufacturer: YUANRD
    [  122.610938] usb 1-6: SerialNumber: 0B009592B7
    [  122.676045] dvb-usb: found a 'Pinnacle PCTV 340e HD Pro USB Stick' in cold state, will try to load a firmware
    [  122.719821] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
    [  122.920294] dib0700: firmware started successfully.
    [  123.421182] dvb-usb: found a 'Pinnacle PCTV 340e HD Pro USB Stick' in warm state.
    [  123.421248] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    [  123.421322] DVB: registering new adapter (Pinnacle PCTV 340e HD Pro USB Stick)
    [  124.214301] usb 1-6: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
    [  124.253042] xc4000 4-0061: creating new instance
    [  124.258172] xc4000: Successfully identified at address 0x61
    [  124.258174] xc4000: Firmware has not been loaded previously
    [  124.307009] Registered IR keymap rc-dib0700-rc5
    [  124.307142] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/rc/rc0/input10
    [  124.307208] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/rc/rc0
    [  124.307310] dvb-usb: schedule remote query interval to 50 msecs.
    [  124.307316] dvb-usb: Pinnacle PCTV 340e HD Pro USB Stick successfully initialized and connected.
    [  124.307515] usbcore: registered new interface driver dvb_usb_dib0700

  4. #4

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Additional info, yes you're right, when the device is plugged in I have also
    Code:
    ls -la /dev/dvb/adapter0/
    total 0
    drwxr-xr-x  2 root root     120 feb 10 17:24 .
    drwxr-xr-x  3 root root      60 feb 10 17:24 ..
    crw-rw----+ 1 root video 212, 0 feb 10 17:24 demux0
    crw-rw----+ 1 root video 212, 1 feb 10 17:24 dvr0
    crw-rw----+ 1 root video 212, 3 feb 10 17:24 frontend0
    crw-rw----+ 1 root video 212, 2 feb 10 17:24 net0
    And the vendor and product info matches the DVD stick as it appears on /sys/dev/char/212:0/device. So it looks like these block devices are being created pointing at the DVB-T USB stick.

    Perhaps this is something that has changed with 13.1? Because in 12.3 apps were looking for (and finding) video devices in /dev/v4l or /dev/videoX I realize I don't know which component is/was responsible for creating these links?

  5. #5

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Replying to myself, the entries in /dev/dvb/adapter0 are for the plugged in Webcam, not for the DVB-T device.

    Quote Originally Posted by barbolani View Post
    Additional info, yes you're right, when the device is plugged in I have also
    Code:
    ls -la /dev/dvb/adapter0/
    total 0
    drwxr-xr-x  2 root root     120 feb 10 17:24 .
    drwxr-xr-x  3 root root      60 feb 10 17:24 ..
    crw-rw----+ 1 root video 212, 0 feb 10 17:24 demux0
    crw-rw----+ 1 root video 212, 1 feb 10 17:24 dvr0
    crw-rw----+ 1 root video 212, 3 feb 10 17:24 frontend0
    crw-rw----+ 1 root video 212, 2 feb 10 17:24 net0
    And the vendor and product info matches the DVD stick as it appears on /sys/dev/char/212:0/device. So it looks like these block devices are being created pointing at the DVB-T USB stick.

    Perhaps this is something that has changed with 13.1? Because in 12.3 apps were looking for (and finding) video devices in /dev/v4l or /dev/videoX I realize I don't know which component is/was responsible for creating these links?

  6. #6

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Again, replying to myself. Maybe it is too late in the day, these entries in /dev/dvb are indeed correct and related to the DVB-T. They even appear and disappear as I plug and unplug the DVB-T stick.

    Quote Originally Posted by barbolani View Post
    Replying to myself, the entries in /dev/dvb/adapter0 are for the plugged in Webcam, not for the DVB-T device.

  7. #7

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Quote Originally Posted by barbolani View Post
    Perhaps this is something that has changed with 13.1? Because in 12.3 apps were looking for (and finding) video devices in /dev/v4l or /dev/videoX I realize I don't know which component is/was responsible for creating these links?
    The following two links should provide some background for you that is relevant to your hybrid device:


    [ 124.258174] xc4000: Firmware has not been loaded previously
    Do you have the firmware for the xc4000 in your /lib/firmware directory?

  8. #8

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Quote Originally Posted by Tyler_K View Post
    The following two links should provide some background for you that is relevant to your hybrid device:

    Do you have the firmware for the xc4000 in your /lib/firmware directory?
    Thanks for the links, and according to these everything seems correctly created in /dev/dvb/adapter0 when I plug the device . Still not clear why kaffeine can't find the device. Everything is ok in theory yet kaffeine does not identify the DVB-T tuner, and in 12.3 was working perfectly. The dmesg output
    Code:
    [  122.719821] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' 
    [  122.920294] dib0700: firmware started successfully.
    seems to imply that the firmware is loaded correctly (in my system is located in /lib/firmware)

  9. #9

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Some progress: I found that when I scanned for channels in Kaffeine dmesg was showing some nasty driver messages related to the xc4000 module. I was -naively- using the 1.4.1 firmware after reading from kernellabs that it was the latest one. After replacing it with the 1.4 firmware the ugly driver crashes are gone and kaffeine recognizes the device and scans for channels from end to end.

    Does not find any, however. The SNR stays at 1% during all the scan.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,698
    Blog Entries
    1

    Default Re: Help installing PCTV 340e USB tuner (was working in 12.3)

    Quote Originally Posted by barbolani View Post
    Some progress: I found that when I scanned for channels in Kaffeine dmesg was showing some nasty driver messages related to the xc4000 module. I was -naively- using the 1.4.1 firmware after reading from kernellabs that it was the latest one. After replacing it with the 1.4 firmware the ugly driver crashes are gone and kaffeine recognizes the device and scans for channels from end to end.

    Does not find any, however. The SNR stays at 1% during all the scan.
    Are you in a position to test this device within a windows environment (just to eliminate potential reception issues)?

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •