Mailinglist Archive: opensuse-bugs (9910 mails)
| < Previous | Next > |
[Bug 231043] with FORCE_PERSISTENT_NAMES network startup sometimes failes
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Sun, 14 Jan 2007 05:06:52 -0700 (MST)
- Message-id: <20070114120652.EEF01F1A@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=231043
------- Comment #2 from ulrich@xxxxxxxxxxxx 2007-01-14 05:06 MST -------
I have now watched things for a longer time and i have found the following
effects:
1) During the first installation of the SMC 2802W i had no firmware present.
So yast did not know the MAC ID and created it's own local name.
After the firmware was present, i reinstalled the device in yast, because i
wanted the correct mac id as the 'official' device the name.
The result was, that there were two entries for this device in
/etc/udev/rules.d/30-net_persistent_names.rules:
SUBSYSTEM=="net", ACTION=="add", ENV{ADDRESS}=="00:30:b4:00:00:00",
IMPORT="/lib/udev/rename_netiface %k eth2"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:e2:64:9f:aa",
IMPORT="/lib/udev/rename_netiface %k eth3"
This seems to be a problem, and the last entry has benn duplicated with every
reboot.
2) Now i have left over only the three entries i need for my three network
cards:
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:c1:26:02:54:d1",
IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0e:2e:9c:7a:fc",
IMPORT="/lib/udev/rename_netiface %k eth1"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:e2:64:9f:aa",
IMPORT="/lib/udev/rename_netiface %k eth2"
At the moment things seem to be stable, but the SMC 2802W now always get eth3,
but it should be eth2 as written in 30-net_persistent_names.rules!
Something seems to go wrong here!
An at least the output of hwinfo:
----------------------------------
19: PCI 09.0: 0282 WLAN controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_1260_3890
Unique ID: DkES.ZsYjV_RuTpB
SysFS ID: /devices/pci0000:00/0000:00:09.0
SysFS BusID: 0000:00:09.0
Hardware Class: network
Model: "Standard Microsystems Corp [SMC] SMC2802W Wireless PCI Adapter"
Vendor: pci 0x1260 "Intersil Corporation"
Device: pci 0x3890 "ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism
Javelin/Prism Xbow]"
SubVendor: pci 0x10b8 "Standard Microsystems Corp [SMC]"
SubDevice: pci 0x2802 "SMC2802W Wireless PCI Adapter"
Revision: 0x01
Driver: "prism54"
Driver Modules: "prism54"
Device File: eth3
Features: WLAN
Memory Range: 0xe9000000-0xe9001fff (rw,non-prefetchable)
IRQ: 11 (11674 events)
HW Address: 00:04:e2:64:9f:aa
WLAN channels: 34 36 38 40 42 44 46 48 52 56 60 64 1 2 3 4 5 6 7 8 9 10 11 12
13 14
WLAN frequencies: 5.17 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32
2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
2.484
WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
WLAN encryption modes: WEP40 WEP104 WEP256
WLAN authentication modes: open sharedkey
Module Alias: "pci:v00001260d00003890sv000010B8sd00002802bc02sc80i00"
Driver Info #0:
Driver Status: prism54 is active
Driver Activation Cmd: "modprobe prism54"
Config Status: cfg=no, avail=yes, need=no, active=unknown
21: PCI 0b.0: 0200 Ethernet controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
Unique ID: rBUF.bM7cYpCLfi8
SysFS ID: /devices/pci0000:00/0000:00:0b.0
SysFS BusID: 0000:00:0b.0
Hardware Class: network
Model: "Compex FN22-3(A) LinxPRO Ethernet Adapter"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x11f6 "Compex"
SubDevice: pci 0x8139 "FN22-3(A) LinxPRO Ethernet Adapter"
Revision: 0x10
Driver: "8139too"
Driver Modules: "8139too"
Device File: eth0
I/O Ports: 0xdc00-0xdcff (rw)
Memory Range: 0xe9003000-0xe90030ff (rw,non-prefetchable)
IRQ: 10 (72281 events)
HW Address: 00:c1:26:02:54:d1
Link detected: yes
Module Alias: "pci:v000010ECd00008139sv000011F6sd00008139bc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd: "modprobe 8139too"
Config Status: cfg=no, avail=yes, need=no, active=unknown
22: PCI 0c.0: 0200 Ethernet controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139_0
Unique ID: JNkJ.IQxIdIhhuH7
SysFS ID: /devices/pci0000:00/0000:00:0c.0
SysFS BusID: 0000:00:0c.0
Hardware Class: network
Model: "Realtek RT8139"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
SubDevice: pci 0x8139 "RT8139"
Revision: 0x10
Driver: "8139too"
Driver Modules: "8139too"
Device File: eth1
I/O Ports: 0xe000-0xe0ff (rw)
Memory Range: 0xe9004000-0xe90040ff (rw,non-prefetchable)
IRQ: 11 (11674 events)
HW Address: 00:0e:2e:9c:7a:fc
Link detected: yes
Module Alias: "pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd: "modprobe 8139too"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Thanks,
Ulrich
--
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, or are watching someone who is.
------- Comment #2 from ulrich@xxxxxxxxxxxx 2007-01-14 05:06 MST -------
I have now watched things for a longer time and i have found the following
effects:
1) During the first installation of the SMC 2802W i had no firmware present.
So yast did not know the MAC ID and created it's own local name.
After the firmware was present, i reinstalled the device in yast, because i
wanted the correct mac id as the 'official' device the name.
The result was, that there were two entries for this device in
/etc/udev/rules.d/30-net_persistent_names.rules:
SUBSYSTEM=="net", ACTION=="add", ENV{ADDRESS}=="00:30:b4:00:00:00",
IMPORT="/lib/udev/rename_netiface %k eth2"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:e2:64:9f:aa",
IMPORT="/lib/udev/rename_netiface %k eth3"
This seems to be a problem, and the last entry has benn duplicated with every
reboot.
2) Now i have left over only the three entries i need for my three network
cards:
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:c1:26:02:54:d1",
IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0e:2e:9c:7a:fc",
IMPORT="/lib/udev/rename_netiface %k eth1"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:e2:64:9f:aa",
IMPORT="/lib/udev/rename_netiface %k eth2"
At the moment things seem to be stable, but the SMC 2802W now always get eth3,
but it should be eth2 as written in 30-net_persistent_names.rules!
Something seems to go wrong here!
An at least the output of hwinfo:
----------------------------------
19: PCI 09.0: 0282 WLAN controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_1260_3890
Unique ID: DkES.ZsYjV_RuTpB
SysFS ID: /devices/pci0000:00/0000:00:09.0
SysFS BusID: 0000:00:09.0
Hardware Class: network
Model: "Standard Microsystems Corp [SMC] SMC2802W Wireless PCI Adapter"
Vendor: pci 0x1260 "Intersil Corporation"
Device: pci 0x3890 "ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism
Javelin/Prism Xbow]"
SubVendor: pci 0x10b8 "Standard Microsystems Corp [SMC]"
SubDevice: pci 0x2802 "SMC2802W Wireless PCI Adapter"
Revision: 0x01
Driver: "prism54"
Driver Modules: "prism54"
Device File: eth3
Features: WLAN
Memory Range: 0xe9000000-0xe9001fff (rw,non-prefetchable)
IRQ: 11 (11674 events)
HW Address: 00:04:e2:64:9f:aa
WLAN channels: 34 36 38 40 42 44 46 48 52 56 60 64 1 2 3 4 5 6 7 8 9 10 11 12
13 14
WLAN frequencies: 5.17 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32
2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
2.484
WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
WLAN encryption modes: WEP40 WEP104 WEP256
WLAN authentication modes: open sharedkey
Module Alias: "pci:v00001260d00003890sv000010B8sd00002802bc02sc80i00"
Driver Info #0:
Driver Status: prism54 is active
Driver Activation Cmd: "modprobe prism54"
Config Status: cfg=no, avail=yes, need=no, active=unknown
21: PCI 0b.0: 0200 Ethernet controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
Unique ID: rBUF.bM7cYpCLfi8
SysFS ID: /devices/pci0000:00/0000:00:0b.0
SysFS BusID: 0000:00:0b.0
Hardware Class: network
Model: "Compex FN22-3(A) LinxPRO Ethernet Adapter"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x11f6 "Compex"
SubDevice: pci 0x8139 "FN22-3(A) LinxPRO Ethernet Adapter"
Revision: 0x10
Driver: "8139too"
Driver Modules: "8139too"
Device File: eth0
I/O Ports: 0xdc00-0xdcff (rw)
Memory Range: 0xe9003000-0xe90030ff (rw,non-prefetchable)
IRQ: 10 (72281 events)
HW Address: 00:c1:26:02:54:d1
Link detected: yes
Module Alias: "pci:v000010ECd00008139sv000011F6sd00008139bc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd: "modprobe 8139too"
Config Status: cfg=no, avail=yes, need=no, active=unknown
22: PCI 0c.0: 0200 Ethernet controller
[Created at pci.286]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139_0
Unique ID: JNkJ.IQxIdIhhuH7
SysFS ID: /devices/pci0000:00/0000:00:0c.0
SysFS BusID: 0000:00:0c.0
Hardware Class: network
Model: "Realtek RT8139"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
SubDevice: pci 0x8139 "RT8139"
Revision: 0x10
Driver: "8139too"
Driver Modules: "8139too"
Device File: eth1
I/O Ports: 0xe000-0xe0ff (rw)
Memory Range: 0xe9004000-0xe90040ff (rw,non-prefetchable)
IRQ: 11 (11674 events)
HW Address: 00:0e:2e:9c:7a:fc
Link detected: yes
Module Alias: "pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd: "modprobe 8139too"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Thanks,
Ulrich
--
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, or are watching someone who is.
| < Previous | Next > |