| 1 |
On Monday 13 December 2010 07:44:51 Stroller wrote: |
| 2 |
> I have a fairly old laptop, but which has a really nice screen and which is |
| 3 |
> actually still quite useful for some simple tasks and for "thin clienting" |
| 4 |
> and stuff. I like to keep it around as a spare, at least. For one thing I |
| 5 |
> want to use it for some network diagnostics, and I want to use it with an |
| 6 |
> old 10mbps 3Com PCMCIA network card. The performance would seem to be |
| 7 |
> adequate for sniffing web-suring traffic (for instance) if I bridge it |
| 8 |
> with the laptop's internal network card. |
| 9 |
> |
| 10 |
> However, the 3Com network card doesn't seem to be recognised under my |
| 11 |
> installation of Gentoo. |
| 12 |
> |
| 13 |
> When I insert the card I see only this in /var/log/messages: |
| 14 |
> |
| 15 |
> Dec 13 06:45:42 stinky kernel: pcmcia_socket pcmcia_socket0: pccard: PCMCIA |
| 16 |
> card inserted into slot 0 |
| 17 |
> |
| 18 |
> And nothing else. Only the onboard network card is shown: |
| 19 |
> |
| 20 |
> $ ifconfig | grep -i hwadd |
| 21 |
> eth0 Link encap:Ethernet HWaddr 00:00:86:42:58:2c |
| 22 |
> $ |
| 23 |
> |
| 24 |
> The network will not start: |
| 25 |
> |
| 26 |
> $ sudo /etc/init.d/net.eth1 start |
| 27 |
> * Starting eth1 |
| 28 |
> * Configuration not set for eth1 - assuming DHCP |
| 29 |
> * Bringing up eth1 |
| 30 |
> * dhcp |
| 31 |
> * network interface eth1 does not exist |
| 32 |
> * Please verify hardware or kernel module (driver) |
| 33 |
> [ !! ] |
| 34 |
> $ |
| 35 |
> |
| 36 |
> If I plug in a wifi card it behaves as I'd expect: |
| 37 |
> |
| 38 |
> Dec 13 07:36:09 stinky kernel: pcmcia_socket pcmcia_socket0: pccard: |
| 39 |
> CardBus card inserted into slot 0 Dec 13 07:36:09 stinky kernel: pci |
| 40 |
> 0000:02:00.0: reg 10: [mem 0xffffe000-0xffffffff] Dec 13 07:36:09 stinky |
| 41 |
> kernel: pci 0000:02:00.0: BAR 0: assigned [mem 0x24000000-0x24001fff] Dec |
| 42 |
> 13 07:36:09 stinky kernel: pci 0000:02:00.0: BAR 0: set to [mem |
| 43 |
> 0x24000000-0x24001fff] (PCI address [0x24000000-0x24001fff] Dec 13 |
| 44 |
> 07:36:10 stinky kernel: cfg80211: Calling CRDA to update world regulatory |
| 45 |
> domain Dec 13 07:36:10 stinky kernel: rt2500pci 0000:02:00.0: enabling |
| 46 |
> device (0000 -> 0002) Dec 13 07:36:10 stinky kernel: rt2500pci |
| 47 |
> 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 Dec |
| 48 |
> 13 07:36:10 stinky kernel: rt2500pci 0000:02:00.0: setting latency timer |
| 49 |
> to 64 Dec 13 07:36:10 stinky kernel: phy0: Selected rate control algorithm |
| 50 |
> 'minstrel' Dec 13 07:36:10 stinky kernel: Registered led device: |
| 51 |
> rt2500pci-phy0::radio Dec 13 07:36:10 stinky kernel: Registered led |
| 52 |
> device: rt2500pci-phy0::quality |
| 53 |
> |
| 54 |
> |
| 55 |
> |
| 56 |
> Compare with when I try with system rescue CD: |
| 57 |
> |
| 58 |
> root@sysresccd /root % ifconfig | grep HWaddr |
| 59 |
> eth0 Link encap:Ethernet HWaddr 00:00:86:42:58:2c |
| 60 |
> eth1 Link encap:Ethernet HWaddr 00:60:08:92:94:df |
| 61 |
> root@sysresccd /root % |
| 62 |
> |
| 63 |
> and this appears in /var/log/messages: |
| 64 |
> |
| 65 |
> Dec 13 06:54:26 sysresccd kernel: pcmcia_socket pcmcia_socket0: pccard: |
| 66 |
> PCMCIA card inserted into slot 0 Dec 13 06:54:26 sysresccd kernel: pcmcia |
| 67 |
> 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 4) Dec 13 06:54:26 |
| 68 |
> sysresccd kernel: 3c589_cs 0.0: eth1: 3Com 3c589, io 0x300, irq 4, hw_addr |
| 69 |
> 00:60:08:92:94:df Dec 13 06:54:26 sysresccd kernel: 3c589_cs 0.0: eth1: |
| 70 |
> 8K FIFO split 5:3 Rx:Tx, auto xcvr ... |
| 71 |
> Dec 13 06:54:38 sysresccd kernel: 3c589_cs 0.0: eth1: flipped to 10baseT |
| 72 |
> Dec 13 06:54:38 sysresccd NetworkManager: <info> DHCP: device eth1 state |
| 73 |
> changed preinit -> bound Dec 13 06:54:38 sysresccd NetworkManager: <info> |
| 74 |
> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Dec 13 |
| 75 |
> 06:54:38 sysresccd NetworkManager: <info> Activation (eth1) Stage 4 of 5 |
| 76 |
> (IP Configure Get) started... Dec 13 06:54:38 sysresccd NetworkManager: |
| 77 |
> <info> address 192.168.1.102 Dec 13 06:54:38 sysresccd NetworkManager: |
| 78 |
> <info> prefix 24 (255.255.255.0) Dec 13 06:54:38 sysresccd |
| 79 |
> NetworkManager: <info> gateway 192.168.1.1 Dec 13 06:54:38 sysresccd |
| 80 |
> NetworkManager: <info> hostname 'Vigor102' Dec 13 06:54:38 sysresccd |
| 81 |
> NetworkManager: <info> nameserver '192.168.1.43' Dec 13 06:54:38 |
| 82 |
> sysresccd NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP |
| 83 |
> Configure Commit) scheduled... Dec 13 06:54:38 sysresccd NetworkManager: |
| 84 |
> <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Dec 13 |
| 85 |
> 06:54:38 sysresccd dhclient: DHCPACK from 192.168.1.1 |
| 86 |
> Dec 13 06:54:38 sysresccd dhclient: bound to 192.168.1.102 -- renewal in |
| 87 |
> 101292 seconds. Dec 13 06:54:38 sysresccd NetworkManager: <info> |
| 88 |
> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Dec 13 |
| 89 |
> 06:54:39 sysresccd NetworkManager: nm_ip4_config_add_nameserver: assertion |
| 90 |
> `nameserver != s' failed Dec 13 06:54:39 sysresccd NetworkManager: |
| 91 |
> nm_ip4_config_add_nameserver: assertion `nameserver != s' failed Dec 13 |
| 92 |
> 06:54:39 sysresccd NetworkManager: <info> Policy set 'Auto eth0' (eth0) |
| 93 |
> as default for routing and DNS. Dec 13 06:54:39 sysresccd NetworkManager: |
| 94 |
> <info> (eth1): device state change: 7 -> 8 (reason 0) Dec 13 06:54:39 |
| 95 |
> sysresccd NetworkManager: <info> Activation (eth1) successful, device |
| 96 |
> activated. Dec 13 06:54:39 sysresccd NetworkManager: <info> Activation |
| 97 |
> (eth1) Stage 5 of 5 (IP Configure Commit) complete. Dec 13 06:54:41 |
| 98 |
> sysresccd kernel: eth1: no IPv6 routers present |
| 99 |
> Dec 13 06:54:46 sysresccd dhcpcd[2469]: eth0: carrier lost |
| 100 |
> Dec 13 06:54:46 sysresccd NetworkManager: <info> (eth0): carrier now OFF |
| 101 |
> (device state 8) Dec 13 06:54:46 sysresccd NetworkManager: <info> (eth0): |
| 102 |
> device state change: 8 -> 2 (reason 40) Dec 13 06:54:46 sysresccd |
| 103 |
> NetworkManager: <info> (eth0): deactivating device (reason: 40). Dec 13 |
| 104 |
> 06:54:47 sysresccd NetworkManager: <info> eth0: canceled DHCP |
| 105 |
> transaction, dhcp client pid 2076 Dec 13 06:54:47 sysresccd |
| 106 |
> NetworkManager: <info> Policy set 'Auto eth1' (eth1) as default for |
| 107 |
> routing and DNS. |
| 108 |
> |
| 109 |
> (snipped for brevity, but see attached systemrescuecd-messages.txt.gz) |
| 110 |
> |
| 111 |
> The last lines of the above, referring to eth0, are when I unplugged the |
| 112 |
> built-in network card to use the ethernet cable with the PCMCIA card. I |
| 113 |
> was able to ssh in just fine. |
| 114 |
> |
| 115 |
> The two cards are shown in `ifconfig`, but strangely not by `lspci`: |
| 116 |
> |
| 117 |
> root@sysresccd /root % ifconfig | grep HWaddr |
| 118 |
> eth0 Link encap:Ethernet HWaddr 00:00:86:42:58:2c |
| 119 |
> eth1 Link encap:Ethernet HWaddr 00:60:08:92:94:df |
| 120 |
> root@sysresccd /root % lspci -vt |
| 121 |
> -[0000:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host |
| 122 |
> bridge +-01.0-[01]----00.0 S3 Inc. 86C270-294 Savage/IX-MV |
| 123 |
> +-02.0 Texas Instruments PCI1450 |
| 124 |
> +-02.1 Texas Instruments PCI1450 |
| 125 |
> +-03.0 3Com Corporation 3c556B CardBus [Tornado] # <--- |
| 126 |
> onboard card +-03.1 3Com Corporation Mini PCI 56k Winmodem |
| 127 |
> +-05.0 Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion |
| 128 |
> Audio Accelerator] +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA |
| 129 |
> +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE |
| 130 |
> +-07.2 Intel Corporation 82371AB/EB/MB PIIX4 USB |
| 131 |
> \-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI |
| 132 |
> root@sysresccd /root % |
| 133 |
> |
| 134 |
> The thing that really confounds me is that the two kernels are compiled |
| 135 |
> with *very* similar options. See attached config files. If you view them |
| 136 |
> using a command such as: |
| 137 |
> |
| 138 |
> colordiff -y kernel.config.sys_rescue_cd-1.6.4 kernel.config.current | |
| 139 |
> less |
| 140 |
> |
| 141 |
> then you'll see they're nearly identical. I have been criticised in the |
| 142 |
> past for being so lazy as to just use systemrescuecd's kernel config, |
| 143 |
> rather than spending the time to make my own, but it's never given me any |
| 144 |
> problems in the past and I don't see how it could have caused this. I'm |
| 145 |
> really stumped, as everything else seems to work fine. |
| 146 |
> |
| 147 |
> The only things I've done is to recompile my kernel a couple of times - |
| 148 |
> once to add in the drivers statically (CONFIG_PCMCIA_3C589=y), instead of |
| 149 |
> as modules, to see if that would make a difference, and second time to |
| 150 |
> match another PCMCIA option that differed. Neither made any difference. |
| 151 |
> |
| 152 |
> The two kernels are slightly different versions, but I wouldn't have |
| 153 |
> expected that to make any difference. The only thing I can think is that |
| 154 |
> I'm overlooking something really stupid. I'd be very grateful for any |
| 155 |
> advice. |
| 156 |
|
| 157 |
What do you get in log messages and dmesg when you compile |
| 158 |
CONFIG_PCMCIA_3C589=m and run modprobe -v |
| 159 |
|
| 160 |
-- |
| 161 |
Regards, |
| 162 |
Mick |
Archives