From: Piter PUNK <piterpk@terra.com.br>
To: linux-hotplug@vger.kernel.org
Subject: Problem with network rules
Date: Fri, 11 Aug 2006 21:06:23 +0000 [thread overview]
Message-ID: <44DCF14F.304@terra.com.br> (raw)
Hi,
I got from one of our users one strange "log". The guy have
a rule for this card, nameing the card as eth1 but the module doesn't
understand that, take a look:
---------------from user--------------------------------------------
[root@localhost rules.d]# cat network-devices.rules
# Local network rules to name your network cards.
# These rules were generated by nethelper.sh, but you can customize
# them if needed.
#
# If you delete this file, /lib/udev/nethelper.sh will try to
# generate it again the next time udev is started.
KERNEL="eth?", SYSFS{address}="00:0e:9b:c5:98:36", NAME="eth0"
KERNEL="eth?", SYSFS{address}="00:c0:9f:97:de:1f", NAME="eth1"
[root@localhost rules.d]# modprobe sis900
[root@localhost rules.d]# /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:C0:9F:97:DE:1F
BROADCAST 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.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0x1800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)
[root@localhost rules.d]# modprobe -r sis900
[root@localhost rules.d]# modprobe bcm43xx
[root@localhost rules.d]# /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0E:9B:C5:98:36
BROADCAST 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.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)
--------------from user------------------------------------
Anyone had a tip of why this thing is happening?
The udev is udev-096. And i thanks any help... i had
sis900 cards embedded in my notebook and built-in in a old
SiS MotherBoard... and i can't reproduce the error...
Thanks for your help,
Piter PUNK
--
| E-Mail: piterpk@terra.com.br (personal)
.|. roberto.batista@ntux.com.br (professional)
/V\
// \\ UIN:116043354 Homepage:www.openslack.org/~piterpk
/( )\
^`~'^ ----> Slackware Linux - The Best One! <----
#105432
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2006-08-11 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 21:06 Piter PUNK [this message]
2006-08-12 3:53 ` Problem with network rules Alexander E. Patrakov
2006-08-13 14:48 ` Piter PUNK
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44DCF14F.304@terra.com.br \
--to=piterpk@terra.com.br \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).