Please send the output for: # mii-tool Maybe there is a problem with your ethernet network Also some output from: # tcpdump -i eth0 Are you using DHCP? Cheers, -----Original Message----- From: Daniel Bauer [mailto:linux@daniel-bauer.com] Sent: Tuesday, December 20, 2005 11:58 AM To: opensuse@opensuse.org Subject: [opensuse] can't ping to gateway Hello, good evening Just installed opensuse succcessful (standard kde install, no changes in software selection). Installed network card with Yast, stopped firewall (clicked "start manual" and stopped it). Everything seems normal, but I don't get any connection to outside. Ping to my gateway doesn't work ("destination host unreachable"). I just entered all the same values for local ip, gateway, name-server... as in Suse 9 on same machine. Ping to local host works. I don't know which info you need, here's what is displayed when typing "ifconfig": eth0 Link encap:Ethernet HWaddr 00:08:A1:35:BF:BC inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::208:a1ff:fe35:bfbc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1957 (1.9 Kb) TX bytes:2462 (2.4 Kb) Interrupt:9 Base address:0xb400 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:102 errors:0 dropped:0 overruns:0 frame:0 TX packets:102 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6880 (6.7 Kb) TX bytes:6880 (6.7 Kb) this is (apart from the no. of packets/bytes) exactly the same as in Suse 9. "route -n" gives the following: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use 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 where I am wondering about the "169.254.0.0"-line, because I never typed in such a ip-number anywhere. On Suse 9 this would give me only 2 lines (192... and 0.0.0.0). Should I send the /var/log/messages of my last Suse10 session? In case: Copy text in mail or attach? What did I forget to make my network connection work? Thanks for any help. Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Dienstag, 20. Dezember 2005 19.03 schrieb Fabian_Salamanca@Dell.com:
Please send the output for:
# mii-tool
Sorry, don't know mii-tool, and couldn't find it on opensuse CD's...
Maybe there is a problem with your ethernet network
Also some output from:
# tcpdump -i eth0
1. try: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 19:27:09.158365 arp who-has 192.168.2.1 tell venus.atelier.foto 19:27:10.158306 arp who-has 192.168.2.1 tell venus.atelier.foto 19:27:10.889092 IP 192.168.2.3.netbios-dgm > 192.168.2.255.netbios-dgm: NBT UDP PACKET(138) 19:27:11.158368 arp who-has 192.168.2.1 tell venus.atelier.foto [...repeated x times...] 19:34:40.778039 IP 192.168.2.3.netbios-dgm > 192.168.2.255.netbios-dgm: NBT UDP PACKET(138) 19:34:40.778119 IP 192.168.2.3.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 19:34:41.532751 IP 192.168.2.3.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 19:34:42.287521 IP 192.168.2.3.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 19:34:43.038806 arp who-has 192.168.2.1 tell 192.168.2.3 36 packets captured 72 packets received by filter 0 packets dropped by kernel (during the above I opened a second console for root and pinged to 192.168.2.1 [which is my gateway], then opened firefox, who tried to connect to somewhere) stopped with ctrl-c, 2. try: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 19:41:18.415325 arp who-has 192.168.2.1 tell venus.atelier.foto [...repeated x times...] 19:42:10.677015 IP 192.168.2.3.netbios-dgm > 192.168.2.255.netbios-dgm: NBT UDP PACKET(138) 19:42:11.062607 arp who-has 192.168.2.1 tell venus.atelier.foto [...repeated x times...] 86 packets received by filter 0 packets dropped by kernel
Are you using DHCP?
No, fixed IP 192.168.2.2 for this machine, 192.168.2.1 for gateway & name-server When looking at the hardware details of the network card I saw that Suse 9 uses "dmfe", while Suse 10 looks at the card as a Tulip-compatible and therefore uses a module called "tulip". For a try I changed it to "dmfe" but then the System didn't recognise the card anymore. Does this information help any further?
Daniel Bauer schrieb:
Am Dienstag, 20. Dezember 2005 19.03 schrieb Fabian_Salamanca@Dell.com:
Please send the output for:
# mii-tool
Sorry, don't know mii-tool, and couldn't find it on opensuse CD's...
Maybe there is a problem with your ethernet network
Also some output from:
# tcpdump -i eth0
1. try:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 19:27:11.158368 arp who-has 192.168.2.1 tell venus.atelier.foto [...repeated x times...]
OK. So your gateway doesn't answer. That either means your gateway is disconnected, defective or switched off. Run # tcpdump -neti eth0 arp or icmp and in another window # ping 192.168.2.3 while this other machine (192.168.2.3) is switched on. If ping works, the bug is clearly not at your machine, but between the switch and the gateway or directly at the gateway. Regards, Carl-Daniel -- http://www.hailfinger.org/
OK. So your gateway doesn't answer. That either means your gateway is disconnected, defective or switched off.
I don't think so. When I shutdown Suse10 and reboot with Suse9 on this same machine there's no problem to connect to the gateway or the other computer. I don't change anything on cards or cables etc, just starting other OS. I also pinged the gateway from the other computer (a Win98) that is connected to the same gateway via the same switch, while running Suse 10 here, and the gateway answers to the Win-Machine. 192.168.2.3 is the Windows Machine, 192.168.2.2 this one, and 192.168.2.1 the gateway.
Run # tcpdump -neti eth0 arp or icmp and in another window # ping 192.168.2.3 while this other machine (192.168.2.3) is switched on. If ping works, the bug is clearly not at your machine, but between the switch and the gateway or directly at the gateway.
Regards, Carl-Daniel
this is the output: # tcpdump -neti eth0 arp or icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.3 tell 192.168.2.2 00:30:4f:21:d8:f9 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: arp who-has 192.168.2.1 tell 192.168.2.3 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.2.1 tell 192.168.2.2 13 packets captured 26 packets received by filter 0 packets dropped by kernel I pinged to 192.168.2.3, stopped after 4 errors, then pinged to 192.168.2.1 and stopped again. Does this list say anything in direction of my problem? regards, Daniel
On Wednesday 21 December 2005 09:59, Daniel Bauer wrote:
Does this list say anything in direction of my problem?
It just indicates that nothing is actually going out of your eth0 through the wire. To eliminate the possibility that there's something wrong with your installation, you could try booting the SUSE 10 Live DVD.
To eliminate the possibility that there's something wrong with your installation, you could try booting the SUSE 10 Live DVD.
I don't have a live-dvd and no dvd-burner, so I can't make one. I was looking around, comparing loaded modules and harware info in Suse 9 and Suse 10. I found that the network-card driver module seems to be unused in Suse10, lsmod gives: Module Size Used by tulip 51360 0 Because Sude9 uses the dmfe driver, I loaded it in S10 with "modprobe dmfe". Now both modules appear in the list, both unused: Module Size Used by dmfe 20252 0 tulip 51360 0 lsmod in Suse 9 has a "1" for "Used" the dmfe-module. Why are the modules not used in S10? How can I find out?
On Wed, 2005-12-21 at 13:20 +0100, Daniel Bauer wrote:
To eliminate the possibility that there's something wrong with your installation, you could try booting the SUSE 10 Live DVD.
I don't have a live-dvd and no dvd-burner, so I can't make one.
I was looking around, comparing loaded modules and harware info in Suse 9 and Suse 10.
I found that the network-card driver module seems to be unused in Suse10, lsmod gives:
Module Size Used by tulip 51360 0
Because Sude9 uses the dmfe driver, I loaded it in S10 with "modprobe dmfe". Now both modules appear in the list, both unused:
Module Size Used by dmfe 20252 0 tulip 51360 0
lsmod in Suse 9 has a "1" for "Used" the dmfe-module.
Why are the modules not used in S10? How can I find out?
In SUSE 10 unload the tulip driver and then load the dmfe first. This sounds like a driver issue. Looking at the docs this does not appear to be a tulip family driver. If you have the kernel sources installed look in /usr/src/linux/Documentation/networking for more information. On the SuSE 9.x box show the results of lsmod | grep tulip. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
In SUSE 10 unload the tulip driver and then load the dmfe first. This sounds like a driver issue. Looking at the docs this does not appear to be a tulip family driver. If you have the kernel sources installed look in /usr/src/linux/Documentation/networking for more information. On the SuSE 9.x box show the results of lsmod | grep tulip.
Ok, thanks! This works so far, it seems that Suse10 recognises the Davicom card wrongly. I typed: rmmod tulip modprobe dmfe ifconfig eth0 up Then ping (and internet access) works. So, I went to Yast/network devices/network card and changed the "hardware details" of the card: - gave it a new name "Davicom" - deleted the entry for the driver "tulip" and entered "dmfe" instead After finishing Yast, network connection was gone again and lsmod showed "tulip" again. Went to Yast again to check if it has saved my entries - it did. I rebooted, but same result: module "tulip" loaded as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as above I can make the network running again. So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not? regards, Daniel
Hello, Am Mittwoch, 21. Dezember 2005 16:08 schrieb Daniel Bauer:
In SUSE 10 unload the tulip driver and then load the dmfe first. This sounds like a driver issue. Looking at the docs this does not appear to be a tulip family driver. If you have the kernel sources installed look in /usr/src/linux/Documentation/networking for more information. On the SuSE 9.x box show the results of lsmod | grep tulip.
Ok, thanks! This works so far, it seems that Suse10 recognises the Davicom card wrongly. I typed:
rmmod tulip modprobe dmfe ifconfig eth0 up
Then ping (and internet access) works. So, I went to Yast/network devices/network card and changed the "hardware details" of the card: - gave it a new name "Davicom" - deleted the entry for the driver "tulip" and entered "dmfe" instead
After finishing Yast, network connection was gone again and lsmod showed "tulip" again. Went to Yast again to check if it has saved my entries - it did. I rebooted, but same result: module "tulip" loaded as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as above I can make the network running again.
So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not?
Even if it is not nice, you could write the rmmod and modprobe command to /etc/init.d/boot.local. Maybe the network script is working correct then. (If not, write a small initscript based on /etc/init.d/skeleton which calls the commands and add Required-Start: network to ensure it is run late enough.) Oh, and please make an entry in bugzilla - this sounds like a bug. Regards, Christian Boltz -- My Trash Can is also a shortcut for Amarok... I guess the Amarok team must have had some wild thoughts about the features of their program =) [Benjamin Bach in opensuse]
Hello,
Am Mittwoch, 21. Dezember 2005 16:08 schrieb Daniel Bauer:
In SUSE 10 unload the tulip driver and then load the dmfe first. This sounds like a driver issue. Looking at the docs this does not appear to be a tulip family driver. If you have the kernel sources installed look in /usr/src/linux/Documentation/networking for more information. On the SuSE 9.x box show the results of lsmod | grep tulip.
Ok, thanks! This works so far, it seems that Suse10 recognises the Davicom card wrongly. I typed:
rmmod tulip modprobe dmfe ifconfig eth0 up
Then ping (and internet access) works. So, I went to Yast/network devices/network card and changed the "hardware details" of the card: - gave it a new name "Davicom" - deleted the entry for the driver "tulip" and entered "dmfe" instead
After finishing Yast, network connection was gone again and lsmod showed "tulip" again. Went to Yast again to check if it has saved my entries - it did. I rebooted, but same result: module "tulip" loaded as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as above I can make the network running again.
So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not?
Even if it is not nice, you could write the rmmod and modprobe command to /etc/init.d/boot.local. Maybe the network script is working correct then. (If not, write a small initscript based on /etc/init.d/skeleton which calls the commands and add Required-Start: network to ensure it is run late enough.)
Oh, and please make an entry in bugzilla - this sounds like a bug. Perhaps a change in /etc/modprob.conf or what ever the file is in SUSE
On Wed, 2005-12-21 at 18:18 +0100, Christian Boltz wrote: 10. Isn't this where some modules are set to load for certain devices? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Hi, On Wed, 21 Dec 2005, Ken Schneider wrote: > On Wed, 2005-12-21 at 18:18 +0100, Christian Boltz wrote: >> Am Mittwoch, 21. Dezember 2005 16:08 schrieb Daniel Bauer: >>>> In SUSE 10 unload the tulip driver and then load the dmfe first. >>>> This sounds like a driver issue. Looking at the docs this does not >>>> appear to be a tulip family driver. If you have the kernel sources >>>> installed look in /usr/src/linux/Documentation/networking for more >>>> information. On the SuSE 9.x box show the results of lsmod | grep >>>> tulip. >>> >>> Ok, thanks! This works so far, it seems that Suse10 recognises the >>> Davicom card wrongly. I typed: >>> >>> rmmod tulip >>> modprobe dmfe >>> ifconfig eth0 up >>> >>> Then ping (and internet access) works. So, I went to >>> Yast/network devices/network card >>> and changed the "hardware details" of the card: >>> - gave it a new name "Davicom" >>> - deleted the entry for the driver "tulip" and entered "dmfe" instead >>> >>> After finishing Yast, network connection was gone again and lsmod >>> showed "tulip" again. Went to Yast again to check if it has saved my >>> entries - it did. I rebooted, but same result: module "tulip" loaded >>> as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as >>> above I can make the network running again. >>> >>> So, my only problem - for the moment ;-) is: >>> how can I make the change definitive, so that "dmfe" will be loaded >>> at boot and "tulip" not? >> >> Even if it is not nice, you could write the rmmod and modprobe command >> to /etc/init.d/boot.local. Maybe the network script is working correct >> then. (If not, write a small initscript based on /etc/init.d/skeleton >> which calls the commands and add Required-Start: network to ensure it >> is run late enough.) >> >> Oh, and please make an entry in bugzilla - this sounds like a bug. > Perhaps a change in /etc/modprob.conf or what ever the file is in SUSE > 10. Isn't this where some modules are set to load for certain devices? Probably the most easiest way is to change /etc/sysconfig/kernel: MODULES_LOADED_ON_BOOT="dmfe" This gets loaded at first, before all other non-initrd modules. If you have more than one entry there, the load sequence is either unpredicted or latest first (I'm only sure that it is not left to right). Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not?
Even if it is not nice, you could write the rmmod and modprobe command to /etc/init.d/boot.local. Maybe the network script is working correct then. (If not, write a small initscript based on /etc/init.d/skeleton which calls the commands and add Required-Start: network to ensure it is run late enough.)
Oh, and please make an entry in bugzilla - this sounds like a bug.
I don't know how to make a bug report - and I feel very unsecure. If OpenSuse has a bug or if it's just because maybe I myself am kind of buggy??? ;-) Anyway: when searching google for "tulip dfme" I found that similar problems also occure on debian systems.
Perhaps a change in /etc/modprob.conf or what ever the file is in SUSE 10. Isn't this where some modules are set to load for certain devices?
Probably the most easiest way is to change /etc/sysconfig/kernel:
MODULES_LOADED_ON_BOOT="dmfe"
This gets loaded at first, before all other non-initrd modules. If you have more than one entry there, the load sequence is either unpredicted or latest first (I'm only sure that it is not left to right).
Cheers -e
Thanks for all the hints! Before trying out the suggested solutions I tried to do the following: In Yast I deleted the network card and finished Yast. Then opened Yast again and "installed" the network card again, leaving the name, that yast gave her untouched, just overwriting "tulip" by "dmfe" (in hardware details). After this eth0 was not on the list given by "infconfig" (only lo appeared). I rebotted the PC - and now the network card works as it should. I've rebotted twice, to see, if was only an accident - but it seems that first deleting and then adding the card again works better than just changing the settings. Now there is one more thing I wonder: in the boot log I find following entries now: ---------- from boot log Suse 10: ----------------- Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:08:a1:35:bf:bc 20 19 Initializing random number generatordone <notice>startproc: execve (/sbin/resmgrd) [ /sbin/resmgrd ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin vga=0x31a RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N acpi=off LINES=59 HOME=/ SHLVL=2 splash=verbose SPLASH=yes ROOTFS_BLKDEV=/dev/hdg1 _=/sbin/startproc DAEMON=/sbin/resmgrd ] Starting resource managerdone eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 40) eth0 configuration: eth-id-00:08:a1:35:bf:bc eth0 IP address: 192.168.2.2/24 done -------------------------------------------- while the antries in Suse 9 are much shorter: -------------- from boot log of Suse 9 (kernel 2.4): ---------------------- Setting up network interfaces: lo done eth0 IP/Netmask: 192.168.2.2 / 255.255.255.0 done <notice>exit status of (network) is (0) ---------------------------------- Maybe the new kernel 2.6 has longer (and a bit mixed up) messages - but maybe there is still something as it should not? I wonder about eth0 showing up 3 times and about the "Waiting for mandatory devices: eth-id-00:08:a1:35:bf:bc". Does this have any meaning or can I just forget about it? kind regards, Daniel
Hallo Leute, Am Mittwoch, 21. Dezember 2005 20:34 schrieb Daniel Bauer:
So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not?
Even if it is not nice, you could write the rmmod and modprobe command to /etc/init.d/boot.local. Maybe the network script is working correct then. (If not, write a small initscript based on /etc/init.d/skeleton which calls the commands and add Required-Start: network to ensure it is run late enough.)
Oh, and please make an entry in bugzilla - this sounds like a bug.
I don't know how to make a bug report -
Have a look at http://bugs.opensuse.org If you still have questions, just ask.
and I feel very unsecure. If OpenSuse has a bug or if it's just because maybe I myself am kind of buggy??? ;-)
*g* You never can be sure, but ...
Anyway: when searching google for "tulip dfme" I found that similar problems also occure on debian systems.
... this sounds like it is really a bug. [reconfigured network card using YaST]
After this eth0 was not on the list given by "infconfig" (only lo appeared). I rebotted the PC - and now the network card works as it should. I've rebotted twice, to see, if was only an accident - but it seems that first deleting and then adding the card again works better than just changing the settings.
This means the bug is - a wrong autodetection - maybe another problem in YaST (difference between modifying a network device and completely re-configuring it) I guess it would be a good idea to use category "YaST2" for your bugreport. Please attach the y2logs [1] to your bug report.
Maybe the new kernel 2.6 has longer (and a bit mixed up) messages - but maybe there is still something as it should not? I wonder about eth0 showing up 3 times and about the "Waiting for mandatory devices: eth-id-00:08:a1:35:bf:bc".
Does your network card use a dynamic IP via DHCP? This would explain the message - it just waits for the DHCP server. Regards, Christian Boltz [1] Sorry, very long link ;-) http://www.opensuse.org/Bug_Reporting_FAQ#I_reported_a_YaST2_bug.2C_and_now_... -- dd ist es herzlich egal was fuer ein FS auf der Platte ist es kopiert die Platte mit Haut und Haaren. [Ruediger Meier in suse-linux]
Oh, and please make an entry in bugzilla - this sounds like a bug.
I don't know how to make a bug report -
Have a look at http://bugs.opensuse.org If you still have questions, just ask.
I was looking around on the "bugs-page" for tulip/dfme and I think the bug is already known there. But the comments there sound to me as if it's not a bug somebody considers worth "repairing". It said, that the bug only occuring with those cheep Davicom-cards - well I didn't know that Linux users only use exclusive high-end devices, maybe one should rename it from opensuse to LuisVuittonSuse or something like that... ;-)
Maybe the new kernel 2.6 has longer (and a bit mixed up) messages - but maybe there is still something as it should not? I wonder about eth0 showing up 3 times and about the "Waiting for mandatory devices: eth-id-00:08:a1:35:bf:bc".
Does your network card use a dynamic IP via DHCP? This would explain the message - it just waits for the DHCP server.
No, I use only a fixed IP on the only remaing network card (the onboard one had to be desabled in bios due to a freeze by the TG3 driver). This is why I'm wondering about the waiting and about the multiple listing of lo and eth0... regards, Daniel
On Thursday 22 December 2005 12:45, Daniel Bauer wrote:
Oh, and please make an entry in bugzilla - this sounds like a bug.
I don't know how to make a bug report -
Have a look at http://bugs.opensuse.org If you still have questions, just ask.
I was looking around on the "bugs-page" for tulip/dfme and I think the bug is already known there. But the comments there sound to me as if it's not a bug somebody considers worth "repairing". It said, that the bug only occuring with those cheep Davicom-cards - well I didn't know that Linux users only use exclusive high-end devices, maybe one should rename it from opensuse to LuisVuittonSuse or something like that... ;-)
It's not SUSE who writes the driver for network cards, the drivers are in the kernel. And it's not about price, but about how rare the card is. Look at Realtek 8139, cheap and crappy card, but very common. It works well in Linux because the driver is maintained and has workarounds for the card's crappiness.
Am Donnerstag, 22. Dezember 2005 14:09 schrieb Silviu Marin-Caea:
On Thursday 22 December 2005 12:45, Daniel Bauer wrote:
> Oh, and please make an entry in bugzilla - this sounds like a > bug.
I don't know how to make a bug repor
have you erase in the firewall conf the param any ? On my system it works now. -- mit freundlichen Grüßen / best Regards. Günther J. Niederwimmer
On Wed, 21 Dec 2005, Daniel Bauer wrote:
In SUSE 10 unload the tulip driver and then load the dmfe first. This sounds like a driver issue. Looking at the docs this does not appear to be a tulip family driver. If you have the kernel sources installed look in /usr/src/linux/Documentation/networking for more information. On the SuSE 9.x box show the results of lsmod | grep tulip. ....
After finishing Yast, network connection was gone again and lsmod showed "tulip" again. Went to Yast again to check if it has saved my entries - it did. I rebooted, but same result: module "tulip" loaded as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as above I can make the network running again.
Yes, you should enter a bug into bugzilla ...
So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not?
Have a look in /etc/sysconfig/hardware In one of the hwcfg-bus-pci-* files, there should be the tulip entry. Just change it to dmfe, and things should work then. Berthold -- ------------------------------------------------------------------ Berthold Gunreben SUSE Linux GmbH -- Dokumentation mailto:bg@suse.de Maxfeldstr. 5 http://www.suse.de/ D-90409 Nuernberg, Germany
participants (9)
-
Berthold Gunreben -
Carl-Daniel Hailfinger -
Christian Boltz -
Daniel Bauer -
Eberhard Moenkeberg -
Fabian_Salamanca＠Dell.com -
Günther J. Niederwimmer -
Ken Schneider -
Silviu Marin-Caea