login
Search
Hello I have for days, weeks even been trying to find a reasonable answer to this question:
Why is it I can change the information in the make menuconfig and get the following errors?
Kernel/Intermodule:179 Warning 'Inter_Module_Register' is Depreciated (declared at) Kernel/Intermodule.c38
Kernel/Intermodule:180 Warning 'Inter_Module_UnRegister' is Depreciated (declared at) Kernel/Intermodule.c79
Kernel/Intermodule:183 Warning 'Inter_Module_Put' is Depreciated (declared at) Kernel/Intermodule.c160
This is a consistant error and I have reformatted my system, reinstalled my Linux and Desktop systems and sucessfully upgraded the packages installed.
Slackware 10.1 -current
KDE 3.4.0
AMD K6-2 500
The following is relavent
At the Linuxquestions.org site, I have asked:
1: If I have an AMD k6-2 should I leave the Processor family at Intel Pentium 4?
2: If I don't have IEEE1394, should I leave it enabled, even though I don't have it?
2A: If I have ACPI disabled in my BIOS should I enable it in the kernel?
3: I have no SCSI Devices installed, Meaning AHA2940 or something like that. Should I leave hardware on?
4: If I have my Ethernet setup, it's under the tulip drivers, should Ijust leave that off, and go withthe realtek?
Yes I have modified all these and more, I have posted the information on the Linuxquestiosn.org site but keep getting you've compiled it wrong, my question is, If I did then your instructions are wrong because I followed those to get these errors. I have sucessfully installed PHP 5 and Apachee Server 2.x and they work fine. Even updated the alsa drivers and had no problems. I know what my system is, and how it works, so why do I want to leave it defaults if none of the defaults are my system?
From Linux 2.6.0 to Linux 2.6.11.7 I have consistantly encounterd these errors. The affect something, because when I do get to boot, something is not working. NIC, Sound somehting and I have asked and asked and to date has not rcvd a good answer, meaning that when I do a new compile, it actually works without flaw.
go to www.dfi.com, look for a K6BV3+ Rev A+ Docs and download the PDF and read what I have. Yes I know what I am doing and yes I have a serious problem, no one seems to know what these errors are, and just sluff them off because they don't know either. I need to know, someone that knows, please answer, I want to be able to use the new Linux 2.6.11.7.
I have attached my mainboard docs
Merely warnings
Hi,
The messages you show in your post are only compile-time warnings. They shouldn't prevent you from building your kernel. in fact, in almost all code I've compiled so far, these kinds of warnings tend to pop off. It only means that some code you're compiling makes use of a deprecated form.
Not supposed to be Errors
I am sorry if I come off as "Confrontational" but. If they don't harm the system, why is it then, after getting it working, it seems to not work?? Going to go with the "No Module" scenario and see.
A few tips...
OK, first things first. Those warnings you posted are just that; warnings. They aren't show stoppers, and aren't responsible for the problems you've been having with drivers. Every kernel release has warnings and errors. I checked back in the forums and found this thread:-
http://kerneltrap.org/node/1684
A guy called John Cherry wrote a script to compile a kernel release with varying configs. It records the number of warnings and errors. The results for the 2.6 kernel are on his site (along with the script used to generate them):-
http://developer.osdl.org/cherry/compile/
No, you should set it to "K6/K6-II/K6-III". According to the menuconfig help text:-
You could do but I can't see any reason to. AFAIK there isn't any other option that relies on it. It just adds to your compile times.
As a general rule I would say if you don't have it, or don't use it, don't enable it in the kernel. With something like ACPI, you can play it safe by enabling it in the kernel at compile time, but disable it at run time with a boot parameter ("pci=noacpi" for example). That way you won't have to recompile the kernel to add / remove ACPI.
I'm not 100% certain what you meant there. While you may not have any real SCSI hardware, some other kernel options require the SCSI stack in order to function. In my case, I have no SCSI hardware but I do have a USB pen drive. This needs the SCSI stack for its hotplug functions I believe. The answer you're probably looking for is to disable it in the kernel. If you find that breaks something else, just recompile with it in.
Drivers are not interchangeable. You can't use Tulip drivers on a RealTek card or vice versa.
I had a quick look at your motherboard manual:-
http://www.dfi.com.tw/Upload/Manual/39210928.PDF
I didn't see any onboard Ethernet so I presume you're using a PCI card or similar. Try looking at the chips on the card for any signs of a chipset code. If you can't tell which chipset it uses, try using "lspci". It displays a list of devices on the PCI bus and could give you some clues.
Alternatively, just build all the Ethernet drivers and turn on automatic module loading:-
Loadable module support ---> Automatic kernel module loading
I think that should do the trick. Once you've performed a successful boot and tested the network connection, "lsmod" will show you which modules were loaded. If you write these down somewhere for future reference, you'll know which drivers to use.
When I started out building my own kernels, I spent a lot of time and many unsuccessful boots trying to work out which bit to enable and which I could leave out. Something that might save time with endless recompiles is to use a live CD such as Knoppix or Ubuntu. I've heard both have excellent hardware detection.
Knoppix - http://www.knopper.net/knoppix/index-en.html
Ubuntu - http://www.ubuntulinux.org/
You can play about with boot parameters and see which modules they detect are needed for your hardware.
HTH.
Compile Errors
In searching, I have discovered...intermodule.c is the culprit. In it, it states "Depreciated" To me, this explains, do not use Modules. So as I understand this. Make menuconfig, and set everything you need, only do not set as a module. Yes? No?
In your lspci comment, it shows a NetworkEverywhere. Kind of confusing to me as the Tulip drivers ask for something else. Now in my serarching I found I need to use ALL the Networking information and the Tulip drive DECChip Tulip dc21x4x for it, as this seems to have worked with no errors. Then enable all of the IP UPv4 IPv6 and Fileters, all of it, and it seems to work. Test build yesterday to see, revealed this.
Going to make an attempt at a "No Module" Version of this and see. Thank you for your tips.
Posted a BUG for this as it has been prevolent from Linux 2.6.11.5 to Linux 2.6.11.7 and All tests have been the same. Each time system is setup the exact same way. http://bugzilla.kernel.org/show_bug.cgi?id=4504 is the bug filed
update fixes:
Well there is a few things that I have discoverd that no one has mentioned.
One: Loopback, seems that no one even thought to say anything about it. Come to find out, if this is not enabled, then I get errors. This is directly related to the Ram Disk so this is one of the things that needs to be addressed.
Two: I2O - Directly linked to alsa and how it handles the I/O resources. If this is not enabled, one of two things take place, sound is either garbled, as in my case, or does not work at all in many other cases.
Graphics/Character Settings - Beware here you can end up with a CGA Display on your console and the only way to fix it is revert to your previous kernel and recompile the new one or the drastic one, format and start all over with a fresh install of everything. Setting the old Kernel is best and easy.
As soon as I get all the details worked out, I will be setting up a "Lunix 2.6.11.X Configuration Guide" for the disenhartened who waant to update to the latest Kernel. More later.
Old Board
That board I had died, now I am trying to find support for the new one, PC Chips M825G Rev 9.2a with VIA KM 266Pro / 8235, for some reason the newer kernels do not support this brand new setup. pcchips.com/tw for the mainboard PDF files.