Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hi Mark On 2/3/07, Mark Kettenis [EMAIL PROTECTED] wrote: Regarding the high interrupt load on the v210; try disconnecting the CD-ROM/DVD-ROM. Removing the CD drives silenced the interrupts, and the CPU load dropped to 0%, thanks. Can you try the attached diff? It has some debug printf's in there, so please send me a dmesg. After CVSupdating last night and applying your patch, the fiber NICs worked for a few pings, but since they changed their status from active to no carrier. Please find some debug output below. By the way, the large Marvell chip on the SK-9S91 NIC is labelled 88E8021. Thanks, Rolf # ifconfig lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33192 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:14:4f:64:0c:52 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 10.7.91.218 netmask 0xff80 broadcast 10.7.91.255 inet6 fe80::214:4fff:fe64:c52%bge0 prefixlen 64 scopeid 0x1 bge1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:14:4f:64:0c:53 media: Ethernet autoselect (1000baseT full-duplex) status: active bge2: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:14:4f:64:0c:54 media: Ethernet autoselect (none) status: no carrier bge3: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:14:4f:64:0c:55 media: Ethernet autoselect (none) status: no carrier msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:59 media: Ethernet autoselect (none) status: no carrier inet6 fe80::200:5aff:fe72:fc59%msk0 prefixlen 64 scopeid 0x5 inet 10.20.0.218 netmask 0xff00 broadcast 10.20.0.255 pflog0: flags=0 mtu 33192 enc0: flags=0 mtu 1536 # # ifconfig -m msk0 msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:59 media: Ethernet autoselect (none) status: no carrier supported media: media none media 1000baseSX media 1000baseSX mediaopt full-duplex media autoselect inet6 fe80::200:5aff:fe72:fc59%msk0 prefixlen 64 scopeid 0x5 inet 10.20.0.218 netmask 0xff00 broadcast 10.20.0.255 # # dmesg console is /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.0-current (GENERIC) #0: Mon Feb 5 02:19:55 CET 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 1073741824 avail memory = 969416704 using 6553 buffers containing 53682176 bytes of memory bootpath: /[EMAIL PROTECTED],60/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Fire V210 cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1336 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) memory-controller at mainbus0 not configured schizo0 at mainbus0: Tomatillo, version 4, ign 7c0, bus B 0 to 0 schizo0: dvma map c000-dfff, iotdb 4d16000-4d96000 pci0 at schizo0 bge0 at pci0 dev 2 function 0 Broadcom BCM5704C rev 0x00, BCM5704 B0 (0x2100): ivec 0x7c8, address 00:14:4f:64:0c:52 brgphy0 at bge0 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 bge1 at pci0 dev 2 function 1 Broadcom BCM5704C rev 0x00, BCM5704 B0 (0x2100): ivec 0x7c9, address 00:14:4f:64:0c:53 brgphy1 at bge1 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 schizo1 at mainbus0: Tomatillo, version 4, ign 780, bus A 0 to 0 schizo1: dvma map c000-dfff, iotdb 547e000-54fe000 pci1 at schizo1 ebus0 at pci1 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 flashprom at ebus0 addr 0-f, 290-290 not configured rtc0 at ebus0 addr 70-71: m5819p pcfiic0 at ebus0 addr 320-321 ipl 46 iic0 at pcfiic0 SUNW,i2c-imax at iic0 addr 0xb not configured SUNW,i2c-imax at iic0 addr 0xc not configured at24c64 at iic0 addr 0x51 not configured at24c64 at iic0 addr 0x54 not configured at24c64 at iic0 addr 0x58 not configured at34c02 at iic0 addr 0x5b not configured at34c02 at iic0 addr 0x5c not configured at34c02 at iic0 addr 0x5d not configured at34c02 at iic0 addr 0x5e not configured ds1307 at iic0 addr 0x68 not configured at24c64 at iic0 addr 0x28 not configured pca9555 at iic0 addr 0x22 not configured pca9555 at iic0 addr 0x23 not configured pca9555 at iic0 addr 0x34 not configured pca9556 at iic0 addr 0x38 not configured power0 at ebus0 addr 800-82f ipl 32: can't map register space com0 at ebus0 addr 3f8-3ff ipl 44: ns16550a, 16 byte fifo com0: console com1 at ebus0 addr 2e8-2ef ipl 44: ns16550a, 16 byte fifo rmc-comm at ebus0 addr 3e8-3ef ipl 44 not configured Acer Labs
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Can you try the attached diff? It has some debug printf's in there,
so please send me a dmesg.
Regarding the high interrupt load on the v210; try disconnecting the
CD-ROM/DVD-ROM.
Index: mii/eephy.c
===
RCS file: /cvs/src/sys/dev/mii/eephy.c,v
retrieving revision 1.39
diff -u -p -r1.39 eephy.c
--- mii/eephy.c 5 Jan 2007 21:40:45 - 1.39
+++ mii/eephy.c 3 Feb 2007 14:10:36 -
@@ -133,7 +133,7 @@ eephyattach(struct device *parent, struc
struct mii_attach_args *ma = aux;
struct mii_data *mii = ma-mii_data;
const struct mii_phydesc *mpd;
- int reg;
+ int reg, page;
mpd = mii_phy_match(ma, eephys);
printf(: %s, rev. %d\n, mpd-mpd_name, MII_REV(ma-mii_id2));
@@ -147,6 +147,33 @@ eephyattach(struct device *parent, struc
/* XXX No loopback support yet, although the hardware can do it. */
sc-mii_flags |= MIIF_NOLOOP;
+
+ {
+ int i;
+ for (i = 0; i 32; i++)
+ printf(%d: 0x%04x\n, i, PHY_READ(sc, i));
+ }
+
+ /* Switch to fiber-only mode if necessary. */
+ if (sc-mii_model == MII_MODEL_MARVELL_E1112
+ sc-mii_flags MIIF_HAVEFIBER) {
+ page = PHY_READ(sc, E1000_EADR);
+ PHY_WRITE(sc, E1000_EADR, 2);
+ reg = PHY_READ(sc, E1000_SCR);
+ printf(16_2: 0x%04x\n, reg);
+ reg = ~E1000_SCR_MODE_MASK;
+ reg |= E1000_SCR_MODE_1000BX;
+ PHY_WRITE(sc, E1000_SCR, reg);
+ PHY_WRITE(sc, E1000_EADR, page);
+
+ PHY_RESET(sc);
+ }
+
+ {
+ int i;
+ for (i = 0; i 32; i++)
+ printf(%d: 0x%04x\n, i, PHY_READ(sc, i));
+ }
sc-mii_capabilities = PHY_READ(sc, E1000_SR) ma-mii_capmask;
if (sc-mii_capabilities BMSR_EXTSTAT)
Index: pci/if_msk.c
===
RCS file: /cvs/src/sys/dev/pci/if_msk.c,v
retrieving revision 1.43
diff -u -p -r1.43 if_msk.c
--- pci/if_msk.c3 Feb 2007 12:50:26 - 1.43
+++ pci/if_msk.c3 Feb 2007 14:10:37 -
@@ -1071,6 +1071,14 @@ msk_attach(struct device *parent, struct
ifp-if_capabilities = IFCAP_VLAN_MTU;
+ /* GMAC and GPHY Reset */
+ SK_IF_WRITE_4(sc_if, 0, SK_GMAC_CTRL, SK_GMAC_RESET_SET);
+ SK_IF_WRITE_4(sc_if, 0, SK_GPHY_CTRL, SK_GPHY_RESET_SET);
+ DELAY(1000);
+ SK_IF_WRITE_4(sc_if, 0, SK_GPHY_CTRL, SK_GPHY_RESET_CLEAR);
+ SK_IF_WRITE_4(sc_if, 0, SK_GMAC_CTRL, SK_GMAC_LOOP_OFF |
+ SK_GMAC_PAUSE_ON | SK_GMAC_RESET_CLEAR);
+
/*
* Do miibus setup.
*/
@@ -1086,7 +1094,7 @@ msk_attach(struct device *parent, struct
ifmedia_init(sc_if-sk_mii.mii_media, 0,
msk_ifmedia_upd, msk_ifmedia_sts);
mii_attach(self, sc_if-sk_mii, 0x, MII_PHY_ANY,
- MII_OFFSET_ANY, MIIF_DOPAUSE|MIIF_FORCEANEG);
+ MII_OFFSET_ANY, MIIF_DOPAUSE|MIIF_HAVEFIBER);
if (LIST_FIRST(sc_if-sk_mii.mii_phys) == NULL) {
printf(%s: no PHY found!\n, sc_if-sk_dev.dv_xname);
ifmedia_add(sc_if-sk_mii.mii_media, IFM_ETHER|IFM_MANUAL,
@@ -1275,6 +1283,8 @@ mskc_attach(struct device *parent, struc
sc-sk_ramsize, sc-sk_ramsize / 1024,
sc-sk_rboff));
+ printf(pmdtype: %c\n, sk_win_read_1(sc, SK_PMDTYPE));
+
switch (sc-sk_type) {
case SK_YUKON_XL:
sc-sk_name = Yukon-2 XL;
@@ -1838,6 +1848,7 @@ msk_init_yukon(struct sk_if_softc *sc_if
DPRINTFN(6, (msk_init_yukon: 1\n));
+#if 0
/* GMAC and GPHY Reset */
SK_IF_WRITE_4(sc_if, 0, SK_GMAC_CTRL, SK_GMAC_RESET_SET);
SK_IF_WRITE_4(sc_if, 0, SK_GPHY_CTRL, SK_GPHY_RESET_SET);
@@ -1848,6 +1859,7 @@ msk_init_yukon(struct sk_if_softc *sc_if
SK_IF_WRITE_4(sc_if, 0, SK_GPHY_CTRL, SK_GPHY_RESET_CLEAR);
SK_IF_WRITE_4(sc_if, 0, SK_GMAC_CTRL, SK_GMAC_LOOP_OFF |
SK_GMAC_PAUSE_ON | SK_GMAC_RESET_CLEAR);
+#endif
DPRINTFN(3, (msk_init_yukon: gmac_ctrl=%#x\n,
SK_IF_READ_4(sc_if, 0, SK_GMAC_CTRL)));
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Both boxes and fiber NICs work fine under Solaris 9 using Syskonnect's proprietary skge driver and a short cross-over fiber patch. So it is definitely not an issue with with the hardware setup, but with OpenBSD. I'll have the fiber NICs for another 10 days before I'll deploy them in a customer's setup. Until then, I would be happy to apply any diffs and retest. Thanks, Rolf
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hi, On 1/30/07, Siegbert Marschall [EMAIL PROTECTED] wrote: Or, are you saying that the Marvell PHY 88112 does not really care about if T, SX or LX is set, because for the optical GBIC electrically all is the same? yupp, from the signal point of view in the moment you have optics it's all the same, just a question of power and wavelength. but as others found out, the phy/driver doesn't seem to know that there are any optics attached and thinks he's got a copper link which is not the same. -sm
msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hello misc, Two identically configured SUN V210, each equipped with a SK-9S91 PCI NIC (single port, single mode fiber 1 Gbit/s), run -current snapshot dated 20 Jan 07 The kernel detects those fiber NICs, besides the four on-board bge, see dmesg below. After boot, the msk0 come up in autoselect media type, but the two fiber NICs' link status remains at no carrier, despite having connected the two NIC with a cross-over fiber patch cable and forcing them up. Forcing the media type 1000baseSX according to msk(4) fails: # ifconfig msk0 media 1000baseSX ifconfig: SIOCSIFMEDIA: Invalid argument # Indeed, this option is missing in the list of media types and options supported by the card: # ifconfig -m msk0 msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:58 media: Ethernet autoselect (100baseTX half-duplex) status: no carrier supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media 1000baseT media 1000baseT mediaopt full-duplex media autoselect inet6 fe80::200:5aff:fe72:fc58%msk0 prefixlen 64 scopeid 0x5 inet 10.10.0.218 netmask 0xff00 broadcast 10.10.0.255 # Maybe I am mistaken by assuming that 1000baseSX should be accepted by msk() for these NICs? After taking a look at the msk() and eephy() driver sources, I still can not figure out if I have a misconception about the use of msk(), or the fiber NICs features, or even if there is a problem with the driver(s) and Gig fiber support. Both fiber NICs are new out-of-the-box. To exclue any hardware problem, I might test them under Solaris 8, According to prior experience, I know that they should work after installing a suitable driver. I can patch and re-test, if this should be of interest. Thanks for any hints and suggestions, Rolf # dmesg console is /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.0-current (GENERIC) #1049: Fri Jan 19 18:36:23 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 1073741824 avail memory = 969416704 using 6553 buffers containing 53682176 bytes of memory bootpath: /[EMAIL PROTECTED],60/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Fire V210 cpu0 at mainbus0: SUNW,UltraSPARC-IIIi (rev 3.4) @ 1336 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 64K data (32 b/l), 1024K external (64 b/l) memory-controller at mainbus0 not configured schizo0 at mainbus0: Tomatillo, version 4, ign 7c0, bus B 0 to 0 schizo0: dvma map c000-dfff, iotdb 4d16000-4d96000 pci0 at schizo0 bge0 at pci0 dev 2 function 0 Broadcom BCM5704C rev 0x00, BCM5704 B0 (0x2100): ivec 0x7c8, address 00:14:4f:64:0c:52 brgphy0 at bge0 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 bge1 at pci0 dev 2 function 1 Broadcom BCM5704C rev 0x00, BCM5704 B0 (0x2100): ivec 0x7c9, address 00:14:4f:64:0c:53 brgphy1 at bge1 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 schizo1 at mainbus0: Tomatillo, version 4, ign 780, bus A 0 to 0 schizo1: dvma map c000-dfff, iotdb 547e000-54fe000 pci1 at schizo1 ebus0 at pci1 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 flashprom at ebus0 addr 0-f, 290-290 not configured rtc0 at ebus0 addr 70-71: m5819p pcfiic0 at ebus0 addr 320-321 ipl 46 iic0 at pcfiic0 SUNW,i2c-imax at iic0 addr 0xb not configured SUNW,i2c-imax at iic0 addr 0xc not configured at24c64 at iic0 addr 0x51 not configured at24c64 at iic0 addr 0x54 not configured at24c64 at iic0 addr 0x58 not configured at34c02 at iic0 addr 0x5b not configured at34c02 at iic0 addr 0x5c not configured at34c02 at iic0 addr 0x5d not configured at34c02 at iic0 addr 0x5e not configured ds1307 at iic0 addr 0x68 not configured at24c64 at iic0 addr 0x28 not configured pca9555 at iic0 addr 0x22 not configured pca9555 at iic0 addr 0x23 not configured pca9555 at iic0 addr 0x34 not configured pca9556 at iic0 addr 0x38 not configured power0 at ebus0 addr 800-82f ipl 32: can't map register space com0 at ebus0 addr 3f8-3ff ipl 44: ns16550a, 16 byte fifo com0: console com1 at ebus0 addr 2e8-2ef ipl 44: ns16550a, 16 byte fifo rmc-comm at ebus0 addr 3e8-3ef ipl 44 not configured Acer Labs M7101 Power rev 0x00 at pci1 dev 6 function 0 not configured ohci0 at pci1 dev 10 function 0 Acer Labs M5237 USB rev 0x03: ivec 0x7a7, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Acer Labs OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pciide0 at pci1 dev 13 function 0 Acer Labs M5229 UDMA IDE rev 0xc4: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0:
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hi, # ifconfig -m msk0 msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:58 media: Ethernet autoselect (100baseTX half-duplex) status: no carrier supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media 1000baseT media 1000baseT mediaopt full-duplex media autoselect inet6 fe80::200:5aff:fe72:fc58%msk0 prefixlen 64 scopeid 0x5 inet 10.10.0.218 netmask 0xff00 broadcast 10.10.0.255 # Maybe I am mistaken by assuming that 1000baseSX should be accepted by msk() for these NICs? try media 1000baseT mediaopt full-duplex , 1G fiberlinks should be always fullduplex, rest ist not relevant since it's purely a hardware- question. wonder how the thing got it's head on 100BaseTX... apart from that it's a good idea to test them with something else, to make sure the fibers are crossed and signal-levels are okay. with single-mode fiber and short cables sometimes you need to insert a dampening-block since the signal can be too strong for the receiver, don't think it's the case here though. -sm
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
On 1/30/07, Siegbert Marschall [EMAIL PROTECTED] wrote: try media 1000baseT mediaopt full-duplex , 1G fiberlinks should be always fullduplex, rest ist not relevant since it's purely a hardware- question. wonder how the thing got it's head on 100BaseTX... apart from that it's a good idea to test them with something else, to make sure the fibers are crossed and signal-levels are okay. with single-mode fiber and short cables sometimes you need to insert a dampening-block since the signal can be too strong for the receiver, don't think it's the case here though. Thanks for your quick reply. Unfortunately, this does not activate the link either: # ifconfig msk0 media 1000baseT mediaopt full-duplex # ifconfig -m msk0 msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:58 media: Ethernet 1000baseT full-duplex (none) status: no carrier supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media 1000baseT media 1000baseT mediaopt full-duplex media autoselect inet6 fe80::200:5aff:fe72:fc58%msk0 prefixlen 64 scopeid 0x5 inet 10.10.0.218 netmask 0xff00 broadcast 10.10.0.255 # Three months ago I used the exact same fiber patch cable with two other SK-9S91 under Solaris 8 in some other V210 or V240, and the fiber link worked fine back then. Thus, the fiber should be OK (crossover, attenuation, etc.). But will cross-check that by installing Solaris again. Further, I noticed ifmedia(4) differentiates between 1000baseT, SX and LX. From this I actually realize that I should be able to set 1000baseLX for single mode fiber, not SX which is for multi mode fiber. Or, are you saying that the Marvell PHY 88112 does not really care about if T, SX or LX is set, because for the optical GBIC electrically all is the same? Rolf
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
* Rolf Sommerhalder [EMAIL PROTECTED] [2007-01-30 21:48]: Two identically configured SUN V210, each equipped with a SK-9S91 PCI NIC (single port, single mode fiber 1 Gbit/s), run -current snapshot dated 20 Jan 07 The kernel detects those fiber NICs, besides the four on-board bge, see dmesg below. After boot, the msk0 come up in autoselect media type, but the two fiber NICs' link status remains at no carrier, despite having connected the two NIC with a cross-over fiber patch cable and forcing them up. Forcing the media type 1000baseSX according to msk(4) fails: # ifconfig msk0 media 1000baseSX ifconfig: SIOCSIFMEDIA: Invalid argument # Indeed, this option is missing in the list of media types and options supported by the card: # ifconfig -m msk0 msk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5a:72:fc:58 media: Ethernet autoselect (100baseTX half-duplex) status: no carrier supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media 1000baseT media 1000baseT mediaopt full-duplex media autoselect inet6 fe80::200:5aff:fe72:fc58%msk0 prefixlen 64 scopeid 0x5 inet 10.10.0.218 netmask 0xff00 broadcast 10.10.0.255 # Maybe I am mistaken by assuming that 1000baseSX should be accepted by msk() for these NICs? looks like the driver/phy driver lacks fibre support for the moment (or it's buggy. I dunno and am to lazy to check right now) -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hi Rolf, Most likely something is not quite right with the eephy(4) driver. The 88E1112 PHY apparently supports both copper and fiber, and I think it should automatically switch over to fiber, but apparently it doesn't. Could you test some diffs for me on that machine? Mark
Re: msk(4) with SK-9S91: Can not set 1000baseSX Single Mode Fiber Media Type
Hi Mark
Most likely something is not quite right with the eephy(4) driver.
eephy_status() in sys/dev/mii/eephy.c seems to be a candidate for
closer examination. It appears to fall through the if() clause and
does the else part, although we have a NIC with MIIF_IS_1000X :
319:if (sc-mii_flags MIIF_IS_1000X) {
320:if (ssr E1000_SSR_1000MBS)
321:
mii-mii_media_active |= IFM_1000_SX;
322:} else {
323:if (ssr E1000_SSR_1000MBS)
324:
mii-mii_media_active |= IFM_1000_T;
325:else if (ssr E1000_SSR_100MBS)
326:
mii-mii_media_active |= IFM_100_TX;
327:else
328:
mii-mii_media_active |= IFM_10_T;
329:}
Could you test some diffs for me on that machine?
Yes, I am happy to do that - I hope that I can continue to use those
two machines over the next few days. Just preparing them with CVSupped
source tree.
Rolf
