Hi all,
I have had nothing short of internet headaches with suse..It started with suse version 9.3 which i never got connected..Then I went to 10.0 and it took two months to get connected..I now have 10.1 for a week and still no connection..tried all the 10.0 stuff.
From all the information I can find it seems to be located with the tulip driver for my eth0 card..In 10.0, I had to use the dmfe module and force it..At least that worked and still does..
It does not seem to work for 10.1 yet..
When I unplug this hard drive and use either Mandriva 2006 or Fedora FC4,5 no problems whatsoever networking..
Suse is and has been my favorite distro and I really hate to lose it..BTW the network is behind a linksys router/switch on cable(DHCP used)..
I can't even ping the router...Suse has found my "weak link in the chain" NETWORKING!!..
Does any one else use the tulip module on a desktop?
Someone said they wrote the driver for laptops..I don't know if thats true or not...
Thank you for reading this...
jolphil

Hi, I have some questions for you.

what does your ifconfig show? do you see your eth0 there?

Also whats the output of ??

It should give you three kernel modules already.

if eth0 is showing on ifconfig then your computer does find your card, but if not, I can suggest doing a "modprobe tulip" as root user.

Anyway, more info would help me or someone else help you.

hi, sorry for the delay but it was not easy for me to get a reply data together without internet access..
Anyway:
Suse 10.1 seems to find my eth0 card and once or twice I can get online but for only one web page? Yes kopnqueror went to yahoo but would not go anywhere else..this happen several times thru the frustration of different settings..
Heres the result of one of my ifconfigs...

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:80:AD:00:64:10
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::280:adff:fe00:6410/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:1 dropped:0 overruns:0 frame:0
TX packets:19 errors:2 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:2620 (2.5 Kb) TX bytes:2140 (2.0 Kb)
Interrupt:177 Base address:0xd800

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:91 errors:0 dropped:0 overruns:0 frame:0
TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7046 (6.8 Kb) TX bytes:7046 (6.8 Kb)


And to the find /lib/modules/ -name "*tulip*"

find /lib/modules/ -name "*tulip*"
/lib/modules/2.6.16.13-4-smp/kernel/drivers/net/tulip
/lib/modules/2.6.16.13-4-smp/kernel/drivers/net/tulip/tulip.ko

Interesting enough many decided to shut off the new knet feature
and doing the traditional method..
So I tried it..
They mention doing an #ifdown eth0 (seemed normal enough)
but when followed by a #ifup eth0 this is the error report..

#ifup eth0
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/ 100 Ethernet (rev 31)
eth0 configuration: eth-id-00:80:ad:00:64:10
Starting DHCP Client Daemon on eth0... . . . . . no IP address yet... background ing.
Error while executing:
Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev eth0' returne d:
RTNETLINK answers: Invalid argument
Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth0
Warning: Could not set up default route via interface
Command ip route replace to default via 192.168.1.1 returned:
. RTNETLINK answers: Network is unreachable
Configuration line: default 192.168.1.1 - -
This needs NOT to be AN ERROR if you set up multiple interfaces.
See man 5 routes how to avoid this warning.

I don't know much about this but I am beginning to think I know the reason one of the founders of Suse resigned some months ago..
jolphil

9.3 should be good.

anyways, if your NIC card problem exists consistantly with SUSE, i suggest you to get another NIC to tryout another distro, say ubuntu (it takes time, but you spent 2 weeks on 10.1 already)

when confirmed that your NIC is working fine with linux (other flavor or suse), you would be glad to go back to suse 10.0, but not 10.1, for your everyday use.

shshjun,
Thank you for your suggestion but this system has plug in hard drives(racks) and internet works for suse 9.0 box,Suse9.2download, and 10.0 download (after 2 months)to get online..It also works fine for debian sarge,FC4 and FC5 and mandriva2006 linux distros..
But As mentioned above Suse is and has been my favorite distro.It even works in WindowsXP...ha..
I know nothing is wrong with my system its either just me not able to configure it or Suse has slipped up with their network support in 10.1....
Either way not a great loss except I have always been stubborn and reluctant to give up for 71 years..Bad habit I guess.
Again thank you for your suggestion..
jolphil

Update: The 10.1 was re-upgraded using the install cdrom's to
get a frest start..The suse 10.1 installer still was unable to find the internet via my wired 4port linksys router to cable..Two other windows systems are also tied to the wired router and do in fact work fine..Other Linux distros ie: Mandriva,FC5,Suse9.2 and 10.0 are plugged into this same tower by using removable hard drive racks..They all work on the internet just fine..Thus it is not my hardware that is defective...I have opted to not use the netmanager as that seems to wipe out my /etc/resolv.conf file each time I try to connect..I have tried to get as close as possible with my net configuration settings of 10.0 which I am now using for this post..OBTW my fire wall is disabled...
The strange thing is several times I can get to yahoo.com once but when I try to change websites it just quits..
This may be confirmed by pinging my router..see below..

# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=150 time=0.574 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=150 time=0.539 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=150 time=0.547 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=150 time=0.547 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=150 time=0.550 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=150 time=0.554 ms

--- 192.168.1.1 ping statistics ---
8 packets transmitted, 6 received, 25% packet loss, time 7000ms
rtt min/avg/max/mdev = 0.539/0.551/0.574/0.032 ms
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.101: icmp_seq=38 Destination Host Unreachable
From 192.168.1.101 icmp_seq=38 Destination Host Unreachable
From 192.168.1.101 icmp_seq=39 Destination Host Unreachable
From 192.168.1.101 icmp_seq=40 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
43 packets transmitted, 0 received, +4 errors, 100% packet loss, time 42002ms
, pipe 3

notice that I can ping the router addy once but when I try the second time,nothing..
Does anyone have a clue as to why this happens?????
Perplexed to the max, I need help!!!
jolphil

i have exactly the same problem on solaris this February. ping works the very first time and failed on next times. http://www.linuxquestions.org/questi...d.php?t=404625
my solution to it is not to use solaris at that time.

another suggestion, try to use static IP address.

my other box doesn't have this problem at all. they connected to the same router. i thought that has something to do timing (or not). it's beyond me at that time and now.

do you have another box observes the same using the same router?

Yes I think I tried that a long time ago but I will give it a go again ..

Yup same here, other distros work..I have heard somewhere else it was timing but never got enough info to understand it..
I will google around for more stuff ..
If I score I will get back to this post..
BTW thank you for your help and good luck,
jolphil