|
laptop battery manager help PLEASE!!!!
i am new to linux and recently installed suse 9 on a dell inspiron 5100. everything seems to be going smoothly except i dont know how to make the battery manager work. when i go into Klaptop it gives me this message:
Your computer seems to have a partial ACPI installation. ACPI was probably enabled, but some of the sub-options were not - you need to enable at least 'AC Adaptor' and 'Control Method Battery' and then rebuild your kernel. PLEASE help me somebody. i know this is posted all over but i am new and am having a very time hard figuring out what i am supposed to do thanks |
You need to recompile your kernel with complete acpi support.
|
Being that you are new to linux , this should be kinda of hard to explain.
You are going to have to rebuild your kernel , depending on what kernel you use it will vary how to set it up. I have a Dell Inspiron 2650 with linux kernel 2.4.22 and 2.6.1 i prefer 2.6.1 . You are going to have to get back to me on the kernel that you want to setup because i cant walk you through it. I would choose 2.6.1 . After the kernel is running nice and smooth , depending on your video card , I'm pretty sure it was a NVIDIA card you will have to recompile your driver for it , and the best part is if you have kernel 2.6.1 running you have to get a patch for the driver. And also a good utility to have is a program called GKrellm, it is a program to give you the specs of your running system including a battery monitor and temperature and fan gauge. But with GKrellm , you are also going to have to install a new I8k module , its specifically for dell laptops . But before i get a head of myself , get back to me bout what kernel you wanna run because both kernels have to have some different "tweeks" done to them in order for them to run perfectly. |
i guess kernel version 2.4.22 is fine becaues that is what the instructions i was given by someone say:
(00) Login as 'root', because you will need root priveleges for all this... (01) Back up any data that is valuable, if possible. (02) Create a directory for storing all the downloads - in console type: mkdir /downloads ***Keep the console open you will need it for steps (05) and onwards *** (03) Click on this link to download linux-2.4.22.tar.bz2 (this is the kernel that worked for me, but if you want to try the latest kernel you can click here to get linux-2.6.1.tar.bz2) (04) Click on this link to download acpid-1.0.2-fr1.i386.rpm (05) cd /usr/src/ (06) tar xjvf /downloads/linux-2.4.22.tar.bz2 (07) ln -s /usr/src/linux-2.4.22 /usr/src/linux (08) cd linux/ (09) make xconfig (10) One of the choices that you have in the menu that comes up is called 'General' or something like that... this opens up another menu, where you should find and enable the following (this is a looooong section you better have some coffee ): Power Management support (y) ACPI Support (y) AC Adapter (y) Battery (y) Button (y) Fan (y) Processor (y) Thermal Zone (y) Relaxed AML Checking (y) Another choice in the main menu has something to do with CPU - you must go there and make sure that you choose the correct CPU type or else your new kernel will compile for a CPU other than what you got. Also go to the menu that (I think) is called File Systems and make sure that reiserfs and ext3 are enabled as modules (choose 'm' rather than 'y') and that ext2 is enabled with a 'y' (it should be by default, but what the hell ). Also in the menu called Block Devices make sure that you have initrd and ramdisk enabled as 'y'. Otherwise you will keep on getting 'Kernel panic' when you boot (if you do get kernel panic after all you might want to look at this, which is about two weeks-worth of me struggling to overcome this issue) I think this is all... After that save and exit. Now you are back to working in the console... (11) make dep && make clean && make modules && make modules_install ***This is likely to take a good ten minutes or so *** (12) Now you need to backup your old kernel: mv /boot/vmlinuz /boot/vmlinuz.old (13) The same goes for the old initrd: mv /boot/initrd /boot/initrd.old (14) cp arch/i386/boot/bzImage /boot/vmlinuz (15) cp System.map /boot/System.map-2.4.22 (16) mkinitrd (17) In /boot/grub/ you should have a file called menu.lst - open it in a simple text editor like Kate or KWrite. It should look something like this: CODE # Modified by YaST2. Last modification on Sat Jan 10 14:58:12 2004 color black/red black/light-gray default 0 gfxmenu (hd0,1)/boot/message timeout 8 title linux kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x317 hdc=ide-scsi hdclun=0 splash=native showopts initrd (hd0,1)/boot/initrd title floppy root (fd0) chainloader +1 title failsafe kernel (hd0,1)/boot/vmlinuz.shipped root=/dev/hda2 showopts ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3 initrd (hd0,1)/boot/initrd.shipped The way it is at the moment it will load your new kernel and initrd at boot, because they are now called vmlinuz and initrd, whereas your original kernel and initrd are now called kernel.old and initrd.old - but if the new kernel that you compiled does not work for some reason you will be busted. So... you need to add a new entry to this file so that when you boot the GRUB loader allows you to choose whether to boot your new or your old kernel (the best way is to copy and paste the entry for the kernel that is already in menu.lst and just add -old to 'title linux' and .old to '/boot/vmlinuz' and '/boot/initrd' ): title linux-old kernel (hd0,1)/boot/vmlinuz.old root=/dev/hda2 (or hda1, hda3, hda4 etc.. must be the same as in the original entry for root=/dev/...) vga=0x317 hdc=ide-scsi hdclun=0 splash=native showopts initrd (hd0,1)/boot/initrd.old That way you should always be able to load your old kernel if the new one does not work (which it likely won't first time round )!! Now save menu.lst (18) Use you file browser to go to /downloads and click on the acpid-1.0.2-fr1.i386.rpm to install it with YaST2. (19) Reboot (20) Select the new kernel when GRUB comes up... (21) Hope... hope... hope... If the kernel does load up you should see the battery meter and all the other nice bits and bobs that come with ACPI in your system tray. If the kernel doesn't work you should still be able to boot with your old kernel and try again . i have several problems with these instructinos and this is the reply i posted after reinstalling Suse 9 twice: except, im not sure but in several instances the script told me that the specified directory doesnt exist (07) ln -s /usr/src/linux-2.4.22 /usr/src/linux (08) cd linux/ I'm not sure if step seven did anythign either of teh two times i tried to do this. and cd linux doesnt exist, did you mean cd linux-2.4.22?? Also, (12) Now you need to backup your old kernel: mv /boot/vmlinuz /boot/vmlinuz.old (13) The same goes for the old initrd: mv /boot/initrd /boot/initrd.old these two commands dont add another vmlinuz and initrd to the boot directory they take a file away and when i booted up i only was given linux-old as an option (14) cp arch/i386/boot/bzImage /boot/vmlinuz (15) cp System.map /boot/System.map-2.4.22 I looked everywhere but coudlnt find a system.map directory or a bzImage directory. are those right? and lastly my menu.lst file had all the things you said except hdo,2 and hdo,3 not hdo,1. was i supposed to add hdo,1 to the file? or was i supposed to change 2 or three to 1? |
Quote:
http://www.sh.nu/download/nvidia/ |
im getting so much conflicting information. what ami supposed to do seriously? i currently have kernel 2.4.21.99, and i havent done anythign yet im just posting information i have recieved. from my point of view 2.6 sounds better just because the numbers are higher. i honestly have no idea where to start or what to do. ill go with 2.6 i suppose, i woudl love to start an email correspondence on this problem with you darkseed if you woudlnt mind, as you have a dell. i am so frustrated
thank you josh |
I'm running Mepis on an Inspiron 8500. I've run RH 9, Fedora Core, Slackware 9.1, Suse 9.0, and currently MEPIS Linux. Of all of these distros Suse was the worst as far as hardware support but a kernel compile will solve some of your problems. I wouldn't recommend compiling a 2.6 kernel if it's your first kernel recompile. Go with 2.4.24. Just download the sources from www.kernel.org and make sure you choose full source (f). There are already several kernel how-to's on this forum (look in the red hat distro section it works for Suse as well with a few small exceptions--don't use make install for one and Suse uses Lilo as a bootloader I believe). If I were you though I would ditch Suse for Fedora or MEPIS. I'm sure some Suse fans will disagree but... I personally found Fedora much easier to deal with and MEPIS is the best right now IMHO besides the lack of Speedstep support. Both of these distros ACPI patches have worked without a hitch for me and Fedora has Speedstep support as well. You can patch the kernel in MEPIS for this... I can tell you how if you want. I can also help you recompile your kernel in Suse as well.
|
| All times are GMT -5. The time now is 01:06 PM. |