Bug#758159: systemd: serial devices no longer working with systemd

[M G Berberich]

Hello,

Am Montag, den 17. November schrieb intrigeri:
> Michael Biebl wrote (21 Aug 2014 01:48:36 GMT) :
> > Am 14.08.2014 23:37, schrieb M G Berberich:
> >> 
> >> since systemd has been installed the serial devices /dev/ttyS2 and
> >> /dev/ttyS3 are no longer working. Devices seems to be initialized
> >> 
> >>   # setserial -g /dev/ttyS*
> >>   …
> >>   /dev/ttyS2, UART: 16550A, Port: 0xc050, IRQ: 16
> >>   /dev/ttyS3, UART: 16550A, Port: 0xc040, IRQ: 16
> >> 
> >> but do no longer work.
> >> 
> >>   # stty -a </dev/ttyS2
> >> 
> >> hangs too.
> >> /dev/ttyS2 and /dev/ttyS3 are not on motherboard, but on a PCI-Card.
> 
> > Is this maybe a permission problem?
> > What's the output of
> > ls -la /dev/ttyS*
> 
> > Please compare that with the output you get when booting with sysvinit.
> > See below.
> 
> >> This worked fine with sysvinit
> 
> > If you boot with init=/lib/sysvinit/init via the kernel command line,
> > the problem is gone?
> 
> Ping? Can you still reproduce this issue? If yes, may you please
> answer Michael's questions? Thanks in advance.

Sorry, but I had reported the bug twice. First time when I
experimented with systemd, second time when Debian forced me to switch
to systemd (by conflicts with kde-full), and has been solved (at least
for me).

The problem was modemmanger, which was automatically installed and
screwed up the serial interfaces.

Please see Bug#762396.

	MfG
	bmg

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