Hi again Duncan, sometimes i get this error when connecting. As i have already mentioned, i am using kernel 2.6.5. This problem isn't linear, sometimes it happens and sometimes it does not. Any idea why the error "Woken by a sem_post event -> Exiting" is happening? Regards, Sergio Freire
Jun 13 21:36:43 centralpark pppoa3[2037]: modem --> pppoa3 --> host stream ready Jun 13 21:36:43 centralpark kernel: CSLIP: code copyright 1989 Regents of the University of California Jun 13 21:36:43 centralpark kernel: PPP generic driver version 2.4.2 Jun 13 21:36:44 centralpark pppd[2087]: pppd 2.4.1 started by root, uid 0 Jun 13 21:36:44 centralpark pppd[2087]: Using interface ppp0 Jun 13 21:36:44 centralpark pppd[2087]: Connect: ppp0 <--> /dev/pts/3 Jun 13 21:36:49 centralpark pppoe[2088]: PPP session is 3735 Jun 13 21:36:53 centralpark pppd[2087]: local IP address 81.193.53.222 Jun 13 21:36:53 centralpark pppd[2087]: remote IP address 213.13.72.1 Jun 13 21:36:53 centralpark pppd[2087]: primary DNS address 194.65.100.117 Jun 13 21:36:53 centralpark pppd[2087]: secondary DNS address 194.65.5.2 Jun 13 21:36:56 centralpark su(pam_unix)[1841]: session closed for user root Jun 13 21:36:56 centralpark pppoa3[2037]: Received signal 1 (thread 1073814432) Jun 13 21:36:56 centralpark pppoa3[2037]: Woken by a sem_post event -> Exiting Jun 13 21:36:56 centralpark pppoa3[2037]: Read from usb Canceled Jun 13 21:36:56 centralpark pppoa3[2037]: Write to usb Canceled Jun 13 21:36:56 centralpark pppoa3[2037]: Exiting Jun 13 21:36:56 centralpark pppoe[2088]: recv (receivePacket): Network is down Jun 13 21:36:56 centralpark pppoe[2088]: recv (receivePacket): Network is down Jun 13 21:37:03 centralpark pppoe[2088]: send (sendPacket): No such device or address Jun 13 21:37:03 centralpark pppd[2087]: Modem hangup Jun 13 21:37:03 centralpark pppd[2087]: Connection terminated. Jun 13 21:37:03 centralpark pppd[2087]: Connect time 0.4 minutes. Jun 13 21:37:03 centralpark pppd[2087]: Sent 366 On Fri, 2004-06-11 at 07:59, Duncan Sands wrote: > Hi Sergio, > > > Duncan and all, can anyone explain why there is a problem with speedtouch 330 in > > kernels 2.6.3 and newer? > > What problem? Can you please be more precise. > > > I was looking at http://speedtouchconf.sourceforge.net but they also have no clear > > explanation. > > I doubt that these newer kernels implement USB core the wrong way... > > The USB core gets changed all the time and sometimes mistakes are made. So it could > be wrongly > implemented. But most likely is that the core follows the standard but the hardware > does not. This > happens a lot: some manufacturers test whether their hardware works with windows, > not whether it > implements the standard correctly. It is then a real pain to work out why things > aren't working with > linux. > > > Is the problem in the module itself, if so, why? > > There is almost certainly nothing wrong with the module. > > > Is the problem in pppd, as somenone mentioned in the internet? > > Who mentioned it, what did they mention? > > > The kernel module, why doesn't it work correctly? > > It does. Most problems come from usbfs (used by modem_run to upload the firmware) > or from a mistake > in the core (core problems usually get fixed fast). In fact most of my spare time > right now is spent on getting > usbfs working better. > > > Sorry for asking all these questions again but there are no clear answers for > > these, neither in the FAQ neither in the forums... there seems to be a lot of > > confusion on these matters. > > Ciao, > > Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
