Greg KH wrote: > I think people usually have better luck using agetty, but it too is > pretty fickle at times.
With agetty it's not working at all. I have just been testing the converter with a different machine, which has a different USB controller, but there is the same problem.. am i really the first one using this driver together with mgetty? Once again, i find these debug messages quite strange: usbserial.c: serial_write_room - port 0 usbserial.c: generic_write_room - port 0 usbserial.c: generic_write_room - returns 64 usbserial.c: serial_write - port 0, 0 byte(s) pl2303.c: pl2303_write - port 0, 0 bytes pl2303.c: pl2303_write - length = 0, data = usbserial.c: serial_write_room - port 0 usbserial.c: generic_write_room - port 0 usbserial.c: generic_write_room - returns 0 pl2303.c: pl2303_write_bulk_callback - port 0 usbserial.c: port_softint - port 0 These mesages are repeated very often, filling the whole dmesg buffer. It seems that write() is called again and again with a buffer size of 0. Stracing mgetty and login does not show those calls. Is this normal behaviour? I really would like to avoid diving into the kernel code.. BTW: Using the generic serial driver leads to results as if baud rates are mismatching - changing the baud rate on one side to other rates had no success. bye Norbert -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr f�r 1 ct/ Min. surfen! ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
