LinHES Forums :: View topic - Problems with serial header on MSI K8NGM2-NBP

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

root@black2:/dev# ls -al /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 Feb 5 23:44 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Feb 5 23:44 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 Feb 5 23:44 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 Feb 5 23:44 /dev/ttyS3

#serial port remote
setserial /dev/ttyS0 uart none
modprobe lirc_serial
/usr/local/sbin/lircd
/usr/local/sbin/lircmd

root@mythfront1:/dev# ls -al /dev/ttyS*
crw-rw-rw- 1 root dialout 4, 64 May 7 2004 /dev/ttyS0
crw-rw-rw- 1 root dialout 4, 65 May 7 2004 /dev/ttyS1
crw-rw-rw- 1 root dialout 4, 66 May 7 2004 /dev/ttyS2
crw-rw-rw- 1 root dialout 4, 67 May 7 2004 /dev/ttyS3
crw-rw-rw- 1 root dialout 4, 68 May 7 2004 /dev/ttyS4

root@mythfront1:~# la /dev/lirc*
crw-r--r-- 1 root root 61, 0 Jun 21 2006 /dev/lirc
crw-r--r-- 1 root root 61, 1 Oct 1 2005 /dev/lirc1
srw-rw-rw- 1 root root 0 Feb 17 18:16 /dev/lircd
prw-r--r-- 1 root root 0 Jul 29 2004 /dev/lircm

root@mythfront1:~# lsmod | grep lirc
lirc_serial 13952 1
lirc_dev 14708 1 lirc_serial

root@black2:/var/log# lsmod | grep lirc
lirc_i2c 12420 0
lirc_dev 16628 1 lirc_i2c
i2c_core 20864 20 wm8775,cx25840,ivtv,nvidia,lirc_i2c,cx88_vp3054_i2c,
cx88xx,saa7134_dvb,dvb_pll,saa7134,ir_kbd_i2c,tda1004x,dvb_bt8xx,bttv,saa7115,msp3400,
tuner,i2c_algo_bit,tveeprom,i2c_nforce2

root@black2:~# pgrep -fl lirc
3998 lirc_dev
5383 /usr/sbin/lircd --driver=default --device=/dev/lirc0

Author:	kmkittre [ Sat Feb 17, 2007 12:09 pm ]
Post subject:	Problems with serial header on MSI K8NGM2-NBP
I purchased an MSI K8NGM2-NBP motherboard. I replaced my frontend motherboard with this one and did not do a re-install of R5D1. Everything is working just fine, but I cannot get my serial port IR receiver to work. I even tried the one that's working just fine on my other frontend. So, I don't think it's the receiver. I recompiled LIRC with version 0.8.1 and that also didn't seem to make a difference. I'm thinking that there may be something wrong with the serial header as I don't even get anything when I do a mode2. Is there any way to test the serial port? Would re-installing Knoppmyth do anything? Thanks in advance for any suggestions.

Author:	tjc [ Sat Feb 17, 2007 1:54 pm ]
Post subject:
I think this is covered in the R5E50 upgrade hints thread. Have you checked to make sure that X isn't trying to open it for a serial mouse and that the mythtv user is a member of the dialout group? http://mysettopbox.tv/phpBB2/viewtopic.php?t=13108 See Known Change #8 in the head posting, and search for a posting by ohrock on the 3rd page.

Author:	kmkittre [ Sat Feb 17, 2007 3:16 pm ]
Post subject:
Thanks for the tips, tjc, but do these really apply to me as I'm using R5D1? [EDIT:] I realize now that maybe I was a little unclear as to what I did. I was running R5D1. I turned off the computer, replaced the motherboard, and then turned the computer back on. Everything is running great except I can't get my serial IR receiver to work. The only difference I can think of is that my old mobo had a standard serial port, and this new one has a serial header instead.

Author:	kmkittre [ Sat Feb 17, 2007 3:42 pm ]
Post subject:
I went ahead and tried those suggestions anyway... When I look at my /etc/group file my dialout line is this: Code: dialout::20: versus what you posted: Code:* dialout:x:20:mythtv I changed it to this: Code: dialout::20:mythtv Also, regarding ohrock's post, when I type Code:* lsof /dev/ttyS* Nothing is listed

Author:	kmkittre [ Sat Feb 17, 2007 4:01 pm ]
Post subject:
More info if it helps: I see this in /var/log/dmesg: Code: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

LinHES Forums http://forum.linhes.org/

Problems with serial header on MSI K8NGM2-NBP http://forum.linhes.org/viewtopic.php?f=2&t=14237	Page 1 of 2

