On Mon, Sep 5, 2011 at 6:25 PM, Shea Levy s...@shealevy.com wrote:
On 09/05/2011 10:59 AM, Eelco Dolstra wrote:
Hi,
On 09/03/2011 02:41 PM, Peter Simons wrote:
this commit
* Use the CFQ I/O scheduler, rather than the ‘none’ scheduler. This
was already the case on Linux
4e64f7f0.5060...@shealevy.com)
Mime-Version: 1.0
Content-type: text/plain; charset=UTF-8
breaks my boot process. The linuxPackages_2_6_38_ati kernel hangs after
probing the ata devices. I've reverted to an older version for now, but
maybe I'm not the only one who's going to have that problem?
On Wed, Sep 07, 2011 at 10:46:43PM +0400, Michael Raskin wrote:
4e64f7f0.5060...@shealevy.com)
Mime-Version: 1.0
Content-type: text/plain; charset=UTF-8
breaks my boot process. The linuxPackages_2_6_38_ati kernel hangs after
probing the ata devices. I've reverted to an older version for
Hi,
On 09/03/2011 02:41 PM, Peter Simons wrote:
this commit
* Use the CFQ I/O scheduler, rather than the ‘none’ scheduler. This
was already the case on Linux 2.6.32, but in newer kernels the CFQ
scheduler is built as a module, so all block devices got the ‘none’
On 09/05/2011 10:59 AM, Eelco Dolstra wrote:
Hi,
On 09/03/2011 02:41 PM, Peter Simons wrote:
this commit
* Use the CFQ I/O scheduler, rather than the ‘none’ scheduler.
This
was already the case on Linux 2.6.32, but in newer kernels the
CFQ
scheduler is built as a
Hi Eelco,
this commit
* Use the CFQ I/O scheduler, rather than the ‘none’ scheduler. This
was already the case on Linux 2.6.32, but in newer kernels the CFQ
scheduler is built as a module, so all block devices got the ‘none’
scheduler instead.
breaks my boot process. The
this commit
* Use the CFQ I/O scheduler, rather than the ‘none’ scheduler. This
was already the case on Linux 2.6.32, but in newer kernels the CFQ
scheduler is built as a module, so all block devices got the ‘none’
scheduler instead.
breaks my boot process. The
