On Tue, Sep 5, 2017 at 1:59 PM, Dan Williams wrote:
> On Tue, 2017-09-05 at 12:32 -0700, Tim Harvey wrote:
>> On Tue, Sep 5, 2017 at 9:53 AM, Dan Williams wrote:
>> > On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote:
>> > > On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams
>> > > wrote:
>> > > > O
On Tue, 2017-09-05 at 12:32 -0700, Tim Harvey wrote:
> On Tue, Sep 5, 2017 at 9:53 AM, Dan Williams wrote:
> > On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote:
> > > On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams
> > > wrote:
> > > > On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote:
> > > >
On Tue, Sep 5, 2017 at 9:40 PM, Tim Harvey wrote:
> On Tue, Sep 5, 2017 at 9:56 AM, Pičugins Arsenijs wrote:
>> I don't know if it's going to help you with this issue, but if you can
>> hardcode a path to the serial port somewhere, take a look in the
>> "/dev/serial/by-id" directory - it has sy
On Tue, Sep 5, 2017 at 9:56 AM, Pičugins Arsenijs wrote:
> I don't know if it's going to help you with this issue, but if you can
> hardcode a path to the serial port somewhere, take a look in the
> "/dev/serial/by-id" directory - it has symlinks to /dev/tty* entries that
> correspond to hardwa
On Tue, Sep 5, 2017 at 9:53 AM, Dan Williams wrote:
> On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote:
>> On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams wrote:
>> > On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote:
>> > > Greetings,
>> > >
>> > > I've got a Sierra Wireless HL7588 modem which
I don't know if it's going to help you with this issue, but if you can hardcode
a path to the serial port somewhere, take a look in the "/dev/serial/by-id"
directory - it has symlinks to /dev/tty* entries that correspond to hardware
serial ports currently connected. Names of the symlinks are gen
On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote:
> On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams wrote:
> > On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote:
> > > Greetings,
> > >
> > > I've got a Sierra Wireless HL7588 modem which exposes three
> > > ttyACM
> > > devs via the cdc_acm driv
On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams wrote:
> On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote:
>> Greetings,
>>
>> I've got a Sierra Wireless HL7588 modem which exposes three ttyACM
>> devs via the cdc_acm driver. The device appears to work fine with
>> ModemManager (1.6.8) but occasio
Check out the paul/Infineon branch for some udev rules that should work in
your case.
You should be able to blacklist the offending ACM interface using a simile
udev rule.
Alternatively, also on that branch is a work in progress plugin for the
HL75xx series that uses the NCM interfaces. There are
On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote:
> Greetings,
>
> I've got a Sierra Wireless HL7588 modem which exposes three ttyACM
> devs via the cdc_acm driver. The device appears to work fine with
> ModemManager (1.6.8) but occasionally mm detects the primary device
> as
> ttyACM2 instead
Greetings,
I've got a Sierra Wireless HL7588 modem which exposes three ttyACM
devs via the cdc_acm driver. The device appears to work fine with
ModemManager (1.6.8) but occasionally mm detects the primary device as
ttyACM2 instead of the usuall ttyACM0. In this case (detected primary
AT interface
11 matches
Mail list logo