[SLE] Turn off USB and play with PCMCIA
I'm a still trying to get this Xircom card working on my laptop. I tried kernel 2.3.99 which has all the bits for CardBus cards, but that won't recognise my boot device, even if I pass root=/dev/hda5 as a kernel argument. However, I've just realised that this usb stuff that the kernel keeps loading is assigning IRQ 9 to itself, the card has also assigned IRQ 9 to itself. The problem with the card seems like an IRQ conflict because the card accepts all signals to it, but doesn't pass anything on, i.e. if it is pinged the I/O light flashes, but nothing gets through to the host machine. If I ping another machine from the host machine then the host machine thinks it is sending stuff to the card, but the card won't send it to a network. (I'm in good company here, Linus Torvalds has also had this problem with a Vaio and Xircom cards). Now, in /etc/pcmcia/config.opts, I've put 'exclude irq 9', but the card is still assigning itself irq 9. Then I tried to recompile the kernel without usb support (I don't need usb support and this machine will probably never go anywhere near a usb device). But it is *still* loading those &!*&^*! usb modules on start up. I checked my /usr/src/linux/.config file by hand, yes, usb support is turned OFF. I checked that I'm booting from my new kernel yes, I am. Why, oh, why is that &%*$* usb stuff still loading? If I can't banish usb to the underworld (i.e. off my computer), how do I get this usb rubbish to assign itself another IRQ or force the ethernet card to assign itself an irq that is not being used. If I go cat /proc/interrupts, I can see that irqs 3-7 and 10-12 are not being used. HELP!!! ------------- Paul Talacko http://www.seditiousdiaries.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
I'm a still trying to get this Xircom card working on my laptop. I tried kernel 2.3.99 which has all the bits for CardBus cards, but that won't HELP!!!
Sorry about the delay in responding to this - my IS department changed my email server and didn't bother telling anyone. Yesterday was a quiet day... Still, I got some work done for a change. ;) I had this problem. The problem was originally thought to be caused by Xircom shipping several types of cards, all slightly different from each other. It now appears that it's caused by a problem in the Xircom driver in the PCMCIA package, which was fixed a few weeks ago by Ingo Molnar. A new PCMCIA package came out a few days ago (see http://sourceforge.net/projects/pcmcia-cs/) which claims to have an update to the Xircom driver; whether this update includes Ingo's patch I don't know - I haven't installed it yet. The workaround (which I'm currently using) is to put the ethernet device into promiscuous mode with: ifconfig eth0 promisc -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
caused by Xircom shipping several types of cards, all slightly different from each other. It now appears that it's caused by a problem in the Xircom driver in the PCMCIA package, which was fixed a few weeks ago by Ingo Molnar. A new PCMCIA package came out a few days ago (see http://sourceforge.net/projects/pcmcia-cs/) which claims to have an update to the Xircom driver; whether this update includes Ingo's patch I don't know - I haven't installed it yet.
I got that package 3.1.21 and installed it. It installed fine, but doesn't make any difference.
The workaround (which I'm currently using) is to put the ethernet device into promiscuous mode with:
ifconfig eth0 promisc
I also tried this, but it doesn't seem to make any difference either. One funny thing though. Last night I tried: ping -f 10.0.0.2 and out of around 1000 packets 2 got through. So there is life somewhere. Maybe this indicates some sort of timing problem.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Looks like you have another flavour of the problem. Try running tcpdump on each machine when you do a ping. This should tell you if the data is coming out or going back, or what.
I got that package 3.1.21 and installed it. It installed fine, but doesn't make any difference.
The workaround (which I'm currently using) is to put the ethernet device into promiscuous mode with:
ifconfig eth0 promisc
I also tried this, but it doesn't seem to make any difference either.
One funny thing though. Last night I tried:
ping -f 10.0.0.2 and out of around 1000 packets 2 got through. So there is life somewhere. Maybe this indicates some sort of timing problem.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Thu, 12 Oct 2000, Derek Fountain wrote:
Looks like you have another flavour of the problem. Try running tcpdump on each machine when you do a ping. This should tell you if the data is coming out or going back, or what.
I've done that and there is some activity there - I just can't interpret the data. Hear is the output from the tcpdump (sorry to those who don't hate large lists of data). I've actually downgraded pcmcia-cs to 3.1.19 because according to a message on pcmcia.sourceforge.net the implementation of drivers is different in this than in 3.1.21 and one works on some configurations and one on the other. Also, something new has happened: on the machine with the Xircom card the keyboard has just frozen. I remember that this is a known bug. Question is, how to fix it. First this is the tcpdump from the machine I'm pinging to (machine 10.0.0.20, which has an NIC which works: 18:40:54.190000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0000 0010 a4c7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e322 0000 0000 0101 0010 a4c7 18:40:54.290000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0210 a4ff fec7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e222 0000 0000 0101 0010 a4c7 18:40:58.190000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0000 0010 a4c7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e322 0000 0000 0101 0010 a4c7 18:40:58.290000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0210 a4ff fec7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e222 0000 0000 0101 0010 a4c7 18:41:02.190000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0000 0010 a4c7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e322 0000 0000 0101 0010 a4c7 18:41:02.290000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0210 a4ff fec7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e222 0000 0000 0101 0010 a4c7 18:41:06.190000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0000 0010 a4c7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e322 0000 0000 0101 0010 a4c7 18:41:06.290000 0:10:a4:c7:27:ae 33:33:0:0:0:2 86dd 70: 6000 0000 0010 3aff fe80 0000 0000 0000 0210 a4ff fec7 27ae ff02 0000 0000 0000 0000 0000 0000 0002 8500 e222 0000 0000 0101 0010 a4c7 18:41:35.230000 arp who-has 10.0.0.2 tell 10.0.0.1 18:41:35.230000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:41:36.220000 arp who-has 10.0.0.2 tell 10.0.0.1 18:41:36.220000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:41:43.940000 arp who-has 10.0.0.2 tell 10.0.0.1 18:41:43.940000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:03.940000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:03.940000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:03.940000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:03.940000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:13.950000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:13.950000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:23.960000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:23.960000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:33.960000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:33.960000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:43.960000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:43.960000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:42:53.960000 arp who-has 10.0.0.2 tell 10.0.0.1 18:42:53.960000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:43:03.960000 arp who-has 10.0.0.2 tell 10.0.0.1 18:43:03.960000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:43:13.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:43:13.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:43:23.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:43:23.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:43.980000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:43.980000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.980000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.980000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.980000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.980000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.980000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.980000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.990000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.990000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.990000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.990000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.990000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.990000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:53.990000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:53.990000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:44:54.000000 arp who-has 10.0.0.2 tell 10.0.0.1 18:44:54.000000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 18:45:03.970000 arp who-has 10.0.0.2 tell 10.0.0.1 18:45:03.970000 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 Now here is the machne I was pining from (host: 10.0.0.1) this has the Xircom card in it: 18:51:32.251780 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:32.351777 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS 18:51:36.251779 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:36.351775 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS 18:51:40.251772 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:40.351756 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS 18:52:09.284548 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:10.281785 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:17.991758 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:27.991771 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:37.991755 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:47.991755 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:52:58.002745 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:08.011751 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:18.011747 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:28.011754 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:38.011747 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:48.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:53:58.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:08.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:18.011747 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:28.011747 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:38.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:48.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:54:58.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:08.011746 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:18.011749 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.011748 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015960 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015967 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015974 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015980 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015985 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015991 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.015997 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016002 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016008 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016014 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016020 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016026 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016031 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016037 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:28.016043 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:38.011750 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.011754 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.031978 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.031986 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.031992 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.031998 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032003 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032009 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032014 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032020 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032025 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032031 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032037 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032043 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032048 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032054 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.032060 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.027804 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027811 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027815 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027819 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027822 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027827 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027831 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027835 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027839 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027843 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027847 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027851 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027855 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027859 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027863 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027868 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027872 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027876 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027880 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027885 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027889 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027893 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027897 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027902 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027923 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027927 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027930 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027933 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027937 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027941 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027944 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.027948 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037448 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037456 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037461 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037467 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037473 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037478 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037484 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037490 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037495 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:55:48.037395 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037399 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037401 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037404 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037407 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037410 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037413 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037416 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.037419 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.041678 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.041681 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:48.041684 arp reply 10.0.0.2 is-at 0:c0:f0:53:0:74 (0:10:a4:c7:27:ae) 18:55:58.021749 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) 18:56:08.021750 arp who-has 10.0.0.2 tell 10.0.0.1 (0:10:a4:c7:27:ae) Thanks for your help
I got that package 3.1.21 and installed it. It installed fine, but doesn't make any difference.
The workaround (which I'm currently using) is to put the ethernet device into promiscuous mode with:
ifconfig eth0 promisc
I also tried this, but it doesn't seem to make any difference either.
One funny thing though. Last night I tried:
ping -f 10.0.0.2 and out of around 1000 packets 2 got through. So there is life somewhere. Maybe this indicates some sort of timing problem.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Paul Talacko wrote:
Looks like you have another flavour of the problem. Try running tcpdump on each machine when you do a ping. This should tell you if the data is coming out or going back, or what.
I've done that and there is some activity there - I just can't interpret the data. Hear is the output from the tcpdump (sorry to those who don't hate large lists of data). I've actually downgraded pcmcia-cs to 3.1.19 because according to a message on pcmcia.sourceforge.net the implementation of drivers is different in this than in 3.1.21 and one works on some configurations and one on the other. Also, something new has happened: on the machine with the Xircom card the keyboard has just frozen. I remember that this is a known bug. Question is, how to fix it.
On Fri, 13 Oct 2000, Derek Fountain wrote:
Odd. I've never seen it happen like that before. It seems the arp requests are going out of the Xircom, being received and responded to by the other end, but then the arp replies are being stored up somewhere - probably in the Xircom card or it's driver - before being released back to the Xircom host all in one great flood. The Xircom host isn't able to understand those arp responses and never tries to issue the ICMP echo response request.
The only thing I can suggest is that the IRQ from the Xircom isn't working correctly, but that appears to be an avenue you've explored.
I will ask on one of the PCMCIA lists, may be this is the bug that will get them to get the whole thing working :-). Anyway, on the irq problem I'm stumped. The ethernet portion of the card, insists on irq9 even though I've got 'irq 9 exclude' in the pcmcia.opts file and even though in rc.config I've got PCMCIA_PCIC_OPTS=""irq_list=7,10,11,12". I don't understand. Also, on the ipv6 stuff. I saw that, but have no idea how to turn it off. On the up side the modem works fine. I used it to download kernel 2.4.0-test9 last night and it is great. Only problem is that that kernel hangs on bootup - it's a known bug which I didn't know about when I compiled that kernel. Paul
I'm afraid I'm beaten. Perhaps someone on one of the PCMCIA lists can help you?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On the up side the modem works fine. I used it to download kernel 2.4.0-test9 last night and it is great. Only problem is that that kernel hangs on bootup - it's a known bug which I didn't know about when I compiled that kernel.
Er, which version of the kernel are you struggling with - 2.2 or 2.4pre? My comments have assumed 2.2... -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Fri, 13 Oct 2000, Derek Fountain wrote:
On the up side the modem works fine. I used it to download kernel 2.4.0-test9 last night and it is great. Only problem is that that kernel hangs on bootup - it's a known bug which I didn't know about when I compiled that kernel.
Er, which version of the kernel are you struggling with - 2.2 or 2.4pre? My comments have assumed 2.2...
2.2. I just tried 2.4pre last night because there was a message from someone saying that with one of the 2.4pre ones the Xircom card works. But I'm still sticking with 2.2.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Fri, 13 Oct 2000, Derek Fountain wrote:
Odd. I've never seen it happen like that before. It seems the arp requests are going out of the Xircom, being received and responded to by the other end, but then the arp replies are being stored up somewhere - probably in the Xircom card or it's driver - before being released back to the Xircom host all in one great flood. The Xircom host isn't able to understand those arp responses and never tries to issue the ICMP echo response request.
Well....it works now. Over the weekend, I found my /usr partition went south in a major way. No amount of fscking could fix the problems. Solution - reformat with block checking and reinstall everything. Recompiled the kernel and pcmcia-cs 3.1.21 and er.... it works. In fact, the card works very, very well and if we could be sure it could run this well on all Linux machines I'd recommend it to everyone. Anyway, thanks for your help. At least through all this mess I've learnt loads about pcmcia and linux development :-) Paul
The only thing I can suggest is that the IRQ from the Xircom isn't working correctly, but that appears to be an avenue you've explored.
I'm afraid I'm beaten. Perhaps someone on one of the PCMCIA lists can help you?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Paul Talacko wrote:
On Thu, 12 Oct 2000, Derek Fountain wrote:
Looks like you have another flavour of the problem. Try running tcpdump on each machine when you do a ping. This should tell you if the data is coming out or going back, or what.
I've done that and there is some activity there - I just can't interpret the data. Hear is the output from the tcpdump (sorry to those who don't hate large lists of data). I've actually downgraded pcmcia-cs to 3.1.19 because according to a message on pcmcia.sourceforge.net the implementation of drivers is different in this than in 3.1.21 and one works on some configurations and one on the other. Also, something new has happened: on the machine with the Xircom card the keyboard has just frozen. I remember that this is a known bug. Question is, how to fix it.
First this is the tcpdump from the machine I'm pinging to (machine 10.0.0.20, which has an NIC which works:
Now here is the machne I was pining from (host: 10.0.0.1) this has the Xircom card in it:
18:51:32.251780 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:32.351777 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS 18:51:36.251779 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:36.351775 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS 18:51:40.251772 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:40.351756 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS
^ Maybe your using IPV6 protocal and shouldn't be??? |
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Mark Hounschell dmarkh@cfl.rr.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
18:51:40.251772 fe80::10:a4c7:27ae > ff02::2 icmpv6: RS 18:51:40.351756 fe80::210:a4ff:fec7:27ae > ff02::2 icmpv6: RS ^ Maybe your using IPV6 protocal and shouldn't be??? |
I did see that, but I have zero knowledge of IPv6 or ICMPv6. I wasn't even sure the tcpdump output meant it was IPv6 that was being used. (I hope someone jumps into the much lamented Richard Stevens' shoes and writes an up to date book on the latest comms protocols soon.) Maybe the original poster could try switching to IPv4 if IPv6 is being used. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Fri, 13 Oct 2000, Mark Hounschell wrote:
^ Maybe your using IPV6 protocal and shouldn't be??? |
How do I turn it off?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Mark Hounschell dmarkh@cfl.rr.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi Paul,,, On Wed, 11 Oct 2000, Paul Talacko wrote:
I'm a still trying to get this Xircom card working on my laptop. I tried kernel 2.3.99 which has all the bits for CardBus cards, but that won't recognise my boot device, even if I pass root=/dev/hda5 as a kernel argument.
Just a shot in the dark, but do you have a dos diskette for your Xircom? Maybe run the setup in dos and assign the card another IRQ. Hope this helps... Jim Hatridge hatridge@straubing.baynet.de Proud Linux User #88484 Owner -- bewulf-newbie list VOTE Harry Browne www.HarryBrowne2000.org and www.lp.org ------------------------------------------------------------------------ Jim's Beowulf Project Looking for giveaway computers and parts I need it all! Email Jim for details on how you can help build a poor man's super computer. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (4)
-
dmarkh＠cfl.rr.com -
fountai＠hursley.ibm.com -
hatridge＠straubing.baynet.de -
talacko＠yarn.demon.co.uk