General TC > Tiny Core Netbooks
eeePC 1000
MikeLockmoore:
vkcbo: I might be able to try to package it, but packaging is not really my forte. I'm a coder!
I'm not using the automatic method of loading this kernal module. I use 'ismod' in a startup script, along with iwconfig and ifconfig. That way, I did not need to alter as much of the base filesytem and add a bunch of things to the backup filelist. But maybe that is not a good strategy if a .tcz is to be made for others to use.
Within the next day or two, I'll try to post my startup scripts. Then maybe the packaging experts tell us whether this is a good strategy to base the .tcz on or suggest another strategy. Then either I or one of them could make a .tcz for the repository.
--
Mike
MikeLockmoore:
Quick update. I'm working with the Core Team to package the rt2860sta driver. I hope to verify a basic .tczm package tomorrow, then I'll post some configuration guidelines and example start script.
--
Mike
MikeLockmoore:
Another udpate: I've tested the pre-release .tczm for the built-in ra2860sta WiFi chipset and it works! With this .tczm, the driver file is automatically uncompressed and loaded into the kernal space. The .tczm also places a hardware config file (RT2860STA.dat) in the correct place the /etc file tree so the driver can find it and start. So with this .tczm, I no longer need a script to do 'ismod' and restore the .data file.
So, as soon as I get to my desktop, I can then run a script like this below to associate with the Wireless Access Point (WAP... the WiFi router):
--- Code: ---#!/bin/sh
# commands to associate with wireless access point
sudo /sbin/ifconfig ra0 up
sudo /usr/local/sbin/iwconfig ra0 essid "{{{YOUR ESSID HERE}}}" key restricted "{{{YOUR KEY HERE}}}"
sleep 2
sudo /sbin/udhcpc -i ra0
sleep 7
# Fix up incorrect (SLOW!) resolv.conf content with a copy of resolv.conf with a real DNS IP!
sudo cp -f /home/tc/drivers/etc_resolv.conf /etc/resolv.conf
--- End code ---
If you want to always associate with one WAP, you could put these commands into your /opt/bootlocal script (in which case you wont need to use sudo with those commands. Or you could keep the commands above in a script in your home folder and call it from /opt/bootlocal. If you associate with different WAPs at different times, you can set up multiple scripts to run as needed. Or maybe there is a nice tool to help you find and associate with different wireless LANs that works well in TC?
Note: You many need to alter the way the security key info is formatted to work with your WAP. If it is unsecured, the iwconfig line can have 'key none' (with no quotes). iwconfig is part of the wireless_toos.tcz extension.
If you want to use a fixed IP address, use something like the following instead of the udhcpc line:
--- Code: ---sudo /sbin/ifconfig ra0 192.168.1.124
--- End code ---
bigpcman:
--- Quote from: MikeLockmoore on October 07, 2009, 12:17:18 PM ---Another udpate: I've tested the pre-release .tczm for the built-in ra2860sta WiFi chipset and it works! With this .tczm, the driver file is automatically uncompressed and loaded into the kernal space. The .tczm also places a hardware config file (RT2860STA.dat) in the correct place the /etc file tree so the driver can find it and start. So with this .tczm, I no longer need a script to do 'ismod' and restore the .data file.
So, as soon as I get to my desktop, I can then run a script like this below to associate with the Wireless Access Point (WAP... the WiFi router):
--- Code: ---#!/bin/sh
# commands to associate with wireless access point
sudo /sbin/ifconfig ra0 up
sudo /usr/local/sbin/iwconfig ra0 essid "{{{YOUR ESSID HERE}}}" key restricted "{{{YOUR KEY HERE}}}"
sleep 2
sudo /sbin/udhcpc -i ra0
sleep 7
# Fix up incorrect (SLOW!) resolv.conf content with a copy of resolv.conf with a real DNS IP!
sudo cp -f /home/tc/drivers/etc_resolv.conf /etc/resolv.conf
--- End code ---
If you want to always associate with one WAP, you could put these commands into your /opt/bootlocal script (in which case you wont need to use sudo with those commands. Or you could keep the commands above in a script in your home folder and call it from /opt/bootlocal. If you associate with different WAPs at different times, you can set up multiple scripts to run as needed. Or maybe there is a nice tool to help you find and associate with different wireless LANs that works well in TC?
Note: You many need to alter the way the security key info is formatted to work with your WAP. If it is unsecured, the iwconfig line can have 'key none' (with no quotes). iwconfig is part of the wireless_toos.tcz extension.
If you want to use a fixed IP address, use something like the following instead of the udhcpc line:
--- Code: ---sudo /sbin/ifconfig ra0 192.168.1.124
--- End code ---
--- End quote ---
What would it take to modify this for the eeepc 900a which uses the Atheros AR5007EG?
MikeLockmoore:
I have also verified the rt2860.tczm with a WEP-secured WiFi access point (my home network), and it worked well in a short test.
--
Mike L.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version