On Tue, Sep 07, 2004 at 10:17:35PM +0200, Geert Uytterhoeven wrote:
> On Tue, 7 Sep 2004, Kars de Jong wrote:
> > So I built the 2.6.8.1 kernel based on my old config, and voila, it
> > worked fine...
> >
> > Now it was time to find out which config option caused the problem...
> >
> > Took me quit
On Thu, 2004-09-09 at 20:18, Christian T. Steigies wrote:
> On Wed, Sep 08, 2004 at 11:00:53PM +0200, Kars de Jong wrote:
> >
> > > I'll try the MVME147 kernels tomorrow as well.
> >
> > Sorry, didn't have time for that.
> >
> > Anyway, I'm going on holiday for the next 2 1/2 weeks, so I leave y
On Wed, Sep 08, 2004 at 11:00:53PM +0200, Kars de Jong wrote:
>
> > I'll try the MVME147 kernels tomorrow as well.
>
> Sorry, didn't have time for that.
>
> Anyway, I'm going on holiday for the next 2 1/2 weeks, so I leave you to
> figure it out. Surely there are more people with an MVME16x boar
On Wed, Sep 08, 2004 at 11:00:53PM +0200, Kars de Jong wrote:
> On Tue, 2004-09-07 at 22:14, Kars de Jong wrote:
> > On Tue, 2004-09-07 at 21:38, Christian T. Steigies wrote:
> > > You are saying we need to build 2.4.27 with this too? What about 2.4.26,
> > > does that debian version work?
> >
> >
On Tue, 2004-09-07 at 22:14, Kars de Jong wrote:
> On Tue, 2004-09-07 at 21:38, Christian T. Steigies wrote:
> > You are saying we need to build 2.4.27 with this too? What about 2.4.26,
> > does that debian version work?
>
> No idea, I'll try it tomorrow.
Tried it, didn't work. Again, my own-comp
On Tue, 2004-09-07 at 21:38, Christian T. Steigies wrote:
> On Tue, Sep 07, 2004 at 08:26:07PM +0200, Kars de Jong wrote:
> > Now it was time to find out which config option caused the problem...
> >
> > Took me quite some recompile/reboot cycles, but it turned out to be
> > CONFIG_SINGLE_MEMORY_C
On Tue, 7 Sep 2004, Kars de Jong wrote:
> So I built the 2.6.8.1 kernel based on my old config, and voila, it
> worked fine...
>
> Now it was time to find out which config option caused the problem...
>
> Took me quite some recompile/reboot cycles, but it turned out to be
> CONFIG_SINGLE_MEMORY_CHU
On Tue, Sep 07, 2004 at 08:26:07PM +0200, Kars de Jong wrote:
>
> So, I decided to take a kernel from daily d-i builds,
> vmlinuz-2.4.27-mvme16x. Oddly enough, this kernel crashed with the same
> error message...
>
> But I did have a working 2.4.26 kernel which I built myself.
>
> Then I tried v
On Mon, 2004-09-06 at 20:06, Kars de Jong wrote:
> I hope to be able to test the SCSI driver and this driver tomorrow.
And I did, with mixed results.
First, I built a kernel (CVS-current with my patches) based on the a
config from the kernel-image-2.6.8-mvme16x_2.6.8-1_m68k.deb from
Christian.
S
9 matches
Mail list logo