LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 10-07-2003, 09:20 AM   #1
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Rep: Reputation: 30
Angry So I finished my kernel compile last night....


I get up this morning and try to reboot the computer with ACPI enabled, and I still get the same crap!!!!!! Even after recompiling the kernel with ACPI support, it still says "acipd: failed, cant find /proc/acpi/events" What good did it do me to compile the kernel if it still doesnt work?

EDIT: other people have gotten it to work on machines similiar to mine, so I dont understand what the problem is here

Last edited by Kramer; 10-07-2003 at 09:21 AM.
 
Old 10-07-2003, 09:39 AM   #2
itsjustme
Senior Member
 
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571

Rep: Reputation: 47
Uh... maybe you did something wrong.

Sorry, you give no details.
 
Old 10-07-2003, 09:47 AM   #3
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
I patched the kernel with the proper patch from the acpi website using kernel 2.4.21-013mdk. I cd to the linux drectory, did "make mrproper" then I did "make xconfig" which brought up the kernel configuration tool. I selected the ACPI options i wanted, as well as changed my processor to the proper thing, also disabled APIC as well as all of the APM stuff. Then i did "make dep" followed by "make clean" followed by "make bzImage". Then I did "make modules" which took on the order of about 6 hours. Once that was done I did "make modules_install" and then "make install". Did I miss something here, and how do I know I booted onto my new kernel instead of my old one? My ACPI still has yet to run Any other info you might need, let me know
 
Old 10-07-2003, 11:38 AM   #4
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
You're going to need to edit /etc/lilo.conf and run LILO (or do grub stuff for grub) to switch kernels. Add an entry that's a duplicate of your current but with the new kernel's name in place of the old.

And copy it to /boot.

Do 'uname -a' to find out what you're running.

Or maybe my head's up my ass. Maybe make install should have taken care of all that? It's been a long time since I compiled a new kernel and it was on Core. I just remember copying crap and editing crap by hand. Sorry - I posted too quick before my brain caught up.

Last edited by slakmagik; 10-07-2003 at 11:40 AM.
 
Old 10-07-2003, 11:52 AM   #5
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
I ran LILO from the terminal, and I guess that replaced it, but now since it has ACPI enabled, it wont boot. I dont get it
 
Old 10-07-2003, 12:24 PM   #6
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Hm. That sucks. I don't know anything about that part of it. You might need to install acpid, maybe edit a config script to start it, maybe edit /etc/acpi/events so that there'd be something in /proc/acpi/events. I don't really know. Try something along those lines? Good luck.
 
Old 10-07-2003, 12:46 PM   #7
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
I have acpid installed, but its like it points to the wrong directory. Any ideas on how to change it? You cant write to the /proc directory since its read only. It has to be started with that in there
 
Old 10-07-2003, 10:22 PM   #8
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
http://www.linuxquestions.org/questi...906#post523906
I decided to upgrade to the 2.4.22 kernel, only this is the trouble Im having. Can anyone help me with this?
 
Old 10-08-2003, 02:51 AM   #9
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Not sure about the acpi stuff but, on that link, you could open an xterm and do 'make menuconfig'. (I think that's it.) And then there's 'make config' which, I believe gives you a whomping big file to edit. I've only ever used the TUI in console but I'm actually looking forward to trying xconfig.
 
Old 10-08-2003, 04:14 AM   #10
ceedeedoos
Member
 
Registered: Aug 2003
Location: Antwerp, Belgium
Distribution: Slackware 10.0, Mandrake 10.1
Posts: 174

Rep: Reputation: 36
are you 100% positive that all you changed was the ACPI options?

Just asking because I remember recompiling with ACPI support built in, and finished up going through the entire kernel and removing some things I should have left in ... and yeah, nothing happened when I booted up :-)

if you did remove other options, try finding an older configuration file of a kernel that worked when you recompiled it, and only adapt the ACPI features. If it still doesn't boot then, I'm dazzled

if you didn't play with other options, I'm just as well dazzled I'd say to compile them in as modules, but that can't make a difference to wether it boots or not, I guess...
 
Old 10-08-2003, 07:36 AM   #11
geoff_f
Member
 
Registered: May 2003
Location: Canberra, Australia
Distribution: openSUSE 11.3
Posts: 445

Rep: Reputation: 31
After you finish compiling, there's a few more steps to go to make your computer boot from the new kernel. You have to copy the new kernel and the new System.map, to your /boot directory, then create a new 'initrd.img' file there. Then you re-configure /etc/lilo.conf and run 'lilo'.

To make the new 'initrd.img' file, type the commands:

cd /usr/src/linux
mkinitrd ./initrd-2.4.21-0.25mdkcustom.img 2.4.21-0.25mdkcustom

Don't miss the period after the 'mkinitrd' command. This command takes the form:

