Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Thu, Sep 29, 2011 at 04:35:31PM +0200, Bart Hartgers wrote:
> Hi ael,
> >
> > I have a real RS232 port on a desktop (back at home now), so
> > I guess I could connect from the netbook USB -> ark3116 -> RS232
> > desktop. I will have to see what cables I have, but I think I have
> > a very old RS232 breakout box somewhere, so I can probably
> > fix something up.
I have found the breakout box. Unfortunately it is all 25 pin
connectors, so I will have to dig out or make some 25 <--> 9
pin cables. Make take a while...
>
> That would be great! Hopefully we can make some progress that way.
>
> > I suppose I could use picoterm or similar to view the incoming data
> > on the desktop: it is a while since I looked at those programs.
>
> I realized I made a mistake: the program I meant is called picocom.
>
> If you have a breakout-box, it would also be interesting to 'manually'
> toggle some signals, basically just short rxd and/or cts to gnd for a
> sec.
> That should trigger some messages in the log if the ark3116 module is
> loaded with debug=1.
It is a very long time since I played with stty, statserial and such.
So I may need to pore over man pages & try and work out what I am
doing. I seem to remember having using minicom at one time. I think
one could set up the serial parameters from a menu, and otherwise it
just worked as a terminal.
Somewhere, I think I have the specification for the garmin connector,
but I can trace the wires otherwise. I guess I will start there. It
can't be very complicated.
I suppose just using statserial while the garmin is attached to the
ordinary RS232 port would at least reveal its initial state.
Unfortunately a hard disc has just failed on one machine (it would
have to be the boot disc..) and the latest xorg packages have decided
to stop working properly on another machine, so I have my hands
rather full just now... )
ael
>
> Thanks!
>
> Bart
>
>
> --
> Bart Hartgers - New e-mail: bart.hartgers@gmail.com
Reply to: