From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: debain: serail to USB converter
Date: Wed, 31 May 2017 14:46:00 -0700 [thread overview]
Message-ID: <F7A84A91-33A7-4925-9585-A79E3A8EED8B@icloud.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705311126310.3197@southernprince>
Eric Oyen here…
be aware, that man page might be a little dated. I tried to find more recent tools, but google kept pointing me here and most of the stuff was for the older 2.6 kernel (some of which is still valid even under the current 3.x/4.x kernels). So, YMMV.
-eric
On May 31, 2017, at 9:27 AM, Linux for blind general discussion wrote:
> Mark Peveto here,
> I think the refreshing issue might've been caused by the older orca in Debian's repo, but I updated that last night. thanks for the man page. I'll
> take a look at it later this afternoon.
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Wed, 31 May 2017, Linux for blind general discussion wrote:
>
>> hmmm. I didn't run into the refreshing issue when I was there. then again, I am on a mac.
>>
>> here is a man page for set serial. https://www.systutorials.com/docs/linux/man/8-setserial/
>>
>> -eric
>>
>> On May 30, 2017, at 2:48 PM, Linux for blind general discussion wrote:
>>
>>> Mark Peveto here,
>>> Well friend, that wasn't real helpful. The page kept refreshing every time I tried to read it so I couldn't get anywhere. If someone can just get me a
>>> straight set of instructions, that'd be helpful. I've already been on several internet pages about the subject, and end up running into some command
>>> they suggest not working, or a file can't be found, etc. Really, I gotta get this done, and i'm hitting more brick walls than i need at this point. I
>>> spent several hours working on this yesterday afternoon, so if you're hearing frustration, that's why.
>>> Thanks folks.
>>>
>>>
>>>
>>>
>>> Mark Peveto
>>> Registered Linux user number 600552
>>> Everything happens after coffee!
>>>
>>> On Tue, 30 May 2017, Linux for blind general discussion wrote:
>>>
>>>> well,
>>>> I don't have the info handy, but here is a page where they talk about finding and setting up new serial ports.
>>>>
>>>> https://www.cyberciti.biz/faq/find-out-linux-serial-ports-with-setserial/
>>>>
>>>> -eric
>>>>
>>>> On May 30, 2017, at 1:27 PM, Linux for blind general discussion wrote:
>>>>
>>>>> Hi all,
>>>>> Mark Peveto here. The serial to usb connector does show in lsmod. But I wasn't told how to configure the com port for it.
>>>>> I wanna get this artic running on this machine.
>>>>> Appreciate the help.
>>>>>
>>>>>
>>>>> Mark Peveto
>>>>> Registered Linux user number 600552
>>>>> Everything happens after coffee!
>>>>>
>>>>> On Tue, 30 May 2017, Linux for blind general discussion wrote:
>>>>>
>>>>>> well,
>>>>>> you might have to plug it in and then open a console and type lsmod at the prompt. If it's a known device, it should show up in there. then all you would need to do is configure a com port.
>>>>>>
>>>>>> btw, as a comparison, use the lsmod command before you plug in and then check after. if it is recognized, you would see an additional module or 2 running.
>>>>>>
>>>>>> -eric
>>>>>>
>>>>>> On May 29, 2017, at 10:59 AM, Linux for blind general discussion wrote:
>>>>>>
>>>>>>> Mark Peveto here.
>>>>>>> Since only one machine i hae here has a serial port, I got a couple serial to usb converters. Trick is, how do I get debian to recognize it? I was
>>>>>>> gonna hook the artic up to one of my other machines.
>>>>>>>
>>>>>>>
>>>>>>> Mark Peveto
>>>>>>> Registered Linux user number 600552
>>>>>>> Everything happens after coffee!
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Blinux-list mailing list
>>>>>>> Blinux-list@redhat.com
>>>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Blinux-list mailing list
>>>>>> Blinux-list@redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Blinux-list mailing list
>>>>> Blinux-list@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>
>>>>
>>>> _______________________________________________
>>>> Blinux-list mailing list
>>>> Blinux-list@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F7A84A91-33A7-4925-9585-A79E3A8EED8B@icloud.com \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).