Bug#762396: systemd: serial devices /dev/ttyS2 and /dev/ttyS3 do not work

2014-09-22 Thread M G Berberich
Am Montag, den 22. September schrieb Michael Biebl:
> Control: reassign -1 modemmanager
> 
> Am 22.09.2014 um 10:58 schrieb M G Berberich:
> > Hello,
> > 
> > Am Sonntag, den 21. September schrieb Michael Biebl:
> >> Am 21.09.2014 um 22:23 schrieb M G Berberich:
> >>> Package: systemd
> >>> Version: 208-8
> >>> Severity: normal
> >>>
> >>> Dear Maintainer,
> >>>
> >>> I have a card with two additional serial devices in the system, giving
> >>> /dev/ttyS2 and /dev/ttyS3. One with a thermal sensor and one with a
> >>> serial terminal. These serial devices do not work when the system is
> >>> started with systemd. They do work fine if sysvinit is used.
> >>
> >> Looking at the systemd-analyze dump, I see
> >>
> > …
> >>
> >> The devices seem to be functional, but maybe the getty on ttyS2
> >> interferes with what you want to do with ttyS2?
> > 
> > No, on ttyS2 there is a serial Terminal (VT320), so this is O.K.
> > 
> > But I found the problem:
> > It was modemmanager, which was _automatically_ installed. Modemmanager
> > screwed up ttyS3 and ttyS2 (perhaps the onboard ttyS0 and ttyS1 also,
> > but I can’t tell, because there is no device on ttyS0 and ttyS1 does
> > not even have a connector). Probably systemd/modemmanager/dbus assumes
> > that there must be a modem understanding AT-commands behind every
> > serial interface. Uninstalling modemmanager does the job.
> 
> Ok, re-assigning to modemmanager.
> Which version of modemmanager did you have installed?

The standard one from jessie: most likely 1.4.0-1

MfG
bmg

-- 
„Des is völlig wurscht, was heut beschlos- | M G Berberich
 sen wird: I bin sowieso dagegn!“  | berbe...@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg)  | www.fmi.uni-passau.de/~berberic


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#762396: systemd: serial devices /dev/ttyS2 and /dev/ttyS3 do not work

2014-09-22 Thread Michael Biebl
Control: reassign -1 modemmanager

Am 22.09.2014 um 10:58 schrieb M G Berberich:
> Hello,
> 
> Am Sonntag, den 21. September schrieb Michael Biebl:
>> Am 21.09.2014 um 22:23 schrieb M G Berberich:
>>> Package: systemd
>>> Version: 208-8
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> I have a card with two additional serial devices in the system, giving
>>> /dev/ttyS2 and /dev/ttyS3. One with a thermal sensor and one with a
>>> serial terminal. These serial devices do not work when the system is
>>> started with systemd. They do work fine if sysvinit is used.
>>
>> Looking at the systemd-analyze dump, I see
>>
> …
>>
>> The devices seem to be functional, but maybe the getty on ttyS2
>> interferes with what you want to do with ttyS2?
> 
> No, on ttyS2 there is a serial Terminal (VT320), so this is O.K.
> 
> But I found the problem:
> It was modemmanager, which was _automatically_ installed. Modemmanager
> screwed up ttyS3 and ttyS2 (perhaps the onboard ttyS0 and ttyS1 also,
> but I can’t tell, because there is no device on ttyS0 and ttyS1 does
> not even have a connector). Probably systemd/modemmanager/dbus assumes
> that there must be a modem understanding AT-commands behind every
> serial interface. Uninstalling modemmanager does the job.

Ok, re-assigning to modemmanager.
Which version of modemmanager did you have installed?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#762396: systemd: serial devices /dev/ttyS2 and /dev/ttyS3 do not work

2014-09-22 Thread M G Berberich
Hello,

Am Sonntag, den 21. September schrieb Michael Biebl:
> Am 21.09.2014 um 22:23 schrieb M G Berberich:
> > Package: systemd
> > Version: 208-8
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I have a card with two additional serial devices in the system, giving
> > /dev/ttyS2 and /dev/ttyS3. One with a thermal sensor and one with a
> > serial terminal. These serial devices do not work when the system is
> > started with systemd. They do work fine if sysvinit is used.
> 
> Looking at the systemd-analyze dump, I see
>
…
>
> The devices seem to be functional, but maybe the getty on ttyS2
> interferes with what you want to do with ttyS2?

No, on ttyS2 there is a serial Terminal (VT320), so this is O.K.

But I found the problem:
It was modemmanager, which was _automatically_ installed. Modemmanager
screwed up ttyS3 and ttyS2 (perhaps the onboard ttyS0 and ttyS1 also,
but I can’t tell, because there is no device on ttyS0 and ttyS1 does
not even have a connector). Probably systemd/modemmanager/dbus assumes
that there must be a modem understanding AT-commands behind every
serial interface. Uninstalling modemmanager does the job.

MfG
bmg

-- 
„Des is völlig wurscht, was heut beschlos- | M G Berberich
 sen wird: I bin sowieso dagegn!“  | berbe...@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg)  | www.fmi.uni-passau.de/~berberic


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#762396: systemd: serial devices /dev/ttyS2 and /dev/ttyS3 do not work

2014-09-21 Thread Michael Biebl
Am 21.09.2014 um 22:23 schrieb M G Berberich:
> Package: systemd
> Version: 208-8
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a card with two additional serial devices in the system, giving
> /dev/ttyS2 and /dev/ttyS3. One with a thermal sensor and one with a
> serial terminal. These serial devices do not work when the system is
> started with systemd. They do work fine if sysvinit is used.

Looking at the systemd-analyze dump, I see


-> Unit dev-ttyS3.device:
Description: PCI 9835 Multi-I/O Controller (2S (16C550 UART))
Instance: n/a
Unit Load State: loaded
Unit Active State: active
..

-> Unit
sys-devices-pci:00-:00:1c.3-:04:00.0-:05:01.0-tty-ttyS2.device:
Description: PCI 9835 Multi-I/O Controller (2S (16C550 UART))
Instance: n/a
Unit Load State: loaded
Unit Active State: active

and a getty on ttyS2:

-> Unit serial-getty@ttyS2.service:
Description: Serial Getty on ttyS2
Instance: ttyS2
Unit Load State: loaded
Unit Active State: active


The devices seem to be functional, but maybe the getty on ttyS2
interferes with what you want to do with ttyS2?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature