Red Hat Bugzilla – Bug 114499
mct_u232: sending break doesn't have any effect
Last modified: 2007-11-30 17:10:35 EST
Description of problem: Sending a break from minicom (or kermit) with kernel 2.6.0-1.61 fails using the mct_u232 driver on /dev/ttyUSB0. Version-Release number of selected component (if applicable): 2.6.0-1.61 How reproducible: Always Steps to Reproduce: 1. connect your usb<->rs232 converter to equipment expecting a break (Sun server, cisco router/switch, etc.) 2. start minicom 3. hit break (in minicom ctrl-a f) when the connected equipment is expecting it (eg. for a cisco when you want to drop to rommon for password recovery or similar activity) Actual results: Doesn't seem to do anything but _something_ is sent over the wire as the lights do blink Expected results: Cisco should drop to rommon, sun to openboot :) Additional info: See bug #112889 and bug #113700 for more information regarding mct_u232.
Unfortunately, there's no easy way to add break to mct_u232. It's a driver based on reverse-engineered code. I suggest turning to Keyspan (or Edgeport). Closing with WONTFIX (should be CANTFIX)