Stealth Wimax driver drvxi314.ko?

[PJJ]

The plot thickens.

What is it? A miracle or a mystery download?

Read all about it at

http://pastebin.com/PckqfPUF

[PJJ]

I noticed that and corrected it.
/lib/modules/3.8.0-29-generic/source points to 3.8.0-29-generic.

The module compiled to /temp. I moved it from there to lib/modules/3.8.02-29-generic.

Tested the driver yesterday. Results later today when I have more time.

Mystery:

While testing driver drxvi314.ko I noticed an interface 'pppo' that was transferring packet.
But I was in an area without any wireless. Only U600 plugged in for testing.

As you will see later on pastebin, I received a message that said xxxx packets transferred.
148 kb approx.
File name: maxcvi200.bin.

Where did that come from?

Earlier I had checked the modem with XP. Started to rest because it did not work. Reset never did anything - as far as I know.
Maybe that triggered the file download?

But HOW?
I was not on an active connection.

[paperplate9]

One thing I noticed in your log:

make -Wall O=/lib/modules/3.8.0-29-generic/build -C /lib/modules/[b]3.8.0-29-generic[/b]/source SUBDIRS=/tmp/kde-peter/ark4hkewN/drxvi314-source modules
make[1]: Entering directory `/usr/src/linux-headers-[b]3.8.0-26-generic[/b]'

make is going into the headers for 3.8.0-26. Can you show what /lib/modules/3.8.0-29-generic/source points to?

[PJJ]

After a failed attempt during which I tried to compile the module as root, I used 'make' as a regular user. The result?

drxvi314.ko in the temp directory.

Moved it to /lib/modules/3.8.0-29-generic.
-rw-r--r-- 1 root root 399703 Aug 31 11:43 drxvi314.ko

Only testing to be done.

I have posted the narrative of the compilation at

http://pastebin.com/20Rks2SH

[PJJ]

As I said I will do so as soon as I have done some house cleaning.
Meanwhile I am tampering with the bcm_wimax driver. Just for the heck of it.

No offense to you, paperplate9. I appreciate your contribution very much. They have made me come very, very close to succeed with the module drxvi314.ko.

Interestingly enough with kernel 3.8.0-29-generic and using the built-in driver module bcm_wimax (staging) I get almost identical results to module drxvi314.ko!
Network Manager even establishes a new 'wired connection' eth1.
It loads and uses the wimax driver usbbcm - just as drxvi314.ko.

Command line code results in messages that are identical to those for drxvi314.ko. - including the infamous "device NOT present".

The problem appears at least to some extend located in the device itself. Truncated file?

Furthermore:
Since error message declares 'interface' as undefined and IP address as 'no IP address" more work is needed here to set up the interface.
Could one of the interface experts please contribute some

wimaxd reports one small error in the file wimaxd.conf. Then gives messages identical to drxvi314.ko including "Trying to open device" in a loop.
Upon closing:

CTerminating Authentication Timer thread.
Timer Authentication thread has finished.
Terminating Check Timeouts Timer thread.
Terminating Periodic Action Timer thread.
Timer Periodic Action thread has finished.

Shutting down the Beceem API interface.
Terminating Process Messages thread.
Process Messages thread has exited
Freeing the Options Table.
Freeing other structures.
Closing EAP supplicant.
Closing Beceem WiMAX device.
Freeing message queue.
Freeing mutexes.
Freeing print context structures.
Beceem API interface has been shut down.


Fewer errors than on my last drxvi314.ko attempt.
For whatever it is worth.
But I will continue to work on the original driver module drxvi314.ko.

[paperplate9]

Thanks again for the reply.
I just did a quick unzip of the raw driver code to a sub-directory of my home directory. Then make, which gave the errors because 'file(s) could not be found.
I assume because the unzipped code was not in the correct directory.

You should be able to extract the zip anywhere. I even extracted to /tmp/asdf and still ended up with /tmp/asdf/drxvi314.ko

[PJJ]

Thanks again for the reply.
I just did a quick unzip of the raw driver code to a sub-directory of my home directory. Then make, which gave the errors because 'file(s) could not be found.
I assume because the unzipped code was not in the correct directory.

I will tackle this after I have erased a lot of sub-directories and files that accumulated during my wrestling match with the U600 modem. Need to do some cleaning and house keeping to avoid undue interference. I will also delete all instances of drxvi314.ko now on file in various places. The only drxvi314.ko should then be the one derived from your source code.

I will post the messages on pastebin again in order to keep some of the clutter out of this thread.
Judging by the number of views it is apparent that many people are encountering problems with Franklin U 600.

[paperplate9]

The source zip file provided is just the raw driver code plus the patches. Patching is just something like: patch -p0 < [patch_file]...but I've already provided the patched code.

But can you post your errors when attempting to compile the source zip I provided? I need to see what you are doing & what output you get.

Edit:
Make sure you have linux-headers installed and that /usr/src/linux points to that directory. Or just modify the Makefile in the drvxi314-source.zip and set KSRC to where the headers are (e.g, /usr/src/linux-headers-3.8.0-29-generic). Don't see what other errors you could be getting.

[PJJ]

Thank you so much for your efforts and cooperation.
Unfortunately I am still on a 32 bit laptop. You are on 64.
insmod replies: Invalid format, of course.
Have briefly tried to compile from your source code. Errors all over because files. directories not found.
Need to take more time for this.

My own compilation with 'install.sh' also resulted in a number of error messages. I guess the patch still is not applied correctly. Tried to do it manually - lots of errors.
I am not sure about the syntax of the patch command to get it to work automatically.
What is the code you used, please?

[paperplate9]

I have attached my drxvi314.ko module.

Built on Ubuntu 13.04 under:

Linux hostname 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ modinfo drxvi314
filename:       /lib/modules/3.8.0-29-generic/drxvi314.ko
license:        GPL
srcversion:     DDCD6B882544594F3C89900
depends:        
vermagic:       3.8.0-29-generic SMP mod_unload modversions

I have also just attached the (patched) driver source (minimum necessary) because personally I would be hesitant to install a driver from binary file, especially if it is distributed under GPLv2.

You should be able to extract the source, "make", and end up with drxvi314.ko. Throw that in /lib/modules/`uname -r` and then run depmod and you should be good to go.

[paperplate9]

PS:
I used 'install.sh' to compile to the kernel (3.11.0-xx-generic) -except for the patch(es) and the Sierra modem instructions. Did not work at all.
It seems that some of the required directories have been rearranged and/or moved to other spots. But I will not touch that in detail at all. Got to get 13.03 working.

Don't know what to tell ya...install.sh worked fine for me. It looks like you are using the same version of the Sprint4gDev (1.6.1.2.2) so maybe try extracting this to a fresh directory and running install.sh right off the bat.

install.sh already does get rid of the CR/LFs (aka dos2unix) and patches source code. The patches are needed because at one point some kernel functions were deprecated (file_operations.ioctl()) and the unpatched beceem driver code will not compile. I will see if I can attach my 13.04 / 3.8.0-29-generic drvxi314.ko to this thread later tonight.

[PJJ]

PS:
I used 'install.sh' to compile to the kernel (3.11.0-xx-generic) -except for the patch(es) and the Sierra modem instructions. Did not work at all.
It seems that some of the required directories have been rearranged and/or moved to other spots. But I will not touch that in detail at all. Got to get 13.03 working.

[PJJ]

Oh, a crazy idea!
I am running 13.04. Could I use your compiled drxvi314.ko if you gave it to me?
My installation is quite standard/defaults.

Yes, either the referenced pastebin (with the exception of the patch(es) or Minhazul (Linux Mint). Both worked for me at one time or another. Last failed was according to Minhaz.
Minhaz does not patch. I looked at the files to patch at one time and found that the newer versions of the files inquestions already had the patched info - at least some of them.

Nevertheless I would patch if it cooperated with me. At this time it just sits there doing nothing, though I have very detailed instructions from the author of the pastebin regarding the patching process. I do apply the instructions. The patch does not apply.

As you know from my postings I had a working drxvi314.ko at one time. Unfortunately, either something happened to it or it got erased when I cleaned with UbuntuTweak.
"locate' still finds it and so does Dolphin.
But modprobe says 'file not found' and insmod installs the module (according to lsusb) but nothing else exciting is happening.

After loading the driver I also get the ifconfig -a eth1 entry. Something is happening.

Latest: XP now also does not find the device. Some code on the device itself was changed (for example by extracting the device while it is still working).
I will call Virgin Mobile and check whether they can direct me to the URL with the wimax installation files for download.
That helped with my Novatel 760 modem by restoring it to factory.

[paperplate9]

drxvi314.ko compilation errors!!!

Since something seems to be wrong with my existing wimax driver drzvi314.ko I decided to re-compile it to the kernel 3.8.0-29-generic.

Did not succeed.

The terminal output with the error messages is now posted at

http://pastebin.com/bcx8vj6F

I need help with this one. I am not a programmer and have no idea what the actual error is and how to fix it.

find . -type f \( -name \*.[hc] -o -name \*.cpp \) -exec dos2unix {} \;

Edit: Are you running the install.sh script? It does this as well as makes some patches to the driver before compiling.

Edit 2: From going through your previous posts, I think you are following http://pastebin.com/AzBndfdH. From there make sure you are performing steps #12 (dos2unix) & #13 (patching) before make'ing the driver. However, I just used install.sh in the root dir of Sprint4gDev with no issue. I've upgraded to Ubuntu 13.04 which built the module fine on kernel 3.8.0-29-generic, as well as allowed me to connect to a base station.

[PJJ]

drxvi314.ko compilation errors!!!

Since something seems to be wrong with my existing wimax driver drzvi314.ko I decided to re-compile it to the kernel 3.8.0-29-generic.

Did not succeed.

The terminal output with the error messages is now posted at

http://pastebin.com/bcx8vj6F

I need help with this one. I am not a programmer and have no idea what the actual error is and how to fix it.