Suse 9.1 3Com 3c59x can't get to the network

Paul Warner

18 Sep 2004 18 Sep '04

22:30

I just installed Suse 9.1 on a Thinkpad laptop, dual booting with Windows 2000. Linux kernel is: 2.6.4-52-default #1 Wed. Apr 7 2004 During the install, the probe did not discover the builtin ethernet adapter, but it did discover the pcmcia card network adapter I have, 3Com 3c556B Hurricane CardBus, module 3c59x. I configured this card with a static ip for my home network, and told it that the default gateway was my Linksys router. But I cannot access the internet. I can't get out with the browser, can't ping hostnames or ip addresses. When I ping, I get the message Destination Host Unreachable. The little green light on the dongle doesn't flicker, but stays on all the time. We have about 5 computers of various operating systems, from Windows XP to Mac Os X to FreeBSD and all can access the internet using this network just fine. A previous install of Suse 7.1 on this same machine also worked using the 3Com card (it also didn't seem to know about the builtin NIC). ifconfig looks like this: eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr fe80::fdff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 Rx packets:0 errors:0 dropped:0 overruns:0 frame:0 Tx packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0(0.0b) TX bytes: 0 (0.0 b) Interrupt:11 Base address 0x1800 ifstatus eth0 eth0 device: 3Com Corporation 3c556B Hurricane CardBus (rev 20) eth0 configuration: eth-id-ff:ff:ff:ff:ff:ff eth0 is up etc. The system knows about the card and THINKS it is configured correctly. I have been through Yast several times, and I can't see what is wrong. I have looked through the admin guide and user guide, and searched for the answer in the archives and on google. I have seen one vague mention of driver conflicts, but haven't come up with anything that was helpful (yet). Many thanks for any suggestions. Thanks, Paul Warner

Show replies by date

ti＠amb.org

19 Sep 19 Sep

00:07

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

Paul Warner writes:

...

During the install, the probe did not discover the builtin ethernet adapter, but it did discover the pcmcia card network adapter I have, 3Com 3c556B Hurricane CardBus, module 3c59x. I configured this card with a static ip for my home network, and told it that the default gateway was my Linksys router.

But I cannot access the internet. I can't get out with the browser, can't ping hostnames or ip addresses. When I ping, I get the message Destination Host Unreachable. The little green light on the dongle ...

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr fe80::fdff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 Rx packets:0 errors:0 dropped:0 overruns:0 frame:0 Tx packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0(0.0b) TX bytes: 0 (0.0 b) Interrupt:11 Base address 0x1800

Did you set up a proper default gateway? Try 'netstat -rn' -Ti

Paul Warner

07:49

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sat, 18 Sep 2004 17:07:44 -0700 (PDT), Ti Kan wrote:

...

Paul Warner writes:

...
During the install, the probe did not discover the builtin ethernet adapter, but it did discover the pcmcia card network adapter I have, 3Com 3c556B Hurricane CardBus, module 3c59x. I configured this card with a static ip for my home network, and told it that the default gateway was my Linksys router.

But I cannot access the internet. I can't get out with the browser, can't ping hostnames or ip addresses. When I ping, I get the message Destination Host Unreachable. The little green light on the dongle ...

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr fe80::fdff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 Rx packets:0 errors:0 dropped:0 overruns:0 frame:0 Tx packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0(0.0b) TX bytes: 0 (0.0 b) Interrupt:11 Base address 0x1800

Did you set up a proper default gateway? Try 'netstat -rn'

-Ti

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

In YAST, I definitely configured a static ip, not DHCP. Here is the result of netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 0 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 0 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 0 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 0 0 0 0 eth0 Suggestions? Thanks for your time! Regards, Paul

ti＠amb.org

08:35

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

Paul Warner writes:

...

...
...
But I cannot access the internet. I can't get out with the browser, can't ping hostnames or ip addresses. When I ping, I get the message Destination Host Unreachable. The little green light on the dongle ...

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr fe80::fdff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 Rx packets:0 errors:0 dropped:0 overruns:0 frame:0 Tx packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0(0.0b) TX bytes: 0 (0.0 b) Interrupt:11 Base address 0x1800

