The output of this command looks something like this.

Nov 30 16:15:23 localhost kernel: usb 2-1: new full speed USB device using uhci_hcd and address 3
Nov 30 16:15:24 localhost kernel: usb 2-1: configuration #1 chosen from 1 choice
Nov 30 16:15:24 localhost kernel: usbcore: registered new driver usbserial
Nov 30 16:15:24 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Nov 30 16:15:24 localhost kernel: usbcore: registered new driver usbserial_generic
Nov 30 16:15:24 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Nov 30 16:15:24 localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
Nov 30 16:15:24 localhost kernel: ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
Nov 30 16:15:24 localhost kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM
Nov 30 16:15:24 localhost kernel: usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
Nov 30 16:15:24 localhost kernel: usbcore: registered new driver ftdi_sio
Nov 30 16:15:24 localhost kernel: drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver

Now this is where we get some good info. We can see every message that the kernel gives while discovering the device and trying to load the drivers for it. You can see the discovery of a new USB device, the usbcore driver registers the usbserial driver and the usbserial_generic driver. Next, the kernel detects that this is a FTDI serial device and usbcore then registers the ftdi_sio driver. The ftdi_sio driver then detects that the device is using a FT232BM chipset and attaches it to the filesystem device node ttyUSB0. Now we have verification that our new hardware is supported, it's working and we can access it at the filesystem device node /dev/ttyUSB0.