public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Gulik <greg-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Newbie looking to try latest ACPI support...
Date: Mon, 09 Dec 2002 10:12:54 -0500	[thread overview]
Message-ID: <3DF4B2F6.6070400@gulik.org> (raw)
In-Reply-To: <3DF4A54F.2030400-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>


I did that my starting with a clean 2.4.20 kernel, applied the 
acpi-20021205-2.4.20.diff patches, reconfigured my kernel, did the 
correct kernel build procedure.  Everything worked without apparent 
error and I do have files in the acpi driver directory:

[root@toshiba1115 pcmcia-cs-3.2.3]# ls 
/lib/modules/2.4.20/kernel/drivers/acpi/
ac.o  battery.o  button.o  fan.o  processor.o  thermal.o  toshiba_acpi.o


While updating my PCMCIA driver I saw the following errors:

make[2]: Leaving directory `/usr/src/pcmcia-cs-3.2.3/etc/cis'
-> Updating client scripts in /etc/pcmcia
-> Running depmod...
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/ac.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/battery.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/button.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/fan.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/processor.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/thermal.o
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20/kernel/drivers/acpi/toshiba_acpi.o
make[1]: Leaving directory `/usr/src/pcmcia-cs-3.2.3/etc'
[root@toshiba1115 pcmcia-cs-3.2.3]#

Is this anything to worry about??

Gregory Gulik wrote:
> Maybe I'll just wipe out that directory and start all over with a fresh 
> copy of the kernel sources and acpi patch...

-- 
Greg Gulik                                 http://www.gulik.org/greg/
greg @ gulik.org                           http://www.drivingevents.com/




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2002-12-09 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07 14:50 Newbie looking to try latest ACPI support Gregory Gulik
     [not found] ` <3DF20AB4.3020205-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>
2002-12-07 15:11   ` Sander Smeenk
2002-12-09 10:51   ` Ducrot Bruno
     [not found]     ` <20021209105144.GB26375-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-12-09 13:56       ` Gregory Gulik
     [not found]         ` <3DF4A0F4.6060103-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>
2002-12-09 14:07           ` Matthew Wilcox
     [not found]             ` <20021209140714.H20336-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-12-09 14:14               ` Gregory Gulik
     [not found]                 ` <3DF4A54F.2030400-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>
2002-12-09 15:12                   ` Gregory Gulik [this message]
     [not found]                     ` <3DF4B2F6.6070400-eIr5aKVv5JjYtjvyW6yDsg@public.gmane.org>
2002-12-09 20:20                       ` Gregory Gulik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DF4B2F6.6070400@gulik.org \
    --to=greg-eir5akvv5jjytjvyw6ydsg@public.gmane.org \
    --cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox