Toshikazu Aiyama, Ph.D. wrote:
A.E.Lawrence wrote:
I have a similar set up with you:
ASUS a8n-sli Deluxe mbrd populated with 5 hard disks:
a) 1 scsi MO on adaptec 2940UW
b) 1 PATA primary master
c) 4 sata on nv_sata, none on sil_SATA
In addition, I have 1 DVD-RAM, and 1 CD-RW on PATA secondary.
Forgot to CC the list.
-- Forwarded message --
From: John Baab [EMAIL PROTECTED]
Date: Apr 12, 2005 8:37 AM
Subject: Re: Installer and installed system differ in disk enumeration
To: A E Lawrence [EMAIL PROTECTED]
I have had a similiar problem while using a pata and a sata drive
There are at least 2 ways to complete installation.
1. Using default kernel: Have you selected a non-default kernel? Choose
default like kernel-image-2.6-amd64, but not 2.6.9-10-amd64.
2. Using chroot: Install mini 64-bit system to one of PATA disk: /dev/hda
through hdd.
aiyama wrote:
There are at least 2 ways to complete installation.
1. Using default kernel: Have you selected a non-default kernel? Choose
default like kernel-image-2.6-amd64, but not 2.6.9-10-amd64.
2. Using chroot: Install mini 64-bit system to one of PATA disk:
A.E.Lawrence wrote:
The problems arise before those options are available :-( But it is
possible to use grub's editing options to get an initial system. Then
one can edit the grub configuration and /etc/fstab to match whichever
kernel is loaded. The point is that the installer is setting
Sata disk enumeration and installer on amd64
I have an ASUS a8n-sli Deluxe mbrd populated with 6 hard disks:-
a) 1 scsi
b) 1 IDE on pata (legacy, parallel ata
c) 4 sata
1) Disk enumeration differs between installer and installed system
On Apr 10, 2005 10:28 AM, A.E.Lawrence [EMAIL PROTECTED] wrote:
Presumably the installer kernal and target kernels load modules in a
different order.
I wonder it is possible to load them in the same order? The installer
may load the kernel modules triggered by the udev-packages, whereas
the
7 matches
Mail list logo