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

Thread: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

  1. #1
    Join Date
    May 2014
    Location
    Prineville, Oregon
    Posts
    20

    Default V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    Hi,
    udev is not creating /dev/video, and so I cannot get my Hauppauge HVR 1600 card to work in V_13.1 (it was working in V_12.3).

    1) Can I use the yast2-tv module from V_12.3 to configure the card? Modprobe and dmesg shows that the drivers are being loaded, the firmware is in /lib/firmware, but mythtv-setup does not find the card because there is no /dev/video.

    2) Can I just create /dev/video using mknod? Will it be permanent (survive a reboot)?

    Thanks for any help.

  2. #2

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    You posted to the wrong forum.
    I cite from the forum's description:
    This forum is NOT for asking questions, but contains submissions to be reviewed and potentially moved to the How To/FAQ area.
    Quote Originally Posted by motonut View Post
    1) Can I use the yast2-tv module from V_12.3 to configure the card? Modprobe and dmesg shows that the drivers are being loaded, the firmware is in /lib/firmware, but mythtv-setup does not find the card because there is no /dev/video.
    Yes, the yast2-tv module should work fine in 13.1. Just install the package from 12.3.

    But actually this shouldn't be needed.
    I just plugged in my old Hauppauge WinTV card (which I always had to configure with yast2-tv) into a freshly installed openSUSE 13.1 system last weekend, and everything worked fine out-of-the-box.

    But, I didn't have a /dev/video either, it was /dev/video0. And IIRC it was just /dev/video0 already when I last used it (and configured it with yast2-tv) in 12.1.

    So think yast2-tv won't help you, especially as you say that the drivers are being loaded.

    2) Can I just create /dev/video using mknod? Will it be permanent (survive a reboot)?
    You should be able to create an alias via an udev rule. Or just create a symlink as a test.
    Code:
    sudo ln -s /dev/video0 /dev/video
    So, do you have a /dev/video0 (and/or /dev/video1)?
    What does "v4l-info" show?

    Can't you tell mythtv to use /dev/video0 instead, f.e.?

    Btw, I always used and preferred xdtv (a fork of xawtv) for watching TV (I created packages myself here: http://software.opensuse.org/package/xdtv).
    And this still worked fine for me last weekend, it even used the existing /dev/video0 without me having to configure anything...
    Last edited by wolfi323; 04-May-2014 at 22:41. Reason: wrong link

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,788

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    This is in the wrong forums indeed.

    CLOSED and will be moved to Hardware.
    Henk van Velden

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,788

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    Quote Originally Posted by hcvv View Post
    CLOSED and will be moved to Hardware.
    Moved from Unreviewed Howto and open again.
    Henk van Velden

  5. #5
    Join Date
    Jun 2008
    Location
    Europe
    Posts
    435

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    I think that yast2-tv was given up for 13.1 because there was no one to maintain it.

  6. #6
    Join Date
    May 2014
    Location
    Prineville, Oregon
    Posts
    20

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    First of all, I apologize for posting in the wrong area. I did not know where the issue belonged.

    I checked /dev again, just to be sure, and there is no /dev/video, /dev/video0, or /dev/dvb (mentioned elsewhere on the web).

    I installed v4l-tools and here is the output from v4l-info:

    MyLinux:/dev # v4l-info
    open /dev/video0: No such file or directory

    I use the Hauppauge HVR1600 mostly to convert old VHS tapes to DVDs, not to watch TV, but I would prefer to be able to do both, since it has the ATSC tuner also.

    It seems like using a udev rule is the best way to go, but I'm not sure how to do that. Where Is there an example I can follow?

    Is there any other information I can provide?

    Thanks for your help.

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,788

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    For an udev rule to work, there must at least be hardware detected by the kernel. Else the kernel can not give udev the signal (and information) to do something. In other words, you cannot write an udev rule when you doi not know what to speciffy in it.

    I know this may not sound a very helpfull observation, but it may help in getting to the point why the device is not recocnised and acted upon.
    Henk van Velden

  8. #8
    Join Date
    May 2014
    Location
    Prineville, Oregon
    Posts
    20

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    That is what is so puzzling to me. Here is my dmesg output:

    MyLinux:/dev # dmesg | grep Hauppauge
    [ 9.568243] cx18-0: Autodetected Hauppauge card
    [ 9.798958] tveeprom 5-0050: Hauppauge model 74351, rev F4F5, serial# 8435428
    [ 9.798977] cx18-0: Autodetected Hauppauge HVR-1600

    Here is /lib/firmware/

    -rw-r--r-- 1 root root 16382 Jul 28 2013 v4l-cx231xx-avcore-01.fw
    -rw-r--r-- 1 root root 141200 Jul 28 2013 v4l-cx23418-apu.fw
    -rw-r--r-- 1 root root 158332 Jul 28 2013 v4l-cx23418-cpu.fw
    -rw-r--r-- 1 root root 16382 Jul 28 2013 v4l-cx23418-dig.fw
    -rw-r--r-- 1 root root 16382 Jul 28 2013 v4l-cx23885-avcore-01.fw
    -rw-r--r-- 1 root root 16382 Jul 28 2013 v4l-cx25840.fw

    lsmod:

    cx18 166886 1
    dvb_core 125656 1 cx18
    cx2341x 28230 1 cx18
    sp5100_tco 13979 0
    videobuf_vmalloc 13589 1 cx18
    mii 13934 1 r8169
    videobuf_core 30118 2 cx18,videobuf_vmalloc
    tveeprom 21216 1 cx18
    v4l2_common 16073 4 cs5345,tuner,cx18,cx2341x
    videodev 141701 5 cs5345,tuner,cx18,cx2341x,v4l2_common

    lspci:

    03:05.0 Multimedia video controller: Conexant Systems, Inc. CX23418 Single-Chip MPEG-2 Encoder with Integrated Analog Video/Broadcast Audio Decoder

  9. #9
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,788

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    Something new for every newcomer here

    Please use CODE tags around your computer text. It is the # button in the tool bar of the post editor.
    Henk van Velden

  10. #10

    Default Re: V_13.1 Is there a Yast2>Hardware>yast2-tv module?

    As I said, it just worked here with a WinTV PCI card.
    I don't have any experience with your particular card.

    If there's no /dev/video* at all, then the card is clearly _not_ working, and so the driver doesn't seem to have been loaded successfully.

    Quote Originally Posted by motonut View Post
    That is what is so puzzling to me. Here is my dmesg output:

    MyLinux:/dev # dmesg | grep Hauppauge
    [ 9.568243] cx18-0: Autodetected Hauppauge card
    [ 9.798958] tveeprom 5-0050: Hauppauge model 74351, rev F4F5, serial# 8435428
    [ 9.798977] cx18-0: Autodetected Hauppauge HVR-1600
    Well, the output of grep only shows those lines that contain the word "Hauppauge".
    But there could be an error message in one of the next lines, which is _not_ shown here.

    I would suggest you pipe the log to "less", then search for "Hauppauge" (press the '/' key), and just post some of the following lines.
    Code:
    dmesg | less

    OTOH, as I already mentioned, the 12.3 yast2-tv module works fine on 13.1.
    So you could try to install it and then configure the card with that (or just take the file /etc/modprobe.d/50-tv from your previous 12.3 installation if possible).
    Code:
    sudo rpm -i http://download.opensuse.org/repositories/openSUSE:/12.3/standard/noarch/yast2-tv-2.21.4-7.1.2.noarch.rpm
    But I cannot say if your card will work then, or there's perhaps a problem in 13.1 itself that causes your card not to work.
    Last edited by wolfi323; 05-May-2014 at 12:36.

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
  •