On Wed, 2003-08-20 at 04:12, [EMAIL PROTECTED] wrote: > Further to my previous message, this is what I get in > /var/spool/messages... > > Aug 20 16:24:49 bree cardmgr[745]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter > Aug 20 16:24:49 bree cardmgr[745]: executing: 'modprobe orinoco_cs' > Aug 20 16:24:49 bree /etc/hotplug/net.agent: invoke ifup eth1 > Aug 20 16:24:49 bree cardmgr[745]: executing: './network start eth1' > Aug 20 16:28:03 bree kernel: eth1: New link status: Connected (0001) > Aug 20 16:28:40 bree kernel: NETDEV WATCHDOG: eth1: transmit timed out > Aug 20 16:28:40 bree kernel: eth1: Tx timeout! ALLOCFID=ffff, TXCOMPLFID=ffff, > EVSTAT=8000 > Aug 20 16:28:41 bree kernel: eth1: New link status: Connected (0001) > Aug 20 16:29:28 bree dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 > Aug 20 16:29:28 bree dhclient: DHCPACK from 192.168.1.1 > Aug 20 16:29:28 bree dhclient: bound to 192.168.1.7 -- renewal in 278 seconds. > Aug 20 16:34:06 bree dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 > Aug 20 16:34:06 bree dhclient: DHCPACK from 192.168.1.1 > Aug 20 16:34:06 bree dhclient: bound to 192.168.1.7 -- renewal in 276 seconds. > Aug 20 16:37:49 bree kernel: eth1: New link status: Disconnected (0002) > Aug 20 16:38:42 bree dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 > Aug 20 16:39:22 bree last message repeated 4 times > Aug 20 16:40:28 bree last message repeated 4 times > Aug 20 16:41:35 bree last message repeated 3 times > Aug 20 16:42:42 bree last message repeated 4 times > Aug 20 16:42:56 bree dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 > Aug 20 16:43:41 bree last message repeated 2 times > Aug 20 16:44:00 bree last message repeated 2 times > Aug 20 16:44:07 bree kernel: hermes @ IO 0x180: Timeout waiting for command > completion. > Aug 20 16:44:07 bree kernel: eth1: Error -110 disabling MAC port > > Any ideas?
I've never had this error before, but I have had problems using that driver with Prism2 cards. It's nice that there's something in there to support the cards "out of the box", but it's not the ideal driver for that chipset. I suggest you download the linux-wlan driver and install them. This dude packages them up nicely for the various Red Hat stock and errata kernels, so you shouldn't normally need to perform any kernel black magic. http://prism2.unixguru.raleigh.nc.us/ Note, after writing that last statement, I checked out his offerings and noticed that he does *not* offer a set for the 2.4.20-19.8 errata kernel, although he does offer them for 2.4.20-18.9 and 2.4.20-19.9 for RH9. I'd suggest you either upgrade to the most recent errata kernel and try his RH9 rpms, or use the source rpm to build your own packages: http://prism2.unixguru.raleigh.nc.us/kernel-wlan-ng-0.2.0-7.src.rpm Once you download/build them, simply install the kernel-wlan-ng, kernel-wlan-ng-pcmcia, and kernel-wlan-ng-modules packages. Reboot, and you should be good to go. You might want to edit the /etc/wlan/wlan.conf to suit your needs, although I've found it can auto-join to many IBSS (no WEP enabled) networks. HTH. -- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
