From: Martin G. <sou...@gl...> - 2012-02-23 03:48:57
|
Hi, Been using DL for a while and now I am trying to replace my PC hardware. I have a new Soekris NET6501 with an internal 2GB mSATA drive (TS2GMSA500). I've installed DL on a USB stick and have it running from there but I want to install it on the mSATA drive. I've used the install-on-usb script and and installed DL on the drive (including etc-mods) however I have a problem - the system boots off the mSATA drive, but then when it comes to loading etc-mods, it cannot find etc-mods or the bootcd.iso file and so cannot boot. If I boot from the mSATA drive with the USB stick in place, it finds the config on the USB stick as well as the bootcd.iso and continues to boot of the USB stick. The USB stick appears as /dev/sda The mSATA drive appears as /dev/sdb I have tried both 1.4 and 1.6 versions of DL with the same result. It's as if DL finds the mSATA drive to start the boot process but then loses it when it creates udev and searches for the configuration file. Does anyone have any thoughts on how I can get this working off the mSATA drive or what I might be doing wrong? Thanks Martin |
From: Dominic R. <dl...@ed...> - 2012-02-23 10:17:29
|
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...' ] On 23/02/2012 03:33, Martin Glazer wrote: > Hi, > > Been using DL for a while and now I am trying to replace my PC hardware. > I have a new Soekris NET6501 with an internal 2GB mSATA drive > (TS2GMSA500). > > I've installed DL on a USB stick and have it running from there but I > want to install it on the mSATA drive. > > I've used the install-on-usb script and and installed DL on the drive > (including etc-mods) however I have a problem - the system boots off > the mSATA drive, but then when it comes to loading etc-mods, it cannot > find etc-mods or the bootcd.iso file and so cannot boot. > > If I boot from the mSATA drive with the USB stick in place, it finds > the config on the USB stick as well as the bootcd.iso and continues to > boot of the USB stick. > The USB stick appears as /dev/sda > The mSATA drive appears as /dev/sdb > > I have tried both 1.4 and 1.6 versions of DL with the same result. > > It's as if DL finds the mSATA drive to start the boot process but then > loses it when it creates udev and searches for the configuration file. > > Does anyone have any thoughts on how I can get this working off the > mSATA drive or what I might be doing wrong? > > > Thanks > > > Martin > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Martin G. <sou...@gl...> - 2012-02-24 02:05:59
|
Hi, Thanks for the response, I don't see it finding any media when it gets to that spot.... ... Version 1.6.0-RC2 Kernel 3.2.4-grsec Mounting SHM FS on /shm waiting until usb-storage driver has initialized all devices ... Creating devices in /dev Searching for configuration media Would you really like to load DL without Configuration Media? (y/n) The mSATA drive has 2 partitions - one with just the etc-mods and the other with both etc-mods and bootdisk.iso, etc I have reformated the mSATA drive a few times already, but that has made no difference. Here is what happens if I boot off the mSATA drive with the USB drive in place... ... Version 1.6.0-RC2 Kernel 3.2.4-grsec Mounting SHM FS on /shm waiting until usb-storage driver has initialized all devices ... Creating devices in /dev Searching for configuration media Checking for "etc-mods.tar.bz2" on "/dev/sda1" ... success! loading configuration Searching for Devil-Linux CD-ROM Search list: checking /dev/sda1 ... Found Devil-Linux v1.6.0-RC2 Found ISO (1.6.0-RC2) on /dev/sda1 Mounting SHM FS on /cdrom/shm Unmounting proc Starting up final system... In other words, the USB drive is identified as /dev/sda I am pretty sure it is booting initially from the mSATA drive as that is what I have in the boot order and I don't see any activity on the USB LED until after the configuration is searched/found. I used SysLinux with serial console for the boot loader as I could not get it to boot using Grub (with serial). Here is the output of fdisk -l (the USB device is seen as /dev/sda) 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 Any other thoughts? On 02/23/2012 03:17 AM, Dominic Raferd wrote: > 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...' ] > > On 23/02/2012 03:33, Martin Glazer wrote: >> Hi, >> >> Been using DL for a while and now I am trying to replace my PC hardware. >> I have a new Soekris NET6501 with an internal 2GB mSATA drive >> (TS2GMSA500). >> >> I've installed DL on a USB stick and have it running from there but I >> want to install it on the mSATA drive. >> >> I've used the install-on-usb script and and installed DL on the drive >> (including etc-mods) however I have a problem - the system boots off >> the mSATA drive, but then when it comes to loading etc-mods, it cannot >> find etc-mods or the bootcd.iso file and so cannot boot. >> >> If I boot from the mSATA drive with the USB stick in place, it finds >> the config on the USB stick as well as the bootcd.iso and continues to >> boot of the USB stick. >> The USB stick appears as /dev/sda >> The mSATA drive appears as /dev/sdb >> >> I have tried both 1.4 and 1.6 versions of DL with the same result. >> >> It's as if DL finds the mSATA drive to start the boot process but then >> loses it when it creates udev and searches for the configuration file. >> >> Does anyone have any thoughts on how I can get this working off the >> mSATA drive or what I might be doing wrong? >> >> >> Thanks >> >> >> Martin >> >> >> ------------------------------------------------------------------------------ >> Virtualization& Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> >> >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Serge L. <ser...@gm...> - 2012-02-24 03:06:23
|
Hi Martin, On 02/23/2012 06:05 PM, Martin Glazer wrote: > > Here is the output of fdisk -l (the USB device is seen as /dev/sda) ... > Any other thoughts? find the PCI address for the device example: root@hyper:/sys/class/block # ls -l /sys/class/block/sdb lrwxrwxrwx 1 root root 0 Feb 22 18:09 /sys/class/block/sdb -> ../../devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:0/block/sdb (address is 00:1a.7) then find what modules the PCI device uses. example: 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 (prog-if 20 [EHCI]) Subsystem: Super Micro Computer Inc Device 0006 Flags: bus master, medium devsel, latency 0, IRQ 18 Memory at fbeda000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd (kernel driver is ehci_hcd). If it doesn't work for some reason, just post "lspci -v | grep "Kernel driver in use:" I'll try to find what driver is absent in initrd. Serge |
From: Martin G. <sou...@gl...> - 2012-02-24 08:06:54
|
Hi, Thanks for that tip. I followed your instructions and it looks like it is using the pcieport module root@Devil:~ # ll /sys/class/block/sdb lrwxrwxrwx 1 root root 0 Mar 3 06:24 /sys/class/block/sdb -> ../../devices/pci0000:00/0000:00:17.0/0000:01:00.0/00b root@Devil:~ # lspci -v ... 00:17.0 PCI bridge: Intel Corporation Atom Processor E6xx PCI Express Port 1 (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 I/O behind bridge: 00001000-00001fff Memory behind bridge: a0000000-a0ffffff Prefetchable memory behind bridge: 80000000-801fffff Capabilities: [40] Express Root Port (Slot-), MSI 00 Capabilities: [90] Subsystem: Gammagraphx, Inc. (or missing ID) Device 0000 Capabilities: [a0] Power Management version 2 Kernel driver in use: pcieport Although doing a lsmod, I don't see that module loaded, root@Devil:~ # lsmod Module Size Used by ipv6 274019 12 dm_mod 66521 0 md_mod 100338 0 i2c_isch 3124 0 i2c_core 18870 1 i2c_isch ahci 19843 1 libahci 19102 1 ahci libata 163311 2 ahci,libahci uas 8089 0 e1000e 138681 0 pch_gbe 32970 0 pch_phub 6506 0 mii 3787 1 pch_gbe lpc_sch 2464 0 shpchp 25273 0 pci_hotplug 22206 1 shpchp cn 3905 0 loop 67443 2 On 02/23/2012 08:06 PM, Serge Leschinsky wrote: > Hi Martin, > > On 02/23/2012 06:05 PM, Martin Glazer wrote: > >> Here is the output of fdisk -l (the USB device is seen as /dev/sda) > ... >> Any other thoughts? > find the PCI address for the device > > example: > > root@hyper:/sys/class/block # ls -l /sys/class/block/sdb > lrwxrwxrwx 1 root root 0 Feb 22 18:09 /sys/class/block/sdb -> > ../../devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:0/block/sdb > > (address is 00:1a.7) > > then find what modules the PCI device uses. > > example: > 00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI > Controller #2 (prog-if 20 [EHCI]) > Subsystem: Super Micro Computer Inc Device 0006 > Flags: bus master, medium devsel, latency 0, IRQ 18 > Memory at fbeda000 (32-bit, non-prefetchable) [size=1K] > Capabilities: [50] Power Management version 2 > Capabilities: [58] Debug port: BAR=1 offset=00a0 > Capabilities: [98] PCI Advanced Features > Kernel driver in use: ehci_hcd > > (kernel driver is ehci_hcd). > > > If it doesn't work for some reason, just post "lspci -v | grep "Kernel driver in > use:" I'll try to find what driver is absent in initrd. > > > Serge |
From: Serge L. <ser...@gm...> - 2012-02-25 01:52:03
|
Hi Martin, On 02/24/2012 12:06 AM, Martin Glazer wrote: > Hi, > > Thanks for that tip. > > I followed your instructions and it looks like it is using the pcieport module .... > Kernel driver in use: pcieport Hmm... Am I correct that this device (/dev/sdb) has PCI-E interface? Interesting... However, I don't see any problem with the _drive_ modules, all ata* drivers are in initrd. Most probably there is a pci discovery specific and you need pci hotplug modules ( pci_hotplug, shpchp) which are apparently not in initrd. If you want, I can send you instruction how to rebuild/repack it and we check what exactly modules are necessary for correct mSATA drive detection. Probably we need to add them by default.... Serge |
From: Martin G. <sou...@gl...> - 2012-02-25 06:14:43
|
Hi Serge, On 02/24/2012 06:51 PM, Serge Leschinsky wrote: > Hmm... Am I correct that this device (/dev/sdb) has PCI-E interface? Interesting... That is what I thought > However, I don't see any problem with the _drive_ modules, all ata* drivers are > in initrd. Most probably there is a pci discovery specific and you need pci > hotplug modules ( pci_hotplug, shpchp) which are apparently not in initrd. If > you want, I can send you instruction how to rebuild/repack it and we check what > exactly modules are necessary for correct mSATA drive detection. > Probably we need to add them by default.... I think it must be the hotplug modules that are missing this is my output from lsmod root@Devil:~ # lsmod Module Size Used by ipv6 274019 12 dm_mod 66521 0 md_mod 100338 0 i2c_isch 3124 0 i2c_core 18870 1 i2c_isch uas 8089 0 ahci 19843 0 libahci 19102 1 ahci e1000e 138681 0 libata 163311 2 ahci,libahci pch_gbe 32970 0 mii 3787 1 pch_gbe pch_phub 6506 0 lpc_sch 2464 0 shpchp 25273 0 pci_hotplug 22206 1 shpchp cn 3905 0 loop 67443 2 additionally, in dmesg, this is what I get from when the mSATA drive is detected. ... scsi2 : ahci ata1: SATA max UDMA/133 abar m1024@0xa0004400 port 0xa0004500 irq 52 ata2: SATA max UDMA/133 abar m1024@0xa0004400 port 0xa0004580 irq 52 ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7: TS2GMSA500, 20101212, max UDMA/133 ata1.00: 3865680 sectors, multi 0: LBA ata1.00: configured for UDMA/133 scsi 1:0:0:0: Direct-Access ATA TS2GMSA500 2010 PQ: 0 ANSI: 5 sd 1:0:0:0: Attached scsi generic sg1 type 0 sd 1:0:0:0: [sdb] 3865680 512-byte logical blocks: (1.97 GB/1.84 GiB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPOO or FUA sdb: sdb1 sdb2 sd 1:0:0:0: [sdb] Attached SCSI disk ata2: SATA link down (SStatus 0 SControl 300) ... Can you please let me know how I can add the missing modules to initrd? Thanks |
From: Martin G. <sou...@gl...> - 2012-02-27 15:49:52
|
Hi Serge, On 02/24/2012 11:34 PM, Serge Leschinsky wrote: > I assume you are in DL. > > cd /tmp/ > cp /boot/initrd.gz ./ > gzip -d initrd.gz > mkdir 123 > cd ./123 > cpio -id< ../initrd > mkdir lib/modules/3.2.4-grsec/kernel/drivers/pci > cp -ar /lib/modules/3.2.4-grsec/kernel/drivers/pci/hotplug > ./lib/modules/3.2.4-grsec/kernel/drivers/pci/ > find . | cpio -H newc -o | gzip -9> ../initrd.gz > > then replace old initrd.gz file on your boot media (/dev/sdb) by new one Thanks for the instructions, but even after replacing the initrd, I had no luck getting the mSATA drive recognised on boot. I also added pci_hotplug to the /etc/sysconfig/config INITRD parameter without success. Was there anything else I needed to do to get this recognised (if it was the hotplug module) or any other way of finding what module is required? Thanks Martin |
From: Serge L. <ser...@gm...> - 2012-02-27 18:51:20
|
Hi Martin, On 02/27/2012 07:49 AM, Martin Glazer wrote: > Thanks for the instructions, but even after replacing the initrd, I had no luck > getting the mSATA drive recognised on boot. > > I also added pci_hotplug to the /etc/sysconfig/config INITRD parameter without > success. > > Was there anything else I needed to do to get this recognised (if it was the > hotplug module) or any other way of finding what module is required? well, probably the hw was detected, but an appropriate device was not created. In initrd we don't use mdev - udev analog. Hmm.... Let's check udev events - edit /etc/init.d/boot and add "udevadm monitor" just after udevd launch. It's better to redirect output somewhere. syslog is not started yet. Serge |
From: Serge L. <ser...@gm...> - 2012-02-27 19:26:30
|
On 02/27/2012 10:51 AM, Serge Leschinsky wrote: > well, probably the hw was detected, but an appropriate device was not created. > In initrd we don't use mdev - udev analog. Hmm.... Let's check udev events - > edit /etc/init.d/boot and add "udevadm monitor" just after udevd launch. It's > better to redirect output somewhere. syslog is not started yet. please "udevadm monitor --env" to see all information Serge |
From: Serge L. <ser...@gm...> - 2012-02-25 06:34:52
|
On 02/24/2012 10:14 PM, Martin Glazer wrote: > I think it must be the hotplug modules that are missing > > this is my output from lsmod > root@Devil:~ # lsmod > Module Size Used by > ipv6 274019 12 > dm_mod 66521 0 > md_mod 100338 0 > i2c_isch 3124 0 > i2c_core 18870 1 i2c_isch > uas 8089 0 > ahci 19843 0 > libahci 19102 1 ahci > e1000e 138681 0 > libata 163311 2 ahci,libahci > pch_gbe 32970 0 > mii 3787 1 pch_gbe > pch_phub 6506 0 > lpc_sch 2464 0 > shpchp 25273 0 > pci_hotplug 22206 1 shpchp > cn 3905 0 > loop 67443 2 ... > Can you please let me know how I can add the missing modules to initrd? > I assume you are in DL. cd /tmp/ cp /boot/initrd.gz ./ gzip -d initrd.gz mkdir 123 cd ./123 cpio -id < ../initrd mkdir lib/modules/3.2.4-grsec/kernel/drivers/pci cp -ar /lib/modules/3.2.4-grsec/kernel/drivers/pci/hotplug ./lib/modules/3.2.4-grsec/kernel/drivers/pci/ find . | cpio -H newc -o | gzip -9 > ../initrd.gz then replace old initrd.gz file on your boot media (/dev/sdb) by new one Serge |
From: Heiko Z. <he...@zu...> - 2012-02-23 17:16:33
|
Quoting Dominic Raferd <dl...@ed...>: > 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? -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Martin G. <sou...@gl...> - 2012-02-24 02:21:18
|
On 02/23/2012 10:16 AM, Heiko Zuerker wrote: > Quoting Dominic Raferd<dl...@ed...>: > >> 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? |