Realtek Wireless firmware extention help?

[coreplayer2]

Finally some success!  Things working as expected!  Now there's a novelty

using the OEM driver specifically for the UA150 adapter we now have a 8712u.ko driver   I think it's a one size fits all these specified models only the name does not reflect the device.

[SamK]

...select the  download server from the "Linux driver for kernel 2.6.x you'll get the zip file I used

size = 2018K

The files downloaded from the link you provide do not correspond with the directory listing in reply #27.
   

[coreplayer2]

ok the link can't be fixed, phew darn java!!  I can go to the site and navigate to the specific driver but can not copy the link.  however  the current link reflects the page from where the driver was downloaded from and used earlier, which still can't be compiled.   The rtl8192su version was selected and downloaded which I'm also no longer using.  

I've had success building the OEM version (for which there is no link) except the zip contains a driver for several compatible models and the resulting build has a different name

compiled driver is named 8712u.ko

and the device is 8192u   ??

[coreplayer2]

just noticed i've been upgraded to a junior   

also updated last post to reflect changes and why I had so much difficulty with the link

[coreplayer2]

The driver in zip file I'm working with now is

RTL8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20100823.zip    (and is 2.0MB in size)

produced a file  8712u.ko    


am not sure if I can simply rename it to reflect the current hardware or not?

[coreplayer2]

the next hurdle  


mksquashfs package  etc etc
mksquashfs: not found


h'mmm    yet squashfs-tools-4.x is confirmed loaded in system stats


now what?  reinstall  lol

[Rich]

Hi coreplayer2

Open AppBrowser and click on local, scroll down to squashfs-tools-4.x select it and click OK, see
if that makes a difference.

[coreplayer2]

Hi Rich

I had to make it  "On-Demand"   then load it up when required  thanks


Ok the extension is made, now if I could just get this driver to communicate with the device we'll be winning   wait the driver is supposed to be the tool making the communication!  

the extension has been created and it loads at boot as seen in the tce.installed directory and in the stats window.   the device however doesn't know how to use the driver.  I wonder if because the driver is a different name ??

the device i think is 8192u  and the driver is 8712u   the name of the file originally included both names

[Juanito]

Did you try "sudo modprobe 8712u"

[coreplayer2]

well actually I couldn't remember that command so have been looking for it, thanks

the return from issuing that command I get is the module is not found in "modules.dep"

 

[Juanito]

Try:

Code: [Select]

$ sudo depmod -a
$ sudo modprobe 8712u
or

Code: [Select]

$ sudo insmod /path-to-file/8712u.ko

[coreplayer2]

looks like this is the problem.

the extension is installed, it is shown in the control panel > system stats > installed.  presumably this is read from tce.installed directory. 

the driver can not be found anywhere.  conducted a thorough search and can not find it.  somehow the path is messed up!

 

[Juanito]

Look in /tmp/tcloop/extension_name - this is where all of the extensions are mounted.

By examining the directory structure of your extension in /tmp/tcloop, you should be able to see where the driver is.

[coreplayer2]

thanks

/tmp/tcloop   was  empty  

rebooting now  and still empty?

[Juanito]

If /tmp/tcloop is empty then none of the extensions are loaded - unless you're using "scatter mode"?