LinHES Forums • View topic - Missing /dev/lirc* after Upgrade To 5E50

Board index KnoppMyth General

All times are UTC - 6 hours

Missing /dev/lirc* after Upgrade To 5E50

Page 2 of 3

[ 31 posts ]

Go to page Previous 1, 2, 3 Next

Print view

Previous topic Next topic

Author

Message

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 6:54 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

Also sorry for all the post just trying to post as much information as possible but here is what i get from this:

cat /proc/bus/input/devices and search for the line N: Name="cx88 IR (Hauppauge"

Code:

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c024 Version=9802
N: Name="B16_b_02 USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-8/input0
S: Sysfs=/class/input/input2
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=f0000 0 0 0 0 0 0 0 0
B: REL=103

cat: and: No such file or directory
cat: search: No such file or directory
cat: for: No such file or directory
cat: the: No such file or directory
cat: line: No such file or directory
cat: N:: No such file or directory
cat: Name=cx88 IR (Hauppauge: No such file or directory

Top

tjc

Post subject:

Posted: Sun Mar 25, 2007 9:46 am

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

ethnarch3 wrote:

cat /proc/bus/input/devices and search for the line N: Name="cx88 IR (Hauppauge"

Oh my... Don't know where you got that from, but only the cat /proc/bus/input/devices part was the command to execute. ;-)

As for the rest it looks OK, it looks like the hardware is being seen and the driver module is being loaded.

Double check your physical connection. The IR dongle should be plugged in to the smaller black jack at the very bottom of the card. This tends to be very near the edge of the slot and the case can interfer with plugging it in all the way. Newer dongles come with one corner of the plastic on the plug nipped off to make this easier. After that, make sure you've got good batteries and a clear line of sight from the remote to the sensor eye on the dongle.

Beyond that... There is some odd flakyness with remotes in R5E50. Do this and report the results:

Code:

root@black2:~# fuser -av /dev/lirc*

                     USER        PID ACCESS COMMAND
/dev/lirc0:          root       2892 F.... lircd

/dev/lirc1:
/dev/lircd:          root       2892 F.... lircd

Also check in /var/log/syslog for messages about "unknown key" as described in this thread http://mysettopbox.tv/phpBB2/viewtopic.php?t=13137

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 10:18 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

I think i destroyed my lirc i found this on knoppmyth wiki and i was trying to go through it thinking maybe if i recompiled lirc it might help.

which is where i got that qoute from:

Quote:

I don't know really if you need to compile a new lirc, perhaps you first try starting at (2).
(1)
apt-get remove lirc
apt-get remove lirc-modules-source
apt-get remove lirc-x
apt-get remove lirc-svga
Get lirc 0.8.0 here: http://prdownloads.sourceforge.net/lirc ... 8.0.tar.gz
Go to a console (Ctrl+Alt+F2) and log in as root. Extract the file with tar xzf lirc-0.8.0.tar.gz.
cd to the new directory lirc-0.8.0 and type
./configure --prefix=/usr --with-driver=devinput --with-x --sysconfdir=/etc/lirc --with-syslog=LOG_USER
(Do not run the setup script ./setup.sh!)
Type make and make install.
(2)
For the next step it is good to boot without connected keyboard or mouse (in fact you don't really want them at your KnoppMyth box, right?) - that is necessary because the input events are mapped dynamically during bootup.
Type cat /proc/bus/input/devices and search for the line N: Name="cx88 IR (Hauppauge Nova-S-Plus ". Two lines below there should be this: S: Sysfs=/class/input/inputX where the X ist a number - this is your input device for the remote - in this example input0.
Edit /etc/lirc/hardware.conf with an editor and add -d /dev/input/event0 to LIRCD_ARGS="", change default to dev/input at DRIVERS="default" and change lirc_i2c to cx88cc at MODULES=... . I added additionally LIRCD_CONF="/etc/lircd.conf".

when i got to the cat out line it never outputted anything so of course i couldnt' finish this to put the correct info in.

So now i officially have a non working lirc. I tried to recompile it using this thread:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=4609&postdays=0&postorder=asc&highlight=lirc&start=0

When i get to this point:

Quote:

12.) To test:
Code:
# rmmod lirc_i2c
# modprobe lirc_i2c
# lircd
# irw

nothing happens with the test

oh yeah and this is what i get now with the lirc-reconfig.sh

Quote:

root@mythtv:~# lirc-reconfig.sh
These are some of the more popular remotes. If you don't
see your remote listed, please contact knoppmyth@gmail.com
with details on your remote.
NOTE: You should only contact knoppmyth@gmail.com
With details on setting up a remote that isn't
listed. If your remote isn't listed or doesn't work,
use the forum for support or check lirc.org.

1) adaptec 16) firefly 31) pinnacle_systems
2) animax 17) hauppauge 32) pixelview
3) asus 18) hercules 33) provideo
4) atiusb 19) imon 34) rca-6n1
5) avermedia 20) iodata 35) remotec
6) avermedia98 21) irblaster 36) sasem
7) bestbuy 22) knc_one 37) sigma_designs

