On Sat, January 6, 2007 11:24 pm, Gus Wirth wrote: This is great stuff, Gus, thanks. On the FC version, I typed 3, meant 5. Keyboard error (the keyboard made a mistake in selecting me as a typist -- its fault).
> 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. > I have prism54 already on the box according to locate. The orinoco surprised me, but I didn't want to rush to change it as the install selected it. I'll try changing it now as directed below. I suspected the module/driver was the problem. > 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. > That's pretty much what I've got. I need to confirm the HW address with iwconfig, but otherwise I got that much tight. > 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. > I know, I know. Sometimes I feel like I don't show enough commitment to Kplug. Wanna hear all my but's? They all come down to being married, having other interests (most of which clog up the house and lead to lots of cleaning obligations), and liking football. I'll use your tips and see if I can break this thing. I have it set up so I can work on it while watching the playoffs ;-) Onward, -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
