API tools faq
paste
Advertisement
pjj90292

bcm_wimax driver now working with 13.04

pjj90292
Oct 4th, 2013
253
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.62 KB | None | 0 0
raw download clone embed print report
  1. It almost is. Made a test today. Following the procedures used to get drxvi314.ko to work with Kubuntu 13.04 I substituted 'bcm_wimax' for drxvi314.ko.
  2.  
  3. It loaded with insmod.
  4. picocom successfully changed the modem to 'auto' (AT+4GMODE=2).
  5. Power light turns on. Some claim that this is how far the driver goes successfully.
  6. It went further for me.
  7. In the following I post the RAW data output (truncated) for my two attempts. The first one failed because I had changed the wimaxd.conf file to reflect values gleaned from Windows modem.ini. This was rejected. Changing back to the linux notation made the driver activate the modem and start connection attempts.
  8.  
  9. The posted data need some interpretation, but I have marked some important steps of the process.
  10.  
  11. Data:
  12.  
  13. 10/04/13
  14. testing the functionality of bcm_wimax.
  15. Start 3g modem.
  16. Reset to 4G
  17. lsusb and demsg output below.
  18.  
  19. 4Gmodem power light is on.
  20. link eth1 is not ready.
  21.  
  22.  
  23.  
  24.  
  25. Output:
  26.  
  27. sudo dmesg -c|tail -15
  28. [ 5669.775395] sr 2:0:0:0: Attached scsi generic sg2 type 5
  29. [ 5669.916219] usb 1-4.2: reset full-speed USB device number 4 using ehci-pci
  30. [ 5676.690829] usb 1-4.2: USB disconnect, device number 4
  31. [ 5682.104169] usb 1-4.2: new full-speed USB device number 5 using ehci-pci
  32. [ 5682.197634] usb 1-4.2: New USB device found, idVendor=1fac, idProduct=0151
  33. [ 5682.197644] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  34. [ 5682.197651] usb 1-4.2: Product: U600 EVDO Modem
  35. [ 5682.197657] usb 1-4.2: Manufacturer: Franklin Wireless Corp.
  36. [ 5682.199422] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device
  37. [ 5895.296184] usb 1-4.1: new high-speed USB device number 6 using ehci-pci
  38. [ 5895.389034] usb 1-4.1: New USB device found, idVendor=198f, idProduct=0220 <-------
  39. [ 5895.389045] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  40. [ 5895.389052] usb 1-4.1: Product: BCSM250 Mobile WiMAX
  41. [ 5895.389058] usb 1-4.1: Manufacturer: Beceem Communications
  42. [ 5895.389063] usb 1-4.1: SerialNumber: SCG90xxxxx
  43. peter@pjj:~$
  44. peter@pjj:~$
  45. peter@pjj:~$
  46. peter@pjj:~$ sudo insmod /lib/modules/3.8.0-31-generic/kernel/drivers/staging/bcm/bcm_wimax.kopeter@pjj:~$
  47. peter@pjj:~$
  48. peter@pjj:~$ sudo dmesg -c|tail -50
  49. [ 5962.938527] bcm_wimax: module is from the staging directory, the quality is unknown, you have been warned.
  50. [ 5962.943588] beceem: Beceem Communications Inc. WiMAX driver, 5.2.45 <----
  51. [ 5962.943598] Copyright 2010. Beceem Communications Inc
  52. [ 5962.946845] usbbcm_device_probe:subtype[1] = 0x000000ff
  53. [ 5962.946854] usbbcm_device_probe:subtype[2] = 0x00000000
  54. [ 5962.946859] usbbcm_device_probe:subtype[4] = 0x00000000
  55. [ 5962.946864] usbbcm_device_probe:subtype[8] = 0x00000000
  56. [ 5962.946869] InitAdapter:Initialising Adapter = f6280500
  57. [ 5962.946933] InitAdapter:Adapter initialised<7>[ 5962.946941] usbbcm_device_probe:psIntfAdapter 0xf3877000
  58. [ 5962.947136] usb 1-4.1: RDM Chip ID 0xbece3301
  59. [ 5962.967455] beceem: AutoSyncup is Disabled
  60. [ 5962.967463] beceem: Disabling autolink up
  61. [ 5962.967467] beceem: DDR Setting: 3
  62. [ 5962.967471] beceem: Power Save Mode: 0
  63. [ 5962.967475] beceem: Enabling Auto Firmware Download
  64. [ 5962.967478] beceem: MIPSConfig : 0x0
  65. [ 5962.967481] beceem: PMU MODE: 0
  66. [ 5962.967484] beceem: uiEEPROMFlag : 0x2
  67. [ 5962.968037] reset_card_proc:Resetting UMA-B
  68. [ 5963.044132] usb 1-4.1: reset high-speed USB device number 6 using ehci-pci
  69. [ 5963.158339] ddr_init:Register Count is =48
  70. [ 5963.187891] usbbcm 1-4.1:1.0: beceem eth1: register usb-0000:00:1d.7-4.1 f4:63:49:07:27:9d
  71. [ 5963.188713] beceem eth1: link up failed (download in progress)
  72. [ 5963.247125] BcmFileDownload:Opened file is = /lib/firmware/macxvi200.bin and length =0x2084a0 to be downloaded at =0xbfc00000
  73. [ 5963.247135] BcmFileDownload:download start 84c96d93InterfaceFileDownload:Got end of file!
  74. [ 5963.825479] InterfaceFileReadbackFromChip:Got end of file!<6>[ 5963.842666] usbcore: registered new interface driver usbbcm <--------- here is the active driver!!!!!!
  75. [ 5963.910336] beceem eth1: enabling interface
  76. [ 5963.911138] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
  77. [ 5963.916215] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
  78. peter@pjj:~$
  79.  
  80. comment:
  81.  
  82. of course not. I have not set up matters and need to activate 4g Virgin Mobile for a day.
  83.  
  84.  
  85. ifconfig -a
  86.  
  87. eth1 Link encap:Ethernet HWaddr f4:63:49:XX:XX:XX
  88. UP BROADCAST NOARP MULTICAST MTU:1400 Metric:1
  89. RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  90. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  91. collisions:0 txqueuelen:5
  92. RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  93.  
  94.  
  95. sudo ifconfig eth1 down
  96.  
  97. sudo ifconfig eth1 192.168.1.1 up
  98.  
  99.  
  100.  
  101. ifconfig eth1
  102. eth1 Link encap:Ethernet HWaddr f4:63:49:xx:xx:xx
  103. inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
  104. UP BROADCAST NOARP MULTICAST MTU:1400 Metric:1
  105. RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  106. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  107. collisions:0 txqueuelen:5
  108. RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  109.  
  110. Now a new connection 'wired ethernet' is shown by Network Manager <----------
  111.  
  112.  
  113. sudo wimaxd -D -c /etc/wimaxd.conf
  114.  
  115. wimaxc -i
  116.  
  117. both start;
  118.  
  119. Wimaxd error:
  120.  
  121.  
  122. sudo wimaxd -D -c /etc/wimaxd.conf
  123. ********** CSCM Server Started ********** 10/04/13 11:54:21
  124.  
  125. Processing configuration file
  126. =============================
  127. Reading CM Server options file '/etc/wimaxd.conf'
  128. Unknown option name: 'Bandwidth' <----------- taken from Windows modem.ini
  129. Unknown option name: 'CenterFrequency' <---------- taken from Windows modem.ini
  130. ERROR: No value given for option '545000,2647000,2657000,2667000,2499000,2505250,2510250,2515250,2521750,2526750,2531750,2538250,2543250,2548250,2554750,2559750,2564750,2621000,2627250,2632250,2637250,2643750,2648750,2653750,2660250,2665250,2670250,2676750,2681750,2686750,2578000,2584000,2590000,2596000,2602000,2608000,2575000,2581000,2587000,2593000,2599000,2605000,2611000'
  131. 3 errors found while reading options file.
  132.  
  133.  
  134. Option Values In Effect
  135. =======================
  136.  
  137. BandwidthMHz <Not Set>
  138. ScanMinFrequencyMHz 0.000
  139. ScanMaxFrequencyMHz 0.000
  140. ScanStepFrequencyMHz 0.000
  141. CenterFrequencyMHz <Not Set>
  142.  
  143.  
  144.  
  145.  
  146. Modified wimaxd.conf file to restore old settings.
  147. Windows option names are not recognized. Original windows is: wimax_bandwidth and wimax_centerfrequency.
  148.  
  149. Reverting back to old linux terminology file resulted in:
  150.  
  151. sudo wimaxd -D -c /etc/wimaxd.conf
  152.  
  153. wimaxc -i
  154.  
  155. both start;
  156.  
  157.  
  158. wimaxd output (truncated):
  159.  
  160. Option Values In Effect
  161. =======================
  162.  
  163. BandwidthMHz 5.000 10.000
  164. ScanMinFrequencyMHz 0.000
  165. ScanMaxFrequencyMHz 0.000
  166. ScanStepFrequencyMHz 0.000
  167. CenterFrequencyMHz 2499.000 2505.250 2508.500 2510.250 2515.250 2518.500 2521.750 2525.000 2526.750 2528.500 2531.750
  168. 2535.000 2538.250 2541.500 2543.250 2545.000 2548.250 2551.500 2554.750 2559.750 2561.500
  169. 2564.750 2575.000 2578.000 2581.000 2584.000 2587.000 2590.000 2593.000 2596.000 2599.000
  170. 2602.000 2605.000 2608.000 2611.000 2621.000 2627.250 2630.500 2632.250 2637.250 2640.500
  171. 2643.750 2647.000 2648.750 2650.500 2653.750 2657.000 2660.250 2663.500 2665.250 2667.000
  172. 2670.250 2673.500 2676.750 2681.750 2683.500 2686.750
  173.  
  174.  
  175. . . .
  176. Message queue initialized.
  177. Process messages thread started successfully.
  178. Changed state to: Library initialized
  179. Timer Periodic Action thread has started.
  180. Timer Check Timeouts thread has started.
  181. Timer Authentication thread has started.
  182. Process Messages thread has started.
  183. Changed state to: Waiting for WiMAX adapter ...
  184. Trying to open device.
  185. Device opened successfully. <--------------------
  186. Registering callback function - Success. <--------------------
  187. Changed state to: WiMAX adapter initialized <-------------------
  188. . . .
  189. ***** Sending subscriber station information request
  190. Sent: 07 00 01 00
  191.  
  192. =============== Received Message Start (2013/09/04 12:10:24.008) ===========
  193. u32State = WiMAX adapter initialized
  194. SS info response received (Type = 7 - Subtype = 1 - Length = 184)
  195. INFO: No socket in BeceemAPI_Unlock()
  196. Client socket FFFFFFFF unlock Beceem API: Was not locked (this is not an error)
  197. Found valid library version: 6.0.37
  198. =============== Received Message End (type=7 sub-type=1) ===============
  199. ***** Message sent successfully
  200. Changed state to: Waiting for WiMAX adapter ...
  201.  
  202. ***** Sending idle mode status request (2013/09/04 12:10:24.200)
  203. Sent: 13 00 02 00
  204. ***** Message sent successfully
  205.  
  206. ***** Sending shutdown status request (2013/09/04 12:10:24.201)
  207. Sent: 1E 00 05 00
  208. ***** Message sent successfully
  209.  
  210. ***** Sending half-mini card status request (2013/09/04 12:10:24.201)
  211. Sent: 24 00 01 00
  212. ***** Message sent successfully
  213.  
  214. ***** Sending link status request (2013/09/04 12:10:24.201)
  215. Sent: 02 00 03 00
  216. ***** Message sent successfully
  217.  
  218. =============== Received Message Start (2013/09/04 12:10:24.201) ===========
  219. u32State = Waiting for WiMAX adapter ...
  220. Idle mode response received (Type = 19 - Subtype = 2 - Length = 8)
  221. Idle mode response length = 8
  222. Changed state to: Waiting for WiMAX adapter ...
  223. Not in idle mode.
  224. =============== Received Message End (type=19 sub-type=2) ===============
  225.  
  226. =============== Received Message Start (2013/09/04 12:10:24.201) ===========
  227. u32State = Waiting for WiMAX adapter ...
  228. Shutdown response received (Type = 30 - Subtype = 5 - Length = 8)
  229. SUBTYPE_SHUTDOWN_MODE_STATUS_RESP return value = 00000001
  230. Changed state to: Waiting for WiMAX adapter ...
  231. =============== Received Message End (type=30 sub-type=5) ===============
  232.  
  233. . . .
  234.  
  235.  
  236. = Received Message Start (2013/09/04 12:10:24.201) ===========
  237. u32State = Waiting for WiMAX adapter ...
  238. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  239. Network Entry Status Received
  240. Link status = WAIT FOR PHY SYNC CMD
  241. Changed state to: Waiting for PHY sync start
  242. =============== Received Message End (type=2 sub-type=2) ===============
  243.  
  244. =============== Received Message Start (2013/09/04 12:10:24.210) ===========
  245. u32State = Waiting for PHY sync start
  246. Half-mini card response received (Type = 36 - Subtype = 3 - Length = 4)
  247. Changed state to: Half-mini Card Device is not shut down
  248. =============== Received Message End (type=36 sub-type=3) ===============
  249.  
  250. ***** Sending link status request (2013/09/04 12:10:28.206)
  251. Sent: 02 00 03 00
  252. ***** Message sent successfully
  253.  
  254. =============== Received Message Start (2013/09/04 12:10:28.207) ===========
  255. u32State = Half-mini Card Device is not shut down
  256. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  257. Network Entry Status Received
  258. Link status = WAIT FOR PHY SYNC CMD
  259. Changed state to: Waiting for PHY sync start
  260. =============== Received Message End (type=2 sub-type=2) ===============
  261. Got connection 1 from 127.0.0.1 <-------------------
  262. Wcm connection handling thread launched successfully
  263. Socket is 00000006
  264. Client socket 00000006 lock Beceem API: SUCCESS (wait = 0 ms)
  265. Client socket 00000006 unlock Beceem API: Success <---------
  266.  
  267. ***** Sending link status request (2013/09/04 12:10:32.311)
  268. Sent: 02 00 03 00
  269.  
  270. . . .
  271.  
  272.  
  273. =============== Received Message Start (2013/09/04 12:10:36.416) ===========
  274. u32State = Waiting for PHY sync start
  275. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  276. Network Entry Status Received
  277. Link status = WAIT FOR PHY SYNC CMD
  278. =============== Received Message End (type=2 sub-type=2) ===============
  279. ***** Message sent successfully
  280. Received 7 bytes:
  281.  
  282. 0000: 73 65 61 72 63 68 00
  283. Executing command 'search'
  284. Client socket 00000006 lock Beceem API: SUCCESS (wait = 0 ms)
  285.  
  286. ***** Sending PHY sync down request
  287. Sent: 03 00 01 00
  288. ***** Message sent successfully
  289. Changed state to: Sync down request sent
  290.  
  291. =============== Received Message Start (2013/09/04 12:10:36.725) ===========
  292. u32State = Sync down request sent
  293. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  294. Network Entry Status Received
  295. Link status = HOST INITIATED SYNC DOWN <-----------------
  296. Changed state to: Connection error <-----------------
  297.  
  298.  
  299. . . .
  300.  
  301.  
  302. Search CF: 2499000 2505250 2508500 2510250 2515250 2518500 2521750 2525000 2526750 2528500 2531750 2535000 2538250 2541500 2543250 2545000 2548250 2551500 2554750 2559750 2561500 2564750 2575000 2578000 2581000 2584000 2587000 2590000 2593000 2596000 2599000 2602000 2605000 2608000 2611000 2621000 2627250 2630500 2632250 2637250 2640500 2643750 2647000 2648750 2650500 2653750 2657000 2660250 2663500 2665250 2667000 2670250 2673500 2676750 2681750 2683500 2686750
  303.  
  304. ***** Sending network search request (2013/09/04 12:10:36.726)
  305. Sent: 01 00 01 00 00 00 00 00 02 00 00 00 02 00 00 00 88 13 00 00 10 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 39 00 00 00 B8 21 26 00 22 3A 26 00 D4 46 26 00 AA 4D 26 00 32 61 26 00 E4 6D 26 00 96 7A 26 00 48 87 26 00 1E 8E 26 00 F4 94 26 00 A6 A1 26 00 58 AE 26 00 0A BB 26 00 BC C7 26 00 92 CE 26 00 68 D5 26 00 1A E2 26 00 CC EE 26 00 7E FB 26 00 06 0F 27 00 DC 15 27 00 8E 22 27 00 98 4A 27 00 50 56 27 00 08 62 27 00 C0 6D 27 00 78 79 27 00 30 85 27 00 E8 90 27 00 A0 9C 27 00 58 A8 27 00 10 B4 27 00 C8 BF 27 00 80 CB 27 00 38 D7 27 00 48 FE 27 00 B2 16 28 00 64 23 28 00 3A 2A 28 00 C2 3D 28 00 74 4A 28 00 26 57 28 00 D8 63 28 00 AE 6A 28 00 84 71 28 00 36 7E 28 00 E8 8A 28 00 9A 97 28 00 4C A4 28 00 22 AB 28 00 F8 B1 28 00 AA BE 28 00 5C CB 28 00 0E D8 28 00 96 EB 28 00 6C F2 28 00 1E FF 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . . . . (code truncated)
  306. ***** Message sent successfully
  307. =============== Received Message End (type=2 sub-type=2) ===============
  308.  
  309. =============== Received Message Start (2013/09/04 12:10:36.785) ===========
  310. u32State = Connection error
  311. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  312. Device status indication: Device is scanning <-----------Woooohhhhooooooo!!
  313. =============== Received Message End (type=2 sub-type=5) ===============
  314.  
  315. ***** Sending link status request (2013/09/04 12:10:40.533)
  316. Sent: 02 00 03 00
  317. ***** Message sent successfully
  318.  
  319. =============== Received Message Start (2013/09/04 12:10:40.535) ===========
  320. u32State = Connection error
  321. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  322. Network Entry Status Received
  323. Link status = WAIT FOR PHY SYNC CMD
  324. Changed state to: Waiting for PHY sync start
  325. =============== Received Message End (type=2 sub-type=2) ===============
  326.  
  327. . . .
  328.  
  329. =============== Received Message Start (2013/09/04 12:10:46.211) ===========
  330. u32State = Waiting for PHY sync start
  331. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  332. Device status indication: Device is ready <------------------------
  333. =============== Received Message End (type=2 sub-type=5) ===============
  334.  
  335. =============== Received Message Start (2013/09/04 12:10:46.213) ===========
  336. u32State = Waiting for PHY sync start
  337. Network search response received (Type = 1 - Subtype = 1 - Length = 12)
  338.  
  339. 0 base stations found. <------------------
  340.  
  341. -- Network Search status: Network search complete
  342. Changed state to: Network Search completed
  343. Changed state to: Waiting for PHY sync start
  344. =============== Received Message End (type=1 sub-type=1) ===============
  345. DEBUG: ServerSocketResponse for ID=20 Text chars=41: Network search returned 0 base stations. <-------------
  346.  
  347. Client socket 00000006 unlock Beceem API: Success
  348.  
  349. ***** Sending link status request (2013/09/04 12:10:48.758)
  350. Sent: 02 00 03 00
  351. ***** Message sent successfully
  352.  
  353. =============== Received Message Start (2013/09/04 12:10:48.758) ===========
  354. u32State = Waiting for PHY sync start
  355. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  356. Network Entry Status Received
  357. Link status = WAIT FOR PHY SYNC CMD
  358. =============== Received Message End (type=2 sub-type=2) ===============
  359.  
  360. Closing wimaxc -i. Code output:
  361.  
  362. ^CTerminating Authentication Timer thread.
  363. Terminating Check Timeouts Timer thread.
  364. Timer Check Timeouts thread has finished.
  365. Terminating Periodic Action Timer thread.
  366. Closing device.
  367.  
  368. So far the driver bcm_wimax is working just fine. Now it is up to me to activate a day of VM 4G and to find a location with good coverage.
  369. If this dirver really works, then it would be unneccessary to go through the trouble of compiling drxvi314.ko to new kernel versions.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!