caraca 23) kworld 38) silitek
9) chronos 24) leadtek 39) streamzap
10) commandir 25) leadtek_pvr200 40) technisat
11) cph03x 26) life-view 41) tekram
12) creative 27) logitech 42) winfast_rm0010
13) dvico 28) mceusb 43) x10
14) ea65 29) packard_bell 44) Quit
15) ericsson 30) pcmak
Choose your remote: 17

Which Hauppauge remote do you have?
a. Black remote
b. Grey remote
c. Silver remote (A415-HPG)
d. PVR-150 w/ transmitter and receiver
e. Radio Shack Universal Remote
f. PVR-150 w/ transmitter and receiver "dog bone"

q. quit
c
Stopping lirc daemon: lircmd lircd.
Starting lirc daemon: lircdDriver `default' not supported.
Supported drivers:
dev/input

With all of the things i have probably destroyed and changed i am thinking maybe i should go through the auto-upgrade again and start clean. Can i upgrade to the same version again? or just use the files that are still in the backup folder to upgrade?

Note: i originall upgraded from R5d1 to R5E50

Top

tjc

Post subject:

Posted: Sun Mar 25, 2007 10:26 am

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

You can auto-upgrade to the same version. It's even one of the standard recommendations for folks who roach something like this. Make sure you don't miss the R5E50 Upgrade Hints thread - http://mysettopbox.tv/phpBB2/viewtopic.php?t=13108

I do still recommend applying the new ivtv drivers since they seem to have reduced the issues I've had with this.

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 10:36 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

I will go back through all the suggestions you gave me again, but this time do it in a more organized way. I am afraid all the things i tried in between your suggestion may have changed something.

I'll let you know where i am at after i am going through all the steps.

I went through the hints for R5E50 when i first upgraded from R5D1 so i think i should be in good condition.

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 10:59 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

Ok so after i reinstalled this is what i have done

1. edit hardware.conf
nano /etc/lirc/hardware.conf

changed the line

Quote:

DEVICE="/dev/lirc"

now the file looks like this

Quote:

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE="/dev/lirc0"
MODULES="lirc_dev lirc_i2c"

Then I ran lirc-reconfig.sh
entered 17
selected c for the ap14 remote

then typed "fuser -av /dev/lirc*"

Quote:

/# fuser -av /dev/lirc*

USER PID ACCESS COMMAND
/dev/lirc0:
/dev/lircd: root 5122 F.... lircd

then i rebooted just to make sure the settings were going through
and i ran "fuser -av /dev/lirc*" and it now says:

Quote:

root@mythtv:~# fuser -av /dev/lirc*
Cannot stat /dev/lirc*: No such file or directory
Cannot stat /dev/lirc*: No such file or directory

USER PID ACCESS COMMAND
/dev/lirc*:

this is similar to what i was originally getting, the lirc device would dissapear on reboot.

I am going to recompile ivtv now, just waiting for the kernel source to compile.....

Ok after recompiling the ivtv drivers from:
http://www.knoppmythwiki.org/index.php?page=CompileIvtv-0.10.0

Quote:

root@mythtv:~# fuser -av /dev/lirc*
Cannot stat /dev/lirc*: No such file or directory
Cannot stat /dev/lirc*: No such file or directory

USER PID ACCESS COMMAND

Then i reran lirc-reconfig.sh with the same options as above
I ran fuser -av /dev/lirc*

Quote:

root@mythtv:~# fuser -av /dev/lirc*

USER PID ACCESS COMMAND
/dev/lirc0:
/dev/lircd: root 3228 F.... lircd

no luck yet then i tried to reboot...

After reboot i ran fuser -av /dev/lirc* again

Quote:

root@mythtv:~# fuser -av /dev/lirc*
Cannot stat /dev/lirc*: No such file or directory
Cannot stat /dev/lirc*: No such file or directory

USER PID ACCESS COMMAND
/dev/lirc*:

Oh yeah and i might as well add this

Quote:

root@mythtv:~# lsmod | grep lirc
lirc_i2c 12420 0
lirc_dev 16628 1 lirc_i2c
i2c_core 20864 23 cx88xx,lirc_i2c,dvb_bt8xx,nxt6000,mt352,sp887x,dst,bttv,dvb_pll,cx24110,or51211,zl10353,lgdt330x,wm8775,cx25840,saa7127,ivtv,saa7115,msp3400,tuner,i2c_algo_bit,tveeprom,i2c_nforce2

root@mythtv:~# dmesg | grep lirc
lirc_dev: IR Remote Control driver registered, at major 61
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
lirc_dev: lirc_register_plugin: sample_rate: 10

any suggestions where to go from here?

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 12:19 pm

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

I tried this and it seems to be receiving commands but still won't control mythtv strangely.

Quote:

root@mythtv:~# rmmod lirc_i2c
root@mythtv:~# modprobe lirc_i2c
root@mythtv:~# lircd
lircd: there seems to already be a lircd process with pid 3220
lircd: otherwise delete stale lockfile /var/run/lircd.pid
root@mythtv:~# irw
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 01 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 01 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f96 00 LEFT grayHauppauge
0000000000001f96 01 LEFT grayHauppauge

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 12:34 pm

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

I think i figured out the problem i just don't know what a good solution is.

I found what i was missing after i realized the commands were being received by lirc is that only the myth-frontend needed to be restarted.

What's happening is that the modules perhaps are not being loaded properly when the computer is restarted. Which is why everytime i restart the /dev/lirc folders disappear. If i then run lirc-reconfig.sh and only restart myth frontend then the remote control works(all this time i didn't realize that ehh wish i tried that earlier).

So how do i get this to load properly when the computer reboots?

Top

tjc

Post subject:

Posted: Sun Mar 25, 2007 2:53 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

- You need to edit the hardware configuration file *after* running the reconfigure script. The upgrade hints are quite specific about this...

- It looks like you have the grey remote not the silver one. Those names suck, but they're traditional, both remotes are basically the same silver/grey metal flake color. The so-called "grey" remote is shaped like a flattened cigar, broadest in the middle (like a brontosaurus), with the "colored" buttons in a square around the OK, on the inside of the batterydoor it says "R808 OH/S 2-3". The "silver" remote is narrower in the middle, with the "colored" buttons in a line at the bottom, on the inside of the batterydoor it says "A415 OH/S 1-4".

Do these steps in the order listed as root:

0) You've already upgrade the ivtv driver which is good.

1) Run the reconfigure script and pick the hauppauge grey remote.

2) Edit the lirc hardware config file and fix the device. Make sure the rest looks like the one I posted.

3) Reboot. (It's easier that walking you through the sequence of restarts needed.)

Top

ethnarch3

Post subject:

Posted: Sun Mar 25, 2007 3:42 pm

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

I do have the A415 OH/S 1-4 -- i am kinda wondering what led you to believe i do not. Maybe i am doing something else wrong?

Yeah i actually did edit the hardware.conf file first the first time i did this in the correct order. I figured i would try it this way this time.

My problem now however is that the hardware.conf file is already set correctly Device="/dev/lirc0" before i run the lirc-reconfig.sh script and after it still says Device="/dev/lirc0" so there is nothing to change back. But i rebooted the computer and the same thing the remote doesn't work.
I can however run the lirc-reconfig.sh script like before and then restart just the frontend and the remote works.

Perhaps i should change it back to /dev/lirc then run the script and then change it again and reboot?

Top

tjc

Post subject:

Posted: Sun Mar 25, 2007 9:53 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

This is what led me to think you have the other remote.

ethnarch3 wrote:

Quote:

root@mythtv:~# irw
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 01 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f95 01 DOWN grayHauppauge
0000000000001f95 00 DOWN grayHauppauge
0000000000001f96 00 LEFT grayHauppauge
0000000000001f96 01 LEFT grayHauppauge

Look at the devices shown by:

Code:

ls -al /dev/lirc*

You should see something like this:

Code:

root@black2:/var/log# ls -al /dev/lirc*
crw-rw---- 1 root video 61, 0 Mar 17 23:08 /dev/lirc0
crw-rw---- 1 root video 61, 1 Mar 17 23:08 /dev/lirc1
srw-rw-rw- 1 root root      0 Mar 17 23:09 /dev/lircd

Since you only have one card you should only have lirc0 and not lirc1.

Top

ethnarch3

Post subject:

Posted: Mon Mar 26, 2007 4:15 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

yeah this is what ls -al /dev/lirc* shows

Code:

root@mythtv:~# ls -al /dev/lirc*
crw-rw---- 1 root video 61, 0 Mar 25 22:00 /dev/lirc0
srw-rw-rw- 1 root root      0 Mar 25 22:00 /dev/lircd

I have the same problem previously though when i reboot the computer i don't get either of those lines(meaning /dev/lirc0 or dev/lircd). And of course the remote doesn't work till i run lirc-reconfig.sh again and then restart the frontend.

So it's not loading on bootup for some reason

Top

tjc

Post subject:

Posted: Mon Mar 26, 2007 6:15 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

What does this show?

Code:

root@black2:/var/log# ls -al /etc/rc?.d | grep lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 K20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 K20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 S20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 S20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 S20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 S20lirc -> ../init.d/lirc
lrwxrwxrwx   1 root root   14 Mar 16 23:37 K20lirc -> ../init.d/lirc

Also what does this show?

Code:

root@black2:/var/log# ls -l /etc/init.d/lirc
-rwxr-xr-x 1 root root 3078 Jan  7 04:06 /etc/init.d/lirc
root@black2:/var/log# md5sum /etc/init.d/lirc
3b1cf2cf4997c6510d5ee769c2daa4f2  /etc/init.d/lirc

Top

ethnarch3

Post subject:

Posted: Tue Mar 27, 2007 4:40 am

Joined: Fri Dec 15, 2006 5:54 am

Posts: 15

From this "/var/log# ls -al /etc/rc?.d | grep lirc" i get this:

Quote:

root@mythtv:/myth/tv# /var/log# ls -al /etc/rc?.d | grep lirc
-bash: /var/log#: No such file or directory

And from this "/var/log# ls -l /etc/init.d/lirc" I get this:

Quote:

root@mythtv:/myth/tv# /var/log# ls -l /etc/init.d/lirc
-bash: /var/log#: No such file or directory

And from this "/var/log# md5sum /etc/init.d/lirc"

Quote:

root@mythtv:/myth/tv# /var/log# md5sum /etc/init.d/lirc
-bash: /var/log#: No such file or directory

Top

tjc

Post subject:

Posted: Tue Mar 27, 2007 6:29 pm

Joined: Thu Mar 25, 2004 11:00 am

Posts: 9551

Location: Arlington, MA

Well that's pretty much a smoking gun. The lirc stuff doesn't start automatically because all the relevant pieces are missing. How the heck did that happen?

I'd suggest getting a new ISO image and redoing the auto upgrade to the same version. Make sure that you have a good backup and don't have anything odd in your /myth/backup/restore.list file by moving orr removing it. Also be sure to check the image at every stage; the md5sum of the KnoppMythR5E50.iso file, using testcd when you boot from the CD, ...

Top

Page 2 of 3

[ 31 posts ]

Go to page Previous 1, 2, 3 Next

Board index KnoppMyth General

All times are UTC - 6 hours

Who is online

Users browsing this forum: No registered users and 6 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum