On Mon, Feb 15, 2016 at 6:52 PM, Warren Young wrote:
> On Feb 15, 2016, at 10:34 AM, Mike - st257 wrote:
> >
> > I have not yet found a USB-to-serial adapter detected as /dev/ttyACM1.
> > Try /dev/ttyUSB0 ?
>
> Both naming schemes are correct, depending
On Feb 15, 2016, at 10:34 AM, Mike - st257 wrote:
>
> I have not yet found a USB-to-serial adapter detected as /dev/ttyACM1.
> Try /dev/ttyUSB0 ?
Both naming schemes are correct, depending on the *type* of USB to serial
converter. The difference comes down to a
On 16/02/16 01:32, Robert Heller wrote:
OK, I just tested it:
sauron.deepsoft.com% sudo /usr/sbin/setenforce permissive
sauron.deepsoft.com% sudo minicom
Device /dev/ttyACM0 access failed: No such file or directory.
sauron.deepsoft.com% sudo /usr/sbin/setenforce enforcing
Nope, that did not
I have not yet found a USB-to-serial adapter detected as /dev/ttyACM1.
Try /dev/ttyUSB0 ?
- Mike
On Sat, Feb 13, 2016 at 10:14 AM, Robert Heller wrote:
> I sent this out about a week or so ago, but I have heard nothing. I am
> *thinking* it is a SELINUX problem, but I
At Sun, 14 Feb 2016 19:20:48 -0500 Robert Heller wrote:
>
> At Mon, 15 Feb 2016 09:41:32 +1100 CentOS mailing list
> wrote:
>
> >
> > On 14/02/16 02:14, Robert Heller wrote:
> > > I sent this out about a week or so ago, but I have heard nothing. I am
On 14/02/16 02:14, Robert Heller wrote:
I sent this out about a week or so ago, but I have heard nothing. I am
*thinking* it is a SELINUX problem, but I cannot figure out what.
If you suspect SELinux is to blame, have you tried putting SELinux into
permissive mode to see that resolves the
I sent this out about a week or so ago, but I have heard nothing. I am
*thinking* it is a SELINUX problem, but I cannot figure out what. The SELINUX
settings for both machines are *exactly* the same (the stock defaults for a
standard CentOS 6 install). The *only* difference is that the desktop
On Sat, Feb 13, 2016 at 5:14 PM, Robert Heller wrote:
> I sent this out about a week or so ago, but I have heard nothing. I am
> *thinking* it is a SELINUX problem, but I cannot figure out what. The SELINUX
> settings for both machines are *exactly* the same (the stock
At Sat, 13 Feb 2016 10:14:30 -0500 CentOS mailing list
wrote:
>
> I sent this out about a week or so ago, but I have heard nothing. I am
> *thinking* it is a SELINUX problem, but I cannot figure out what. The SELINUX
> settings for both machines are *exactly* the same (the
> OK, I tried rebooting without the '8250.nr_uarts=8' option and that had no
> effect.
>
> I wonder if I should file a bug report? I don't know if I should file it
with
> the Red Hat bugzilla or the CentOS bugzilla.
Should be with the Red Hat, I guess.
I have two computers: both running CentOS 6.7, 64-bit, with
kernel 2.6.32-573.12.1.el6.x86_64. One is a laptop with an 2 core Intel
processor and the other is a desktop machine with a 4 core AMD processor. Both
with selinux enabled.
I have a USB serial port device (a RR-CirKits LCC-Buffer
11 matches
Mail list logo