On Sunday, 27 of January 2008, G L wrote:
> Hello,
Hi,
> Thanks for replying!
>
> Well I updated Mythbuntu 7.10 to the latest kernel offered, which is
> 2.6.22-14-generic.
Please don't drop CCs in the next messages, thanks.
Would you be able to install a kernel.org kernel?
Rafael
-
To unsub
[0.00] Kernel command line:
root=UUID=1bc00e49-e21a-47fc-8641-fbd7b557f8dd ro acpi_osi=!Linux
==> /proc/acpi/ac_adapter <==
==> /proc/acpi/alarm <==
2008-01-00 00:38:15
==> /proc/acpi/battery <==
==> /proc/acpi/button <==
==> /proc/acpi/embedded_controller <==
==> /proc/acpi/fan <==
=
On Sat, Jan 26, 2008 at 05:46:59PM +0200, eaglex wrote:
> > Could you send the output of lspci and upload somewhere the DSDT (or
> > send me provately as I'm not sure about the limits for postings to this
> > list).
>
> lspci: http://pastebin.ca/873456
> dsdt: http://pastebin.ca/873459
01:00.0 VG
> eh... this is known not to be working with sony-laptop. Even though the
> DSDT exposes the brightness methods the nvidia cards have their own way
> to handle dimming the screen.
> You can try with nvclock which works for *some* cards.
Thanks, I'll try nvclock.
> For now all sony-laptop can do i
On Sun, Jan 27, 2008 at 03:16:27PM +0200, eaglex wrote:
...
> > For now all sony-laptop can do is enable the Fn keys, I'll add your
> > model to the DMI list asap.
>
> Any chances of getting the rest of the controls working? (like turning
> on bluetooth and so on)
well, not until somebody is able
I'm currently trying out suspend (S3) on a few machines but none of them wakes
up completely/properly (I have a few more hosts I'm planning to try suspend
on once I can get useful information out of those not waking up properly).
Tested kernels: 2.6.24(-rc8), on one 2.6.23.8
To suspend I enter
Bruno Prémont a écrit :
I'm currently trying out suspend (S3) on a few machines but none of them wakes
up completely/properly (I have a few more hosts I'm planning to try suspend
on once I can get useful information out of those not waking up properly).
Tested kernels: 2.6.24(-rc8), on one 2.6
On 23-01-08 18:38, Thomas Renninger wrote:
isapnp is totally untested. Also the sysfs is rather untested.
If nobody beats me to it I'll debug this myself later on, but as a quick
heads up:
pnp: the driver 'cs4236_isapnp' has been registered
cs4236_isapnp 01:01.00: driver attached
cs4236_isa
On Saturday 26 January 2008 14:48:24 Eric Cooper wrote:
> I happened to look at the patched asus_acpi.c module that was posted
> by Asus for the Eee PC and noticed that it's 75% dead code -- the Eee
> PC support is just stuck on at the end. And of course it conflicts
> with the real asus_acpi.ko i
On Friday 18 January 2008 23:58:18 Carlos Corbacho wrote:
> ANYWR - Another New Year WMI release
>
> Len,
>
> Can you please review at least the first two patches in this series, as I
> would still really like to try and get them into 2.6.25.
Len,
I have a small update for acer-wmi to add another
Hi Thomas,
On Sun, 2008-01-20 at 02:23 +0200, Pekka Enberg wrote:
> > When krealloc() returns NULL, there wasn't enough memory to fit the
> > new size but the original memory region remains unchanged.
On Jan 23, 2008 7:38 PM, Thomas Renninger <[EMAIL PROTECTED]> wrote:
> Thanks Pekka, this one sh
On Sat, Jan 26, 2008 at 10:00:45PM -0800, Andrew Morton wrote:
> - Create a new /sys node with a new name which has the new semantics.
The semantics are the same as they always have been - values between 0
and max_brightness are valid values. If you've made assumptions about
what max_brightness
On Sunday, 27 of January 2008, Bruno Prémont wrote:
> I'm currently trying out suspend (S3) on a few machines but none of them
> wakes
> up completely/properly (I have a few more hosts I'm planning to try suspend
> on once I can get useful information out of those not waking up properly).
>
> T
On Mon, 28 Jan 2008 01:25:50 + Matthew Garrett <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 26, 2008 at 10:00:45PM -0800, Andrew Morton wrote:
> > - Create a new /sys node with a new name which has the new semantics.
>
> The semantics are the same as they always have been - values between 0
> an
On Sun, Jan 27, 2008 at 09:10:13PM -0800, Andrew Morton wrote:
> You cannot seriously tell me that if we are to change this range from 0-8
> up to 0-100 then this is not a backwards-incompatible change in
> semantics.
We're talking about changing 0-100 to 0-something sane, because the
current dr
Hi, all,
This patch series is for T-state coordination.
Patch 01 Set the bit of ACPI_PDC_SMP_T_SWCOORD.
Patch 02 Check the parameter when calling the function of
acpi_processor_get/set_throttling.
Patch 03 Update the T-state coordination after obtaining _TSD info
Patch 04 Add the t-state event no
Subject: ACPI : Update the t-state for every affected cpu when t-state is
changed
>From : Zhao Yakui <[EMAIL PROTECTED]>
According to ACPI spec, the _TSD object provides T-state control cross
logical processor dependency information to OSPM. So the t-state
coordination should be considered when T
Subject: ACPI : Update T-state coordination after getting _TSD info
>From : Zhao Yakui <[EMAIL PROTECTED]>
Accordint to ACPI spec, the _TSD object provides T-state control cross
logical processor dependency information to OSPM.
After the _TSD data for all cpus are obtained, OSPM will set up
the T
Subject: ACPI: Set the bif of ACPI_PDC_SMP_T_SWCOORD for _PDC
>From : Zhao Yakui <[EMAIL PROTECTED]>
The bit of ACPI_PDC_SMP_T_SWCOORD is set so that OSPM is capable of
native ACPI throttling software coordination for mutli-processors
using the _TSD information.
Signed-off-by: Zhao Yakui <[EMA
Subject: ACPI : Check parameter when calling acpi_processor_get/set_throttling
>From : Zhao Yakui <[EMAIL PROTECTED]>
It is necessary to check the parameter when calling the function of
acpi_processor_get/set_throttling function so as to avoid the NULL
pointer reference in pr or throttling.
htt
Subject: ACPI : Add T-state event notifier function
>From : Zhao Yakui <[EMAIL PROTECTED]>
The t-state coordination should be considered when T-state for one cpu
is changed.It means that OSPM should select one proper target T-state for
the all affected cpus before updating T-state.
So the funct
21 matches
Mail list logo
