Raja, I hope that others on list(discuss@xxxxxxxxxxxxx) can help you with this issue. I am sorry to run out of ideas and things to try out. Apr 2 21:27:27 DELL-1710 kernel: [ 1566.069218] tty_port_close_start: tty->count = 1 port count = 0. I do believe that you are correct in determining that the device is created and then closed immediately. Maybe some fix like Yair did with slmodem code to get it working after 2.6.31.X kernels? I can relay your messages to wvdial code maintainers, but I am not sure that they could find a fix? But I'll do it if that will help fix your connection. Hope that someone on the list can help, let me know if I should CC: wvdial/wvstreams list to see if they have a fix? Regards, Antonio On 4/2/10, R. S. Patil <kpr.rspatil@xxxxxxxxx> wrote: > Thanks Antonio, > > > >> I don't know what to recommend? The only thing I would try is not >> create the following link: >> >> root@DELL-1710:/dev# ln ttyACM0 ttyS4 >> > Yes I tried this No change in error reported. > >> and see by starting fresh, or unplugging in the device and replugging >> it in and before attempting to dialout do a >> >> # ls /dev/ttyACM* and see if you do not see /dev/ttyACM1 or >> /dev/ttyACM2 and so forth. > > No such thing is happening with every connect disconnect it > gets /dev/ttyACM0 only. > >> >> Try that and hopefully this time it will work. > > Unfortunately this has not happened. > > BTW have u noticed this when phone is connected > > Apr 2 21:27:27 DELL-1710 kernel: [ 1566.069218] tty_port_close_start: > tty->count = 1 port count = 0. > > > is it closing the port as soon as it is created ? > > Can derive any clue out of that. If u are not position to find out > what is happening can u suggest me some useful links ? > > Thanks and regards > > Raja >
