Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
11-19-2002, 09:57 AM
|
#1
|
LQ Newbie
Registered: Apr 2002
Posts: 29
Rep:
|
Confused about kernel compilation options
I am now in the midst of compiling a new kernel
that supports apci and also to disable the
apm option
In make menuconfig, it was shown that the
"Advanced Power Management Bios Support" option
with an asterisk and ACPI without an asterisk
which is correct.
BUT in make xconfig, in the "Advanced Power Management Bios Support" option it was shown as a "n" ?! Shouldn't it be
a "y" ? And I could not enable the ACPI support option
here unlike in menuconfig ....
I am pretty sure I am missing something here,
could some one enlighten me ?
I am running Red Hat 8 by the way with kernel version
2.4.18-14.
Thanks in advance !
|
|
|
11-19-2002, 05:47 PM
|
#2
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
I have never used menuconfig, I would guess if there's a * next to something there, it is enabled. make xconfig is much more well defined I think.. is there a particular reason you want to use menuconfig ?
When in doubt, I'd open up the .config file and see if the option I'm concerned about has a 'y'/'n' next to it.
|
|
|
11-21-2002, 08:57 PM
|
#3
|
LQ Newbie
Registered: Apr 2002
Posts: 29
Original Poster
Rep:
|
From the hint given by nxny, I found that .config file holds the
kernel settings values. I did more research and now can
enable the ACPI in make xconfig by copying the config file
from /usr/src/linux-2.4/configs.
These are the steps I have done:
1) Copy the kernel-2.4.18-athlon.config from /usr/src/linux-2.4/configs
to /usr/src/linux-2.4/.config
2) Edit the Makefile and change the line that has EXTRAVERSION = -14custom to EXTRAVERSIOn = -14acpi
3) make oldconfig
4) make xconfig
5) Enable the ACPI options. Disable the APM options
5) Save and exit
6) make dep clean
7) make bzImage modules
At stage 7 it stops, I am not sure whether it is at bzImage stage
or modules stage. But the last two lines were
make[1]: Leaving directory `/usr/src/linux-2.4.18-14/driver`
make: ***[_mod_drivers} Error 2
I am attempting to compile this kernel with ACPI support for my
Compaq Presario 725 notebook by the way ....
I am not sure if the steps are correct, any one can comment on
the above steps ? Any advice given will be appreciated ! Thanks in advance.
|
|
|
11-21-2002, 10:34 PM
|
#4
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
What I do is use the RH config file as a base .config and then make xconfig to enable some disable some.
We'd need more than just the last 2 lines to see where the error occured. You need to go back to the point where make says.. oh I couldnt execute this step. From that point on, that error usually is carried through until make gets miffed and stops.
|
|
|
All times are GMT -5. The time now is 08:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|