Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Using a Hauppauge HD PVR 1212 usb capture device

You can ask for help with video cards, tv cards, dvb, monitors, webcams, digital cameras and software related to these devices, here. Tutorials about these devices can be posted here, too.
Message
Author
User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 11380
Joined: Wed Jul 12, 2006 5:54 am

Re: Using a Hauppauge HD PVR 1212 usb capture device

#11 Post by lucky9 » Sat May 10, 2014 1:38 am

Did you run update-grub from the new (booted) kernel? (If you're booting the OS that the kernel was installed into then the place (like /dev/sda1) is known by the system. That's what you're booting so you don't have to do anything.)

As root you might try update-initramfs in a console. You get there by choosing/highlighting the new kernel and hit the e key then typing 3 and hit the Enter Key. Login as root and run the update-xxxx command.

A lot of the time video drivers may need to be reinstalled on the new kernel. When you get to the GRUB boot screen, Down Arrow to the new kernel. Then use a cheatcode to see if this is what's happening. You'll have to do the e as above to enter the cheatcode. I'd recommend xdrvr=vesa as this is a basic all-the-time-supported driver.
See here: http://www.mepis.org/docs/en/index.php?title=Cheatcode
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

User avatar
Volofrog
Forum Regular
Forum Regular
Posts: 128
Joined: Sun Jan 11, 2009 1:09 am

Re: Using a Hauppauge HD PVR 1212 usb capture device

#12 Post by Volofrog » Mon May 12, 2014 12:10 am

I have had no success in getting a new kernel to boot. I decided to re-install M11 and try again. This time I left the home directory under root (\).

As root, I ran the following:

Code: Select all

[root@audiovisual Volofrog]# apt-get install linux-image-$(dpkg --print-architecture|sed 's/i386/686-pae/') linux-headers-$(dpkg --print-architecture|sed 's/i386/686-pae/') -t squeeze-backports -s

[root@audiovisual Volofrog]# apt-get install linux-image-$(dpkg --print-architecture|sed 's/i386/686-pae/') linux-headers-$(dpkg --print-architecture|sed 's/i386/686-pae/') -t squeeze-backports 
When i tried to re-boot into the new kernel, the computer locked up during the boot process. The computer will boot into the old kernel.

I do not know if the following helps, but I am including the last lines of dmesg and the dmesg logs found in /var/log/.

dmesg from a termiinal

Code: Select all

[   11.672228] ndiswrapper version 1.56 loaded (smp=yes, preempt=no)
[   11.894267] usbcore: registered new interface driver ndiswrapper
[   12.751425] fuse init (API version 7.15)
[   14.072062] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input5
[   15.563563] lp: driver loaded but no devices found
[   15.649082] ppdev: user-space parallel port driver
[   15.819324] Bluetooth: Core ver 2.15
[   15.819332] NET: Registered protocol family 31
[   15.819333] Bluetooth: HCI device and connection manager initialized
[   15.819334] Bluetooth: HCI socket layer initialized
[   16.017158] Bluetooth: L2CAP ver 2.15
[   16.017159] Bluetooth: L2CAP socket layer initialized
[   16.028674] Bluetooth: RFCOMM TTY layer initialized
[   16.028677] Bluetooth: RFCOMM socket layer initialized
[   16.028678] Bluetooth: RFCOMM ver 1.11
[   16.068809] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.068811] Bluetooth: BNEP filters: protocol multicast
[   16.104661] Bluetooth: SCO (Voice Link) ver 0.6
[   16.104665] Bluetooth: SCO socket layer initialized
[   16.387292] r8169 0000:03:00.0: eth0: link up
[   16.387299] r8169 0000:03:00.0: eth0: link up
[   26.453337] start_kdeinit (2597): /proc/2599/oom_adj is deprecated, please use /proc/2599/oom_score_adj instead.
From dmesg located in /var/log/

Code: Select all

[   11.894267] usbcore: registered new interface driver ndiswrapper
[   12.751425] fuse init (API version 7.15)
[   14.072062] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input5
[   15.563563] lp: driver loaded but no devices found
[   15.649082] ppdev: user-space parallel port driver
From dmesg.0 logged when booting into new kernel.

Code: Select all

