* [gentoo-user] How does grub assemble a RAID1 for / ??
@ 2010-04-03 23:07 Mark Knecht
2010-04-03 23:37 ` Neil Bothwick
2010-04-03 23:45 ` [gentoo-user] " Albert Hopkins
0 siblings, 2 replies; 25+ messages in thread
From: Mark Knecht @ 2010-04-03 23:07 UTC (permalink / raw
To: gentoo-user
Hi,
I'm doing an install roughly following this guide:
http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml
Differences:
1) AMD64
2) A non-RAID Gentoo install already resides /dev/sda
3) I'm doing the RAID install on /dev/sdb3 & /dev/sdc3
4) RAID1 only
5) No LVM
6) Shared /boot & grub
7) grub not installed for the RAID installation as I am using the
non-raid grub to boot options
The install is complete but it won't boot. grub finds the kernel
and starts booting but then I get the typical VFS file sync error as
the kernel starts looking for the install on /dev/md3. What I'm not
understanding is how does the boot process get the information
required to assemble the RAID device. By hand in the non-RAID install
I do this:
keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3
mdadm: /dev/md3 has been started with 2 drives.
keeper ~ # cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sdb3[0] sdc3[1]
52436092 blocks super 1.1 [2/2] [UU]
unused devices: <none>
keeper ~ #
but when I try to boot the RAID install it says it cannot find /dev/md3.
From within the non-RAID install I can mount md3. It's got the RAID
install and I can chroot into it and continue doing install like
things so all the data is there but I cannot boot it.
I don't see what allows grub (I gruss) to start up mdadm, assemble
the device and then continue the boot. What am I missing?
grub.conf and fdisk info follows.
Thanks,
Mark
keeper ~ # cat /boot/grub/grub.conf
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title /dev/sda1 Gentoo Linux 2.6.33-gentoo
root (hd0,0)
kernel (hd0,0)/boot/bzImage-2.6.33-gentoo root=/dev/sda3
title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID
root (hd0,0)
kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md3
keeper ~ #
keeper ~ # fdisk -l /dev/sda /dev/sdb /dev/sdc
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1d23ae47
Device Boot Start End Blocks Id System
/dev/sda1 * 1 14 112423+ 83 Linux
/dev/sda2 16 538 4200997+ 82 Linux swap / Solaris
/dev/sda3 2048 5964 31463302+ 83 Linux
/dev/sda4 6000 121601 928573065 5 Extended
/dev/sda5 6000 19054 104864256 83 Linux
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa06ef201
Device Boot Start End Blocks Id System
/dev/sdb1 1 14 112423+ 83 Linux
/dev/sdb2 16 538 4200997+ 82 Linux swap / Solaris
/dev/sdb3 544 7071 52436160 fd Linux raid autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2ab15637
Device Boot Start End Blocks Id System
/dev/sdc1 1 14 112423+ 83 Linux
/dev/sdc2 16 538 4200997+ 82 Linux swap / Solaris
/dev/sdc3 544 7071 52436160 fd Linux raid autodetect
keeper ~ #
From the RAID1 fstab
/dev/sda1 /boot ext2 noauto,noatime 1 2
/dev/md3 / ext3 noatime 0 1
/dev/sda2 none swap sw 0 0
/dev/sdb2 none swap sw 0 0
/dev/sdc2 none swap sw 0 0
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [gentoo-user] How does grub assemble a RAID1 for / ?? 2010-04-03 23:07 [gentoo-user] How does grub assemble a RAID1 for / ?? Mark Knecht @ 2010-04-03 23:37 ` Neil Bothwick 2010-04-04 1:01 ` Mark Knecht 2010-04-03 23:45 ` [gentoo-user] " Albert Hopkins 1 sibling, 1 reply; 25+ messages in thread From: Neil Bothwick @ 2010-04-03 23:37 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 1055 bytes --] On Sat, 3 Apr 2010 16:07:06 -0700, Mark Knecht wrote: > The install is complete but it won't boot. grub finds the kernel > and starts booting but then I get the typical VFS file sync error as > the kernel starts looking for the install on /dev/md3. What I'm not > understanding is how does the boot process get the information > required to assemble the RAID device. By hand in the non-RAID install > I do this: > > keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 > mdadm: /dev/md3 has been started with 2 drives. > keeper ~ # cat /proc/mdstat > Personalities : [raid1] > md3 : active raid1 sdb3[0] sdc3[1] > 52436092 blocks super 1.1 [2/2] [UU] > > unused devices: <none> > keeper ~ # > > but when I try to boot the RAID install it says it cannot find /dev/md3. You need to set the partition type for the RAIDed partitions to "Linux raid autodetect". You'll probably then find that the kernel sets the RAID as /dev/md0, not md3. -- Neil Bothwick "You want us to do WHAT?" - Ancient Chinese wall engineer. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] How does grub assemble a RAID1 for / ?? 2010-04-03 23:37 ` Neil Bothwick @ 2010-04-04 1:01 ` Mark Knecht 2010-04-04 2:38 ` [gentoo-user] " Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 1:01 UTC (permalink / raw To: gentoo-user On Sat, Apr 3, 2010 at 4:37 PM, Neil Bothwick <neil@digimed.co.uk> wrote: > On Sat, 3 Apr 2010 16:07:06 -0700, Mark Knecht wrote: > >> The install is complete but it won't boot. grub finds the kernel >> and starts booting but then I get the typical VFS file sync error as >> the kernel starts looking for the install on /dev/md3. What I'm not >> understanding is how does the boot process get the information >> required to assemble the RAID device. By hand in the non-RAID install >> I do this: >> >> keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 >> mdadm: /dev/md3 has been started with 2 drives. >> keeper ~ # cat /proc/mdstat >> Personalities : [raid1] >> md3 : active raid1 sdb3[0] sdc3[1] >> 52436092 blocks super 1.1 [2/2] [UU] >> >> unused devices: <none> >> keeper ~ # >> >> but when I try to boot the RAID install it says it cannot find /dev/md3. > > You need to set the partition type for the RAIDed partitions to "Linux > raid autodetect". You'll probably then find that the kernel sets the RAID > as /dev/md0, not md3. > > > -- > Neil Bothwick Tried changing root=/dev/md0. No change. The actual failure message is the fairly standard VFS - Unable to mount root fs on unknown-block(9,0) I can control this using (for instance) title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md3 md=3,1,/dev/sdb3,/dev/sdc3 which changes the message to 'unknown-block(9,3)' Since the mknod command for md devices is always 9 1 or 9 3 those match up. Is this saying that the special file thing for 9,0 and 9,3 are missing at boot time? As I posted in the first post the partitions are marked as autodetect, but if it matters I did that late in the process after the RAID was built. keeper ~ # fdisk -l /dev/sdb /dev/sdc Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xa06ef201 Device Boot Start End Blocks Id System /dev/sdb1 1 14 112423+ 83 Linux /dev/sdb2 16 538 4200997+ 82 Linux swap / Solaris /dev/sdb3 544 7071 52436160 fd Linux raid autodetect Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x2ab15637 Device Boot Start End Blocks Id System /dev/sdc1 1 14 112423+ 83 Linux /dev/sdc2 16 538 4200997+ 82 Linux swap / Solaris /dev/sdc3 544 7071 52436160 fd Linux raid autodetect keeper ~ # Answering Albert - I did it with /dev/md3 because that's how the install guide did it: mknod /dev/md3 b 9 3 mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3 From fstab: /dev/md3 / ext3 noatime 0 1 From grub.conf: title Gentoo root (hd0,0) kernel /boot/kernel root=/dev/md3 Granted, my kernel line is a little different: root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md3 but I didn't make it up. I just followed the guide. I set the same RAID kernel options as shown in the guide but maybe there is some other requirement not shown in the guide but actually required? The CONFIG_RAID_ATTRS is not discussed for instance:: keeper / # cat /usr/src/linux/.config | grep RAID CONFIG_RAID_ATTRS=m # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_PMCRAID is not set CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y # CONFIG_MD_RAID10 is not set # CONFIG_MD_RAID456 is not set keeper / # Thanks! - Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 1:01 ` Mark Knecht @ 2010-04-04 2:38 ` Kerin Millar 2010-04-04 14:20 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 2:38 UTC (permalink / raw To: gentoo-user On 04/04/2010 02:01, Mark Knecht wrote: > Tried changing root=/dev/md0. No change. > > The actual failure message is the fairly standard > > VFS - Unable to mount root fs on unknown-block(9,0) [snip] > CONFIG_MD_RAID1=y That's all that needs to be enabled within the RAID section of the kernel. However, all the other options that would normally be required to boot must also be compiled in statically for things to work as expected (ATA/SCSI controller driver, filesystem of choice, CONFIG_BLK_DEV_SD and so forth). It seems that you may have overlooked something. However, it's impossible to determine whether that's the case based on the information presented thus far. I would suggest that you double-check your .config in full, or present it here for review, along with the output of lspci -nn. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 2:38 ` [gentoo-user] " Kerin Millar @ 2010-04-04 14:20 ` Mark Knecht 2010-04-04 17:32 ` Kerin Millar 2010-04-05 0:47 ` walt 0 siblings, 2 replies; 25+ messages in thread From: Mark Knecht @ 2010-04-04 14:20 UTC (permalink / raw To: gentoo-user On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millar <kerframil@gmail.com> wrote: > On 04/04/2010 02:01, Mark Knecht wrote: >> >> Tried changing root=/dev/md0. No change. >> >> The actual failure message is the fairly standard >> >> VFS - Unable to mount root fs on unknown-block(9,0) > > [snip] > >> CONFIG_MD_RAID1=y > > That's all that needs to be enabled within the RAID section of the kernel. > However, all the other options that would normally be required to boot must > also be compiled in statically for things to work as expected (ATA/SCSI > controller driver, filesystem of choice, CONFIG_BLK_DEV_SD and so forth). It > seems that you may have overlooked something. However, it's impossible to > determine whether that's the case based on the information presented thus > far. > > I would suggest that you double-check your .config in full, or present it > here for review, along with the output of lspci -nn. > > Cheers, > > --Kerin Hi Kerin, Happy for any help I can get. Instead of the whole .config file here's a diff. Remember that the machine already boots non-RAID from /dev/sda and I'm trying to build my first RAID boot on /dev/sdb & sdc. First, here's the RAID I would like to boot from: keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 mdadm: /dev/md3 has been started with 2 drives. keeper ~ # mdadm --detail /dev/md3 /dev/md3: Version : 1.01 Creation Time : Sat Apr 3 11:43:39 2010 Raid Level : raid1 Array Size : 52436092 (50.01 GiB 53.69 GB) Used Dev Size : 52436092 (50.01 GiB 53.69 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sun Apr 4 06:40:54 2010 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : keeper:3 (local to host keeper) UUID : 6dcf5ddb:c4a2d5ea:ba59df10:f5473502 Events : 3703 Number Major Minor RaidDevice State 0 8 19 0 active sync /dev/sdb3 1 8 35 1 active sync /dev/sdc3 keeper ~ # cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sdb3[0] sdc3[1] 52436092 blocks super 1.1 [2/2] [UU] unused devices: <none> keeper ~ # Here's the diff of the running kernel without RAID and the kernel I created while in the install chroot on the RAID device: keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config 4c4 < # Mon Mar 29 01:02:31 2010 --- > # Sun Apr 4 06:28:53 2010 893,912c893,906 < CONFIG_MD_LINEAR=m < CONFIG_MD_RAID0=m < CONFIG_MD_RAID1=m < CONFIG_MD_RAID10=m < CONFIG_MD_RAID456=m < # CONFIG_MULTICORE_RAID456 is not set < CONFIG_MD_RAID6_PQ=m < # CONFIG_ASYNC_RAID6_TEST is not set < CONFIG_MD_MULTIPATH=m < CONFIG_MD_FAULTY=m < CONFIG_BLK_DEV_DM=m < CONFIG_DM_DEBUG=y < CONFIG_DM_CRYPT=m < CONFIG_DM_SNAPSHOT=m < CONFIG_DM_MIRROR=m < # CONFIG_DM_LOG_USERSPACE is not set < CONFIG_DM_ZERO=m < CONFIG_DM_MULTIPATH=m < # CONFIG_DM_MULTIPATH_QL is not set < # CONFIG_DM_MULTIPATH_ST is not set --- > # CONFIG_MD_LINEAR is not set > CONFIG_MD_RAID0=y > CONFIG_MD_RAID1=y > # CONFIG_MD_RAID10 is not set > # CONFIG_MD_RAID456 is not set > # CONFIG_MD_MULTIPATH is not set > # CONFIG_MD_FAULTY is not set > CONFIG_BLK_DEV_DM=y > # CONFIG_DM_DEBUG is not set > # CONFIG_DM_CRYPT is not set > # CONFIG_DM_SNAPSHOT is not set > # CONFIG_DM_MIRROR is not set > # CONFIG_DM_ZERO is not set > # CONFIG_DM_MULTIPATH is not set 914,915c908,909 < CONFIG_DM_UEVENT=y < CONFIG_BLK_DEV_DM_BBR=m --- > # CONFIG_DM_UEVENT is not set > # CONFIG_BLK_DEV_DM_BBR is not set 2293,2298d2286 < CONFIG_XOR_BLOCKS=m < CONFIG_ASYNC_CORE=m < CONFIG_ASYNC_MEMCPY=m < CONFIG_ASYNC_XOR=m < CONFIG_ASYNC_PQ=m < CONFIG_ASYNC_RAID6_RECOV=m keeper ~ # One additional thing I thought of last night was some message that came up when I first built the RAID about the partitions having metadata and to be sure that the bootloader understands metadata. In the cool light of morning that seems fairly important. I am using grub-static on this machine. I assumed this would be OK but possibly it isn't? If rebuilding the RAID from scratch is important, or just makes things more straight forward, then don't hesitate to suggest it and I'll document the build step by step. This install isn't important. I'm just doing it to learn how to do RAID and most importantly to test the disk drives. I purchased other disk drives that aren't working with RAID at all so I wanted to test these a bit before I did anything real. The final install with be a 3 disk RAID1 but the 3rd drive hasn't arrived yet so none of this is critically important. Thanks! Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 14:20 ` Mark Knecht @ 2010-04-04 17:32 ` Kerin Millar 2010-04-04 17:50 ` Mark Knecht 2010-04-05 0:47 ` walt 1 sibling, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 17:32 UTC (permalink / raw To: gentoo-user On 04/04/2010 15:20, Mark Knecht wrote: > On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millar<kerframil@gmail.com> wrote: >> On 04/04/2010 02:01, Mark Knecht wrote: >>> >>> Tried changing root=/dev/md0. No change. >>> >>> The actual failure message is the fairly standard >>> >>> VFS - Unable to mount root fs on unknown-block(9,0) >> >> [snip] >> >>> CONFIG_MD_RAID1=y >> >> That's all that needs to be enabled within the RAID section of the kernel. >> However, all the other options that would normally be required to boot must >> also be compiled in statically for things to work as expected (ATA/SCSI >> controller driver, filesystem of choice, CONFIG_BLK_DEV_SD and so forth). It >> seems that you may have overlooked something. However, it's impossible to >> determine whether that's the case based on the information presented thus >> far. >> >> I would suggest that you double-check your .config in full, or present it >> here for review, along with the output of lspci -nn. >> >> Cheers, >> >> --Kerin > > Hi Kerin, > Happy for any help I can get. > > Instead of the whole .config file here's a diff. Remember that the > machine already boots non-RAID from /dev/sda and I'm trying to build > my first RAID boot on /dev/sdb& sdc. > No, really, the whole thing needs to be seen, along with the lspci data. It's very likely that this thread can be drawn to a close if you provide exactly what's being asked for :) > One additional thing I thought of last night was some message that > came up when I first built the RAID about the partitions having > metadata and to be sure that the bootloader understands metadata. In The bootloader does not enter into this. If the kernel is being loaded - which, by your own admission it is - the bootloader has done its job. What happens thereafter is entirely the responsibility of the kernel. Essentially, the subject of this thread is a misnomer and the issue lies with your kernel. As for the warning regarding metadata, it's applicable to legacy bootloaders which may not be able to fathom the presence of the md superblock data at the beginning of a block device that happens to be a member of a raid1 volume. As far as grub is concerned, this is a non-issue. Even if it were an issue, you wouldn't even get as far as being able to load the kernel in the first instance. Indeed, the bootloader itself would likely fail to initialise properly. > If rebuilding the RAID from scratch is important, or just makes > things more straight forward, then don't hesitate to suggest it and > I'll document the build step by step. This install isn't important. On the other hand, if you don't get to the point of understanding why the kernel isn't configured so as to be able to assemble the array on this occasion, a re-install isn't going to change that. Moreover, you won't be able to fix any such problem that may occur again unaided. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 17:32 ` Kerin Millar @ 2010-04-04 17:50 ` Mark Knecht 2010-04-04 18:13 ` Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 17:50 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 10:32 AM, Kerin Millar <kerframil@gmail.com> wrote: > On 04/04/2010 15:20, Mark Knecht wrote: >> >> On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millar<kerframil@gmail.com> wrote: >>> >>> On 04/04/2010 02:01, Mark Knecht wrote: >>>> >>>> Tried changing root=/dev/md0. No change. >>>> >>>> The actual failure message is the fairly standard >>>> >>>> VFS - Unable to mount root fs on unknown-block(9,0) >>> >>> [snip] >>> >>>> CONFIG_MD_RAID1=y >>> >>> That's all that needs to be enabled within the RAID section of the >>> kernel. >>> However, all the other options that would normally be required to boot >>> must >>> also be compiled in statically for things to work as expected (ATA/SCSI >>> controller driver, filesystem of choice, CONFIG_BLK_DEV_SD and so forth). >>> It >>> seems that you may have overlooked something. However, it's impossible to >>> determine whether that's the case based on the information presented thus >>> far. >>> >>> I would suggest that you double-check your .config in full, or present it >>> here for review, along with the output of lspci -nn. >>> >>> Cheers, >>> >>> --Kerin >> >> Hi Kerin, >> Happy for any help I can get. >> >> Instead of the whole .config file here's a diff. Remember that the >> machine already boots non-RAID from /dev/sda and I'm trying to build >> my first RAID boot on /dev/sdb& sdc. >> > > No, really, the whole thing needs to be seen, along with the lspci data. > It's very likely that this thread can be drawn to a close if you provide > exactly what's being asked for :) > >> One additional thing I thought of last night was some message that >> came up when I first built the RAID about the partitions having >> metadata and to be sure that the bootloader understands metadata. In > > The bootloader does not enter into this. If the kernel is being loaded - > which, by your own admission it is - the bootloader has done its job. What > happens thereafter is entirely the responsibility of the kernel. > > Essentially, the subject of this thread is a misnomer and the issue lies > with your kernel. > > As for the warning regarding metadata, it's applicable to legacy bootloaders > which may not be able to fathom the presence of the md superblock data at > the beginning of a block device that happens to be a member of a raid1 > volume. As far as grub is concerned, this is a non-issue. Even if it were an > issue, you wouldn't even get as far as being able to load the kernel in the > first instance. Indeed, the bootloader itself would likely fail to > initialise properly. > >> If rebuilding the RAID from scratch is important, or just makes >> things more straight forward, then don't hesitate to suggest it and >> I'll document the build step by step. This install isn't important. > > On the other hand, if you don't get to the point of understanding why the > kernel isn't configured so as to be able to assemble the array on this > occasion, a re-install isn't going to change that. Moreover, you won't be > able to fix any such problem that may occur again unaided. > > Cheers, > > --Kerin No problem supplying it. I did the rebuild this morning but forced metadata to Type 1.0. No change as you suggested there wouldn't be. OK, here's: 1) lspci to read & lspci -k to see drivers both from the non-RAID kernel 2) The RAID kernel config 3) At the very end a diff between the kernel config in this email and the running one without RAID. (I.e. - the changes I made to attempt to mount / which is on RAID.) Note that the Marvell SATA controller is for two external eSATA ports that have nothing attached at this time. It's the Intel controller that's in play here. Thanks, Mark keeper ~ # lspci 00:00.0 Host bridge: Intel Corporation X58 I/O Hub to ESI Port (rev 13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) 00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0 (rev 13) 00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0 (rev 13) 00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13) 00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) 00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) 00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13) 00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1 00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2 00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 02:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1) 06:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2) 07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) keeper ~ # keeper ~ # lspci -k 00:00.0 Host bridge: Intel Corporation X58 I/O Hub to ESI Port (rev 13) Subsystem: Intel Corporation Device 4f53 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13) Kernel driver in use: pcieport 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) Kernel driver in use: pcieport 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) Kernel driver in use: pcieport 00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0 (rev 13) 00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0 (rev 13) 00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13) 00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13) 00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13) 00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13) 00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection Subsystem: Intel Corporation Device 0000 Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller Subsystem: Intel Corporation Device 0022 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1 Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2 Kernel driver in use: pcieport 00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5 Kernel driver in use: pcieport 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 Subsystem: Intel Corporation Device 4f53 Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller Subsystem: Intel Corporation Device 4f53 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller Subsystem: Intel Corporation Device 4f53 Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller Subsystem: Intel Corporation Device 4f53 02:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9500 GT] (rev a1) Kernel driver in use: nvidia Kernel modules: nvidia 06:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2) Subsystem: Intel Corporation Device 4f53 Kernel driver in use: ahci 07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) Subsystem: Intel Corporation Device 4f53 Kernel modules: firewire-ohci keeper ~ # # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_STRIP_ASM_SYMS is not set # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y # CONFIG_SCHEDSTATS is not set # CONFIG_TIMER_STATS is not set # CONFIG_DEBUG_OBJECTS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_KMEMLEAK is not set CONFIG_DEBUG_PREEMPT=y # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set # CONFIG_DEBUG_MEMORY_INIT is not set # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y # CONFIG_FRAME_POINTER is not set # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_LATENCYTOP is not set # CONFIG_SYSCTL_SYSCALL_CHECK is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_TRACING_SUPPORT=y # CONFIG_FTRACE is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set CONFIG_HAVE_ARCH_KMEMCHECK=y # CONFIG_STRICT_DEVMEM is not set CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_CPA_DEBUG is not set # CONFIG_OPTIMIZE_INLINING is not set # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set # # Security options # # CONFIG_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_NETWORK is not set # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_TOMOYO is not set # CONFIG_IMA is not set # CONFIG_DEFAULT_SECURITY_SELINUX is not set # CONFIG_DEFAULT_SECURITY_SMACK is not set # CONFIG_DEFAULT_SECURITY_TOMOYO is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # CONFIG_CRYPTO_CBC=y # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m # # Hash modes # CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m # CONFIG_CRYPTO_VMAC is not set # # Digest # CONFIG_CRYPTO_CRC32C=y # CONFIG_CRYPTO_CRC32C_INTEL is not set # CONFIG_CRYPTO_GHASH is not set CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m # CONFIG_CRYPTO_AES_NI_INTEL is not set CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m # CONFIG_CRYPTO_SALSA20 is not set CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m # CONFIG_CRYPTO_ZLIB is not set # CONFIG_CRYPTO_LZO is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set CONFIG_CRYPTO_HW=y # CONFIG_CRYPTO_DEV_PADLOCK is not set # CONFIG_CRYPTO_DEV_HIFN_795X is not set CONFIG_HAVE_KVM=y CONFIG_VIRTUALIZATION=y # CONFIG_KVM is not set CONFIG_VIRTIO=m CONFIG_VIRTIO_RING=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y # CONFIG_CRC_T10DIF is not set CONFIG_CRC_ITU_T=y CONFIG_CRC32=y # CONFIG_CRC7 is not set CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_NLATTR=y keeper ~ # keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config 4c4 < # Mon Mar 29 01:02:31 2010 --- > # Sun Apr 4 09:56:49 2010 893,912c893,906 < CONFIG_MD_LINEAR=m < CONFIG_MD_RAID0=m < CONFIG_MD_RAID1=m < CONFIG_MD_RAID10=m < CONFIG_MD_RAID456=m < # CONFIG_MULTICORE_RAID456 is not set < CONFIG_MD_RAID6_PQ=m < # CONFIG_ASYNC_RAID6_TEST is not set < CONFIG_MD_MULTIPATH=m < CONFIG_MD_FAULTY=m < CONFIG_BLK_DEV_DM=m < CONFIG_DM_DEBUG=y < CONFIG_DM_CRYPT=m < CONFIG_DM_SNAPSHOT=m < CONFIG_DM_MIRROR=m < # CONFIG_DM_LOG_USERSPACE is not set < CONFIG_DM_ZERO=m < CONFIG_DM_MULTIPATH=m < # CONFIG_DM_MULTIPATH_QL is not set < # CONFIG_DM_MULTIPATH_ST is not set --- > # CONFIG_MD_LINEAR is not set > CONFIG_MD_RAID0=y > CONFIG_MD_RAID1=y > # CONFIG_MD_RAID10 is not set > # CONFIG_MD_RAID456 is not set > # CONFIG_MD_MULTIPATH is not set > # CONFIG_MD_FAULTY is not set > CONFIG_BLK_DEV_DM=y > # CONFIG_DM_DEBUG is not set > # CONFIG_DM_CRYPT is not set > # CONFIG_DM_SNAPSHOT is not set > # CONFIG_DM_MIRROR is not set > # CONFIG_DM_ZERO is not set > # CONFIG_DM_MULTIPATH is not set 914,915c908,909 < CONFIG_DM_UEVENT=y < CONFIG_BLK_DEV_DM_BBR=m --- > # CONFIG_DM_UEVENT is not set > # CONFIG_BLK_DEV_DM_BBR is not set 2293,2298d2286 < CONFIG_XOR_BLOCKS=m < CONFIG_ASYNC_CORE=m < CONFIG_ASYNC_MEMCPY=m < CONFIG_ASYNC_XOR=m < CONFIG_ASYNC_PQ=m < CONFIG_ASYNC_RAID6_RECOV=m keeper ~ # ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 17:50 ` Mark Knecht @ 2010-04-04 18:13 ` Kerin Millar 2010-04-04 18:43 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 18:13 UTC (permalink / raw To: gentoo-user On 04/04/2010 18:50, Mark Knecht wrote: [snip] > No problem supplying it. I did the rebuild this morning but forced > metadata to Type 1.0. No change as you suggested there wouldn't be. > > OK, here's: > > 1) lspci to read& lspci -k to see drivers both from the non-RAID kernel > 2) The RAID kernel config > 3) At the very end a diff between the kernel config in this email and > the running one without RAID. (I.e. - the changes I made to attempt to > mount / which is on RAID.) > > Note that the Marvell SATA controller is for two external eSATA ports > that have nothing attached at this time. It's the Intel controller > that's in play here. > > Thanks, > Mark [snip lspci data] OK. [snip kconfig data] Something isn't right here. This .config appears to be severely stunted. It's missing lots of options that should be defined (whether active or not). Indeed, a typical .config might easily exceed 2000 lines. It's also missing the comment at the top which describes the kernel version in use. Is this really the entire .config file that is currently residing within /mnt/gentoo/usr/src/linux, having mounted the root filesystem and that was used to build the kernel you're attempting to boot with? If so, it's broken and you should just delete it entirely and start anew with make menuconfig. If not, then please present the file in full (no diffs, no obfuscation please). Aside from all of that, notable options that are going to be required to boot in your case are: CONFIG_MD_RAID1 CONFIG_SATA_AHCI CONFIG_BLK_DEV_SD CONFIG_BLK_DEV_SR CONFIG_MSDOS_PARTITION (normally implicit but worth mentioning) That, and the option corresponding with whichever filesystem you use. Also, make sure CONFIG_SYSFS_DEPRECATED_V2 is off or else udev will balk. You may use the forward slash key to search for option names in make menuconfig (never edit .config directly). All needed options should be enabled as <*>. Also, if you're not experienced with kernel configuration and need a skeleton .config with which to begin, I would suggest you take a look at http://kernel-seeds.org. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 18:13 ` Kerin Millar @ 2010-04-04 18:43 ` Mark Knecht 2010-04-04 19:29 ` Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 18:43 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 11:13 AM, Kerin Millar <kerframil@gmail.com> wrote: > On 04/04/2010 18:50, Mark Knecht wrote: > > [snip] > >> No problem supplying it. I did the rebuild this morning but forced >> metadata to Type 1.0. No change as you suggested there wouldn't be. >> >> OK, here's: >> >> 1) lspci to read& lspci -k to see drivers both from the non-RAID kernel >> 2) The RAID kernel config >> 3) At the very end a diff between the kernel config in this email and >> the running one without RAID. (I.e. - the changes I made to attempt to >> mount / which is on RAID.) >> >> Note that the Marvell SATA controller is for two external eSATA ports >> that have nothing attached at this time. It's the Intel controller >> that's in play here. >> >> Thanks, >> Mark > > [snip lspci data] > > OK. > > [snip kconfig data] > > Something isn't right here. This .config appears to be severely stunted. > It's missing lots of options that should be defined (whether active or not). > Indeed, a typical .config might easily exceed 2000 lines. It's also missing > the comment at the top which describes the kernel version in use. > > Is this really the entire .config file that is currently residing within > /mnt/gentoo/usr/src/linux, having mounted the root filesystem and that was > used to build the kernel you're attempting to boot with? If so, it's broken > and you should just delete it entirely and start anew with make menuconfig. > If not, then please present the file in full (no diffs, no obfuscation > please). > > Aside from all of that, notable options that are going to be required to > boot in your case are: > > CONFIG_MD_RAID1 > CONFIG_SATA_AHCI > CONFIG_BLK_DEV_SD > CONFIG_BLK_DEV_SR > CONFIG_MSDOS_PARTITION (normally implicit but worth mentioning) > > That, and the option corresponding with whichever filesystem you use. Also, > make sure CONFIG_SYSFS_DEPRECATED_V2 is off or else udev will balk. You may > use the forward slash key to search for option names in make menuconfig > (never edit .config directly). All needed options should be enabled as <*>. > > Also, if you're not experienced with kernel configuration and need a > skeleton .config with which to begin, I would suggest you take a look at > http://kernel-seeds.org. > > Cheers, > > --Kerin Sorry. I was on a Windows box and it looks like putty cut it off. Booted into Linux and this looks more correct. (2424 lines in vi on that machine and 2424 lines in late on this machine so I think it's all there...) I looked at your suggestions above and they are all set to =y. CONFIG_SYSFS_DEPRECATED_V2 is 'not set'. - Mark # # Automatically generated make config: don't edit # Linux kernel version: 2.6.33-gentoo # Sun Apr 4 09:56:49 2010 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y # CONFIG_KTIME_SCALAR is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_LZO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # # CONFIG_TREE_RCU is not set CONFIG_TREE_PREEMPT_RCU=y # CONFIG_TINY_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=15 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set # CONFIG_SYSFS_DEPRECATED_V2 is not set # CONFIG_RELAY is not set # CONFIG_NAMESPACES is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_EMBEDDED=y # CONFIG_UID16 is not set CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_PERF_COUNTERS is not set # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_COMPAT_BRK=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y # # GCOV-based kernel profiling # CONFIG_SLOW_WORK=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y # CONFIG_BLK_DEV_INTEGRITY is not set CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # CONFIG_INLINE_SPIN_TRYLOCK is not set # CONFIG_INLINE_SPIN_TRYLOCK_BH is not set # CONFIG_INLINE_SPIN_LOCK is not set # CONFIG_INLINE_SPIN_LOCK_BH is not set # CONFIG_INLINE_SPIN_LOCK_IRQ is not set # CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set # CONFIG_INLINE_SPIN_UNLOCK is not set # CONFIG_INLINE_SPIN_UNLOCK_BH is not set # CONFIG_INLINE_SPIN_UNLOCK_IRQ is not set # CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_READ_TRYLOCK is not set # CONFIG_INLINE_READ_LOCK is not set # CONFIG_INLINE_READ_LOCK_BH is not set # CONFIG_INLINE_READ_LOCK_IRQ is not set # CONFIG_INLINE_READ_LOCK_IRQSAVE is not set # CONFIG_INLINE_READ_UNLOCK is not set # CONFIG_INLINE_READ_UNLOCK_BH is not set # CONFIG_INLINE_READ_UNLOCK_IRQ is not set # CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_WRITE_TRYLOCK is not set # CONFIG_INLINE_WRITE_LOCK is not set # CONFIG_INLINE_WRITE_LOCK_BH is not set # CONFIG_INLINE_WRITE_LOCK_IRQ is not set # CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set # CONFIG_INLINE_WRITE_UNLOCK is not set # CONFIG_INLINE_WRITE_UNLOCK_BH is not set # CONFIG_INLINE_WRITE_UNLOCK_IRQ is not set # CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set CONFIG_MUTEX_SPIN_ON_OWNER=y # CONFIG_FREEZER is not set # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y # CONFIG_SPARSE_IRQ is not set CONFIG_X86_MPPARSE=y # CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y CONFIG_SCHED_OMIT_FRAME_POINTER=y # CONFIG_PARAVIRT_GUEST is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set CONFIG_MCORE2=y # CONFIG_MATOM is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_P6_NOP=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y # CONFIG_PROCESSOR_SELECT is not set CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y # CONFIG_X86_DS is not set CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set # CONFIG_AMD_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y # CONFIG_IOMMU_API is not set # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=8 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y # CONFIG_X86_MCE_AMD is not set CONFIG_X86_MCE_THRESHOLD=y # CONFIG_X86_MCE_INJECT is not set CONFIG_X86_THERMAL_VECTOR=y # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_ARCH_PHYS_ADDR_T_64BIT=y # CONFIG_DIRECT_GBPAGES is not set # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set # CONFIG_DISCONTIGMEM_MANUAL is not set CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y # CONFIG_MEMORY_HOTPLUG is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y # CONFIG_KSM is not set CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y # CONFIG_MEMORY_FAILURE is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=y CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_EFI=y CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 # CONFIG_HOTPLUG_CPU is not set # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management and ACPI options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SUSPEND is not set # CONFIG_HIBERNATION is not set # CONFIG_PM_RUNTIME is not set CONFIG_ACPI=y # CONFIG_ACPI_PROCFS is not set # CONFIG_ACPI_PROCFS_POWER is not set # CONFIG_ACPI_POWER_METER is not set CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=m # CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set # CONFIG_ACPI_PCI_SLOT is not set # CONFIG_X86_PM_TIMER is not set CONFIG_ACPI_CONTAINER=m # CONFIG_ACPI_SBS is not set # CONFIG_SFI is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=m # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=m # CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_POWERNOW_K8=m CONFIG_X86_SPEEDSTEP_CENTRINO=m CONFIG_X86_P4_CLOCKMOD=m # # shared options # CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Memory power savings # # CONFIG_I7300_IDLE is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_DOMAINS=y CONFIG_PCIEPORTBUS=y CONFIG_PCIEAER=y # CONFIG_PCIE_ECRC is not set # CONFIG_PCIEAER_INJECT is not set # CONFIG_PCIEASPM is not set CONFIG_ARCH_SUPPORTS_MSI=y # CONFIG_PCI_MSI is not set CONFIG_PCI_LEGACY=y # CONFIG_PCI_DEBUG is not set # CONFIG_PCI_STUB is not set CONFIG_HT_IRQ=y # CONFIG_PCI_IOV is not set CONFIG_PCI_IOAPIC=y CONFIG_ISA_DMA_API=y CONFIG_K8_NB=y CONFIG_PCCARD=m CONFIG_PCMCIA=m CONFIG_PCMCIA_LOAD_CIS=y CONFIG_PCMCIA_IOCTL=y CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_YENTA_O2=y CONFIG_YENTA_RICOH=y CONFIG_YENTA_TI=y CONFIG_YENTA_ENE_TUNE=y CONFIG_YENTA_TOSHIBA=y CONFIG_PD6729=m CONFIG_I82092=m CONFIG_PCCARD_NONSTATIC=m # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set # CONFIG_HAVE_AOUT is not set # CONFIG_BINFMT_MISC is not set CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set CONFIG_INET_AH=m CONFIG_INET_ESP=m CONFIG_INET_IPCOMP=m CONFIG_INET_XFRM_TUNNEL=m CONFIG_INET_TUNNEL=m CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=y # CONFIG_INET_DIAG is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set CONFIG_IPV6=m # CONFIG_IPV6_PRIVACY is not set # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set # CONFIG_INET6_AH is not set # CONFIG_INET6_ESP is not set # CONFIG_INET6_IPCOMP is not set # CONFIG_IPV6_MIP6 is not set # CONFIG_INET6_XFRM_TUNNEL is not set # CONFIG_INET6_TUNNEL is not set CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m # CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=m # CONFIG_IPV6_SIT_6RD is not set CONFIG_IPV6_NDISC_NODETYPE=y # CONFIG_IPV6_TUNNEL is not set # CONFIG_IPV6_MULTIPLE_TABLES is not set # CONFIG_IPV6_MROUTE is not set # CONFIG_NETLABEL is not set # CONFIG_NETWORK_SECMARK is not set # CONFIG_NETFILTER is not set # CONFIG_IP_DCCP is not set CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_HMAC_NONE is not set # CONFIG_SCTP_HMAC_SHA1 is not set CONFIG_SCTP_HMAC_MD5=y # CONFIG_RDS is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=m # CONFIG_VLAN_8021Q_GVRP is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_PHONET is not set # CONFIG_IEEE802154 is not set # CONFIG_NET_SCHED is not set # CONFIG_DCB is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set # CONFIG_WIRELESS is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" # CONFIG_DEVTMPFS is not set CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=m CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set # CONFIG_CONNECTOR is not set # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_PNP=y # CONFIG_PNP_DEBUG_MESSAGES is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # # DRBD disabled because PROC_FS, INET or CONNECTOR not selected # # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=8192 # CONFIG_BLK_DEV_XIP is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set # CONFIG_VIRTIO_BLK is not set # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y # CONFIG_AD525X_DPOT is not set # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_ICS932S401 is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_CS5535_MFGPT is not set # CONFIG_HP_ILO is not set # CONFIG_ISL29003 is not set # CONFIG_DS1682 is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_AT24 is not set # CONFIG_EEPROM_LEGACY is not set # CONFIG_EEPROM_MAX6875 is not set # CONFIG_EEPROM_93CX6 is not set # CONFIG_CB710_CORE is not set CONFIG_HAVE_IDE=y CONFIG_IDE=y # # Please see Documentation/ide/ide.txt for help/info on IDE drives # CONFIG_IDE_XFER_MODE=y CONFIG_IDE_ATAPI=y # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_IDE_GD=y CONFIG_IDE_GD_ATA=y # CONFIG_IDE_GD_ATAPI is not set # CONFIG_BLK_DEV_IDECS is not set # CONFIG_BLK_DEV_DELKIN is not set CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y # CONFIG_BLK_DEV_IDETAPE is not set CONFIG_BLK_DEV_IDEACPI=y CONFIG_IDE_TASK_IOCTL=y CONFIG_IDE_PROC_FS=y # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_PLATFORM=y # CONFIG_BLK_DEV_CMD640 is not set CONFIG_BLK_DEV_IDEPNP=y CONFIG_BLK_DEV_IDEDMA_SFF=y # # PCI IDE chipsets support # CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_PCIBUS_ORDER is not set # CONFIG_BLK_DEV_GENERIC is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_JMICRON is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT8172 is not set # CONFIG_BLK_DEV_IT8213 is not set # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set # CONFIG_BLK_DEV_TC86C001 is not set CONFIG_BLK_DEV_IDEDMA=y # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=m CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=m CONFIG_CHR_DEV_SCH=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=m CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_FC_TGT_ATTRS=y CONFIG_SCSI_ISCSI_ATTRS=y CONFIG_SCSI_SAS_ATTRS=m CONFIG_SCSI_SAS_LIBSAS=m CONFIG_SCSI_SAS_ATA=y CONFIG_SCSI_SAS_HOST_SMP=y # CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_SRP_TGT_ATTRS=y CONFIG_SCSI_LOWLEVEL=y # CONFIG_ISCSI_TCP is not set # CONFIG_SCSI_BNX2_ISCSI is not set # CONFIG_BE2ISCSI is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_HPSA is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_3W_SAS is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_MVSAS is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_MPT2SAS is not set # CONFIG_SCSI_HPTIOP is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_VMWARE_PVSCSI is not set # CONFIG_LIBFC is not set # CONFIG_LIBFCOE is not set # CONFIG_FCOE is not set # CONFIG_FCOE_FNIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_PMCRAID is not set # CONFIG_SCSI_PM8001 is not set # CONFIG_SCSI_SRP is not set # CONFIG_SCSI_BFA_FC is not set CONFIG_SCSI_LOWLEVEL_PCMCIA=y CONFIG_PCMCIA_FDOMAIN=m CONFIG_PCMCIA_QLOGIC=m CONFIG_PCMCIA_SYM53C500=m # CONFIG_SCSI_DH is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_VERBOSE_ERROR=y CONFIG_ATA_ACPI=y # CONFIG_SATA_PMP is not set CONFIG_SATA_AHCI=y # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ACPI is not set # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATP867X is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set CONFIG_ATA_GENERIC=y # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set CONFIG_PATA_MPIIX=y # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PCMCIA is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RDC is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_TOSHIBA is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_PLATFORM is not set # CONFIG_PATA_SCH is not set CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y # CONFIG_MD_LINEAR is not set CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y # CONFIG_MD_RAID10 is not set # CONFIG_MD_RAID456 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set # CONFIG_DM_CRYPT is not set # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_DM_DELAY is not set # CONFIG_DM_UEVENT is not set # CONFIG_BLK_DEV_DM_BBR is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # You can enable one or both FireWire driver stacks. # # # The newer stack is recommended. # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_OHCI_DEBUG=y CONFIG_FIREWIRE_SBP2=m # CONFIG_FIREWIRE_NET is not set # CONFIG_IEEE1394 is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set CONFIG_BONDING=m # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_VETH is not set # CONFIG_NET_SB1000 is not set # CONFIG_ARCNET is not set CONFIG_PHYLIB=m # # MII PHY device drivers # # CONFIG_MARVELL_PHY is not set # CONFIG_DAVICOM_PHY is not set # CONFIG_QSEMI_PHY is not set CONFIG_LXT_PHY=m # CONFIG_CICADA_PHY is not set # CONFIG_VITESSE_PHY is not set # CONFIG_SMSC_PHY is not set # CONFIG_BROADCOM_PHY is not set # CONFIG_ICPLUS_PHY is not set # CONFIG_REALTEK_PHY is not set # CONFIG_NATIONAL_PHY is not set # CONFIG_STE10XP is not set # CONFIG_LSI_ET1011C_PHY is not set CONFIG_MDIO_BITBANG=m CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_CASSINI is not set CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m CONFIG_TYPHOON=m # CONFIG_ETHOC is not set # CONFIG_DNET is not set CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_DE2104X_DSL=0 CONFIG_TULIP=m CONFIG_TULIP_MWI=y CONFIG_TULIP_MMIO=y CONFIG_TULIP_NAPI=y CONFIG_TULIP_NAPI_HW_MITIGATION=y CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_ULI526X=m CONFIG_PCMCIA_XIRCOM=m # CONFIG_HP100 is not set # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set CONFIG_E100=m # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_R6040 is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SMSC9420 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_KS8842 is not set # CONFIG_KS8851_MLL is not set # CONFIG_VIA_RHINE is not set # CONFIG_SC92031 is not set # CONFIG_ATL2 is not set CONFIG_NETDEV_1000=y CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set # CONFIG_DL2K is not set CONFIG_E1000=m CONFIG_E1000E=m # CONFIG_IP1000 is not set CONFIG_IGB=m CONFIG_IGB_DCA=y CONFIG_IGBVF=m # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SIS190 is not set # CONFIG_SKGE is not set # CONFIG_SKY2 is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # CONFIG_CNIC is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # CONFIG_ATL1E is not set # CONFIG_ATL1C is not set # CONFIG_JME is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # CONFIG_WLAN is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set # CONFIG_NET_PCMCIA is not set CONFIG_WAN=y # CONFIG_HDLC is not set # CONFIG_DLCI is not set # CONFIG_SBNI is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOL2TP=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLHC=m CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y # CONFIG_NET_FC is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set CONFIG_VIRTIO_NET=m CONFIG_VMXNET3=m # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set CONFIG_INPUT_POLLDEV=m # CONFIG_INPUT_SPARSEKMAP is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ADP5588 is not set CONFIG_KEYBOARD_ATKBD=y # CONFIG_QT2160 is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_LM8323 is not set # CONFIG_KEYBOARD_MAX7359 is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_OPENCORES is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_XTKBD is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_SENTELIC is not set CONFIG_MOUSE_PS2_TOUCHKIT=y CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_MOUSE_SYNAPTICS_I2C is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m CONFIG_SERIO_CT82C710=m CONFIG_SERIO_PCIPS2=m CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_SERIO_ALTERA_PS2 is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set CONFIG_DEVKMEM=y # CONFIG_SERIAL_NONSTANDARD is not set CONFIG_NOZOMI=m # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_CS=m CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y # CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set # CONFIG_LEGACY_PTYS is not set # CONFIG_VIRTIO_CONSOLE is not set CONFIG_IPMI_HANDLER=m CONFIG_IPMI_PANIC_EVENT=y CONFIG_IPMI_PANIC_STRING=y CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y # CONFIG_HW_RANDOM_TIMERIOMEM is not set CONFIG_HW_RANDOM_INTEL=y # CONFIG_HW_RANDOM_AMD is not set # CONFIG_HW_RANDOM_VIA is not set # CONFIG_HW_RANDOM_VIRTIO is not set CONFIG_NVRAM=m # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # PCMCIA character devices # # CONFIG_SYNCLINK_CS is not set # CONFIG_CARDMAN_4000 is not set # CONFIG_CARDMAN_4040 is not set # CONFIG_IPWIRELESS is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set # CONFIG_HANGCHECK_TIMER is not set # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y # CONFIG_I2C_CHARDEV is not set CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_ALGOBIT=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_ISCH is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # # ACPI drivers # # CONFIG_I2C_SCMI is not set # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_OCORES is not set # CONFIG_I2C_SIMTEC is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_STUB is not set # # Miscellaneous I2C Chip support # # CONFIG_SENSORS_TSL2550 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # CONFIG_SPI is not set # # PPS support # # CONFIG_PPS is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_BATTERY_DS2760 is not set # CONFIG_BATTERY_DS2782 is not set CONFIG_BATTERY_BQ27x00=m # CONFIG_BATTERY_MAX17040 is not set CONFIG_HWMON=m # CONFIG_HWMON_VID is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_K8TEMP is not set # CONFIG_SENSORS_K10TEMP is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_G760A is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set # CONFIG_SENSORS_IBMAEM is not set # CONFIG_SENSORS_IBMPEX is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM73 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4215 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_LM95241 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_AMC6821 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_TMP401 is not set # CONFIG_SENSORS_TMP421 is not set # CONFIG_SENSORS_VIA_CPUTEMP is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set CONFIG_SENSORS_HDAPS=m # CONFIG_SENSORS_LIS3_I2C is not set CONFIG_SENSORS_APPLESMC=m # # ACPI drivers # # CONFIG_SENSORS_ATK0110 is not set # CONFIG_SENSORS_LIS3LV02D is not set CONFIG_THERMAL=y # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y # CONFIG_SSB_B43_PCI_BRIDGE is not set CONFIG_SSB_PCMCIAHOST_POSSIBLE=y CONFIG_SSB_PCMCIAHOST=y # CONFIG_SSB_SILENT is not set # CONFIG_SSB_DEBUG is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_MFD_TMIO is not set # CONFIG_PMIC_DA903X is not set # CONFIG_PMIC_ADP5520 is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM831X is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_AB3100_CORE is not set # CONFIG_MFD_88PM8607 is not set # CONFIG_REGULATOR is not set # CONFIG_MEDIA_SUPPORT is not set # # Graphics support # CONFIG_AGP=m # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=m # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set # CONFIG_VGA_ARB is not set CONFIG_DRM=m CONFIG_DRM_KMS_HELPER=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set # CONFIG_DRM_I830 is not set CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=m CONFIG_FB_CFB_COPYAREA=m CONFIG_FB_CFB_IMAGEBLIT=m # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set # CONFIG_FB_EFI is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set CONFIG_BACKLIGHT_CLASS_DEVICE=m # CONFIG_BACKLIGHT_GENERIC is not set # CONFIG_BACKLIGHT_PROGEAR is not set # CONFIG_BACKLIGHT_MBP_NVIDIA is not set # CONFIG_BACKLIGHT_SAHARA is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64 CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_FB_CON_DECOR is not set # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_LOGO is not set CONFIG_SOUND=m # CONFIG_SOUND_OSS_CORE is not set CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m # CONFIG_SND_SEQUENCER is not set # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set # CONFIG_SND_HRTIMER is not set # CONFIG_SND_DYNAMIC_MINORS is not set CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_DMA_SGBUF=y # CONFIG_SND_RAWMIDI_SEQ is not set # CONFIG_SND_OPL3_LIB_SEQ is not set # CONFIG_SND_OPL4_LIB_SEQ is not set # CONFIG_SND_SBAWE_SEQ is not set # CONFIG_SND_EMU10K1_SEQ is not set CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y # CONFIG_SND_PCSP is not set # CONFIG_SND_DUMMY is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # CONFIG_SND_AC97_POWER_SAVE is not set CONFIG_SND_PCI=y # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AW2 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_OXYGEN is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 is not set # CONFIG_SND_CS5535AUDIO is not set # CONFIG_SND_CTXFI is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_INDIGOIOX is not set # CONFIG_SND_INDIGODJX is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_ENS1370 is not set CONFIG_SND_ENS1371=m # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_FM801 is not set CONFIG_SND_HDA_INTEL=m # CONFIG_SND_HDA_HWDEP is not set # CONFIG_SND_HDA_INPUT_BEEP is not set # CONFIG_SND_HDA_INPUT_JACK is not set # CONFIG_SND_HDA_PATCH_LOADER is not set CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y CONFIG_SND_HDA_CODEC_ATIHDMI=y CONFIG_SND_HDA_CODEC_NVHDMI=y CONFIG_SND_HDA_CODEC_INTELHDMI=y CONFIG_SND_HDA_ELD=y CONFIG_SND_HDA_CODEC_CIRRUS=y CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CA0110=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y # CONFIG_SND_HDA_POWER_SAVE is not set CONFIG_SND_HDSP=m # CONFIG_SND_HDSPM is not set # CONFIG_SND_HIFIER is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set # CONFIG_SND_INTEL8X0 is not set # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_LX6464ES is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set CONFIG_SND_RME9652=m # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VIRTUOSO is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m # CONFIG_SND_USB_USX2Y is not set # CONFIG_SND_USB_CAIAQ is not set # CONFIG_SND_USB_US122L is not set CONFIG_SND_PCMCIA=y # CONFIG_SND_VXPOCKET is not set # CONFIG_SND_PDAUDIOCF is not set # CONFIG_SND_SOC is not set # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=y CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=m # CONFIG_HID_PID is not set CONFIG_USB_HIDDEV=y # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE is not set # # Special HID drivers # CONFIG_HID_A4TECH=m CONFIG_HID_APPLE=m CONFIG_HID_BELKIN=m CONFIG_HID_CHERRY=m CONFIG_HID_CHICONY=m CONFIG_HID_CYPRESS=m # CONFIG_HID_DRAGONRISE is not set CONFIG_HID_EZKEY=m # CONFIG_HID_KYE is not set CONFIG_HID_GYRATION=m # CONFIG_HID_TWINHAN is not set # CONFIG_HID_KENSINGTON is not set CONFIG_HID_LOGITECH=m # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_HID_MICROSOFT=m CONFIG_HID_MONTEREY=m # CONFIG_HID_NTRIG is not set CONFIG_HID_PANTHERLORD=m # CONFIG_PANTHERLORD_FF is not set CONFIG_HID_PETALYNX=m CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m CONFIG_HID_SUNPLUS=m # CONFIG_HID_GREENASIA is not set # CONFIG_HID_SMARTJOYPLUS is not set # CONFIG_HID_TOPSEED is not set # CONFIG_HID_THRUSTMASTER is not set # CONFIG_HID_ZEROPLUS is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=m # CONFIG_USB_DEBUG is not set CONFIG_USB_ANNOUNCE_NEW_DEVICES=y # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # CONFIG_USB_OTG_WHITELIST is not set # CONFIG_USB_OTG_BLACKLIST_HUB is not set # CONFIG_USB_MON is not set # CONFIG_USB_WUSB is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set # CONFIG_USB_XHCI_HCD is not set CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_OXU210HP_HCD is not set CONFIG_USB_ISP116X_HCD=m # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_ISP1362_HCD is not set CONFIG_USB_OHCI_HCD=m # CONFIG_USB_OHCI_HCD_SSB is not set # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=m CONFIG_USB_U132_HCD=m CONFIG_USB_SL811_HCD=m CONFIG_USB_SL811_CS=m CONFIG_USB_R8A66597_HCD=m # CONFIG_USB_WHCI_HCD is not set # CONFIG_USB_HWA_HCD is not set # # Enable Host or Gadget support to see Inventra options # # # USB Device Class drivers # CONFIG_USB_ACM=m # CONFIG_USB_PRINTER is not set # CONFIG_USB_WDM is not set # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m CONFIG_USB_STORAGE_DEBUG=y CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m # CONFIG_USB_STORAGE_ONETOUCH is not set CONFIG_USB_STORAGE_KARMA=m # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB port drivers # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_BERRY_CHARGE is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_IDMOUSE is not set CONFIG_USB_FTDI_ELAN=m # CONFIG_USB_APPLEDISPLAY is not set CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_VST is not set # CONFIG_USB_GADGET is not set # # OTG and related infrastructure # # CONFIG_NOP_USB_XCEIV is not set # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=m # # LED drivers # # CONFIG_LEDS_ALIX2 is not set # CONFIG_LEDS_PCA9532 is not set # CONFIG_LEDS_LP3944 is not set # CONFIG_LEDS_CLEVO_MAIL is not set # CONFIG_LEDS_PCA955X is not set # CONFIG_LEDS_BD2802 is not set # CONFIG_LEDS_INTEL_SS4200 is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y # CONFIG_LEDS_TRIGGER_TIMER is not set # CONFIG_LEDS_TRIGGER_IDE_DISK is not set # CONFIG_LEDS_TRIGGER_HEARTBEAT is not set # CONFIG_LEDS_TRIGGER_BACKLIGHT is not set # CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set # # iptables trigger is under Netfilter config (LED target) # # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set CONFIG_RTC_LIB=m CONFIG_RTC_CLASS=m # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_DS1307 is not set # CONFIG_RTC_DRV_DS1374 is not set # CONFIG_RTC_DRV_DS1672 is not set # CONFIG_RTC_DRV_MAX6900 is not set # CONFIG_RTC_DRV_RS5C372 is not set # CONFIG_RTC_DRV_ISL1208 is not set # CONFIG_RTC_DRV_X1205 is not set # CONFIG_RTC_DRV_PCF8563 is not set # CONFIG_RTC_DRV_PCF8583 is not set # CONFIG_RTC_DRV_M41T80 is not set # CONFIG_RTC_DRV_BQ32K is not set # CONFIG_RTC_DRV_S35390A is not set # CONFIG_RTC_DRV_FM3130 is not set # CONFIG_RTC_DRV_RX8581 is not set # CONFIG_RTC_DRV_RX8025 is not set # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=m # CONFIG_RTC_DRV_DS1286 is not set # CONFIG_RTC_DRV_DS1511 is not set # CONFIG_RTC_DRV_DS1553 is not set # CONFIG_RTC_DRV_DS1742 is not set # CONFIG_RTC_DRV_STK17TA8 is not set # CONFIG_RTC_DRV_M48T86 is not set # CONFIG_RTC_DRV_M48T35 is not set # CONFIG_RTC_DRV_M48T59 is not set # CONFIG_RTC_DRV_MSM6242 is not set # CONFIG_RTC_DRV_BQ4802 is not set # CONFIG_RTC_DRV_RP5C01 is not set # CONFIG_RTC_DRV_V3020 is not set # # on-CPU RTC drivers # CONFIG_DMADEVICES=y # # DMA Devices # CONFIG_ASYNC_TX_DISABLE_CHANNEL_SWITCH=y CONFIG_INTEL_IOATDMA=y CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y # CONFIG_ASYNC_TX_DMA is not set # CONFIG_DMATEST is not set CONFIG_DCA=y # CONFIG_AUXDISPLAY is not set CONFIG_UIO=m # CONFIG_UIO_CIF is not set # CONFIG_UIO_PDRV is not set # CONFIG_UIO_PDRV_GENIRQ is not set # CONFIG_UIO_SMX is not set # CONFIG_UIO_AEC is not set # CONFIG_UIO_SERCOS3 is not set # CONFIG_UIO_PCI_GENERIC is not set # # TI VLYNQ # # CONFIG_STAGING is not set # CONFIG_X86_PLATFORM_DEVICES is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y CONFIG_EFI_VARS=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y # CONFIG_ISCSI_IBFT_FIND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y CONFIG_JBD2=y CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set # CONFIG_NILFS2_FS is not set CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_QUOTA=y # CONFIG_QUOTA_NETLINK_INTERFACE is not set CONFIG_PRINT_QUOTA_WARNING=y # CONFIG_QFMT_V1 is not set # CONFIG_QFMT_V2 is not set CONFIG_QUOTACTL=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set CONFIG_FUSE_FS=m # CONFIG_CUSE is not set CONFIG_GENERIC_ACL=y # # Caches # # CONFIG_FSCACHE is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=y CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=y # CONFIG_NTFS_DEBUG is not set CONFIG_NTFS_RW=y # # Pseudo filesystems # CONFIG_PROC_FS=y # CONFIG_PROC_KCORE is not set CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_CONFIGFS_FS=m CONFIG_MISC_FILESYSTEMS=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set CONFIG_HFS_FS=y CONFIG_HFSPLUS_FS=y # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set CONFIG_SQUASHFS=y # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 # CONFIG_VXFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_OMFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set CONFIG_ROOT_NFS=y # CONFIG_NFSD is not set CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y CONFIG_RPCSEC_GSS_SPKM3=m # CONFIG_SMB_FS is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_WEAK_PW_HASH is not set CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set # CONFIG_CIFS_EXPERIMENTAL is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y # CONFIG_MINIX_SUBPARTITION is not set CONFIG_SOLARIS_X86_PARTITION=y # CONFIG_UNIXWARE_DISKLABEL is not set CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_PARTITION is not set CONFIG_EFI_PARTITION=y # CONFIG_SYSV68_PARTITION is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m CONFIG_NLS_ISO8859_1=y CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=y CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=y CONFIG_DLM=m # CONFIG_DLM_DEBUG is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_STRIP_ASM_SYMS is not set # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y # CONFIG_SCHEDSTATS is not set # CONFIG_TIMER_STATS is not set # CONFIG_DEBUG_OBJECTS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_KMEMLEAK is not set CONFIG_DEBUG_PREEMPT=y # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set # CONFIG_DEBUG_MEMORY_INIT is not set # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y # CONFIG_FRAME_POINTER is not set # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_LATENCYTOP is not set # CONFIG_SYSCTL_SYSCALL_CHECK is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_TRACING_SUPPORT=y # CONFIG_FTRACE is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set CONFIG_HAVE_ARCH_KMEMCHECK=y # CONFIG_STRICT_DEVMEM is not set CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_CPA_DEBUG is not set # CONFIG_OPTIMIZE_INLINING is not set # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set # # Security options # # CONFIG_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_NETWORK is not set # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_TOMOYO is not set # CONFIG_IMA is not set # CONFIG_DEFAULT_SECURITY_SELINUX is not set # CONFIG_DEFAULT_SECURITY_SMACK is not set # CONFIG_DEFAULT_SECURITY_TOMOYO is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # CONFIG_CRYPTO_CBC=y # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m # # Hash modes # CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m # CONFIG_CRYPTO_VMAC is not set # # Digest # CONFIG_CRYPTO_CRC32C=y # CONFIG_CRYPTO_CRC32C_INTEL is not set # CONFIG_CRYPTO_GHASH is not set CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m # CONFIG_CRYPTO_AES_NI_INTEL is not set CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m # CONFIG_CRYPTO_SALSA20 is not set CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m # CONFIG_CRYPTO_ZLIB is not set # CONFIG_CRYPTO_LZO is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set CONFIG_CRYPTO_HW=y # CONFIG_CRYPTO_DEV_PADLOCK is not set # CONFIG_CRYPTO_DEV_HIFN_795X is not set CONFIG_HAVE_KVM=y CONFIG_VIRTUALIZATION=y # CONFIG_KVM is not set CONFIG_VIRTIO=m CONFIG_VIRTIO_RING=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y # CONFIG_CRC_T10DIF is not set CONFIG_CRC_ITU_T=y CONFIG_CRC32=y # CONFIG_CRC7 is not set CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_NLATTR=y ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 18:43 ` Mark Knecht @ 2010-04-04 19:29 ` Kerin Millar 2010-04-04 19:52 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 19:29 UTC (permalink / raw To: gentoo-user On 04/04/2010 19:43, Mark Knecht wrote: [snip] >> Aside from all of that, notable options that are going to be required to >> boot in your case are: >> >> CONFIG_MD_RAID1 >> CONFIG_SATA_AHCI >> CONFIG_BLK_DEV_SD >> CONFIG_BLK_DEV_SR >> CONFIG_MSDOS_PARTITION (normally implicit but worth mentioning) >> >> That, and the option corresponding with whichever filesystem you use. Also, >> make sure CONFIG_SYSFS_DEPRECATED_V2 is off or else udev will balk. You may >> use the forward slash key to search for option names in make menuconfig >> (never edit .config directly). All needed options should be enabled as<*>. >> >> Also, if you're not experienced with kernel configuration and need a >> skeleton .config with which to begin, I would suggest you take a look at >> http://kernel-seeds.org. >> >> Cheers, >> >> --Kerin > > Sorry. I was on a Windows box and it looks like putty cut it off. > Booted into Linux and this looks more correct. (2424 lines in vi on > that machine and 2424 lines in late on this machine so I think it's > all there...) > > I looked at your suggestions above and they are all set to =y. > CONFIG_SYSFS_DEPRECATED_V2 is 'not set'. > > - Mark > > # > # Automatically generated make config: don't edit > # Linux kernel version: 2.6.33-gentoo > # Sun Apr 4 09:56:49 2010 > # [snip long config] Ah, that looks better. Not that I've pored over every line, but at first glance everything seems to be in order. There are no obvious gotchas that I can see, so I'm somewhat puzzled. Here are a few random things that spring to mind though ... I would suggest switching off CONFIG_IDE. It may contend for control of your hardware with the AHCI driver, assuming that emulation/comptability mode is enabled in the BIOS. The device nodes may be unavailable at the time that they are needed, for some strange reason. If you mount the root filesystem from a livecd (with no bind mounts), try creating static nodes in dev/: mknod /dev/md0 b 9 0 mknod /dev/md1 b 9 1 mknod /dev/md2 b 9 2 mknod /dev/md3 b 9 3 Note that the preferred minor of your array can be determined by examining any component partition. For instance, "mdadm -E /dev/sdb3". Avoid manual specification of the RAID parameters. The kernel should be perfectly able to assemble the array by examining the superblocks of partitions of type "FD". Does it work if you specify "root=/dev/sdb3" or "root=/dev/sdc3"? With raid1, it's possible to mount just the component partition (although it will later result in a resync). The point is, it would at least confirm as to whether the underlying block devices are available to the kernel from the outset. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 19:29 ` Kerin Millar @ 2010-04-04 19:52 ` Mark Knecht 2010-04-04 20:06 ` Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 19:52 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 12:29 PM, Kerin Millar <kerframil@gmail.com> wrote: <SNIP> > > Ah, that looks better. Not that I've pored over every line, but at first > glance everything seems to be in order. There are no obvious gotchas that I > can see, so I'm somewhat puzzled. As am I! > > Here are a few random things that spring to mind though ... > > I would suggest switching off CONFIG_IDE. It may contend for control of your > hardware with the AHCI driver, assuming that emulation/comptability mode is > enabled in the BIOS. > > The device nodes may be unavailable at the time that they are needed, for > some strange reason. If you mount the root filesystem from a livecd (with no > bind mounts), try creating static nodes in dev/: > > mknod /dev/md0 b 9 0 > mknod /dev/md1 b 9 1 > mknod /dev/md2 b 9 2 > mknod /dev/md3 b 9 3 So this suggests that because I did the install from a running Gentoo chroot that the mknod commands didn't stick? Somehow they were part of, or because part of, the host Gentoo non-RAID install? Interesting. I'll boot next ffrom the Live CD and try it. > > Note that the preferred minor of your array can be determined by examining > any component partition. For instance, "mdadm -E /dev/sdb3". That's what I thought from the install guide but it seemed others here had other opions. > > Avoid manual specification of the RAID parameters. The kernel should be > perfectly able to assemble the array by examining the superblocks of > partitions of type "FD". > > Does it work if you specify "root=/dev/sdb3" or "root=/dev/sdc3"? With > raid1, it's possible to mount just the component partition (although it will > later result in a resync). The point is, it would at least confirm as to > whether the underlying block devices are available to the kernel from the > outset. OK, this was interesting, and I suppose it depends on what you mean 'should work'. Clearly it gets much further, into the interactive portion of the boot with the green asterics on the right. When it finally gets to the md0 portion it says the the superblock does not correctly specify an ext2 filesystem and asks for a password or Control D. Control D reboots and entering the password results in a (none) prompt and seems to require a hard reset. None the less it got much further, but not to a usable state. Off to do the Live CD work. Back in 30 minutes. Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 19:52 ` Mark Knecht @ 2010-04-04 20:06 ` Kerin Millar 2010-04-04 22:16 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 20:06 UTC (permalink / raw To: gentoo-user On 04/04/2010 20:52, Mark Knecht wrote: > So this suggests that because I did the install from a running Gentoo > chroot that the mknod commands didn't stick? Somehow they were part > of, or because part of, the host Gentoo non-RAID install? Interesting. I don't know what the handbook says these days, but I understand that it's lately taken to recommending a bind mount of /dev. If that's the case, then none of the static device nodes that are contained with the /dev directory within the stage3 tarball will actually make it on to the root filesystem because, at the time of unpacking, they will be redirected to the (volatile) tmpfs mount at /dev with respect to the livecd environment. From the point of view of the problem you're having, it may not even matter but it's one thing to try anyway. It's interesting that the component disks are available. In principle, there's no reason why the array should not be assembled. Here's an example of how it looks during the boot process on one of my systems: Command line: root=/dev/md2 Kernel command line: root=/dev/md2 quiet ata1: SATA max UDMA/133 cmd 0xcc30 ctl 0xcc28 bmdma 0xcc40 irq 23 ata2: SATA max UDMA/133 cmd 0xcc38 ctl 0xcc2c bmdma 0xcc48 irq 23 md: raid1 personality registered for level 1 md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 6 and added 6 devices. md: autorun ... md: considering sdb3 ... md: adding sdb3 ... md: sdb2 has different UUID to sdb3 md: sdb1 has different UUID to sdb3 md: adding sda3 ... md: sda2 has different UUID to sdb3 md: sda1 has different UUID to sdb3 md: created md2 md: bind<sda3> md: bind<sdb3> md: running: <sdb3><sda3> md: kicking non-fresh sdb3 from array! md: unbind<sdb3> md: export_rdev(sdb3) raid1: raid set md2 active with 1 out of 2 mirrors md2: detected capacity change from 0 to 248798183424 md: considering sdb2 ... md: adding sdb2 ... md: sdb1 has different UUID to sdb2 md: adding sda2 ... md: sda1 has different UUID to sdb2 md: created md1 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> md: kicking non-fresh sdb2 from array! md: unbind<sdb2> md: export_rdev(sdb2) raid1: raid set md1 active with 1 out of 2 mirrors md1: detected capacity change from 0 to 1085669376 md: considering sdb1 ... md: adding sdb1 ... md: adding sda1 ... md: created md0 You might consider disabling the framebuffer temporarily, as it may impact upon your ability to see what's going on early during the boot process. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 20:06 ` Kerin Millar @ 2010-04-04 22:16 ` Mark Knecht 2010-04-04 22:47 ` Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 22:16 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 1:06 PM, Kerin Millar <kerframil@gmail.com> wrote: > On 04/04/2010 20:52, Mark Knecht wrote: >> >> So this suggests that because I did the install from a running Gentoo >> chroot that the mknod commands didn't stick? Somehow they were part >> of, or because part of, the host Gentoo non-RAID install? Interesting. > > I don't know what the handbook says these days, but I understand that it's > lately taken to recommending a bind mount of /dev. If that's the case, then > none of the static device nodes that are contained with the /dev directory > within the stage3 tarball will actually make it on to the root filesystem > because, at the time of unpacking, they will be redirected to the (volatile) > tmpfs mount at /dev with respect to the livecd environment. > > From the point of view of the problem you're having, it may not even matter > but it's one thing to try anyway. > > It's interesting that the component disks are available. In principle, > there's no reason why the array should not be assembled. Here's an example > of how it looks during the boot process on one of my systems: > > Command line: root=/dev/md2 > Kernel command line: root=/dev/md2 quiet > ata1: SATA max UDMA/133 cmd 0xcc30 ctl 0xcc28 bmdma 0xcc40 irq 23 > ata2: SATA max UDMA/133 cmd 0xcc38 ctl 0xcc2c bmdma 0xcc48 irq 23 <SNIP> > > You might consider disabling the framebuffer temporarily, as it may impact > upon your ability to see what's going on early during the boot process. > > Cheers, > > --Kerin Hi Kerin, First, thanks for sticking with me on this. I really appreciate it. Second, I apologize for the length of the reply but it's still not working and I wanted to try and clearly show the steps I've taken. Maybe you or someone else will see the step I'm missing. OK, more and more it's looking to me like on the RAID I'm just not getting the /devmdX special file that has to be there to mount/bind/whatever the hardware to. What creates it, other than mknod? Can I do it by hand some other way? Read on... 1) Booted non-RAID and look in /dev for md*. md0 is there. I mount the RAID and look in the directory /mnt/gentoo/dev/ for anything named md*. There's nothing. 2) Booting with the Live CD I modprobe raid1, assemble the RAID, and then do the recommended chroot: livecd usr # cd / livecd / # mount -t proc proc /mnt/gentoo/proc livecd / # mount -o bind /dev /mnt/gentoo/dev livecd / # cp -L /etc/resolv.conf /mnt/gentoo/etc/ livecd / # chroot /mnt/gentoo /bin/bash livecd / # env-update && source /etc/profile 3) I look in /dev and still no md*. (There shouldn't be) 4) Because I used md3 to get into the RAID from the Live CD I create some new devices, but specifically don't do md3: livecd / # mknod /dev/md0 b 9 0 livecd / # mknod /dev/md1 b 9 1 livecd / # mknod /dev/md2 b 9 2 livecd / # mknod /dev/md4 b 9 4 livecd / # mknod /dev/md5 b 9 5 5) ls the directory and I see the ones I created plus md3 bound from the chroot above: livecd / # ls /dev/md* /dev/md0 /dev/md1 /dev/md2 /dev/md3 /dev/md4 /dev/md5 /dev/md: 3 6) I exit the chroot and look again at what's now in the Live CD /dev. As expected I still see all 6. livecd / # exit exit livecd ~ # ls /dev/md* /dev/md0 /dev/md1 /dev/md2 /dev/md3 /dev/md4 /dev/md5 /dev/md: 3 livecd ~ # df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 3052532 29600 3022932 1% / /dev/sr0 117392 117392 0 100% /mnt/cdrom /dev/loop0 87424 87424 0 100% /mnt/livecd udev 10240 216 10024 3% /dev tmpfs 3052532 6152 3046380 1% /mnt/livecd/lib64/firmware tmpfs 3052532 0 3052532 0% /mnt/livecd/usr/portage /dev/md3 30969528 2254188 27142180 8% /mnt/gentoo livecd ~ # 7) Try booting RAID a couple of times with different command line options. It still fails the same way. 8) Boot back to non-RAID and mount the RAID, this time as md0 just to be different. I look in /dev and see only md0, as expected: keeper ~ # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 30969600 7244840 22151596 25% / udev 10240 228 10012 3% /dev shm 3053512 0 3053512 0% /dev/shm /dev/md0 30969528 2254188 27142180 8% /mnt/gentoo keeper ~ # ls /dev/md* /dev/md0 /dev/md: 0 keeper ~ # 9) I look in /mnt/gentoo/dev to see if ANY md special files are there. There are none: keeper ~ # ls -al /mnt/gentoo/dev/md* ls: cannot access /mnt/gentoo/dev/md*: No such file or directory keeper ~ # All the other stuff is there, but not the special files I created while in the chroot. So, to me, this comes down to something like when I'm booting /dev/md0 or md3 isn't available so the kernel cannot mount the RAID anywhere. What creates the special file, at least by hand, is mknod, and for some reason I'm unable to make that work for me. Either there's something weird about doing this on RAID, or there's something stupid that I'm still doing. (I vote for the latter although I've been doing it for days so I probably cannot even see it anymore.) I guess I would hope that some piece of software is supposed to make these special files on the fly when booting if they don't exist. Maybe that's the purpose of appending md=0,/dev/sdb3,/dev/sdc3 but even that's not working for me. Maybe that points to something in kernel config that turns that on? I don't know. Note that in the Gentoo RAID install guide that I'm following the only mknod step is pre-chroot so nothing in the final RAID design ever does that by hand. If that guide actually results in a working system http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml I've tried all the boot options shown at the end. I don't know what to try next. Cheers, Mark RAID fstab: /dev/sda1 /boot ext2 noauto,noatime 1 2 /dev/md0 / ext3 noatime 0 1 /dev/sda2 none swap sw 0 0 /dev/sdb2 none swap sw 0 0 /dev/sdc2 none swap sw 0 0 /dev/cdrom /mnt/cdrom auto noauto,ro 0 0 grub.conf: default 0 timeout 30 splashimage=(hd0,0)/boot/grub/splash.xpm.gz title /dev/sda1 Gentoo Linux 2.6.33-gentoo root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo root=/dev/sda3 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID using md0 root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md0 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID using md3 root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md3 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID explicit md0=... root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md0 md=0,/dev/sdb3,/dev/sdc3 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID explicit md3=... root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/md3 md=3,/dev/sdb3,/dev/sdc3 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID sdb3 only root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/sdb3 title /dev/sda1 Gentoo Linux 2.6.33-gentoo-RAID sdc3 only root (hd0,0) kernel (hd0,0)/boot/bzImage-2.6.33-gentoo-RAID root=/dev/sdc3 ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 22:16 ` Mark Knecht @ 2010-04-04 22:47 ` Kerin Millar 2010-04-04 23:12 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 22:47 UTC (permalink / raw To: gentoo-user On 04/04/2010 23:16, Mark Knecht wrote: > First, thanks for sticking with me on this. I really appreciate it. > Second, I apologize for the length of the reply but it's still not > working and I wanted to try and clearly show the steps I've taken. > Maybe you or someone else will see the step I'm missing. [snip] > I don't know what to try next. OK, I think I now understand what's happening here. I regret that I did not recall this earlier but only the original RAID superblock format (version 0.90.00) is supported for automatic assembly! I have two servers that are set up in a similar way as your box, and they both use this format. It's possible that the docs may be out of date but /usr/src/linux/Documentation/md.txt says: "When md is compiled into the kernel (not as module), partitions of type 0xfd are scanned and automatically assembled into RAID arrays. This autodetection may be suppressed with the kernel parameter "raid=noautodetect". As of kernel 2.6.9, only drives with a type 0 superblock can be autodetected and run at boot time." Also, look at this: http://www.mail-archive.com/linux-raid@vger.kernel.org/msg06215.html To quote Neil Brown: "v0.90 can be used with 'in kernel autodetect' (i.e. partition type 0xfd). v1 cannot (I consider this an improvement :-)" Well, I can't say I agree with him there. Anyway, it seems that you're using the 1.1 superblock format. So, what options does this leave you with? a) Backup the root filesystem, and re-create the array with the regular superblock format. If necessary, coerce mdadm with -e 0 but it should be a default. b) Rely on userspace tools to assemble the array. This means either having the root filesystem off raid, or using an initrd/initramfs image. I'd got for the first option as it keeps things simple and the benefits of the v1 format are nebulous in practical terms. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 22:47 ` Kerin Millar @ 2010-04-04 23:12 ` Mark Knecht 2010-04-04 23:51 ` Kerin Millar 0 siblings, 1 reply; 25+ messages in thread From: Mark Knecht @ 2010-04-04 23:12 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 3:47 PM, Kerin Millar <kerframil@gmail.com> wrote: > On 04/04/2010 23:16, Mark Knecht wrote: >> >> First, thanks for sticking with me on this. I really appreciate it. >> Second, I apologize for the length of the reply but it's still not >> working and I wanted to try and clearly show the steps I've taken. >> Maybe you or someone else will see the step I'm missing. > > [snip] > >> I don't know what to try next. > > OK, I think I now understand what's happening here. I regret that I did not > recall this earlier but only the original RAID superblock format (version > 0.90.00) is supported for automatic assembly! I have two servers that are > set up in a similar way as your box, and they both use this format. It's > possible that the docs may be out of date but > /usr/src/linux/Documentation/md.txt says: > > "When md is compiled into the kernel (not as module), partitions of type > 0xfd are scanned and automatically assembled into RAID arrays. This > autodetection may be suppressed with the kernel parameter > "raid=noautodetect". As of kernel 2.6.9, only drives with a type 0 > superblock can be autodetected and run at boot time." > > Also, look at this: > > http://www.mail-archive.com/linux-raid@vger.kernel.org/msg06215.html > > To quote Neil Brown: > > "v0.90 can be used with 'in kernel autodetect' (i.e. partition type 0xfd). > v1 cannot (I consider this an improvement :-)" > > Well, I can't say I agree with him there. > > Anyway, it seems that you're using the 1.1 superblock format. So, what > options does this leave you with? > > a) Backup the root filesystem, and re-create the array with the regular > superblock format. If necessary, coerce mdadm with -e 0 but it should > be a default. > > b) Rely on userspace tools to assemble the array. This means either > having the root filesystem off raid, or using an initrd/initramfs > image. > > I'd got for the first option as it keeps things simple and the benefits of > the v1 format are nebulous in practical terms. > > Cheers, > > --Kerin > > > Hi, From my post this morning: "No problem supplying it. I did the rebuild this morning but forced metadata to Type 1.0. No change as you suggested there wouldn't be." I guess I didn't post it there but what I meant by that was the following: 1) If you don't specify metadata then you get the newest - I think that's currently ver. 1.2 or something. 2) I tried 1.0 this morning (shown below) which didn't fix it. (commands used are below) I will immediately try 0.90 as I have no problem with the limitations at this time: 0, 0.90 Use the original 0.90 format superblock. This format limits arrays to 28 component devices and limits component devices of levels 1 and greater to 2 terabytes. I should hopefully know in an hour or two how this worked. Thanks for the help! Cheers, Mark keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb3 /dev/sdc3 mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/' or '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=1.0 mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/' or '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=1.0 Continue creating array? n mdadm: create aborted. keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2 --metadata=1.0 /dev/sdb3 /dev/sdc3 mdadm: array /dev/md0 started. keeper ~ # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdc3[1] sdb3[0] 31463228 blocks super 1.0 [2/2] [UU] [>....................] resync = 3.9% (1241664/31463228) finish=5.2min speed=95512K/sec unused devices: <none> keeper ~ # ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 23:12 ` Mark Knecht @ 2010-04-04 23:51 ` Kerin Millar 2010-04-04 23:58 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Kerin Millar @ 2010-04-04 23:51 UTC (permalink / raw To: gentoo-user On 05/04/2010 00:12, Mark Knecht wrote: > 1) If you don't specify metadata then you get the newest - I think > that's currently ver. 1.2 or something. Interesting. I suppose that might be a change in mdadm-3.0 (a version which I have yet to use to create any new arrays). However, that would contradict the man page which still says: "0, 0.90, default" > 2) I tried 1.0 this morning (shown below) which didn't fix it. Right. Any version above in the 1 series (1, 1.0, 1.1, 1.2) will not work. I'm certain that reverting to the original format is going to resolve the issue and that we've just been barking up the wrong tree(s) hitherto. --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 23:51 ` Kerin Millar @ 2010-04-04 23:58 ` Mark Knecht 2010-04-05 0:28 ` Kerin Millar 2010-04-05 0:34 ` Mark Knecht 0 siblings, 2 replies; 25+ messages in thread From: Mark Knecht @ 2010-04-04 23:58 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 4:51 PM, Kerin Millar <kerframil@gmail.com> wrote: > On 05/04/2010 00:12, Mark Knecht wrote: >> >> 1) If you don't specify metadata then you get the newest - I think >> that's currently ver. 1.2 or something. > > Interesting. I suppose that might be a change in mdadm-3.0 (a version which > I have yet to use to create any new arrays). However, that would contradict > the man page which still says: > > "0, 0.90, default" > >> 2) I tried 1.0 this morning (shown below) which didn't fix it. > > Right. Any version above in the 1 series (1, 1.0, 1.1, 1.2) will not work. > I'm certain that reverting to the original format is going to resolve the > issue and that we've just been barking up the wrong tree(s) hitherto. > > --Kerin I'm emerging gentoo-sources in the chroot now. One thing about this that still confuses me is where /dev/md3, or whatever, comes from when I boot if the the mknod command is never executed within the chrrot. (As per the install guide.) Not a big deal to proceed and see what happens. Maybe the kernel just creates it based on discovering the RAID? Or it makes it because I explicitly define it at the command line? As I say, no big deal to just push forward but that's still a question for me at this point. Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 23:58 ` Mark Knecht @ 2010-04-05 0:28 ` Kerin Millar 2010-04-05 0:34 ` Mark Knecht 1 sibling, 0 replies; 25+ messages in thread From: Kerin Millar @ 2010-04-05 0:28 UTC (permalink / raw To: gentoo-user On 05/04/2010 00:58, Mark Knecht wrote: > One thing about this that still confuses me is where /dev/md3, or > whatever, comes from when I boot if the the mknod command is never > executed within the chrrot. (As per the install guide.) Not a big deal > to proceed and see what happens. Maybe the kernel just creates it > based on discovering the RAID? Or it makes it because I explicitly > define it at the command line? Well, it shouldn't matter. The md block device will be initialised by the kernel as soon as it loads, whereupon it will be resolved internally by its registered major/minor numbers for the purpose of mounting the root filesystem (that's the "9, 0" that you referred to earlier in the thread). Once the root filesystem is mounted read-only, it proceeds to load init. Later, the device node will need to be present - for instance, when fstab is parsed - but udev will have taken care of it by that time. That is, udev will manifest the device node in a tmpfs filesystem which is mounted at /dev and dynamically populated early on during the boot process. Cheers, --Kerin ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 23:58 ` Mark Knecht 2010-04-05 0:28 ` Kerin Millar @ 2010-04-05 0:34 ` Mark Knecht 1 sibling, 0 replies; 25+ messages in thread From: Mark Knecht @ 2010-04-05 0:34 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 4:58 PM, Mark Knecht <markknecht@gmail.com> wrote: > On Sun, Apr 4, 2010 at 4:51 PM, Kerin Millar <kerframil@gmail.com> wrote: >> On 05/04/2010 00:12, Mark Knecht wrote: >>> >>> 1) If you don't specify metadata then you get the newest - I think >>> that's currently ver. 1.2 or something. >> >> Interesting. I suppose that might be a change in mdadm-3.0 (a version which >> I have yet to use to create any new arrays). However, that would contradict >> the man page which still says: >> >> "0, 0.90, default" >> >>> 2) I tried 1.0 this morning (shown below) which didn't fix it. >> >> Right. Any version above in the 1 series (1, 1.0, 1.1, 1.2) will not work. >> I'm certain that reverting to the original format is going to resolve the >> issue and that we've just been barking up the wrong tree(s) hitherto. >> >> --Kerin > > I'm emerging gentoo-sources in the chroot now. > > One thing about this that still confuses me is where /dev/md3, or > whatever, comes from when I boot if the the mknod command is never > executed within the chrrot. (As per the install guide.) Not a big deal > to proceed and see what happens. Maybe the kernel just creates it > based on discovering the RAID? Or it makes it because I explicitly > define it at the command line? > > As I say, no big deal to just push forward but that's still a question > for me at this point. > > Cheers, > Mark > OK, I'm up and running now. Using --metadata=0.90 when first creating the RAID was the solution. It seems that md0 is (I guess) there by default and then md3 gets created by the kernel extra command line stuff I guess: k2 ~ # ls /dev/md* /dev/md0 /dev/md3 /dev/md: 0 3 3_0 k2 ~ # localhost ~ # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md3 41294780 2258892 36938208 6% / udev 10240 232 10008 3% /dev shm 3053480 0 3053480 0% /dev/shm Thanks for all the help today Kerin. I really appreciate it! Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-04 14:20 ` Mark Knecht 2010-04-04 17:32 ` Kerin Millar @ 2010-04-05 0:47 ` walt 2010-04-05 1:03 ` Mark Knecht 2010-04-05 10:38 ` Mick 1 sibling, 2 replies; 25+ messages in thread From: walt @ 2010-04-05 0:47 UTC (permalink / raw To: gentoo-user On 04/04/2010 07:20 AM, Mark Knecht wrote: > keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config > 4c4 > < # Mon Mar 29 01:02:31 2010 > --- >> # Sun Apr 4 06:28:53 2010 > 893,912c893,906 > < CONFIG_MD_LINEAR=m > < CONFIG_MD_RAID0=m Hi Mark, Interesting thread, and I'm learning a lot from following along. I know very little about raid so I can benefit from nearly any question. Just one suggestion about diffs, though. Most people who post and/or test patches will expect the 'unified' diff format, which is generated by using 'diff -u'. Much easier for humans to parse. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-05 0:47 ` walt @ 2010-04-05 1:03 ` Mark Knecht 2010-04-05 10:38 ` Mick 1 sibling, 0 replies; 25+ messages in thread From: Mark Knecht @ 2010-04-05 1:03 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 5:47 PM, walt <w41ter@gmail.com> wrote: > On 04/04/2010 07:20 AM, Mark Knecht wrote: >> >> keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config >> 4c4 >> < # Mon Mar 29 01:02:31 2010 >> --- >>> >>> # Sun Apr 4 06:28:53 2010 >> >> 893,912c893,906 >> < CONFIG_MD_LINEAR=m >> < CONFIG_MD_RAID0=m > > Hi Mark, > > Interesting thread, and I'm learning a lot from following along. I know > very little about raid so I can benefit from nearly any question. > > Just one suggestion about diffs, though. Most people who post and/or test > patches will expect the 'unified' diff format, which is generated by using > 'diff -u'. Much easier for humans to parse. > Walt, Good to know about the diff stuff. I hope I can remember that next time. Glad if this thread can help others, either now or in the future. I do intend to follow up with the mdadm guys about the actual metadata requirements when I get a chance. I'm just finishing emerge -DuN @world on the new RAID build. Fast with an 8 core processor and Enterprise class RAID drives. Can hardly wait for the big 12 core machine with two RAIDs in it to start running. Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] Re: How does grub assemble a RAID1 for / ?? 2010-04-05 0:47 ` walt 2010-04-05 1:03 ` Mark Knecht @ 2010-04-05 10:38 ` Mick 1 sibling, 0 replies; 25+ messages in thread From: Mick @ 2010-04-05 10:38 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: Text/Plain, Size: 883 bytes --] On Monday 05 April 2010 01:47:57 walt wrote: > On 04/04/2010 07:20 AM, Mark Knecht wrote: > > keeper ~ # diff /usr/src/linux/.config > > /mnt/gentoo/usr/src/linux/.config 4c4 > > < # Mon Mar 29 01:02:31 2010 > > --- > > > >> # Sun Apr 4 06:28:53 2010 > > > > 893,912c893,906 > > < CONFIG_MD_LINEAR=m > > < CONFIG_MD_RAID0=m > > Hi Mark, > > Interesting thread, and I'm learning a lot from following along. I know > very little about raid so I can benefit from nearly any question. > > Just one suggestion about diffs, though. Most people who post and/or test > patches will expect the 'unified' diff format, which is generated by using > 'diff -u'. Much easier for humans to parse. I find 'diff -y' even easier on a wide screen, especially if you have emerged colordiff and have added 'alias diff=colordiff' in your .bashrc -- Regards, Mick [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 198 bytes --] ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] How does grub assemble a RAID1 for / ?? 2010-04-03 23:07 [gentoo-user] How does grub assemble a RAID1 for / ?? Mark Knecht 2010-04-03 23:37 ` Neil Bothwick @ 2010-04-03 23:45 ` Albert Hopkins 2010-04-04 9:57 ` Xavier Parizet 1 sibling, 1 reply; 25+ messages in thread From: Albert Hopkins @ 2010-04-03 23:45 UTC (permalink / raw To: gentoo-user On Sat, 2010-04-03 at 16:07 -0700, Mark Knecht wrote: > The install is complete but it won't boot. grub finds the kernel > and starts booting but then I get the typical VFS file sync error as > the kernel starts looking for the install on /dev/md3. What I'm not > understanding is how does the boot process get the information > required to assemble the RAID device. GRUB does not assemble raid. That's why it only works with RAID1. By your own account, GRUB has succeeded, therefore GRUB is not the problem. The problem is the kernel The kernel assembles RAID by looking for partitions of with the Linux RAID partition type, finding out what kind of RAID they are, and assembling them (according to their RAID volume UUID). You apparently only have one RAID volume. It's probably being assigned to /dev/md0, yet you are passing root=/dev/md3.. not sure why you are doing that. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] How does grub assemble a RAID1 for / ?? 2010-04-03 23:45 ` [gentoo-user] " Albert Hopkins @ 2010-04-04 9:57 ` Xavier Parizet 2010-04-04 14:21 ` Mark Knecht 0 siblings, 1 reply; 25+ messages in thread From: Xavier Parizet @ 2010-04-04 9:57 UTC (permalink / raw To: gentoo-user [-- Attachment #1: Type: text/plain, Size: 1197 bytes --] Try appending md=3,/dev/sdb3,/dev/sdc3 to the kernel command line parameters. On 04/04/2010 01:45 AM, Albert Hopkins wrote: > On Sat, 2010-04-03 at 16:07 -0700, Mark Knecht wrote: >> The install is complete but it won't boot. grub finds the kernel >> and starts booting but then I get the typical VFS file sync error as >> the kernel starts looking for the install on /dev/md3. What I'm not >> understanding is how does the boot process get the information >> required to assemble the RAID device. > > GRUB does not assemble raid. That's why it only works with RAID1. > > By your own account, GRUB has succeeded, therefore GRUB is not the > problem. > > The problem is the kernel > > The kernel assembles RAID by looking for partitions of with the Linux > RAID partition type, finding out what kind of RAID they are, and > assembling them (according to their RAID volume UUID). > > You apparently only have one RAID volume. It's probably being assigned > to /dev/md0, yet you are passing root=/dev/md3.. not sure why you are > doing that. -- Xavier Parizet YaGB : http://gentooist.com GPG : C7DC B10E FC21 63BE B453 D239 F6E6 DF65 1569 91BF [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 262 bytes --] ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [gentoo-user] How does grub assemble a RAID1 for / ?? 2010-04-04 9:57 ` Xavier Parizet @ 2010-04-04 14:21 ` Mark Knecht 0 siblings, 0 replies; 25+ messages in thread From: Mark Knecht @ 2010-04-04 14:21 UTC (permalink / raw To: gentoo-user On Sun, Apr 4, 2010 at 2:57 AM, Xavier Parizet <xav@gentooist.com> wrote: > Try appending md=3,/dev/sdb3,/dev/sdc3 to the kernel command line > parameters. > Thanks. Tried that one last night but no luck, although it does change the message to Unknown-block(9,3) from Unknown-block(9,0). Cheers, Mark ^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2010-04-05 11:03 UTC | newest] Thread overview: 25+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-04-03 23:07 [gentoo-user] How does grub assemble a RAID1 for / ?? Mark Knecht 2010-04-03 23:37 ` Neil Bothwick 2010-04-04 1:01 ` Mark Knecht 2010-04-04 2:38 ` [gentoo-user] " Kerin Millar 2010-04-04 14:20 ` Mark Knecht 2010-04-04 17:32 ` Kerin Millar 2010-04-04 17:50 ` Mark Knecht 2010-04-04 18:13 ` Kerin Millar 2010-04-04 18:43 ` Mark Knecht 2010-04-04 19:29 ` Kerin Millar 2010-04-04 19:52 ` Mark Knecht 2010-04-04 20:06 ` Kerin Millar 2010-04-04 22:16 ` Mark Knecht 2010-04-04 22:47 ` Kerin Millar 2010-04-04 23:12 ` Mark Knecht 2010-04-04 23:51 ` Kerin Millar 2010-04-04 23:58 ` Mark Knecht 2010-04-05 0:28 ` Kerin Millar 2010-04-05 0:34 ` Mark Knecht 2010-04-05 0:47 ` walt 2010-04-05 1:03 ` Mark Knecht 2010-04-05 10:38 ` Mick 2010-04-03 23:45 ` [gentoo-user] " Albert Hopkins 2010-04-04 9:57 ` Xavier Parizet 2010-04-04 14:21 ` Mark Knecht
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox