From: Mike K. <mk...@vx...> - 2007-01-08 00:28:54
|
Using: irattach /dev/ttyUSB0 none -s I am seeing JetEye IR dongle blink red. However irdadump still only shows localhost. Plus there's no longer a debug under /proc/net/irda. Naturally I now see an irda1 intf whereas before I had only irda0. I <somehow> screwed up irda and /dev/ir* doesn't show up anymore. I used to have 10s of entries for lpt, comm, etc. What can fix this? Is somehow irda kernel driver not creating dev nodes due to smsir failure with io port? I'm assuming perhaps that I want to just keep testing with dongle as there may be a kernel issue with builtin sir for latest kernels. mike Mike Klein wrote: > I want to get basic irda working before starting with lirc. Basic irda > is sir/fir and lirc is cir...correct? > > When I run irdadump...I only see "localhost" in output...not IR from my > T68i phone which is sending a file via IR. Additionally when I run > obex-server I cannot get any communication during IR file xfer with phone. > > I am using Ubuntu with 2.6.17-10-generic kernel on Toshiba Satellite > P25-S609 laptop. I believe from some googling that sms is broken in this > kernel?? > > I have installed irda-utils and every other ir-related pkg I could get > my hands on. > > I am using SIR built into laptop in addition to JetEye 9680. JetEye is > connected via USB-serial dongle (KeySpan). > > dmsg shows <some> clean startup of devices: > > [17179588.244000] drivers/usb/serial/usb-serial.c: USB Serial support > registered for Keyspan - (without firmware) > [17179588.244000] drivers/usb/serial/usb-serial.c: USB Serial support > registered for Keyspan 1 port adapter > [17179588.244000] drivers/usb/serial/usb-serial.c: USB Serial support > registered for Keyspan 2 port adapter > [17179588.244000] drivers/usb/serial/usb-serial.c: USB Serial support > registered for Keyspan 4 port adapter > [17179588.244000] keyspan 5-1:1.0: Keyspan 1 port adapter converter detected > [17179588.244000] usb 5-1: Keyspan 1 port adapter converter now attached > to ttyUSB0 > [17179588.244000] drivers/usb/serial/keyspan.c: v1.1.4:Keyspan USB to > Serial Converter Driver > > But it does show some sms errors: > > [17179590.108000] smsc_superio_flat(): fir: 0x6f8, sir: 0x2f8, dma: 03, > irq: 3, mode: 0x0e > [17179590.108000] smsc_ircc_present: can't get sir_base of 0x2f8 > [17179651.276000] smsc_superio_flat(): fir: 0x6f8, sir: 0x2f8, dma: 01, > irq: 3, mode: 0x0e > [17179651.276000] smsc_ircc_set_sir_speed(), Setting speed to: 9600 > [17179659.100000] smsc_ircc_change_speed() changing speed to: 9600 > [17179659.100000] smsc_ircc_set_sir_speed(), Setting speed to: 9600 > > > /var/log/messages also shows: > > Jan 7 15:00:55 screamer kernel: [17179648.164000] SMsC IrDA Controller > found > Jan 7 15:00:55 screamer kernel: [17179648.164000] IrCC version 2.0, > firport 0x6f8, sirport 0x2f8 dma=1, irq=3 > Jan 7 15:00:55 screamer kernel: [17179648.164000] No transceiver found. > Defaulting to Fast pin select > Jan 7 15:00:55 screamer kernel: [17179648.164000] IrDA: Registered > device irda0 > ... > Jan 7 15:01:00 screamer irattach: executing: '/sbin/modprobe irda0' > Jan 7 15:01:00 screamer irattach: executing: 'echo screamer > > /proc/sys/net/irda/devname' > Jan 7 15:01:00 screamer irattach: executing: 'echo 1 > > /proc/sys/net/irda/discovery' > Jan 7 15:01:00 screamer irattach: Starting device irda0 > > Not sure what "No transceiver found" means...other than only receiver > found and not transmitter. > > My laptop has modem plus ir (not builtin serial port). I have configured > ir for FIR and 2f8/irq3...which I believe s/be /dev/ttyS1. > > > root@screamer:/etc/default# lsmod | grep ir > smsc_ircc2 24732 0 > irda 214332 1 smsc_ircc2 > crc_ccitt 3200 1 irda > > > [root@mother log]# ls -l /dev/ir* > crw-rw---- 1 root uucp 161, 0 Jan 30 2003 /dev/ircomm0 > crw-rw---- 1 root uucp 161, 1 Jan 30 2003 /dev/ircomm1 > crw-rw---- 1 root uucp 161, 10 Jan 30 2003 /dev/ircomm10 > crw-rw---- 1 root uucp 161, 11 Jan 30 2003 /dev/ircomm11 > crw-rw---- 1 root uucp 161, 12 Jan 30 2003 /dev/ircomm12 > crw-rw---- 1 root uucp 161, 13 Jan 30 2003 /dev/ircomm13 > crw-rw---- 1 root uucp 161, 14 Jan 30 2003 /dev/ircomm14 > crw-rw---- 1 root uucp 161, 15 Jan 30 2003 /dev/ircomm15 > crw-rw---- 1 root uucp 161, 2 Jan 30 2003 /dev/ircomm2 > crw-rw---- 1 root uucp 161, 3 Jan 30 2003 /dev/ircomm3 > crw-rw---- 1 root uucp 161, 4 Jan 30 2003 /dev/ircomm4 > crw-rw---- 1 root uucp 161, 5 Jan 30 2003 /dev/ircomm5 > crw-rw---- 1 root uucp 161, 6 Jan 30 2003 /dev/ircomm6 > crw-rw---- 1 root uucp 161, 7 Jan 30 2003 /dev/ircomm7 > crw-rw---- 1 root uucp 161, 8 Jan 30 2003 /dev/ircomm8 > crw-rw---- 1 root uucp 161, 9 Jan 30 2003 /dev/ircomm9 > crw-rw---- 1 root lp 161, 16 Jan 30 2003 /dev/irlpt0 > crw-rw---- 1 root lp 161, 17 Jan 30 2003 /dev/irlpt1 > crw-rw---- 1 root lp 161, 26 Jan 30 2003 /dev/irlpt10 > crw-rw---- 1 root lp 161, 27 Jan 30 2003 /dev/irlpt11 > crw-rw---- 1 root lp 161, 28 Jan 30 2003 /dev/irlpt12 > crw-rw---- 1 root lp 161, 29 Jan 30 2003 /dev/irlpt13 > crw-rw---- 1 root lp 161, 30 Jan 30 2003 /dev/irlpt14 > crw-rw---- 1 root lp 161, 31 Jan 30 2003 /dev/irlpt15 > crw-rw---- 1 root lp 161, 18 Jan 30 2003 /dev/irlpt2 > crw-rw---- 1 root lp 161, 19 Jan 30 2003 /dev/irlpt3 > crw-rw---- 1 root lp 161, 20 Jan 30 2003 /dev/irlpt4 > crw-rw---- 1 root lp 161, 21 Jan 30 2003 /dev/irlpt5 > crw-rw---- 1 root lp 161, 22 Jan 30 2003 /dev/irlpt6 > crw-rw---- 1 root lp 161, 23 Jan 30 2003 /dev/irlpt7 > crw-rw---- 1 root lp 161, 24 Jan 30 2003 /dev/irlpt8 > crw-rw---- 1 root lp 161, 25 Jan 30 2003 /dev/irlpt9 > crw------- 1 root root 10, 187 Jan 30 2003 /dev/irnet > > The above devices automagickally were removed by something I did...what > would cause this? > > root@screamer:/etc/default# ifconfig > > ...cut for brevity... > > irda0 Link encap:IrLAP HWaddr 06:27:dd:95 > UP RUNNING NOARP MTU:2048 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7241 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:8 > RX bytes:0 (0.0 b) TX bytes:227363 (222.0 KiB) > Interrupt:3 Base address:0x6f8 > > > mklein@screamer:/etc/default$ lsusb > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 005 Device 002: ID 06cd:0121 Keyspan > Bus 005 Device 001: ID 0000:0000 > Bus 004 Device 005: ID 046d:c709 Logitech, Inc. > Bus 004 Device 004: ID 046d:c70a Logitech, Inc. > Bus 004 Device 002: ID 046d:0b02 Logitech, Inc. > Bus 004 Device 003: ID 046d:c70e Logitech, Inc. > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > mklein@screamer:/etc/default$ > > > root@screamer:/etc/modprobe.d# more irda-utils > # Other aliases are defined in the modules themselves > alias char-major-10-187 irnet > > # For FIR device > > # Module name has changed for this device, so this is a compatibility hack > # that the user can select the name used for 2.4 when really using 2.6 > install smc-ircc /sbin/modprobe smsc-ircc2 > install toshoboe /sbin/modprobe donauboe > > #options > #alias irda0 > > > root@screamer:/etc/modprobe.d# cat smsc-ircc2 > alias irda0 smsc-ircc2 > alias tty-ldisc-11 irtty-sir > alias char-major-161 ircomm-tty > alias char-major-10-187 irnet > > > root@screamer:/etc/default# more irda-utils > # Set your startup settings for irattach, the IrDA-daemon, here. > > # Set this to 'false' if you do not need to start irattach. Otherwise set it > # to 'true'. > ENABLE="false" > > # Set this to 'false' if you do not want automatic discovery of irda > devices. > # If 'true', it will automatically start irattach if devices are found. > AUTOMATIC="true" > > # Set discovery mode which usually is a good idea for finding other devices. > # If set 'true' or 'false' irattach and sysctl are used to enable and > disable > # discovery mode. By default discover mode is disabled. > DISCOVERY="true" > > # Set IRDA device to access (e.g. /dev/ttyS1 or irda0). > # In case of irda0, the proper module for FIR-mode has to be set in > # /etc/modutils/irda-utils (2.4) or /etc/modprobe.d/irda-utils (2.6) > DEVICE="/dev/ttyS1" > > # Set dongle type, e.g. none, tekram, esi, actisys, actisys+, ep7211, > girbil, > # litelink, airport, old_belkin, mcp2120, act200l, ma600). You do not need > # a dongle for FIR mode. > DONGLE="none" > > # Set the serial device to quiet with setserial. This is only useful on some > # machines in FIR-mode, so most people should leave it blank. See > # README.Debian for more information. > SETSERIAL="" > > In above I'm not sure whether to use /dev/ttyS1 or irda as device. > Neither seems to work. > > Anything obviously wrong? > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users > |