Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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.
Ok so i have a Toshiba with gusty gibbon and there is a sound bug that does not allow me to hear anything unless i boot acpi=off. So there has been no progress at all on this bug so basically i came to ask one simple question that i could not find a good answer to here or google. Is booting acpi=off bad news or is it ok? This is my laptop, its plugged in 99% of the time. I would be nice to see my battery state, is there any way to see this with acpi=off?? thanks in advance!
Booting with that option turns off ACPI in the kernel, which means you lose all the power management functions that depend on it (as you have noticed, battery level is one of them). You might be able to use it's predecessor APM, though.
well, it won't break the system that is for sure.
but you will lose ACPI functions, like auto-turn of when you do halt.
basically, you have to press the button to turn it off, and more things like that.
it's not a problem, more of an annoyance.
maybe you can try to view the battery state in "kdesysgaurd", but i doubt it will work with ACPI off...
like ms3fgx say's, you can try turning on APM.
maybe you should get a system that fully supports linux? or simply the official standards should do (the fact that there is a problem with your sound <=> acpi either means that:
the hardware suplyer does not create (decent) drivers
-or-
the machine is not fully compliant with standards
nothing to do with ubuntu, it's not their fault others don't know how to make hardware (or others buying faulty hardware...)
not to be mean but you just stated the most obvious things. of course i know that. and there is no way im going to go by a whole new system....i know its possible to fix this it just might take some time and there is no way im taking the easy way (buying a new system).
and just to clear this up it IS a bug in ubuntu acpi modules. the developers and sounds team HAVE TOLD US ITS A BUG. my computer should be FULLY supported but its not because of the BUG. The two reasons it does not work is 1)the bug and 2) they did not entirely fix the problems the promised to whit acpi/sounds that was in feisty. sorry but i have been having many people tell me its not ubuntus fault when it is.
yews but if i do that my linuxant modem driver wont work so i need to keep 2.6.22.14. i would have no problem but i bought the driver and dont want to waste the money.
It seems, from the bug report, that sounds works fine with feisty and edgy. Why don't you downgrade?
I think it's safe to wait a bit before installing the "brand new version" of ubuntu, "brand new" does not necessarily mean "better".
That is what i though about doing but i cant find a download. also my main problem is that i would like to keep 2.6.22.14 so i dont have to buy another linuxant driver. i wish i would have just installed feisty in the first place.
so there is a fix on the bug site now that is working for everyone but me. and im sure it would work for me but when i installed the packages my modem stopped working. when i ran hsfconfig it told me that the driver did not support custom drivers and i will need to obtain (buy) the generic debian driver. any ideas? other than buying the driver of course.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.