On Sat, Jan 13, 2007 at 04:45:12 +0100, Tino Keitel wrote:
> On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
>
> [...]
>
> > I think I found the problem. In 2.6.18, I had a slightly different
> > config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without
> > the USB DVB-T b
On Sat 2007-01-13 04:45:12, Tino Keitel wrote:
> On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
>
> [...]
>
> > I think I found the problem. In 2.6.18, I had a slightly different
> > config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without
> > the USB DVB-T box attached.
On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
[...]
> I think I found the problem. In 2.6.18, I had a slightly different
> config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without
> the USB DVB-T box attached. I tweaked the USB options a bit and
> activated some options
On Fri, Jan 12, 2007 at 14:50:25 +, Pavel Machek wrote:
> Hi!
>
> > > >> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > > >> > 2.6.20-rc3.
> > > >>
> > > >> Is this issue still present in -rc4?
> > > >
> > > >I used 2.6.20-rc4 in single user mode, and applied 2 pat
Hi!
> > >> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > >> > 2.6.20-rc3.
> > >>
> > >> Is this issue still present in -rc4?
> > >
> > >I used 2.6.20-rc4 in single user mode, and applied 2 patches from
> > >netdev to get wake on LAN support. This way I was able to set
On Tue, Jan 09, 2007 at 22:51:04 +0800, Luming Yu wrote:
> >> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> >> > 2.6.20-rc3.
> >>
> >> Is this issue still present in -rc4?
> >
> >I used 2.6.20-rc4 in single user mode, and applied 2 patches from
> >netdev to get wake on L
> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > 2.6.20-rc3.
>
> Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from
netdev to get wake on LAN support. This way I was able to set up an
automatic suspend/resume loop. I
On Monday, 8 January 2007 23:02, Tino Keitel wrote:
> On Mon, Jan 08, 2007 at 17:17:19 +0100, Pavel Machek wrote:
> > On Sun 2007-01-07 23:27:06, Tino Keitel wrote:
> > > On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > > > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> >
On Mon, Jan 08, 2007 at 17:17:19 +0100, Pavel Machek wrote:
> On Sun 2007-01-07 23:27:06, Tino Keitel wrote:
> > On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > > > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
>
On Sun 2007-01-07 23:27:06, Tino Keitel wrote:
> On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> > > > No information about the device/driver that refuses to resume
On Mon, Jan 08, 2007 at 00:44:45 +0100, Adrian Bunk wrote:
> On Sun, Jan 07, 2007 at 11:27:06PM +0100, Tino Keitel wrote:
> > On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > > > On Sun, 2007-01-07 at 16:17 +0100, Tino Ke
On Sun, Jan 07, 2007 at 11:27:06PM +0100, Tino Keitel wrote:
> On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> > > > No information about the device/driver that ref
On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> > > No information about the device/driver that refuses to resume.
> >
> > You should be able to identify the problemat
On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> > No information about the device/driver that refuses to resume.
>
> You should be able to identify the problematic driver by removing each
> driver manually before suspending.
I ca
On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> No information about the device/driver that refuses to resume.
You should be able to identify the problematic driver by removing each
driver manually before suspending.
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-k
15 matches
Mail list logo