DaveG

Well, I get the lovely broken 0% stuck-on-screen volume OSD with kmilo and klaptop, so I had to set things up myself. Here's what I did to get these 3 keys working on my Inspiron 5100: 1) Use xev to find the keycodes. Run the command, mouseover the box, and press the keys. 2) Make those keys known with xmodmap. Here's my $HOME/.Xmodmap file, though your codes may differ: ! Volume Up keycode 176=F20 ! Volume Down keycode 174=F21 ! Volume Mute keycode 160=F22 3) Add a little $HOME/.kde/Autostart script to set the keys. Make sure to mark it executable. Run it to ready the keys; KDE will then run it on start from now on. #! /bin/sh if [ -f $HOME/.Xmodmap ]; then /usr/bin/xmodmap $HOME/.Xmodmap fi 4) Go into KMix -> Settings -> Global Shortcuts and set your keys there. Voila. Working volume fn-keys made from scratch. :) Idealy, all this would work by default... but that ain't happening at this rate.

I've got this fixed and working via help from the official forum, so I'm posting the result here solely for the reference of anyone else reading this. http://www.jlab.org/~moffit/computer/inspiron5100.html Upon adding the very obscure widget acpi_irq_balance to my kernel line in grub's config, things just magically work now.

No one even seems to be reading this thread... Someone, anyone, please, please, throw me a bone here. Here's my progress on this idiocy thus far: I'm not exaggerating things here. NO acpi events are firing. I can press the power button, shut the lid, etc, and still get no events: [root@localhost dave]# cat /var/log/acpid Laptop mode enabled, not active. Laptop mode enabled, not active [unchanged] Laptop mode enabled, not active [unchanged] Laptop mode enabled, not active [unchanged] Laptop mode enabled, not active [unchanged] I've found that adding "acpi=ht" to my kernel line in GRUB's menu.lst adds some funcionality. The power button now does an immediate power kill, which is actually worse than before. It's supposed to shutdown, not die outright. If I need a forced power off, holding the button has always worked fine. I'll stick to "log out", "turn off computer". It has always worked fine. (and yes, it turns it off by itself after shutting down) Only other changes are the removal of "Suspend to RAM" from KPowersave's menu (not that it works, anyway) and it now turns the screen off on lid close. Attempting other things like "acpi=on", "nolapic", and "noapic" do nothing. I've found this page, saying that the events aren't detected for this model, though it's quite an old page, and I don't really know what it's about. I know the lid button works on this machine; I've been shutting the lid to hibernate in Windows for years. This is an extremely basic function, and I'm getting quite annoyed that I can't get this to work. Can someone please at least try to help?

Ok, after a month of hunting, I finally got hibernation to work. (see here) However, I still get nothing when I press my power button or close the lid. KPowersave has them set to power off and hibernate, but it doesn't do anything. I've tried editing the various /etc/acpi/actions files with no results. Near as I can tell, the events aren't even firing. Drakxservices says both acpi and acpid are running and set to load on boot. I just want to be able to close the lid and have it lock and hibernate. How do I get it to actually detect the lid close?

I've finally fixed it! I got around to futzing with this again today, and I've finally found the solution. Basically, the "resume device" parameter in /etc/suspend.conf is crap; it must be specified in /boot/grub/menu.lst instead. only enabled options /etc/susped.conf: compress = y splash = y relevant entry in /boot/grub/menu.lst: title Mandriva Linux kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=Mandriva_Linux root=/dev/hdc5 splash=silent vga=791 resume=/dev/hdc6 initrd (hd0,4)/boot/initrd.img (where vmlinuz and initrd.img are symlinks to the files for my kernel, 2.6.22.12-laptop-1mdv in this case, and my swap partition is hdc6) After booting into the above GRUB entry, I can then hibernate via KPowersave's "suspend to disk" without any issues. My swap partition is not damaged with this setup. I do notice some graphical glitches on resume, just before the password prompt, however they don't seem to be of any consequence. Also note that specifying "compress = y" in /etc/suspend.conf is a definite must, as it noticeably speeds up the resume time. Oh, and "suspend to RAM" still doesn't work, but I don't use it so I don't care.

