ZenwalkThis forum is for the discussion of Zenwalk Linux.
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.
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.
have 2 hp pavilions (6736 & 6835) that don't fully shutdown. they shut down to the point off turning off the power and then just sets. i have to push the button on the tower to turn it off. feels like i back in windows 95 days!
i know i've seen a thread somewhere around, not sure if it's here on on the zenwalk community forums, but i can't find it again.
also, both of these computers get a video mode error on startup saying something along the lines of i have entered a bad paramater(?) i then get the option of seeing available video modes, which i don't have a clue as to what to enter, or wait 30 seconds. if i just hit the spacebar, they boot fine.
The error you are seeing in based on a lilo parameter that defines a console resolution at startup. Don't worry, it is nothing to worry about. I'm not sure how to stop it,though.
what's so tough about replying to whichever one you think you know how to fix? you simply type in something like "this is what you do to fix shutdown issue............ or, this is what video mode you need and this is how to edit whatever, etc..........
the video problem will probably be the harder to fix over these forums as i have the issue on 3 machines actually, and all 3 have different model monitors, which i'm sure probably has something to do with it and i at least need to know their specs most likely.
the shutdown issue is the on i'd really like to fix.
Last edited by missmoondog; 10-11-2006 at 08:18 PM.
...also, both of these computers get a video mode error on startup saying something along the lines of i have entered a bad paramater(?) i then get the option of seeing available video modes, which i don't have a clue as to what to enter, or wait 30 seconds. if i just hit the spacebar, they boot fine.
"You passed an undefined mode number" No, I don't know what it means either! As root you need to edit /etc/lilo.conf. Look for the section shown below. In my case the default setting was vga=normal but I had to comment that out and uncomment vga=791. But I had to try a few options before I got one that worked.
Make sure you run lilo -v after you make any changes to lilo.conf.
Code:
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
[QUOTE=missmoondog]have 2 hp pavilions (6736 & 6835) that don't fully shutdown. they shut down to the point off turning off the power and then just sets. i have to push the button on the tower to turn it off.
If your computers will not power down, that means either the acpi daemon is not running, or your motherboards are not ACPI-compliant.
Hsve you already checked you haven't disabled the daemon from running?
I have an Asus P2B-DS mobo, the early versions of which had a bug preventing proper ACPI compliance. Because of this, they are on a 'black list' of mainboards which the kernel will not normally allow ACPI for.
The problem is that I have one of the last versions, which were fixed.
So everytime I install any version of Linux, I have to add the parameter 'acpi=force' as described in the thread.
If they shut down in Windows, then maybe you need to investigate the APM options.
where EXACTLY do the punctuation marks go and what type are they. i'm finding some posts have it like this: addappend = "acpi=force" and this addappend = "acpi=force " and this addappend = 'acpi=force' and this addappend = acpi=force' and this addappend = 'acpi=force'
would somebody make up my mind and type the crap the CORRECT way, please?!!
thanks
edit:
nevermind. got the answer on another forum. no marks go around the acpi=force
yay! it worked, wit the correct punctuation!
Last edited by missmoondog; 10-20-2006 at 04:23 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.