I just received an ESP32-2432S028 in the mail and plugged it in to USB and fired up the Arduino IDE to try and mess with it. But no dice.. It turns out this particular dev board uses CH341 serial to USB converter, for which a standard driver is in fact included with the kernal. DMESG reports the device gets connected as ttyUSB0, but then the following happens:

[1089016.769711] usb 1-12: USB disconnect, device number 7
[1089026.049960] usb 1-12: new full-speed USB device number 8 using xhci_hcd
[1089026.341566] usb 1-12: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[1089026.341575] usb 1-12: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[1089026.341580] usb 1-12: Product: USB Serial
[1089026.350406] ch341 1-12:1.0: ch341-uart converter detected
[1089026.364430] usb 1-12: ch341-uart converter now attached to ttyUSB0
[1089026.965382] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input105
[1089027.081355] usb 1-12: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1
[1089027.088620] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[1089027.088678] ch341 1-12:1.0: device disconnected

Sadly, or perhaps rather not for accesibility sake, the device gets identified as a screen based keyboard by the Braile TTY system, and disconnects the CH341 in favor of using the screen keyboard through BRLTTY.

If you are not a blind person, then it is unlikely you need BRLTTY, and in this case, the fix is to simply remove the BRLTTY system to get back to the ch341 getting used directly and not substituted out by BRLTTY. To do this, simply execute sudo apt remove brltty and then re-connect