I finally have been able to get the irblaster to startup properly on Com1 but it doesnt transmit anything but its able to record signals from my remote. Do I need to compile the module with transmitting support. All I did was download lirc-0.8 run setup and chose irda then actisys 200L then ran make and make install. Then put startup scripts and everything else.




Also after a minute or so it stops working.. Is this linux just unloading the module? or is it something else. The only way I can get it to work again is to reboot the machine and then irw and irrecord and irsend begin to work again? Where should I start looking should I be loading the driver lirc_sir differently or with some parameters?

Anyone experience either of these?

Okay...Ive realized that the lirc_sir is being loaded as a module. The feeling I have is linux loads the module on startup then the system feels that the module isnt being used so it unloads the module which is how modules work. Now what Ive done is gone into the kernel and tried to make the Actisys module builtin rather then as a module so linux will never unload it as it will always be running. Only problem is when I try to build it in it says the module this one depends on is loaded as a module so it will keep this as a module also. Ive seared all over google but cant figure out which module lirc_sir depends on.

From running lsmod I know its lirc_dev but I dont know which heading in menuconfig this falls under.

I think once I can have this built-in to the kernel it will stay on long enough for me to recreate a tailor made lirc conf file so the ir200L can transmit codes on the proper frequencies to my digital box. Ive been researching the lirc_sir module and it doesnt need to be configured for transmitting the way the lirc_serial module does becuase its built for two way transmission. Any ideas on my previous question?

You didn't actually ask a question.
Linux does not automatically unload modules that aren't in use.
Also, you cannot unload a module that is in use (which lirc_sir would be when it is working - lircd would be using it via /dev/lirc)
Are you sure that the module gets unloaded?
Perhaps lircd is just crashing.

dmesg
Apr 3 10:58:05 mythfrontendbox kernel: lirc_dev: IR Remote Control driver registered, at major 61
Apr 3 10:58:05 mythfrontendbox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Apr 3 10:58:05 mythfrontendbox kernel: lirc_sir: I/O port 0x03f8, IRQ 4.
Apr 3 10:58:05 mythfrontendbox kernel: lirc_sir: Installed.

/var/log/lircd
Mar 30 21:19:57 mythfrontendbox lircd: caught signal
Apr 3 10:58:02 mythfrontendbox lircd: lircd(act200l) ready
Apr 3 10:59:14 mythfrontendbox lircd: accepted new client on /dev/lircd

then after running a few programs or doing nothing this shows up in the lircd logs:

Apr 3 11:08:57 mythfrontendbox lircd: removed client

Here is the lircd process after that messages shows up: root@mythfrontendbox:/var/log# ps -ef | grep lircd
root 2172 1 0 10:58 ? 00:00:00 /usr/local/sbin/lircd

Even if I restart the daemon its doesnt matter it still wont work until I reboot.

