Lan Barnes wrote:
On Sat, January 6, 2007 6:52 pm, Lan Barnes wrote:
MythDora (RH FC 3 based) 3.2 is installed. Next is wifi connectivity
because I simply can't cable that far in this old house.
The card in question is a Prism card. Picked up on boot according to both
dmesg and /var/log/messages. They call it wifi0. No wifi0 appears in /dev.
I used the RH GUI tools to set up the ifup scripts, checking all the
parameters against working machines. The channel, modes, and WEP mojo all
match. I chose not to bind to a HW Addr, not knowing if the probe had
gotten the card of eth0 on the MB. Don't knwo how to probe a card for its
HW Addr (something in /proc?).
I suspect that the right module needs to be found and loaded.
Could you most kindly tell me what diagnostics to run so I can sound more
intelligent asking for help?
Oh, ping says network unreachable. No DHCP, all static.
OK, iwconfig shows that the card is found and the config is taken, but
signal level is 0. The google sirtes say that the module should be
PCI : prism2_pci.o
I'm presently running run-parts to build a locate db.
Wish I knew more about modules.
Are you sure that MythDora is based on FC3? The site says it's based on
FC5 (that's a Five, not Three). It's an important difference because
your modules will change based on your kernel.
It appears the module you actually want is called prism54.ko The names
for modules were changed in the 2.6 kernel line to end in .ko instead of .o.
You don't really need to know the suffix. Load the module with:
# modprobe prism54
Look at your /var/log/messages file and dmesg to see if there are any
errors.
But you say that iwconfig found the interface so it looks like you don't
need to do anything except feed in the right parameters. Try running:
$ iwlist eth1 scan
Substitute the correct interface for eth1, which you found by running
iwconfig. It should show your wireless access point and give you some
information about it. If it doesn't do that there is something else
wrong. It would help if you told us the make and model of wireless card
so we could determine if you need to get some firmware. Also the output
of lspci that shows the info for your card.
What does the /etc/sysconfig/network-scripts/ifcfg-ethX file look like
(where X is the number of the interface)? It should look something like
this:
# Wireless device
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=static
NETMASK=255.255.255.0
DHCP_HOSTNAME=
IPADDR=192.168.1.x
DOMAIN=
HWADDR=xx:xx:xx:xx:xx:xx
USERCTL=yes
PEERDNS=yes
TYPE=Wireless
IPV6INIT=no
ESSID=KPLUG
MODE=Managed
RATE=Auto
CHANNEL=
Substitue in the right numbers for the HWADDR (might not be needed so
comment out) and the IPADDR and the right name for the DEVICE and ESSID.
It might help to start with not to use WEP until you get regular
wireless working, then add it in later.
It would have been really to your benefit to have come to the
Installfest today since we were pounding away on problems like this today.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