Did you set up a proper default gateway? Try 'netstat -rn'

Here is the result of netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 0 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 0 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 0 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 0 0 0 0 eth0

This shows that your default route is set up to go to 192.168.2.1, yet the Flags field does not show that it's a gateway (should be 'UG'). Is 192.168.2.1 a real working gateway node (i.e., a DSL router or your ISP's gateway) that routes to the internet? I think there is a configuration error in your /etc/sysconfig/network/routes file. It should simply contain a line that looks like: default x.x.x.x - - Where x.x.x.x is the IP number of yout Internet gateway. Also, check your /etc/sysconfig/network/ifcfg-eth* file. Pay particular attention to your NETWORK, NETMASK and BROADCAST lines. -Ti

Jerry Feldman

13:35

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 01:35:04 -0700 (PDT) ti@amb.org (Ti Kan) wrote:

...

Paul Warner writes:

...

...
Here is the result of netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window

irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 0 0

0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 0 0

0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 0 0

0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 0 0

0 0 eth0

This shows that your default route is set up to go to 192.168.2.1, yet the Flags field does not show that it's a gateway (should be 'UG'). Is 192.168.2.1 a real working gateway node (i.e., a DSL router or your ISP's gateway) that routes to the internet? In addition to what Ti mentioned, can you get to the Linksys from this box. Try ping -c1 192.168.2.1 or use your browser.

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Paul Warner

14:00

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 09:35:15 -0400, Jerry Feldman wrote:

...

On Sun, 19 Sep 2004 01:35:04 -0700 (PDT) ti@amb.org (Ti Kan) wrote:

...
Paul Warner writes:

...
...
Here is the result of netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window

irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 0 0

0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 0 0

0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 0 0

0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 0 0

0 0 eth0

This shows that your default route is set up to go to 192.168.2.1, yet the Flags field does not show that it's a gateway (should be 'UG'). Is 192.168.2.1 a real working gateway node (i.e., a DSL router or your ISP's gateway) that routes to the internet? In addition to what Ti mentioned, can you get to the Linksys from this box. Try ping -c1 192.168.2.1 or use your browser.

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Hi Jerry, ping -c1 192.168.2.1 results in DESTINATION HOST UNREACHABLE This is the same as attempts to use ping to access any other web site, either by name or ip address. And there IS a NETWORK line in /etc/syscontfig/networks/ifcfg-eth-id* NETWORK='192.168.2.0' Sorry for the mistakes. I am copying the info to another machine by hand... I can say that from all the other OS's/machines on my network, I can access the router via the browser, or ping, etc. Thanks, Paul

Jerry Feldman

14:37

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 15:00:27 +0100 Paul Warner wrote:

...

On Sun, 19 Sep 2004 09:35:15 -0400, Jerry Feldman wrote:

...

...
box. Try ping -c1 192.168.2.1 or use your browser.

...

ping -c1 192.168.2.1 results in DESTINATION HOST UNREACHABLE

This is the same as attempts to use ping to access any other web site, either by name or ip address.

And there IS a NETWORK line in /etc/syscontfig/networks/ifcfg-eth-id*

NETWORK='192.168.2.0'

Sorry for the mistakes. I am copying the info to another machine by hand... I can say that from all the other OS's/machines on my network, I can access the router via the browser, or ping, etc. It appears that we have a more basic problem. Let's go to YaST, click on Network Devices/Network Card. It should show that the card is already detected and display it as a PCMCIA device. I would completely delete this device and start over. Also for the time being set it up as automatic via DHCP. After completing the configuration, then see if you get an IP address from the router. If you are not able to get an IP address, then you may have a hardware issue. Check your cable, Remember that the Linksys routers have an uplink connector that shares itself with connector 1. Also, try unplugging and plugging in the card, and use dmesg to see what the kernel says.