Does this output help lsmod:
root@mythfrontendbox:~# lsmod
Module Size Used by
sg 30496 0
shpchp 44000 0
pci_hotplug 27972 1 shpchp
intel_agp 21148 1
agpgart 30672 1 intel_agp
8250_pnp 10496 0
pcspkr 3844 0
tsdev 8000 0
ivtv 209044 0
lirc_sir 17984 0
lirc_dev 15108 1 lirc_sir
ipv6 247648 42
ttusb_dec 22412 0
ttusbdecfe 5120 1 ttusb_dec
dvb_ttusb_budget 30492 0
cx22700 7172 1 dvb_ttusb_budget
budget_av 14592 0
tda10021 7812 1 budget_av
budget_ci 13440 0
budget 11648 0
s5h1420 10116 1 budget
budget_core 9092 3 budget_av,budget_ci,budget
dvb_ttpci 87100 0
l64781 8708 2 budget,dvb_ttpci
tda8083 7300 3 dvb_ttusb_budget,budget,dvb_ttpci
stv0297 8960 2 budget_ci,dvb_ttpci
sp8870 8716 1 dvb_ttpci
ttpci_eeprom 4480 2 budget_core,dvb_ttpci
saa7146_vv 45056 2 budget_av,dvb_ttpci
dvb_bt8xx 13956 0
nxt6000 8708 1 dvb_bt8xx
mt352 7940 1 dvb_bt8xx
dvb_pll 11140 1 dvb_bt8xx
sp887x 9092 1 dvb_bt8xx
dst_ca 17408 1 dvb_bt8xx
or51211 11268 1 dvb_bt8xx
lgdt330x 9372 1 dvb_bt8xx
saa7146 16776 6 budget_av,budget_ci,budget,budget_core,dvb_ttpci,saa7146_vv
dst 25732 2 dvb_bt8xx,dst_ca
bt878 10328 2 dvb_bt8xx,dst
mt312 9092 0
cx24110 9092 1 dvb_bt8xx
tda1004x 14980 3 dvb_ttusb_budget,budget_av,budget_ci
ves1820 7812 3 dvb_ttusb_budget,budget,dvb_ttpci
stv0299 11528 5 dvb_ttusb_budget,budget_av,budget_ci,budget,dvb_ttpci
bttv 159312 2 dvb_bt8xx,bt878
btcx_risc 6152 1 bttv
ves1x93 7940 2 budget,dvb_ttpci
dvb_core 76072 10 ttusb_dec,dvb_ttusb_budget,budget_av,budget_ci,budget,budget_core,dvb_ttpci,dvb_bt8xx,dst_ca,stv0299
video_buf 19204 2 saa7146_vv,bttv
v4l2_common 6912 2 saa7146_vv,bttv
v4l1_compat 15108 1 saa7146_vv
evdev 9472 0
skge 36368 0
autofs4 18180 1
af_packet 20872 0
tda9887 16912 0
msp3400 33072 0
saa7115 16272 0
tuner 43556 0
tveeprom 15632 1 bttv
i2c_algo_bit 10632 2 ivtv,bttv
videodev 9600 3 ivtv,saa7146_vv,bttv
3c59x 42536 0
mii 6656 1 3c59x
i2c_piix4 10000 0
i2c_core 19328 36 ivtv,dvb_ttusb_budget,cx22700,budget_av,tda10021,budget_ci,budget,s5h1420,budget_core,dvb_ttpci,l64781,tda8083,stv0297,sp8870,ttpci_eeprom,dvb_bt8xx,nxt6000,mt352,sp887x,or51211,lgdt330x,dst,mt312,cx24110,tda1004x,ves1820,stv0299,bttv,ves1x93,tda9887,msp3400,saa7115,tuner,tveeprom,i2c_algo_bit,i2c_piix4
parport_pc 37700 0
parport 32840 1 parport_pc
8250 22132 1 8250_pnp
serial_core 19328 1 8250
pcmcia 33836 0
firmware_class 10112 13 ivtv,ttusb_dec,dvb_ttusb_budget,budget_av,budget_ci,dvb_ttpci,sp8870,dvb_bt8xx,sp887x,or51211,tda1004x,bttv,pcmcia
yenta_socket 25612 0
rsrc_nonstatic 12928 1 yenta_socket
pcmcia_core 37528 3 pcmcia,yenta_socket,rsrc_nonstatic
video 16388 0
thermal 13192 0
processor 25128 1 thermal
fan 5508 0
container 5376 0
button 7056 0
battery 10500 0
ac 5636 0
rtc 12468 0
ohci1394 32436 0
ieee1394 300760 1 ohci1394
usb_storage 62656 0
ohci_hcd 20612 0
uhci_hcd 31632 0
usbcore 113156 6 ttusb_dec,dvb_ttusb_budget,usb_storage,ohci_hcd,uhci_hcd
a100u2w 11968 0
megaraid 38856 0
tmscsim 23616 0
BusLogic 76692 0

Any suggestions?