SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 11 | September | 2005 ]

<< Previous Message << >> Next Message >>


Date: Sun, 11 Sep 2005 19:59:34 PDT7
From: "Michael Rakijas" <mrakijas@adelphia.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Ethernet IRQ and SPCIIRQ related questions

I'm still trying to get eCS fully working on what I hope will become my main
production machine. I generally install a minimal system first before adding
the bells and whistles later - the core install went okay. At initial install,
since I didn't know what the mainboard Ethernet implementation was, I installed
the IBMNULL driver so that I could run NICPAK after installation.

So far, so good. I found the proper driver for the VIA chipset, FETND.OS2 and
the associated .NIF file. It installed okay but seems to load strangely.
During boot up, the data shown at the loading of the driver says IRQ=0xB, which
implies to me that it is using IRQ11. I go to the device manager and it shows
the Ethernet hardware device in the equipment list as using IRQ10. Also, using
IRQ10 is the EHCI Compatible USB Host Controller. However, there are two
entries for IRQ11 as well. They both for UHCI Compatible USB Host Controllers.
LANTRAN.LOG seems to show an IRQ conflict as well. It reports an LT00042 error
that FETND_nif was not able to bind because multiple adapters are trying to use
the same IRQ level.

Fine, I say. So, I go to SPCIIRQ to try and get a change in the IRQ ... but
which? Report in SPCIIRQ says for the Ethernet device as Bus=0, Device=18,
Function=0 Ethernet(11) despite what the device manager says. So, the device
line in CONFIG.SYS reads either BASEDEV=SPCIIRQ.SYS 0 18 0 1 10 or
BASEDEV=SPCIIRQ.SYS 0 18 0 1 11 but both report an SPCIIRQ parameter error when
trying to load.

Could it be that SPCIIRQ is not able to change the IRQ for what is not an PCI
board (but mainboard) device? Why is it that even the OS can't get its IRQ
straight? Is there some way to tell the FETND device driver to change which
IRQ to trigger on? Any other suggestions? Thanks.

-Rocky

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 11 | September | 2005 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.