From: Hans H. A. <han...@gm...> - 2006-02-02 19:40:02
|
Hi I have been browsing the Internet for a solution to this problem. I have observed A LOT of people having the same problem asking this question but I have never seen it answered. I have been following this guide: http://www.mythtv.org/wiki/index.php/Ubuntu_Installation#5.0_LIRC And it runs smoothly until i am supposed to write irw. Instead a showing a blank line it just exits. If I check the lircd daemon i= t has been interrupted: root@eruantalon:/home/hans # lircd -n lircd: lircd(hauppauge) ready lircd: accepted new client on /dev/lircd lircd: could not get file information for /dev/lirc lircd: default_init(): No such file or directory lircd: caught signal Termineret root@eruantalon:/home/hans # I have tried googling for "no such device" lircd and other things but I onl= y run into other people who are having the same problem as I am. This guy claims that he solved his problem by making a symbolic link like this: http://www.linuxquestions.org/questions/showthread.php?t=3D345414&highlight= =3Dlircd+no+such+device ln -s /dev/lirc /dev/lircd When I first installed lirc there was something called /dev/lirc but after restarting it went away. Now all I have is /dev/lircd which I guess is not the same. My setup is the following: Kubuntu Breezy Badger Linux version 2.6.12-10-686 lirc 8.0 I have just bought a winTV-PVR-150 MCE kit with remote The remote sends to little box that is connected to my computer via a USB-cable. I'd be happy to supply any information you would require to help me and the many other who suffer from this problem. I have been looking through the past list and it seems that people have bee= n having this problem for years. About time we cleaned it up. Don't you think= ? Regards Hans Harhoff Andersen ps. This is my personal server. This is were I will post any and all of the information which you deem relevant so as to have one place to go to to hel= p me :-) http://coops2.homelinux.net/wiki/index.php/Lirc |
From: Nick <kno...@gm...> - 2006-02-02 20:09:40
|
On 02/02/06, Hans Harhoff Andersen <han...@gm...> wrote: > Hi > > I have been browsing the Internet for a solution to this problem. I have > observed A LOT of people having the same problem asking this question but= I > have never seen it answered. > > I have been following this guide: > http://www.mythtv.org/wiki/index.php/Ubuntu_Installation#5.0_LIRC > And it runs smoothly until i am supposed to write irw. > Instead a showing a blank line it just exits. If I check the lircd daemon= it > has been interrupted: > > root@eruantalon:/home/hans # lircd -n > lircd: lircd(hauppauge) ready > lircd: accepted new client on /dev/lircd > lircd: could not get file information for /dev/lirc > lircd: default_init(): No such file or directory > lircd: caught signal Do you have a /dev/lirc0 device created instead? If you do then create a symlink from this to /dev/lirc (or start lircd with the option '--device=3D/dev/lirc0'). If not, your LIRC drivers may not be loaded fully - what is the output of 'lsmod| grep lirc'? Nick |
From: Nick <kno...@gm...> - 2006-02-04 17:14:01
|
On 04/02/06, Hans Harhoff Andersen <han...@gm...> wrote: > This is my lirc logfile: > Feb 2 20:07:08 eruantalon lircd: lircd(hauppauge) ready > Feb 2 20:07:30 eruantalon lircd: accepted new client on /dev/lircd > Feb 2 20:07:30 eruantalon lircd: could not get file information for > /dev/lirc > > Feb 2 20:07:30 eruantalon lircd: default_init(): No such file or director= y > Feb 2 20:07:30 eruantalon lircd: caught signal > > This repeated as many times as I've tried to use irw and lircd. > I am using udev for device creation, but the /dev/lirc device first showe= d > when i ran make install from the lirc source directory. > What does this mean? Is the current version of /dev/lirc a pointer to > nothing. It seems to disappear every time I reboot. Does this mean that u= dev > is not findeing the right device or what? How do I go about finding out > wether the kernel recognizes my hauppauge remote control? Hans, The lirc_i2c module is for running the IR receiver plugged directly into the PVR card, not via USB as far as I know. Maybe you need a different module to support the USB-based receiver? Perhaps this is why LIRC is not creating the /dev/lirc device - because it cannot find a device attached to the PVR card? The only additional things I can think of are: i) ensure you have a valid /etc/lircd.conf file ( the remote definition) ii) enable udev logging to determine whether the kernel is seeing the LIRC devices when the modules are being loaded iii) check your udev rules and create a udev symlink between /dev/lirc0 and /dev/lirc iv) ensure that the USB receiver is supported under LIRC and the correct module is being loaded? Other than that, I would post again back to the list and see if any other Kubuntu users have had the same problems with 0.8. I've CC'd this reply to the list just in case. Nick |
From: Hans H. A. <han...@gm...> - 2006-02-05 14:13:01
|
Oops I wasn't aware that I was only replying to you. I just hit reply in gmail.... Well how do you start udev logging and what should I look for. Until now I just assumed that if it said my pvr card was supported for remotecontrol then that wold mean to usb-reciever that came with the card. Is there another product that I haven't heard about that allows yoo to plug an IR-reciever directly to a winTV-PVR-150 card? I look into the other points you mentioned when I get a chance. Hans 2006/2/4, Nick <kno...@gm...>: > > On 04/02/06, Hans Harhoff Andersen <han...@gm...> wrote: > > This is my lirc logfile: > > Feb 2 20:07:08 eruantalon lircd: lircd(hauppauge) ready > > Feb 2 20:07:30 eruantalon lircd: accepted new client on /dev/lircd > > Feb 2 20:07:30 eruantalon lircd: could not get file information for > > /dev/lirc > > > > Feb 2 20:07:30 eruantalon lircd: default_init(): No such file or > directory > > Feb 2 20:07:30 eruantalon lircd: caught signal > > > > This repeated as many times as I've tried to use irw and lircd. > > I am using udev for device creation, but the /dev/lirc device first > showed > > when i ran make install from the lirc source directory. > > What does this mean? Is the current version of /dev/lirc a pointer to > > nothing. It seems to disappear every time I reboot. Does this mean that > udev > > is not findeing the right device or what? How do I go about finding out > > wether the kernel recognizes my hauppauge remote control? > > Hans, > > The lirc_i2c module is for running the IR receiver plugged directly > into the PVR card, not via USB as far as I know. Maybe you need a > different module to support the USB-based receiver? Perhaps this is > why LIRC is not creating the /dev/lirc device - because it cannot find > a device attached to the PVR card? > > The only additional things I can think of are: > > i) ensure you have a valid /etc/lircd.conf file ( the remote definition) > ii) enable udev logging to determine whether the kernel is seeing the > LIRC devices when the modules are being loaded > iii) check your udev rules and create a udev symlink between > /dev/lirc0 and /dev/lirc > iv) ensure that the USB receiver is supported under LIRC and the > correct module is being loaded? > > Other than that, I would post again back to the list and see if any > other Kubuntu users have had the same problems with 0.8. I've CC'd > this reply to the list just in case. > > Nick > |
From: Pshem K. <ps...@gm...> - 2006-02-05 00:28:15
|
T24gMDMvMDIvMDYsIEhhbnMgSGFyaG9mZiBBbmRlcnNlbiA8aGFuc2hhcmhvZmZAZ21haWwuY29t PiB3cm90ZToKPiBIaQo+Cj4gSSBoYXZlIGJlZW4gYnJvd3NpbmcgdGhlIEludGVybmV0IGZvciBh IHNvbHV0aW9uIHRvIHRoaXMgcHJvYmxlbS4gSSBoYXZlCj4gb2JzZXJ2ZWQgQSBMT1Qgb2YgcGVv cGxlIGhhdmluZyB0aGUgc2FtZSBwcm9ibGVtIGFza2luZyB0aGlzIHF1ZXN0aW9uIGJ1dCBJCj4g aGF2ZSBuZXZlciBzZWVuIGl0IGFuc3dlcmVkLgoKe2N1dH0KCj4gSSBoYXZlIGp1c3QgYm91Z2h0 IGEgd2luVFYtUFZSLTE1MCBNQ0Uga2l0IHdpdGggcmVtb3RlCj4gVGhlIHJlbW90ZSBzZW5kcyB0 byBsaXR0bGUgYm94IHRoYXQgaXMgY29ubmVjdGVkIHRvIG15IGNvbXB1dGVyIHZpYSBhCj4gVVNC LWNhYmxlLgoKWW91IG5lZWQgdGhlIGxpcmNfbWNldXNiMiBtb2R1bGUgYW5kIHRoZSBjb25maWd1 cmF0aW9uIGZpbGUgdGhhdCBjb21lcwp3aXRoIGl0LiBJIGhhdmUgZXhhY3RseSB0aGUgc2FtZSBj YXJkIGFuZCB3YXMgYWxzbyBzdHJ1Z2dsaW5nIHRvIG1ha2UKaXQgd29yay4gVGhlIGZ1bm5pZXN0 IHRoaW5nIGlzIHRoYXQgdGhlIHJlbW90ZSBhY3R1YWxseSB3b3JrcwpwZXJmZWN0bHkgd2l0aCBs aXJjIC44IHdpdGhvdXQgYW55IHByb2JsZW1zIDotKQoKSG9wZSB0aGlzIGhlbHBzCnBzaGVta28K |