On Sun, Mar 15, 2020 at 02:50:08PM +0100, Pierre Labastie via blfs-support 
wrote:
> Le 15/03/2020 à 14:23, Chris Gorman via blfs-support a écrit :
> > Hello,
> > 
> > I am new to udev and am trying to get udev to make /dev/ttyUSB0 when a
> > FTDI cable is plugged in.  I get the following from dmesg when the
> > cable is plugged in.
> > 
> > [   48.544775] usb 3-9.3: new full-speed USB device number 9 using xhci_hcd
> > [   48.645980] usb 3-9.3: New USB device found, idVendor=0403,
> > idProduct=6001, bcdDevice= 6.00
> > [   48.645985] usb 3-9.3: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [   48.645989] usb 3-9.3: Product: FT232R USB UART
> > [   48.645991] usb 3-9.3: Manufacturer: FTDI
> > [   48.645993] usb 3-9.3: SerialNumber: AL03O8V3
> > 
> > Unfortunately no device node /dev/ttyUSB0 is created in /dev.  On the
> > same machine with ubuntu 18.04, I get a ttyUSB0 device node made in
> > dev.  I tried creating the following code in
> > /etc/udev/rules.d/97-ftdi.rules
> > 
> > SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
> > ATTRS{serial}=="AL03O8V3", MODE="0660", GROUP="dialout",
> > SYMLINK+="test"
> > 
> > This makes a test symlink but no /dev/ttyUSB0.
> > 
> > I have also tried mknod /dev/ttyUSB0 c 188 0, which will create the
> > file, but my terminal emulation software doesn't work with it.  And it
> > is deleted when I reboot.
> > 
> > Looking for some ideas on how to get this cable working.  Thanks in advance.
> > 
> 
> Missing driver?
> Try plug in the cable, then run (as root) "lspci -v": that might have useful
> information about a kernel driver.
> 
> Pierre

Google finds a page at
https://cateee.net/lkddb/web-lkddb/USB_SERIAL_FTDI_SIO.html
which suggests CONFIG_USB_SERIAL_FTDI_SIO

ĸen
-- 
#define THE_TRUTH_AND_THATS_CUTTIN_ME_OWN_THROAT true
            Al Viro, complaining about a 'TRUE' macro in staging

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to