Hmm.. The problem is that I'd like to stay with the Redhat kernel so I don't break anything else. And Redhat at this moment has 2.4.20 as its highest release.
Can I just steal the pl2303.c and pl2303.h files from the 2.4.24 release and remake them on my computer, or do I also need to remake usbserial and other stuff? I notice that Greg KH made some changes to the driver and added it at the 2.4.23 level. Will those changes fix my problem? Thanks in advance. Ovanes On Wed, 14 Jan 2004, Christopher Fowler wrote: > I had issues with the pl2303 reporting with 2.4.18. I've since then > upgraded to 2.4.24 and have had no problems. > > > On Wed, 2004-01-14 at 13:37, [EMAIL PROTECTED] wrote: > > Hello there, > > > > I'm not a kernel coder myself, but I think there may be a problem > > with the pl2303 driver. > > > > I have a gateway 400VTX laptop that doesn't have a serial port, so I > > bought a ATEN UC-232 -based serial->usb converter to make my GPS work. > > > > First, setserial doesn't work: > > > > #setserial /dev/usb/ttyUSB0 > > Cannot get serial info: Invalid argument > > > > but even worse, it crashes my system... > > > > setserial -a /dev/usb/ttyUSB0 > > > > (The above command puts my little system to never-ending sleep, > > making 2 of the LED lights blink.) > > > > I was using a program called gpsd(comes with gpsdrive) > > > > The first time I run gpsdrive, it seems that all is fine and I'm able > > to get gps data. after I exit gpsdrive and run it again, it still > > works fine, but when I exit the 2nd time, my system goes to sleep > > again in the same way. (with the same 2 lights blinking) > > > > I had both usbserial and pl2303 loaded with debug=1 and here's what > > the 1st run produced: (Don't know why the lines are truncated in > > the beginning) > > > > Jan 14 07:33:12 localhost kernel: <serial.c: generic_chars_in_buffer - returns 0 > > Jan 14 07:33:13 localhost kernel: <_callback - port 0 > > Jan 14 07:33:25 localhost kernel: <ta = 32 > > Jan 14 07:33:34 localhost kernel: <7_callback - port 0 > > Jan 14 07:33:40 localhost kernel: <a = 2c > > Jan 14 07:33:47 localhost kernel: <_callback - port 0 > > Jan 14 07:35:34 localhost kernel: <a = 38 > > > > Then, when I run it the 2nd time, here's what the logs gave me: > > > > Jan 14 07:35:38 localhost kernel: <serial.c: generic_chars_in_buffer - returns 0 > > Jan 14 07:35:49 localhost kernel: <a = 4c > > Jan 14 07:35:55 localhost kernel: <_read_bulk_callback - length = 1, data = 2e > > Jan 14 07:36:13 localhost kernel: <_read_bulk_callback - length = 1, data = 50 > > Jan 14 07:36:24 localhost kernel: <in_buffer = port 0 > > Jan 14 07:36:26 localhost kernel: <turns 0 * After this it froze > > > > The only thing different between the 2 runs is that there seems to be > > still data left in the buffer the 2nd time... > > > > ...<_read_bulk_callback - length = 1, data = 2e > > ...<_read_bulk_callback - length = 1, data = 50 > > > > In fact, I think this is the only debug message produced by the pl2303 > > driver. When I repeated this with only the pl2303 driver being debug=1, > > the only syslog entry I received was during the 2nd run: > > > > Jan 14 08:02:25 localhost kernel: llback - length = 1, data = 50 > > > > Do you think there's hope for me? What should I do? > > > > I'm using Redhat 2.4.20-28.9 > > > > Do you know if Belkin drivers are any better? Which serial usb > > converters have the best support on Linux? > > > > Ovanes ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
