Hello,
I think there is a problem with kernel-image-2.6.8-1-686, but I'm not sure
whether I messed up something...
I installed sarge on a SATA host a while ago (Intel ICH, worked just
fine!). Now I upgraded from the installer's kernel-image-2.6.8-1-386 to
version 2.6.8-10 of the
On Wed, Dec 01, 2004 at 12:01:29PM +0100, Richard Atterer wrote:
Obviously, you cannot load the SATA modules if you need the SATA code to
access the hard disc.
Of course you can, that's what initial ramdisks are for.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital
On Wed, Dec 01, 2004 at 03:06:17AM -0800, Steve Langasek wrote:
On Wed, Dec 01, 2004 at 12:01:29PM +0100, Richard Atterer wrote:
Obviously, you cannot load the SATA modules if you need the SATA code to
access the hard disc.
Of course you can, that's what initial ramdisks are for.
On Wed, Dec 01, 2004 at 03:27:56PM +0100, Richard Atterer wrote:
On Wed, Dec 01, 2004 at 03:06:17AM -0800, Steve Langasek wrote:
On Wed, Dec 01, 2004 at 12:01:29PM +0100, Richard Atterer wrote:
Obviously, you cannot load the SATA modules if you need the SATA code to
access the hard disc.
Richard Atterer [EMAIL PROTECTED] writes:
Hello,
I think there is a problem with kernel-image-2.6.8-1-686, but I'm not sure
whether I messed up something...
I installed sarge on a SATA host a while ago (Intel ICH, worked just
fine!). Now I upgraded from the installer's
On Wed, Dec 01, 2004 at 06:37:52PM +0100, Goswin von Brederlow wrote:
The problem is with near certainty that you updated from a
sata-ide driver to a sata-scsi driver. The device names for your disk
subsequently changed from /dev/hda to /dev/sda.
No, I am positive that I have been using
6 matches
Mail list logo