![]() |
ubuntu.com - launchpad.net - ubuntu help
|
|
|||||||
Ubuntu 9.10 is out!!!
When downloading Ubuntu 9.10 please consider using bittorrent to get your copy of Ubuntu. The Ubuntu Developers Summit for Lucid Lynx will be held the week of 16-Nov-2009 till 20-Nov-2009 in Dallas, TX USA. Visit the the Ubuntu wiki for more information about UDS and how to participate remotely. |
|
Mythbuntu Discussions for the Mythbuntu project. |
|
|
Thread Tools | Display Modes |
|
|
#1 | ||
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
[SOLVED] Adding lirc_pvr150 module = system hard lock
OK its been solved!
Follow the quotes Quote:
Quote:
I ‘am trying to get my pvr-150 blaster to work in Gusty and/or Mythbuntu but it’s giving me grief. I have installed the “lirc” and “lirc-modules-source” from the package manager. And Choose the Hauppauge tv card when asked. Then I opened “/etc/lirc/hardware.conf” and Modify the “MODULES” line from “ MODULES="lirc_dev lirc_i2c" “ to “MODULES="lirc_dev lirc_pvr150 lirc_i2c" “ adding the prv150 to be loaded. Then I download the firmware “haup-ir-blaster.bin” and move it to “/lib/firmware/” and confirm its there. Now here is where the fun begins. If I reboot or “sudo /etc/init.d/lirc restart” the system hard locks. The only way I can boot the system to normal mode is to rename “/etc/lirc/lircd.conf” (--OR--) to edit “/etc/lirc/hardware.conf” and remove “lirc_pvr150” from the “MODULES” line. I have tried editing “/etc/lirc/hardware.conf” and the “MODULES” line to just “MODULES="lirc_pvr150" “ and it still hard locks. This is all from a fresh install of Gusty or Mythbuntu RC. This is from my /var/log/messages, with the lirc_pvr150 in the modules line of hardware.conf and no lircd.conf file: Code:
Oct 22 22:57:30 ubuntu kernel: [ 46.516840] ivtv: ==================== START INIT IVTV ==================== Oct 22 22:57:30 ubuntu kernel: [ 46.516845] ivtv: version 1.0.0 (2.6.22-14-generic SMP mod_unload 586 ) loading Oct 22 22:57:30 ubuntu kernel: [ 46.516971] ivtv0: Autodetected Hauppauge card (cx23416 based) Oct 22 22:57:30 ubuntu kernel: [ 46.517215] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 Oct 22 22:57:30 ubuntu kernel: [ 46.517225] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21 Oct 22 22:57:30 ubuntu kernel: [ 46.517238] ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Oct 22 22:57:30 ubuntu kernel: [ 46.578274] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20 Oct 22 22:57:30 ubuntu kernel: [ 46.578280] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 20 (level, high) -> IRQ 18 Oct 22 22:57:30 ubuntu kernel: [ 46.900604] intel8x0_measure_ac97_clock: measured 52793 usecs Oct 22 22:57:30 ubuntu kernel: [ 46.900610] intel8x0: clocking to 48000 Oct 22 22:57:30 ubuntu kernel: [ 47.208450] ivtv0: loaded v4l-cx2341x-enc.fw firmware (4158612376 bytes) Oct 22 22:57:30 ubuntu kernel: [ 47.424328] ivtv0: Encoder revision: 0x02050032 Oct 22 22:57:30 ubuntu kernel: [ 47.424332] ivtv0: Recommended firmware version is 0x02060039. Oct 22 22:57:30 ubuntu kernel: [ 47.484674] tveeprom 2-0050: Hauppauge model 26032, rev C199, serial# 8359175 Oct 22 22:57:30 ubuntu- kernel: [ 47.484680] tveeprom 2-0050: tuner model is TCL 2002N 5H (idx 99, type 50) Oct 22 22:57:30 ubuntu kernel: [ 47.484683] tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) Oct 22 22:57:30 ubuntu kernel: [ 47.484686] tveeprom 2-0050: audio processor is CX25841 (idx 35) Oct 22 22:57:30 ubuntu kernel: [ 47.484689] tveeprom 2-0050: decoder processor is CX25841 (idx 28) Oct 22 22:57:30 ubuntu kernel: [ 47.484692] tveeprom 2-0050: has no radio, has IR receiver, has IR transmitter Oct 22 22:57:30 ubuntu kernel: [ 47.484695] ivtv0: Autodetected Hauppauge WinTV PVR-150 Oct 22 22:57:30 ubuntu kernel: [ 47.484698] ivtv0: reopen i2c bus for IR-blaster support Oct 22 22:57:30 ubuntu kernel: [ 47.576126] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) Oct 22 22:57:30 ubuntu kernel: [ 47.791103] cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) Oct 22 22:57:30 ubuntu kernel: [ 52.102889] cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes) Oct 22 22:57:30 ubuntu kernel: [ 52.218192] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) Oct 22 22:57:30 ubuntu kernel: [ 52.275914] tuner 2-0061: type set to 50 (TCL 2002N) Oct 22 22:57:30 ubuntu kernel: [ 52.611960] ivtv0: Registered device video0 for encoder MPEG (4 MB) Oct 22 22:57:30 ubuntu kernel: [ 52.612254] ivtv0: Registered device video32 for encoder YUV (2 MB) Oct 22 22:57:30 ubuntu kernel: [ 52.612547] ivtv0: Registered device vbi0 for encoder VBI (1 MB) Oct 22 22:57:30 ubuntu kernel: [ 52.612752] ivtv0: Registered device video24 for encoder PCM audio (1 MB) Oct 22 22:57:30 ubuntu kernel: [ 52.640505] ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 Oct 22 22:57:30 ubuntu kernel: [ 52.640646] ivtv: ==================== END INIT IVTV ==================== I am stuck at this point need some advise please. ![]() Last edited by Akriss; October 30th, 2007 at 03:42 PM.. Reason: Added quotes on how to fix it |
||
|
|
|
|
|
#2 |
|
Ubuntu Developer
![]() Join Date: Oct 2005
Location: Austin, TX
Beans: 2,725
Ubuntu 8.04 Hardy Heron
|
Re: Adding lirc_pvr150 module = system hard lock
Rather than both lirc_i2c and lirc_pvr150:
can you try with just lirc_pvr150 in the MODULES= line? |
|
|
|
|
|
#3 | |
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
Re: Adding lirc_pvr150 module = system hard lock
Yes I have tryed that as well.
from above Quote:
|
|
|
|
|
|
|
#4 |
|
Ubuntu Developer
![]() Join Date: Oct 2005
Location: Austin, TX
Beans: 2,725
Ubuntu 8.04 Hardy Heron
|
Re: Adding lirc_pvr150 module = system hard lock
Well that's not good. I'm wondering if perhaps the lirc_pvr150 author hasn't made this module compatible with 2.6.22. You may very well be the first person actually testing it on Gutsy (which would be rather unfortunate). Lets see if you can narrow this down a little further.
rmmod all lirc modules. Hit ctrl alt f1 to switch to virtual terminal 1. login here. From here modprobe lirc_pvr150. See if you get some kernel backtrace here about what is happening. |
|
|
|
|
|
#5 |
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
Re: Adding lirc_pvr150 module = system hard lock
$modprobe lirc_pvr150
Code:
WARNING Error inserting lirc_dev (/lib/modules/2/6/22-14-generic/ubuntu/media/lirc/lirc_dev/lirc_dev.ko) Operation not permitted WARNING Error inserting lirc_pvr150 (/lib/modules/2/6/22-14-generic/ubuntu/media/lirc/lirc_pvr150/lirc_pvr150.ko) Operation not permitted And that with just lirc_pvr150 in the module line. ![]() Last edited by Akriss; October 23rd, 2007 at 02:34 AM.. Reason: more info w/sudo |
|
|
|
|
|
#6 |
|
Ubuntu Developer
![]() Join Date: Oct 2005
Location: Austin, TX
Beans: 2,725
Ubuntu 8.04 Hardy Heron
|
Re: Adding lirc_pvr150 module = system hard lock
Sorry should have been more specific
Code:
sudo modprobe lirc_pvr150 |
|
|
|
|
|
#7 |
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
Re: Adding lirc_pvr150 module = system hard lock
LOL
I edited my post as you posted. I tryed it hard locked. =/ |
|
|
|
|
|
#8 |
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
Re: Adding lirc_pvr150 module = system hard lock
After Google'n around for a few hours looking for tips, I came upon the answer on "Mark's Braindump" page.
http://www.blushingpenguin.com/mark/blog/?p=24 He has a patched lirc for the hauppauge pvr 150 blaster and kernel's >2.6.16. Works like a champ. |
|
|
|
|
|
#9 | |
|
Ubuntu Developer
![]() Join Date: Oct 2005
Location: Austin, TX
Beans: 2,725
Ubuntu 8.04 Hardy Heron
|
Re: Adding lirc_pvr150 module = system hard lock
Quote:
So if I attempt to prepare a diff between the latest posted on Mark's site and our current kernel module, and post a deb, would you be willing to revert your changes temporarily to test it so that we can fix this for everyone? Thanks |
|
|
|
|
|
|
#10 |
|
5 Cups of Ubuntu
![]() Join Date: Oct 2007
Beans: 26
|
Re: Adding lirc_pvr150 module = system hard lock
Yes I am willing to help out.
I have been doing the installs on a spare HD till I get all the kinks sorted out and then will move it to the production HD when all is working well. |
|
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|