From: John R. <jo...@en...> - 2002-01-22 21:58:08
|
Christoph, Firstly, I've past the last few lines of the log file here. Secondly, and more importantly, who are you and what is your connection to this project? Having searched the archives I've noticed a few messages from you along the lines of "RTFM", and I'd class this response in a similar manner - "tail /var/log/lircd" - without even a "hi" is, frankly, down right rude. Whether you are officially connected to this project or you are just somebody who "helps out", you are not giving a good impression of open-source software or this project. Having said that, if you (or anyone else for that matter) can help, of course I'd appreciate it - but if you feel like ignoring me - fine, I'll just go off and buy a commercial device and software, and add this to my list of reasons to scrap my many open-source solutions (and my clients). It seems, Christoph, you are the sort of person Bill Gates would love to employ. BTW, i'm more than happy to accept that my problems are to do with mistakes that i am making, I just don't like be treated like a wanker. Many regards John Jan 21 13:43:20 devsys lircd-0.6.4: could not get hardware features Jan 21 13:43:20 devsys lircd-0.6.4: this device driver does not support the new LIRC interface Jan 21 13:43:20 devsys lircd-0.6.4: make sure you use a current version of the d river Jan 21 13:43:20 devsys lircd-0.6.4: caught signal Jan 21 13:45:49 devsys lircd-0.6.4: lircd(serial) ready Jan 21 13:46:02 devsys lircd-0.6.4: accepted new client on /dev/lircd Jan 21 13:46:02 devsys lircd-0.6.4: could not get hardware features Jan 21 13:46:02 devsys lircd-0.6.4: this device driver does not support the new LIRC interface Jan 21 13:46:02 devsys lircd-0.6.4: make sure you use a current version of the d river Jan 21 13:46:02 devsys lircd-0.6.4: caught signal > -----Original Message----- > From: lir...@li... > [mailto:lir...@li...]On Behalf Of Christoph > Bartelmus > Sent: 22 January 2002 19:25 > To: lir...@li... > Subject: Re: raw codes / pace 2500s digibox > > > Hi! > > John Risby "jo...@en..." wrote: > > [...] > > and when i ps -A i see that lircd has gone. > > > Any advice will be gratefully accepted. > > tail /var/log/lircd > > Christoph > |
From: Stephen D. <st...@da...> - 2002-01-23 12:51:31
Attachments:
skydigital
|
On Tue, 22 Jan 2002, John Risby wrote: > BTW, i'm more than happy to accept that my problems are to do with mistakes > that i am making, I just don't like be treated like a wanker. Well - in this email you came across like a self-important wanker. But I don't suppose that was the intended effect... Christoph, has been the core maintainer for lirc. Reading the docs in your lirc source tree would have provided this information. Seems rude that you take lirc without even taking the time to see who was generous enough to create it and give it to you for nothing? I have an lirc config file for Sky Digital boxes (which I presume is in the current distrib somewhere as I contributed it). I've attached that. The Sky Digital boxes appear to use RC-6 or something like it. But RC6 isn't documented properly (or, wasn't in June 2001) so the remote needs to be handled with raw codes, I did make some improvements to LIRC's lirc_serial module at the time in order to get the Sky box to accept the codes. That's been in lirc CVS since last June or so. I was contacted by Scott Baily in the winlirc project about these changes, however I'm not sure whether he integrated them or not - you'd have to ask them. Steve |
From: John R. <jo...@en...> - 2002-01-23 13:59:07
|
Hi all, I just want to publicly apologise for my message which I posted last night. I've also emailed Christoph personally, and two other people on the list who contacted me off-list, with some explanation, although I don't feel it is appropriate to post the details publicly. All I can say is I am sorry for sounding like a tosser, and to say that I do appreciate the work that is put into this, and other, open-source projects. Sincerely, John > -----Original Message----- > From: lir...@li... > [mailto:lir...@li...]On Behalf Of John Risby > Sent: 22 January 2002 21:56 > To: lir...@li... > Subject: FW: raw codes / pace 2500s digibox > > > Christoph, > > Firstly, I've past the last few lines of the log file here. > |
From: <col...@hi...> - 2002-01-25 06:49:25
|
Hi! Stephen Davies "st...@da..." wrote: [...] > I have an lirc config file for Sky Digital boxes (which I presume is in > the current distrib somewhere as I contributed it). I've attached > that. The Sky Digital boxes appear to use RC-6 or something like it. > But RC6 isn't documented properly (or, wasn't in June 2001) so the > remote needs to be handled with raw codes, RC6 is supported. Look at the Philips DVD-712 and the Loewe 150_TV config files. I'm not really sure if your config really is RC6. Looks different somehow although there seem to be many common parameters. Christoph |
From: Stephen D. <st...@da...> - 2002-01-25 08:55:31
|
On 25 Jan 2002, Christoph Bartelmus wrote: > RC6 is supported. Look at the Philips DVD-712 and the Loewe 150_TV config > files. I'm not really sure if your config really is RC6. Looks different > somehow although there seem to be many common parameters. Thanks for the explanation. The coding from the Sky controls is a biphase code and I think constant number of bits when I worked it out, so somehow seems it should be able to be configured without using raw mode. Still - the config file works fine and that's the main thing. Steve |
From: <col...@hi...> - 2002-01-26 19:14:30
|
Hi! Stephen Davies "st...@da..." wrote: > On 25 Jan 2002, Christoph Bartelmus wrote: >> RC6 is supported. Look at the Philips DVD-712 and the Loewe 150_TV >> config files. I'm not really sure if your config really is RC6. Looks >> different somehow although there seem to be many common parameters. > Thanks for the explanation. The coding from the Sky controls is a > biphase code and I think constant number of bits when I worked it out, > so somehow seems it should be able to be configured without using raw > mode. > Still - the config file works fine and that's the main thing. Raw codes don't support toggle bits like present in RC5 and RC6. You can do a simple test to find out if it is a RC6 remote. Get the DVC-712 config and feed it to irrecord. If irrecord now recognises your remote it is RC6. Christoph |
From: <col...@hi...> - 2002-01-25 06:49:30
|
Hi! First of all I'd like to say that I'm really gald that things cleared up really quickly in this thread. John, I certainly accept you apology. Actually I'm doing this job way to long to become insulted, but I must admit that I was a bit astonished by your reaction. ;) John Risby "jo...@en..." wrote: [...] > Firstly, I've past the last few lines of the log file here. > Secondly, and more importantly, who are you and what is your connection > to this project? Having searched the archives I've noticed a few > messages from you along the lines of "RTFM", and I'd class this > response in a similar manner - "tail /var/log/lircd" - without even a > "hi" is, frankly, down right rude. Just some words of explanation why my answers tend to be, err, quite brief. I'm doing the work for this project in my free time. Lately, related to my current job, my free time has become really scarce. Nevertheless I try answering all mails related to this project. But this is only possible if I come directly to the point. While throwing a "tail /var/log/lircd" in your direction might not be very polite, I think it was enough to push you in the right direction. [...] > Jan 21 13:43:20 devsys lircd-0.6.4: could not get hardware features > Jan 21 13:43:20 devsys lircd-0.6.4: this device driver does not support > the new LIRC interface > Jan 21 13:43:20 devsys lircd-0.6.4: make sure you use a current version > of the d river > Jan 21 13:43:20 devsys lircd-0.6.4: caught signal Looks like /dev/lirc is still a link to the ttySx that you use to connect the Silitek receiver. To use the transmitter, you need the lirc_serial module. This is interfaced by a character device. Solution: rm /dev/lirc && mknod /dev/lirc c 61 0 Christoph |
From: John R. <jo...@en...> - 2002-01-25 13:53:00
|
Thank you Christoph for accepting my apology and being prepared to continue to help. Looks like /dev/lirc is still a link to the ttySx that you use to > connect > the Silitek receiver. To use the transmitter, you need the lirc_serial > module. This is interfaced by a character device. > Solution: > > rm /dev/lirc && mknod /dev/lirc c 61 0 > Ok, I've tried that (I *think* i had tried it previously too and then gone back as it to ttyS0 as it hadn't worked). Now I am getting this error. Jan 25 13:46:24 devsys lircd-0.6.5pre2: lircd(serial) ready Jan 25 13:46:25 devsys lircd-0.6.5pre2: accepted new client on /dev/lircd Jan 25 13:46:25 devsys lircd-0.6.5pre2: could not open /dev/lirc Jan 25 13:46:25 devsys lircd-0.6.5pre2: default_init(): No such device Jan 25 13:46:25 devsys lircd-0.6.5pre2: caught signal The transmitter is home-brew and based on the one at http://www.lirc.org/transmitters.html (the first, simple one). I used a 2.2k resistor (it says bigger than 1k?) and connected the wire from dtr to the diode, resistor, emitter and then to ground. That hasn't worked and since I've connected pins 1 and 4 (on advice from somebody on a different list). It still doesn't work. Is there anything obviously stupid I am doing? The device is connected to serial port 1 (standard settings). Thank you again John |
From: John R. <jo...@en...> - 2002-01-27 17:09:48
|
The full error msg being given for modprobe is as follows... /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol free_irq_Rsmp_f20dabd8 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __request_region_Rsmp_1a1a4f09 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __global_restore_flags_Rsmp_54dd1dcb /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol remove_wait_queue_Rsmp_5e06e0c0 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol unregister_chrdev_Rsmp_c192d491 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol register_chrdev_Rsmp_9e673338 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __global_cli_Rsmp_64576b05 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol add_wait_queue_Rsmp_4565a3ee /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __wake_up_Rsmp_127fda83 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __check_region_Rsmp_f1d0cdab /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol printk_Rsmp_1b7d4074 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol ioport_resource_Rsmp_865ebccd /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __global_save_flags_Rsmp_5d902e96 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __pollwait_Rsmp_816e5e5a /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol schedule_Rsmp_4292364c /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __const_udelay_Rsmp_eae3dfd6 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __udelay_Rsmp_9e7d6bd0 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol cpu_data_Rsmp_d3b73c3c /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __generic_copy_from_user_Rsmp_116166aa /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol request_irq_Rsmp_0c60f2e0 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol sleep_on_timeout_Rsmp_241949d2 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __release_region_Rsmp_d49501d4 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol do_gettimeofday_Rsmp_72270e35 /lib/modules/2.4.2-2/misc/lirc_serial.o: insmod /lib/modules/2.4.2-2/misc/lirc_serial.o failed /lib/modules/2.4.2-2/misc/lirc_serial.o: insmod lirc_serial failed Thanks John |
From: John R. <jo...@en...> - 2002-01-27 18:26:21
|
sorry to respond to myself (and do my working out in public...) but having re-compiled my kernel, the last error message has now gone away. Now though, when i run lircd (with a test confiruation file of .../sharp/G0009AJ - trying it with an old sharp video up here), i now get the following error rc: command failed: SEND_ONCE G0009AJ Stop rc: hardware does not support sending and a tail of the log file shows Jan 27 18:25:06 devsys lircd-0.6.5pre2: accepted new client on /dev/lircd Jan 27 18:25:06 devsys lircd-0.6.5pre2: error processing command: SEND_ONCE G0009AJ Stop Jan 27 18:25:06 devsys lircd-0.6.5pre2: hardware does not support sending Jan 27 18:25:06 devsys lircd-0.6.5pre2: removed client Does this signify a problem with my hardware perhaps? Thanks John -----Original Message----- From: lir...@li... [mailto:lir...@li...] On Behalf Of John Risby Sent: 27 January 2002 17:10 To: lir...@li... Subject: RE: FW: raw codes / pace 2500s digibox The full error msg being given for modprobe is as follows... /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol free_irq_Rsmp_f20dabd8 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __request_region_Rsmp_1a1a4f09 <snip> |
From: <col...@hi...> - 2002-01-28 21:19:15
|
Hi! John Risby "jo...@en..." wrote: [...] > Now though, when i run lircd (with a test confiruation file of > .../sharp/G0009AJ - trying it with an old sharp video up here), i now > get the following error > rc: command failed: SEND_ONCE G0009AJ Stop > rc: hardware does not support sending Have you enabled the transmitter in the setup.sh dialog? Christoph |
From: John R. <jo...@en...> - 2002-02-08 13:00:25
|
finally got it working. thanks to everyone for their help. not sure *exactly* what was wrong, i didn't approach the debugging process very well and was working on a few things at once (ie, i was presuming the h/w must be broken and working on that whilst recompiling the kernel etc). still it works now. btw, not actually tested it on my pace 2500s, i'm using it on an amstrad drx200 which is connected to my dedicated showshifter machine. (http://www.showshifter.com). all these digiboxes use the same remote however. thanks again, john |
From: <col...@hi...> - 2002-01-26 19:14:27
|
Hi! John Risby "jo...@en..." wrote: [...] >> the Silitek receiver. To use the transmitter, you need the lirc_serial >> module. This is interfaced by a character device. [...] > Now I am getting this error. > Jan 25 13:46:24 devsys lircd-0.6.5pre2: lircd(serial) ready > Jan 25 13:46:25 devsys lircd-0.6.5pre2: accepted new client on > /dev/lircd > Jan 25 13:46:25 devsys lircd-0.6.5pre2: could not open > /dev/lirc > Jan 25 13:46:25 devsys lircd-0.6.5pre2: default_init(): No > such device Probably the kernel module is not loaded. modprobe lirc_serial Christoph |
From: John R. <jo...@en...> - 2002-01-26 23:54:33
|
Hi Christoph, modprobe is giving me lots of errors. I connect to the linux box via telnet (local network) and this is the screen dump of the errors (some will have passed off the screen tho, yell if you need more than this). Thanks John /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __pollwait_Rsmp_816e5 e5a /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol schedule_Rsmp_4292364 c /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __const_udelay_Rsmp_e ae3dfd6 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __udelay_Rsmp_9e7d6bd 0 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol cpu_data_Rsmp_d3b73c3 c /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __generic_copy_from_u ser_Rsmp_116166aa /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol request_irq_Rsmp_0c60 f2e0 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol sleep_on_timeout_Rsmp _241949d2 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol __release_region_Rsmp _d49501d4 /lib/modules/2.4.2-2/misc/lirc_serial.o: unresolved symbol do_gettimeofday_Rsmp_ 72270e35 /lib/modules/2.4.2-2/misc/lirc_serial.o: insmod /lib/modules/2.4.2-2/misc/lirc_s erial.o failed /lib/modules/2.4.2-2/misc/lirc_serial.o: insmod lirc_serial failed > -----Original Message----- > From: lir...@li... > [mailto:lir...@li...]On Behalf Of Christoph > Bartelmus > Sent: 26 January 2002 18:54 > To: lir...@li... > Subject: Re: FW: raw codes / pace 2500s digibox > > > Hi! > > John Risby "jo...@en..." wrote: > [...] > >> the Silitek receiver. To use the transmitter, you need the lirc_serial > >> module. This is interfaced by a character device. > [...] > > Now I am getting this error. > > > Jan 25 13:46:24 devsys lircd-0.6.5pre2: lircd(serial) ready > > Jan 25 13:46:25 devsys lircd-0.6.5pre2: accepted new client on > > /dev/lircd > > Jan 25 13:46:25 devsys lircd-0.6.5pre2: could not open > > /dev/lirc > > Jan 25 13:46:25 devsys lircd-0.6.5pre2: default_init(): No > > such device > > Probably the kernel module is not loaded. > > modprobe lirc_serial > > Christoph > |
From: <col...@hi...> - 2002-01-28 06:34:33
|
Hi! John Risby "jo...@en..." wrote: [...] > modprobe is giving me lots of errors. The kernel config and the config this module were compiled with do not match. Please follow the instructions given in the documentation how to compile the kernel modules. The only way that is guaranteed to work is to compile your own kernel and use this kernel to compile the LIRC kernel modules. Christoph |