Your message dated 10 Apr 2001 02:53:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line smc-ultra issues
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Apr 2001 21:18:08 +0000
>From [EMAIL PROTECTED] Wed Apr 04 16:18:08 2001
Return-path: <[EMAIL PROTECTED]>
Received: from kleene.math.wisc.edu [144.92.166.90] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14kufH-00016y-00; Wed, 04 Apr 2001 16:18:08 -0500
Received: from grad7d.math.wisc.edu (grad7d.math.wisc.edu [144.92.166.215])
        by kleene.math.wisc.edu (8.9.3/8.9.3) with SMTP id QAA21636
        for <[EMAIL PROTECTED]>; Wed, 4 Apr 2001 16:18:06 -0500 (CDT)
Date: Wed, 4 Apr 2001 16:18:06 -0500 (CDT)
From: Jeffery Kline <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]

Package: kernel-image
Package: boot-floppies
Version: kernel versions 2.2.12 thru 2.2.18pre21

Cannot install smc-ultra module. error includes:

/lib/modules/2.2.17/net/smc-ultra.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters
/lib/modules/2.2.17/net/smc-ultra.o: insmod /lib/modules/2.2.17/net/smc-ultra.o failed
/lib/modules/2.2.17/net/smc-ultra.o: insmod smc-ultra failed


We have the correct io and irq params from each card (collected from dmesg
while running slink and using the slightly different output we get when
using the DOS utilities disk) -- we get the same error with both insmod
(after installing 8390, of course) and modprobe. We have compiled new
kernels with smc-ultra.o module and compiled smc-ultra support into the
kernel. We have attempted every combination of io/irq settings available
with modprobe and insmod (even settings we knew to be incorrect). We have
tried using the safe-boot floppies.  We reported this bug last July.  Net
searches produce minimal help and offer no new suggestions.  Three of our
staff have tried to solve this problem since April 2000.

We are stumped.

The cards _do_ work with slink. We have about 15 machines we wish to
upgrade to potato.

--Jeff



---------------------------------------
Received: (at 92919-done) by bugs.debian.org; 10 Apr 2001 06:52:52 +0000
>From [EMAIL PROTECTED] Tue Apr 10 01:52:52 2001
Return-path: <[EMAIL PROTECTED]>
Received: from arroz.onshored.com [216.220.101.2] (postfix)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14ms1E-0001EK-00; Tue, 10 Apr 2001 01:52:52 -0500
Received: from arroz.fake (localhost [127.0.0.1])
        by arroz.onshored.com (Postfix) with ESMTP id 8C16093802
        for <[EMAIL PROTECTED]>; Tue, 10 Apr 2001 02:53:37 -0400 (EDT)
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: smc-ultra issues
From: Adam Di Carlo <[EMAIL PROTECTED]>
Date: 10 Apr 2001 02:53:37 -0400
Message-ID: <[EMAIL PROTECTED]>
Lines: 12
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]


I have to close this bug.  It's not a boot-floppies issue but a kernel
issue.

Regarding documenting it, we are utterly incapable of documenting
every tweak for every bit of hardware and how to work around it.  Even
if we could, it changes too quickly.  The place for documentation like
this would be elsewhere, such as in the kernel documentation, hardware
FAQs, and the like.

-- 
.....Adam Di [EMAIL PROTECTED]<URL:http://www.onshored.com/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to