Professional Web Applications Themes

Dell PowerEdge 1600sc NIC - SCO

SCO openserver 5.07, MP1, all patches to date. Can't figure right driver for built-in NIC on Dell PowerEdge 1600sc. dell support claimed was intel pro 100, but i don't think he's correct (well, at least it did not recognize card when used that driver) closest i came is the Intel Pro 1000 - after the mp1 update, but with Bus 0/Device 2/Function 0 - i get a ton of garbage spewed onto the console (even though card works and is recognized) from the eeG driver. "Queue (some large negative # that changes) allready open" for now, disabled and went back ...

  1. #1

    Default Dell PowerEdge 1600sc NIC

    SCO openserver 5.07, MP1, all patches to date.

    Can't figure right driver for built-in NIC on Dell PowerEdge 1600sc.

    dell support claimed was intel pro 100, but i don't think he's correct
    (well, at least it did not recognize card when used that driver)

    closest i came is the Intel Pro 1000 - after the mp1 update, but
    with Bus 0/Device 2/Function 0 - i get a ton of garbage spewed onto
    the console (even though card works and is recognized) from the eeG driver.

    "Queue (some large negative # that changes) allready open"

    for now, disabled and went back to my trusty 3com 905b...

    anyone know correct driver?

    --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
    -Joe Chasan- Magnatech Business Systems, Inc.
    com Hicksville, NY - USA
    http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264
    Joe Guest

  2. #2

    Default Re: Dell PowerEdge 1600sc NIC

    "Joe Chasan" <com> wrote in message
    news:magnatechonline.com... 
    driver. 


    Joe,
    I just installed SCO OpenServer 5.0.6 on a new Dell 1600 SC. When I
    ordered the server from Dell, the techies said that the integrated nic was
    not compatable with SCO. I ordered a seperate nic that was supported. The
    specs on the Dell website says that the integrated nic is an Intel Gigabit
    Nic with PXE support. I know this is not much help but thought I would pass
    it on.
    Dale


    Dale Guest

  3. #3

    Default Re: Dell PowerEdge 1600sc NIC

    Joe Chasan wrote:
     

    Run `hr -v -r pci > /tmp/pci`. Find the entry that describes the
    network controller, post it. Then we'll know for sure what actual
    hardware it is.
     
    Bela Guest

  4. #4

    Default Re: Dell PowerEdge 1600sc NIC

    Bela Lubkin wrote (on Fri, Aug 29, 2003 at 06:30:32PM +0000): 
    >
    > Run `hr -v -r pci > /tmp/pci`. Find the entry that describes the
    > network controller, post it. Then we'll know for sure what actual
    > hardware it is.
    > [/ref]

    You mean hw, right?

    --
    _________________________________________
    Nachman Yaakov Ziskind, EA, LLM com
    Attorney and Counselor-at-Law http://yankel.com
    Economic Group Pension Services http://egps.com
    Actuaries and Employee Benefit Consultants
    Nachman Guest

  5. #5

    Default Re: Dell PowerEdge 1600sc NIC

    On Fri, Aug 29, 2003 at 06:30:32PM +0000, Bela Lubkin wrote: 
    >
    > Run `hr -v -r pci > /tmp/pci`. Find the entry that describes the
    > network controller, post it. Then we'll know for sure what actual
    > hardware it is.[/ref]

    the pertinent part...

    Index: 2
    DeviceNum: 2
    Function: 0
    Bus: 0
    VendorId: 0x8086 Intel
    DeviceId: 0x100e
    RevId: 0x02
    Command: 0x0117 Memory Enabled, I/O Enabled
    Status: 0x0230
    ClassCode: 0x020000 Ethernet controller
    CacheLineSize: 16 32 bit words
    LatencyTimer: 0x20
    HeaderType: 0x00 Single-function, Standard encoding
    SelfTest: 0x00 Not BIST capable
    BaseAddr[0]: 0xfe100000 Memory 0xfe100000, 32 bit space
    BaseAddr[1]: 0x00000000
    BaseAddr[2]: 0x0000ecc1 I/O 0xecc0
    BaseAddr[3]: 0x00000000
    BaseAddr[4]: 0x00000000
    BaseAddr[5]: 0x00000000
    CardbusCISPtr: 0x00000000
    SubsysVendorID: 0x1028 Dell Computer Corporation
    SubsystemID: 0x0135
    ROMbaseAddress: 0x00000000 Expan ROM 0x00000000, Disabled
    InterruptLine: 0x0b IRQ-11
    InterruptPin: 0x01 INTA
    Min_Gnt: 0xff
    Max_Lat: 0x00
    New Capabilities
    CapPtr: 0xdc
    CapID: 0x01 PCI Power Management (PM)
    NxtCapPtr: 0xe4
    CapID: 0x07
    NxtCapPtr: 0xf0
    CapID: 0x05 Message Signaled Interrupts (MSI)
    NxtCapPtr: 0x00 (End of list)

    --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
    -Joe Chasan- Magnatech Business Systems, Inc.
    com Hicksville, NY - USA
    http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264
    Joe Guest

  6. #6

    Default Re: Dell PowerEdge 1600sc NIC

    Joe Chasan wrote:
     [/ref][/ref]
     

    Ok, that's definitely an Intel Pro/1000 (gigabit) card. What did you
    mean by "but with Bus 0/Device 2/Function 0"? Did you mean that
    `netconfig` didn't automatically recognize the card, and you had to
    identify it by bus/device/function? Because it should have been
    recognized automatically.

    I forget whether ORS507MP1 includes the Pro/1000 driver ("eeG"), or
    whether it's a separate download. What does:

    # what /etc/conf/pack.d/eeG/Driver.o

    say? I'm getting:

    eeG - Intel Gigabit, SCO OSR5 MDI driver, Ver 1.0.8 (09Apr2003 16:03)

    That driver package -- the one associated with, but I'm not sure if
    actually installed as part of MP1 -- is supposed to autodetect that
    chip.

    Can you check /usr/adm/syslog for when you had the driver active, and
    post a section of the messages it spewed, starting with the first one
    after boot time and continuing until they are clearly repetitive? I'm
    hoping to see the actual pattern of "some large negative # that
    changes", as well as timing. And any other messages from the driver
    that don't match that pattern.
     
    Bela Guest

  7. #7

    Default Re: Dell PowerEdge 1600sc NIC

    Bela Lubkin typed (on Sat, Aug 30, 2003 at 10:05:11PM +0000):
    | Joe Chasan wrote:
    |
    | > > > SCO openserver 5.07, MP1, all patches to date.
    | > > >
    | > > > Can't figure right driver for built-in NIC on Dell PowerEdge 1600sc.
    | > > >
    | > > > dell support claimed was intel pro 100, but i don't think he's correct
    | > > > (well, at least it did not recognize card when used that driver)
    | > > >
    | > > > closest i came is the Intel Pro 1000 - after the mp1 update, but
    | > > > with Bus 0/Device 2/Function 0 - i get a ton of garbage spewed onto
    | > > > the console (even though card works and is recognized) from the eeG driver.
    | > > >
    | > > > "Queue (some large negative # that changes) allready open"
    |
    | > Index: 2
    | > DeviceNum: 2
    | > Function: 0
    | > Bus: 0
    | > VendorId: 0x8086 Intel
    | > DeviceId: 0x100e
    | > ClassCode: 0x020000 Ethernet controller
    | > SubsysVendorID: 0x1028 Dell Computer Corporation
    | > SubsystemID: 0x0135
    |
    | Ok, that's definitely an Intel Pro/1000 (gigabit) card. What did you
    | mean by "but with Bus 0/Device 2/Function 0"? Did you mean that
    | `netconfig` didn't automatically recognize the card, and you had to
    | identify it by bus/device/function? Because it should have been
    | recognized automatically.
    |
    | I forget whether ORS507MP1 includes the Pro/1000 driver ("eeG"), or
    | whether it's a separate download. What does:
    |
    | # what /etc/conf/pack.d/eeG/Driver.o
    |
    | say? I'm getting:
    |
    | eeG - Intel Gigabit, SCO OSR5 MDI driver, Ver 1.0.8 (09Apr2003 16:03)
    |
    | That driver package -- the one associated with, but I'm not sure if
    | actually installed as part of MP1 -- is supposed to autodetect that
    | chip.

    Yes, see osr507mp1.[pdf|htm|txt]:
    This Maintenance Pack includes version 1.0.8 of the eeG
    driver...

    --
    JP
    Jean-Pierre Guest

  8. #8

    Default Re: Dell PowerEdge 1600sc NIC

    On Sat, Aug 30, 2003 at 10:05:11PM +0000, Bela Lubkin wrote: [/ref]

    >
    > Ok, that's definitely an Intel Pro/1000 (gigabit) card. What did you
    > mean by "but with Bus 0/Device 2/Function 0"? Did you mean that
    > `netconfig` didn't automatically recognize the card, and you had to
    > identify it by bus/device/function? Because it should have been
    > recognized automatically.
    >
    > I forget whether ORS507MP1 includes the Pro/1000 driver ("eeG"), or
    > whether it's a separate download. What does:
    >
    > # what /etc/conf/pack.d/eeG/Driver.o
    >
    > say? I'm getting:
    >
    > eeG - Intel Gigabit, SCO OSR5 MDI driver, Ver 1.0.8 (09Apr2003 16:03)
    >
    > That driver package -- the one associated with, but I'm not sure if
    > actually installed as part of MP1 -- is supposed to autodetect that
    > chip.[/ref]

    was autodetected with eeG/Pro/1000 with correct device/function/etc after
    mp1 installed
     

    Aug 29 08:42:37 mbsi WARNING: eeG: Queue -265414168 allready open
    Aug 29 08:42:38 mbsi last message repeated 84 times
    Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413960 allready open
    Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413960 allready open
    Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413908 allready open
    Aug 29 08:42:38 mbsi last message repeated 5 times
    Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413804 allready open
    Aug 29 08:42:39 mbsi last message repeated 7 times
    Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413752 allready open
    Aug 29 08:42:39 mbsi last message repeated 3 times
    Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413700 allready open
    Aug 29 08:42:39 mbsi last message repeated 5 times
    Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413804 allready open
    Aug 29 08:43:02 mbsi last message repeated 46 times
    Aug 29 08:43:37 mbsi last message repeated 8 times
    Aug 29 08:43:37 mbsi WARNING: eeG: Queue -265413752 allready open
    Aug 29 08:43:38 mbsi last message repeated 9 times
    Aug 29 08:44:28 mbsi WARNING: eeG: Queue -265413804 allready open

    --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
    -Joe Chasan- Magnatech Business Systems, Inc.
    com Hicksville, NY - USA
    http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264
    Joe Guest

  9. #9

    Default Re: Dell PowerEdge 1600sc NIC

    Joe Chasan wrote:
     
    > > [/ref]
    >
    > was autodetected with eeG/Pro/1000 with correct device/function/etc after
    > mp1 installed
    >
    > Aug 29 08:42:37 mbsi WARNING: eeG: Queue -265414168 allready open
    > Aug 29 08:42:38 mbsi last message repeated 84 times
    > Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413960 allready open
    > Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413960 allready open
    > Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413908 allready open
    > Aug 29 08:42:38 mbsi last message repeated 5 times
    > Aug 29 08:42:38 mbsi WARNING: eeG: Queue -265413804 allready open
    > Aug 29 08:42:39 mbsi last message repeated 7 times
    > Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413752 allready open
    > Aug 29 08:42:39 mbsi last message repeated 3 times
    > Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413700 allready open
    > Aug 29 08:42:39 mbsi last message repeated 5 times
    > Aug 29 08:42:39 mbsi WARNING: eeG: Queue -265413804 allready open
    > Aug 29 08:43:02 mbsi last message repeated 46 times
    > Aug 29 08:43:37 mbsi last message repeated 8 times
    > Aug 29 08:43:37 mbsi WARNING: eeG: Queue -265413752 allready open
    > Aug 29 08:43:38 mbsi last message repeated 9 times
    > Aug 29 08:44:28 mbsi WARNING: eeG: Queue -265413804 allready open[/ref]

    Besides TCP/IP, do you have any other network protocol stacks in your
    kernel? I'm thinking of things like:

    IPX/SPX
    LAN Manager Server using NetBEUI
    AFPS using NetBEUI
    DECNET
    tcpdump

    The message you're getting comes from eeG_open(), which normally ought
    be called exactly once between boot and shutdown. You say it _does_
    work, so these opens must be additional ones being done by something
    other than IP. I can easily imagine that if the other protocol stack's
    open failed, it would persistently try again, leading to this endless
    stream of failures.

    Any Windows networking stack that uses NetBIOS should be OK (Samba,
    VisionFS, AFPS or LAN Manager Server over NetBIOS) -- NetBIOS is a
    protocol on top of TCP/IP and wouldn't be trying to talk to the card at
    that level.
     
    Bela Guest

Similar Threads

  1. Dell computers
    By Don77 webforumsuser@macromedia.com in forum Macromedia Flash Actionscript
    Replies: 8
    Last Post: February 7th, 11:15 AM
  2. OT- DELL = HELL
    By Bill Ray in forum Macromedia Fireworks
    Replies: 14
    Last Post: August 3rd, 10:13 PM
  3. new HOWTO: debian on a dell i8k
    By nori heikkinen in forum Debian
    Replies: 0
    Last Post: June 29th, 07:00 AM
  4. Dell 2000FP Profile
    By Hokuahi in forum Adobe Photoshop 7, CS, CS2 & CS3
    Replies: 0
    Last Post: June 28th, 07:03 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139