Realtek Wireless firmware extention help?

[coreplayer2]

all but one extensions are loaded and appear to function except of course for the extension I created.

I still have the structure of the directories I used during extension creation complete with driver in case I needed to make another.

The install follows the guide in the wiki as best I can accomplish to a HDD  with persistence for Home and Opt


This was the destined to be location of the driver  

/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/rtl8712u.ko.gz

this was created inside a directory called package.  I cd to tmp where package was located and ran mksquashfs package/ rtl8712u-2.6.33.3-tinycore.tcz

[Juanito]

I'd suggest trying this:

Code: [Select]

$ sudo mkdir -p /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
$ sudo cp /path-to-file/rtl8712u.ko.gz /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
$ sudo depmod -a
$ sudo modprobe rtl8712u
and then "lsmod" to double-check the driver  loaded

[coreplayer2]

thanks for the info

but at this point would it be better to remake the extension to point to a better location?

it looks to me like the extension is trying to copy the file to a location in the file system which doesn't exist yet?


Oh I got it you want to load the driver to see if it does infact work then remake the extension?

[Juanito]

it looks to me like the extension is trying to copy the file to a location in the file system which doesn't exist yet?

The extension loading routine would create the location if it did not exist.

Oh I got it you want to load the driver to see if it does infact work then remake the extension?

affirmative

[coreplayer2]

that procedure loaded the module as 8712u   

[Juanito]

Good 

What does "dmesg | tail -20" say?

BTW I built a quick extension that seems to work without problems:

Code: [Select]

$ tce-load -i 8712u.tcz
$ modinfo 8712u
filename:       kernel.tclocal/drivers/net/wireless/8712u.ko.gz
description:    rtl871x wireless lan driver
author:         ...
license:        GPL
vermagic:       2.6.33.3-tinycore SMP mod_unload 486
Of course I don't have the hardware to test further

[coreplayer2]

That's so cool


anyhow there is one other issue.  the module currently does not communicate with the device.   I'm wondering if I need to instigate a connection or if the file name which is different is an issue?

brb with the other answer.  ok it say's "not found"

[Juanito]

anyhow there is one other issue.  the module currently does not communicate with the device.   I'm wondering if I need to instigate a connection or if the file name which is different is an issue?

Yes, you'll need to instigate a connection.

I'd suggest to use the wifi extension - load the extension and then "sudo wifi.sh"

[coreplayer2]

I wish I could build an extension that fast  You're my hero!!



Ok the issue I have is understanding how this works.

the file is  RTL8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20100823.zip   when compiled the output is 8712.ko  my device is the 8192su version so I'm wondering does the driver once loaded look for a compatible device?  or should the file name be changed to suit the device?

[Juanito]

Assuming you chose the correct driver in the first place - "rtl871x wireless lan driver" suggests it will be good for any device whose name is 871x, but the driver source filename suggests it will be good for your device - then the driver will find the hardware on its own.

I'd suggest you try the wifi.tcz extension and see how things go.

pasting the contents of "dmesg | tail -20" might also give some indication of whether things might work.

[coreplayer2]

Thanks

I tried both the above with no joy.

first the   dmesg | tail -20  command returned    not found


then the wifi.tcz was already installed and when run  displays a message that no wifi devices found

[gutmensch]

what is a newbie like me to do?

RTFM

Code: [Select]

$ dmesg | tail -20

can hardly yield "not found". You're obviously doing something wrong (again).

[Juanito]

first the   dmesg | tail -20  command returned    not found

eh?

You can also access dmesg from the panel icon - panel/system stats/dmesg

There will be a whole bunch of yada-yada, but you're looking for something like:

Code: [Select]

b43-phy0: Broadcom 4312 WLAN found (core revision 15)
phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'TKIP'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
b43 ssb0:0: firmware: requesting b43/ucode15.fw
b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

[coreplayer2]

Wait!!!    while the new wifitcz module did nothing , the wicd net manager succeeded!!!    we are now connected  to a WPA2 wireless network!!

[Juanito]

Good 

If you were already trying with wicd, that could quite possibly prevent wifi.sh from working.

..and hopefully this shows you connected to the Internet:

Code: [Select]

$ sudo ping -c2 www.google.com