Lan Barnes wrote:
On Tue, January 9, 2007 6:26 pm, Lan Barnes wrote:
Well, here we go.

The MythDora is showing every sign in ifconfig and iwconfig of bring
healthy. But it throws a set error ("mode not supported." This doesn't
bother me because my working laptop throws the same error.

Here's my thought. The laptop fails if I try to reset with the Fedora
utility. It works when I run my scripts out of rc.local.

[EMAIL PROTECTED] etc]# cat /etc/rc.d/init.d/atheros.sh
modprobe ath_pci
ifconfig ath0 up

iwconfig ath0 key abae032345
iwpriv ath0 authmode 2

iwconfig ath0 essid "marconi"
ifconfig ath0 192.168.100.40 netmask 255.255.255.0 up
route add default gw 192.168.100.1

iwconfig ath0 key abae032345

# and

ifup House_Wireless

<hmm ... gonna have to change that WEP key after all this. No biggie>

So I'll try doing it by hand after the box is up.


Didn't work. Poop!

Thoughts?

Well, my earlier comment about the hostap driver might have been wrong. It appears that in about kernel 2.6.14 things changed and the hostap driver was added which ALSO hosts the orinoco chipsets and might even be better. So now there seems to exist two different drivers from different groups trying to provide the same service. The key is in the PCI device ID which is hard-coded in the device driver as a static stuct (I'm looking at the source code right now!), like this snippet from the hostap_pci.c file found in driver/net/wireless/hostap/:

static struct pci_device_id prism2_pci_id_table[] __devinitdata = {
        /* Intersil Prism3 ISL3872 11Mb/s WLAN Controller */
        { 0x1260, 0x3872, PCI_ANY_ID, PCI_ANY_ID },
        /* Intersil Prism2.5 ISL3874 11Mb/s WLAN Controller */
        { 0x1260, 0x3873, PCI_ANY_ID, PCI_ANY_ID },
        /* Samsung MagicLAN SWL-2210P */
        { 0x167d, 0xa000, PCI_ANY_ID, PCI_ANY_ID },
        { 0 }
};

The key to understanding this is in the numbers, which are the Vendor ID and the Product ID. If you run lspci -n, you will get numbers instead of a translation to English for the device IDs. Then if you use the numbers you can grep the kernel source code to find the drivers for the device. Running lspci without -n and then with -n allows you to match numbers to descriptions because the list in the same order. Somewhere there is a database of ID's to descriptions but I don't know where it is yet. Anyway, try posting your numbers and I'll search the source for you if you don't want to poke around yourself.

Gus


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to