Hello, we would like to know which way lustre is heading. From the s/w repository we see that only redhat and suse ditros seems to be supported. Is this the official policy of the lustre development to stick to (only) these two distros ? If not, then the sun src patches are still missing in the lustre AND e2fsprogs branches. Thanks and Regards Heiko
On 2010-05-19, at 01:40, Heiko Schr?ter wrote:> we would like to know which way lustre is heading. > >> From the s/w repository we see that only redhat and suse ditros seems to be supported. > > Is this the official policy of the lustre development to stick to (only) these two distros ?On the client side, we will support the main distros that our customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after release), and SLES 10/11. We make a best-effort attempt to have the client work with all client kernels, but since our resources are limited we cannot test kernels other than the supported ones. I don''t see any huge demand for e.g. an officially-supported Ubuntu client kernel, but there has long been an unofficial Debian lustre package. On the server side, we will continue to support RHEL5.x and SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being worked on) for the Lustre 2.x release. Since maintaining kernel patches for other kernels is a lot of work, we do not attempt to provide patches for other than official kernels. However, there have in the past been ports of the kernel patches to other kernels by external contributors (e.g. FC11, FC12, etc) and this will hopefully continue in the future. There is also bug 21524 which outlines how the server core kernel patches could be removed. By removing the core kernel and ldiskfs patches, there would no longer be a strong link between the Lustre code and the particular kernel version that was being used on the server, just like there is no longer a strong link on the client. However, given the ever-changing nature of the kernel APIs I think there will always be an ongoing need to maintain the Lustre code to work with the latest kernels. Bug 21635 describes how to remove/cleanup patches to the ldiskfs code. We hope to work on these patches incrementally, either by changing the Lustre code to remove the need for the patch, or by submitting the patch upstream. However, external assistance is always welcome.> If not, then the sun src patches are still missing in the lustre AND e2fsprogs branches.I''m not sure what you mean. The e2fsprogs patches have always been in a separate repository from the core Lustre code, and all of the Lustre/ldiskfs kernel patches are in the Git repository. Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc.
Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie:> On 2010-05-19, at 01:40, Heiko Schr?ter wrote: > > we would like to know which way lustre is heading. > > > >> From the s/w repository we see that only redhat and suse ditros seems to be supported. > > > > Is this the official policy of the lustre development to stick to (only) these two distros ? > > On the client side, we will support the main distros that our customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after release), and SLES 10/11. We make a best-effort attempt to have the client work with all client kernels, but since our resources are limited we cannot test kernels other than the supported ones. I don''t see any huge demand for e.g. an officially-supported Ubuntu client kernel, but there has long been an unofficial Debian lustre package. > > On the server side, we will continue to support RHEL5.x and SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being worked on) for the Lustre 2.x release. Since maintaining kernel patches for other kernels is a lot of work, we do not attempt to provide patches for other than official kernels. However, there have in the past been ports of the kernel patches to other kernels by external contributors (e.g. FC11, FC12, etc) and this will hopefully continue in the future.The server side is the more critical part as we are using gentoo+lustre running a vanilla kernel 2.6.22.19 with the lustre patches version 1.6.6. As far as we are concerned it would be nice to have the pathces for the "vanilla-kernels" in 1.8.3+. This would be just fine. On the other hand if maintaining is the key problem on your side what would be a major argument against using a patched sles/rhel on a lustre server not running the sles/rhel distro ? I know a lot of things can happen but are these rhel/sles patches do brake some key features of the kernel which would only work under that specific distro ? I''ve positivley tested a lustre client with a sles patched kernel on a gentoo distro. But i''am a bit nervous about testing it on our live lustre server system.> > > If not, then the sun src patches are still missing in the lustre AND e2fsprogs branches. > > I''m not sure what you mean. The e2fsprogs patches have always been in a separate repository from the core Lustre code, and all of the Lustre/ldiskfs kernel patches are in the Git repository.I know. But the patches are missing for 1.41.10 in that repo. i.e. as this here "e2fsprogs-1.41.6.sun1-patches.tgz" Thanks very much for your help. Regards Heiko
On Wednesday 19 May 2010, Heiko Schr?ter wrote:> Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie: > > On 2010-05-19, at 01:40, Heiko Schr?ter wrote: > > > we would like to know which way lustre is heading. > > > > > >> From the s/w repository we see that only redhat and suse ditros seems > > >> to be supported. > > > > > > Is this the official policy of the lustre development to stick to > > > (only) these two distros ? > > > > On the client side, we will support the main distros that our customers > > are using, namely RHEL/OEL/CentOS 5.x (and 6.x after release), and SLES > > 10/11. We make a best-effort attempt to have the client work with all > > client kernels, but since our resources are limited we cannot test > > kernels other than the supported ones. I don''t see any huge demand for > > e.g. an officially-supported Ubuntu client kernel, but there has long > > been an unofficial Debian lustre package. > > > > On the server side, we will continue to support RHEL5.x and SLES10/11 for > > the Lustre 1.8 release, and RHEL 5.x (6.x is being worked on) for the > > Lustre 2.x release. Since maintaining kernel patches for other kernels > > is a lot of work, we do not attempt to provide patches for other than > > official kernels. However, there have in the past been ports of the > > kernel patches to other kernels by external contributors (e.g. FC11, > > FC12, etc) and this will hopefully continue in the future. > > The server side is the more critical part as we are using gentoo+lustre > running a vanilla kernel 2.6.22.19 with the lustre patches version 1.6.6. > As far as we are concerned it would be nice to have the pathces for the > "vanilla-kernels" in 1.8.3+. This would be just fine. > > On the other hand if maintaining is the key problem on your side what would > be a major argument against using a patched sles/rhel on a lustre serverThat is what I would recommend and what several groups do (usually with Debian, though).> not running the sles/rhel distro ? I know a lot of things can happen but > are these rhel/sles patches do brake some key features of the kernel which > would only work under that specific distro ? I''ve positivley tested a > lustre client with a sles patched kernel on a gentoo distro. But i''am a > bit nervous about testing it on our live lustre server system.The only thing that really might cause trouble is udev, since sysfs maintainers like to break old udev versions. I think upcoming Debian Squeeze requires 2.6.27 at a minimum. Cheers, Bernd -- Bernd Schubert DataDirect Networks
I''ve used a SLES kernel on an FC install for a long time on my home system. With newer distros there are also fewer changes to the base kernel, so there shouldn''t be as much trouble to use e.g. the SLES 11 SP1 kernel (2.6.32) when it is released. Cheers, Andreas On 2010-05-19, at 6:01, Heiko Schr?ter <schroete at iup.physik.uni-bremen.d e> wrote:> Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie: >> On 2010-05-19, at 01:40, Heiko Schr?ter wrote: >>> we would like to know which way lustre is heading. >>> >>>> From the s/w repository we see that only redhat and suse ditros >>>> seems to be supported. >>> >>> Is this the official policy of the lustre development to stick to >>> (only) these two distros ? >> >> On the client side, we will support the main distros that our >> customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after >> release), and SLES 10/11. We make a best-effort attempt to have >> the client work with all client kernels, but since our resources >> are limited we cannot test kernels other than the supported ones. >> I don''t see any huge demand for e.g. an officially-supported Ubuntu >> client kernel, but there has long been an unofficial Debian lustre >> package. >> >> On the server side, we will continue to support RHEL5.x and >> SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being >> worked on) for the Lustre 2.x release. Since maintaining kernel >> patches for other kernels is a lot of work, we do not attempt to >> provide patches for other than official kernels. However, there >> have in the past been ports of the kernel patches to other kernels >> by external contributors (e.g. FC11, FC12, etc) and this will >> hopefully continue in the future. > > The server side is the more critical part as we are using gentoo > +lustre running a vanilla kernel 2.6.22.19 with the lustre patches > version 1.6.6. > As far as we are concerned it would be nice to have the pathces for > the "vanilla-kernels" in 1.8.3+. This would be just fine. > > On the other hand if maintaining is the key problem on your side > what would be a major argument against using a patched sles/rhel on > a lustre server not running the sles/rhel distro ? > I know a lot of things can happen but are these rhel/sles patches do > brake some key features of the kernel which would only work under > that specific distro ? > I''ve positivley tested a lustre client with a sles patched kernel on > a gentoo distro. But i''am a bit nervous about testing it on our live > lustre server system. > >> >>> If not, then the sun src patches are still missing in the lustre >>> AND e2fsprogs branches. >> >> I''m not sure what you mean. The e2fsprogs patches have always been >> in a separate repository from the core Lustre code, and all of the >> Lustre/ldiskfs kernel patches are in the Git repository. > > I know. But the patches are missing for 1.41.10 in that repo. i.e. > as this here "e2fsprogs-1.41.6.sun1-patches.tgz" > > Thanks very much for your help. > Regards > Heiko
Quick "Public Service Announcement" ClusterStor is and will be providing support services for SLES on both 1.8x and 2.x releases. If anyone would like to receive additional information please contact me at kevin.canady at clusterstor.com or 415.505.7701 Best regards, Kevin P. Kevin Canady Vice President, ClusterStor Inc. 415.505.7701 kevin.canady at clusterstor.com On May 19, 2010, at 8:01 AM, Andreas Dilger wrote:> I''ve used a SLES kernel on an FC install for a long time on my home > system. With newer distros there are also fewer changes to the base > kernel, so there shouldn''t be as much trouble to use e.g. the SLES 11 > SP1 kernel (2.6.32) when it is released. > > Cheers, Andreas > > On 2010-05-19, at 6:01, Heiko Schr?ter <schroete at iup.physik.uni-bremen.d > e> wrote: > >> Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie: >>> On 2010-05-19, at 01:40, Heiko Schr?ter wrote: >>>> we would like to know which way lustre is heading. >>>> >>>>> From the s/w repository we see that only redhat and suse ditros >>>>> seems to be supported. >>>> >>>> Is this the official policy of the lustre development to stick to >>>> (only) these two distros ? >>> >>> On the client side, we will support the main distros that our >>> customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after >>> release), and SLES 10/11. We make a best-effort attempt to have >>> the client work with all client kernels, but since our resources >>> are limited we cannot test kernels other than the supported ones. >>> I don''t see any huge demand for e.g. an officially-supported Ubuntu >>> client kernel, but there has long been an unofficial Debian lustre >>> package. >>> >>> On the server side, we will continue to support RHEL5.x and >>> SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being >>> worked on) for the Lustre 2.x release. Since maintaining kernel >>> patches for other kernels is a lot of work, we do not attempt to >>> provide patches for other than official kernels. However, there >>> have in the past been ports of the kernel patches to other kernels >>> by external contributors (e.g. FC11, FC12, etc) and this will >>> hopefully continue in the future. >> >> The server side is the more critical part as we are using gentoo >> +lustre running a vanilla kernel 2.6.22.19 with the lustre patches >> version 1.6.6. >> As far as we are concerned it would be nice to have the pathces for >> the "vanilla-kernels" in 1.8.3+. This would be just fine. >> >> On the other hand if maintaining is the key problem on your side >> what would be a major argument against using a patched sles/rhel on >> a lustre server not running the sles/rhel distro ? >> I know a lot of things can happen but are these rhel/sles patches do >> brake some key features of the kernel which would only work under >> that specific distro ? >> I''ve positivley tested a lustre client with a sles patched kernel on >> a gentoo distro. But i''am a bit nervous about testing it on our live >> lustre server system. >> >>> >>>> If not, then the sun src patches are still missing in the lustre >>>> AND e2fsprogs branches. >>> >>> I''m not sure what you mean. The e2fsprogs patches have always been >>> in a separate repository from the core Lustre code, and all of the >>> Lustre/ldiskfs kernel patches are in the Git repository. >> >> I know. But the patches are missing for 1.41.10 in that repo. i.e. >> as this here "e2fsprogs-1.41.6.sun1-patches.tgz" >> >> Thanks very much for your help. >> Regards >> Heiko > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
Dardo D Kleiner - CONTRACTOR
2010-May-20 01:04 UTC
[Lustre-discuss] Future of lustre 1.8.3+
Kevin, et al - I''m both personally and professionally encouraged to hear ClusterStor stand up and publicly state intent to support Lustre on SLES. The million dollar question is in regards to *server* support - in particular wrt the 2.x series. As a token of my interest, as well as a testament to my limited ability to maintain this in the long run, I submit the attached patches to the recent 1.10.0.40 beta release that enable building (and confirmed to be runnable) the server on current SLES11 kernel (2.6.27.45-0.1-default). One caveat is that quota support is not compilable and appears to be a bit more difficult job than I can probably manage. And I most certainly didn''t run a full regression suite, but a straightforward single stream read/write appears to work fine. Up to .38 it was mostly monkey work - but .40 introduced additional patches to the RHEL ext4 implementation that has more substantially diverged from the one in current SLES11. Perhaps SLES11SP1 will converge better... There''s perhaps a Bugzilla report where this is better posted, and tomorrow I''ll look around a bit more for that, but I felt like getting it out there asap. This has been a topic of much interest in my community and I''m starting to feel a bit alone in my desire to keep SLE across the board in my environment. I''ve invested quite a bit of time and effort there and though many are fine with black box appliances, in our research environment I prefer to have more transparency. Sincerely - Dardo On 5/19/2010 11:21 AM, Kevin Canady wrote:> Quick "Public Service Announcement" > > ClusterStor is and will be providing support services for SLES on both 1.8x and 2.x releases. If anyone would like to receive additional information please contact me at kevin.canady at clusterstor.com or 415.505.7701 > > Best regards, > Kevin > > P. Kevin Canady > Vice President, > ClusterStor Inc. > 415.505.7701 > kevin.canady at clusterstor.com > > On May 19, 2010, at 8:01 AM, Andreas Dilger wrote: > >> I''ve used a SLES kernel on an FC install for a long time on my home >> system. With newer distros there are also fewer changes to the base >> kernel, so there shouldn''t be as much trouble to use e.g. the SLES 11 >> SP1 kernel (2.6.32) when it is released. >> >> Cheers, Andreas >> >> On 2010-05-19, at 6:01, Heiko Schr?ter<schroete at iup.physik.uni-bremen.d >> e> wrote: >> >>> Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie: >>>> On 2010-05-19, at 01:40, Heiko Schr?ter wrote: >>>>> we would like to know which way lustre is heading. >>>>> >>>>>> From the s/w repository we see that only redhat and suse ditros >>>>>> seems to be supported. >>>>> >>>>> Is this the official policy of the lustre development to stick to >>>>> (only) these two distros ? >>>> >>>> On the client side, we will support the main distros that our >>>> customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after >>>> release), and SLES 10/11. We make a best-effort attempt to have >>>> the client work with all client kernels, but since our resources >>>> are limited we cannot test kernels other than the supported ones. >>>> I don''t see any huge demand for e.g. an officially-supported Ubuntu >>>> client kernel, but there has long been an unofficial Debian lustre >>>> package. >>>> >>>> On the server side, we will continue to support RHEL5.x and >>>> SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being >>>> worked on) for the Lustre 2.x release. Since maintaining kernel >>>> patches for other kernels is a lot of work, we do not attempt to >>>> provide patches for other than official kernels. However, there >>>> have in the past been ports of the kernel patches to other kernels >>>> by external contributors (e.g. FC11, FC12, etc) and this will >>>> hopefully continue in the future. >>> >>> The server side is the more critical part as we are using gentoo >>> +lustre running a vanilla kernel 2.6.22.19 with the lustre patches >>> version 1.6.6. >>> As far as we are concerned it would be nice to have the pathces for >>> the "vanilla-kernels" in 1.8.3+. This would be just fine. >>> >>> On the other hand if maintaining is the key problem on your side >>> what would be a major argument against using a patched sles/rhel on >>> a lustre server not running the sles/rhel distro ? >>> I know a lot of things can happen but are these rhel/sles patches do >>> brake some key features of the kernel which would only work under >>> that specific distro ? >>> I''ve positivley tested a lustre client with a sles patched kernel on >>> a gentoo distro. But i''am a bit nervous about testing it on our live >>> lustre server system. >>> >>>> >>>>> If not, then the sun src patches are still missing in the lustre >>>>> AND e2fsprogs branches. >>>> >>>> I''m not sure what you mean. The e2fsprogs patches have always been >>>> in a separate repository from the core Lustre code, and all of the >>>> Lustre/ldiskfs kernel patches are in the Git repository. >>> >>> I know. But the patches are missing for 1.41.10 in that repo. i.e. >>> as this here "e2fsprogs-1.41.6.sun1-patches.tgz" >>> >>> Thanks very much for your help. >>> Regards >>> Heiko >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss > >-------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: lustre-sles11.patch.1.10.0.40 Url: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100519/9cd74b03/attachment-0001.pl
Hi all, On Wed, 2010-05-19 at 14:43 +0200, Bernd Schubert wrote:> That is what I would recommend and what several groups do (usually with > Debian, though). > > > not running the sles/rhel distro ? I know a lot of things can happen but > > are these rhel/sles patches do brake some key features of the kernel which > > would only work under that specific distro ? I''ve positivley tested a > > lustre client with a sles patched kernel on a gentoo distro. But i''am a > > bit nervous about testing it on our live lustre server system. > > The only thing that really might cause trouble is udev, since sysfs > maintainers like to break old udev versions. I think upcoming Debian Squeeze > requires 2.6.27 at a minimum.Argg!!!, I think I am stacked with this situation. I compiled linux-2.6.18-164.11.1.el5.tar.bz2 under Ubuntu 10.04 (from Debian Squeeze) using make-kpkg and after dealing with postinst.d hooks to create initrd image (not created by default!!!), I tried to boot and then I got the following before dropping into a initramfs shell: --------------------------------------------------------------------------- Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Done. libudev: udev_monitor_new_from_netlink: error getting socket: Invalid argument wait-for-root[431] : segfault Gave up waiting form root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) -Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/0cff75ed-ba7f-4799-b596-cf2b214b9768 does not exist. Dropping to a shell! BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) buit-in shell (ask) Enter ''Help'' for a list of built-in commands. (initramfs) ------------------------------------------------------------------------------ Is this the problem you are talking about? Could you give me some ideas of how can be solved? Regards -- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I thought that there were Debian packages for Lustre, why not use those? Cheers, Andreas On 2010-05-20, at 9:48, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote:> Hi all, > > On Wed, 2010-05-19 at 14:43 +0200, Bernd Schubert wrote: > >> That is what I would recommend and what several groups do (usually >> with >> Debian, though). >> >>> not running the sles/rhel distro ? I know a lot of things can >>> happen but >>> are these rhel/sles patches do brake some key features of the >>> kernel which >>> would only work under that specific distro ? I''ve positivley >>> tested a >>> lustre client with a sles patched kernel on a gentoo distro. But >>> i''am a >>> bit nervous about testing it on our live lustre server system. >> >> The only thing that really might cause trouble is udev, since sysfs >> maintainers like to break old udev versions. I think upcoming >> Debian Squeeze >> requires 2.6.27 at a minimum. > > Argg!!!, I think I am stacked with this situation. I compiled > linux-2.6.18-164.11.1.el5.tar.bz2 under Ubuntu 10.04 (from Debian > Squeeze) using make-kpkg and after dealing with postinst.d hooks to > create initrd image (not created by default!!!), I tried to boot and > then I got the following before dropping into a initramfs shell: > > --- > --- > --------------------------------------------------------------------- > Begin: Mounting root file system... ... > Begin: Running /scripts/local-top ... > Done. > libudev: udev_monitor_new_from_netlink: error getting socket: Invalid > argument wait-for-root[431] : segfault > Gave up waiting form root device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Check root= (did the system wait for the right device?) > -Missing modules (cat /proc/modules; ls /dev) > ALERT! /dev/disk/by-uuid/0cff75ed-ba7f-4799-b596-cf2b214b9768 does not > exist. Dropping to a shell! > > > BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) buit-in shell (ask) > Enter ''Help'' for a list of built-in commands. > > (initramfs) > --- > --- > --- > --------------------------------------------------------------------- > > Is this the problem you are talking about? Could you give me some > ideas > of how can be solved? > > Regards > > > -- > Ramiro Alba > > Centre Tecnol?gic de Tranfer?ncia de Calor > http://www.cttc.upc.edu > > > Escola T?cnica Superior d''Enginyeries > Industrial i Aeron?utica de Terrassa > Colom 11, E-08222, Terrassa, Barcelona, Spain > Tel: (+34) 93 739 86 46 > > > -- > Aquest missatge ha estat analitzat per MailScanner > a la cerca de virus i d''altres continguts perillosos, > i es considera que est? net. > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote:> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, IOk, I am getting http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 but, please. Where can I get a suitable config file to apply both for servers and clients?> thought that there were Debian packages for Lustre, why not use those?Yes. I used them at the beginning, but after lustre 1.8.0.1 vanilla servers are not any more supported to be used as servers and I started to use RH5 kernels with lustre-1.8.1.1, both for clients and servers. In my case using Ubuntu 10.04 with kernel 2.6.32 NOT suported as a lustre patchless client, I prefer using an only kernel for the whole cluster, do I? Thanks for your answer. Regards> > Cheers, Andreas > > On 2010-05-20, at 9:48, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote: > > > Hi all, > > > > On Wed, 2010-05-19 at 14:43 +0200, Bernd Schubert wrote: > > > >> That is what I would recommend and what several groups do (usually > >> with > >> Debian, though). > >> > >>> not running the sles/rhel distro ? I know a lot of things can > >>> happen but > >>> are these rhel/sles patches do brake some key features of the > >>> kernel which > >>> would only work under that specific distro ? I''ve positivley > >>> tested a > >>> lustre client with a sles patched kernel on a gentoo distro. But > >>> i''am a > >>> bit nervous about testing it on our live lustre server system. > >> > >> The only thing that really might cause trouble is udev, since sysfs > >> maintainers like to break old udev versions. I think upcoming > >> Debian Squeeze > >> requires 2.6.27 at a minimum. > > > > Argg!!!, I think I am stacked with this situation. I compiled > > linux-2.6.18-164.11.1.el5.tar.bz2 under Ubuntu 10.04 (from Debian > > Squeeze) using make-kpkg and after dealing with postinst.d hooks to > > create initrd image (not created by default!!!), I tried to boot and > > then I got the following before dropping into a initramfs shell: > > > > --- > > --- > > --------------------------------------------------------------------- > > Begin: Mounting root file system... ... > > Begin: Running /scripts/local-top ... > > Done. > > libudev: udev_monitor_new_from_netlink: error getting socket: Invalid > > argument wait-for-root[431] : segfault > > Gave up waiting form root device. Common problems: > > - Boot args (cat /proc/cmdline) > > - Check rootdelay= (did the system wait long enough?) > > - Check root= (did the system wait for the right device?) > > -Missing modules (cat /proc/modules; ls /dev) > > ALERT! /dev/disk/by-uuid/0cff75ed-ba7f-4799-b596-cf2b214b9768 does not > > exist. Dropping to a shell! > > > > > > BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) buit-in shell (ask) > > Enter ''Help'' for a list of built-in commands. > > > > (initramfs) > > --- > > --- > > --- > > --------------------------------------------------------------------- > > > > Is this the problem you are talking about? Could you give me some > > ideas > > of how can be solved? > > > > Regards > > > > > > -- > > Ramiro Alba > > > > Centre Tecnol?gic de Tranfer?ncia de Calor > > http://www.cttc.upc.edu > > > > > > Escola T?cnica Superior d''Enginyeries > > Industrial i Aeron?utica de Terrassa > > Colom 11, E-08222, Terrassa, Barcelona, Spain > > Tel: (+34) 93 739 86 46 > > > > > > -- > > Aquest missatge ha estat analitzat per MailScanner > > a la cerca de virus i d''altres continguts perillosos, > > i es considera que est? net. > > > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss >-- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
On 2010-05-20, at 11:33, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote:> On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote: >> The SLES11 kernel is at 2.6.27 so it could be usable for this. >> Also, I > > Ok, I am getting > http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 > > but, please. Where can I get a suitable config file to apply both for > servers and clients?The config files are in the Lustre source tree in lustre/ kernel_patches/kernel_configs/ You can just use the .config file from your client kernel (ie patchless) since you don''t need the patched server kernel on the clients.>> thought that there were Debian packages for Lustre, why not use >> those? > > Yes. I used them at the beginning, but after lustre 1.8.0.1 vanilla > servers are not any more supported to be used as servers and I started > to use RH5 kernels with lustre-1.8.1.1, both for clients and servers.That''s too bad that the Debiana maintainers have stopped making updates. Doubly so because we worked to add the fixes needed to build on Debian into the Lustre sources, so it is possible to do "make debs" to get Debian packages using all of the standard Debian packaging tools.> In my case using Ubuntu 10.04 with kernel 2.6.32 NOT suported as a > lustre patchless client, I prefer using an only kernel for the > whole cluster, > do I? >That is by no means a requirement.> Thanks for your answer. > > Regards > >> >> Cheers, Andreas >> >> On 2010-05-20, at 9:48, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote: >> >>> Hi all, >>> >>> On Wed, 2010-05-19 at 14:43 +0200, Bernd Schubert wrote: >>> >>>> That is what I would recommend and what several groups do (usually >>>> with >>>> Debian, though). >>>> >>>>> not running the sles/rhel distro ? I know a lot of things can >>>>> happen but >>>>> are these rhel/sles patches do brake some key features of the >>>>> kernel which >>>>> would only work under that specific distro ? I''ve positivley >>>>> tested a >>>>> lustre client with a sles patched kernel on a gentoo distro. But >>>>> i''am a >>>>> bit nervous about testing it on our live lustre server system. >>>> >>>> The only thing that really might cause trouble is udev, since sysfs >>>> maintainers like to break old udev versions. I think upcoming >>>> Debian Squeeze >>>> requires 2.6.27 at a minimum. >>> >>> Argg!!!, I think I am stacked with this situation. I compiled >>> linux-2.6.18-164.11.1.el5.tar.bz2 under Ubuntu 10.04 (from Debian >>> Squeeze) using make-kpkg and after dealing with postinst.d hooks to >>> create initrd image (not created by default!!!), I tried to boot and >>> then I got the following before dropping into a initramfs shell: >>> >>> --- >>> --- >>> --- >>> ------------------------------------------------------------------ >>> Begin: Mounting root file system... ... >>> Begin: Running /scripts/local-top ... >>> Done. >>> libudev: udev_monitor_new_from_netlink: error getting socket: >>> Invalid >>> argument wait-for-root[431] : segfault >>> Gave up waiting form root device. Common problems: >>> - Boot args (cat /proc/cmdline) >>> - Check rootdelay= (did the system wait long enough?) >>> - Check root= (did the system wait for the right device?) >>> -Missing modules (cat /proc/modules; ls /dev) >>> ALERT! /dev/disk/by-uuid/0cff75ed-ba7f-4799-b596-cf2b214b9768 does >>> not >>> exist. Dropping to a shell! >>> >>> >>> BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) buit-in shell (ask) >>> Enter ''Help'' for a list of built-in commands. >>> >>> (initramfs) >>> --- >>> --- >>> --- >>> --- >>> ------------------------------------------------------------------ >>> >>> Is this the problem you are talking about? Could you give me some >>> ideas >>> of how can be solved? >>> >>> Regards >>> >>> >>> -- >>> Ramiro Alba >>> >>> Centre Tecnol?gic de Tranfer?ncia de Calor >>> http://www.cttc.upc.edu >>> >>> >>> Escola T?cnica Superior d''Enginyeries >>> Industrial i Aeron?utica de Terrassa >>> Colom 11, E-08222, Terrassa, Barcelona, Spain >>> Tel: (+34) 93 739 86 46 >>> >>> >>> -- >>> Aquest missatge ha estat analitzat per MailScanner >>> a la cerca de virus i d''altres continguts perillosos, >>> i es considera que est? net. >>> >>> _______________________________________________ >>> Lustre-discuss mailing list >>> Lustre-discuss at lists.lustre.org >>> http://lists.lustre.org/mailman/listinfo/lustre-discuss >> > -- > Ramiro Alba > > Centre Tecnol?gic de Tranfer?ncia de Calor > http://www.cttc.upc.edu > > > Escola T?cnica Superior d''Enginyeries > Industrial i Aeron?utica de Terrassa > Colom 11, E-08222, Terrassa, Barcelona, Spain > Tel: (+34) 93 739 86 46 > > > -- > Aquest missatge ha estat analitzat per MailScanner > a la cerca de virus i d''altres continguts perillosos, > i es considera que est? net. >
On 2010-05-19, at 19:04, Dardo D Kleiner - CONTRACTOR wrote:> I''m both personally and professionally encouraged to hear ClusterStor stand > up and publicly state intent to support Lustre on SLES. The million dollar > question is in regards to *server* support - in particular wrt the 2.x > series. As a token of my interest, as well as a testament to my limited > ability to maintain this in the long run, I submit the attached patches to > the recent 1.10.0.40 beta release that enable building (and confirmed to be > runnable) the server on current SLES11 kernel (2.6.27.45-0.1-default). One > caveat is that quota support is not compilable and appears to be a bit more > difficult job than I can probably manage. And I most certainly didn''t run > a full regression suite, but a straightforward single stream read/write > appears to work fine.In fact, it is best to check bugzilla first and/or post to the list. We update Lustre to match the latest RHEL/SLES kernels for each releases. Work is already underway to address the significant changes in SLES11 SP1, since this moves the kernel from 2.6.27 to 2.6.32.> Up to .38 it was mostly monkey work - but .40 introduced additional patches > to the RHEL ext4 implementation that has more substantially diverged from > the one in current SLES11. Perhaps SLES11SP1 will converge better...That is my hope. More below...> There''s perhaps a Bugzilla report where this is better posted, and tomorrow > I''ll look around a bit more for that, but I felt like getting it out there > asap. This has been a topic of much interest in my community and I''m > starting to feel a bit alone in my desire to keep SLE across the board in > my environment. I''ve invested quite a bit of time and effort there and > though many are fine with black box appliances, in our research environment > I prefer to have more transparency.To correct any confusion that is out there - there is no statement or intention to stop supporting SLES10/11 on the 1.8 release. There is neither any statement or intention to stop supporting SLES on the client, even in the 2.0 release. There will be no official support from Oracle for SLES11 on the 2.0 servers. Since the SLES11 SP1 kernel is moving to the same base 2.6.32 kernel as RHEL6 (which IS going to be supported in Lustre 2.0) it is my hope that the kernel patches for these two distros will be the same. I applaud that others are stepping forward to start contributing to Lustre, but let''s not waste efforts doing the same work multiple times. I think the only way to avoid this is if we continue to communicate in channels such as this list and bugzilla what is being worked on.> On 5/19/2010 11:21 AM, Kevin Canady wrote: >> Quick "Public Service Announcement" >> >> ClusterStor is and will be providing support services for SLES on both 1.8x and 2.x releases. If anyone would like to receive additional information please contact me at kevin.canady at clusterstor.com or 415.505.7701 >> >> Best regards, >> Kevin >> >> P. Kevin Canady >> Vice President, >> ClusterStor Inc. >> 415.505.7701 >> kevin.canady at clusterstor.com >> >> On May 19, 2010, at 8:01 AM, Andreas Dilger wrote: >> >>> I''ve used a SLES kernel on an FC install for a long time on my home >>> system. With newer distros there are also fewer changes to the base >>> kernel, so there shouldn''t be as much trouble to use e.g. the SLES 11 >>> SP1 kernel (2.6.32) when it is released. >>> >>> Cheers, Andreas >>> >>> On 2010-05-19, at 6:01, Heiko Schr?ter<schroete at iup.physik.uni-bremen.d >>> e> wrote: >>> >>>> Am Mittwoch 19 Mai 2010, um 10:33:04 schrieben Sie: >>>>> On 2010-05-19, at 01:40, Heiko Schr?ter wrote: >>>>>> we would like to know which way lustre is heading. >>>>>> >>>>>>> From the s/w repository we see that only redhat and suse ditros >>>>>>> seems to be supported. >>>>>> >>>>>> Is this the official policy of the lustre development to stick to >>>>>> (only) these two distros ? >>>>> >>>>> On the client side, we will support the main distros that our >>>>> customers are using, namely RHEL/OEL/CentOS 5.x (and 6.x after >>>>> release), and SLES 10/11. We make a best-effort attempt to have >>>>> the client work with all client kernels, but since our resources >>>>> are limited we cannot test kernels other than the supported ones. >>>>> I don''t see any huge demand for e.g. an officially-supported Ubuntu >>>>> client kernel, but there has long been an unofficial Debian lustre >>>>> package. >>>>> >>>>> On the server side, we will continue to support RHEL5.x and >>>>> SLES10/11 for the Lustre 1.8 release, and RHEL 5.x (6.x is being >>>>> worked on) for the Lustre 2.x release. Since maintaining kernel >>>>> patches for other kernels is a lot of work, we do not attempt to >>>>> provide patches for other than official kernels. However, there >>>>> have in the past been ports of the kernel patches to other kernels >>>>> by external contributors (e.g. FC11, FC12, etc) and this will >>>>> hopefully continue in the future. >>>> >>>> The server side is the more critical part as we are using gentoo >>>> +lustre running a vanilla kernel 2.6.22.19 with the lustre patches >>>> version 1.6.6. >>>> As far as we are concerned it would be nice to have the pathces for >>>> the "vanilla-kernels" in 1.8.3+. This would be just fine. >>>> >>>> On the other hand if maintaining is the key problem on your side >>>> what would be a major argument against using a patched sles/rhel on >>>> a lustre server not running the sles/rhel distro ? >>>> I know a lot of things can happen but are these rhel/sles patches do >>>> brake some key features of the kernel which would only work under >>>> that specific distro ? >>>> I''ve positivley tested a lustre client with a sles patched kernel on >>>> a gentoo distro. But i''am a bit nervous about testing it on our live >>>> lustre server system. >>>> >>>>> >>>>>> If not, then the sun src patches are still missing in the lustre >>>>>> AND e2fsprogs branches. >>>>> >>>>> I''m not sure what you mean. The e2fsprogs patches have always been >>>>> in a separate repository from the core Lustre code, and all of the >>>>> Lustre/ldiskfs kernel patches are in the Git repository. >>>> >>>> I know. But the patches are missing for 1.41.10 in that repo. i.e. >>>> as this here "e2fsprogs-1.41.6.sun1-patches.tgz" >>>> >>>> Thanks very much for your help. >>>> Regards >>>> Heiko >>> _______________________________________________ >>> Lustre-discuss mailing list >>> Lustre-discuss at lists.lustre.org >>> http://lists.lustre.org/mailman/listinfo/lustre-discuss >> >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss >> >> > <lustre-sles11.patch.1.10.0.40>_______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discussCheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc.
On Thu, 2010-05-20 at 14:45 -0600, Andreas Dilger wrote:> > On 2010-05-20, at 11:33, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote: > > Yes. I used them at the beginning, but after lustre 1.8.0.1 vanilla > > servers are not any more supported to be used as servers and I started > > to use RH5 kernels with lustre-1.8.1.1, both for clients and servers. > > That''s too bad that the Debiana maintainers have stopped making > updates.I don''t know that they did. I have to admit that I don''t read these too closely, but it seems that 1.8.3 did get accepted into some Debian release (process): http://lists.alioth.debian.org/pipermail/pkg-lustre-maintainers/2010-May/000317.html Maybe, being unfamiliar with the Debian processes, I am mis-understanding what that message is saying. There were others at the same time. The archive for May is at http://lists.alioth.debian.org/pipermail/pkg-lustre-maintainers/2010-May/thread.html> Doubly so because we worked to add the fixes needed to build > on Debian into the Lustre sources, so it is possible to do "make debs" > to get Debian packages using all of the standard Debian packaging tools.I could be wrong (as I have not inspected the actual Debian packages lately) but I don''t think they are using our work there (yet?) unfortunately. :-( I would hope that the diff between us and them would be small, and if not that they would report bugs and submit patches. But perhaps also, part of the problem is that our ability to focus time and effort on that stuff is limited by the allocation of resources to supported aspects of the project. i.e. we can only provide "best effort" time and effort. Cheers, b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100520/867d4804/attachment.bin
Ramiro Alba Queipo
2010-May-21 08:00 UTC
[Lustre-discuss] Future of lustre 1.8.3+(Debian and SLES/RH kernels)
Hi Andreas, On Thu, 2010-05-20 at 14:45 -0600, Andreas Dilger wrote:> > On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote: > >> The SLES11 kernel is at 2.6.27 so it could be usable for this. > >> Also, I > > > > Ok, I am getting > > http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 > > > > but, please. Where can I get a suitable config file to apply both for > > servers and clients? > > The config files are in the Lustre source tree in lustre/ > kernel_patches/kernel_configs/Of course. I did not remember. Anyway, I downloaded: kernel-default-base-2.6.27.39-0.3_lustre.1.8.3.x86_64.rpm and extracted: config-2.6.27.39-0.3_lustre.1.8.3-default which I modified at: CONFIG_LOCALVERSION="-0.3_lustre.1.8.3-default" to CONFIG_LOCALVERSION="-0.3.1-lustre.1.8.3" because debian ''make-kpkg'' command refused to create the package. By the way. I''ve just compared that config file with the one in lustre source tree: kernel-2.6.27-2.6-sles11-x86_64.config and I found a difference: CONFIG_THINKPAD_ACPI_BAY=y NOT the one in rpm package. I do not think this is meaningful, do I? Anyway, in future, which is the best config file to get from?> > You can just use the .config file from your client kernel (ie > patchless) since you don''t need the patched server kernel on the > clients. > > >> thought that there were Debian packages for Lustre, why not use > >> those? > > > > Yes. I used them at the beginning, but after lustre 1.8.0.1 vanilla > > servers are not any more supported to be used as servers and I started > > to use RH5 kernels with lustre-1.8.1.1, both for clients and servers. > > That''s too bad that the Debiana maintainers have stopped making > updates. Doubly so because we worked to add the fixes needed to build > on Debian into the Lustre sources, so it is possible to do "make debs" > to get Debian packages using all of the standard Debian packaging tools.No. They did not. Debian Squeeze (testing) is offering lustre-1.8.2, but ONLY for clients and vanilla kernels 2.6.26 and 2.6.27. I my case I intend to build the whole cluster (both servers and clients) with Ubuntu 10.04, so, though it is not a requirement, it is more practical, I think, to use an only kernel for every node. I started, when using lustre 1.6 series using vanilla kernel 2.6.22-14, but then, at lustre-1.8.1 vanilla kernels are not supported any more to be used in servers. So I started using RH5 kernels with Ubuntu 8.04 using udev-117 and lustre 1.8.1.1. I make some test and everything seemed to be fine. Now I intend to upgrade to Ubuntu 10.04 using udev-151, and I found the problem with udev and kernel versions under 2.6.27, but using SLES11 kernel boots and seems to work (not tested lustre yet) Sometimes I can not avoid to think in using RH5 or SLES11 on our cluster to simplify problems, but I am too used to Debian/Ubuntu and I loved them. So I''d like to know if: - Anyone have been had a similar experience? - Any comments about the approach I am using to start lustre on Ubuntu?> > > In my case using Ubuntu 10.04 with kernel 2.6.32 NOT suported as a > > lustre patchless client, I prefer using an only kernel for the > > whole cluster, > > do I? > > > That is by no means a requirement. > > > Thanks for your answer. > > > > Regards > > > >> > >> Cheers, Andreas > >> > >> On 2010-05-20, at 9:48, Ramiro Alba Queipo <raq at cttc.upc.edu> wrote: > >> > >>> Hi all, > >>> > >>> On Wed, 2010-05-19 at 14:43 +0200, Bernd Schubert wrote: > >>> > >>>> That is what I would recommend and what several groups do (usually > >>>> with > >>>> Debian, though). > >>>> > >>>>> not running the sles/rhel distro ? I know a lot of things can > >>>>> happen but > >>>>> are these rhel/sles patches do brake some key features of the > >>>>> kernel which > >>>>> would only work under that specific distro ? I''ve positivley > >>>>> tested a > >>>>> lustre client with a sles patched kernel on a gentoo distro. But > >>>>> i''am a > >>>>> bit nervous about testing it on our live lustre server system. > >>>> > >>>> The only thing that really might cause trouble is udev, since sysfs > >>>> maintainers like to break old udev versions. I think upcoming > >>>> Debian Squeeze > >>>> requires 2.6.27 at a minimum. > >>> > >>> Argg!!!, I think I am stacked with this situation. I compiled > >>> linux-2.6.18-164.11.1.el5.tar.bz2 under Ubuntu 10.04 (from Debian > >>> Squeeze) using make-kpkg and after dealing with postinst.d hooks to > >>> create initrd image (not created by default!!!), I tried to boot and > >>> then I got the following before dropping into a initramfs shell: > >>> > >>> --- > >>> --- > >>> --- > >>> ------------------------------------------------------------------ > >>> Begin: Mounting root file system... ... > >>> Begin: Running /scripts/local-top ... > >>> Done. > >>> libudev: udev_monitor_new_from_netlink: error getting socket: > >>> Invalid > >>> argument wait-for-root[431] : segfault > >>> Gave up waiting form root device. Common problems: > >>> - Boot args (cat /proc/cmdline) > >>> - Check rootdelay= (did the system wait long enough?) > >>> - Check root= (did the system wait for the right device?) > >>> -Missing modules (cat /proc/modules; ls /dev) > >>> ALERT! /dev/disk/by-uuid/0cff75ed-ba7f-4799-b596-cf2b214b9768 does > >>> not > >>> exist. Dropping to a shell! > >>> > >>> > >>> BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) buit-in shell (ask) > >>> Enter ''Help'' for a list of built-in commands. > >>> > >>> (initramfs) > >>> --- > >>> --- > >>> --- > >>> --- > >>> ------------------------------------------------------------------ > >>> > >>> Is this the problem you are talking about? Could you give me some > >>> ideas > >>> of how can be solved? > >>> > >>> Regards > >>> > >>> > >>> -- > >>> Ramiro Alba > >>> > >>> Centre Tecnol?gic de Tranfer?ncia de Calor > >>> http://www.cttc.upc.edu > >>> > >>> > >>> Escola T?cnica Superior d''Enginyeries > >>> Industrial i Aeron?utica de Terrassa > >>> Colom 11, E-08222, Terrassa, Barcelona, Spain > >>> Tel: (+34) 93 739 86 46 > >>> > >>> > >>> -- > >>> Aquest missatge ha estat analitzat per MailScanner > >>> a la cerca de virus i d''altres continguts perillosos, > >>> i es considera que est? net. > >>> > >>> _______________________________________________ > >>> Lustre-discuss mailing list > >>> Lustre-discuss at lists.lustre.org > >>> http://lists.lustre.org/mailman/listinfo/lustre-discuss > >> > > -- > > Ramiro Alba > > > > Centre Tecnol?gic de Tranfer?ncia de Calor > > http://www.cttc.upc.edu > > > > > > Escola T?cnica Superior d''Enginyeries > > Industrial i Aeron?utica de Terrassa > > Colom 11, E-08222, Terrassa, Barcelona, Spain > > Tel: (+34) 93 739 86 46 > > > > > > -- > > Aquest missatge ha estat analitzat per MailScanner > > a la cerca de virus i d''altres continguts perillosos, > > i es considera que est? net. > > >-- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
Hi Ramiro, Ramiro Alba Queipo wrote:> On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote: > >> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I >> > Ok, I am getting > http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 > > but, please. Where can I get a suitable config file to apply both for > servers and clients? >you''ll find a precompiled Lustre patches SLES11 kernel for Debian Lenny package here: http://pkg-lustre.alioth.debian.org/backports/lustre-1.8.3/ We haven''t really tested this kernel ourself yet, but our support company did. You could give it a try on Ubuntu 10.04 as well. The kernel config will be available in /boot/config-<kernel version> once you installed it. Kind regards, Christopher -- Christopher Huhn Linux therapist GSI Helmholtzzentrum fuer Schwerionenforschung GmbH Planckstr. 1 64291 Darmstadt http://www.gsi.de/ Gesellschaft mit beschraenkter Haftung Sitz der Gesellschaft / Registered Office: Darmstadt Handelsregister / Commercial Register: Amtsgericht Darmstadt, HRB 1528 Geschaeftsfuehrung / Managing Directors: Professor Dr. Dr. h.c. Horst Stoecker, Christiane Neumann, Dr. Hartmut Eickhoff Vorsitzende des Aufsichtsrates / Supervisory Board Chair: Dr. Beatrix Vierkorn-Rudolph Stellvertreter / Deputy Chair: Dr. Rolf Bernhard
Hi Cristopher: I''ve had a look at the config file and found a lot of differences with the one available on lustre source. Especially I saw:> # CONFIG_RESOURCE_COUNTERS is not set > CONFIG_SYSFS_DEPRECATED=y > CONFIG_SYSFS_DEPRECATED_V2=ywhich is not going to work with de udev version on Ubuntu 10.04 (from Debian Squeeze) Anyway, I''ve finally compiled everything now using SLES11 kernel and it seems to work. By the way are you using Debian and Lustre? If positive, what is your feeling? Cheers On Fri, 2010-05-21 at 11:08 +0200, Christopher Huhn wrote:> Hi Ramiro, > > Ramiro Alba Queipo wrote: > > On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote: > > > >> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I > >> > > Ok, I am getting > > http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 > > > > but, please. Where can I get a suitable config file to apply both for > > servers and clients? > > > you''ll find a precompiled Lustre patches SLES11 kernel for Debian Lenny > package here: > http://pkg-lustre.alioth.debian.org/backports/lustre-1.8.3/ > > We haven''t really tested this kernel ourself yet, but our support > company did. > You could give it a try on Ubuntu 10.04 as well. > > The kernel config will be available in /boot/config-<kernel version> > once you installed it. > > Kind regards, > Christopher > > > -- > Christopher Huhn > Linux therapist > > GSI Helmholtzzentrum fuer Schwerionenforschung GmbH > Planckstr. 1 > 64291 Darmstadt > http://www.gsi.de/ > > Gesellschaft mit beschraenkter Haftung > > Sitz der Gesellschaft / Registered Office: Darmstadt > Handelsregister / Commercial Register: > Amtsgericht Darmstadt, HRB 1528 > > Geschaeftsfuehrung / Managing Directors: > Professor Dr. Dr. h.c. Horst Stoecker, > Christiane Neumann, > Dr. Hartmut Eickhoff > Vorsitzende des Aufsichtsrates / Supervisory Board Chair: > Dr. Beatrix Vierkorn-Rudolph > Stellvertreter / Deputy Chair: Dr. Rolf Bernhard > >-- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
Christopher Huhn
2010-May-21 12:34 UTC
[Lustre-discuss] Future of lustre 1.8.3+/Debian support
Hi Ramiro, Ramiro Alba Queipo wrote:> By the way are you using Debian and Lustre? If positive, what is your > feeling? >Right now we are running Lustre 1.6.7.2 on Debian Etch. The current size is net 1 PB (100+ OSS servers, gross 1.6 PB) and roughly 500 number crunchers running Debian Etch and Lenny. From the Lustre point of view the installation is rather low end "cheap and big" scratch space - no infiniband, no OSS/OST failover ... We plan to migrate to 1.8.3+ on Debian Lenny but this will still need some testing and preparations. Overall the cluster runs quite fine and we have no indication that the problems we had and have are specific to Debian. We are running Debian for almost 15 years and have no plans to run a larger quantity of servers on a non-Debian based distro (a handful of server run SLES for proprietary products with expensive support contracts). Ubuntu LTS is also an opportunity for server installations but we still have to evaluate this. What worries us is that the Lustre server patches do not appear to progress towards integration into the mainline kernel but rather away from it, which makes porting to Debian (and up-to-date kernels in general) more and more difficult. It is obvious that this is no major goal in Oracles business model, but I fear that in the long term Lustre development momentum will be diverted to alternative technologies like Ceph that integrate better into Linux kernel development just the way Xen failed to keep up with the Linux kernel and has more or less been superseded by KVM nowadays. Anyhow there is no convincing alternative to Lustre today for our use case. Regards, Christopher
Andreas Dilger
2010-May-21 14:50 UTC
[Lustre-discuss] Future of lustre 1.8.3+/Debian support
On 2010-05-21, at 6:34, Christopher Huhn <C.Huhn at gsi.de> wrote:> What worries us is that the Lustre server patches do not appear to > progress towards integration into the mainline kernel but rather away > from it, which makes porting to Debian (and up-to-date kernels in > general) more and more difficult.I would have to disagree. There is an open bug with detailed descriptions on how to remove the patches to the core kernel, and with the move to ext4-based ldiskfs many of the complex patches that we developed are now part of ext4. It''s true that there is no effort to submit Lustre upstream, but that is largely due to the huge amount of effort it would require to restructure Lustre to meet the whims of the kernel maintainers. By reducing or eliminating the server kernel patches at least it will mean the maintenance for new kernels will be limited to the API changes that appear with each new kernel.
On 21/05/10 10:08, Christopher Huhn wrote:> Hi Ramiro, > > Ramiro Alba Queipo wrote: >> On Thu, 2010-05-20 at 10:16 -0600, Andreas Dilger wrote: >> >>> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I >>> >> Ok, I am getting >> http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 >> >> but, please. Where can I get a suitable config file to apply both for >> servers and clients?One thing to watch out for in your kernel configs is to make sure that: CONFIG_SECURITY_FILE_CAPABILITIES=N otherwise you will run into: https://bugzilla.lustre.org/show_bug.cgi?id=21439 (each write call causes 2 getxattr calls, which will pound your MDS into the ground). The SLES11, debian/lenny and ubuntu kernels all have this feature set, so if you are building clients against those kernels, you may be in trouble. Cheers, Guy -- Dr. Guy Coates, Informatics System Group The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK Tel: +44 (0)1223 834244 x 6925 Fax: +44 (0)1223 496802 -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Guy Coates wrote:> One thing to watch out for in your kernel configs is to make sure that: > > CONFIG_SECURITY_FILE_CAPABILITIES=NI hope this is not the case for the now obsolete: CONFIG_EXT3_FS_SECURITY=y which appears to be enabled by default on RHEL5.x Its not entirely clear to me what this is for but would metadata performance be better without it? GREG> > otherwise you will run into: > > https://bugzilla.lustre.org/show_bug.cgi?id=21439 > > (each write call causes 2 getxattr calls, which will pound your MDS into > the ground). > > The SLES11, debian/lenny and ubuntu kernels all have this feature set, > so if you are building clients against those kernels, you may be in > trouble. > > > Cheers, > > Guy >-- Greg Matthews 01235 778658 Senior Computer Systems Administrator Diamond Light Source, Oxfordshire, UK
The problem with SELinux is that it is trying to access the security xattr for each file access but Lustre does not cache xattrs on the client. The other main question about SELinux is whether it even makes sense in a distributed environment. For now (see bug) we have just disabled the access to this specific attribute in Lustre. It would be nice if someone with more understanding of SELinux would investigate if there is some global settings file that could be modified to exclude Lustre from the security policy checking, and then we can push this to the upstream distros. Cheers, Andreas On 2010-05-26, at 8:43, Gregory Matthews <greg.matthews at diamond.ac.uk> wrote:> Guy Coates wrote: >> One thing to watch out for in your kernel configs is to make sure >> that: >> >> CONFIG_SECURITY_FILE_CAPABILITIES=N > > I hope this is not the case for the now obsolete: > > CONFIG_EXT3_FS_SECURITY=y > > which appears to be enabled by default on RHEL5.x > > Its not entirely clear to me what this is for but would metadata > performance be better without it? > > GREG > >> >> otherwise you will run into: >> >> https://bugzilla.lustre.org/show_bug.cgi?id=21439 >> >> (each write call causes 2 getxattr calls, which will pound your MDS >> into >> the ground). >> >> The SLES11, debian/lenny and ubuntu kernels all have this feature >> set, >> so if you are building clients against those kernels, you may be in >> trouble. >> >> >> Cheers, >> >> Guy >> > > > -- > Greg Matthews 01235 778658 > Senior Computer Systems Administrator > Diamond Light Source, Oxfordshire, UK > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
On 26/05/10 16:18, Andreas Dilger wrote:> The problem with SELinux is that it is trying to access the security > xattr for each file access but Lustre does not cache xattrs on the client. > > The other main question about SELinux is whether it even makes sense in > a distributed environment.Just to be clear, SELinux was disabled on these machines (selinux=0 kernel option); simply having the kernel-config set still triggers the code path/bug. Cheers, Guy -- Dr. Guy Coates, Informatics System Group The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK Tel: +44 (0)1223 834244 x 6925 Fax: +44 (0)1223 496802 -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Hi Guy, On Wed, 2010-05-26 at 14:59 +0100, Guy Coates wrote:> >> > >>> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I > >>> > >> Ok, I am getting > >> http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 > >> > >> but, please. Where can I get a suitable config file to apply both for > >> servers and clients? > > One thing to watch out for in your kernel configs is to make sure that: > > CONFIG_SECURITY_FILE_CAPABILITIES=NOK. But the question is if this issue still applies for lustre-1.8.3 and SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite surprising that if this problems persist, Oracle is offering lustre packages for SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ??????? I am just about to start testing, so I''d like to clarify this. Cheers> > otherwise you will run into: > > https://bugzilla.lustre.org/show_bug.cgi?id=21439 > > (each write call causes 2 getxattr calls, which will pound your MDS into > the ground). > > The SLES11, debian/lenny and ubuntu kernels all have this feature set, > so if you are building clients against those kernels, you may be in > trouble. > > > Cheers, > > Guy > > -- > Dr. Guy Coates, Informatics System Group > The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK > Tel: +44 (0)1223 834244 x 6925 > Fax: +44 (0)1223 496802 > > > -- > The Wellcome Trust Sanger Institute is operated by Genome Research > Limited, a charity registered in England with number 1021457 and a > company registered in England with number 2742969, whose registered > office is 215 Euston Road, London, NW1 2BE. >-- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
On 26/05/10 16:31, Ramiro Alba Queipo wrote:> Hi Guy, > > On Wed, 2010-05-26 at 14:59 +0100, Guy Coates wrote: >>>> >>>>> The SLES11 kernel is at 2.6.27 so it could be usable for this. Also, I >>>>> >>>> Ok, I am getting >>>> http://downloads.lustre.org/public/kernels/sles11/linux-2.6.27.39-0.3.1.tar.bz2 >>>> >>>> but, please. Where can I get a suitable config file to apply both for >>>> servers and clients? >> >> One thing to watch out for in your kernel configs is to make sure that: >> >> CONFIG_SECURITY_FILE_CAPABILITIES=N > > OK. But the question is if this issue still applies for lustre-1.8.3 and > SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite surprising > that if this problems persist, Oracle is offering lustre packages for > SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ??????? > I am just about to start testing, so I''d like to clarify this.The binary SLES packages are fine; it is the source packages that may be problematic, depending on your config. There is a bug filed against this now (22913), so no doubt it will be fixed in a subsequent release. In regard to your testing, it is easy to check if a client is mis-behaving; run: #cat /dev/zero > /lustre/filesystem & and watch the client IO stats with: #watch -n 1 cat /proc/fs/lustre/llite/*/stats If getxattr is going up with write_bytes, then you have a problem. Cheers, Guy -- Dr. Guy Coates, Informatics System Group The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK Tel: +44 (0)1223 834244 x 6925 Fax: +44 (0)1223 496802 -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
On Wed, 2010-05-26 at 16:48 +0100, Guy Coates wrote:> >> One thing to watch out for in your kernel configs is to make sure that: > >> > >> CONFIG_SECURITY_FILE_CAPABILITIES=N > > > > OK. But the question is if this issue still applies for lustre-1.8.3 and > > SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite surprising > > that if this problems persist, Oracle is offering lustre packages for > > SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ??????? > > I am just about to start testing, so I''d like to clarify this. > > The binary SLES packages are fine; it is the source packages that may be > problematic, depending on your config. There is a bug filed against thisSorry Guy. May be there is something I am missing, but SLES11 rpm kernel server packages for lustre-1.8.3 are created using a config with ONFIG_SECURITY_FILE_CAPABILITIES=y (See yourself on the attachement extracted from kernel-default-base-2.6.27.39-0.3_lustre.1.8.3.x86_64.rpm). So, the should have the same problem. Cheers> now (22913), so no doubt it will be fixed in a subsequent release. > > In regard to your testing, it is easy to check if a client is mis-behaving; > > run: > > #cat /dev/zero > /lustre/filesystem & > > and watch the client IO stats with: > > #watch -n 1 cat /proc/fs/lustre/llite/*/stats >Many thanks for the info. I''ll do try> > If getxattr is going up with write_bytes, then you have a problem. >Cheers> -- > Dr. Guy Coates, Informatics System Group > The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK > Tel: +44 (0)1223 834244 x 6925 > Fax: +44 (0)1223 496802 > > > -- > The Wellcome Trust Sanger Institute is operated by Genome Research > Limited, a charity registered in England with number 1021457 and a > company registered in England with number 2742969, whose registered > office is 215 Euston Road, London, NW1 2BE. >-- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net. -------------- next part -------------- # # Automatically generated make config: don''t edit # Linux kernel version: 2.6.27.39 # Fri Apr 9 18:56:48 2010 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" # CONFIG_GENERIC_LOCKBREAK is not set 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_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 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_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_AOUT=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_X86_SMP=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y # CONFIG_KTIME_SCALAR is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="-0.3_lustre.1.8.3-default" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SUSE_KERNEL=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_RT_GROUP_SCHED is not set # CONFIG_USER_SCHED is not set CONFIG_CGROUP_SCHED=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y CONFIG_MM_OWNER=y CONFIG_CGROUP_MEM_RES_CTLR=y # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_PROC_PID_CPUSET=y CONFIG_RELAY=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # 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_COMPAT_BRK=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROFILING=y # CONFIG_TRACEPOINTS is not set CONFIG_MARKERS=y CONFIG_OPROFILE=m CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_KRETPROBES=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y # CONFIG_HAVE_DMA_ATTRS is not set CONFIG_USE_GENERIC_SMP_HELPERS=y # CONFIG_HAVE_CLK is not set CONFIG_PROC_PAGE_MONITOR=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # CONFIG_UTRACE is not set CONFIG_BLOCK=y CONFIG_BLK_DEV_IO_TRACE=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set CONFIG_DEFAULT_DEADLINE=y # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="deadline" CONFIG_PREEMPT_NOTIFIERS=y CONFIG_CLASSIC_RCU=y CONFIG_FREEZER=y # # 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_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_X86_PC=y # CONFIG_X86_XEN is not set # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_64_XEN is not set # CONFIG_X86_VSMP is not set # CONFIG_PARAVIRT_GUEST is not set CONFIG_MEMTEST=y # 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_MWINCHIP2 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 is not set CONFIG_GENERIC_CPU=y CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=128 CONFIG_X86_INTERNODE_CACHE_BYTES=128 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y CONFIG_CALGARY_IOMMU=y # CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT is not set CONFIG_AMD_IOMMU=y CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y CONFIG_MAXSMP=y CONFIG_NR_CPUS=512 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_DIRECT_GBPAGES=y CONFIG_NUMA=y CONFIG_K8_NUMA=y CONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y CONFIG_NUMA_EMU=y CONFIG_NODES_SHIFT=9 CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y 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_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MIGRATION=y CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MMU_NOTIFIER=y CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 CONFIG_X86_RESERVE_LOW_64K=y CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set CONFIG_X86_PAT=y CONFIG_EFI=y CONFIG_SECCOMP=y # CONFIG_SECCOMP_DISABLE_TSC is not set # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y CONFIG_COMPAT_VDSO=y # # Hardware Performance Monitoring support # CONFIG_PERFMON=y # CONFIG_PERFMON_DEBUG is not set CONFIG_PERFMON_DEBUG_FS=y CONFIG_X86_PERFMON_P4=m CONFIG_X86_PERFMON_PEBS_P4=m CONFIG_X86_PERFMON_CORE=m CONFIG_X86_PERFMON_PEBS_CORE=m CONFIG_X86_PERFMON_INTEL_ATOM=m CONFIG_X86_PERFMON_INTEL_ARCH=m CONFIG_X86_PERFMON_AMD64=m CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y # # Power management options # CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_DOCK=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_THERMAL=m CONFIG_ACPI_NUMA=y CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_CUSTOM_DSDT_FILE="" # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_CUSTOM_DSDT_INITRD=y CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_DEBUG=y # CONFIG_ACPI_DEBUG_FUNC_TRACE is not set CONFIG_ACPI_EC=y CONFIG_ACPI_PCI_SLOT=m CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=m CONFIG_ACPI_HOTPLUG_MEMORY=m CONFIG_ACPI_SBS=m # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # 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=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_POWERNOW_K8=m CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_P4_CLOCKMOD is not set # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_DOMAINS=y # CONFIG_DMAR is not set CONFIG_INTR_REMAP=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=m CONFIG_PCIEAER=y CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY=y # CONFIG_PCI_DEBUG is not set CONFIG_HT_IRQ=y CONFIG_ISA_DMA_API=y CONFIG_K8_NB=y CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set 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=m CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_ACPI=m CONFIG_HOTPLUG_PCI_ACPI_IBM=m CONFIG_HOTPLUG_PCI_CPCI=y CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m CONFIG_HOTPLUG_PCI_SHPC=m # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y CONFIG_BINFMT_MISC=m 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=m CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m CONFIG_XFRM_SUB_POLICY=y CONFIG_XFRM_MIGRATE=y # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m CONFIG_NET_KEY_MIGRATE=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y CONFIG_IP_MROUTE=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y 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=m CONFIG_INET_TCP_DIAG=m CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m # CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set CONFIG_IP_VS=m # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS application helper # CONFIG_IP_VS_FTP=m CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m CONFIG_IPV6_MIP6=m CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y # CONFIG_IPV6_MROUTE is not set # CONFIG_NETLABEL is not set CONFIG_NETWORK_SECMARK=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=y # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=m CONFIG_NF_CT_ACCT=y CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CT_PROTO_DCCP=m CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CONNTRACK_SLP=m CONFIG_NF_CT_NETLINK=m CONFIG_NETFILTER_XTABLES=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NOTRACK=m CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_SECMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m # # IP: Netfilter Configuration # CONFIG_NF_CONNTRACK_IPV4=m # CONFIG_NF_CONNTRACK_PROC_COMPAT is not set CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_RECENT=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_ADDRTYPE=m CONFIG_IP_NF_MATCH_IPV4OPTIONS=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_DCCP=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_PROTO_UDPLITE=m CONFIG_NF_NAT_PROTO_SCTP=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_SECURITY=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_SECURITY=m # # DECnet: Netfilter Configuration # # CONFIG_DECNET_NF_GRABULATOR is not set # # Bridge: Netfilter Configuration # CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_ULOG=m CONFIG_BRIDGE_EBT_NFLOG=m CONFIG_IP_DCCP=m CONFIG_INET_DCCP_DIAG=m CONFIG_IP_DCCP_ACKVEC=y # # DCCP CCIDs Configuration (EXPERIMENTAL) # CONFIG_IP_DCCP_CCID2=m # CONFIG_IP_DCCP_CCID2_DEBUG is not set CONFIG_IP_DCCP_CCID3=m # CONFIG_IP_DCCP_CCID3_DEBUG is not set CONFIG_IP_DCCP_CCID3_RTO=100 CONFIG_IP_DCCP_TFRC_LIB=m # # DCCP Kernel Hacking # # CONFIG_IP_DCCP_DEBUG is not set # CONFIG_NET_DCCPPROBE 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_TIPC is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m # CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m CONFIG_ATM_MPOA=m CONFIG_ATM_BR2684=m # CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_STP=m CONFIG_GARP=m CONFIG_BRIDGE=m CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y CONFIG_DECNET=m # CONFIG_DECNET_ROUTER is not set CONFIG_LLC=y CONFIG_LLC2=m CONFIG_IPX=m CONFIG_IPX_INTERN=y CONFIG_ATALK=m CONFIG_DEV_APPLETALK=m CONFIG_IPDDP=m CONFIG_IPDDP_ENCAP=y CONFIG_IPDDP_DECAP=y CONFIG_X25=m CONFIG_LAPB=m CONFIG_ECONET=m # CONFIG_ECONET_AUNUDP is not set # CONFIG_ECONET_NATIVE is not set CONFIG_WAN_ROUTER=m CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_MULTIQ=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_INGRESS=m # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m CONFIG_CLS_U32_PERF=y CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_IPT=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_ACT_SKBEDIT=m # CONFIG_NET_CLS_IND is not set CONFIG_NET_SCH_FIFO=y CONFIG_DCB=m CONFIG_DCBNL=y # # Network testing # CONFIG_NET_PKTGEN=m CONFIG_NET_TCPPROBE=m CONFIG_HAMRADIO=y # # Packet Radio protocols # CONFIG_AX25=m CONFIG_AX25_DAMA_SLAVE=y CONFIG_NETROM=m CONFIG_ROSE=m # # AX.25 network device drivers # CONFIG_MKISS=m CONFIG_6PACK=m CONFIG_BPQETHER=m CONFIG_BAYCOM_SER_FDX=m CONFIG_BAYCOM_SER_HDX=m CONFIG_BAYCOM_PAR=m CONFIG_YAM=m CONFIG_CAN=m CONFIG_CAN_RAW=m CONFIG_CAN_BCM=m # # CAN Device Drivers # CONFIG_CAN_VCAN=m # CONFIG_CAN_DEBUG_DEVICES is not set CONFIG_IRDA=m # # IrDA protocols # CONFIG_IRLAN=m CONFIG_IRNET=m CONFIG_IRCOMM=m CONFIG_IRDA_ULTRA=y # # IrDA options # CONFIG_IRDA_CACHE_LAST_LSAP=y # CONFIG_IRDA_FAST_RR is not set # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # CONFIG_DONGLE=y CONFIG_ESI_DONGLE=m CONFIG_ACTISYS_DONGLE=m CONFIG_TEKRAM_DONGLE=m CONFIG_TOIM3232_DONGLE=m CONFIG_LITELINK_DONGLE=m CONFIG_MA600_DONGLE=m CONFIG_GIRBIL_DONGLE=m CONFIG_MCP2120_DONGLE=m CONFIG_OLD_BELKIN_DONGLE=m CONFIG_ACT200L_DONGLE=m CONFIG_KINGSUN_DONGLE=m CONFIG_KSDAZZLE_DONGLE=m CONFIG_KS959_DONGLE=m # # FIR device drivers # CONFIG_USB_IRDA=m CONFIG_SIGMATEL_FIR=m CONFIG_NSC_FIR=m CONFIG_WINBOND_FIR=m CONFIG_SMC_IRCC_FIR=m CONFIG_ALI_FIR=m CONFIG_VLSI_FIR=m CONFIG_VIA_FIR=m CONFIG_MCS_FIR=m CONFIG_BT=m CONFIG_BT_L2CAP=m CONFIG_BT_SCO=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_CMTP=m CONFIG_BT_HIDP=m # # Bluetooth device drivers # CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIBTSDIO=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_LL=y CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m CONFIG_BT_HCIBFUSB=m CONFIG_BT_HCIDTL1=m CONFIG_BT_HCIBT3C=m CONFIG_BT_HCIBLUECARD=m CONFIG_BT_HCIBTUART=m CONFIG_BT_HCIVHCI=m CONFIG_AF_RXRPC=m # CONFIG_AF_RXRPC_DEBUG is not set CONFIG_RXKAD=m CONFIG_FIB_RULES=y # # Wireless # CONFIG_CFG80211=m CONFIG_NL80211=y CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y CONFIG_MAC80211=m # # Rate control algorithm selection # CONFIG_MAC80211_RC_PID=y CONFIG_MAC80211_RC_DEFAULT_PID=y CONFIG_MAC80211_RC_DEFAULT="pid" CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set CONFIG_IEEE80211_CRYPT_WEP=m CONFIG_IEEE80211_CRYPT_CCMP=m CONFIG_IEEE80211_CRYPT_TKIP=m CONFIG_RFKILL=m CONFIG_RFKILL_INPUT=m CONFIG_RFKILL_LEDS=y CONFIG_NET_9P=m CONFIG_NET_9P_VIRTIO=m # CONFIG_NET_9P_DEBUG is not set CONFIG_NETVM=y # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" # CONFIG_STANDALONE is not set CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y 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=y CONFIG_PROC_EVENTS=y CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set CONFIG_MTD_CONCAT=m CONFIG_MTD_PARTITIONS=y CONFIG_MTD_REDBOOT_PARTS=m CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1 # CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set # CONFIG_MTD_REDBOOT_PARTS_READONLY is not set CONFIG_MTD_AR7_PARTS=m # # User Modules And Translation Layers # CONFIG_MTD_CHAR=m CONFIG_MTD_BLKDEVS=m CONFIG_MTD_BLOCK=m # CONFIG_MTD_BLOCK_RO is not set # CONFIG_FTL is not set # CONFIG_NFTL is not set # CONFIG_INFTL is not set CONFIG_RFD_FTL=m # CONFIG_SSFDC is not set CONFIG_MTD_OOPS=m # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=m CONFIG_MTD_JEDECPROBE=m CONFIG_MTD_GEN_PROBE=m CONFIG_MTD_CFI_ADV_OPTIONS=y CONFIG_MTD_CFI_NOSWAP=y # CONFIG_MTD_CFI_BE_BYTE_SWAP is not set # CONFIG_MTD_CFI_LE_BYTE_SWAP is not set # CONFIG_MTD_CFI_GEOMETRY is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set # CONFIG_MTD_OTP is not set CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_CFI_STAA=m CONFIG_MTD_CFI_UTIL=m # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set CONFIG_MTD_ABSENT=m # # Mapping drivers for chip access # CONFIG_MTD_COMPLEX_MAPPINGS=y CONFIG_MTD_PHYSMAP=m CONFIG_MTD_PHYSMAP_START=0x8000000 CONFIG_MTD_PHYSMAP_LEN=0x4000000 CONFIG_MTD_PHYSMAP_BANKWIDTH=2 # CONFIG_MTD_SC520CDP is not set # CONFIG_MTD_NETSC520 is not set CONFIG_MTD_TS5500=m # CONFIG_MTD_SBC_GXX is not set CONFIG_MTD_AMD76XROM=m CONFIG_MTD_ICHXROM=m CONFIG_MTD_ESB2ROM=m CONFIG_MTD_CK804XROM=m CONFIG_MTD_SCB2_FLASH=m # CONFIG_MTD_NETtel is not set # CONFIG_MTD_DILNETPC is not set # CONFIG_MTD_L440GX is not set CONFIG_MTD_PCI=m CONFIG_MTD_INTEL_VR_NOR=m # CONFIG_MTD_PLATRAM is not set # # Self-contained MTD device drivers # CONFIG_MTD_PMC551=m CONFIG_MTD_PMC551_BUGFIX=y # CONFIG_MTD_PMC551_DEBUG is not set # CONFIG_MTD_DATAFLASH is not set # CONFIG_MTD_M25P80 is not set CONFIG_MTD_SLRAM=m CONFIG_MTD_PHRAM=m CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 CONFIG_MTD_BLOCK2MTD=m # # Disk-On-Chip Device Drivers # CONFIG_MTD_DOC2000=m CONFIG_MTD_DOC2001=m CONFIG_MTD_DOC2001PLUS=m CONFIG_MTD_DOCPROBE=m CONFIG_MTD_DOCECC=m CONFIG_MTD_DOCPROBE_ADVANCED=y CONFIG_MTD_DOCPROBE_ADDRESS=0x0000 CONFIG_MTD_DOCPROBE_HIGH=y CONFIG_MTD_DOCPROBE_55AA=y CONFIG_MTD_NAND=m # CONFIG_MTD_NAND_VERIFY_WRITE is not set CONFIG_MTD_NAND_ECC_SMC=y # CONFIG_MTD_NAND_MUSEUM_IDS is not set CONFIG_MTD_NAND_IDS=m CONFIG_MTD_NAND_DISKONCHIP=m # CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0 CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE=y CONFIG_MTD_NAND_CAFE=m CONFIG_MTD_NAND_NANDSIM=m CONFIG_MTD_NAND_PLATFORM=m CONFIG_MTD_ALAUDA=m CONFIG_MTD_ONENAND=m # CONFIG_MTD_ONENAND_VERIFY_WRITE is not set CONFIG_MTD_ONENAND_OTP=y CONFIG_MTD_ONENAND_2X_PROGRAM=y CONFIG_MTD_ONENAND_SIM=m # # UBI - Unsorted block images # CONFIG_MTD_UBI=m CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_RESERVE=1 # CONFIG_MTD_UBI_GLUEBI is not set # # UBI debugging options # # CONFIG_MTD_UBI_DEBUG is not set CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_SERIAL=m CONFIG_PARPORT_PC_FIFO=y CONFIG_PARPORT_PC_SUPERIO=y CONFIG_PARPORT_PC_PCMCIA=m # CONFIG_PARPORT_GSC is not set CONFIG_PARPORT_AX88796=m CONFIG_PARPORT_1284=y CONFIG_PARPORT_NOT_PC=y CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m CONFIG_PARIDE=m # # Parallel IDE high-level drivers # CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m CONFIG_PARIDE_PT=m CONFIG_PARIDE_PG=m # # Parallel IDE protocol modules # CONFIG_PARIDE_ATEN=m CONFIG_PARIDE_BPCK=m CONFIG_PARIDE_COMM=m CONFIG_PARIDE_DSTR=m CONFIG_PARIDE_FIT2=m CONFIG_PARIDE_FIT3=m CONFIG_PARIDE_EPAT=m CONFIG_PARIDE_EPATC8=y CONFIG_PARIDE_EPIA=m CONFIG_PARIDE_FRIQ=m CONFIG_PARIDE_FRPW=m CONFIG_PARIDE_KBIC=m CONFIG_PARIDE_KTTI=m CONFIG_PARIDE_ON20=m CONFIG_PARIDE_ON26=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_CISS_SCSI_TAPE=y CONFIG_BLK_DEV_DAC960=m CONFIG_BLK_DEV_UMEM=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=m CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=128000 CONFIG_BLK_DEV_XIP=y CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 CONFIG_CDROM_PKTCDVD_WCACHE=y CONFIG_ATA_OVER_ETH=m CONFIG_CIPHER_TWOFISH=m CONFIG_VIRTIO_BLK=m # CONFIG_BLK_DEV_HD is not set CONFIG_MISC_DEVICES=y CONFIG_IBM_ASM=m CONFIG_PHANTOM=m CONFIG_EEPROM_93CX6=m CONFIG_SGI_IOC4=m CONFIG_TIFM_CORE=m CONFIG_TIFM_7XX1=m CONFIG_ACER_WMI=m CONFIG_ASUS_LAPTOP=m CONFIG_FUJITSU_LAPTOP=m # CONFIG_FUJITSU_LAPTOP_DEBUG is not set CONFIG_HP_WMI=m CONFIG_MSI_LAPTOP=m CONFIG_PANASONIC_LAPTOP=m CONFIG_COMPAL_LAPTOP=m CONFIG_SONY_LAPTOP=m CONFIG_SONYPI_COMPAT=y CONFIG_THINKPAD_ACPI=m # CONFIG_THINKPAD_ACPI_DEBUG is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_INTEL_MENLOW=m CONFIG_EEEPC_LAPTOP=m CONFIG_ENCLOSURE_SERVICES=m CONFIG_SGI_XP=m CONFIG_HP_ILO=m CONFIG_SGI_GRU=m # CONFIG_SGI_GRU_DEBUG is not set CONFIG_HAVE_IDE=y CONFIG_IDE=m CONFIG_BLK_DEV_IDE=m # # Please see Documentation/ide/ide.txt for help/info on IDE drives # CONFIG_IDE_TIMINGS=y CONFIG_IDE_ATAPI=y # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_BLK_DEV_IDEDISK=m CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECS=m CONFIG_BLK_DEV_DELKIN=m CONFIG_BLK_DEV_IDECD=m CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y CONFIG_BLK_DEV_IDETAPE=m CONFIG_BLK_DEV_IDEFLOPPY=m CONFIG_BLK_DEV_IDESCSI=m CONFIG_BLK_DEV_IDEACPI=y # CONFIG_IDE_TASK_IOCTL is not set CONFIG_IDE_PROC_FS=y # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=m CONFIG_BLK_DEV_PLATFORM=m CONFIG_BLK_DEV_CMD640=m CONFIG_BLK_DEV_CMD640_ENHANCED=y CONFIG_BLK_DEV_IDEPNP=m CONFIG_BLK_DEV_IDEDMA_SFF=y # # PCI IDE chipsets support # CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_OFFBOARD=y CONFIG_BLK_DEV_GENERIC=m # CONFIG_BLK_DEV_OPTI621 is not set CONFIG_BLK_DEV_RZ1000=m CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_AEC62XX=m CONFIG_BLK_DEV_ALI15X3=m CONFIG_BLK_DEV_AMD74XX=m CONFIG_BLK_DEV_ATIIXP=m CONFIG_BLK_DEV_CMD64X=m CONFIG_BLK_DEV_TRIFLEX=m CONFIG_BLK_DEV_CS5520=m CONFIG_BLK_DEV_CS5530=m CONFIG_BLK_DEV_HPT366=m CONFIG_BLK_DEV_JMICRON=m CONFIG_BLK_DEV_SC1200=m CONFIG_BLK_DEV_PIIX=m CONFIG_BLK_DEV_IT8213=m CONFIG_BLK_DEV_IT821X=m CONFIG_BLK_DEV_NS87415=m CONFIG_BLK_DEV_PDC202XX_OLD=m CONFIG_BLK_DEV_PDC202XX_NEW=m CONFIG_BLK_DEV_SVWKS=m CONFIG_BLK_DEV_SIIMAGE=m CONFIG_BLK_DEV_SIS5513=m CONFIG_BLK_DEV_SLC90E66=m # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=m # CONFIG_BLK_DEV_TC86C001 is not set CONFIG_BLK_DEV_IDEDMA=y # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=m 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=m CONFIG_SD_IOSTATS=y CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=m # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=m CONFIG_CHR_DEV_SCH=m CONFIG_SCSI_ENCLOSURE=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y # CONFIG_SCSI_SCAN_ASYNC is not set 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=m 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=y CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_SRP_TGT_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m CONFIG_SCSI_CXGB3_ISCSI=m CONFIG_BLK_DEV_3W_XXXX_RAID=m CONFIG_SCSI_3W_9XXX=m CONFIG_SCSI_ACARD=m CONFIG_SCSI_AACRAID=m CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=32 CONFIG_AIC7XXX_RESET_DELAY_MS=5000 # CONFIG_AIC7XXX_DEBUG_ENABLE is not set CONFIG_AIC7XXX_DEBUG_MASK=0 CONFIG_AIC7XXX_REG_PRETTY_PRINT=y CONFIG_SCSI_AIC7XXX_OLD=m CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=32 CONFIG_AIC79XX_RESET_DELAY_MS=15000 # CONFIG_AIC79XX_DEBUG_ENABLE is not set CONFIG_AIC79XX_DEBUG_MASK=0 CONFIG_AIC79XX_REG_PRETTY_PRINT=y CONFIG_SCSI_AIC94XX=m CONFIG_AIC94XX_DEBUG=y CONFIG_SCSI_DPT_I2O=m CONFIG_SCSI_ADVANSYS=m CONFIG_SCSI_ARCMSR=m CONFIG_SCSI_ARCMSR_AER=y CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=m CONFIG_MEGARAID_MAILBOX=m CONFIG_MEGARAID_LEGACY=m CONFIG_MEGARAID_SAS=m CONFIG_SCSI_HPTIOP=m CONFIG_SCSI_BUSLOGIC=m CONFIG_LIBFC=m CONFIG_FCOE=m CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_EATA=m CONFIG_SCSI_EATA_TAGGED_QUEUE=y CONFIG_SCSI_EATA_LINKED_COMMANDS=y CONFIG_SCSI_EATA_MAX_TAGS=16 CONFIG_SCSI_FUTURE_DOMAIN=m CONFIG_SCSI_GDTH=m CONFIG_SCSI_IPS=m CONFIG_SCSI_INITIO=m # CONFIG_SCSI_INIA100 is not set CONFIG_SCSI_PPA=m CONFIG_SCSI_IMM=m # CONFIG_SCSI_IZIP_EPP16 is not set # CONFIG_SCSI_IZIP_SLOW_CTR is not set CONFIG_SCSI_MVSAS=m CONFIG_SCSI_STEX=m CONFIG_SCSI_SYM53C8XX_2=m CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 CONFIG_SCSI_SYM53C8XX_MMIO=y # CONFIG_SCSI_IPR is not set CONFIG_SCSI_QLOGIC_1280=m CONFIG_SCSI_QLA_FC=m CONFIG_SCSI_QLA_ISCSI=m CONFIG_SCSI_LPFC=m CONFIG_SCSI_DC395x=m CONFIG_SCSI_DC390T=m CONFIG_SCSI_DEBUG=m CONFIG_SCSI_SRP=m CONFIG_SCSI_LOWLEVEL_PCMCIA=y CONFIG_PCMCIA_FDOMAIN=m CONFIG_PCMCIA_QLOGIC=m CONFIG_PCMCIA_SYM53C500=m CONFIG_SCSI_DH=m CONFIG_SCSI_DH_RDAC=m CONFIG_SCSI_DH_HP_SW=m CONFIG_SCSI_DH_EMC=m CONFIG_SCSI_DH_ALUA=m CONFIG_ATA=m # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=m CONFIG_SATA_SIL24=m CONFIG_ATA_SFF=y CONFIG_SATA_SVW=m CONFIG_ATA_PIIX=m CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_PDC_ADMA=m CONFIG_SATA_QSTOR=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SX4=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m CONFIG_SATA_INIC162X=m CONFIG_PATA_ACPI=m CONFIG_PATA_ALI=m CONFIG_PATA_AMD=m CONFIG_PATA_ARTOP=m CONFIG_PATA_ATIIXP=m CONFIG_PATA_CMD640_PCI=m CONFIG_PATA_CMD64X=m CONFIG_PATA_CS5520=m CONFIG_PATA_CS5530=m CONFIG_PATA_CYPRESS=m CONFIG_PATA_EFAR=m CONFIG_ATA_GENERIC=m CONFIG_PATA_HPT366=m CONFIG_PATA_HPT37X=m CONFIG_PATA_HPT3X2N=m CONFIG_PATA_HPT3X3=m # CONFIG_PATA_HPT3X3_DMA is not set CONFIG_PATA_IT821X=m CONFIG_PATA_IT8213=m CONFIG_PATA_JMICRON=m CONFIG_PATA_TRIFLEX=m CONFIG_PATA_MARVELL=m CONFIG_PATA_MPIIX=m CONFIG_PATA_OLDPIIX=m CONFIG_PATA_NETCELL=m CONFIG_PATA_NINJA32=m CONFIG_PATA_NS87410=m CONFIG_PATA_NS87415=m CONFIG_PATA_OPTI=m CONFIG_PATA_OPTIDMA=m CONFIG_PATA_PCMCIA=m CONFIG_PATA_PDC_OLD=m CONFIG_PATA_RADISYS=m CONFIG_PATA_RZ1000=m CONFIG_PATA_SC1200=m CONFIG_PATA_SERVERWORKS=m CONFIG_PATA_PDC2027X=m CONFIG_PATA_SIL680=m CONFIG_PATA_SIS=m CONFIG_PATA_VIA=m CONFIG_PATA_WINBOND=m CONFIG_PATA_SCH=m CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_RAID5_RESHAPE=y CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=m # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=m CONFIG_DM_MIRROR=m CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=m CONFIG_DM_DELAY=m CONFIG_DM_RAID45=m CONFIG_DM_UEVENT=y CONFIG_FUSION=y CONFIG_FUSION_SPI=m CONFIG_FUSION_FC=m CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_MAX_FC_SGE=256 CONFIG_FUSION_CTL=m CONFIG_FUSION_LAN=m # CONFIG_FUSION_LOGGING is not set # # IEEE 1394 (FireWire) support # # # Enable only one of the two stacks, unless you know what you are doing # # CONFIG_FIREWIRE is not set CONFIG_IEEE1394=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y CONFIG_IEEE1394_ETH1394=m CONFIG_IEEE1394_RAWIO=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_DV1394=m # CONFIG_IEEE1394_VERBOSEDEBUG is not set CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_IFB=m CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_MACVLAN=m CONFIG_EQUALIZER=m CONFIG_TUN=m CONFIG_VETH=m # CONFIG_NET_SB1000 is not set CONFIG_ARCNET=m CONFIG_ARCNET_1201=m CONFIG_ARCNET_1051=m CONFIG_ARCNET_RAW=m CONFIG_ARCNET_CAP=m CONFIG_ARCNET_COM90xx=m CONFIG_ARCNET_COM90xxIO=m CONFIG_ARCNET_RIM_I=m # CONFIG_ARCNET_COM20020 is not set CONFIG_PHYLIB=m # # MII PHY device drivers # CONFIG_MARVELL_PHY=m CONFIG_DAVICOM_PHY=m CONFIG_QSEMI_PHY=m CONFIG_LXT_PHY=m CONFIG_CICADA_PHY=m CONFIG_VITESSE_PHY=m CONFIG_SMSC_PHY=m CONFIG_BROADCOM_PHY=m CONFIG_ICPLUS_PHY=m CONFIG_REALTEK_PHY=m CONFIG_MDIO_BITBANG=m CONFIG_NET_ETHERNET=y CONFIG_MII=m CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_CASSINI=m CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m CONFIG_TYPHOON=m CONFIG_ENC28J60=m # CONFIG_ENC28J60_WRITEVERIFY is not set CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set 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=m # 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_NET_PCI=y CONFIG_PCNET32=m CONFIG_AMD8111_ETH=m CONFIG_ADAPTEC_STARFIRE=m CONFIG_B44=m CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y CONFIG_FORCEDETH=m CONFIG_FORCEDETH_NAPI=y CONFIG_EEPRO100=m CONFIG_E100=m CONFIG_FEALNX=m CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_8139CP=m CONFIG_8139TOO=m # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set CONFIG_R6040=m CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m CONFIG_VIA_RHINE=m # CONFIG_VIA_RHINE_MMIO is not set CONFIG_SC92031=m # CONFIG_NET_POCKET is not set CONFIG_ATL2=m CONFIG_NETDEV_1000=y CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set CONFIG_DL2K=m CONFIG_E1000=m # CONFIG_E1000_DISABLE_PACKET_SPLIT is not set CONFIG_E1000E=m CONFIG_IP1000=m CONFIG_IGB=m CONFIG_IGB_LRO=y CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m CONFIG_R8169=m CONFIG_R8169_VLAN=y CONFIG_SIS190=m CONFIG_SKGE=m # CONFIG_SKGE_DEBUG is not set CONFIG_SKY2=m # CONFIG_SKY2_DEBUG is not set CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m CONFIG_QLA3XXX=m CONFIG_ATL1=m CONFIG_ATL1E=m CONFIG_NETDEV_10000=y CONFIG_CHELSIO_T1=m CONFIG_CHELSIO_T1_1G=y CONFIG_CHELSIO_T3=m CONFIG_IXGBE=m CONFIG_IXGBE_LRO=y CONFIG_IXGBE_DCB=y CONFIG_IXGB=m CONFIG_S2IO=m CONFIG_MYRI10GE=m CONFIG_NETXEN_NIC=m CONFIG_NIU=m CONFIG_MLX4_CORE=m CONFIG_MLX4_DEBUG=y CONFIG_TEHUTI=m CONFIG_BNX2X=m CONFIG_SFC=m # CONFIG_SFC_RESOURCE is not set CONFIG_TR=y CONFIG_IBMOL=m CONFIG_3C359=m CONFIG_TMS380TR=m CONFIG_TMSPCI=m CONFIG_ABYSS=m # # Wireless LAN # CONFIG_WLAN_PRE80211=y CONFIG_STRIP=m CONFIG_PCMCIA_WAVELAN=m CONFIG_PCMCIA_NETWAVE=m CONFIG_WLAN_80211=y CONFIG_PCMCIA_RAYCS=m CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW2100_DEBUG is not set CONFIG_IPW2200=m CONFIG_IPW2200_MONITOR=y CONFIG_IPW2200_RADIOTAP=y CONFIG_IPW2200_PROMISCUOUS=y CONFIG_IPW2200_QOS=y # CONFIG_IPW2200_DEBUG is not set CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m CONFIG_LIBERTAS_CS=m CONFIG_LIBERTAS_SDIO=m # CONFIG_LIBERTAS_DEBUG is not set CONFIG_AIRO=m CONFIG_HERMES=m CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_NORTEL_HERMES=m CONFIG_PCI_HERMES=m CONFIG_PCMCIA_HERMES=m CONFIG_PCMCIA_SPECTRUM=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m CONFIG_PCMCIA_ATMEL=m CONFIG_AIRO_CS=m CONFIG_PCMCIA_WL3501=m CONFIG_PRISM54=m CONFIG_USB_ZD1201=m CONFIG_USB_NET_RNDIS_WLAN=m CONFIG_RTL8180=m CONFIG_RTL8187=m CONFIG_ADM8211=m CONFIG_MAC80211_HWSIM=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m CONFIG_ATH5K=m # CONFIG_ATH5K_DEBUG is not set CONFIG_ATH9K=m CONFIG_IWLWIFI=m CONFIG_IWLCORE=m CONFIG_IWLWIFI_LEDS=y CONFIG_IWLWIFI_RFKILL=y # CONFIG_IWLWIFI_DEBUG is not set CONFIG_IWLAGN=m CONFIG_IWLAGN_SPECTRUM_MEASUREMENT=y CONFIG_IWLAGN_LEDS=y CONFIG_IWL4965=y CONFIG_IWL5000=y CONFIG_IWL3945=m CONFIG_IWL3945_RFKILL=y CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y CONFIG_IWL3945_LEDS=y # CONFIG_IWL3945_DEBUG is not set CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m CONFIG_HOSTAP_CS=m CONFIG_B43=m CONFIG_B43_PCI_AUTOSELECT=y CONFIG_B43_PCICORE_AUTOSELECT=y CONFIG_B43_PCMCIA=y CONFIG_B43_PIO=y CONFIG_B43_LEDS=y CONFIG_B43_RFKILL=y # CONFIG_B43_DEBUG is not set CONFIG_B43LEGACY=m CONFIG_B43LEGACY_PCI_AUTOSELECT=y CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y CONFIG_B43LEGACY_LEDS=y CONFIG_B43LEGACY_RFKILL=y # CONFIG_B43LEGACY_DEBUG is not set CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_PIO=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set # CONFIG_B43LEGACY_PIO_MODE is not set CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set CONFIG_RT2X00=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_PCI=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_RFKILL=y CONFIG_RT2X00_LIB_LEDS=y CONFIG_RT2400PCI=m CONFIG_RT2400PCI_RFKILL=y CONFIG_RT2400PCI_LEDS=y CONFIG_RT2500PCI=m CONFIG_RT2500PCI_RFKILL=y CONFIG_RT2500PCI_LEDS=y CONFIG_RT61PCI=m CONFIG_RT61PCI_RFKILL=y CONFIG_RT61PCI_LEDS=y CONFIG_RT2500USB=m CONFIG_RT2500USB_LEDS=y CONFIG_RT73USB=m CONFIG_RT73USB_LEDS=y # CONFIG_RT2X00_LIB_DEBUGFS is not set # CONFIG_RT2X00_DEBUG is not set # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m CONFIG_USB_HSO=m CONFIG_NET_PCMCIA=y CONFIG_PCMCIA_3C589=m CONFIG_PCMCIA_3C574=m CONFIG_PCMCIA_FMVJ18X=m CONFIG_PCMCIA_PCNET=m CONFIG_PCMCIA_NMCLAN=m CONFIG_PCMCIA_SMC91C92=m CONFIG_PCMCIA_XIRC2PS=m CONFIG_PCMCIA_AXNET=m CONFIG_WAN=y CONFIG_LANMEDIA=m CONFIG_HDLC=m CONFIG_HDLC_RAW=m CONFIG_HDLC_RAW_ETH=m CONFIG_HDLC_CISCO=m CONFIG_HDLC_FR=m CONFIG_HDLC_PPP=m CONFIG_HDLC_X25=m CONFIG_PCI200SYN=m CONFIG_WANXL=m # CONFIG_PC300 is not set CONFIG_PC300TOO=m CONFIG_FARSYNC=m # CONFIG_DSCC4 is not set CONFIG_DLCI=m CONFIG_DLCI_MAX=8 # CONFIG_WAN_ROUTER_DRIVERS is not set CONFIG_LAPBETHER=m CONFIG_X25_ASY=m # CONFIG_SBNI is not set CONFIG_ATM_DRIVERS=y CONFIG_ATM_DUMMY=m CONFIG_ATM_TCP=m CONFIG_ATM_LANAI=m CONFIG_ATM_ENI=m # CONFIG_ATM_ENI_DEBUG is not set CONFIG_ATM_ENI_TUNE_BURST=y # CONFIG_ATM_ENI_BURST_TX_16W is not set CONFIG_ATM_ENI_BURST_TX_8W=y CONFIG_ATM_ENI_BURST_TX_4W=y CONFIG_ATM_ENI_BURST_TX_2W=y # CONFIG_ATM_ENI_BURST_RX_16W is not set # CONFIG_ATM_ENI_BURST_RX_8W is not set CONFIG_ATM_ENI_BURST_RX_4W=y CONFIG_ATM_ENI_BURST_RX_2W=y CONFIG_ATM_FIRESTREAM=m CONFIG_ATM_ZATM=m # CONFIG_ATM_ZATM_DEBUG is not set CONFIG_ATM_IDT77252=m # CONFIG_ATM_IDT77252_DEBUG is not set # CONFIG_ATM_IDT77252_RCV_ALL is not set CONFIG_ATM_IDT77252_USE_SUNI=y CONFIG_ATM_AMBASSADOR=m # CONFIG_ATM_AMBASSADOR_DEBUG is not set CONFIG_ATM_HORIZON=m # CONFIG_ATM_HORIZON_DEBUG is not set CONFIG_ATM_IA=m # CONFIG_ATM_IA_DEBUG is not set CONFIG_ATM_FORE200E=m CONFIG_ATM_FORE200E_USE_TASKLET=y CONFIG_ATM_FORE200E_TX_RETRY=16 CONFIG_ATM_FORE200E_DEBUG=0 CONFIG_ATM_HE=m CONFIG_ATM_HE_USE_SUNI=y CONFIG_FDDI=y # CONFIG_DEFXX is not set CONFIG_SKFP=m CONFIG_HIPPI=y CONFIG_ROADRUNNER=m CONFIG_ROADRUNNER_LARGE_RINGS=y CONFIG_PLIP=m 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_PPPOATM=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=y CONFIG_NETCONSOLE=m CONFIG_NETCONSOLE_DYNAMIC=y CONFIG_NETPOLL=y CONFIG_NETPOLL_TRAP=y CONFIG_NET_POLL_CONTROLLER=y CONFIG_VIRTIO_NET=m CONFIG_ISDN=y CONFIG_MISDN=m CONFIG_MISDN_DSP=m CONFIG_MISDN_L1OIP=m # # mISDN hardware drivers # CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCMULTI=m CONFIG_ISDN_I4L=m CONFIG_ISDN_PPP=y CONFIG_ISDN_PPP_VJ=y CONFIG_ISDN_MPP=y CONFIG_IPPP_FILTER=y CONFIG_ISDN_PPP_BSDCOMP=m CONFIG_ISDN_AUDIO=y CONFIG_ISDN_TTY_FAX=y CONFIG_ISDN_X25=y # # ISDN feature submodules # CONFIG_ISDN_DIVERSION=m # # ISDN4Linux hardware drivers # # # Passive cards # CONFIG_ISDN_DRV_HISAX=m # # D-channel protocol features # CONFIG_HISAX_EURO=y CONFIG_DE_AOC=y # CONFIG_HISAX_NO_SENDCOMPLETE is not set # CONFIG_HISAX_NO_LLC is not set # CONFIG_HISAX_NO_KEYPAD is not set CONFIG_HISAX_1TR6=y CONFIG_HISAX_NI1=y CONFIG_HISAX_MAX_CARDS=8 # # HiSax supported cards # CONFIG_HISAX_16_3=y CONFIG_HISAX_TELESPCI=y CONFIG_HISAX_S0BOX=y CONFIG_HISAX_FRITZPCI=y CONFIG_HISAX_AVM_A1_PCMCIA=y CONFIG_HISAX_ELSA=y CONFIG_HISAX_DIEHLDIVA=y CONFIG_HISAX_SEDLBAUER=y CONFIG_HISAX_NETJET=y CONFIG_HISAX_NETJET_U=y CONFIG_HISAX_NICCY=y CONFIG_HISAX_BKM_A4T=y CONFIG_HISAX_SCT_QUADRO=y CONFIG_HISAX_GAZEL=y CONFIG_HISAX_HFC_PCI=y CONFIG_HISAX_W6692=y CONFIG_HISAX_HFC_SX=y CONFIG_HISAX_ENTERNOW_PCI=y CONFIG_HISAX_DEBUG=y # # HiSax PCMCIA card service modules # CONFIG_HISAX_SEDLBAUER_CS=m CONFIG_HISAX_ELSA_CS=m CONFIG_HISAX_AVM_A1_CS=m CONFIG_HISAX_TELES_CS=m # # HiSax sub driver modules # CONFIG_HISAX_ST5481=m CONFIG_HISAX_HFCUSB=m CONFIG_HISAX_HFC4S8S=m CONFIG_HISAX_FRITZ_PCIPNP=m CONFIG_HISAX_HDLC=y # # Active cards # CONFIG_HYSDN=m CONFIG_HYSDN_CAPI=y CONFIG_ISDN_DRV_GIGASET=m CONFIG_GIGASET_BASE=m CONFIG_GIGASET_M105=m CONFIG_GIGASET_M101=m # CONFIG_GIGASET_DEBUG is not set CONFIG_GIGASET_UNDOCREQ=y CONFIG_ISDN_CAPI=m CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y CONFIG_CAPI_TRACE=y CONFIG_ISDN_CAPI_MIDDLEWARE=y CONFIG_ISDN_CAPI_CAPI20=m CONFIG_ISDN_CAPI_CAPIFS_BOOL=y CONFIG_ISDN_CAPI_CAPIFS=m CONFIG_ISDN_CAPI_CAPIDRV=m # # CAPI hardware drivers # CONFIG_CAPI_AVM=y CONFIG_ISDN_DRV_AVMB1_B1PCI=m CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m CONFIG_ISDN_DRV_AVMB1_AVM_CS=m CONFIG_ISDN_DRV_AVMB1_T1PCI=m CONFIG_ISDN_DRV_AVMB1_C4=m # CONFIG_CAPI_EICON is not set CONFIG_PHONE=m CONFIG_PHONE_IXJ=m CONFIG_PHONE_IXJ_PCMCIA=m # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=m CONFIG_INPUT_POLLDEV=m # # 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=m CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_KEYBOARD_SUNKBD=m # CONFIG_KEYBOARD_LKKBD is not set CONFIG_KEYBOARD_XTKBD=m CONFIG_KEYBOARD_NEWTON=m # CONFIG_KEYBOARD_STOWAWAY is not set CONFIG_KEYBOARD_GPIO=m 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_TOUCHKIT is not set CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m # CONFIG_MOUSE_VSXXXAA is not set CONFIG_MOUSE_GPIO=m CONFIG_INPUT_JOYSTICK=y CONFIG_JOYSTICK_ANALOG=m CONFIG_JOYSTICK_A3D=m CONFIG_JOYSTICK_ADI=m CONFIG_JOYSTICK_COBRA=m CONFIG_JOYSTICK_GF2K=m CONFIG_JOYSTICK_GRIP=m CONFIG_JOYSTICK_GRIP_MP=m CONFIG_JOYSTICK_GUILLEMOT=m CONFIG_JOYSTICK_INTERACT=m CONFIG_JOYSTICK_SIDEWINDER=m CONFIG_JOYSTICK_TMDC=m CONFIG_JOYSTICK_IFORCE=m CONFIG_JOYSTICK_IFORCE_USB=y CONFIG_JOYSTICK_IFORCE_232=y CONFIG_JOYSTICK_WARRIOR=m CONFIG_JOYSTICK_MAGELLAN=m CONFIG_JOYSTICK_SPACEORB=m CONFIG_JOYSTICK_SPACEBALL=m CONFIG_JOYSTICK_STINGER=m CONFIG_JOYSTICK_TWIDJOY=m CONFIG_JOYSTICK_ZHENHUA=m CONFIG_JOYSTICK_DB9=m CONFIG_JOYSTICK_GAMECON=m CONFIG_JOYSTICK_TURBOGRAFX=m CONFIG_JOYSTICK_JOYDUMP=m CONFIG_JOYSTICK_XPAD=m CONFIG_JOYSTICK_XPAD_FF=y CONFIG_JOYSTICK_XPAD_LEDS=y CONFIG_INPUT_TABLET=y CONFIG_TABLET_USB_ACECAD=m CONFIG_TABLET_USB_AIPTEK=m CONFIG_TABLET_USB_GTCO=m CONFIG_TABLET_USB_KBTAB=m CONFIG_TABLET_USB_WACOM=m CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_ADS7846=m CONFIG_TOUCHSCREEN_FUJITSU=m CONFIG_TOUCHSCREEN_GUNZE=m CONFIG_TOUCHSCREEN_ELO=m CONFIG_TOUCHSCREEN_ELOUSB=m CONFIG_TOUCHSCREEN_MTOUCH=m CONFIG_TOUCHSCREEN_INEXIO=m CONFIG_TOUCHSCREEN_MK712=m CONFIG_TOUCHSCREEN_PENMOUNT=m CONFIG_TOUCHSCREEN_TOUCHRIGHT=m CONFIG_TOUCHSCREEN_TOUCHWIN=m CONFIG_TOUCHSCREEN_UCB1400=m CONFIG_TOUCHSCREEN_WM97XX=m CONFIG_TOUCHSCREEN_WM9705=y CONFIG_TOUCHSCREEN_WM9712=y CONFIG_TOUCHSCREEN_WM9713=y CONFIG_TOUCHSCREEN_USB_COMPOSITE=m CONFIG_TOUCHSCREEN_USB_EGALAX=y CONFIG_TOUCHSCREEN_USB_PANJIT=y CONFIG_TOUCHSCREEN_USB_3M=y CONFIG_TOUCHSCREEN_USB_ITM=y CONFIG_TOUCHSCREEN_USB_ETURBO=y CONFIG_TOUCHSCREEN_USB_GUNZE=y CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y CONFIG_TOUCHSCREEN_USB_IRTOUCH=y CONFIG_TOUCHSCREEN_USB_IDEALTEK=y CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y CONFIG_TOUCHSCREEN_USB_GOTOP=y CONFIG_TOUCHSCREEN_TOUCHIT213=m CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=m CONFIG_INPUT_APANEL=m CONFIG_INPUT_ATLAS_BTNS=m CONFIG_INPUT_ATI_REMOTE=m CONFIG_INPUT_ATI_REMOTE2=m CONFIG_INPUT_KEYSPAN_REMOTE=m CONFIG_INPUT_POWERMATE=m CONFIG_INPUT_YEALINK=m CONFIG_INPUT_UINPUT=m # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m CONFIG_SERIO_CT82C710=m CONFIG_SERIO_PARKBD=m CONFIG_SERIO_PCIPS2=m CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=m CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m CONFIG_GAMEPORT_L4=m CONFIG_GAMEPORT_EMU10K1=m CONFIG_GAMEPORT_FM801=m # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_DEVKMEM=y CONFIG_SERIAL_NONSTANDARD=y CONFIG_COMPUTONE=m CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set CONFIG_DIGIEPCA=m CONFIG_MOXA_INTELLIO=m CONFIG_MOXA_SMARTIO=m CONFIG_ISI=m CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_SYNCLINK_GT=m CONFIG_N_HDLC=m CONFIG_RISCOM8=m CONFIG_SPECIALIX=m CONFIG_SX=m CONFIG_RIO=m CONFIG_RIO_OLDPCI=y CONFIG_STALDRV=y 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=16 CONFIG_SERIAL_8250_RUNTIME_UARTS=8 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_SERIAL_JSM=m CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=0 CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m CONFIG_HVC_DRIVER=y CONFIG_VIRTIO_CONSOLE=m CONFIG_IPMI_HANDLER=m CONFIG_IPMI_PANIC_EVENT=y # CONFIG_IPMI_PANIC_STRING is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_INTEL=m CONFIG_HW_RANDOM_AMD=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_NVRAM=y CONFIG_R3964=m CONFIG_APPLICOM=m # # PCMCIA character devices # CONFIG_SYNCLINK_CS=m CONFIG_CARDMAN_4000=m CONFIG_CARDMAN_4040=m CONFIG_IPWIRELESS=m # CONFIG_MWAVE is not set CONFIG_PC8736x_GPIO=m CONFIG_NSC_GPIO=m CONFIG_RAW_DRIVER=m CONFIG_MAX_RAW_DEVS=4096 CONFIG_HPET=y CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=m CONFIG_TCG_TPM=m CONFIG_TCG_TIS=m CONFIG_TCG_NSC=m CONFIG_TCG_ATMEL=m CONFIG_TCG_INFINEON=m CONFIG_TELCLOCK=m CONFIG_DEVPORT=y CONFIG_CRASHER=m CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=m CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # CONFIG_I2C_ALI1535=m CONFIG_I2C_ALI1563=m CONFIG_I2C_ALI15X3=m CONFIG_I2C_AMD756=m CONFIG_I2C_AMD756_S4882=m CONFIG_I2C_AMD8111=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NFORCE2_S4985=m CONFIG_I2C_SIS5595=m CONFIG_I2C_SIS630=m CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m # # I2C system bus drivers (mostly embedded / system-on-chip) # CONFIG_I2C_GPIO=m CONFIG_I2C_OCORES=m # CONFIG_I2C_SIMTEC is not set # # External I2C/SMBus adapter drivers # CONFIG_I2C_PARPORT=m CONFIG_I2C_PARPORT_LIGHT=m CONFIG_I2C_TAOS_EVM=m CONFIG_I2C_TINY_USB=m # # Graphics adapter I2C/DDC channel drivers # CONFIG_I2C_VOODOO3=m # # Other I2C/SMBus bus drivers # CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_STUB=m # # Miscellaneous I2C Chip support # CONFIG_DS1682=m CONFIG_AT24=m CONFIG_SENSORS_EEPROM=m CONFIG_SENSORS_PCF8591=m # CONFIG_TPS65010 is not set CONFIG_SENSORS_MAX6875=m CONFIG_SENSORS_TSL2550=m # 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=y CONFIG_SPI_DEBUG=y CONFIG_SPI_MASTER=y # # SPI Master Controller Drivers # CONFIG_SPI_BITBANG=m CONFIG_SPI_BUTTERFLY=m CONFIG_SPI_LM70_LLP=m # # SPI Protocol Masters # CONFIG_SPI_AT25=m CONFIG_SPI_SPIDEV=m CONFIG_SPI_TLE62X0=m CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y # # I2C GPIO expanders: # CONFIG_GPIO_MAX732X=m CONFIG_GPIO_PCA953X=m CONFIG_GPIO_PCF857X=m # # PCI GPIO expanders: # # # SPI GPIO expanders: # CONFIG_GPIO_MAX7301=m CONFIG_GPIO_MCP23S08=m CONFIG_W1=m CONFIG_W1_CON=y # # 1-wire Bus Masters # CONFIG_W1_MASTER_MATROX=m CONFIG_W1_MASTER_DS2490=m CONFIG_W1_MASTER_DS2482=m CONFIG_W1_MASTER_GPIO=m # # 1-wire Slaves # CONFIG_W1_SLAVE_THERM=m CONFIG_W1_SLAVE_SMEM=m CONFIG_W1_SLAVE_DS2433=m CONFIG_W1_SLAVE_DS2433_CRC=y CONFIG_W1_SLAVE_DS2760=m CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set CONFIG_PDA_POWER=m CONFIG_BATTERY_DS2760=m CONFIG_HWMON=m CONFIG_HWMON_VID=m CONFIG_SENSORS_ABITUGURU=m CONFIG_SENSORS_ABITUGURU3=m CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m CONFIG_SENSORS_ADCXX=m CONFIG_SENSORS_ADM1021=m CONFIG_SENSORS_ADM1025=m CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7470=m CONFIG_SENSORS_ADT7473=m CONFIG_SENSORS_K8TEMP=m CONFIG_SENSORS_ASB100=m CONFIG_SENSORS_ATXP1=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_I5K_AMB=m CONFIG_SENSORS_F71805F=m CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m CONFIG_SENSORS_FSCHER=m CONFIG_SENSORS_FSCPOS=m CONFIG_SENSORS_FSCHMD=m CONFIG_SENSORS_GL518SM=m CONFIG_SENSORS_GL520SM=m CONFIG_SENSORS_CORETEMP=m CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IT87=m CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM70=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m CONFIG_SENSORS_MAX1619=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_SIS5595=m CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_SMSC47M1=m CONFIG_SENSORS_SMSC47M192=m CONFIG_SENSORS_SMSC47B397=m CONFIG_SENSORS_ADS7828=m CONFIG_SENSORS_THMC50=m CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_VT8231=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m CONFIG_SENSORS_HDAPS=m CONFIG_SENSORS_APPLESMC=m # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL=m CONFIG_THERMAL_HWMON=y CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_ACQUIRE_WDT=m CONFIG_ADVANTECH_WDT=m CONFIG_ALIM1535_WDT=m CONFIG_ALIM7101_WDT=m CONFIG_SC520_WDT=m CONFIG_EUROTECH_WDT=m CONFIG_IB700_WDT=m CONFIG_IBMASR=m CONFIG_WAFER_WDT=m CONFIG_I6300ESB_WDT=m CONFIG_ITCO_WDT=m CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_IT8712F_WDT=m CONFIG_HP_WATCHDOG=m CONFIG_SC1200_WDT=m CONFIG_PC87413_WDT=m CONFIG_60XX_WDT=m CONFIG_SBC8360_WDT=m CONFIG_CPU5_WDT=m CONFIG_SMSC37B787_WDT=m CONFIG_W83627HF_WDT=m CONFIG_W83697HF_WDT=m CONFIG_W83877F_WDT=m CONFIG_W83977F_WDT=m CONFIG_MACHZ_WDT=m CONFIG_SBC_EPX_C3_WATCHDOG=m # # PCI-based Watchdog Cards # CONFIG_PCIPCWATCHDOG=m CONFIG_WDTPCI=m CONFIG_WDT_501_PCI=y # # USB-based Watchdog Cards # CONFIG_USBPCWATCHDOG=m # # Sonics Silicon Backplane # CONFIG_SSB_POSSIBLE=y CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_PCMCIAHOST_POSSIBLE=y CONFIG_SSB_PCMCIAHOST=y # 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=m CONFIG_MFD_SM501_GPIO=y CONFIG_HTC_PASIC3=m # CONFIG_MFD_TMIO is not set # # Multimedia devices # # # Multimedia core support # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2_COMMON=m CONFIG_VIDEO_ALLOW_V4L1=y CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMIZE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_MT2131=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_V4L1=m CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DMA_CONTIG=m CONFIG_VIDEOBUF_DVB=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_TDA9840=m CONFIG_VIDEO_TDA9875=m CONFIG_VIDEO_TEA6415C=m CONFIG_VIDEO_TEA6420=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS5345=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_M52790=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_WM8739=m CONFIG_VIDEO_VP27SMPX=m CONFIG_VIDEO_BT819=m CONFIG_VIDEO_BT856=m CONFIG_VIDEO_KS0127=m CONFIG_VIDEO_OV7670=m CONFIG_VIDEO_SAA7110=m CONFIG_VIDEO_SAA7111=m CONFIG_VIDEO_SAA7114=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_SAA717X=m CONFIG_VIDEO_TVP5150=m CONFIG_VIDEO_VPX3220=m CONFIG_VIDEO_CX25840=m CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_SAA7127=m CONFIG_VIDEO_SAA7185=m CONFIG_VIDEO_ADV7170=m CONFIG_VIDEO_ADV7175=m CONFIG_VIDEO_UPD64031A=m CONFIG_VIDEO_UPD64083=m CONFIG_VIDEO_VIVI=m CONFIG_VIDEO_BT848=m CONFIG_VIDEO_BT848_DVB=y CONFIG_VIDEO_SAA6588=m CONFIG_VIDEO_BWQCAM=m CONFIG_VIDEO_CQCAM=m CONFIG_VIDEO_W9966=m CONFIG_VIDEO_CPIA=m CONFIG_VIDEO_CPIA_PP=m CONFIG_VIDEO_CPIA_USB=m CONFIG_VIDEO_CPIA2=m CONFIG_VIDEO_SAA5246A=m CONFIG_VIDEO_SAA5249=m # CONFIG_TUNER_3036 is not set CONFIG_VIDEO_STRADIS=m CONFIG_VIDEO_ZORAN=m CONFIG_VIDEO_ZORAN_DC30=m CONFIG_VIDEO_ZORAN_ZR36060=m CONFIG_VIDEO_ZORAN_BUZ=m CONFIG_VIDEO_ZORAN_DC10=m CONFIG_VIDEO_ZORAN_LML33=m CONFIG_VIDEO_ZORAN_LML33R10=m CONFIG_VIDEO_ZORAN_AVS6EYES=m CONFIG_VIDEO_MEYE=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_DVB=m CONFIG_VIDEO_MXB=m # CONFIG_VIDEO_DPC is not set CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX23885=m CONFIG_VIDEO_AU0828=m CONFIG_VIDEO_IVTV=m CONFIG_VIDEO_FB_IVTV=m CONFIG_VIDEO_CX18=m CONFIG_VIDEO_CAFE_CCIC=m CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_EM28XX=m CONFIG_VIDEO_EM28XX_ALSA=m CONFIG_VIDEO_EM28XX_DVB=m CONFIG_VIDEO_USBVISION=m CONFIG_VIDEO_USBVIDEO=m CONFIG_USB_VICAM=m CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m CONFIG_USB_QUICKCAM_MESSENGER=m CONFIG_USB_ET61X251=m CONFIG_VIDEO_OVCAMCHIP=m CONFIG_USB_W9968CF=m CONFIG_USB_OV511=m CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m CONFIG_USB_ZC0301=m CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_ZR364XX=m CONFIG_USB_STKWEBCAM=m CONFIG_USB_S2255=m CONFIG_SOC_CAMERA=m CONFIG_SOC_CAMERA_MT9M001=m CONFIG_MT9M001_PCA9536_SWITCH=y CONFIG_SOC_CAMERA_MT9V022=m CONFIG_MT9V022_PCA9536_SWITCH=y CONFIG_SOC_CAMERA_PLATFORM=m CONFIG_VIDEO_SH_MOBILE_CEU=m CONFIG_RADIO_ADAPTERS=y CONFIG_RADIO_GEMTEK_PCI=m CONFIG_RADIO_MAXIRADIO=m CONFIG_RADIO_MAESTRO=m CONFIG_USB_DSBR=m CONFIG_USB_SI470X=m CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # CONFIG_TTPCI_EEPROM=m CONFIG_DVB_AV7110=m # CONFIG_DVB_AV7110_FIRMWARE is not set CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_DVB_CINERGYT2=m # CONFIG_DVB_CINERGYT2_TUNING is not set CONFIG_DVB_SIANO_SMS1XXX=m CONFIG_DVB_SIANO_SMS1XXX_SMS_IDS=y # # Supported FlexCopII (B2C2) Adapters # CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_DVB_B2C2_FLEXCOP_PCI=m CONFIG_DVB_B2C2_FLEXCOP_USB=m # CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set # # Supported BT878 Adapters # CONFIG_DVB_BT8XX=m # # Supported Pluto2 Adapters # CONFIG_DVB_PLUTO2=m # # Supported DVB Frontends # # # Customise DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set # # DVB-S (satellite) frontends # CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0299=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m # # DVB-T (terrestrial) frontends # CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m CONFIG_DVB_DRX397XD=m CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m # # DVB-C (cable) frontends # CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m # # ATSC (North American/Korean Terrestrial/Cable DTV) frontends # CONFIG_DVB_NXT200X=m CONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_S5H1411=m # # Digital terrestrial only tuners/PLL # CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m # # SEC control devices for DVB-S # CONFIG_DVB_LNBP21=m CONFIG_DVB_ISL6405=m CONFIG_DVB_ISL6421=m CONFIG_DAB=y CONFIG_USB_DABUSB=m # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=m CONFIG_AGP_SIS=m CONFIG_AGP_VIA=m CONFIG_DRM=m CONFIG_DRM_TDFX=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_I810=m # CONFIG_DRM_I830 is not set CONFIG_DRM_I915=m CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m CONFIG_DRM_VIA=m CONFIG_DRM_VIA_CHROME9=m CONFIG_DRM_SAVAGE=m CONFIG_VGASTATE=m CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y CONFIG_FIRMWARE_EDID=y CONFIG_FB_DDC=m CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y CONFIG_FB_HECUBA=m CONFIG_FB_SVGALIB=m # CONFIG_FB_MACMODES is not set CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # CONFIG_FB_CIRRUS=m # CONFIG_FB_PM2 is not set CONFIG_FB_CYBER2000=m CONFIG_FB_ARC=m # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set CONFIG_FB_VGA16=m CONFIG_FB_UVESA=m CONFIG_FB_VESA=y CONFIG_FB_EFI=y CONFIG_FB_IMAC=y CONFIG_FB_N411=m CONFIG_FB_HGA=m CONFIG_FB_HGA_ACCEL=y CONFIG_FB_S1D13XXX=m CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y CONFIG_FB_RIVA=m CONFIG_FB_RIVA_I2C=y # CONFIG_FB_RIVA_DEBUG is not set CONFIG_FB_RIVA_BACKLIGHT=y CONFIG_FB_LE80578=m CONFIG_FB_CARILLO_RANCH=m CONFIG_FB_INTEL=m # CONFIG_FB_INTEL_DEBUG is not set CONFIG_FB_INTEL_I2C=y CONFIG_FB_MATROX=m CONFIG_FB_MATROX_MILLENIUM=y CONFIG_FB_MATROX_MYSTIQUE=y CONFIG_FB_MATROX_G=y CONFIG_FB_MATROX_I2C=m CONFIG_FB_MATROX_MAVEN=m CONFIG_FB_MATROX_MULTIHEAD=y CONFIG_FB_RADEON=m CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y # CONFIG_FB_RADEON_DEBUG is not set CONFIG_FB_ATY128=m CONFIG_FB_ATY128_BACKLIGHT=y CONFIG_FB_ATY=m CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GENERIC_LCD=y CONFIG_FB_ATY_GX=y CONFIG_FB_ATY_BACKLIGHT=y # CONFIG_FB_S3 is not set CONFIG_FB_SAVAGE=m CONFIG_FB_SAVAGE_I2C=y CONFIG_FB_SAVAGE_ACCEL=y CONFIG_FB_SIS=m CONFIG_FB_SIS_300=y CONFIG_FB_SIS_315=y CONFIG_FB_NEOMAGIC=m CONFIG_FB_KYRO=m CONFIG_FB_3DFX=m CONFIG_FB_3DFX_ACCEL=y CONFIG_FB_VOODOO1=m CONFIG_FB_VT8623=m CONFIG_FB_TRIDENT=m CONFIG_FB_TRIDENT_ACCEL=y CONFIG_FB_ARK=m CONFIG_FB_PM3=m CONFIG_FB_CARMINE=m CONFIG_FB_CARMINE_DRAM_EVAL=y # CONFIG_CARMINE_DRAM_CUSTOM is not set CONFIG_FB_GEODE=y CONFIG_FB_GEODE_LX=m CONFIG_FB_GEODE_GX=m CONFIG_FB_GEODE_GX1=m CONFIG_FB_SM501=m CONFIG_FB_VIRTUAL=m CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=m CONFIG_LCD_LTV350QV=m CONFIG_LCD_ILI9320=m CONFIG_LCD_VGG2432A4=m CONFIG_LCD_PLATFORM=m CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_CORGI=m CONFIG_BACKLIGHT_PROGEAR=m CONFIG_BACKLIGHT_CARILLO_RANCH=m CONFIG_BACKLIGHT_MBP_NVIDIA=m # # Display device support # CONFIG_DISPLAY_SUPPORT=m # # Display hardware drivers # # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64 CONFIG_VIDEO_SELECT=y CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_LOGO is not set # # Bootsplash configuration # CONFIG_BOOTSPLASH=y CONFIG_SOUND=m CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y CONFIG_SND_VERBOSE_PRINTK=y CONFIG_SND_DEBUG=y # CONFIG_SND_DEBUG_VERBOSE is not set # CONFIG_SND_PCM_XRUN_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y # CONFIG_SND_PCSP is not set CONFIG_SND_DUMMY=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_MTS64=m CONFIG_SND_SERIAL_U16550=m CONFIG_SND_MPU401=m CONFIG_SND_PORTMAN2X4=m CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 CONFIG_SND_SB_COMMON=m CONFIG_SND_PCI=y CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m CONFIG_SND_AW2=m CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_OXYGEN_LIB=m CONFIG_SND_OXYGEN=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y # CONFIG_SND_CS5530 is not set CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_INPUT_BEEP=y 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_CONEXANT=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0 CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_HIFIER=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_MAESTRO3=m CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VIRTUOSO=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_SPI=y CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_USX2Y=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_PCMCIA=y CONFIG_SND_VXPOCKET=m CONFIG_SND_PDAUDIOCF=m # CONFIG_SND_SOC is not set CONFIG_SOUND_PRIME=m CONFIG_SOUND_OSS=m CONFIG_SOUND_TRACEINIT=y CONFIG_SOUND_DMAP=y CONFIG_SOUND_SSCAPE=m CONFIG_SOUND_VMIDI=m CONFIG_SOUND_TRIX=m CONFIG_SOUND_MSS=m CONFIG_SOUND_MPU401=m CONFIG_SOUND_PAS=m CONFIG_SOUND_PSS=m CONFIG_PSS_MIXER=y # CONFIG_PSS_HAVE_BOOT is not set # CONFIG_SOUND_SB is not set CONFIG_SOUND_YM3812=m CONFIG_SOUND_UART6850=m CONFIG_SOUND_AEDSP16=m CONFIG_SC6600=y CONFIG_SC6600_JOY=y CONFIG_SC6600_CDROM=4 CONFIG_SC6600_CDROMBASE=0x0 CONFIG_AEDSP16_MSS=y # CONFIG_AEDSP16_SBPRO is not set CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=m # CONFIG_HID_DEBUG is not set CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=m CONFIG_USB_HIDINPUT_POWERBOOK=y CONFIG_HID_FF=y CONFIG_HID_PID=y CONFIG_LOGITECH_FF=y # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_PANTHERLORD_FF=y CONFIG_THRUSTMASTER_FF=y CONFIG_ZEROPLUS_FF=y CONFIG_USB_HIDDEV=y # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE 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=y # CONFIG_USB_OTG is not set CONFIG_USB_MON=y # # USB Host Controller Drivers # CONFIG_USB_C67X00_HCD=m CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_ISP116X_HCD=m CONFIG_USB_ISP1760_HCD=m 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 is not set CONFIG_USB_SL811_HCD=m CONFIG_USB_SL811_CS=m CONFIG_USB_R8A66597_HCD=m # # Enable Host or Gadget support to see Inventra options # # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m # # NOTE: USB_STORAGE enables SCSI, and ''SCSI disk support'' # # # may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_DATAFAB=y CONFIG_USB_STORAGE_FREECOM=y CONFIG_USB_STORAGE_ISD200=y CONFIG_USB_STORAGE_DPCM=y CONFIG_USB_STORAGE_USBAT=y CONFIG_USB_STORAGE_SDDR09=y CONFIG_USB_STORAGE_SDDR55=y CONFIG_USB_STORAGE_JUMPSHOT=y CONFIG_USB_STORAGE_ALAUDA=y CONFIG_USB_STORAGE_ONETOUCH=y CONFIG_USB_STORAGE_KARMA=y CONFIG_USB_STORAGE_CYPRESS_ATACB=y # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m # # USB port drivers # CONFIG_USB_USS720=m CONFIG_USB_SERIAL=m CONFIG_USB_EZUSB=y CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP2101=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_FUNSOFT=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KEYSPAN_MPR=y CONFIG_USB_SERIAL_KEYSPAN_USA28=y CONFIG_USB_SERIAL_KEYSPAN_USA28X=y CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y CONFIG_USB_SERIAL_KEYSPAN_USA19=y CONFIG_USB_SERIAL_KEYSPAN_USA18X=y CONFIG_USB_SERIAL_KEYSPAN_USA19W=y CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y CONFIG_USB_SERIAL_KEYSPAN_USA49W=y CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_MOTOROLA=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_QUALCOMM=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m CONFIG_USB_SERIAL_SAFE_PADDED=y CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_RIO500=m CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m CONFIG_USB_BERRY_CHARGE=m CONFIG_USB_LED=m CONFIG_USB_CYPRESS_CY7C63=m CONFIG_USB_CYTHERM=m CONFIG_USB_PHIDGET=m CONFIG_USB_PHIDGETKIT=m CONFIG_USB_PHIDGETMOTORCONTROL=m CONFIG_USB_PHIDGETSERVO=m CONFIG_USB_IDMOUSE=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_APPLEDISPLAY=m CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y CONFIG_USB_LD=m CONFIG_USB_TRANCEVIBRATOR=m CONFIG_USB_IOWARRIOR=m # CONFIG_USB_TEST is not set CONFIG_USB_ISIGHTFW=m CONFIG_USB_ATM=m CONFIG_USB_SPEEDTOUCH=m CONFIG_USB_CXACRU=m CONFIG_USB_UEAGLEATM=m CONFIG_USB_XUSBATM=m # CONFIG_USB_GADGET is not set CONFIG_MMC=m # CONFIG_MMC_DEBUG is not set # CONFIG_MMC_UNSAFE_RESUME is not set # # MMC/SD Card Drivers # CONFIG_MMC_BLOCK=m CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=m CONFIG_MMC_TEST=m # # MMC/SD Host Controller Drivers # CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PCI=m CONFIG_MMC_RICOH_MMC=m CONFIG_MMC_WBSD=m CONFIG_MMC_TIFM_SD=m CONFIG_MMC_SPI=m CONFIG_MMC_SDRICOH_CS=m CONFIG_MEMSTICK=m # CONFIG_MEMSTICK_DEBUG is not set # # MemoryStick drivers # # CONFIG_MEMSTICK_UNSAFE_RESUME is not set CONFIG_MSPRO_BLOCK=m # # MemoryStick Host Controller Drivers # CONFIG_MEMSTICK_TIFM_MS=m CONFIG_MEMSTICK_JMICRON_38X=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=m # # LED drivers # CONFIG_LEDS_PCA9532=m CONFIG_LEDS_GPIO=m CONFIG_LEDS_CLEVO_MAIL=m CONFIG_LEDS_PCA955X=m # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_IDE_DISK=y CONFIG_LEDS_TRIGGER_HEARTBEAT=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=m # CONFIG_ACCESSIBILITY is not set CONFIG_INFINIBAND=m CONFIG_INFINIBAND_USER_MAD=m CONFIG_INFINIBAND_USER_ACCESS=m CONFIG_INFINIBAND_USER_MEM=y CONFIG_INFINIBAND_ADDR_TRANS=y CONFIG_INFINIBAND_MTHCA=m CONFIG_INFINIBAND_MTHCA_DEBUG=y CONFIG_INFINIBAND_IPATH=m CONFIG_INFINIBAND_AMSO1100=m # CONFIG_INFINIBAND_AMSO1100_DEBUG is not set CONFIG_INFINIBAND_CXGB3=m # CONFIG_INFINIBAND_CXGB3_DEBUG is not set CONFIG_MLX4_INFINIBAND=m CONFIG_INFINIBAND_NES=m # CONFIG_INFINIBAND_NES_DEBUG is not set CONFIG_INFINIBAND_IPOIB=m CONFIG_INFINIBAND_IPOIB_CM=y CONFIG_INFINIBAND_IPOIB_DEBUG=y # CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set CONFIG_INFINIBAND_SRP=m CONFIG_INFINIBAND_ISER=m CONFIG_EDAC=y # # Reporting subsystems # # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_MM_EDAC=m CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m 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=y CONFIG_RTC_DRV_TEST=m # # I2C RTC drivers # CONFIG_RTC_DRV_DS1307=m CONFIG_RTC_DRV_DS1374=m CONFIG_RTC_DRV_DS1672=m CONFIG_RTC_DRV_MAX6900=m CONFIG_RTC_DRV_RS5C372=m CONFIG_RTC_DRV_ISL1208=m CONFIG_RTC_DRV_X1205=m CONFIG_RTC_DRV_PCF8563=m CONFIG_RTC_DRV_PCF8583=m CONFIG_RTC_DRV_M41T80=m CONFIG_RTC_DRV_M41T80_WDT=y CONFIG_RTC_DRV_S35390A=m CONFIG_RTC_DRV_FM3130=m # # SPI RTC drivers # CONFIG_RTC_DRV_M41T94=m CONFIG_RTC_DRV_DS1305=m CONFIG_RTC_DRV_MAX6902=m CONFIG_RTC_DRV_R9701=m CONFIG_RTC_DRV_RS5C348=m # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=m CONFIG_RTC_DRV_DS1511=m CONFIG_RTC_DRV_DS1553=m CONFIG_RTC_DRV_DS1742=m CONFIG_RTC_DRV_STK17TA8=m CONFIG_RTC_DRV_M48T86=m CONFIG_RTC_DRV_M48T59=m CONFIG_RTC_DRV_V3020=m # # on-CPU RTC drivers # CONFIG_DMADEVICES=y # # DMA Devices # CONFIG_INTEL_IOATDMA=m CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y CONFIG_DMATEST=m CONFIG_DCA=m CONFIG_AUXDISPLAY=y # CONFIG_KS0108 is not set CONFIG_UIO=m CONFIG_UIO_CIF=m CONFIG_UIO_PDRV=m CONFIG_UIO_PDRV_GENIRQ=m CONFIG_UIO_SMX=m CONFIG_STAGING=y CONFIG_ET131X=m # CONFIG_ET131X_DEBUG is not set CONFIG_SLICOSS=m CONFIG_SXG=m CONFIG_ME4000=m CONFIG_VIDEO_GO7007=m CONFIG_VIDEO_GO7007_USB=m CONFIG_USB_IP_COMMON=m CONFIG_USB_IP_VHCI_HCD=m CONFIG_USB_IP_HOST=m CONFIG_W35UND=m CONFIG_PRISM2_USB=m CONFIG_ECHO=m CONFIG_USB_ATMEL=m CONFIG_AGNX=m CONFIG_OTUS=m CONFIG_RT2860=m CONFIG_RT2870=m CONFIG_RT3070=m CONFIG_BENET=m CONFIG_RTL8187SE=m CONFIG_RTL8192E=m CONFIG_HYPERV=m CONFIG_HYPERV_STORAGE=m CONFIG_HYPERV_BLOCK=m CONFIG_HYPERV_NET=m # # Firmware Drivers # CONFIG_EDD=m # CONFIG_EDD_OFF 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=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=m 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=m CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_NFS4ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4DEV_FS=m CONFIG_EXT4DEV_FS_XATTR=y CONFIG_EXT4DEV_FS_POSIX_ACL=y CONFIG_EXT4DEV_FS_SECURITY=y CONFIG_JBD=m CONFIG_JBD_DEBUG=y CONFIG_JBD2=m CONFIG_JBD2_DEBUG=y CONFIG_FS_MBCACHE=m CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set CONFIG_REISERFS_FS_XATTR=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_REISERFS_FS_SECURITY=y CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y CONFIG_JFS_SECURITY=y # CONFIG_JFS_DEBUG is not set CONFIG_JFS_STATISTICS=y CONFIG_FS_POSIX_ACL=y CONFIG_FS_NFS4ACL=y CONFIG_XFS_FS=m CONFIG_XFS_QUOTA=y CONFIG_XFS_DMAPI=m CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y # CONFIG_XFS_DEBUG is not set CONFIG_GFS2_FS=m CONFIG_GFS2_FS_LOCKING_DLM=m CONFIG_OCFS2_FS=m CONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m CONFIG_OCFS2_FS_STATS=y # CONFIG_OCFS2_DEBUG_MASKLOG is not set # CONFIG_OCFS2_DEBUG_FS is not set # CONFIG_OCFS2_COMPAT_JBD is not set CONFIG_OCFS2_FS_POSIX_ACL=y CONFIG_DNOTIFY=y CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_DMAPI=m # CONFIG_DMAPI_DEBUG is not set CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y CONFIG_PRINT_QUOTA_WARNING=y CONFIG_QUOTA_TREE=m CONFIG_QFMT_V1=m CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=m CONFIG_FUSE_FS=m CONFIG_GENERIC_ACL=y # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set CONFIG_NTFS_RW=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_VMCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=m # # Miscellaneous filesystems # CONFIG_ADFS_FS=m # CONFIG_ADFS_FS_RW is not set CONFIG_AFFS_FS=m CONFIG_ECRYPT_FS=m CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m CONFIG_BEFS_FS=m # CONFIG_BEFS_DEBUG is not set CONFIG_BFS_FS=m CONFIG_EFS_FS=m CONFIG_JFFS2_FS=m CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_WRITEBUFFER=y # CONFIG_JFFS2_FS_WBUF_VERIFY is not set CONFIG_JFFS2_SUMMARY=y CONFIG_JFFS2_FS_XATTR=y CONFIG_JFFS2_FS_POSIX_ACL=y CONFIG_JFFS2_FS_SECURITY=y CONFIG_JFFS2_COMPRESSION_OPTIONS=y CONFIG_JFFS2_ZLIB=y # CONFIG_JFFS2_LZO is not set CONFIG_JFFS2_RTIME=y # CONFIG_JFFS2_RUBIN is not set # CONFIG_JFFS2_CMODE_NONE is not set CONFIG_JFFS2_CMODE_PRIORITY=y # CONFIG_JFFS2_CMODE_SIZE is not set # CONFIG_JFFS2_CMODE_FAVOURLZO is not set CONFIG_UBIFS_FS=m CONFIG_UBIFS_FS_XATTR=y CONFIG_UBIFS_FS_ADVANCED_COMPR=y CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y # CONFIG_UBIFS_FS_DEBUG is not set CONFIG_CRAMFS=m CONFIG_SQUASHFS=m # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 CONFIG_VXFS_FS=m CONFIG_MINIX_FS=y CONFIG_OMFS_FS=m CONFIG_HPFS_FS=m CONFIG_QNX4FS_FS=m CONFIG_ROMFS_FS=m CONFIG_SYSV_FS=m CONFIG_UFS_FS=m CONFIG_UFS_FS_WRITE=y # CONFIG_UFS_DEBUG is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y CONFIG_NFS_SWAP=y CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=m CONFIG_SUNRPC_GSS=m CONFIG_SUNRPC_XPRT_RDMA=m CONFIG_SUNRPC_SWAP=y CONFIG_RPCSEC_GSS_KRB5=m CONFIG_RPCSEC_GSS_SPKM3=m # CONFIG_SMB_FS is not set CONFIG_CIFS=m CONFIG_CIFS_STATS=y CONFIG_CIFS_STATS2=y CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_EXPERIMENTAL=y CONFIG_CIFS_DFS_UPCALL=y CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y CONFIG_NCPFS_SMALLDOS=y CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y CONFIG_CODA_FS=m CONFIG_AFS_FS=m # CONFIG_AFS_DEBUG is not set CONFIG_9P_FS=m CONFIG_NOVFS=m # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set CONFIG_OSF_PARTITION=y # CONFIG_AMIGA_PARTITION is not set CONFIG_ATARI_PARTITION=y 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=y CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set CONFIG_SGI_PARTITION=y CONFIG_ULTRIX_PARTITION=y CONFIG_SUN_PARTITION=y CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_SYSV68_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="utf8" CONFIG_NLS_CODEPAGE_437=m 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=m 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=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m CONFIG_DLM=m CONFIG_DLM_DEBUG=y # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y CONFIG_UNUSED_SYMBOLS=y CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set # CONFIG_DETECT_SOFTLOCKUP is not set CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_DEBUG_SLAB is not set # 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_STACKTRACE=y # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_WRITECOUNT is not set CONFIG_DEBUG_MEMORY_INIT=y # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_FRAME_POINTER is not set CONFIG_UNWIND_INFO=y CONFIG_STACK_UNWIND=y # CONFIG_BOOT_PRINTK_DELAY is not set CONFIG_RCU_TORTURE_TEST=m # CONFIG_KPROBES_SANITY_TEST is not set CONFIG_BACKTRACE_SELF_TEST=m CONFIG_LKDTM=m # CONFIG_FAULT_INJECTION is not set CONFIG_LATENCYTOP=y CONFIG_SYSCTL_SYSCALL_CHECK=y CONFIG_HAVE_FTRACE=y CONFIG_HAVE_DYNAMIC_FTRACE=y # CONFIG_FTRACE is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_CONTEXT_SWITCH_TRACER is not set CONFIG_PROVIDE_OHCI1394_DMA_INIT=y CONFIG_DYNAMIC_PRINTK_DEBUG=y # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set # CONFIG_STRICT_DEVMEM is not set # CONFIG_X86_VERBOSE_BOOTUP is not set CONFIG_EARLY_PRINTK=y CONFIG_EARLY_PRINTK_DBGP=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC 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_MMIOTRACE is not set 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_DEBUG_BOOT_PARAMS is not set # CONFIG_CPA_DEBUG is not set # CONFIG_OPTIMIZE_INLINING is not set CONFIG_KDB=y CONFIG_KDB_MODULES=m CONFIG_KDB_OFF=y CONFIG_KDB_CONTINUE_CATASTROPHIC=0 CONFIG_KDB_USB=y CONFIG_KDB_KDUMP=y # # Security options # CONFIG_KEYS=y CONFIG_KEYS_DEBUG_PROC_KEYS=y CONFIG_SECURITY=y CONFIG_SECURITY_DEFAULT="apparmor" CONFIG_SECURITY_NETWORK=y # CONFIG_SECURITY_NETWORK_XFRM is not set CONFIG_SECURITY_FILE_CAPABILITIES=y CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT=y # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 CONFIG_SECURITY_APPARMOR_DISABLE=y CONFIG_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_BLKCIPHER=m CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m # # Block modes # CONFIG_CRYPTO_CBC=m CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m 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 # # Digest # CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m 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=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m # CONFIG_CRYPTO_TWOFISH is not set CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_HIFN_795X=m CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y CONFIG_HAVE_KVM=y CONFIG_VIRTUALIZATION=y CONFIG_KVM_KMP=y # CONFIG_KVM is not set CONFIG_VIRTIO=m CONFIG_VIRTIO_RING=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=m CONFIG_CRC_T10DIF=m CONFIG_CRC_ITU_T=m CONFIG_CRC32=y CONFIG_CRC7=m CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_LZO_COMPRESS=m CONFIG_LZO_DECOMPRESS=m CONFIG_GENERIC_ALLOCATOR=y CONFIG_REED_SOLOMON=m CONFIG_REED_SOLOMON_DEC16=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_CHECK_SIGNATURE=y
On 26/05/10 17:25, Ramiro Alba Queipo wrote:> On Wed, 2010-05-26 at 16:48 +0100, Guy Coates wrote: > >>>> One thing to watch out for in your kernel configs is to make sure that: >>>> >>>> CONFIG_SECURITY_FILE_CAPABILITIES=N >>> >>> OK. But the question is if this issue still applies for lustre-1.8.3 and >>> SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite surprising >>> that if this problems persist, Oracle is offering lustre packages for >>> SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ??????? >>> I am just about to start testing, so I''d like to clarify this. >> >> The binary SLES packages are fine; it is the source packages that may be >> problematic, depending on your config. There is a bug filed against this > > Sorry Guy. May be there is something I am missing, but SLES11 rpm kernel > server packages for lustre-1.8.3 are created using a config with > ONFIG_SECURITY_FILE_CAPABILITIES=y (See yourself on the attachementYou are entirely correct. Cheers, Guy -- Dr Guy Coates, Informatics System Group The Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1HH, UK Tel: +44 (0)1223 834244 ex 6925 Fax: +44 (0)1223 496802 -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
On Wed, 2010-05-19 at 14:01 +0200, Heiko Schr?ter wrote:> I know. But the patches are missing for 1.41.10 in that repo. i.e. as this here "e2fsprogs-1.41.6.sun1-patches.tgz"Please find the patches at http://downloads.lustre.org/public/tools/e2fsprogs/1.41.10.sun2/e2fsprogs-1.41.10.sun2-patches.tar.gz Thanks, Girish> Thanks very much for your help. > Regards > Heiko > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
Am Donnerstag 27 Mai 2010, um 09:12:50 schrieben Sie: Thanks very much, Girish ! Regards Heiko> On Wed, 2010-05-19 at 14:01 +0200, Heiko Schr?ter wrote: > > > I know. But the patches are missing for 1.41.10 in that repo. i.e. as this here "e2fsprogs-1.41.6.sun1-patches.tgz" > Please find the patches at > http://downloads.lustre.org/public/tools/e2fsprogs/1.41.10.sun2/e2fsprogs-1.41.10.sun2-patches.tar.gz > > Thanks, > Girish > > > Thanks very much for your help. > > Regards > > Heiko > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss >
Hello, does the following procedure "look" right installing a patched kernel src (i.e. SLES11) and lustre 1.8.3 plus the e2fsprogs.sun2 ? a) Unpack i.e. SLES 11 Kernel src. (I don''t know for sure if the links are really needed, because the Kernel is allready patched.) cd SLES11kernelDir ln -s ../lustre-1.8.3/lustre/kernel_patches/patches patches ln -s ../lustre-1.8.3/lustre/kernel_patches/series/2.6-sles11.series series make menuconfig et.al. b) Reboot new patched kernel. c) Install the LUSTRE 1.8.3 modules depmod -a d) Install E2FSPROG: tar -xzf e2fsprogs-1.41.10-sun2-patches.tar.gz tar -xzf e2fsprogs-1.41.10.sun2.tgz cd e2fsprogs-1.41.10.sun2 mkdir build ln -s ../e2fsprogs-1.41.10-sun2-patches patches ln -s ../e2fsprogs-1.41.10-sun2-patches/series series quilt push -av cd build ../configure --with-lustre=/usr/src/lustre-1.8.3 --enable-fsck make && make install Doing a) to d) on every MDS/OSS before doing e) e) Continue with Chapter 13 "Upgrading lustre". Thanks for any corrections if the above proc is broken. Regards Heiko
On Wednesday 26 May 2010, Guy Coates wrote:> On 26/05/10 17:25, Ramiro Alba Queipo wrote: > > On Wed, 2010-05-26 at 16:48 +0100, Guy Coates wrote: > >>>> One thing to watch out for in your kernel configs is to make sure > >>>> that: > >>>> > >>>> CONFIG_SECURITY_FILE_CAPABILITIES=N > >>> > >>> OK. But the question is if this issue still applies for lustre-1.8.3 > >>> and SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite > >>> surprising that if this problems persist, Oracle is offering lustre > >>> packages for SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ??????? > >>> I am just about to start testing, so I''d like to clarify this. > >> > >> The binary SLES packages are fine; it is the source packages that may be > >> problematic, depending on your config. There is a bug filed against this > > > > Sorry Guy. May be there is something I am missing, but SLES11 rpm kernel > > server packages for lustre-1.8.3 are created using a config with > > ONFIG_SECURITY_FILE_CAPABILITIES=y (See yourself on the attachement > > You are entirely correct.To be clear here, this is a CLIENT side issue. So whatever you do set on the server side is irrelevant. Oracle cannot set kernel options for clients, as those are upstream kernels and lustre is compiled patchless against it. Applying this Lustre patch from bugzilla#15587 should solve the issue without the need to recompile the kernel: https://bugzilla.lustre.org/attachment.cgi?id=29116 Cheers, Bernd -- Bernd Schubert DataDirect Networks
Hi Bernd, Sorry if I insist on this issue or if my questions may seem simple, but just to clarify: On Thu, 2010-05-27 at 12:51 +0200, Bernd Schubert wrote:> > >> The binary SLES packages are fine; it is the source packages that may be > > >> problematic, depending on your config. There is a bug filed against this > > > > > > Sorry Guy. May be there is something I am missing, but SLES11 rpm kernel > > > server packages for lustre-1.8.3 are created using a config with > > > ONFIG_SECURITY_FILE_CAPABILITIES=y (See yourself on the attachement > > > > You are entirely correct. > > To be clear here, this is a CLIENT side issue. So whatever you do set on the > server side is irrelevant. Oracle cannot set kernel options for clients, as > those are upstream kernels and lustre is compiled patchless against it. > > Applying this Lustre patch from bugzilla#15587 should solve the issue without > the need to recompile the kernel: > > https://bugzilla.lustre.org/attachment.cgi?id=29116- Is this an issue that affects every client, both patchless clients and not patchless or only those clients with SLES11 servers.? - May I apply the above patch to build modules that will be used both and servers and clients? (I usually do: no patchless kernel for clients but the same as servers) Regards -- Ramiro Alba Centre Tecnol?gic de Tranfer?ncia de Calor http://www.cttc.upc.edu Escola T?cnica Superior d''Enginyeries Industrial i Aeron?utica de Terrassa Colom 11, E-08222, Terrassa, Barcelona, Spain Tel: (+34) 93 739 86 46 -- Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i d''altres continguts perillosos, i es considera que est? net.
On Fri, May 28, 2010 at 10:12:22AM +0200, Ramiro Alba Queipo wrote:> - Is this an issue that affects every client, both patchless clients and > not patchless or only those clients with SLES11 servers.?The server does not matter here. This is a client side issue. Since CONFIG_SECURITY_FILE_CAPABILITIES is enabled in both the stock SLES11 kernel and our patched kernel, all SLES11 clients are affected.> - May I apply the above patch to build modules that will be used both > and servers and clients? (I usually do: no patchless kernel for clients > but the same as servers)Yes. Although the patch is only needed on clients, you can of course install the same modules on the servers too. Johann
On 2010-05-27, at 02:11, Heiko Schr?ter wrote:> does the following procedure "look" right installing a patched kernel src (i.e. SLES11) and lustre 1.8.3 plus the e2fsprogs.sun2 ?What is your goal, exactly? You don''t really need to rebuild e2fsprogs on every MDS/OSS, and in fact there is no reason to rebuild/reinstall e2fsprogs when updating Lustre - the same e2fsprogs is usable for all Lustre versions. Even if you are building your own Lustre you can probably use the pre-built e2fsprogs.> a) Unpack i.e. SLES 11 Kernel src. > (I don''t know for sure if the links are really needed, because the Kernel is allready patched.) > cd SLES11kernelDir > ln -s ../lustre-1.8.3/lustre/kernel_patches/patches patches > ln -s ../lustre-1.8.3/lustre/kernel_patches/series/2.6-sles11.series series > make menuconfig et.al. > > b) Reboot new patched kernel. > > c) Install the LUSTRE 1.8.3 modules > depmod -a > > d) Install E2FSPROG: > tar -xzf e2fsprogs-1.41.10-sun2-patches.tar.gz > tar -xzf e2fsprogs-1.41.10.sun2.tgz > cd e2fsprogs-1.41.10.sun2 > mkdir build > ln -s ../e2fsprogs-1.41.10-sun2-patches patches > ln -s ../e2fsprogs-1.41.10-sun2-patches/series series > quilt push -av > cd build > ../configure --with-lustre=/usr/src/lustre-1.8.3 --enable-fsck > make && make install > > Doing a) to d) on every MDS/OSS before doing e) > > e) Continue with Chapter 13 "Upgrading lustre". > > > Thanks for any corrections if the above proc is broken. > > Regards > Heiko > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discussCheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc.
Am Samstag 29 Mai 2010, um 05:10:25 schrieben Sie:> On 2010-05-27, at 02:11, Heiko Schr?ter wrote: > > does the following procedure "look" right installing a patched kernel src (i.e. SLES11) and lustre 1.8.3 plus the e2fsprogs.sun2 ? > > What is your goal, exactly?I''am trying to define a procedure for me how to upgrade our lustre 1.6.6 running vanilla 2.6.22.19 kernels (gentoo distribution) to lustre 1.8.3 with SLES11 kernel 2.6.27.39. Having said that i did it on a client and it works for the client side. Before sending 100TB data down the drain i want to make sure that the general approach of upgrading "sounds" reasonable.> You don''t really need to rebuild e2fsprogs on every MDS/OSS, and in fact there is no reason to rebuild/reinstall e2fsprogs when updating Lustre - the same e2fsprogs is usable for all Lustre versions. Even if you are building your own Lustre you can probably use the pre-built e2fsprogs.Hm, that sounds differently (to me) in the READMEs and on the Webpage for upgrading from 1.8.2 to 1.8.3. I cannot not oversee myself what e2fs versions are really needed, as there are different packages for SLES and RH, so i try to stick to the docs as close as poss. For upgrading i understand that i need to use "tunefs.lustre" et al and i''am not sure if these commands trigger some of the e2fsprogs. <Quote> Changes from v1.8.2 to v1.8.3 Recommended e2fsprogs version: 1.41.10-sun2 </Quote> Thanks for your help. Regards Heiko> > > a) Unpack i.e. SLES 11 Kernel src. > > (I don''t know for sure if the links are really needed, because the Kernel is allready patched.) > > cd SLES11kernelDir > > ln -s ../lustre-1.8.3/lustre/kernel_patches/patches patches > > ln -s ../lustre-1.8.3/lustre/kernel_patches/series/2.6-sles11.series series > > make menuconfig et.al. > > > > b) Reboot new patched kernel. > > > > c) Install the LUSTRE 1.8.3 modules > > depmod -a > > > > d) Install E2FSPROG: > > tar -xzf e2fsprogs-1.41.10-sun2-patches.tar.gz > > tar -xzf e2fsprogs-1.41.10.sun2.tgz > > cd e2fsprogs-1.41.10.sun2 > > mkdir build > > ln -s ../e2fsprogs-1.41.10-sun2-patches patches > > ln -s ../e2fsprogs-1.41.10-sun2-patches/series series > > quilt push -av > > cd build > > ../configure --with-lustre=/usr/src/lustre-1.8.3 --enable-fsck > > make && make install > > > > Doing a) to d) on every MDS/OSS before doing e) > > > > e) Continue with Chapter 13 "Upgrading lustre". > > > > > > Thanks for any corrections if the above proc is broken. > > > > Regards > > Heiko > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss >
On 2010-05-31, at 02:49, Heiko Schr?ter wrote: Am Samstag 29 Mai 2010, um 05:10:25 schrieben Sie:> I''am trying to define a procedure for me how to upgrade our lustre 1.6.6 running vanilla 2.6.22.19 kernels (gentoo distribution) to lustre 1.8.3 with SLES11 kernel 2.6.27.39. > Having said that i did it on a client and it works for the client side. > Before sending 100TB data down the drain i want to make sure that the general approach of upgrading "sounds" reasonable. > >> You don''t really need to rebuild e2fsprogs on every MDS/OSS, and in fact there is no reason to rebuild/reinstall e2fsprogs when updating Lustre - the same e2fsprogs is usable for all Lustre versions. Even if you are building your own Lustre you can probably use the pre-built e2fsprogs. > > Hm, that sounds differently (to me) in the READMEs and on the Webpage for upgrading from 1.8.2 to 1.8.3.Sorry, you are right that if you are upgrading from Lustre 1.6.6 (which is quite old) that you should also upgrade to the latest e2fsprogs at the same time. While there are no immediate incompatibilities between the two, of course the newer version has quite a number of bug fixes from upstream and also Lustre-specific fixes. I was just pointing out that the version of e2fsprogs is not directly tied to the minor release of Lustre. In fact Lustre and e2fsprogs are released independently, so the goal is that the latest version of e2fsprogs can run against all versions of Lustre. The only reason we need different e2fsprogs binaries for different distros is that unfortunately the RPM dependency and library names are different between RHEL and SLES (even if they are the same version) so a single RPM will not install cleanly on both distros.> I cannot not oversee myself what e2fs versions are really needed, as there are different packages for SLES and RH, so i try to stick to the docs as close as poss. > For upgrading i understand that i need to use "tunefs.lustre" et al and i''am not sure if these commands trigger some of the e2fsprogs.Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc.