From: "Amin" <raihan@citech-bd.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Network card and kernel module problems
Date: Wed, 5 Feb 2003 10:47:33 +0600 [thread overview]
Message-ID: <000001c2ccd7$bcfb0e80$eb6510ac@citechbd.com> (raw)
In-Reply-To: 5.1.0.14.1.20030203091129.02140130@celine
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hi people,
First --- sorry about not including specific error messages earlier. The
attached file is a (snipped) list of bootup messages, and contains the
messages I'm concerned with.
I've decided to reinstall, perhaps try a different distro, and see if that
will do the trick. And thanks
to Lawson for pointing out the EXTRAVERSION point. Just want to make sure
about something --- you're talking about
/usr/src/linux-2.4.18-14/Makefile, right?
Yawar Amin
P.S. Is it a good sign or a bad sign that I've got my kernel version
memorized?
[-- Attachment #2: startup_errors.txt --]
[-- Type: text/plain, Size: 3107 bytes --]
...
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol try_inc_mod_count_Re6105b23
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol jiffies_R0da02d67
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol del_timer_Rfc62f16d
Feb 4 15:41:26 localhost netfs: Mounting other filesystems: succeeded
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol sprintf_R1d26aa98
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol printk_R1b7d4074
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod /lib/modules/2.4.18-14/kernel/drivers/input/input.o failed
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod keybdev failed
Feb 4 15:40:45 localhost rc.sysinit: Initializing USB keyboard: failed
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o:
Feb 4 15:40:45 localhost modprobe: unresolved symbol mod_timer_R1f13d309
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol unregister_chrdev_Rc192d491
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol register_chrdev_R44b36f42
Feb 4 15:41:27 localhost autofs: automount startup succeeded
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol request_module_R27e4dc04
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol try_inc_mod_count_Re6105b23
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol jiffies_R0da02d67
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol del_timer_Rfc62f16d
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol sprintf_R1d26aa98
Feb 4 15:41:27 localhost sshd: Starting sshd:
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: unresolved symbol printk_R1b7d4074
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod /lib/modules/2.4.18-14/kernel/drivers/input/input.o failed
Feb 4 15:40:45 localhost modprobe: /lib/modules/2.4.18-14/kernel/drivers/input/input.o: insmod mousedev failed
... [snip]
Feb 4 15:41:15 localhost network: Setting network parameters: succeeded
Feb 4 15:41:16 localhost network: Bringing up loopback interface: succeeded
Feb 4 15:41:17 localhost ifup:
Feb 4 15:41:17 localhost ifup: Determining IP information for eth0...
Feb 4 15:41:22 localhost ifup: failed; no link present. Check cable?
Feb 4 15:41:22 localhost network: Bringing up interface eth0: failed
...
next prev parent reply other threads:[~2003-02-05 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 15:56 Network card and kernel module problems Amin
2003-02-02 16:15 ` pa3gcu
2003-02-03 12:09 ` Amin
2003-02-03 16:55 ` pa3gcu
2003-02-04 21:52 ` whitnl73
2003-02-03 17:24 ` Ray Olszewski
2003-02-05 4:47 ` Amin [this message]
2003-02-05 6:21 ` Ray Olszewski
2003-02-05 20:24 ` whitnl73
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 15:24 Whitnl73@juno.com
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='000001c2ccd7$bcfb0e80$eb6510ac@citechbd.com' \
--to=raihan@citech-bd.com \
--cc=linux-newbie@vger.kernel.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