Try ifconfig eth0 192.168.1.20 up. Dmesg can often give good information on Hardware detection. If problems persist, check that the card is seated properly. Maybe move it to another slot. Brian Marr On Wednesday 26 December 2001 17:09, you wrote:
Hey all & happy holidays...
I was wondering if anyone might have some insight into a network problem I'm having.
My networking setup in SuSE 7.1 was working flawlessly. Then I backed up everything and installed 7.3, but with the same settings I'm unable to get my network back up. Just to test my sanity I reinstalled 7.1, got the network back up, and did an upgrade install to 7.3. Sure enough 7.3 mucked up my settings somehow.
Anyway, if you're still with me and don't mind having a look at some info I procured, I sure appreciate your time. Sorry if there's redundant info here (please skip right on over it)...
Setting up the 'Network Configuration' via Yast/Yast2 produces no errors. But I can't 'ping' myself. $ ping 192.168.1.20 connect: Network is unreachable
--------------------------------------------
The PCMCIA HOWTO claims that 'Network is unreachable' is "foolproof indication of a routing error", but the routing info (only a static IP address & netmask) is identical to my 7.1 settings.
Ok, I'll start from the beginning. I have a LinkSys PC Card - NP100. 'SUPPORTED.CARDS' lists a 'Linksys NP100 Network Everywhere v2' (w/axnet_cs driver) and a 'Linksys NP100 Network Everywhere' (w/pcnet-cs driver).
--------------------------------------------
Here's what cardctl tells me. (v2?) $ cardctl ident Socket 0: product info: "Network Everywhere", "Fast Ethernet 10/100 PC Card", "2.0", " " manfid: 0x0149, 0xc1ab function: 6 (network)
--------------------------------------------
proc/net/dev shows no sign of 'eth0' (I believe 'eth0' was automatically detected in 7.1) $ cat /proc/net/dev Inter-| Receive
| Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 5360 79 0 0 0 0 0 0 5360 79 0 0 0 0 0 0 sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
--------------------------------------------
And 'ifconfig' doesn't list 'eth0' either (only 'lo'?). $ ifconfig
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
--------------------------------------------
And 'route' also gives me absolutely nothing (i.e., no 'eth0'). $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface
--------------------------------------------
Is my problem with resource assignments? Here's my interrupts. $ cat /proc/interrupts CPU0 0: 192611 XT-PIC timer 1: 10364 XT-PIC keyboard 2: 0 XT-PIC cascade 8: 2 XT-PIC rtc 11: 4 XT-PIC usb-ohci, i82365 12: 13650 XT-PIC PS/2 Mouse 14: 10213 XT-PIC ide0 15: 5 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0 MIS: 0
--------------------------------------------
And my ioports. cat /proc/ioports 0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02f8-02ff : PCI device 11c1:0441 0376-0376 : ide1 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0cf8-0cff : PCI conf1 1800-180f : PCI device 1179:0103 1800-1807 : ide0 1808-180f : ide1 1c00-1cff : PCI device 11c1:0441 ffe0-ffff : PCI device 1179:0701
--------------------------------------------
Now here's a section from '/var/log/messages'. I don't understand much here... Some IRQ problems? It does show a load attempt of the 'axnet_cs' driver, but at the bottom there's a problem. ... Dec 26 08:32:41 boo kernel: Linux PCMCIA Card Services 3.1.28 Dec 26 08:32:41 boo kernel: kernel build: 2.4.10-4GB #1 Tue Oct 9 00:11:42 GMT 2001 Dec 26 08:32:41 boo kernel: options: [pci] [cardbus] [apm] Dec 26 08:32:42 boo kernel: Intel PCIC probe: <4>PCI: No IRQ known for interrupt pin A of device 00:13.0. Please try using pci=biosirq. Dec 26 08:32:42 boo kernel: PCI: No IRQ known for interrupt pin B of device 00:13.1. Please try using pci=biosirq. Dec 26 08:32:42 boo kernel: Dec 26 08:32:42 boo kernel: Toshiba ToPIC97 rev 07 PCI-to-CardBus at slot 00:13, mem 0x10000000 Dec 26 08:32:42 boo kernel: host opts [0]: [slot 0xf0] [ccr 0x11] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 20/20] Dec 26 08:32:42 boo kernel: host opts [1]: [slot 0xf0] [ccr 0x21] [cdr 0x86] [rcr 0x02] [no pci irq] [lat 168/176] [bus 21/21] Dec 26 08:32:42 boo kernel: ISA irqs (default) = 4,5,7,9,10,12 polling interval = 1000 ms Dec 26 08:32:42 boo rcpcmcia: /sbin/insmod /lib/modules/2.4.10-4GB/pcmcia-external/ds.o Dec 26 08:32:43 boo cardmgr[414]: starting, version is 3.1.28 Dec 26 08:32:43 boo cardmgr[414]: modpath = /lib/modules/2.4.10-4GB/ Dec 26 08:32:43 boo cardmgr[414]: modsubdir = pcmcia-external Dec 26 08:32:43 boo cardmgr[414]: watching 2 sockets Dec 26 08:32:43 boo cardmgr[414]: initializing socket 0 Dec 26 08:32:43 boo kernel: cs: memory probe 0x0d0000-0x0dffff: clean. Dec 26 08:32:43 boo cardmgr[414]: socket 0: Generic AX88190 or pcnet Fast Ethernet Dec 26 08:32:43 boo cardmgr[414]: executing: 'insmod -v /lib/modules/2.4.10-4GB//pcmcia-external/axnet_cs.o' Dec 26 08:32:43 boo cardmgr[414]: + Using /lib/modules/2.4.10-4GB//pcmcia-external/axnet_cs.o Dec 26 08:32:43 boo cardmgr[414]: + Symbol version prefix '' Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x2f8-0x2ff 0x330-0x337 0x388-0x38f 0x3c0-0x3df 0x480-0x48f Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0230-0x02f7: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0300-0x032f: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0338-0x0387: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0390-0x03bf: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x03e0-0x047f: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0490-0x04cf: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x04d8-0x04ff: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0800-0x08ff: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0a00-0x0aff: clean. Dec 26 08:32:43 boo kernel: cs: IO port probe 0x0c00-0x0cff: clean. Dec 26 08:32:43 boo kernel: axnet_cs: this is not an AX88190 card! Dec 26 08:32:43 boo kernel: axnet_cs: use pcnet_cs instead ... --------------------------------------------
Nonetheless, an 'lsmod' shows 'axnet_cs' loaded. $ lsmod Module Size Used by axnet_cs 11456 0 (unused) ds 6832 2 [axnet_cs] i82365 23296 2 pcmcia_core 43008 0 [axnet_cs ds i82365] ipv6 124736 -1 (autoclean) evdev 4160 0 (unused) input 3072 0 [evdev] usb-ohci 17680 0 (unused) iptable_nat 12656 0 (autoclean) (unused) ip_conntrack 12848 1 (autoclean) [iptable_nat] iptable_filter 1728 0 (autoclean) (unused) ip_tables 10496 4 [iptable_nat iptable_filter] nls_euc-jp 4064 2 (autoclean) nls_cp932 76496 3 (autoclean) reiserfs 147920 1 usbcore 47264 1 [usb-ohci]
--------------------------------------------
If I remove the 'axnet_cs' module and try to load 'pcnet_cs' as recommend in /var/log/messages (last line above), I get the error "pcnet_cs: Card Services release does not match!" in 'dmesg'. $ modprobe pcnet_cs /lib/modules/2.4.10-4GB/kernel/drivers/net/pcmcia/pcnet_cs.o: init_module: Operation not permitted Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.10-4GB/kernel/drivers/net/pcmcia/pcnet_cs.o: insmod /lib/modules/2.4.10-4GB/kernel/drivers/net/pcmcia/pcnet_cs.o failed
--------------------------------------------
I don't know if this help, but here's 'lspci'. $ lspci 00:00.0 Host bridge: Toshiba America Info Systems 601 (rev a2) 00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01) 00:08.0 VGA compatible controller: S3 Inc. ViRGE/MX (rev 06) 00:0b.0 USB Controller: NEC Corporation USB (rev 02) 00:10.0 IDE interface: Toshiba America Info Systems: Unknown device 0103 (rev 34) 00:11.0 Communication controller: Toshiba America Info Systems FIR Port (rev 23) 00:13.0 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07) 00:13.1 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
--------------------------------------------
Lastly, 'rcnetwork start' does nothing useful that I can see. $ rcnetwork start $
--------------------------------------------
And 'rcnetwork start' w/the addition of 'eth0' gives me this. $ rcnetwork start eth0 Setting up network device eth0 SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFBRDADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device eth0: unknown interface: No such device
failed Please run `rcroute start' to restore the routings.
--------------------------------------------
Also, 'eth0' is no where to be found in 'dmesg' start-up messages.
--------------------------------------------
Sorry to have you read all this...
Eric
__________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com