Any changes made to u3g recently?
-
Does anyone know if any changes were made to the u3g drivers within the most recent snapshot of 2.0? Maybe something was done on FreeBSD8.1 itself? I have a USB/MC760 which I was able to get up and running a little over 2 weeks ago (http://forum.pfsense.org/index.php/topic,32781.0.html)
Every since upgrading to yesterdays i386 snapshot and including today's, my 3g modem is unable to connect. See log below. I've removed and recreated the interface a couple of times with no luck. I did test the modem on my windows laptop to verify that it is still working, which it does. I may go back to an older snapshot but since i've been testing the IPv6 stuff, I want to stay with the latest snapshot if possible.
What stand out is this: 'can't lock device cuaU0.0'
Thanks as always!
Cino
Feb 10 09:28:26 ppp: [opt2_link0] Link: reconnection attempt 11 in 4 seconds Feb 10 09:28:26 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:26 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:26 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:25 ppp: [opt2_link0] Link: reconnection attempt 10 Feb 10 09:28:23 ppp: [opt2_link0] Link: reconnection attempt 10 in 2 seconds Feb 10 09:28:23 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:23 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:23 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:22 ppp: [opt2_link0] Link: reconnection attempt 9 Feb 10 09:28:20 ppp: [opt2_link0] Link: reconnection attempt 9 in 2 seconds Feb 10 09:28:20 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:20 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:20 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:18 ppp: [opt2_link0] Link: reconnection attempt 8 Feb 10 09:28:17 ppp: [opt2_link0] Link: reconnection attempt 8 in 1 seconds Feb 10 09:28:17 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:17 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:17 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:16 ppp: [opt2_link0] Link: reconnection attempt 7 Feb 10 09:28:14 ppp: [opt2_link0] Link: reconnection attempt 7 in 2 seconds Feb 10 09:28:14 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:14 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:14 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:13 ppp: [opt2_link0] Link: reconnection attempt 6 Feb 10 09:28:11 ppp: [opt2_link0] Link: reconnection attempt 6 in 2 seconds Feb 10 09:28:11 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:11 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:11 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:11 ppp: [opt2_link0] Link: reconnection attempt 5 Feb 10 09:28:06 ppp: [opt2_link0] Link: reconnection attempt 5 in 4 seconds Feb 10 09:28:06 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:06 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:06 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:06 ppp: [opt2_link0] Link: reconnection attempt 4 Feb 10 09:28:02 ppp: [opt2_link0] Link: reconnection attempt 4 in 4 seconds Feb 10 09:28:02 ppp: [opt2_link0] LCP: Down event Feb 10 09:28:02 ppp: [opt2_link0] Link: DOWN event Feb 10 09:28:02 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:28:02 ppp: [opt2_link0] Link: reconnection attempt 3 Feb 10 09:27:58 ppp: [opt2_link0] Link: reconnection attempt 3 in 4 seconds Feb 10 09:27:58 ppp: [opt2_link0] LCP: Down event Feb 10 09:27:58 ppp: [opt2_link0] Link: DOWN event Feb 10 09:27:58 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:27:57 ppp: [opt2_link0] Link: reconnection attempt 2 Feb 10 09:27:55 ppp: [opt2_link0] Link: reconnection attempt 2 in 2 seconds Feb 10 09:27:55 ppp: [opt2_link0] LCP: Down event Feb 10 09:27:55 ppp: [opt2_link0] Link: DOWN event Feb 10 09:27:55 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:27:54 ppp: [opt2_link0] Link: reconnection attempt 1 Feb 10 09:27:52 ppp: [opt2_link0] Link: reconnection attempt 1 in 2 seconds Feb 10 09:27:52 ppp: [opt2_link0] LCP: Down event Feb 10 09:27:52 ppp: [opt2_link0] Link: DOWN event Feb 10 09:27:52 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:27:52 ppp: [opt2_link0] LCP: LayerStart Feb 10 09:27:52 ppp: [opt2_link0] LCP: state change Initial --> Starting Feb 10 09:27:52 ppp: [opt2_link0] LCP: Open event Feb 10 09:27:52 ppp: [opt2_link0] Link: OPEN event Feb 10 09:27:52 ppp: [opt2] Bundle: Interface ng0 created Feb 10 09:27:52 ppp: web: web is not running Feb 10 09:27:52 ppp: last message repeated 2 times Feb 10 09:27:51 ppp: process 6789 terminated Feb 10 09:27:51 ppp: [opt2_link0] Link: Shutdown Feb 10 09:27:51 ppp: [opt2] Bundle: Shutdown Feb 10 09:27:49 ppp: [opt2] IPCP: Close event Feb 10 09:27:49 ppp: [opt2] IFACE: Close event Feb 10 09:27:49 ppp: caught fatal signal term Feb 10 09:27:49 ppp: waiting for process 6789 to die... Feb 10 09:27:49 ppp: process 8497 started, version 5.5 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 18:46 18-Jan-2011) Feb 10 09:27:49 ppp: Feb 10 09:27:49 ppp: Multi-link PPP daemon for FreeBSD Feb 10 09:27:49 ppp: [opt2_link0] Link: reconnection attempt 1 in 3 seconds Feb 10 09:27:49 ppp: [opt2_link0] LCP: Down event Feb 10 09:27:49 ppp: [opt2_link0] Link: DOWN event Feb 10 09:27:49 ppp: [opt2_link0] can't lock device cuaU0.0 Feb 10 09:27:49 ppp: [opt2_link0] LCP: LayerStart Feb 10 09:27:49 ppp: [opt2_link0] LCP: state change Initial --> Starting Feb 10 09:27:49 ppp: [opt2_link0] LCP: Open event Feb 10 09:27:49 ppp: [opt2_link0] Link: OPEN event Feb 10 09:27:49 ppp: [opt2] Bundle: Interface ng0 created Feb 10 09:27:49 ppp: web: web is not running Feb 10 09:27:49 ppp: process 6789 started, version 5.5 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 18:46 18-Jan-2011) Feb 10 09:27:49 ppp: Feb 10 09:27:49 ppp: Multi-link PPP daemon for FreeBSD -
You can rm -r /var/lock/* and it will start.
-
@ermal:
You can rm -r /var/lock/* and it will start.
Thanks for the quick reply. I don't have a /var/lock/ folder on my box. I created one to see if that would make a difference, it didn't.
Anything else I could try?
Edit: Thanks for pointing me into the right direction. Like I said, I didn't have a /var/lock/ folder but I found a /var/spool/lock/ folder. With-in that folder was a file named 'LCK..cuaU0.0' Deleted that file and now 3G is back into action!