Void's Forums

by **Copperhead** » Tue Jun 17, 2003 6:42 am

I tried to get both of these guys running tonight, but I hit errors, both having to do with the same module (defxx.o).

Here are my error messages:

make[2]: *** [drivers/net/defxx.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2

Does anyone know what this defxx.o module is, and how I can go about taking it out? I have never really tried to fool around with BETA kernels before, but I am trying to do a little warm up before 2.6 comes out.

Thanks

by **Void Main** » Tue Jun 17, 2003 7:06 am

In "make xconfig" it's under "Networking support"->"FDDI driver support"=>"Digital DEFEA and DEFPA". If you don't have FDDI then turn off everything under FDDI and FDDI itself.

Here's my .config file if you want to use it as a base:
http://voidmain.is-a-geek.net/files/con ... .6x.config

by **Copperhead** » Tue Jun 17, 2003 7:08 am

Thank you!

The main problem with these things is that I don't know what half of them do.

I'll give that a try right now.

by **Void Main** » Tue Jun 17, 2003 7:12 am

Also, it might be faster to use my config as a base. I added a link to it in my previous message. It's set up for an Athlon processor so if you use something else you'll want to change that.

by **Copperhead** » Tue Jun 17, 2003 8:09 am

Thanks...

I had originally tried to compile it to meet my specs (AMD Athalon k-5 class) but it didn't like that for some reason or another. I switched it o 386, and no more problems, other than some SCSI stuff I had to mend out.

Speaking of which, I copied my old config file (that uses SCSI Emulation) to the 2.5.72 config file. I didn't see SCSI-Emulation support in xconfig. Will I still have this feature enabled?

by **Void Main** » Tue Jun 17, 2003 1:22 pm

I assume you mean BLK_DEV_IDESCSI (SCSI emulation support). In "make xconfig" it's under "ATA/ATAPI/MFM/RLL device support"->"SCSI emulation support".

by **Copperhead** » Tue Jun 17, 2003 11:45 pm

I got 2.5.72 to compile with no errors. I took out all of the stuff that make gave me an error or, and rebuilt the bzImage and the modules. Now, when I select the 2.5.72 kernel to boot from LILO, it gets up to the "loading linux.bin....decompressing kernel image......" and just freezes right there. It won't even boot up.

What could be causing this? I compiled this kernel the sme way I did for 2.4.21, using the same config file.

by **Void Main** » Wed Jun 18, 2003 7:18 am

Hmmm. I believe I have had that happen to me when compiling for my Athlon but I don't recall having a problem when compiling for my K6 or my P100. I don't remember what steps I took to get it working on my Athlon, if I did at all (I'm running 2.4.20 on it right now). You might search the LKML (Linux Kernel Mailing List) archives for some hints. If I get a chance I'll see what I can come up with.

by **Copperhead** » Wed Jun 25, 2003 8:54 pm

I found this while reading up on Rock Linux's web site:

"An immediate halt after 'loading Linux kernel' indicates your kernel has been built for the wrong CPU."

I think I built it for 586, where I should have built it for 686.

Thanks for the help though. I'll see how it goes.

by **Void Main** » Wed Jun 25, 2003 8:57 pm

Don't count on it. A 686 CPU can run a kernel built for a 686 and below (586 is below 686).

by **Copperhead** » Thu Jun 26, 2003 2:59 am

Well, after eight days, I finally got it to run. :shock:

I am still having a few problems, one quite severe, and one that isn't so bad. When I run lsmod, I get this ouput:

Module Size Used by Not tainted
lsmod: QM_MODULES: Function not implemented

The other problem is that I no longer have sound, but I think I just forgot to compile the module for my soundcard (es1371.)

This thing was no joke. You have to choose what you are compiling wisely. I think that was what my problem was, and why I was getting so many compile errors on my first few attempts. This was a little more challenging, and copying my 2.4.21 config file wouldn't help me in the slightest. As for why it wasn't booting once I did get it compiled, I still have no idea. I chose 386 this time, just to be safe, and followed the advice from whoever wrote those nice little captions on qconfig.

One other thing...My little Tux guy is gone on the boot screen! This kernel had options so that you could have three of them, and not one came up.

by **Void Main** » Thu Jun 26, 2003 7:58 am

That's why I asked if you wanted to use my config as a base, it may have gotten you started a little faster. Did you upgrade your modutils? There is a README that comes with the kernel that tells you what version you need to be at for several packages. You really need to look at that and make sure you are upgraded to the appropriate levels. modutils is just one of several packages. On Red Hat I had to change a couple of things on my rc.sysinit script because module loading is a little different in 2.5.x. It's possible that your sound is not working merely because the module for your sound card did not get automatically loaded. You might try seeing if the module is there and load it manually.

by **Copperhead** » Thu Jun 26, 2003 4:04 pm

Thanks. I just forgot to compile the module for my sound card. It is in there now, and the kernel is recompiling as I type.

I initially did try out your config file, but I kept having the same problem. On boot, after compilation, it would only mount my / partition as read only, and forced me to manually run fsck. I don't know why..maybe I missed something, or just did something wrong because I am an idiot. None the less, no matter what I tried it kept making me run fsck, to which it gave me a message of "Bad Superblock..."

I am still wondering about the boot screen though. I miss Tux! Do you know of any way to get him up there instead of that boring old text screen? He was up there in 2.4.x, but now he is gone.

Thanks for all of your help.

Void's Forums

Errors compiling 2.5.68 and 2.5.72 kernel

Errors compiling 2.5.68 and 2.5.72 kernel

Who is online