Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Pyserial and Ubuntu Linux kernel 3.13.0-65-generic Date: Tue, 6 Oct 2015 21:31:02 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 19 Message-ID: References: <201510030907.t93974tU002535@fido.openend.se> <201510030919.t939Jdq6003741@fido.openend.se> <560FE87D.2050706@gmail.com> NNTP-Posting-Host: 67-130-15-94.dia.static.qwest.net X-Trace: reader1.panix.com 1444167062 2605 67.130.15.94 (6 Oct 2015 21:31:02 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 6 Oct 2015 21:31:02 +0000 (UTC) User-Agent: slrn/1.0.2 (Linux) Xref: csiph.com comp.lang.python:97457 On 2015-10-03, Laura Creighton wrote: > https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345 > seems to be about a whole lot of serial ports to me, not just FTDI We just ran into the OP's problem where I work: Ununtu kernel updated and all serial ports stopped working (it isn't just an FTDI problem). Booting with the previous kernel makes the serial ports work again. What I'm trying to figure out: is this something _Ubuntu_ did so that only affects Ubuntu kernels? [I haven't seen it mentioned on the linux-serial mailing list, and nobody other than Ubuntu users seem to have the problem, so I think the answer to my question is "yes".] -- Grant Edwards grant.b.edwards Yow! Am I SHOPLIFTING? at gmail.com