https://bugzilla.novell.com/show_bug.cgi?id=335486 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335486#c35 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@novell.com |kasievers@novell.com Status|ASSIGNED |NEW --- Comment #35 from Marius Tomaschewski <mt@novell.com> 2008-05-27 08:16:40 MDT --- (In reply to comment #34 from Walter Haidinger)
Hi Marius, thanks for your help!
Thanks for your reports!
rpm -V ... udev is quiet (no changes), and syslog-ng (not syslog!) shows only /etc/syslog-ng/syslog-ng.conf which is ok (added custom entries).
OK. I meant "rpm -V sysconfig" of course, but you verified it bellow ;-)
Replying to comment #33:
rpm -V udev sysconfig ok, nothing is printed.
OK.
None of the 5 udev rules listed in comment #33 exist on my system.
The obsoleted 30-... rule was even documented in the Release Notes, IIRC. So yes, I'm aware of that.
Now, without anything obvious wrong in the udev setup, how can we debug this further?
What are the possible reasons that the "add" action of 77-network.rules is _not_ triggered?
Yes, this is the question here. It mayby happens, because of your 2.6.25.4-vmhost32 kernel... Perhaps the forcedeth driver does not trigger this event without patch? Hmm... Marcs and Peters seem to use suse default kernels... We will ask the maintainer and find it out - reassigning to him. The rename rule (70-persistent-net.rules) is called / visible in your boot.msg file. <6>udev: renamed network interface eth1 to eth0 <6>udev: renamed network interface eth0_rename to eth1 In my case, I can see more log lines when rename happens (10.3): <6>eth0 renamed to eth0_rename <6>eth1 renamed to eth0 <6>udev: renamed network interface eth1 to eth0 <6>eth0_rename renamed to eth1 <6>udev: renamed network interface eth0_rename to eth1 I think, it makes sense to enable ulog debug mode; perhaps it is visible there. Please set udev_log="debug" in /etc/udev/udev.conf, reboot and provide the logs - should be in /var/log/boot.msg. Alternatively, you can also try to trigger it at runtime: rcnetwork stop rmmod forcedeth # network card driver udevcontrol log_priority=debug rcnetwork start -o boot & # in background, or modprobe on another modprobe forcedeth # terminal after rcnetwork start... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.