LinHES

Got it working after discovering the following:

/usr/LH/bin/load-modules-mythvantage.sh sets the ttyS0 parameters and loads the lirc_serial module, this is called on /etc/rc.sysinit in the line 87, here is a subset of the code:

But at this point in rc.sysinit ttyS0 does not exists, so it must be loaded after all the drivers are loaded, modified the rc.sysinit script, removed the line 87 and moved the /usr/LH/bin/load-modules-mythvantage.sh after the depmod, this is in the about the line 345 or so.

Also the /usr/LH/bin/load-modules-mythvantage.sh does wrong checks for the serial config.. in there in the lines 32 or so:

original file:

it checks the /etc/systemconfig file values, here is an snip of that file on my linhes installation:

It must check for $HostBlasterType not $ReceiverType (according to my /etc/systemconfig file) so those lines must be:

After this changes it will create a /dev/lircd1 device (in my case) wich you can use on the /usr/bin/change_chan.sh

Here is my change /usr/bin/change_chan.sh (change the REMOTE_NAME to whatever remote codes you have)

The initial design didn't include for supporting a serial blaster that was not also used as a receiver. The next release should fix this.

Modifing rc.sysinit should not be required, /usr/LH/bin/load-modules-mythvantage.sh is run twice to account for the missing ttySX.

modified load-modules-mythvantage.sh to not load lirc_serial if the setserial command failed.

On the latest update 6.0.0.7 updated May 4
This is still a challenge, in order to get it working I have to go into the services menu change serial ports, let it reconfigure, go back in and reset to the correct port. I must do this every reboot.
Ati all in wonder remote (usb) and serial irblaster.

EDIT:When the blaster works the ati all in wonder does not, I will hang on before doing the manual fixes so I can test any patches

Craig

I just did an update today and my irblaster is again not working despite using the fixes that used to work. If I look in dev I see lirc lirc0 and lircd
altering my change_chan.sh script to use each device lirc and lirc0 get connection refused
lircd fails silently.

Why can't we set it up the way 5.5 was setup it worked great.

Any suggestions as to how I might get this functioning again or any more info that may be needed to help trouble shoot this.

I am just using the irblaster no remote (I gave up on the ati remote and irblaster at the same time)

Thanks

Craig

just more info from var/log/lirc
Jul 19 21:51:08 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:51:08 hdbe lircd: could not get file information for /dev/lirc0 Jul 19 21:51:08 hdbe lircd: default_init(): No such file or directory Jul 19 21:51:08 hdbe lircd: WARNING: Failed to initialize hardware Jul 19 21:55:51 hdbe lircd: lircd(default) ready Jul 19 21:56:11 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:56:11 hdbe lircd: removed client Jul 19 21:56:11 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:56:11 hdbe lircd: removed client Jul 19 21:56:19 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:56:19 hdbe lircd: removed client Jul 19 21:56:20 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:56:20 hdbe lircd: removed client Jul 19 21:59:31 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:59:31 hdbe lircd: removed client Jul 19 21:59:31 hdbe lircd: accepted new client on /dev/lircd Jul 19 21:59:31 hdbe lircd: removed client Jul 19 22:00:06 hdbe lircd: accepted new client on /dev/lircd Jul 19 22:00:06 hdbe lircd: removed client Jul 19 22:00:06 hdbe lircd: accepted new client on /dev/lircd Jul 19 22:00:06 hdbe lircd: removed client Jul 19 22:12:50 hdbe lircd: accepted new client on /dev/lircd Jul 19 22:12:50 hdbe lircd: removed client Jul 19 22:13:09 hdbe lircd: accepted new client on /dev/lircd Jul 19 22:13:09 hdbe lircd: removed client Jul 19 22:13:23 hdbe lircd: accepted new client on /dev/lircd Jul 19 22:13:23 hdbe lircd: removed client

Although it accepts the client it does not change the channel

I thought I had my 5.5 to 6 upgrade all finished and this issue got me as well. I have restored my 5.5 so I will have a working install and I will do a test install on extra disk to troubleshoot. This is a showstopper for me as I rely on my serial blaster to change the channel on my satellite receiver. Anybody else have their serial blaster working? What is a good alternative to a serial blaster?

