Thanks for the reply. See below. ----- Original Message ----- From: "Ray Olszewski" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 14, 2004 11:15 PM Subject: Re: [leaf-user] Module won't load
> At 08:27 PM 5/14/2004 -0400, ALParada wrote: > >Hi Everyone, > > > >I am having problems booting with the e1000 module, or at least I think that > >is the problem. It boots fine until it gets to "configuring network > >interfaces" then it hangs. I have tried it on several machines successfully, > >but they don't use that module. I tried a couple of different e1000 modules > >but with same result. I renamed the module and it booted, so I think that's > >the problem. I got the module from the modules.tar file which I think is the > >latest. I am currently running Bering on the PC that doesn't boot, and it > >works fine, so I don't think it is a hardware issue. Has anyone had this > >problem and how do I solve it? > > Your description is, I think, too hard to follow. Certainly too hard for > me, and I suspect for others as well. Please try again, and be more exact > about ... > > 1. What version of Bering you are using. I am using uClibc 2.1.1 > > 2. What version of the e1000 module you are using. (One from"the" > modules.tar file which you "think is the latest" is too vague.) Why do you > think it is the correct version for the kernel you are booting? It was the latest I could find: http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/modules.lrp > > 3. What NIC you are attempting to use the module with. And does this NIC > work in some other context (under Windows, or with a different Linux distro)? Intel Pro1000 currently working under Bering 1.2 > > 4. If you do not use /etc/modules to load the module, but instead wait > until boot/init is finished, then insmod it from the command line, what the > result is. Do you get any error message back to the console? I have not tried this. > > 5. The meaning of "hangs". How long do you wait before giving up? Does > CTRL-C not work? Does CTRL-ALT-DEL not work? I waited about 3 minutes. I did not try ^C and ^ALT-DEL does not work. Normally it zips right by and you don't notice it so 3 minutes was enough. > > 6. Nouns in many places where you use "it". For example, when you write, "I > have tried it on several machines successfully, but they don't use that > module" ... is "it" e1000.o, an unspecified version of Bering, or something > else? And if "it" does mean the module, in what sense is it "successful" in > these tries? Other examples are "It boots fine until it gets to > 'configuring network interfaces' then it hangs" and "I am currently running > Bering on the PC that doesn't boot, and it > works fine" (also, what does "works fine" mean?). I am booting from a floppy and loading the packages from USB. I have one uClibc 2.1.1 distro with all the modules and packages that I need. What I mean, is that the distro loads to the login prompt with the e1000 module on any machine that doesn't use the e1000.o module. On the PC that does use the modules it stops at the 'configuring network interfaces' line. Bering 1.2 is running on this machine that "hangs" with uClibc, so I believe the hardware is good. > 7. What "I renamed the module and it booted" means. What did you change the > name from, and to? What I mean is that I commented out the /etc/modules e1000 line. It made no difference. I then renamed the e1000 module at /lib/modules to e1000.o.old. Once I did this the PC in question booted to the login prompt. >Is the "it" that booted the Bering kernel (with or > without an interface for the NIC in question), or do you mean that the > renamed e1000 module in this instance successfully created an eth0 (or > whatever) interface? (Normal rules of English diction say that "it" refers > to a module here ... but modules don't "boot", kernels do. So I'm unclear > what you mean by "boot" if it applies to the module, not the kernel.) Either the kernel or the PC. I got to the login prompt which is what I consider "booted". I did not check whether an ethernet adapter was created but I suspect that it wasn't. > You *probably have a simple problem, easy to correct. But without a clear > description, I ... and others, probably ... will find it difficult to help > you spot it. I am hoping it is a simple problem. It is all that is keeping me from upgrading to uClibc, but more importantly openvpn. Many thanks, > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
