lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Wed, 13 Sep 2006 09:33:25 -0700
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"Michiel de Boer" <x@...elhomicide.demon.nl>,
	"Ben B" <kernel@...cactii.net>
Cc:	<linux-kernel@...r.kernel.org>, <davej@...emonkey.org.uk>
Subject: RE: speedstep-centrino broke

 

>-----Original Message-----
>From: linux-kernel-owner@...r.kernel.org 
>[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of 
>Michiel de Boer
>Sent: Wednesday, September 13, 2006 12:28 AM
>To: Ben B
>Cc: linux-kernel@...r.kernel.org; davej@...emonkey.org.uk
>Subject: Re: speedstep-centrino broke
>
>Ben B wrote:
>> Hi,
>>
>> My HP notebook decided that its BIOS upgrade would break
>> speedstep-centrino, and trying to load the module gives me a "no such
>> device" error. This is with various combinations of kernel config
>> relating to cpufreq. Also tried acpi-cpufreq with the same error.
>>
>> I suspect that the new bios is broken, but perhaps it's 
>correct and the
>> linux driver is missing something?
>>
>> Anyway, relevent info below.
>>
>> Cheers,
>> Ben
>>   
>
>I have the same problem, running kernel 2.6.17.13, and also 
>get the 'No 
>such device' error.
>This problem doesn't occur when i boot 2.6.16.16, so the 
>behaviour must 
>have been introduced
>somewhere in between.
>

Just to confirm. Moving from 2.6.16.16 to 2.6.17.13 with no other change
to system (BIOS change) breaks the driver? Did you also try acpi-cpufreq
driver with 2.6.17.13?

Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