I'm trying to build a Mythtv system, based on OpenSUSE 10.3. I've got almost everything installed and working, and am now trying, so far unsuccessfully, to get the remote control configured. My remote control is that supplied with a Hauppauge PVR-150. (Grey, not serial, not USB, with the 4 colored buttons arranged in a row at the bottom, not arranged around the 'OK' button near the top.) According to YAST lirc is installed. During my troubleshooting, I returned to YAST, and installed the 4 lirc kernel modules: default, bigsmp, xen, and xenpae. I was pretty sure I didn't need any other than 'default', but selected all of them in case I was wrong. Of course, that resulted in adding all of the additional kernels to my system & boot menu as well, but I can always either tolerate that or remove the others later, I assume. After adding the additional modules, I still have no functional lirc. I HAVE found an 'Oops' in /var/log/messages/, and also saw a message at the lirc sourceforge site mentioning a bug in lirc for the 2.6.22 kernel, and a patch to remedy the bug. ( http://sourceforge.net/mailarchive/message.php?msg_id=14912-18254%40sneakema... ) My system is running kernel 2.6.22.13-0.3. Here is an excerpt from my /var/log/messages/, shwoing the 'Oops': Dec 27 01:47:16 mythbe su: (to root) mythtv on /dev/pts/1 Dec 27 01:47:31 mythbe kernel: lirc_dev: IR Remote Control driver registered, at major 61 Dec 27 01:47:31 mythbe kernel: bttv: driver version 0.9.17 loaded Dec 27 01:47:31 mythbe kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture Dec 27 01:47:31 mythbe kernel: cx2388x v4l2 driver version 0.0.6 loaded Dec 27 01:47:31 mythbe kernel: lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150)) Dec 27 01:47:31 mythbe kernel: BUG: unable to handle kernel paging request at virtual address 00dddf01 Dec 27 01:47:31 mythbe kernel: printing eip: Dec 27 01:47:31 mythbe kernel: e0c850a9 Dec 27 01:47:31 mythbe kernel: *pdpt = 0000000002902001 Dec 27 01:47:31 mythbe kernel: *pde = 0000000000000000 Dec 27 01:47:31 mythbe kernel: Oops: 0000 [#1] Dec 27 01:47:31 mythbe kernel: SMP Dec 27 01:47:31 mythbe kernel: last sysfs file: /block/md1/md/raid_disks Dec 27 01:47:31 mythbe kernel: Modules linked in: cx8800 cx88xx bttv video_buf compat_ioctl32 btcx_risc lirc_i2c lirc_dev ip6t_LOG nf_conntrack_ipv6 xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq microcode ir_kbd_i2c ir_common snd_seq_device ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_mangle iptable_nat nf_nat iptable_filter ip6table_mangle nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables ip6table_filter ip6_tables x_tables ipv6 apparmor xfs loop dm_mod wm8775 cx25840 tuner 8139too ivtv firmware_class i2c_algo_bit cx2341x tveeprom videodev 8139cp v4l2_common mii v4l1_compat snd_intel8x0 snd_ac97_codec button ac97_bus snd_pcm usb_storage snd_timer shpchp snd i2c_i801 iTCO_wdt iTCO_vendor_support soundcore intel_agp snd_page_alloc agpgart pci_hotplug i2c_core parport_pc ide_core sr_mod cdrom parport rtc_cmos rtc_core rtc_lib sg raid456 xor raid0 sd_mod uhci_hcd ehci_hcd usbcore edd raid1 ext3 mbcache jbd fan ata_piix libata scsi_mod thermal processor Dec 27 01:47:31 mythbe kernel: CPU: 0 Dec 27 01:47:31 mythbe kernel: EIP: 0060:[<e0c850a9>] Tainted: G N VLI Dec 27 01:47:31 mythbe kernel: EFLAGS: 00210216 (2.6.22.13-0.3-bigsmp #1) Dec 27 01:47:31 mythbe kernel: EIP is at __i2c_check_addr+0x26/0x35 [i2c_core] Dec 27 01:47:31 mythbe kernel: eax: dddf0029 ebx: dddf01e1 ecx: 00dddf01 edx: 00000071 Dec 27 01:47:31 mythbe kernel: esi: 00000071 edi: dddf0029 ebp: fffffff0 esp: c93a1c08 Dec 27 01:47:31 mythbe kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Dec 27 01:47:31 mythbe kernel: Process modprobe (pid: 4460, ti=c93a0000 task=de023550 task.ti=c93a0000) Dec 27 01:47:31 mythbe kernel: Stack: dbb10400 dbb10460 e0c85c88 00000001 c0122381 dddfebd8 dbb10400 e0987cec Dec 27 01:47:31 mythbe kernel: dbb1047a dddf0059 dbb10400 e0987cec dbb1047a 00000071 e098728b e0987d52 Dec 27 01:47:31 mythbe kernel: 00000071 dbb10464 000051fd dddfebb8 00000071 00000000 c93a1cac dddfebb8 Dec 27 01:47:31 mythbe kernel: Call Trace: Dec 27 01:47:31 mythbe kernel: [<e0c85c88>] i2c_attach_client+0x29/0x175 [i2c_core] Dec 27 01:47:31 mythbe kernel: [<c0122381>] __cond_resched+0x18/0x29 Dec 27 01:47:31 mythbe kernel: [<e098728b>] ir_attach+0x24c/0x260 [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<e09875a1>] ir_probe+0xa5/0x2ad [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<c01d374a>] __next_cpu+0x12/0x20 Dec 27 01:47:31 mythbe kernel: [<e0c863a6>] i2c_register_driver+0x9e/0xce [i2c_core] Dec 27 01:47:31 mythbe kernel: [<e09874f8>] init_module+0x42/0x46 [lirc_i2c] Dec 27 01:47:31 mythbe kernel: [<c014491f>] sys_init_module+0x172c/0x1802 Dec 27 01:47:31 mythbe kernel: [<c0176593>] do_sync_read+0x0/0x10a Dec 27 01:47:31 mythbe kernel: [<e0963b78>] videobuf_read_stream+0x179/0x209 [video_buf] Dec 27 01:47:31 mythbe kernel: [<e0963b74>] videobuf_read_stream+0x175/0x209 [video_buf] Dec 27 01:47:31 mythbe kernel: [<c017665a>] do_sync_read+0xc7/0x10a Dec 27 01:47:31 mythbe kernel: [<e0963079>] videobuf_read_one+0x2ca/0x2cb [video_buf] Dec 27 01:47:31 mythbe kernel: [<e0962000>] pci_dma_sync_sg_for_cpu+0x0/0x1 [video_buf] Dec 27 01:47:31 mythbe kernel: [<e097ec82>] lirc_register_plugin+0x0/0x448 [lirc_dev] Dec 27 01:47:31 mythbe kernel: [<c0104ea2>] sysenter_past_esp+0x6b/0xa9 Dec 27 01:47:31 mythbe kernel: [<c02c0000>] xfrm4_rcv_encap+0x1d4/0x3f4 Dec 27 01:47:31 mythbe kernel: ======================= Dec 27 01:47:31 mythbe kernel: Code: d2 c3 31 c0 c3 56 89 d6 53 8b 88 b8 01 00 00 8d 98 b8 01 00 00 eb 14 0f b7 81 5a fe ff ff 39 f0 75 07 b8 f0 ff ff ff eb 0e 89 d1 <8b> 11 0f 18 02 90 39 d9 75 e2 31 c0 5b 5e c3 56 89 d6 53 89 cb Dec 27 01:47:31 mythbe kernel: EIP: [<e0c850a9>] __i2c_check_addr+0x26/0x35 [i2c_core] SS:ESP 0068:c93a1c08 My first question is, is the above the result of the bug mentioned on the sourceforge page? Secondly, I found an online how-to for installing Mythtv to Suse 10.0 that advises removing the lirc packaged with Suse, and compiling/installing lirc from source. I'm using 10.3, & I don't know whether or not the advice holds for me. Deciding to give it a shot though, I launched YAST to try and uninstall the exisiting lirc on my system. YAST warned me that many components, nearly all or all of them Myth-related, were dependent on lirc, and removal of lirc would break those components. Rather than going ahead with the task, I cancelled. (This was before adding the various kernel modules to the system.) My Second question: If I remove every lirc piece through YAST, and then download, compile, and install the latest lirc, will the installed components on my system that are dependent on lirc break? Or will they 'see' the new llirc just fine? I'm nearly ready to give up, reformat, and try again from scratch, but I'm hoping to avoid that. Thanks, Steve -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org