(In general, when debugging, I always check the lowest level things first. In this case, the first step is can we see the router? The next step would be can we access another system on the same LAN. Then try to access an Internet site by its IP address. Then we check our DNS entries by trying to access a site by name. I also tend to go to YaST first, then to the network scripts, but I haven't found any major issues with the network scripts in SuSE for quite a while). Note that the 3Com cards have always been a bit problematical because there are several different modules. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Doug B

14:56

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sunday 19 September 2004 09:00 am, Paul Warner wrote:

...

ping -c1 192.168.2.1 results in DESTINATION HOST UNREACHABLE

This is the same as attempts to use ping to access any other web site, either by name or ip address.

I got curious and did a google search on '3Com Corporation 3c556B Hurricane CardBus'. One of the things turned up was: *******************************************

...

I posted this information on the forum without any response. The network card in my IBM Thinkpad A21m is a 3Com 556B mini PCI combo card (ethernet & modem). I have no interest in the modem side... (dumb winmodem) but the ethernet adapter worked OK in Knoppix 3.2 & 3.3. I checked the 3c59x.o driver's file size and it is the same in 3.3 and 3.4 so I'm guessing that it hasn't changed. Something has however as it is detected differently. Here is the output of lspci -v from the laptop under 3.3 and 3.4. Does anyone have any idea what changed to cause this to fail?

Knoppix 3.3 initialises the card correctly (3Com Corporation 3c556B Hurricane CardBus) and I get an IP address from the dhcp server. However the card is not detected correctly in Knoppix 3.4 (3Com Corporation 3c556B CardBus [Tornado]). This results in a MAC address of FF:FF:FF:FF:FF:FF.

Thanks in advance. Dallas

Try booting with knoppix acpi=off and/or noapic Maybe your board has (as many do) a faulty ACPI implementation that requires ACPI support to be turned off in the Kernel. ******************************************* Sounds like yours. The response was: ******************************************* Thanks Klaus, knoppix acpi=off did the trick. Regards Dallas ******************************************* Worth a shot. Also worth a shot (if you haven't done so already) is checking connections and trying different cables and ports on your router/switch. Doug

Jerry Feldman

15:08

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 09:56:55 -0500 Doug B wrote:

...

...
Knoppix 3.3 initialises the card correctly (3Com Corporation 3c556B Hurricane CardBus) and I get an IP address from the dhcp server. However the card is not detected correctly in Knoppix 3.4 (3Com Corporation 3c556B CardBus [Tornado]). This results in a MAC address of FF:FF:FF:FF:FF:FF.

This is an indication that the problem is with the 2.6 kernel module. The kernel guys changed the driver interface in 2.6, and some of the binary drivers for 2.4 have not been ported to 2.6 :-(

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Paul Warner

16:50

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 11:08:00 -0400, Jerry Feldman wrote:

...

On Sun, 19 Sep 2004 09:56:55 -0500 Doug B wrote:

...
...
Knoppix 3.3 initialises the card correctly (3Com Corporation 3c556B Hurricane CardBus) and I get an IP address from the dhcp server. However the card is not detected correctly in Knoppix 3.4 (3Com Corporation 3c556B CardBus [Tornado]). This results in a MAC address of FF:FF:FF:FF:FF:FF.

This is an indication that the problem is with the 2.6 kernel module. The kernel guys changed the driver interface in 2.6, and some of the binary drivers for 2.4 have not been ported to 2.6 :-(

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Yes, I'm worried that it is a kernel problem as well. I'm aware that with 9.1 all NIC drivers are now in the kernel. I deleted the settings for the card as suggested. It was correctly re-detected, and I reset it to use DHCP (and reset the other computers on the network). Now when I try to ping the router I get the message: connect: Network is unreachable I rebooted into windows on the same machine (you recall I'm dual-booting with win2k), and, after reconfiguring to use DHCP, I was able to surf the web using this pcmcia card and the same cable I was trying to use with the Suse 9.1 install. So this confirms that the card, dongle, cable and connection to the router are working for this computer. Of course Windows can see the other 3Com NIC, the one that is built in, but which seems to be a windows only variety. I disconnected that one for this test and used the pcmcia card. Is there a chance there is a kernel driver for this other nic card in the machine? It seems to be called 3Com 10/100 Mini PCI Ethernet Adapter... I guess that's extremely unlikely if the card isn't even detected by the probe. I searched on the web and can only see windows drivers for it. It's a shame that the pcmcia card no longer works, since it was purchased in the first place to work with Suse 7.1. So how exactly do I boot with acpi=off? I do appreciate all the help. I presume that if we trace this to the lack of a kernel driver, my only option is to go out and buy another (supported) NIC... I will need to know how to be sure I get one that has a 9.1 driver. Regards, Paul

Paul Warner

18:56

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

It so happens I have a Knoppix 3.3 cd. I tried it in this machine and it found the pcmcia NIC and could get out to the internet just fine. On Sun, 19 Sep 2004 11:08:00 -0400, Jerry Feldman wrote:

...

On Sun, 19 Sep 2004 09:56:55 -0500 Doug B wrote:

...
...
Knoppix 3.3 initialises the card correctly (3Com Corporation 3c556B Hurricane CardBus) and I get an IP address from the dhcp server. However the card is not detected correctly in Knoppix 3.4 (3Com Corporation 3c556B CardBus [Tornado]). This results in a MAC address of FF:FF:FF:FF:FF:FF.

This is an indication that the problem is with the 2.6 kernel module. The kernel guys changed the driver interface in 2.6, and some of the binary drivers for 2.4 have not been ported to 2.6 :-(

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Jerry Feldman

19:42

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 19:56:13 +0100 Paul Warner wrote:

...

It so happens I have a Knoppix 3.3 cd. I tried it in this machine and it found the pcmcia NIC and could get out to the internet just fine. The issue is definitely with the module for the 2.6 kernel. Your configuration should be ok. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Paul Warner

20 Sep 20 Sep

22:09

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

...

I got curious and did a google search on '3Com Corporation 3c556B Hurricane CardBus'. One of the things turned up was:

*******************************************

...
I posted this information on the forum without any response. The network card in my IBM Thinkpad A21m is a 3Com 556B mini PCI combo card (ethernet & modem). I have no interest in the modem side... (dumb winmodem) but the ethernet adapter worked OK in Knoppix 3.2 & 3.3. I checked the 3c59x.o driver's file size and it is the same in 3.3 and 3.4 so I'm guessing that it hasn't changed. Something has however as it is detected differently. Here is the output of lspci -v from the laptop under 3.3 and 3.4. Does anyone have any idea what changed to cause this to fail?

Knoppix 3.3 initialises the card correctly (3Com Corporation 3c556B Hurricane CardBus) and I get an IP address from the dhcp server. However the card is not detected correctly in Knoppix 3.4 (3Com Corporation 3c556B CardBus [Tornado]). This results in a MAC address of FF:FF:FF:FF:FF:FF.

Thanks in advance. Dallas

Try booting with

knoppix acpi=off

and/or noapic

Maybe your board has (as many do) a faulty ACPI implementation that requires ACPI support to be turned off in the Kernel.

******************************************* Sounds like yours. The response was: ******************************************* Thanks Klaus,

knoppix acpi=off

did the trick.

Regards Dallas *******************************************

Worth a shot.

Doug

I am sending this mail from my Thinkpad. IT WORKS! The one thing I hadn't tried was turning acpi and apic off, as Doug suggested above. I did it one at a time. I edited /etc/grub/menu.lst to add acpi=off to the linux boot line, and for the first time I got a proper mac address for the pcmcia card (not the FF:FF:FF:FF:FF:FF thing I got before). But still no network. I turned the firewall off, but no change...ping gave this response, as before: "connect: Network is unreachable" I was going to mail the list to report some headway but not success, and then I thought, well, I haven't tried noapic, so I added that to the menu.lst file and rebooted. And bingo, here I am surfing the web! I want to say a BIG thanks to everyone who gave me their thoughts. As I read through the posts on this list I can see it is a great community. I hope this thread is of some value to others. I wonder, in my ignorance, if some of the bootup and other peripherals problems (floppy drives, etc.) I'm reading about in the list couldn't be helped by turning apic and/or acpi off. And perhaps we should let the kernel guys know that there may be a problem with apic or acpi. Any suggestions on that? Thanks, Paul

Paul Warner

19 Sep 19 Sep

13:35

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

On Sun, 19 Sep 2004 01:35:04 -0700 (PDT), Ti Kan wrote:

...

Paul Warner writes:

...
...
...
But I cannot access the internet. I can't get out with the browser, can't ping hostnames or ip addresses. When I ping, I get the message Destination Host Unreachable. The little green light on the dongle ...

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr fe80::fdff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 Rx packets:0 errors:0 dropped:0 overruns:0 frame:0 Tx packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0(0.0b) TX bytes: 0 (0.0 b) Interrupt:11 Base address 0x1800

Did you set up a proper default gateway? Try 'netstat -rn'

Here is the result of netstat -rn

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 0 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 0 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 0 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 0 0 0 0 eth0

This shows that your default route is set up to go to 192.168.2.1, yet the Flags field does not show that it's a gateway (should be 'UG'). Is 192.168.2.1 a real working gateway node (i.e., a DSL router or your ISP's gateway) that routes to the internet?

I think there is a configuration error in your /etc/sysconfig/network/routes file. It should simply contain a line that looks like:

default x.x.x.x - -

Where x.x.x.x is the IP number of yout Internet gateway.

Also, check your /etc/sysconfig/network/ifcfg-eth* file. Pay particular attention to your NETWORK, NETMASK and BROADCAST lines.

Hi Ti, Oh, rats - yes, you would be right if I had only typed it correctly. But I typed the flags column wrong. I'm sorry. That column should be all U's, until the last line, which is UG. The darn thing should look like this: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 Yes, 192.168.2.1 is the working gateway (router) for all of the other machines on my home network, connecting to the outside world via our 'ISP'. This is the /etc/sysconfig/network/routes file: routes: 192.168.2.1 - - Here is the /etc/sysconfig/network/ifcfg-eth* file (note there is no NETWORK line): BOOTPROTO='static' BROADCAST='192.168.2.255' IPADDR='102.168.2.105' MTU='' NETMASK='255.255.255.0' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='somerandomstring' _nm_name='bus-pci-0000:00:03.0' Thanks! Regards, Paul

John Scott

20 Sep 20 Sep

15:51

New subject: [SLE] Suse 9.1 3Com 3c59x can't get to the network

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Warner wrote: | I just installed Suse 9.1 on a Thinkpad laptop, dual booting with Windows 2000. | Linux kernel is: 2.6.4-52-default #1 Wed. Apr 7 2004 | | During the install, the probe did not discover the builtin ethernet | adapter, but it did discover the pcmcia card network adapter I have, | 3Com 3c556B Hurricane CardBus, module 3c59x. I configured this card | with a static ip for my home network, and told it that the default | gateway was my Linksys router. | I had the same problem on my laptop with a Cisco 340 wireless. Card is seen and detected, gets an ip, etc, etc. Using the route command gave this: 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo Ah, no gateway. Type route add default gw <gateway ip> and hit enter. Issue route again: 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default ROUTER-1.1.h 0.0.0.0 UG 0 0 0 eth0 Everything works now. I've only had to do a route add when I change networks. Annoying, yeah, but I'm up and running in seconds. John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBTvxt5JB+bPW3+KwRAiBFAJ9j/lGN46DX1qaIY1Jd4/NHOX9LkACcCieQ AVRWw1RRkTQaBsx1JLCAx90= =Ok6F -----END PGP SIGNATURE-----

7168

Age (days ago)

7170

Last active (days ago)

List overview

Download

14 comments

5 participants

participants (5)

Doug B
Jerry Feldman
John Scott
Paul Warner
ti＠amb.org