Hi!
> > > > In the mean time I asked him to try with minimal number modules loaded.
> > >
> > > I indeed tryied with way much less modules lodaded, without success:
> >
> > Well, you still have way too many modules. What about init=/bin/bash
> > boot?
>
> Well, with this, the system does not wa
> > > In the mean time I asked him to try with minimal number modules loaded.
> >
> > I indeed tryied with way much less modules lodaded, without success:
>
> Well, you still have way too many modules. What about init=/bin/bash
> boot?
Well, with this, the system does not wake up either.
Moreo
> > I indeed tryied with way much less modules lodaded, without success:
>
> Well, you still have way too many modules. What about init=/bin/bash
> boot?
Hmmm, OK. I'll try that as soon as I have the opportunity (ie no mor
email to read, nothing left to hack, etc:-))
signature.asc
Descri
Hi!
> > Christian can't get s2ram to work to work with a 2.6.17 kernel, although
> > it is in the whitelist. It used to work with 2.6.16. Do you now of any
> > regressions?
> > Could anybody give him a hand in trying to get it to work again?
> >
> > In the mean time I asked him to try with minim
Quoting Tim Dijkstra ([EMAIL PROTECTED]):
> Hi,
>
> Christian can't get s2ram to work to work with a 2.6.17 kernel, although
> it is in the whitelist. It used to work with 2.6.16. Do you now of any
> regressions?
> Could anybody give him a hand in trying to get it to work again?
>
> In the mean
Hi,
Christian can't get s2ram to work to work with a 2.6.17 kernel, although
it is in the whitelist. It used to work with 2.6.16. Do you now of any
regressions?
Could anybody give him a hand in trying to get it to work again?
In the mean time I asked him to try with minimal number modules loaded
