I managed to track down the problems I was having with Minicom and thought I would let you know for future reference. I'm using Red Hat Linux 7.3. Red Hat's version of Minicom has been patched from the original 2.00.0 source code. I found one bug with Red Hat's RPM and one bug with the Lockdev package that they distribute. Lockdev is a library that does file locking on TTYs. The first bug was that the --noinit or -o option in Minicom would not keep the app from trying to obtain a lock on the tty. I submitted a patch to RedHat for that bug. The second bug was that the Lockdev library was redirecting me to /dev/ttyUSB0 instead of just trying to grab the lock on /dev/usb/ttyUSB0. Even though permissions were correct on /dev/usb/ttyUSB0, they weren't on /dev/ttyUSB0, which I didn't even realize existed at first. The result was an error that didn't indicate a permissions problem very cleanly at all. The quick fix is to point Minicom at /dev/ttyUSB0 and make sure permissions are correct on it. Hopefully this helps someone in the future. I'll have to try submitting this thread to the Sourceforge mailing list. Cheers, Nathan
-----Original Message----- From: Greg KH [mailto:[EMAIL PROTECTED]] Sent: Mon 9/23/2002 5:09 PM To: Nathan Crapo Cc: Subject: Re: usbserial driver and minicom - lock failed permission denied On Fri, Sep 20, 2002 at 05:14:02PM -0700, [EMAIL PROTECTED] wrote: > Greg, > > First of all thanks for the great work! I've got a problem and have > checked for help on google and the linux-usb list server. Couldn't > manage to find anything describing my problem. > > I'm trying to use an EdgePort/4 USB serial converter. I'm using > minicom, but can't seem to open /dev/usb/ttyUSB0 as any user except > root. I've set the permissions on /dev/usb/ttyUSB0 to 666 like I've > been doing on /dev/ttyS*, but it still doesn't do the trick. The > error message is "Device /dev/usb/ttyUSB0 lock failed: Permission > denied.". I haven't looked at the source for minicom or the > io_edgeport driver yet. I wondered if you've seen this before. > > I'm running Red Hat Linux 7.3 with kernel 2.4.18-3smp. I've included > an strace output if you care to look. You'll note that access on the > dev node is coming back alright. This is a minicom configuration issue, and not a driver problem. Sorry, but I have no idea what to do. Good luck, greg k-h __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com ------------------------------------------------------- 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
