My system has a PVR-250, 7N1f2 motherboard, Sempron 2500 and a homemade IR blaster on COM 2 controlling a DISH 301.

It had R4v? and has been running fine for 2 years. It developed some hard drive issues and I put in a new drive and installed R5C7 on Wednesday. When it asked about the irblaster during install I picked "I will install my own" and I found channel_change.sh and irblasterd.conf for the 301 and put them in \etc\irblaster and did a chmod on channel_change.sh. That worked and the Myth box was able to control the 301.

I noticed R5D1 was just released so I thought I would do a fresh install to try it. When it asked about the irblaster I told it COM 2 and picked the 301.
It then gave a fatal error:

FATAL: Error inserting lirc_serial (/lib/modules/2.6.17-chw-8/misc/lirc_serial.ko): Device or resource busy
##################################################
## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ##
## is using. ##
##################################################


I rebooted and ran irblaster.sh:


Which comm port is the blaster attached to?
a) COM1
b) COM2

b
What device are you controlling with the blaster:
1) Cox_Cable_SA3250 6) LG_Goldeneye_TV 11) Nokia_MM9802S
2) Dish_Network_301 7) Motorola_CFT2200 12) Sky_Digibox_UK
3) Explorer_SA2000 Motorola_DCT2000 13) I'll install my own
4) Explorer_SA8000 9) Motorola_DCT2244
5) Hughes_DDS_GAEBO 10) Motorola_DCT2524
#? 2


Selected Dish_Network_301.
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.17-chw-8/misc/lirc_serial.ko): Device or resource busy
##################################################
## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ##
## is using. ##
##################################################

I tried restarting the irblaster:

/dev$ /etc/init.d/irblaster restart
FATAL: Error inserting lirc_serial (/lib/modules/2.6.17-chw-8/misc/lirc_serial.ko): Device or resource busy
Stopping irblaster daemon: irblasterdNo process in pidfile `/var/run/irblasterd.pid' found running; none killed.
.
##################################################
## UNABLE TO DETERMINE WHICH DEVICE lirc_serial ##
## is using. ##
##################################################


Any suggestions on what to look at appreciated.

Can you reboot and then run lsmod and see if the lirc_serial module is already being loaded by some other means. The irblaster scripts need to actually load the lirc_serial module so that they can determine which lirc minor device number lirc_serial attaches itself to. In my case it is always the first one because I have a USB remote, but for others that use the prv-x50 remotes, the first minor device number is allocated to that (when lirc is setup) and the second would be allocated to lirc serial.

The box was shutdown so this is after it booted.

lsmod doesn't show lirc_serial. The only thing it shows with lirc is this:

lirc_i2c 10244 2
lirc_dev 14468 1 lirc_i2c

So the question is why wont it insert the lirc_serial module.
Are the serial ports on configured in some unusual way on your box?
e. is com1 IRQ="4" IO="0x3f8" and com2 IRQ="3" IO="0x2f8"?

Before loading the module the script disables the uart on the serial port with the command:
setserial /dev/ttyS0 uart none
for COM1 or:
setserial /dev/ttyS1 uart none
for COM2

Also it passes the parameters IO and IRQ to the lirc_serial mocule by putting them in /etc/mythtv/modules/lirc_serial and ensuring that /etc/modprobe.d/KnoppMyth includes /etc/mythtv/modules/lirc_serial. Is that all setup like it should be? I must admit I havent tried using the blaster on COM2 for a while, so perhaps something about the parameter passing is broken. I have seen some posts with people having trouble passing parameters to the ivtv module.

Perhaps you should try com1. If the parameters are not being passed to the lirc_serial module properly, I think it defaults to com1. You could test that theory by using the following commands as root and checking if the lirc_serial module loads without error:
setserial /dev/ttyS0 uart none
modprobe lirc_serial

I had a similar problem after installing R5D1. Someting else loaded lirc_serial before the irblaster script runs. I couln't did find the real problem for a lack of linux know how. But if you set the driver in /etc/lirc/hardware.conf to null, then the irblaster script runs, and everything seems to work.

could you post your hardware.conf. I'm sorry, i don't know what you mean by null as I am still getting use to linux and programming in general.

thanks in advance

_________________
R5D1, PVR350, ASUS A7N8X-E Deluxe, AMD 2200+, SB Live.

I didn't think there were two serial ports on the board. Turns out there is another 10 pin header that is COM 1. I swapped the connector from COM 2 onto it, started the box and ran irblaster.sh telling it to use COM 1 and it didn't complain about anything and I ran channel_change.sh manually and it changed channels.

Funny that COM2 worked fine on the original R4 build and also the R5C7 I did last week.

Thanks for your input.

That points to an issue passing parameters to lirc_serial. I'll investigate.