> Looking back through this bug report, manually loading sata_via worked
> for him with the 2.4.26 kernel before. I'm not clear on whether this is
> still the problem (in which case we need lspci information and to
> reassign it to discover1-data), or whether the module is now loaded by
> the insta
Christian Perrier wrote:
> Quoting Joey Hess ([EMAIL PROTECTED]):
> > Christian Perrier wrote:
> > > We should then close this bug report though I have a little concern as the
> > > installation did not work with the 2.4 kernel which is the default d-i
> > > kernelshould we keep such bug report
Quoting Joey Hess ([EMAIL PROTECTED]):
> Christian Perrier wrote:
> > We should then close this bug report though I have a little concern as the
> > installation did not work with the 2.4 kernel which is the default d-i
> > kernelshould we keep such bug reports opened when using 2.6 solves
> >
Christian Perrier wrote:
> We should then close this bug report though I have a little concern as the
> installation did not work with the 2.4 kernel which is the default d-i
> kernelshould we keep such bug reports opened when using 2.6 solves
> a problem?
If you're going to close it otherwise
Quoting Greg Baker ([EMAIL PROTECTED]):
> I just tried this again with rc2 netinst and it seemed to work just
> fine.
>
> I had to use linux26 to get the SATA drive working (at least, I think
> that was the problem). But after that, everything was smooth sailing:
> both SATA and on-board ethernet
I just tried this again with rc2 netinst and it seemed to work just
fine.
I had to use linux26 to get the SATA drive working (at least, I think
that was the problem). But after that, everything was smooth sailing:
both SATA and on-board ethernet.
--
Greg Baker, Lecturer
School of Computing Scie
6 matches
Mail list logo