mkinitrd ./<kernel_version>.img <kernel_version>

The example above shows that you use whatever name you gave your new kernel; in my case it was '2.4.21-0.25mdkcustom'.

In /usr/src/linux you will find a file called 'System.map'. It's a good idea to make a copy of this as System.map-<kernel_version> in /usr/src/linux.

Rename 'vmlinuz', 'initrd.img' and 'System.map' in /boot to 'vmlinuz-old', 'initrd.img-old' and 'System.map-old'. Now copy the new versions of these files into /boot. These steps are completed by:

cp /boot/vmlinuz /boot/vmlinuz-old
cp /boot/intird.img /boot/intird.img-old
cp /boot/System.map /boot/System.map-old
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz
cp /usr/src/linux/initrd-<kernel_version>.img /boot/initrd.img
cp /usr/src/linux/System.map /boot/System.map

Make a copy of your /etc/lilo.conf as lilo.back, then change your lilo.conf to make it look like this:

#---------start of /etc/lilo.conf---------------

boot=/dev/hda
default="linux"
prompt
timeout=200
vga=788

image=/boot/vmlinuz
label="linux"
root=/dev/hda1
append="devfs=mount hdc=ide-scsi acpi=off quiet"
read-only

image=/boot/vmlinuz-old
label="linux-old"
root=/dev/hda1
append="devfs=mount hdc=ide-scsi acpi=off quiet"
read-only


image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda1
append="devfs=mount hdc=ide-scsi acpi=off"
read-only

image=/boot/vmlinuz
label="failsafe"
root=/dev/hda1
append="devfs=nomount hdc=ide-scsi acpi=off failsafe"
read-only

other=/dev/fd0
label="floppy"
unsafe

#----------------end of lilo.conf------------------

In this example, the section in bold has been added. You do this by copying the first 'image=' block of your lilo.conf and pasting it directly below, then changing the names in the first two lines to add the '-old' suffix. [I'll clarify this: the idea is not to make your lilo.conf look like the above example; rather, it is to take whatever yours is, and modify it by copying the first block, pasting it underneath with the '-old' names.]

When that is done, type:

lilo

You should now be able to re-boot your computer and be able to select between your new and old kernels.

Source:
http://www.tldp.org/HOWTO/Kernel-HOWTO/index.html
(especially steps 2(Quick Steps), 10(Kernel Files Information) and 15(Appendix A - Creating initrd.img file))
 
Old 10-08-2003, 07:37 AM   #12
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
I changed all of the ACPI options from "m" to "y", all of the ones I needed at least. It boots now, but ACPI still fails to start, giving the same error message as before "starting acpid: failed, cant open proc/acpi/events"
 
Old 10-08-2003, 07:57 AM   #13
cswbww
LQ Newbie
 
Registered: Oct 2003
Location: Hong Kong,PRC
Distribution: desktop->slackware 9.1; laptop->gentoo 1.4
Posts: 6

Rep: Reputation: 0
what is your chipset version?Sometimes there are special requirement for kernel compiling. As for my experience,nvidia-nforce2,I should disable the 'acpi' in the chipset bios option before I compile the new kernel.
 
Old 10-08-2003, 08:16 AM   #14
Kramer
Member
 
Registered: Aug 2003
Location: Somewhere south of sanity...
Distribution: Mandrake 9.1
Posts: 550

Original Poster
Rep: Reputation: 30
As far as chipset, Id have to look when I got home (fall break :-D). By chipset you mean motherboard, right? Anything else you want to know, I can probably tell you. Im just somewhat stumped as to why it still doesnt work. I think geoff_f may have found part of the problem, in that Im still booting onto the old kernel. Im going to try what he suggested later on this afternoon.
 
Old 03-28-2004, 08:26 PM   #15
hooya27
Member
 
Registered: Aug 2003
Location: In a van down by the river
Distribution: Mandrake
Posts: 48

Rep: Reputation: 15
Um, just a guess here, but "acpi=off' on as kernel options in lilo.conf may need to be
'acpi=on'...

Just a stab in the dark
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
upgraded kernel, won't let me compile kernel once Suspend2 patches are applied microsoft/linux Linux - Laptop and Netbook 3 10-02-2005 02:37 PM
Kernel Problems. Howto Compile a new kernel from 4.2 with backwards compatibility ? ShoCkwave Linux - General 2 06-19-2004 06:02 AM
2.6.1 kernel upgrade finished ... nvidia next, what to svarreby Slackware 4 01-19-2004 07:21 PM
Kernel 2.4.23 compile causes kernel panics on ATA RAID-1 (mirror) array Raptor Ramjet Slackware 3 12-18-2003 01:40 PM
Just finished up a kernel compile... Kramer Linux - General 19 11-07-2003 09:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:50 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration