O.K. So I've got the Cisco 350 card installed so that I can configure the card and get it to register to an Access Point, but only after bringing up the ACU. The ACU (Aironet Client Utility) works and I can configure the card for my SSID and WEP key, etc. I can see in the ACU status and in the Access Point that I am associated, so I know that RH8 is firing up the card at some level.

This is the only network connection at present in the notebook.

I can't figure out how to get it to get a dhcp address. If I type dhcpcd eth0, I get:

bash: dhcpcd: command not found

In the System Tools/Network Device Control, it tells me device eth0 is inactive, and won't activate when clicking the activate button.

In the System Settings/Network panel, I have profile for this card with a type of Wireless, but I can't activate that either.

When I installed, I did select that it should use DHCP, and Kickstart confirms that that is the setting.

Yes, I was logged in as root when installing (it's the only user on this station).

TIA for any help,

Brent

/sbin/dhcpcd eth0

dhcpcd is on almost everything on the planet by default unless RH didn't something really dumb on their last run through. Its just not in the default path of a user, and now thanks to some changes in 'su', you keep the path of the pervious user before you su'ed. To avoid that, "su -" that will just relog you in entirely as root, with root's proper path.

Cheers,

Finegan

Thanks for your reply!

Well, I found the dhcpcd equivalent. In RH8, apparently it's called dhclient.

On to the other problem, though. The card only fires up after running the Aironet Client Utility (ACU), not automatically on bootup. The ACU is from Cisco and is (on Windows) only used for configuring the card options, not for firing up the card. How do I get it to automatically fire up the card on boot?

Even stranger, after getting the card to register and using dhclient to get an address, the system gradually starts to slow down, until it won't open a new terminal or browser window, but does respond to already open windows. When I try to shut the system down, it only gets about halfway down and won't finish.

Thanks for any help!

Brent

Well, I've reinstalled from scratch and when I try to run the Cisco/Aironet Driver installer, it asks about which kernel version I'm running. When I run uname -a, I get

Linux localhost.localdomain 2.4.18-14 #1 Wed Sept 4 11:57:58 EDT 2002 i586 i586 i386 GNU/Linux

Unfortunately, the driver selections all ask for Kernel 2.4.2-processor (which I assume is the i586). When I select Kernel 2.4.2-i586, the install script then complains about there not being a /lib/modules/2.4.2-2/kernel/drivers/net/pcmcia directory.

I would think that 8.0 would have the latest kernel. No?

Not sure where to go now, and I'm probably too thick to find, unpack, and compile a bunch of source.

Please help!

Brent

2.4.2, the kernel the aironet package is looking for was one of the last kernels that shipped WITHOUT the modules already in there, the cisco package is out of date, RedHat is more or less current. RH already has airo and airo_cs on board (the modules for the job). If you use the command: "/sbin/lsmod" you'll probably see them loaded.

You can hand modify the file /etc/sysconfig/network-scripts/ifcg-wireless (or something like that, I always mis-spell the ifgh ifhg part... and put in all of your lan specific info. Or you can put it in /etc/pcmcia/wireless.opts, both will work (wacky eh, there are actually about 15 different ways). The Cisco client utility isn't necessary, although it is prettier that the command line.

Or you can just adjust everything with "iwconfig"

iwconfig eth1 essid ghagurgle (for the wireless network named ghagurgle)

iwconfig eth1 enc 23456789 (to change the WEP key to 23456789).

Post back with what chokes where... when it doesn't work, give me the output of:

iwconfig eth1
ifconfig eth1

This is assuming you have onboard ethernet, if not the device is probably just eth0.

I have no idea what that memory rabbit was, I've never dealt with something like that coming from a wireless device, nor heard of it. Its probably some hard to reproduce bug that's hardware specific... We'll take a whack at it if it re-occurs. What's the model of the laptop?

Cheers,

Finegan

use the kpciinstall option for the driver instead of the cw