On 02/23/2012 10:16 AM, Heiko Zuerker wrote:
Quoting Dominic Raferd <dl@edendevelopments.co.uk>:

Hi Martin

Can you tell us what you see, without USB stick in, when the boot
process gets to the stage:

Creating devices in /dev
Searching for configuration media
Checking...

what gets checked and what results are returned?

I wonder if your system is checking the device where etc-mods-tar.bz2 is
stored, or if it is trying to check it but is unable to read it. With
your USB stick out I think the mSATA drive would be /dev/sda. Did you
store the configuration on the first partition of mSATA (/dev/sda1) or
on a separate second partition (/dev/sda2)? If the former, you might try
the latter, it is really better anyway. What boot loader are you using?
Did you (re-)format the partition(s) and if so how?

Dominic

[ After the initial boot process there are normally two steps to finding
the DL system configuration:

 1. search for etc-mods.tar.bz2 on devices in turn (e.g. /dev/hda
    /dev/hdc1 /dev/hdc /deb/hdb1) which should (of course) end with
    success, then 'loading configuration'
 2. search for Devil-Linux CD-ROM, in this case a 'Search List' is first
    printed (e.g. /dev/hda /dev/hdc /dev/hdb) and then they are checked
    in turn, so this should end with 'Found Devil-Linux v...' ]
Do you see your partitions listed?
Does the kernel detect your SATA controller? Does it find the drive?
Yes I see the partitions listed
root@Devil:~ # fdisk -l

Disk /dev/sda: 4009 MB, 4009754624 bytes
145 heads, 48 sectors/track, 1125 cylinders, total 7831552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          48     7831551     3915752    b  W95 FAT32

Disk /dev/sdb: 1979 MB, 1979228160 bytes
255 heads, 63 sectors/track, 240 cylinders, total 3865680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63     3850559     1925248+   b  W95 FAT32
/dev/sdb2         3850560     3865679        7560    b  W95 FAT32


I am assuming the kernel is seeing the sata controller as I can access the mSATA drive once booted to partition/read/write, etc.

Would there be any device driver that is only being loaded once etc-mods has been read?