Re: Roadrunner & OS/2?

[A complimentary Cc of this posting was sent to

<mailNOT4Bob@xxxxxxxxxxxxx>], who wrote in article <44f5091a@kcnews03>:
Linksys LNE100X Fast Ethernet Adapter(LNE100TX v5) driver
Slot (Indx) number :1
IRQ number :0B
Ehternet Address: 00-14-BF-5C-B2-31

I have very little idea what this all means and, following these
messages, the system stops.

Probably your driver is a wrong one. There are about 5 (?) different
Linksys drivers. You need to pick up the correct one; there is no
simple way to determine which one it is. Linksys changes the chipset
used by their cards on random basis (maybe the most competitive by
price chipset of the current month?); in some years people could tell
you which driver to choose by the color of the box (!).

The driver on CD is almost definitely a wrong one. The general advice
is to avoid this mess and get a different adapter - now you know why.

Alternatively, try

http://pws.prserv.net/mckinnis/nicpak/

OR: my linksys was in a blue box (IIRC), and I use FASTNIC.OS2. PCI.EXE
reports:

Vendor 1317h ADMtek
Device 0985h AN983 FastNIC PCI 10/100 Fast Ethernet Adapter
Command 0017h (I/O Access, Memory Access, BusMaster,
MemWrite+Invalidate)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans.,
Medium Timin
g)
Revision 11h, Header Type 00h, Bus Latency A0h
Self test 00h (Self test not supported)
PCI Class Network, type Ethernet
Subsystem ID 05741317h LNE100TX Fast Ethernet Adapter
Subsystem Vendor 1317h ADMtek
Address 0 is an I/O Port : 00008800h
Address 1 is a Memory Address (anywhere in 0-4GiB) : DE800000h
System IRQ 5, INT# A
Expansion ROM of 128 KiB decoded by this card, currently disabled
New Capabilities List Present:
Power Management Capability, Version 1.1
Supports low power State D1
Supports low power State D2
Supports PME# from mode(s) D0, D1, D2, D3hot, D3cold
current requirement for 3.3Vaux: 100 mA
Current Power State : D0 (Device operational, no power saving)

Hope this helps,
Ilya
.

Relevant Pages

  • Re: [PATCH -mm] kexec jump -v9
    ... methods for each and every driver to handle that case, ... hibernation and suspend should be solved in separate patches. ... for a possible power state transition. ... @suspend place the device in a low power state. ...
    (Linux-Kernel)
  • Re: MCP2 on Intel 945 Mobo advice?
    ... I would try disabling all of the onboard hardware such as COM ports, NIC, audio, IEEE384, etc. and try a boot to see what works. ... No help, reverses a bit of the PCI sniff data, but the PCI NIC still works and the audio never does. ... If your two cards don't like to share an IRQ, your only solution would be to not use one. ... Supports low power State D1 ...
    (comp.os.os2.setup.misc)
  • Re: [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
    ... some devices support>1 low-power state which can be used to save ... not being used will most likely use the lowest power state, ... How, from the above message, is the driver to know that it's being asked ...
    (Linux-Kernel)
  • RE: why this API (SetSystemPowerState) can not change the system power
    ... are you calling SetSystemPowerState from a driver or from an application? ... So the driver must not assume that the request ... use a bitmask to describe the power state you want to change to ... My system power state is in useridle mode, when I got an event in my driver ...
    (microsoft.public.windowsce.embedded)
  • Re: [PATCH] call drv->shutdown at rmmod
    ... This has been one of the biggest problem areas ... You're assuming that a driver can always bring a device out a shutdown ... We have similar goals - introduce device power state code paths into ...
    (Linux-Kernel)