[    8.176618] hdpvr 4-1.4:1.0: device now attached to video0
[    8.176644] usbcore: registered new interface driver hdpvr
[    8.571303] HDMI status: Codec=0 Pin=5 Presence_Detect=0 ELD_Valid=0
[    8.603206] HDMI status: Codec=1 Pin=5 Presence_Detect=0 ELD_Valid=0
[    8.635154] HDMI status: Codec=2 Pin=5 Presence_Detect=0 ELD_Valid=0
[    8.667103] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[    8.683193] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input6
[    8.683470] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input7
[    8.683749] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input8
[    8.684024] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input9
[    9.224005] Adding 1020120k swap on /dev/sda3.  Priority:1 extents:1 across:1020120k 
[    9.328988] EXT3-fs (sda1): using internal journal
[   10.731715] fuse init (API version 7.17)
[   12.268509] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input10
[   13.938728] Bluetooth: Core ver 2.16
[   13.938740] NET: Registered protocol family 31
[   13.938742] Bluetooth: HCI device and connection manager initialized
[   13.938743] Bluetooth: HCI socket layer initialized
[   13.938745] Bluetooth: L2CAP socket layer initialized
[   13.938748] Bluetooth: SCO socket layer initialized
[   14.172125] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.172128] Bluetooth: BNEP filters: protocol multicast
[   14.174209] Bluetooth: RFCOMM TTY layer initialized
[   14.174214] Bluetooth: RFCOMM socket layer initialized
[   14.174216] Bluetooth: RFCOMM ver 1.11
Notice that the hdpvr was recognized and assigned to video0. The screen locks into the last phase and hangs. Being patient, I left the computer in the screen to see if it would ever continue. Next day, it was still hung in the boot process.

I hope I have included something that will trigger a thought in someone else. I am not sure which way to go next.

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9285
Joined: Wed Jul 12, 2006 2:26 pm

Re: Using a Hauppauge HD PVR 1212 usb capture device

#13 Post by kmathern » Mon May 12, 2014 8:21 am

With the boot stalling at the "[ 26.453337] start_kdeinit ..." line, I think it's related to the video driver.

Are you using the proprietary nvidia driver with the original 2.6.36-1mepis-smp kernel? If so did you use sgfxi to install it?

If you did use sgfxi to install the nvidia driver to the original kernel, you can use sgfxi's -! 40 option to build the nvidia module for the backports kernel.
The way you do that is to boot to the desktop with the original kernel, then in a konsole run the following command:

Code: Select all

su -c 'sgfxi -! 40'
The update-grub command needs to have been run before running the sgfxi -! 40 command.

After running the sgfxi command, shutdown and try again to boot the backports kernel.

User avatar
Volofrog
Forum Regular
Forum Regular
Posts: 128
Joined: Sun Jan 11, 2009 1:09 am

Re: Using a Hauppauge HD PVR 1212 usb capture device

#14 Post by Volofrog » Tue May 13, 2014 1:56 am

Several installs ago, I did run sgfxi to install the video, but I have not done so since the last two installs. Should I run sgfxi first before using the -! 40' version? From what was written, I may be close to getting the system up and I do not want to skip a step through ignorance.

Thanks for the help. It is greatly appreciated!

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9285
Joined: Wed Jul 12, 2006 2:26 pm

Re: Using a Hauppauge HD PVR 1212 usb capture device

#15 Post by kmathern » Tue May 13, 2014 8:18 am

Volofrog wrote:Several installs ago, I did run sgfxi to install the video, but I have not done so since the last two installs. Should I run sgfxi first before using the -! 40' version? From what was written, I may be close to getting the system up and I do not want to skip a step through ignorance.

Thanks for the help. It is greatly appreciated!
Let's first verify that your machine uses a nvidia videocard. There's this post of yours in a different thread, http://forum.mepiscommunity.org/viewtop ... 18#p318918, where you were using a Nvidia GeForce 210 card. Is that the same machine that you're using now? [I'm going to assume that it is]

Since you haven't needed to use sgfxi on your last two installs, M11's stock nvidia driver (260.19.21 series) apparently works OTOB with a GeForce 210 card. But I'm fairly certain M11's 260.19.21 series nvidia driver doesn't support the 3.2 backports kernel. That's why the 2.6.36 kernel will boot (and use the nvidia driver) but the backports kernel won't.

Sgfxi is probably the easiest thing to use to install a newer version nvidia driver that will support both the 3.2 backports kernel & M11's original 2.6.36 kernel.

You do need to first run sgfxi (without the -! 40 option) to install the nvidia driver on one of the kernels, before running it again with the -! 40 option to install the nvidia driver on the other kernel.

User avatar
Volofrog
Forum Regular
Forum Regular
Posts: 128
Joined: Sun Jan 11, 2009 1:09 am

Re: Using a Hauppauge HD PVR 1212 usb capture device

#16 Post by Volofrog » Tue May 13, 2014 9:19 pm

It has been a journey, but my system now boots into the new kernel. My thanks to all for the support and help. As I work with my Hauppaugh 1212, I will post my successes, and issues. Many thanks again to all.

Post Reply

Return to “Video-Related”