API tools faq
paste
Advertisement
pjj90292

Wimax driver module bcm_wimax and drxvi314.ko

pjj90292
Aug 2nd, 2013
361
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 22.21 KB | None | 0 0
raw download clone embed print report
  1. Title:
  2. Attempting to re-compile driver module bcm_wimax to linux kernel 3.8.0-27-generic (Kubuntu 13.04).
  3.  
  4. #pjj90292
  5. #Following is a record of my efforts to compile a working bcm_wimax driver to my latest linux kernel #3.8.0-27-generic by using the data from linux kernel 3.0.
  6. #This is to test whether bcm_wimax driver that comes with the kernel has indeed a retrogression that #prevents it from working.
  7. #I am using the built-in driver on Kubuntu 13.04 with a Franklin U600 modem on the Virgin #Mobile/Sprint Wimax network.
  8. #This modem is a dual modem. It has a 3G CDMA network (known as "EV-DO" or "Evolution Data #Optimized") modem that works fine and is easy to manage with the Linux Network Manager.
  9. #The tricky part is the 4G Wimax modem designed to work on the Sprint Wimax network.
  10. #Kubuntu comes with a built-in wimax driver for the Sprint 4G network called bcm_wimax. this driver #is a kernel module in most linux distributions. Problem is that the driver is said to work only with #kernel 2.6 and later; 2.6 Mint and 12.04 are just two of the versions that come with a working #bcm_driver or can be made to use the 'native' Windows driver drxvi314.ko in its Linux incarnation. #Rumor has it that this driver is no longer working with the latest versions: "The drxvi314 driver #won't compile in modern kernels without extensive modification, as the driver API has changed.. ." #Quoted from "Sprint 4G on Ubuntu 11.04+ with a Sierra 250U modem. . ." previously posted by #another poster on Pastebin.
  11.  
  12. #To compile the driver module to the 13.04 kernel I followed the instructions received from Matthew #Middleton who has helped me greatly and inspired my attempts to get the 4G modem of U600 to #work on my Kubuntu installations.
  13. #I removed all existing versions of the driver module bcm_wimax in their respective locations by #renaming the file before I started to re-compile the module according to some instructions I had
  14. #received a long time ago from Matthew Middleton, a poster on pastebin.
  15.  
  16.  
  17. I am quoting the relevant parts of these instructions here in order for you to see the procedures used and the results to be expected.
  18.  
  19. ". . . Try this much simpler method, which I e-mailed you previously. You should be using the linux-3.0 source code to build the driver. (i.e. this file: https://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.bz2)
  20.  
  21. 1. Get into the driver's folder. (i.e. cd linux-3.0/drivers/staging/bcm)
  22. 2. Edit Makefile (use vim, nano, gedit, or your favorite editor) by adding 5 lines to the file, as follows: (I and II)
  23. I. Add this at the top: KVERSION = $(shell uname -r)
  24. II. Add the following 4 lines to the bottom:
  25.  
  26. all:
  27. make -C /lib/modules/$(KVERSION)/build M=$(PWD) modules
  28. clean:
  29. make -C /lib/modules/$(KVERSION)/build M=$(PWD) clean
  30.  
  31.  
  32. 3. Type make, and it will build in less than 30 seconds.
  33. 4. Since you're in the path with the module, simply type sudo insmod bcm_wimax.ko
  34.  
  35.  
  36. 5. Use lsmod to verify that the driver is in the kernel. Do dmesg | tail to see what messages the driver generated.
  37. 6. rm any older builds of bcm_wimax.ko, so you don't get confused, and so that a broken driver isn't loaded by mistake.
  38. 7. Add the command to insmod this driver to the top of your wimax connect script. It shouldn't be loaded automatically, as that can prevent the 3G modem from working."
  39.  
  40.  
  41. See the contents of the driver's folder (Linux 3.0):
  42.  
  43.  
  44. root@pjj:/usr/src/linux-3.0/drivers/staging/bcm# ls
  45. Adapter.h InterfaceDld.c Ioctl.h PHSModule.h
  46. Bcmchar.c InterfaceIdleMode.c IPv6Protocol.c Protocol.h
  47. Bcmnet.c InterfaceIdleMode.h IPv6ProtocolHdr.h Prototypes.h
  48. CmHost.c InterfaceInit.c Kconfig Qos.c
  49. CmHost.h InterfaceInit.h LeakyBucket.c Queue.h
  50. cntrl_SignalingInterface.h InterfaceIsr.c led_control.c sort.c
  51. DDRInit.c InterfaceIsr.h led_control.h target_params.h
  52. DDRInit.h InterfaceMacros.h Macros.h TODO
  53. Debug.h InterfaceMisc.c Makefile Transmit.c
  54. HandleControlPacket.c InterfaceMisc.h Misc.c Typedefs.h
  55. headers.h InterfaceRx.c nvm.c vendorspecificextn.c
  56. hostmibs.c InterfaceRx.h nvm.h vendorspecificextn.h
  57. HostMIBSInterface.h InterfaceTx.c PHSDefines.h Version.h
  58. InterfaceAdapter.h InterfaceTx.h PHSModule.c
  59.  
  60. Next step: Edit Makefile
  61. according to the above instructions. Modifications added to file.
  62.  
  63. Next step: Make
  64.  
  65. root@pjj:/usr/src/linux-3.0/drivers/staging/bcm# make
  66. make -C /lib/modules/3.8.0-27-generic/build M=/usr/src/linux-3.0/drivers/staging/bcm modules
  67. make[1]: Entering directory `/usr/src/linux-headers-3.8.0-27-generic'
  68. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceDld.o
  69. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceIdleMode.o
  70. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceInit.o
  71. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceRx.o
  72. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceIsr.o
  73. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceMisc.o
  74. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/InterfaceTx.o
  75. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/CmHost.o
  76. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/IPv6Protocol.o
  77. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/Qos.o
  78. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/Transmit.o
  79. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/Bcmnet.o
  80. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/DDRInit.o
  81. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/HandleControlPacket.o
  82. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/LeakyBucket.o
  83. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/Misc.o
  84. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/sort.o
  85. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/Bcmchar.o
  86. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/hostmibs.o
  87. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/PHSModule.o
  88. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/led_control.o
  89. /usr/src/linux-3.0/drivers/staging/bcm/led_control.c: In function ‘LEDControlThread’:
  90. /usr/src/linux-3.0/drivers/staging/bcm/led_control.c:789:4: warning: case value ‘255’ not in enumerated type ‘LedEventInfo_t’ [-Wswitch]
  91. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/nvm.o
  92. CC [M] /usr/src/linux-3.0/drivers/staging/bcm/vendorspecificextn.o
  93. LD [M] /usr/src/linux-3.0/drivers/staging/bcm/bcm_wimax.o
  94. Building modules, stage 2.
  95. MODPOST 1 modules
  96. CC /usr/src/linux-3.0/drivers/staging/bcm/bcm_wimax.mod.o
  97. LD [M] /usr/src/linux-3.0/drivers/staging/bcm/bcm_wimax.ko
  98. make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-27-generic'
  99. root@pjj:/usr/src/linux-3.0/drivers/staging/bcm#
  100.  
  101. Looks like the 'make' process completed successfully. A driver 'bcm_wimax' is now present in the above folder dated August 1, 2013.
  102.  
  103.  
  104.  
  105. Next:
  106. "Since you're in the path with the module, simply type sudo insmod bcm_wimax.ko"
  107.  
  108. Result:
  109.  
  110. root@pjj:/lib/modules/3.8.0-27-generic/kernel/drivers/staging/bcm# sudo insmod bcm_wimax.ko
  111.  
  112. Error: could not load module bcm_wimax.ko: No such file or directory
  113.  
  114.  
  115. Modified driver is in linux-3.0!!
  116.  
  117. Copied modified driver from linux-3.0 compiled with 3.8.0 to
  118. /lib/modules in linux-3.8.0-27-generic.
  119.  
  120. root@pjj:/lib/modules/3.8.0-27-generic# ls -a -l
  121. total 3756
  122. drwxr-xr-x 5 root root 4096 Aug 1 15:22 .
  123. drwxr-xr-x 6 root root 4096 Jul 29 12:54 ..
  124. -rw-r--r-- 1 root root 290924 Aug 1 15:02 bcm_wimax.ko
  125. . . .
  126.  
  127. Then:
  128. insmod bcm_wimax.ko
  129.  
  130. result:
  131.  
  132. root@pjj:/lib/modules/3.8.0-27-generic# lsmod
  133. Module Size Used by
  134. bcm_wimax 234833 0
  135. . . .
  136.  
  137. Checking dmesg:
  138.  
  139. dmesg |tail -40
  140.  
  141. "root@pjj:/lib/modules/3.8.0-27-generic# dmesg |tail -40
  142. [ 4975.277103] usb 1-4.1: SerialNumber: SCG900. . . (correct number given)
  143. [ 4975.278718] usbbcm_device_probe:subtype[1] = 0x000000ff
  144. [ 4975.278726] usbbcm_device_probe:subtype[2] = 0x00000000
  145. [ 4975.278730] usbbcm_device_probe:subtype[4] = 0x00000000
  146. [ 4975.278734] usbbcm_device_probe:subtype[8] = 0x00000000
  147. [ 4975.278739] InitAdapter:Initialising Adapter = f3ae0500
  148. [ 4975.278799] InitAdapter:Adapter initialised<7>[ 4975.278809] usbbcm_device_probe:psIntfAdapter 0xf15b9000
  149. [ 4975.278979] usb 1-4.1: RDM Chip ID 0xbece3301
  150. [ 4975.286513] beceem: AutoSyncup is Disabled
  151. [ 4975.286521] beceem: Disabling autolink up
  152. [ 4975.286525] beceem: DDR Setting: 3
  153. [ 4975.286529] beceem: Power Save Mode: 0
  154. [ 4975.286532] beceem: Enabling Auto Firmware Download
  155. [ 4975.286536] beceem: MIPSConfig : 0x0
  156. [ 4975.286539] beceem: PMU MODE: 0
  157. [ 4975.286542] beceem: uiEEPROMFlag : 0x2
  158. [ 4975.287082] reset_card_proc:Resetting UMA-B
  159. [ 4975.360217] usb 1-4.1: reset high-speed USB device number 6 using ehci-pci
  160. [ 4975.474163] ddr_init:Register Count is =48
  161. [ 4975.497521] usbbcm 1-4.1:1.0: beceem eth1: register usb-0000:00:1d.7-4.1 f (MAC ID) correct
  162. [ 4975.545924] BcmFileDownload:Opened file is = /lib/firmware/macxvi200.bin and length =0x2084a0 to be downloaded at =0xbfc00000
  163. [ 4975.545934] BcmFileDownload:download start 3baca7dfInterfaceFileDownload:Got end of file!
  164. [ 4976.151804] InterfaceFileReadbackFromChip:Got end of file!<6>[ 4976.402414] beceem eth1: enabling interface
  165. [ 4976.403213] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
  166. [ 4976.409431] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
  167. [ 9364.485728] usbcore: deregistering interface driver usbbcm
  168. [ 9364.488386] InterfaceRDM:Device got removed
  169. [ 9364.488392] InterfaceRDM:Device got removedInterfaceWRM:Device got removed
  170. [ 9364.488406] InterfaceWRM:Device got removed<6>[ 9364.488503] reset_card_proc:Resetting UMA-B
  171. [ 9364.560157] usb 1-4.1: reset high-speed USB device number 6 using ehci-pci
  172. [ 9364.652642] InterfaceRDM:Device got removed by me!!
  173. [ 9364.652652] reset_card_proc:read failed with status :-19<5>[ 9364.652748] beceem eth1: protocol reset
  174. [ 9364.652900] usbbcm 1-4.1:1.0: beceem eth1: unregister usb-0000:00:1d.74.1
  175. [ 9364.652926] beceem eth1: disabling interface
  176. [ 9626.468944] usb 1-4: USB disconnect, device number 3
  177. [ 9626.468954] usb 1-4.1: USB disconnect, device number 6
  178. [ 9626.473486] usb 1-4.2: USB disconnect, device number 5
  179.  
  180. #The above information refers to status prior to removal of USB device and insmod of modified driver bcm_wimax.
  181.  
  182. #New, with device reinserted:
  183.  
  184. [10283.026048] beceem: Beceem Communications Inc. WiMAX driver, 5.2.45
  185. [10283.026058] Copyright 2010. Beceem Communications Inc
  186. [10283.034756] usbcore: registered new interface driver usbbcm"
  187.  
  188. usbbcm is the driver that is to be expected with the 4G modem active in Linux.
  189. Modem should now light up on 4G side.
  190. It does not.
  191.  
  192. lsmod
  193. bcm_wimax 234833 0
  194.  
  195. lsusb
  196. . . .
  197. Bus 001 Device 005: ID 1fac:0151
  198. 3G modem shown, no 4G!
  199.  
  200. usb-devices:
  201. . . .
  202. T: Bus=01 Lev=02 Prnt=07 Port=01 Cnt=01 Dev#= 9 Spd=12 MxCh= 0
  203. D: Ver= 1.10 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
  204. P: Vendor=1fac ProdID=0151 Rev=00.00
  205. S: Manufacturer=Franklin Wireless Corp.
  206. S: Product=U600 EVDO Modem
  207. C: #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=500mA
  208. I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
  209. I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
  210. I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  211. I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  212. I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  213. I: If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  214. . . .
  215. Following instructions on how to turn on the 4G (Beceem) modem published in Ubuntu Forum I do:
  216.  
  217. picocom /dev/ttyACM0 -b115200 -l -r
  218.  
  219. to start communication with the modem port.
  220. Result:
  221.  
  222. peter@pjj:~$ picocom /dev/ttyACM0 -b115200 -l -r
  223. picocom v1.7
  224.  
  225. “port is : /dev/ttyACM0
  226. flowcontrol : none
  227. baudrate is : 115200
  228. parity is : none
  229. databits are : 8
  230. escape is : C-a
  231. local echo is : no
  232. noinit is : no
  233. noreset is : yes
  234. nolock is : yes
  235. send_cmd is : sz -vv
  236. receive_cmd is : rz -vv
  237. imap is :
  238. omap is :
  239. emap is : crcrlf,delbs,
  240.  
  241. Terminal ready
  242.  
  243. OK”
  244.  
  245. Then enter:
  246. AT+4GMODE=2.
  247.  
  248. “OK”
  249.  
  250. 4G modem powers on, red light on.
  251.  
  252.  
  253. Test:
  254. lsusb
  255.  
  256. root@pjj:/lib/modules/3.8.0-27-generic# lsusb
  257. Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
  258. Bus 002 Device 002: ID 047d:102d Kensington Pilot Optical
  259. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  260. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  261. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  262. Bus 001 Device 010: ID 198f:0220 Beceem Communications Inc. BCSM250 WiMAX Adapter
  263. Bus 001 Device 009: ID 1fac:0151
  264.  
  265. Test:
  266. usb-devices:
  267.  
  268.  
  269. T: Bus=01 Lev=02 Prnt=07 Port=00 Cnt=01 Dev#= 10 Spd=480 MxCh= 0
  270. D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
  271. P: Vendor=198f ProdID=0220 Rev=00.01
  272. S: Manufacturer=Beceem Communications
  273. S: Product=BCSM250 Mobile WiMAX
  274. S: SerialNumber=SCG900. . .
  275. C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
  276. I: If#= 0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbbcm
  277.  
  278.  
  279. According to Sprint Instructions ethernet should be showing.
  280.  
  281. Next test:
  282. ifconfig -a
  283.  
  284. Results in:
  285. eth1 Link encap:Ethernet HWaddr (fMAC address shown)
  286. UP BROADCAST NOARP MULTICAST MTU:1400 Metric:1
  287. RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  288. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  289. collisions:0 txqueuelen:5
  290. RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  291. . . .
  292. eth1 a new 'wired connection' that represents the 4G modem.
  293.  
  294. Therefore:
  295.  
  296. Starting CSSM wimax server:
  297.  
  298. wimaxd -D /etc/wimaxd.conf
  299.  
  300. "root@pjj:/lib/modules/3.8.0-27-generic# wimaxd -D /etc/wimaxd.conf
  301. ********** CSCM Server Started ********** 08/01/13 15:44:24"
  302. (. . . Processing configuration file
  303. =============================
  304. “Reading CM Server options file '/etc/wimaxd.conf'
  305. ERROR: No value given for option '3'
  306. ERROR: No value given for option '3'
  307. ERROR: No value given for option '3'
  308. ERROR: No value given for option '3'
  309. ERROR: No value given for option '3'
  310. 5 errors found while reading options file.”
  311.  
  312.  
  313. I have not yet been able to determine what the errors above refer to!
  314.  
  315.  
  316. Finally:
  317.  
  318. peter@pjj:~$ wimaxc -i
  319.  
  320. It gives the expected result as quoted in Sprint Mobile Broadband 4G Setup Guide:
  321.  
  322. peter@pjj:~$ wimaxc -i
  323. Beceem CM Server Version 1.1.7.0
  324.  
  325. >
  326.  
  327. Sprint instructions:
  328.  
  329. > search
  330. Result, sample only according to Sprint:
  331.  
  332. “Network search returned 1 base station.
  333. Idx BSID
  334. Pre
  335. Freq
  336. BW RSSI CINR
  337. 0 01:01:00:00:02:3d:58:59 0x40 2647.000 10.000 -84 11
  338. >”
  339.  
  340. My result:
  341.  
  342. > search
  343. Beceem WiMAX device is NOT present
  344. >
  345.  
  346. End of story.
  347.  
  348. No 4G connection
  349.  
  350. The identical result is also arrived at with the bult-in wimax module. It can therfore be concluded that the current bcm_wimax driver is working.
  351. Something else must still be wrong in my 4G modem setup.
  352.  
  353. I have attempted to contact the author of a post in the Ubuntu Forum who discovered the above way of turniing power on to the U600 4G modem. He is successfully using the modem with Kubuntu/Ubuntu 12.04. Because of the hacked forum I have not received a response yet.
  354.  
  355. It is also noteworthy that Network Manager detects the U600 broadband modem as a 'wired connection' as soon as the 4G part is manually powered on as described above.
  356. I assume that the connection would work if I could complete several files correctly (mainly wimaxd.conf) and fill in the correct parameters on the NM menu 802.1x security.
  357. The security parameters are mostly part of the wimaxd.conf file.
  358. I am only uncertain about two of them.
  359.  
  360. My question in this regard is whether it is at all necessary for a connection to have the wimaxd.conf file. After all, authentication and identification of the modem for a working connection are due to the
  361. parameters shown in the Network Manager pulldown menue for security.
  362.  
  363.  
  364. My next step:
  365.  
  366. I have several options.
  367. I will let the above path simmer for a while. Maybe someone comes up with an idea or I can get in touch with the author of the post on the Ubuntu Forum.
  368. It appears that even when 4G is activated and powered on another step is required to make wimax operative. There is a python script that achieves this, It was published on pastebin. Unfortunately, U600 does not work with CNS but rather requires something like Qim (or so). It supposedly comes with kubuntu. But I am totally unfamiliar with it and could not write a script even if I found the app and understood the language.
  369.  
  370. Alternatively, I will one more time attempt to follow the directions in the Sprint Mobile Broadband 4G Setup guide and related instructions in order to compile the Linux module of drxvi314.ko to the Linux kernel. It is said to work no longer , but we will have to test that.
  371. My previous compilation attempts have all failed with several errors – except once when I successfully got the driver – but it did not work either.
  372.  
  373. PJJ
  374. 08/02/13
  375.  
  376.  
  377.  
  378.  
  379.  
  380.  
  381.  
  382.  
  383. PART II
  384. Wimax driver module for Kubuntu 13.04. Compilation.
  385.  
  386.  
  387. #Blacklisted bcm_wimax driver because it apparently does not work for 13.04 or my particular se1305tup.
  388. Activated and insmod drxvi314.ko (for kernel 3.8.0-19 located at /lib/modules/3.8.0-19-generic/drxvi314.ko).
  389.  
  390. insmod successful.
  391.  
  392. lsusb:
  393. Bus 001 Device 013: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
  394. Bus 002 Device 002: ID 047d:102d Kensington Pilot Optical
  395. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  396. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  397. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  398. Bus 001 Device 016: ID 198f:0220 Beceem Communications Inc. BCSM250 WiMAX Adapter <------
  399. Bus 001 Device 015: ID 1fac:0151
  400.  
  401.  
  402. usb-devices
  403. T: Bus=01 Lev=02 Prnt=13 Port=00 Cnt=01 Dev#= 16 Spd=480 MxCh= 0
  404. D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
  405. P: Vendor=198f ProdID=0220 Rev=00.01
  406. S: Manufacturer=Beceem Communications <------
  407. S: Product=BCSM250 Mobile WiMAX
  408. S: SerialNumber=SCG900xxxx
  409. C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
  410. I: If#= 0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbbcm
  411.  
  412. lsmod
  413. . . .
  414. qcaux 12529 1
  415. usbserial 27423 3 qcaux
  416. drxvi314 309219 2 <------
  417. usb_storage . . .
  418.  
  419. ifconfig -a
  420. eth1 Link encap:Ethernet HWaddr f4:63:49:x.x.x
  421. inet6 addr: fe80::f663:49ff:fe07:279d/64 Scope:Link <------ note the inet address
  422. UP BROADCAST MULTICAST MTU:1400 Metric:1
  423. RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  424. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  425. collisions:0 txqueuelen:1000
  426. RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  427. #The inet addr. was missing before though I got eth1 info back
  428.  
  429. #Before:
  430. #ifconfig -a eth1
  431. #eth1 Link encap:Ethernet HWaddr f4:63:49:06:XX:XX
  432. # BROADCAST MULTICAST MTU:1400 Metric:1 <---- no inet!
  433. # RX packets:625 errors:0 dropped:0 overruns:0 frame:0
  434. # TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  435. # collisions:0 txqueuelen:1000
  436. # RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  437.  
  438. #to be sure one more; sudo ifconfig eth1 up
  439. #then:
  440. ifconfig -a eth1:
  441.  
  442. eth1 Link encap:Ethernet HWaddr f4:63:49:x.x.x
  443. inet6 addr: fe80::f663:49ff:fe07:279d/64 Scope:Link <------
  444. UP BROADCAST MULTICAST MTU:1400 Metric:1
  445. RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  446. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  447. collisions:0 txqueuelen:1000
  448. RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  449.  
  450. #Start CSCM server
  451. peter@pjj:~$ sudo wimaxd -c /etc/wimaxd.conf
  452. ********** CSCM Server Started ********** 08/05/13 11:47:22
  453.  
  454. #Start daemon
  455. peter@pjj:~$ wimaxc -i
  456. Beceem CM Server Version 1.1.7.0
  457.  
  458. > search . . . . . . . . . .
  459.  
  460. Result:
  461. Network search returned 0 base stations. <---- at least it searched and did not give an error right away.
  462.  
  463. # At this point I have a steady green light on the modem for the 3G part. Modem connects to Virgin Mobile with 3G speeds.
  464. #I also have (and have had for a while) the steady red light that indicates power to the 4G Beceem modem.
  465. #As indicated in above the 4G modem is detected, modprobe/insmod loads it.
  466.  
  467. modinfo /lib/modules/3.8.0-19-generic/drxvi314.ko
  468. filename: /lib/modules/3.8.0-19-generic/drxvi314.ko
  469. license: GPL
  470. srcversion: DDCD6B882544594F3C89900
  471. depends:
  472. vermagic: 3.8.0-19-generic SMP mod_unload modversions 686
  473.  
  474.  
  475. #Conclusion:
  476. #It looks like driver module drxvi314.ko for 3.8.0-19-generic does indeed work with the U600 modem despite reports from other sources that it does no longer.
  477. #I will next test whether the module drxvi314.ko for the latest kernel version 3.8.0-27-generic also works. It should since we are still in the same basic kernel version 0f 3.8.0.
  478.  
  479. I presume that the above result
  480. "Network search returned 0 base stations"
  481. simply means that there is no wimax signal at my present location.
  482. I am sure of that because Windows also can not connect under Windows at this location.
  483. Using my external antenna might change that.
  484.  
  485. Consequently I will not recompile the drxvi314.ko module to 3.8.0-27-generic until i have tested today's setup with the antenna attached or from a location with a proven wimax signal.
  486.  
  487. If it works, I will have to compile the drxvi314.ko module to the latest version of the kernel (though it should automatically be carried forward since dkms is in effect). In my case that is 3.10.0
  488.  
  489. This is as far as I ever managed to get with the U600 and Linux despite all the assistance received from other sources. Many roads lead to Rome. This might just be another one.
  490. The bcm_wimax driver has so far not worked for me. I blacklisted it as a consequence.
  491.  
  492. Finally:
  493. I am running a connection to the modem via picocom while doing my other manipulations. Picocom reports a very long series of 'OK' followed by '16,99',21,99' and 22,99. I do not know what this means.
  494. If anyone knows, would you please let me know?
  495. PJJ
  496. 08/06/12
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!