Re: Dell PowerEdge 1600sc NIC

From: Bela Lubkin (belal_at_sco.com)
Date: 08/31/03 

Date: Sat, 30 Aug 2003 22:05:11 GMT
To: scomsc@xenitec.ca

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.

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<

Relevant Pages

  • RE: [UPDATED PATCH] EFI support for ia32 kernels
    ... >> reuse a single driver image for multiple architectures assuming there ... As one of the people responsible for the EFI Specification and our ... Perhaps the UNDI network card interface that Intel developed ... BIOS can't shadow that much ROM code. ...
    (Linux-Kernel)
  • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
    ... >> because, originally, video cards / system RAM could NOT afford to have ... > GL actually "copies" everything, but it's done by the graphics card, so ... > anyway if it's not hardware accelerated. ... installed the proper driver, then it zooms around the screen... ...
    (alt.lang.asm)
  • Re: XXX_Init only being called once
    ... > My stream interface driver has been stripped right back to try to solve ... > I plug my card in the first time. ... > There are two new active keys in the registry PCMCIA and myDriver. ... > No entry points are called in my driver. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: WDF storage driver is a dead-end street
    ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ... AHCI controller card, etc. ... Since the extension is passed in the miniport at ... So I need to create a virtual adapter out of two physical adapters. ...
    (microsoft.public.development.device.drivers)
  • Re: VIA Envy24PT sound card driver loads at startup properly 9 of 10 times
    ... driver updates including the latest and correct driver for the sound card. ... Onboard sound chip is disabled in BIOS and the driver for it is not installed. ... The sound card, Chaintech, Envy24 Family Audio Controller WDM, is installed/seated properly and uses the IRQ 16 exclusively. ...
    (microsoft.public.windowsxp.hardware)