From: joy <gracecott@sancharnet.in>
To: James Miller <jamtat@mailsnare.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: net (& module, I guess) problems after dist-upgrade
Date: Sun, 13 Jun 2004 10:13:07 +0530 [thread overview]
Message-ID: <40CBDB5B.7060105@sancharnet.in> (raw)
In-Reply-To: <Pine.LNX.4.58.0406121719540.1071@debian-emach>
James Miller wrote:
>This has all been a long-winded preface to the question: what
>the heck I gotta do to get my NIC modules back to loading on boot? Am I
>
>
Well, since you know the modules to be loaded , the quick and dirty
solution would be to put a shell script
in /etc/init.d which says modprobe this and modprobe that.... followed
by an ifup -a (just to be sure!)
I used this and works fine for me......
>gonna run into other module problems as well? What's the way to start
>
>
That's somthing you'll have to wait and watch (I guess;-)
>this process that gets the module loading routine working as it should be?
>I think there was a reference to modules.dep or maybe modules.conf in that
>message I saw during dist-upgrade. But there was definitely nothing there
>telling me how I could manually start the process that couldn't finish
>during dist-upgrade. Any pointers, please?
>
>Thanks, James
>
>PS Most of the above refers to having booted using the new kernel (2.6.6,
>though some of those boots were with the old 2.6.5 kernel and one was even
>with the 2.4.22 kernel). None of those were able to use eth0 and gave the
>same error message during the boot process.
>
>
possibly modules .conf was to be written on bootup or something....?.
regards, Joy.M.M
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-06-13 4:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 21:01 Debian Sid startup problems James Miller
2004-06-11 23:15 ` Ray Olszewski
2004-06-12 1:05 ` James Miller
2004-06-12 1:55 ` Ray Olszewski
2004-06-12 2:21 ` James Miller
2004-06-12 3:12 ` James Miller
2004-06-12 4:36 ` James Miller
2004-06-12 5:08 ` Ray Olszewski
2004-06-12 16:20 ` James Miller
2004-06-12 18:04 ` chuck gelm
2004-06-12 18:10 ` James Miller
2004-06-12 18:47 ` James Miller
2004-06-12 18:32 ` Ray Olszewski
2004-06-12 19:04 ` James Miller
2004-06-12 19:27 ` Ray Olszewski
2004-06-12 19:50 ` James Miller
2004-06-12 22:36 ` net (& module, I guess) problems after dist-upgrade James Miller
2004-06-13 3:57 ` Ray Olszewski
2004-06-14 15:01 ` James Miller
2004-06-14 16:35 ` Ray Olszewski
2004-06-14 17:33 ` James Miller
2004-06-14 18:06 ` James Miller
2004-06-14 18:50 ` Ray Olszewski
2004-06-14 19:13 ` James Miller
2004-06-14 22:44 ` James Miller
2004-06-14 19:25 ` pa3gcu
2004-06-13 4:43 ` joy [this message]
2004-06-12 1:36 ` Debian Sid startup problems James Miller
2004-06-12 2:07 ` Ray Olszewski
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=40CBDB5B.7060105@sancharnet.in \
--to=gracecott@sancharnet.in \
--cc=jamtat@mailsnare.net \
--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