I tried upgrading again. This time I purchased a MCE remote only to find that it is a phillips ehome type that supports remote control but no blasting. So.... Back to the PVR-150 and Serial IR Blaster. Again, the remote works fine, but no go on the blaster.

I have tried to carefully check my remote names to make sure that there are no typos. I have come to the conclusion that the problem is the serial port, but I can't for the life of me figure out what is wrong. I looked at the LIRC page on ArchWiki and this seemed to confirm that this may be the issue. On the other hand, maybe I am just confused. Can we dare hope to have serial blaster support in R6? I will go back to R5.5 again.

dmesg | grep serial

serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
tveeprom 0-0050: Hauppauge model 26032, rev C199, serial# 8005046
lirc_serial: port 03f8 already in use
lirc_serial: use 'setserial /dev/ttySX uart none'
lirc_serial: or compile the serial port driver as module and
lirc_serial: make sure this module is loaded first

I have a streamzap remote and a serial blaster. I've been digging around trying to get the blaster to work. I've found the following:

1) there is a typo in /etc/sv/lircd/run
the line

this typo keeps the lirc_serial module from loading

2) I've also had to edit /etc/sv/lircd/run by changing the line

and then commenting out the lines with "do" and "done"

Now it works for my setup.

That is really good news! Let me try again with those edits. I can follow the $serial_port change easily. As far as the other part:

Change this:

To:

Is that correct?

Thanks!

Well I got it to change channel once and that is it. At least lirc_serial starts now. Still no blasting for me.

Thank goodness for Clonezilla! I have had to restore 5.5 three times now.

Almost.

Change
for i="1"
to just

I don't know what the

or

do.

Well, I know what the code does, I just don't know why it's there. I removed them from my script and things still work.

I've made a minimalist /etc/sv/lircd/run script by stripping out everything that's not needed.

This assumes:
- The receiver is not serial and the driver has already been loaded - it will use /dev/lirc0 and /dev/lircd

- The transmitter is serial and the correct serial port has been entered into /etc/systemconfig - it will use /dev/lirc1 and /dev/lircd1

/usr/bin/change_chan.sh must be modified so that the irsend lines look like this:

and

Any changes you make to the run script will be overwritten on the next update.
Instead of making mass changes to the lircd runit script, make your changes here:
/etc/runit/lirc.sh

OK! jams, you lost me now. Is there an update pending that will get irblasting working? This task has been open since April, so it would be great to see it completed.

I don't see lirc.sh in /etc/runit. Are you suggesting using the modifications above as lirc.sh? This will prevent it being overwritten again by code that does not work?

OK! jams, you lost me now. Is there an update pending that will get irblasting working? This task has been open since April, so it would be great to see it completed.

I don't see lirc.sh in /etc/runit. Are you suggesting using the modifications above as lirc.sh? This will prevent it being overwritten again by code that does not work?

"Is there an update pending that will get irblasting working?"
Probably, this was working for me some time ago, but looks like somebody broke it. When I get time I will look at it some more, although it appears that you guys have already found one of the problems.

"I don't see lirc.sh in /etc/runit. Are you suggesting using the modifications above as lirc.sh? This will prevent it being overwritten again by code that does not work?"
The file does not exist, however if it does exist the run file will source it instead of continuing. Look at the top of the run file, notice the check for the file and the if statement. The thing to watch out for is that lirc.sh must not return unless the process has died or stopped.

Any help would be appreciated. I would like to keep my serial blaster until I have to get a new motherboard!

Finally! Success!

I finally had time to day to attempt upgrade again. kebe thanks for the script changes! They worked!

jams Thanks for the tips regarding the lirc.sh! That is where I place the above script.

Changing channels is a wonderful thing.

This procedure worked for me. However, some of the changes were overwritten after performing an update. They were easily corrected. Silver Hauppauge remote and serial IR blaster both work at the same time now.

if you use /etc/runit/lirc.sh the changes will not be overwritten. Thats the entire point of that file.

This seems to work and I'll test it tonight. But what about us poor sods that uses a combined receiver/transmitter blaster?

kebe wrote:

This assumes:
- The receiver is not serial and the driver has already been loaded - it will use /dev/lirc0 and /dev/lircd

[EDIT] Ok, tested and both transmit and receive seems to work ok.