Author:	tjc [ Sat Feb 17, 2007 4:37 pm ]
Post subject:
Check to make sure that there is an appropriate setserial invocation being made in the init scripts... Folks usually do this in bootmisc.sh See ethernut's posting here: http://mysettopbox.tv/phpBB2/viewtopic.php?t=13097 Also double check the ownership of the port in /dev using: Code: root@black2:/dev# ls -al /dev/ttyS* crw-rw---- 1 root dialout 4, 64 Feb 5 23:44 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Feb 5 23:44 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Feb 5 23:44 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Feb 5 23:44 /dev/ttyS3

Author:	kmkittre [ Sat Feb 17, 2007 7:07 pm ]
Post subject:
yeah, here's what I have in my bootmisc.sh: Code: #serial port remote setserial /dev/ttyS0 uart none modprobe lirc_serial /usr/local/sbin/lircd /usr/local/sbin/lircmd Code: root@mythfront1:/dev# ls -al /dev/ttyS* crw-rw-rw- 1 root dialout 4, 64 May 7 2004 /dev/ttyS0 crw-rw-rw- 1 root dialout 4, 65 May 7 2004 /dev/ttyS1 crw-rw-rw- 1 root dialout 4, 66 May 7 2004 /dev/ttyS2 crw-rw-rw- 1 root dialout 4, 67 May 7 2004 /dev/ttyS3 crw-rw-rw- 1 root dialout 4, 68 May 7 2004 /dev/ttyS4

Author:	kmkittre [ Sat Feb 17, 2007 7:27 pm ]
Post subject:
Also, when I do a list of my /dev/lirc devices: Code: root@mythfront1:~# la /dev/lirc* crw-r--r-- 1 root root 61, 0 Jun 21 2006 /dev/lirc crw-r--r-- 1 root root 61, 1 Oct 1 2005 /dev/lirc1 srw-rw-rw- 1 root root 0 Feb 17 18:16 /dev/lircd prw-r--r-- 1 root root 0 Jul 29 2004 /dev/lircm I thought maybe I should be using /dev/lirc1? So I tried setting my hardware.conf to it: Code: DEVICE="/dev/lirc1" This did not appear to make a difference...

Author:	kmkittre [ Sat Feb 17, 2007 7:31 pm ]
Post subject:
Would I potentially gain something by doing a fresh install of knoppmyth on this machine?

Author:	tjc [ Sat Feb 17, 2007 10:26 pm ]
Post subject:
Running lirc-reconfigure.sh would do most of what an install would do as far as this goes.

Author:	kmkittre [ Sat Feb 17, 2007 11:01 pm ]
Post subject:
lirc-reconfigure.sh is not doing anything, where should I be running this script? Edit: nevermind, it's lirc-reconfig.sh

Author:	kmkittre [ Sat Feb 17, 2007 11:04 pm ]
Post subject:
Does that do anything other than setup an lircd.conf and lircrc file? I mean, if even mode2 is not showing any remote activity, will running this script potentially change any of that?

Author:	tjc [ Sun Feb 18, 2007 10:16 am ]
Post subject:
Sorry about the bad name, I was typing from memory... The script also starts the daemon (and sets things up so it starts at boot time) which should load the correct modules. Try running lsmod to see what drivers have been loaded and looking in /dev to see what devices are there.

Author:	kmkittre [ Sun Feb 18, 2007 2:03 pm ]
Post subject:
Code: root@mythfront1:~# lsmod \| grep lirc lirc_serial 13952 1 lirc_dev 14708 1 lirc_serial I'm not sure what I should be looking for in /dev?

Page 1 of 2	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/

Author:	tjc [ Sun Feb 18, 2007 2:08 pm ]
Post subject:
Yow. Didn't need the whole thing. You're just looking for the lirc modules and anything that they depend on... Like this... Code: root@black2:/var/log# lsmod \| grep lirc lirc_i2c 12420 0 lirc_dev 16628 1 lirc_i2c i2c_core 20864 20 wm8775,cx25840,ivtv,nvidia,lirc_i2c,cx88_vp3054_i2c, cx88xx,saa7134_dvb,dvb_pll,saa7134,ir_kbd_i2c,tda1004x,dvb_bt8xx,bttv,saa7115,msp3400, tuner,i2c_algo_bit,tveeprom,i2c_nforce2 Is your lircd getting passed the right driver info? What does this show for you? Code: root@black2:~# pgrep -fl lirc 3998 lirc_dev 5383 /usr/sbin/lircd --driver=default --device=/dev/lirc0 A search through recent posts for lirc_serial might also be productive.