Ok, the card is on IRQ3 (not sure how that got past the default filters... but oh well.) So I went into BIOS and simply disabled COM2 (aka IR port). Still the same issue. Here are a couple lines from tcpdump on both machines:
server: 10:34:41.651859 arp who-has 192.168.0.5 tell my.host.machine 10:34:41.651859 arp reply 192.168.0.5 is-at 0:e0:98:88:3a:2b workstation: 10:35:26.651859 arp who-has 192.168.0.5 tell 192.168.0.1 10:35:26.651859 arp reply 192.168.0.5 is-at 0:e0:98:88:3a:2b This happens when I set the trouble system up with an IP of 192.168.0.5 and ping it from the server. Can I ping a mac address? Anyway, my original theory was that nothing was getting to the server... but as you can see, the arp reply is definately getting to both. There is no longer a potential for IRQ conflicts (anything that would want to use IRQ3 is disabled) and I don't think the driver would only work sometimes.. but not others. Perhaps I am wrong... I don't know. Oh, and I have switched sockets (many times) and lsmod and route -n produce exactly the same results when hardwired. (Obviously things would change a little when it acutally gets its address from DHCP) HELP! :-P - Matt Bradford ----- Original Message ----- From: "David Talkington" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 03, 2002 2:41 AM Subject: Re: Question about PCMCIA networking > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Matthew Bradford wrote: > > >Now when I boot up (changing no settings) the card is detected and the > >driver is loaded (known from hearing both beeps and doing an lsmod) but it > >will not transmit anything over the network. It is as if it can only listen > > I haven't seen this for a long time, but based on my experience with > this kind of thing, I'd put my money on a driver problem or conflict. > I'd investigate the contents of /etc/pcmcia/config.opts, and exclude > resources that you might be sharing with other devices; /proc/interrupts > might give you some clues. And try the other slot, too. > > The outputs of `lsmod' and `route -n', when the card is working vs. when > it isn't, might be interesting as well. > > - -d > > - -- > David Talkington > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
