On Wednesday, 8 November 2006 01:44, Stefan Seyfried wrote:
> On Tue, Nov 07, 2006 at 10:02:07PM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 7 November 2006 15:32, Rafael J. Wysocki wrote:
> > > On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote:
> > > > On Tue, Nov 07, 2006 at 02:28:26PM
On Tue, Nov 07, 2006 at 10:02:07PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, 7 November 2006 15:32, Rafael J. Wysocki wrote:
> > On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote:
> > > On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote:
> > > > The same parameter works fo
On Tuesday, 7 November 2006 15:32, Rafael J. Wysocki wrote:
> On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote:
> > On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote:
> > > The same parameter works for 'resume', but currenty it needs to be set in
> > > the config file. Howe
On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote:
> On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote:
> > The same parameter works for 'resume', but currenty it needs to be set in
> > the config file. However, when I finally apply the command-line-parsing
> > patch,
> > i
On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote:
> The same parameter works for 'resume', but currenty it needs to be set in
> the config file. However, when I finally apply the command-line-parsing
> patch,
> it'll be easy to add a command line switch for that.
The module load
On Tuesday, 7 November 2006 10:24, Stefan Seyfried wrote:
> On Mon, Nov 06, 2006 at 09:01:20PM +0100, Rafael J. Wysocki wrote:
> > On Monday, 6 November 2006 17:34, Stefan Seyfried wrote:
>
> > > So how about this (i elected vt63 since that is where the in-kernel code
> > > traditionally printed i
On Mon, Nov 06, 2006 at 09:01:20PM +0100, Rafael J. Wysocki wrote:
> On Monday, 6 November 2006 17:34, Stefan Seyfried wrote:
> > So how about this (i elected vt63 since that is where the in-kernel code
> > traditionally printed its messages):
>
> Frankly, I don't like this change.
I did expect
Hi!
> when investigating a suspend problem, i noticed that it is not paticlularly
> useful to switch to the console where the kernel messages are redirected to:
> After resume, you see nothing of the suspend messages, because everything
> is pushed off the screen by the drivers chatting about susp
On Monday, 6 November 2006 17:34, Stefan Seyfried wrote:
> Hi,
>
> when investigating a suspend problem, i noticed that it is not paticlularly
> useful to switch to the console where the kernel messages are redirected to:
> After resume, you see nothing of the suspend messages, because everything
Hi,
when investigating a suspend problem, i noticed that it is not paticlularly
useful to switch to the console where the kernel messages are redirected to:
After resume, you see nothing of the suspend messages, because everything
is pushed off the screen by the drivers chatting about suspend and
10 matches
Mail list logo
