Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: coreplayer2 on June 23, 2011, 05:02:21 AM
-
I'm in desperate need of firmware/extention for a Realtek USB wireless b/g/n adapter. So far I've really struggled for close on three weeks attempting every trick I can find before inevitably compiling from source.
At some point I was able to create an ndiswrapper with WinXP drivers on an earlier tinycore build which did at least function reliably, although was a little high on cpu resources unfortunately. Since then I haven't been able to duplicate the same configuration. Anyhow the issue with the current ndiswrapper is not being able to connect or stay connected for very long, appears to be a driver/firmware issue.
Attempted the new wifi extension over the last couple of days, also without any success. "Fails to get an IP address." then times out. I don't know if the script flushes the routing tables etc etc post failed connection which leaves you a reboot available to start over.
When booted to a puppy linux distro the wireless adapter functions 100% without any extra work on the same PC. With the script available here to convert deb files to tcz extensions I grabbed the driver form this distro and attempted to convert it, without any success.
This bring me to a decision point, I think the only reliable method of connection is to compile the correct firmware/driver. So I grabbed the driver/firmware source for the rtl8192su from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false)
and installed "compiletc" & "squachfs-tools-4". The source came with a makefile but no configure file.
The first hurdle: running either make or ./make results in "file not found!!"
any suggestions welcome please?
-
Hi coreplayer2,
The first hurdle: running either make or ./make results in "file not found!!"
any suggestions welcome please?
This may help: http://forum.tinycorelinux.net/index.php?topic=7219.0
Is the linux-headers extension the cause as mentioned in reply #13?
-
Thanks SamK that link was extremely informative. Darn it I forgot about the headers!!! what is a newbie like me to do? Will get right on it asap
thanks again SamK
meanwhile I still get file not found!! :(
-
Hi coreplayer2
The extension you are looking for is called compiletc.tcz. It includes all the tools and the headers.
-
Ah yes I am aware of this extension and already have it installed thanks. In addition I used the tce-load command to confirm "make" was installed which is part of compiltc
but still no joy, how hard can this be?
-
Hi coreplayer2
If you type /usr/local/bin/make does it find it then?
If it does then your path is not set correctly, if not, then compiletc is not installed correctly.
-
Was thinking it had only to be a path issue
brb
-
Hi coreplayer2
Was thinking it had only to be a path issue
So did it find make when you gave the full path?
-
but still no joy, how hard can this be?
A couple of ideas...
This wiki page is helpful:
http://wiki.tinycorelinux.net/wiki:creating_extensions
After unzipping the download there is a driver directory. In this there is a further .tar.gz, unpack this also. This will create yet a further directory. Change (cd) into this directory then follow the steps in the wiki.
-
Thanks guys but still no cigar :(
given the full path i still get "not found" Although there is a difference, instead of "file not found" the command "/usr/local/bin/make" returns "not found"
currently uninstalling compiletc and reinstalling I just have to rig up a wired connection
-
Hi coreplayer2
Exactly what I was going to suggest.
-
I wish I could copy and paste the results I get from the terminal but that doesn't appear to function either.
meanwhile
the error now is something like this
make *** /lib/modules/2.6.33.3-tinycore/build: No such file or directory, stop.
make *** [ALL] Error 2
-
using these commands from the directory where the makefile is located the result is the same
/usr/local/bin/make
./make
from root or not
The good news is if I type "make -h" at the prompt, make returns all options
We shouldn't have to specify the file right? like "make -f makefile" ?
-
Hi coreplayer2
All you should have to do is cd into the directory containing makefile of the project you are trying
to compile and type make
If the makefile is called something besides makefile or Makefile you need to specify the file name.
-
I typed the error in second post above if we open a terminal at the location of the makefile
-
ok did an uninstall and reinstall of the linux headers again
here goes :-\
-
Hi coreplayer2
I didn't see that other post. Copy/paste from a terminal is done by using the left mouse button to
highlight the text you want to copy then go to where you want to paste it to and click the middle
button, the text will wind up where the cursor is flashing.
So make is working and it's finding the makefile.
make *** /lib/modules/2.6.33.3-tinycore/build: No such file or directory, stop.
I believe that means the header files are either not installed or not mounted. Not sure how to fix that.
Maybe one of the administrators can provide a hint.
-
thanks
the copy paste function may be related to the mouse settings because I lost this capability after setting up the mouse. I disparately need a clipboard
I think i'll reboot on last time then install compiletc and the headers again, then try
:o
-
Hi coreplayer2
All you need is compiletc. The headers are included with that package.
-
really??
-
make *** /lib/modules/2.6.33.3-tinycore/build: No such file or directory, stop.
This error occurs when there is no symlink to the kernel source, eg /lib/modules/2.6.33.3-tinycore/build -> /usr/src/linux-2.6.33.3
A quick fix is to load the linux-headers-2.6.33.3-tinycore extension in addition to compiletc
-
make *** /lib/modules/2.6.33.3-tinycore/build: No such file or directory, stop.
make *** [ALL] Error 2
I believe that means the header files are either not installed or not mounted. Not sure how to fix that.
I can recreate these messages by deliberately not loading the header files.
@coreplayer2
In Control Panel-->System Stats is a tab "Installed". This lists what is successfully loaded. Can you confirm that "linux-headers-2.6.33.3-tinycore" appears in the list.
If not visible can you confirm precisely each step you conduct to download and load the extension?
-
Cool, thanks for the help :)
ok am uninstalling everything, rebooting and reinstalling compiletc and then the headers. Am also assuming the directory with source files (and the makefile) needs to be copied to the tmp directory.
will cd to this directory and attempt the make command agin
-
ok
compiletc & linux-headers-2.6.33.3-tinycore & make are all listed now in the installed tab of tinycore system stats
brb
-
Well, we're definitely getting there but still no cigar :(
he he! I found the middle mouse button restores clipboard copies :)
tc@box:/tmp/rtl8192su$ sudo -s
root@box:/tmp/rtl8192su# make
make[1]: Entering directory `/usr/local/src/linux-headers-2.6.33.3-tinycore'
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8180_93cx6.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192U_wx.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192S_phy.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192S_rtl6052.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192S_rtl8225.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r819xU_cmdpkt.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.o
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c: In function 'dm_txpower_trackingcallback':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c:1096: warning: unused variable 'dev'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c: In function 'dm_check_txpower_tracking':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c:1737: warning: unused variable 'priv'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c: At top level:
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c:1114: warning: 'dm_InitializeTXPowerTracking_TSSI' defined but not used
/tmp/rtl8192su/HAL/rtl8192u/r8192U_dm.c:1652: warning: 'dm_CheckTXPowerTracking_TSSI' defined but not used
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192SU_HWImg.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192S_firmware.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192S_Efuse.o
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192U_core.o
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c: In function 'rtl819x_set_mcast_register':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:4338: warning: unused variable 'dev'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c: In function 'rtl8192_usb_probe':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11333: error: 'struct net_device' has no member named 'open'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11334: error: 'struct net_device' has no member named 'stop'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11335: error: 'struct net_device' has no member named 'tx_timeout'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11336: error: 'struct net_device' has no member named 'do_ioctl'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11337: error: 'struct net_device' has no member named 'set_multicast_list'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11338: error: 'struct net_device' has no member named 'set_mac_address'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11339: error: 'struct net_device' has no member named 'get_stats'
make[2]: *** [/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.o] Error 1
make[1]: *** [_module_/tmp/rtl8192su/HAL/rtl8192u] Error 2
make[1]: Leaving directory `/usr/local/src/linux-headers-2.6.33.3-tinycore'
make: *** [all] Error 2
root@box:/tmp/rtl8192su#
since the error was generated whilst in the HAL/rtl8192u/ directory I entered this location, opened a terminal and ran make to investigate
root@box:/tmp/rtl8192su/HAL/rtl8192u# make
make -C /lib/modules/2.6.33.3-tinycore/build M=/tmp/rtl8192su/HAL/rtl8192u CC=gcc modules
make[1]: Entering directory `/usr/local/src/linux-headers-2.6.33.3-tinycore'
CC [M] /tmp/rtl8192su/HAL/rtl8192u/r8192U_core.o
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c: In function 'rtl819x_set_mcast_register':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:4338: warning: unused variable 'dev'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c: In function 'rtl8192_usb_probe':
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11333: error: 'struct net_device' has no member named 'open'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11334: error: 'struct net_device' has no member named 'stop'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11335: error: 'struct net_device' has no member named 'tx_timeout'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11336: error: 'struct net_device' has no member named 'do_ioctl'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11337: error: 'struct net_device' has no member named 'set_multicast_list'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11338: error: 'struct net_device' has no member named 'set_mac_address'
/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.c:11339: error: 'struct net_device' has no member named 'get_stats'
make[2]: *** [/tmp/rtl8192su/HAL/rtl8192u/r8192U_core.o] Error 1
make[1]: *** [_module_/tmp/rtl8192su/HAL/rtl8192u] Error 2
make[1]: Leaving directory `/usr/local/src/linux-headers-2.6.33.3-tinycore'
make: *** [modules] Error 2
root@box:/tmp/rtl8192su/HAL/rtl8192u#
-
Well, the driver is not compatible with the kernel. Not your fault.
-
he he! I found the middle mouse button restores clipboard copies :)
That's what Rich was trying to explain in reply #16.
Well, we're definitely getting there but still no cigar :(
Can you post the full name and size of the zip file you downloaded?
Also it would be good to see a listing of everything in the directory that holds the makefile.
-
yes thx I'd been trying to paste using both l&r mouse buttons which of course didn't work after changing the mouse settings, but I got it now thanks to you both :)
Ok this took some work but here is a screen shot showing the exact contents of the zip file extracted to tmp directory. This looks a little different from your description right?
(http://db.tt/BZHmbqQ)
and the source download link I provided in post #1 I believe
-
Ok this took some work but here is a screen shot showing the exact contents of the zip file extracted to tmp directory.
and the source download link I provided in post #1 I believe
The download link you provided is to the Realtek site - what I was asking for is the name and size of the zip file you downloaded.
An alternative way to provide a listing of directory contents is to run in a terminal:
ls -1laYou can then copy and paste the output (it's handy to know about the middle mouse button).
-
Thanks I was looking for some quick method as opposed to editing a screen shot :)
a directory listing at the terminal = ls -1la as in "LS -1LA" ? (lower case of course)
brb with the link
I think this is the link the Hong Kopng server (HK1) from the same link from post #1 is the closet I can get to the link to the zip file. if you select the download server from the "Linux driver for kernel 2.6.x you'll get the zip file I used
size = 2018K
well I provided the wrong link in post #1 but corrected that now, however the source I've been using looks to be the correct version
Ok I have the Linux source code from the branded manufacturer (Amped Wireless) for their UA150 adapter. As far as I can tell it is for kernel 2.6
we'll see
-
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.
-
...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.
-
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 ??
-
just noticed i've been upgraded to a junior ;D
also updated last post to reflect changes and why I had so much difficulty with the link
-
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?
-
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
-
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.
-
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
-
Did you try "sudo modprobe 8712u"
-
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"
???
-
Try:
$ sudo depmod -a
$ sudo modprobe 8712u
or $ sudo insmod /path-to-file/8712u.ko
-
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!
-
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.
-
thanks
/tmp/tcloop was empty ???
rebooting now and still empty?
-
If /tmp/tcloop is empty then none of the extensions are loaded - unless you're using "scatter mode"?
-
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
-
I'd suggest trying this:
$ 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
-
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?
-
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
-
that procedure loaded the module as 8712u :)
-
Good :)
What does "dmesg | tail -20" say?
BTW I built a quick extension that seems to work without problems: $ 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
-
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"
-
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"
-
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?
-
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.
-
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 :(
-
what is a newbie like me to do?
RTFM :)
$ dmesg | tail -20
can hardly yield "not found". You're obviously doing something wrong (again).
-
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: 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)
-
Wait!!! while the new wifitcz module did nothing , the wicd net manager succeeded!!! we are now connected to a WPA2 wireless network!!
-
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: $ sudo ping -c2 www.google.com
-
the connection is excellent, solid and at 100% it does not flinch. cool I can't thank you guys enough. for me this task has been day in day out for almost three weeks.
pity the the wifi.tcz extension didn't appear to flush the tables then bring up the device which Wicd network manager accomplished without an issue. Maybe the wifi app would function from a reboot without and previous connection.
of course the extension still needs to be remade with the ideal path.
-
Try this - somewhat longwinded and assuming you have not rebooted, but it will get the job done:
$ mkdir /tmp/pkg
$ cd /tmp/pkg
$ sudo tar -czvf realtec.tce --numeric-owner /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/8712u.ko.gz
$ sudo tar xzf realtec.tce
$ sudo rm realtec.tce
$ cd ..
$ sudo mksquashfs pkg/ 8712u.tcz
$ sudo chown tc:staff 8712u.tcz
$ cp 8712u.tcz /path-to-a-safe-place
-
already had chromium installed in anticipation of success :) browses the web just fine thanks again Juanito and not forgetting maro, rich and especially SamK for heading me in the right direction.
the fat lady isn't singing yet though because I still have to learn the correct path for the module to be copied too and then recreate the extension.
-
..I still have to learn the correct path for the module to be copied too and then recreate the extension.
The correct path for the module is in the post above.
If you drop me a pm, I can send you the extension I made.
-
You type too fast :) I see the path and I'm sure this is the path I used earlier, only that I used xfe to create the directories and copy the driver with, then I fear I may have entered the directory above where I should have been located to make the extension from.
doh!!
ok am running your commands from above post now :)
-
ok where did I go wrong with this?
tc@box:/tmp/pkg$ sudo tar -czvf realtec.tce --numeric-owner /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
/8712u.ko.gz
tar: Removing leading `/' from member names
tar: /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/8712u.ko.gz: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tc@box:/tmp/pkg$
-
I don't know, but do this:
$ sudo mkdir -p /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
$ sudo cp /path-to-file/8712u.ko.gz /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
..and then go back to the start of the previous instructions - i.e. "mkdir /tmp/pkg", etc
-
I think I got it.. the file name is rtl8712.ko.gz currently ::)
am here now
tc@box:/tmp/pkg$ sudo tar -czvf realtec.tce --numeric-owner /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
/rtl8712u.ko.gz
tar: Removing leading `/' from member names
/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/rtl8712u.ko.gz
tc@box:/tmp/pkg$ sudo tar xzf realtec.tce
tc@box:/tmp/pkg$ sudo rm realtec.tce
tc@box:/tmp/pkg$ cd ..
tc@box:/tmp$ sudo mksquashfs pkg/rtl8712u.tcz
sudo: mksquashfs: command not found
tc@box:/tmp$
I forgot, I'd put squashfs in On-Demand so I could load it at will, as onboot would not load when needed or would have to reboot
-
tc@box:/tmp$ sudo mksquashfs pkg/rtl8712u.tcz
SYNTAX:mksquashfs source1 source2 ... dest [options] [-e list of exclude
dirs/files]etc etc long list of options
but I think I need to cd to wireless directory or provide an extension name ??
disregard, all that was needed was a space between source and destination :)
-
The command is:
$ sudo mksquashfs pkg/ rtl8712u.tcz
i.e. there is a space between "pkg/" and "rtl8712u.tcz"
-
lol lol I type too slow!!
-
I caught the error thanks am now ready to reboot since the extension is in the optional directory and set to load at boot
-
Well I thank you again for all your help. I have to get some sleep and hit this again tomorrow. After the reboot no dice, no wifi devices yet the driver is listed as installed. Same as before, driver can not be found anywhere.. even rebooted with the extension you sent me and that is same, can not be found.
I saw an error message flash by quickly during boot of something not initialized. It is clear the extensions are not installing into the correct location in the file system.
good night.
-
Ok am ready to hit this again.
all the extensions we made yesterday load as expected, yet when we drill down to the expected location the actual driver does not exist.
This is the expected location right?
/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/8712u.ko.gz
The file 8712u.ko.gz does not exist at this location, and issuing the command "sudo modprobe 8712u" produces "module 8712u not found" after booting with each of the three extensions we made yesterday.
-
Hi coreplayer2
Try this, sudo find / -iname 8712u.ko.gz
If it's anywhere on your system, that should tell you where it is.
-
Thanks
this morning I created a new extension since both extensions made by myself and Juanito installed but failed to copy the file 8712u.ko.gz to it's desired location.
location for the driver is:
/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
So this morning I created another extension this time I cd to tmp (instead of /tmp/pkg like yesterday)
tmp/pkg/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless/r8712u.ko.gz
cd tmp
mksquashfs pkg/ r8712u-2.6.33-tinycore.tcz
copied r8712u-2.6.33-tinycore.tcz to optional directory and opened AppsAudit, On Boot Maintenance, then moved r8712u-2.6.33-tinycore.tcz to the onboot list, exited out of the OnBoot maintenance and rebooted.
After the reboot the extension is again loaded, it is listed in the installed list yet STILL the driver r8712u.ko.gz can not be found anywhere on the system particularly is not listed in /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless
back to square one, ok maybe two..
-
Hi coreplayer2
Try this, sudo find / -iname 8712u.ko.gz
If it's anywhere on your system, that should tell you where it is.
That's a cool command thanks :)
one more reboot, extension is installed (of this there is no question) I can find only the development and backup copies of the driver now named r8712u.ko.gz it is definitely not listed in any other location especially not in /usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/net/wireless where the extension should have copied it to.
but I can copy the driver manually to the proper location and load it up and works (or at least it did yesterday)
-
Seems like every time I reboot there's is a different story :(
If I look back there is a familiar "file not found" when the file was present on the last boot. eg, an earlier boot I was able to start the Wicd daemon now the command can't be found. I uninstalled and reinstalled and loaded OnBoot wifi, now it can't be found either
When I run dmesg |tail -20 there is a WARNING maximal mount count reached
Checking all Md5 hashes turns up all OK.
I don't have any idea why the file system continuously gets corrupted, but this appears to be the root of all my issues. and am not sure how to fix it either.
-
Hi coreplayer2
Considering the problems you are having I have a few questions/requests
1. How did you install TC? Did you use one of the install utilities?
2. Did you install to a hard drive or a USB memory stick?
3. When you reboot do you run a backup first or do just hit the reset or power button?
4. Could you please post the output of showbootcodes.
5. Run the following commands:
dmesg > dmesg.txt
mount > mount.txt
ps ax > ps.txt
lsmod > lsmod.txt
6. When you go to reply, click on Additional Options and attach the files from step 5.
Maybe with some information about your setup someone can figure out what's going on.
-
I can't believe it!!!
I ran a file system check (which was clean) and set the max mount count to (0) I think?? and viola all my issues are resolved. Booted with base norestore, ran fsck & tune2fs -i0 -c0 on /dev/hda1 & 2
tcloop is no longer empty ;D
all my apps function now ;D
no more "file not found" issues ;D
And the best thing is my new wireless extension loads at boot and copies the driver to the correct location and runs
double YAY!!
-
I ran a file system check and set the max mount count to (-1) I think?? and viola all my issues are resolved.
No - setting the max count to -1 did not fix your issues.
Using fsck to repair the corruption in the file system fixed your issues.
max count triggers a warning to check the file system when the file system has been mounted {max count} times.
-
Oh ok but the fsck returned "clean"
@ Juanito
Note: tcloop is no longer empty ;D
-
It seems highly possible my issues were caused by file corruption, but how was this possible? The physical drive has never had issues and is relatively new. I'm thinking back to when these issue have occured previously (within the last few weeks) and I recollect introducing a USB thumb drive partially formatted with FAT32 as per the wicki to transfer files from a windows PC. Could this be a cause?
-
Unclean shutdown, power cut, etc...
-
Thanks, but kinda obvious :)
Lately there have been several instances of similar issues, which I resolved quickly with a wipe of the drive and a reinstall. The more I think of this I am becoming increasingly more suspicious that each event was related to transferring files via a usb drive having a FAT32 partition where corruption occurred shortly after the usb drives use.
Just a thought..
-
It is extremely important to umount theUSB drives before unplugging.
This is true even for Windows ( Safely remove ).
FAT filesystem corruption may not be detected if the directory and FAT are
written, but not all of the data.
-
It seems that all my compiling issues are resolved now after a fix of the file system, am still interested in other possible reasons (besides the obvious) for the file system corruption I experienced. am still perusing other ideas on this.
Meanwhile the newly compiled wireless driver works great. Only thing is the package included an early version of wpa_supplicant. how this is used during compilation I don't know yet. when compiling the driver what is the meaning of compiled with, or compiled against another app source like wpa_supplicant??
The compiled driver whilst large does not apparently contain a usable wpa_supplicant as an additional wpa_supplicant extension is needed to function.
The issue I see is one wpa_supplicant version used with the driver source during compiling and another version used by a network manager?
any thoughts please?