From: Jeff Chua <jeffchua@silk.corp.fedex.com>
To: linux-kernel@silk.corp.fedex.com, jchua@fedex.com
Subject: unresolved symbols in 2.4.0-test13-pre4
Date: Thu, 28 Dec 2000 21:32:46 +0800 [thread overview]
Message-ID: <200012281332.eBSDWkv20288@silk.corp.fedex.com> (raw)
upgraded to test13-pre4. When I ran "depmod -a", I got a lot of errors
about unresolved symbols for the drm modules ...
depmod: *** Unresolved symbols in /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/i810.o
depmod: *** Unresolved symbols in /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/mga.o
depmod: *** Unresolved symbols in /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/r128.o
depmod: *** Unresolved symbols in /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/tdfx.o
"depmod -ae" shows the following ....
depmod: *** Unresolved symbols in /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/i810.o
depmod: remap_page_range
depmod: __wake_up
depmod: mtrr_add
depmod: __generic_copy_from_user
depmod: schedule
depmod: kmalloc
depmod: si_meminfo
depmod: create_proc_entry
depmod: inter_module_put
depmod: __get_free_pages
depmod: boot_cpu_data
depmod: inter_module_get
depmod: remove_wait_queue
depmod: high_memory
depmod: iounmap
depmod: free_pages
depmod: __ioremap
depmod: del_timer
depmod: interruptible_sleep_on
depmod: __pollwait
depmod: kfree
depmod: remove_proc_entry
depmod: pci_find_slot
depmod: kill_fasync
depmod: fasync_helper
depmod: add_wait_queue
depmod: do_mmap_pgoff
depmod: mem_map
depmod: sprintf
depmod: jiffies
depmod: printk
depmod: add_timer
depmod: __generic_copy_to_user
(repeat for the other 3 modules ...)
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-28 14:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200012281332.eBSDWkv20288@silk.corp.fedex.com \
--to=jeffchua@silk.corp.fedex.com \
--cc=jchua@fedex.com \
--cc=linux-kernel@silk.corp.fedex.com \
/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
all inboxes | Powered by JetHome®