I am not, that is exactly what I was pointing out.
On 20 September 2016 03:06:20 Zé Loff <zel...@zeloff.org> wrote:
On Tue, Sep 20, 2016 at 01:30:35AM +0000, Stuart Henderson wrote:
On 2016-09-19, Fred <open...@crowsons.com> wrote:
> According to the dmesg you have:
>
> puc0 at pci0 dev 22 function 3 "Intel 6 Series KT" rev 0x04: ports: 1
com
> com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo
> com4: probed fifo depth: 0 bytes
> did you try cuaU3?
That one would be (tty|cua)04 (which will need additional device
nodes creating with MAKEDEV. But it's PCI not USB.
It might be behind one of these disabled hubs though:
uhub2 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching Hub"
rev 2.00/0.00 addr 2
uhub2: device problem, disabling port 1
uvideo0 at uhub2 port 6 configuration 1 interface 0 "Chicony Electronics
Co., Ltd. Integrated Camera" rev 2.00/7.52 addr 3
video0 at uvideo0
uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub"
rev 2.00/0.00 addr 2
uhub3: device problem, disabling port 5
(btw, dmesg after the email signature means it gets stripped by most
email programs, so hard to quote :)
Aren't you guys mixing com* and ucom*? If it is a USB dongle it should
show up as ucom0 on dmesg. (plus, it used to work as cuaU0)
--
