Your message dated Thu, 19 Apr 2001 23:08:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#94458: depmod after drivers installation fails because directory
is incorrect
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; 19 Apr 2001 02:30:22 +0000
>From [EMAIL PROTECTED] Wed Apr 18 21:30:22 2001
Return-path: <[EMAIL PROTECTED]>
Received: from cepheus.azstarnet.com [169.197.56.195]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14q4D7-00040O-00; Wed, 18 Apr 2001 21:30:21 -0500
Received: from [169.197.11.182] (dhcp950.mc01.dsl.azstarnet.com [169.197.11.182])
by cepheus.azstarnet.com (8.9.3/8.9.3) with ESMTP id TAA14146
for <[EMAIL PROTECTED]>; Wed, 18 Apr 2001 19:30:09 -0700 (MST)
Message-Id: <[EMAIL PROTECTED]>
X-Sent-via: StarNet http://www.azstarnet.com/
X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410)
Date: Wed, 18 Apr 2001 19:28:31 -0700
Subject: depmod after drivers installation fails because directory is
incorrect
From: "Chris Tillman" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Mime-version: 1.0
X-Priority: 3
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
Package: boot-floppies
Version: 2.2.23
After Install Operating System Kernel and Drivers completed, an error
message informed me that the drivers installation had failed. Looking in the
error log, I noted the error
depmod: No modules were found in /target/lib/modules/2.2.19 that could be
configured.
I went to Execute a Shell and navigated to /target/lib/modules and asked for
a ls, with the results
2.2.18pre21
Apparently a directory was created but with the incorrect revision number to
match the installation package.
---------------------------------------
Received: (at 94458-done) by bugs.debian.org; 20 Apr 2001 03:08:51 +0000
>From [EMAIL PROTECTED] Thu Apr 19 22:08:51 2001
Return-path: <[EMAIL PROTECTED]>
Received: from nevyn.res.cmu.edu (nevyn.them.org) [128.2.145.225] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14qRHu-0006Ql-00; Thu, 19 Apr 2001 22:08:50 -0500
Received: from drow by nevyn.them.org with local (Exim 3.22 #1 (Debian))
id 14qRHY-0006vg-00; Thu, 19 Apr 2001 23:08:28 -0400
Date: Thu, 19 Apr 2001 23:08:28 -0400
From: Daniel Jacobowitz <[EMAIL PROTECTED]>
To: Chris Tillman <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#94458: depmod after drivers installation fails because directory is
incorrect
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.16i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED]
on Thu, Apr 19, 2001 at 07:16:43PM -0700
Delivered-To: [EMAIL PROTECTED]
On Thu, Apr 19, 2001 at 07:16:43PM -0700, Chris Tillman wrote:
> Absolutely right, it was my mistake. I re-downloaded and re-burned floppies
> and it didn't complain about that.
Whew!
> What does it mean after installing drivers, when the error log gives
> messages like
>
> Unresolved symbols in /lib/modules/2.2.19/net/3c503.o
>
> I got a bunch of these messages.
It happens :) Don't worry about it unless you need one of the modules
with an error.
> I did, however, get all the way thru installation of the Base system, for
> the first time. I even tried make my hard disk bootable and it didn't
> complain, maybe it did something. Although it didn't boot into Linux.
Nope, it really didn't do anything. That'll get fixed some day...
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
