[opensuse-factory] Kernel boot parameters by default, feature 312962
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues. pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Nov 09, 2011 at 08:13:23PM -0800, Roger Luedecke wrote:
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues.
Not a good idea, please never do that, you will then be running BIOS code that has never been tested by the BIOS vendor. If this is needed, please let the kernel developers know what is going wrong, we should work exactly like other operating systems and not need to tell the BIOS differently.
pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard. Only enable it if you have tested that you really need it. You have been warned. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Nov 09, 2011 at 08:29:27PM -0800, Greg KH wrote:
pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard.
Only enable it if you have tested that you really need it. You have been warned.
That would be many/most Laptop users?
Ciao
Joerg
--
Joerg Mayer
On Thu, Nov 10, 2011 at 10:48:09AM +0100, Joerg Mayer wrote:
On Wed, Nov 09, 2011 at 08:29:27PM -0800, Greg KH wrote:
pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard.
Only enable it if you have tested that you really need it. You have been warned.
That would be many/most Laptop users?
No, only a very small minority need it (it's only recent models that this could affect). Use powertop to test if that is you or not. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, November 09, 2011 08:29:27 PM Greg KH wrote:
On Wed, Nov 09, 2011 at 08:13:23PM -0800, Roger Luedecke wrote:
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues.
Not a good idea, please never do that, you will then be running BIOS code that has never been tested by the BIOS vendor.
If this is needed, please let the kernel developers know what is going wrong, we should work exactly like other operating systems and not need to tell the BIOS differently.
pcie_aspm=force fixes power regression issue shown here;
http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard.
Only enable it if you have tested that you really need it. You have been warned.
greg k-h I use these so my machine would stop sounding like a vaccum cleaner. But you are the kernel geek. Question now is, can we do something upstream to help the issues that these parameters correct for me and others? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 10, 2011 at 06:08:35AM -0800, Roger Luedecke wrote:
On Wednesday, November 09, 2011 08:29:27 PM Greg KH wrote:
On Wed, Nov 09, 2011 at 08:13:23PM -0800, Roger Luedecke wrote:
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues.
Not a good idea, please never do that, you will then be running BIOS code that has never been tested by the BIOS vendor.
If this is needed, please let the kernel developers know what is going wrong, we should work exactly like other operating systems and not need to tell the BIOS differently.
pcie_aspm=force fixes power regression issue shown here;
http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard.
Only enable it if you have tested that you really need it. You have been warned.
greg k-h I use these so my machine would stop sounding like a vaccum cleaner. But you are the kernel geek.
Insults will get you no where.
Question now is, can we do something upstream to help the issues that these parameters correct for me and others?
Again, the first one should not be used unless your BIOS really is broken. The second one is not enabled because, again, some BIOSes are broken and lie so we need to be safe so that your machine doesn't break, there's nothing we can do automatically to enable this to be safe so that is why it is the way it is. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, November 10, 2011 07:40:53 AM you wrote:
On Thu, Nov 10, 2011 at 06:08:35AM -0800, Roger Luedecke wrote:
On Wednesday, November 09, 2011 08:29:27 PM Greg KH wrote:
On Wed, Nov 09, 2011 at 08:13:23PM -0800, Roger Luedecke wrote:
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues.
Not a good idea, please never do that, you will then be running BIOS code that has never been tested by the BIOS vendor.
If this is needed, please let the kernel developers know what is going wrong, we should work exactly like other operating systems and not need to tell the BIOS differently.
pcie_aspm=force fixes power regression issue shown here;
http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Only works on some machines, not others, be careful, it can lock your machine up hard.
Only enable it if you have tested that you really need it. You have been warned.
greg k-h
I use these so my machine would stop sounding like a vaccum cleaner. But you are the kernel geek.
Insults will get you no where.
Question now is, can we do something upstream to help the issues that these parameters correct for me and others?
Again, the first one should not be used unless your BIOS really is broken.
The second one is not enabled because, again, some BIOSes are broken and lie so we need to be safe so that your machine doesn't break, there's nothing we can do automatically to enable this to be safe so that is why it is the way it is.
greg k-h I really wish I knew why KMail likes you so much... it always tries to respond to you directly instead of the list, though it acts normally the rest of the time.
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 10, 2011 at 07:53:43AM -0800, Roger Luedecke wrote:
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down?
Again, no, there is nothing the kernel can do, it is a broken BIOS you are dealing with, please push your vendor to provide an updated, fixed, one. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 10, 2011 at 08:05:21AM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 07:53:43AM -0800, Roger Luedecke wrote:
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down?
Again, no, there is nothing the kernel can do, it is a broken BIOS you are dealing with, please push your vendor to provide an updated, fixed, one.
Dislaimer: IIRC, both points below are from phoronix.
At least one vendor has already declared that they see no need to
fix this as it works on Windows.
There is something that can be done: "Fix" the drivers individually to
turn on the powersaving.
Ciao
Joerg
PS: Is geek a bad word nowadays?
--
Joerg Mayer
On Thu, Nov 10, 2011 at 08:52:32PM +0100, Joerg Mayer wrote:
On Thu, Nov 10, 2011 at 08:05:21AM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 07:53:43AM -0800, Roger Luedecke wrote:
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down?
Again, no, there is nothing the kernel can do, it is a broken BIOS you are dealing with, please push your vendor to provide an updated, fixed, one.
Dislaimer: IIRC, both points below are from phoronix.
Which should never really be trusted. Seriously.
At least one vendor has already declared that they see no need to fix this as it works on Windows.
That's true, and that vendor doesn't care about Linux, so there's nothing we can do about it.
There is something that can be done: "Fix" the drivers individually to turn on the powersaving.
And exactly how can that be done? Specifics are needed as no one has yet been able to determine how to do this.
PS: Is geek a bad word nowadays?
I've always considered it as such: geek [geek] noun Slang. 1. a computer expert or enthusiast (a term of pride as self-reference, but often considered offensive when used by outsiders.) 2. a peculiar or otherwise dislikable person, especially one who is perceived to be overly intellectual. 3. a carnival performer who performs sensationally morbid or disgusting acts, as biting off the head of a live chicken. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 10/11/2011 21:13, Greg KH a écrit :
I've always considered it as such:
geek [geek] noun Slang. 1. a computer expert or enthusiast (a term of pride as self-reference, but often considered offensive when used by outsiders.) 2. a peculiar or otherwise dislikable person, especially one who is perceived to be overly intellectual. 3. a carnival performer who performs sensationally morbid or disgusting acts, as biting off the head of a live chicken.
oh! what dictionary is that! same here: http://www.thefreedictionary.com/geek are we not all geekos? among computer addicts, I never understood this as offensive. My bad. thanks quoting this jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 10, 2011 at 10:31:36PM +0100, jdd wrote:
Le 10/11/2011 21:13, Greg KH a écrit :
I've always considered it as such:
geek [geek] noun Slang. 1. a computer expert or enthusiast (a term of pride as self-reference, but often considered offensive when used by outsiders.) 2. a peculiar or otherwise dislikable person, especially one who is perceived to be overly intellectual. 3. a carnival performer who performs sensationally morbid or disgusting acts, as biting off the head of a live chicken.
oh! what dictionary is that!
http://dictionary.reference.com/browse/geek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 10, 2011 at 12:13:01PM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 08:52:32PM +0100, Joerg Mayer wrote:
On Thu, Nov 10, 2011 at 08:05:21AM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 07:53:43AM -0800, Roger Luedecke wrote:
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down?
Again, no, there is nothing the kernel can do, it is a broken BIOS you are dealing with, please push your vendor to provide an updated, fixed, one.
Dislaimer: IIRC, both points below are from phoronix.
Which should never really be trusted.
Seriously.
At least one vendor has already declared that they see no need to fix this as it works on Windows.
That's true, and that vendor doesn't care about Linux, so there's nothing we can do about it.
There is something that can be done: "Fix" the drivers individually to turn on the powersaving.
And exactly how can that be done? Specifics are needed as no one has yet been able to determine how to do this.
Ok, I spoke too soon, we might have a fix: https://lkml.org/lkml/2011/11/10/467 Will see how this goes, so perhaps this will be resolved in a few months. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, November 10, 2011 02:08:24 PM Greg KH wrote:
On Thu, Nov 10, 2011 at 12:13:01PM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 08:52:32PM +0100, Joerg Mayer wrote:
On Thu, Nov 10, 2011 at 08:05:21AM -0800, Greg KH wrote:
On Thu, Nov 10, 2011 at 07:53:43AM -0800, Roger Luedecke wrote:
Yeah, it does look like this is the best solution for now. Any hope on some sort of upstream fix coming down?
Again, no, there is nothing the kernel can do, it is a broken BIOS you are dealing with, please push your vendor to provide an updated, fixed, one.
Dislaimer: IIRC, both points below are from phoronix.
Which should never really be trusted.
Seriously.
At least one vendor has already declared that they see no need to fix this as it works on Windows.
That's true, and that vendor doesn't care about Linux, so there's nothing we can do about it.
There is something that can be done: "Fix" the drivers individually to turn on the powersaving.
And exactly how can that be done? Specifics are needed as no one has yet been able to determine how to do this.
Ok, I spoke too soon, we might have a fix: https://lkml.org/lkml/2011/11/10/467
Will see how this goes, so perhaps this will be resolved in a few months.
thanks,
greg k-h Yay! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10.11.2011 05:13, Roger Luedecke wrote:
acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues.
This is going to subtly break many systems as the code paths in the BIOS that you force with this switch are probably untested, even by the BIOS vendor. If the BIOS is so broken that it does not work with Windows, do you really expect the vendor to implement working Linux-specific code? -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Greg KH -
jdd -
Joerg Mayer -
Roger Luedecke -
Stefan Seyfried