LinHES Forums http://forums.linhes.org/ |
|
Upgrading to R5F1 - irblaster won't work http://forums.linhes.org/viewtopic.php?f=1&t=16458 |
Page 1 of 1 |
Author: | BluesBrian [ Wed Sep 12, 2007 12:06 am ] |
Post subject: | Upgrading to R5F1 - irblaster won't work |
under R5C7, I had my irblaster working great. Getting it to work post-upgrade is proving to be a real challenge. I've gone over everything that I can squeek out of Greg Frost's tread.. http://mysettopbox.tv/phpBB2/viewtopic.php?t=9352 when I execute Code: /etc/init.d/irblaster start
I get the message Quote: FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error
################################################## ## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ## ## is using. ## ################################################## I'm guessing that my symbolic links are screwed up.. but I've run out of ideas on how to fix it. Thanks! |
Author: | BluesBrian [ Wed Sep 12, 2007 11:03 pm ] |
Post subject: | |
Here's my /etc/irblaster/hardware.conf Code: # /etc/irblaster/hardware.conf
# # Author: Greg Frost # The COM Port used by the IRBlaster. Set it to COM1 COM2 or "". IRBLASTER_SERIAL_PORT="COM1" # Set this to the lirc device that will be used by lirc_serial. In my case # it is /dev/lirc. I have a USB remote, so my remote does not use the # /dev/lirc device, so it is used by lirc_serial for my ir blaster. If you # have a remote that uses /dev/lirc, the blaster may user /dev/lirc1. Not # sure. IRBLASTER_DEVICE="/dev/lirc1" |
Author: | tjc [ Wed Sep 12, 2007 11:29 pm ] |
Post subject: | |
Why didn't you go to R5F27 which has been out since Sunday? |
Author: | BluesBrian [ Thu Sep 13, 2007 8:08 am ] |
Post subject: | |
tjc wrote: Why didn't you go to R5F27 which has been out since Sunday? What can I say, my psychic interface isn't working. .. I started the upgrade to R5F1 on 09/04. I'm tempted to charge-along with the R5F27 upgrade, although, I would like to understand why the irblaster isn't working first... and get it working.
|
Author: | Greg Frost [ Thu Sep 13, 2007 3:13 pm ] |
Post subject: | |
If you read the hints and tips you would have seen something about the possibility of xorg grabbing the serial port for a serial mouse. dont know if this is your problem, but I didn't see you see that you had checked it. |
Author: | BluesBrian [ Thu Sep 13, 2007 8:55 pm ] |
Post subject: | |
Greg Frost wrote: If you read the hints and tips you would have seen something about the possibility of xorg grabbing the serial port for a serial mouse. dont know if this is your problem, but I didn't see you see that you had checked it.
Right! I didn't make the connection. Now done.. X restarted. restarting irblaster comes up with the same error. I'll have to admit, when it comes to the /dev directory, I'm in the fog. Here's what it looks like: Code: ls -l /dev/ttyS* andcrw-rw---- 1 root dialout 4, 64 Sep 13 19:21 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Sep 13 19:21 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Sep 13 19:21 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Sep 13 19:21 /dev/ttyS3 Code: ls -l /dev/lirc* crw-rw---- 1 root video 61, 0 Sep 13 19:21 /dev/lirc0 srw-rw-rw- 1 root root 0 Sep 13 19:21 /dev/lircd I re-ran the irblaster.sh config script and it gives me Code: Selected Motorola_DCT2244.
cp: cannot stat `/usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblasterd.conf': No such file or directory System startup links for /etc/init.d/irblaster already exist. Stopping irblaster daemon: irblasterdNo process in pidfile `/var/run/irblasterd.pid' found running; none killed. . FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error ################################################## ## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ## ## is using. ## ################################################## |
Author: | slowtolearn [ Thu Sep 13, 2007 9:18 pm ] |
Post subject: | |
BluesBrian wrote: I re-ran the irblaster.sh config script and it gives me[code]Selected Motorola_DCT2244. I can't speak for R5F1 but this file is called /usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblaster.conf (no d) in R5F27. I suspect this error is the crux of your problem.
cp: cannot stat `/usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblasterd.conf': No such file or directory You could A) try copying /usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblasterd.conf to /usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblaster.conf or B) edit the irblaster.sh script to point to the correct file. |
Author: | BluesBrian [ Thu Sep 13, 2007 10:38 pm ] |
Post subject: | |
slowtolearn wrote: You could A) try copying /usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblasterd.conf to /usr/local/share/knoppmyth/irblaster/Motorola_DCT2244/irblaster.conf or B) edit the irblaster.sh script to point to the correct file.
I did Plan A .. and got: Code: Selected Motorola_DCT2244. Shorter error message! System startup links for /etc/init.d/irblaster already exist. Stopping irblaster daemon: irblasterdNo process in pidfile `/var/run/irblasterd.pid' found running; none killed. . FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error ################################################## ## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ## ## is using. ## ################################################## Then I deleted the files in /etc/irblaster, re-ran the irblaster.sh script and got Code: Selected Motorola_DCT2244. .. so I'm thinking that "System startup links" is the key??? Is that what the "update-rc.d" is about??? .. so I ran System startup links for /etc/init.d/irblaster already exist. Stopping irblaster daemon: irblasterdNo process in pidfile `/var/run/irblasterd.pid' found running; none killed. . FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error ################################################## ## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ## ## is using. ## ################################################## Code: update-rc.d -f irblaster remove then re-ran the irblaster.sh script again.. and got: Code: Selected Motorola_DCT2244. Looks like were getting.... I'm still leaning toward something that's dorked in the device setup (fogged).
Adding system startup for /etc/init.d/irblaster ... /etc/rc0.d/K21irblaster -> ../init.d/irblaster /etc/rc1.d/K21irblaster -> ../init.d/irblaster /etc/rc6.d/K21irblaster -> ../init.d/irblaster /etc/rc2.d/S21irblaster -> ../init.d/irblaster /etc/rc3.d/S21irblaster -> ../init.d/irblaster /etc/rc4.d/S21irblaster -> ../init.d/irblaster /etc/rc5.d/S21irblaster -> ../init.d/irblaster Stopping irblaster daemon: irblasterdNo process in pidfile `/var/run/irblasterd.pid' found running; none killed. . FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error ################################################## ## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ## ## is using. ## ################################################## |
Author: | Greg Frost [ Thu Sep 13, 2007 11:11 pm ] |
Post subject: | |
BluesBrian wrote: Code: FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error Why can't it insert the lirc_serial module? Are your serial ports enabled in the bios? Something else using the serial port? lirc_serial already loaded? |
Author: | BluesBrian [ Fri Sep 14, 2007 8:23 am ] |
Post subject: | |
Greg Frost wrote: BluesBrian wrote: Code: FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error (1) Why can't it insert the lirc_serial module? (2) Are your serial ports enabled in the bios? (3) Something else using the serial port? (4) lirc_serial already loaded? (1) I dunno how that works (2) sure (3) There shouldn't be! how can I tell? (4) if so, can I unload it, then run irblaster.sh again? (how would I unload it?) I have an hd with R5C7 .. a backup of my primary system (the primary having been upgraded to R5F1) .. if I shutdoen/swap drives/restart.. the irblaster works. I'll concluded that there is no bios setting wrong or hardware issue. |
Author: | Greg Frost [ Fri Sep 14, 2007 4:45 pm ] |
Post subject: | |
I'm not sure what would cause that Input/Output error. To see if the module is loaded, run the command (as root) Code: lsmod | grep lirc
If it is not, try running: modprobe lirc_serial what happens? are there any suspicious error messages in /var/log/messages? What is in the file /etc/mythtv/modules/lirc_serial? What type of remote does your system use? |
Author: | BluesBrian [ Fri Sep 14, 2007 8:24 pm ] |
Post subject: | |
Greg Frost wrote: I'm not sure what would cause that Input/Output error. To see if the module is loaded, run the command (as root) Code: lsmod | grep lirc If it is not, try running: modprobe lirc_serial what happens? are there any suspicious error messages in /var/log/messages? What is in the file /etc/mythtv/modules/lirc_serial? What type of remote does your system use? lsmod | grep lirc Code: lirc_i2c 12420 2 modprobe lirc_seriallirc_dev 16772 1 lirc_i2c i2c_core 20864 18 i2c_ec,cx88_vp3054_i2c,saa7134_dvb,dvb_pll,saa7134,ir_kbd_i2c,tda1004x,dvb_bt8xx,cx88xx,bttv,lirc_i2c, saa7127,ivtv,saa7115,msp3400,tuner,i2c_algo_bit,tveeprom Code: FATAL: Error inserting lirc_serial (/lib/modules/2.6.18-chw-13/misc/lirc_serial.ko): Input/output error cat messages |grep lirc Code: Sep 14 18:59:27 MythBox kernel: lirc_dev: IR Remote Control driver registered, at major 61 Sep 14 18:59:27 MythBox kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR) Sep 14 18:59:27 MythBox kernel: lirc_dev: lirc_register_plugin: sample_rate: 10 Sep 14 18:59:32 MythBox kernel: lirc_serial: auto-detected active high receiver Sep 14 18:59:32 MythBox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0 Sep 14 18:59:32 MythBox kernel: lirc_dev: lirc_register_plugin: no module owner registered Sep 14 19:03:48 MythBox kernel: lirc_serial: auto-detected active high receiver Sep 14 19:03:48 MythBox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0 Sep 14 19:03:48 MythBox kernel: lirc_dev: lirc_register_plugin: no module owner registered cat messages |grep ttyS Code: Sep 14 18:59:27 MythBox kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A cat /etc/mythtv/modules/lirc_serialSep 14 18:59:27 MythBox kernel: 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Code: alias char-major-61 lirc_serial
options lirc_serial irq=4 io=0x3f8 PVR-350 - "silver" remote (A415-HPG) |
Author: | Greg Frost [ Fri Sep 14, 2007 11:21 pm ] |
Post subject: | |
Is it possible for me to ssh in to your box and poke around to see if I can see whats wrong? |
Author: | BluesBrian [ Mon Oct 08, 2007 8:31 am ] |
Post subject: | |
I did solve this issue by running "Auto Upgrade" to R5F27. Keep in mind the important locations for configuration bits: /etc/irblaster/hardware.conf /etc/irblaster/irblasterd.conf /etc/irblaster/channel_change.sh /etc/init.d/irblaster /dev/irblasterd |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |