Menu
▾
▴
Re: [irda-users] Re: Girbil IrDA adapter
|
From: Donald P. <don...@ya...> - 2004-09-14 21:28:27
|
Sorry forgot to mention kernel versions...
Working kernel is:
Linux version 2.4.22-10mdk (np...@no...) (gcc version
3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)) #1 Thu Sep 18 12:30:58 CEST 2003
Tried kernels from Mandrake 10 (2.6.3) and 10.1rc which is
Linux version 2.6.8.1-8mdksmp (np...@n3...) (gcc version
3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #1 SMP Fri Sep 3 16:58:32 CEST
2004
Regards,
Donald
On Tue, 2004-09-14 at 22:23 +0100, Donald Page wrote:
> Hmm lots of questions...
>
> First the girbil dongle is connected direct to the serial port on the
> motherboard (ttyS0) and the LED blinks on outgoing traffic i.e. when it
> is trying to discover peer devices - except it isn't of course...
>
> I'm using stock Mandrake distributions for everything here so basically
> I edit /etc/sysconfig/irda to:
> IRDA=yes
> DEVICE=/dev/ttyS0
> DONGLE=girbil
> DISCOVERY=yes
> and then it is started from /etc/rc.d/init.d/irda which does
> daemon /usr/sbin/irattach ${DEVICE} ${ARGS}
> where $DEVICE is read from above and $ARGS=-s
> which I confirmed from doing a 'ps -eaf' and getting
> /usr/sbin/irattach /dev/ttyS0 -d girbil -s
> Running irdadump as requested and catting irlap gives
> irlap0 state: LAP_NDM
> device name: irda0, hardware name: ttyS0
> caddr: 0x2a, saddr: 0x91cb7ca4, daddr: 0x000000
> win size: 0, win: 0, line capacity: 0, bytes left: 0
> tx queue len: 0 win queue len: 0 rbusy: FALSE mbusy: FALSE
> retrans: 0 vs: 0 vr: 0 va: 0
> qos bps maxtt dsize winsize addbofs mintt ldisc comp
> tx 9600 0 64 1 12 0 0
> rx 9600 0 64 1 12 0 0
> I haven't compiled my own kernel and therefore can't do the debug sorry.
> The first lines of lsmod are:
> Module Size Used by
> girbil-sir 3556 1
> irtty-sir 6880 2
> sir-dev 15068 2 girbil-sir,irtty-sir
> irda 134844 3 girbil-sir,sir-dev
> crc-ccitt 2656 1 irda
>
> Regards,
>
> Donald
> -------------------
> On Tue, 2004-09-14 at 18:27 +0200, Martin Diehl wrote:
> > [just returning after another offline period - sorry if I missed some
> > posting(s)]
> >
> > On Mon, 13 Sep 2004, Jean Tourrilhes wrote:
> >
> > > On Sun, Sep 12, 2004 at 09:42:20PM +0100, Donald Page wrote:
> > > > Jean,
> > > >
> > > > Apologies for writing directly but I don't subscribe to the IrDA mailing
> > > > list. I have a Girbil IrDA adapter which was working fine with 2.4
> > > > kernels but appears to not work with 2.6 kernels. I have checked this
> >
> > Which is the latest working 2.4 kernel? Which 2.6 version doesn't work?
> > The girbil dongle needs the raw write mode which had some issues in
> > earlier 2.6 releases. 2.6.8 and later is expected to be ok.
> >
> > > > with both Mandrake 10.0 and 10.1 rc1 kernels - the drivers appear to
> > > > load find but the adapter itself shows no sign of life - normally I get
> > > > a red LED pulsing on top. It also continues to work fine with Win98. Are
> >
> > Do you know, if the blinking LED indicates outgoing or incoming traffic?
> > For example, if it's pulsing when Win98 is trying to discover peer devices
> > but there is none, we'd know tx is sufficient for LED activity and thus if
> > it stays dark with Linux the issue must be in the tx-path.
> >
> > > > you aware of any such issues? Is there something else I can do to try
> > > > and debug the problem? Irdadump shows nothing other than the internal
> > > > 'noise':
> > > >
> > > > 20:42:00.968814 xid:cmd 148c1057 > ffffffff S=6 s=0 (14)
> > > > 20:42:01.058785 xid:cmd 148c1057 > ffffffff S=6 s=1 (14)
> > > > 20:42:01.148766 xid:cmd 148c1057 > ffffffff S=6 s=2 (14)
> > > > 20:42:01.238746 xid:cmd 148c1057 > ffffffff S=6 s=3 (14)
> > > > 20:42:01.328727 xid:cmd 148c1057 > ffffffff S=6 s=4 (14)
> > > > 20:42:01.418709 xid:cmd 148c1057 > ffffffff S=6 s=5 (14)
> > > > 20:42:01.508689 xid:cmd 148c1057 > ffffffff S=6 s=* piper hint=0400 [
> > > > Computer ] (21)
> > > > 20:42:03.968158 xid:cmd 148c1057 > ffffffff S=6 s=0 (14)
> >
> > This proves the stack is working and trying to discover peer devices. At
> > this point it's not clear yet, whether the dongle is actually emitting
> > these frames and we are not receiving anything - or the dongle isn't
> > actually transmitting in the first place.
> >
> > > The irtty driver architecture has changed in 2.6.X, and the
> > > various dongle drivers have been blindly updated. Nobody bothered to
> > > test those, and I don't have those hardware, so there is likely to be
> > > bugs.
> >
> > I've just done a visual compare between old girbil and the new girbil-sir
> > drivers. Conclusion was there's no apparent operational difference - at
> > least AFAICS - so in theory it should work, if the old one from 2.4 did...
> >
> > > Please contact Martin Diehl for details. The source code of
> > > those dongle driver is trivial, so you should find the bug in no time.
> >
> > Before going into details I'd suggest validating the setup is correct.
> >
> > Donald, how is your irda-setup configured, particularly how are you
> > calling irattach? Is the dongle connected to an on-board RS232 port or are
> > you using an usb-to-rs232 converter? And please sent the output of lsmod
> > and /proc/net/irda/irlap while running the irdadump. Another important
> > piece of information would be the syslog while running with debug-level=3
> > (check IRDA_DEBUG is set when compiling the kernel and then after modprobe
> > irda, but before doing the irattach, "echo 3 > /proc/sys/net/irda/debug").
> >
> > HTH,
> > Martin
|