Thank you. Ok then, why does having that set correctly hose my swap partition?...

Someone might call this a feature, but I call it a bug, as I have it clearly set to "click to focus" in the control center. When I scroll (using my touchpad) whatever window is currently under the cursor gets focus and the effect of the scroll. Oddly enough, while the window gets focus, it doesn't get raised. I want this to be disabled. Any clue where this is set? [moved from Software by spinynorman] Edit by DaveG: Moved to "Art and Design" sub-forum it seems... really? This counts as art and/or design?

[dave@localhost ~]$ lshal | grep system.hardware system.hardware.primary_video.product = 19543 (0x4c57) (int) system.hardware.primary_video.vendor = 4098 (0x1002) (int) system.hardware.product = 'Inspiron 5100' (string) system.hardware.serial = '14GQ831' (string) system.hardware.uuid = '44454C4C-3400-1047-8051-B1C04F383331' (string) system.hardware.vendor = 'Dell Computer Corporation' (string) My graphics card is an ATI Radeon Mobility 7500 with 16 MB of VRAM. I have 512 MB of RAM in this thing; 1024 MB on a good day, if it feels like detecting the other stick... I've been trying out the Sleep Quirk Debugger with no luck. Via pm-suspend or KPowersave's menu, I get the same result; stall on resume. (which, as I said, may be an ATI/fglrx issue, and I don't really care if this works, though it should) I've noticed that my 20-video-quirk-pm-dell.fdi file was missing my model, so I updated it and rebooted, but when I "lshal | grep quirk" I get nothing. I don't think it's using the fdi files... On the more pessimistic side of things, linux-laptop.net has a bunch of install reports saying that no one has gotten suspend/hibernate to work on this thing. On a side-note, KPowersave seems to work quite well, and says it's throttling the CPU speed just fine. Though, I'm usually plugged in, so battery life isn't really an issue, but heat very much is, and anything that can lower its strain is a good thing for me. Also, monitor brightness works fine natively via the fn-keys, with no need for configuration. That at least seems to be directly handled by my BIOS. Now, I'm already getting more to go on here, which is great, but I still don't have a concrete answer on what my suspend.conf settings should be. Should my "resume device" really be set to my swap partition? I need to know if the error is in the settings or in how the settings are used. PS Thanks for moving this to the appropriate forum.

Ok, I initially asked for help on Mandriva's official forum, but I've been waiting for some sort of help for three and a half weeks now, so I thought I might as well try here. Link to other thread Here's the gist: Mandriva 2008 One install on a Dell Inspiron 5100 Laptop. (multi-boot with Linux, Windows, and Dell diagnostics all listed in GRUB) Currently using kernel 2.6.22.12-laptop-1mdv with the virtualbox and fglrx modules. KPowersave is installed and seems to function, however the power button, suspend button (fn+F1), and lid close sensor all don't work. (I've hacked the volume fn keys into working with Xmodmap) KLaptop does not work. Installing it causes the volume to try to fade to 0, and forces the OSD onscreen at all times. "Suspend to RAM" does not work. It stalls trying to resume. (may be an fglrx issue; don't really care about this one working or not) "Suspend to disk" does not work. It seems to suspend ok, skips GRUB on boot, but does not resume. I always get the following in the boot log: No resume device specified Trying userspace resume from suspend.conf file No resume device in suspend.conf Via a websearch and /usr/share/doc/suspend/HOWTO I'm told that in /etc/suspend.conf "resume device" should be set to my swap partition. (/dev/hdc6 in my case) This destroys my swap partition, and requires me to reformat it to get it working again. Boot-up and shut-down times are not that bad, but I would just like to be able to hibernate this thing like a sane person again... I'm trying to get a straight answer: What are my /etc/suspend.conf settings supposed to be? If you had to jump through hoops to get this working, what hoops were they? If your install has working "suspend to disk", what are the contents of your /etc/suspend.conf file? If "resume device" is in fact supposed to be the swap, then what the hell is going on here? If any of this is somewhere out there and I just don't know where to find it, please post a link. [moved from Software by spinynorman - welcome aboard :)]