[gentoo-user] problems getting systemd to work

[gentoo-user] problems getting systemd to work

[covici]

Hi.  I have been trying to get systemd to boot, but I have run into
several problems and need some help.  I am using everything but /boot as
lvm's, with a separate user partition.  I had to copy systemd to /sbin
because the initrd looks for the realinit too soon, but that is maybe
another matter.  

I had set confirm_spawn=y in the kernel command line, but it only waits
a short time and then says assuming positive response and tries to
continue -- how can I get it to wait for me?  Also, even so, it died on
mounting of my lvms, saying there was some kind of timeout and came to a
complete halt (maybe it was a shell, but no prompt) after all those
failed, so I could do nothing much.  Openrc works fine, but I was trying
to get gnome to work, so I was trying to use systemd.

It saved no logs (none I can find), but then again /var was not mounted.

Any help with this would be appreciated.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Mon, May 12, 2014 at 2:22 AM,  <covici@ccs.covici.com> wrote:
> Hi.  I have been trying to get systemd to boot, but I have run into
> several problems and need some help.  I am using everything but /boot as
> lvm's, with a separate user partition.  I had to copy systemd to /sbin
> because the initrd looks for the realinit too soon, but that is maybe
> another matter.

Moving systemd to /sbin sounds like it's not going to work. Run
readelf -d /usr/lib/systemd/systemd; all the NEEDED libraries on
/usr/lib should be available to the binary at the time it's being
executed.

How did you get your initramfs? dracut? genkernel? Roll your own?

> I had set confirm_spawn=y in the kernel command line, but it only waits
> a short time and then says assuming positive response and tries to
> continue -- how can I get it to wait for me?  Also, even so, it died on
> mounting of my lvms, saying there was some kind of timeout and came to a
> complete halt (maybe it was a shell, but no prompt) after all those
> failed, so I could do nothing much.  Openrc works fine, but I was trying
> to get gnome to work, so I was trying to use systemd.
>
> It saved no logs (none I can find), but then again /var was not mounted.
>
> Any help with this would be appreciated.

I use dracut for my initramfs; I would recommend you to try it.
However, last time I tried to use it with LVM (a few days ago), the
last version (037) failed, but 036-r4 worked perfectly.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Mon, May 12, 2014 at 2:22 AM,  <covici@ccs.covici.com> wrote:
> > Hi.  I have been trying to get systemd to boot, but I have run into
> > several problems and need some help.  I am using everything but /boot as
> > lvm's, with a separate user partition.  I had to copy systemd to /sbin
> > because the initrd looks for the realinit too soon, but that is maybe
> > another matter.
> 
> Moving systemd to /sbin sounds like it's not going to work. Run
> readelf -d /usr/lib/systemd/systemd; all the NEEDED libraries on
> /usr/lib should be available to the binary at the time it's being
> executed.

How can I do this, genkernel looks for its init before it mounts /usr
and genkernel-next will not mount the separate /usr at all.  My latest
initrd is from the very latest genkernel.

But how to get a complete history of systemd actions in the order that
they are done, I thought the confirm_spawn would do this for me -- at
least for my initial debugging.


> 
> How did you get your initramfs? dracut? genkernel? Roll your own?
> 
> > I had set confirm_spawn=y in the kernel command line, but it only waits
> > a short time and then says assuming positive response and tries to
> > continue -- how can I get it to wait for me?  Also, even so, it died on
> > mounting of my lvms, saying there was some kind of timeout and came to a
> > complete halt (maybe it was a shell, but no prompt) after all those
> > failed, so I could do nothing much.  Openrc works fine, but I was trying
> > to get gnome to work, so I was trying to use systemd.
> >
> > It saved no logs (none I can find), but then again /var was not mounted.
> >
> > Any help with this would be appreciated.
> 
> I use dracut for my initramfs; I would recommend you to try it.
> However, last time I tried to use it with LVM (a few days ago), the
> last version (037) failed, but 036-r4 worked perfectly.
> 
> Regards.
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-12 4:15 GMT-06:00  <covici@ccs.covici.com>:

> How can I do this, genkernel looks for its init before it mounts /usr
> and genkernel-next will not mount the separate /usr at all.  My latest
> initrd is from the very latest genkernel.
>
> But how to get a complete history of systemd actions in the order that
> they are done, I thought the confirm_spawn would do this for me -- at
> least for my initial debugging.
>

I have had this trouble too, and a very similar setup than you, and
after a few workarounds I got to boot with a genkernel and a dracut
generated initramfs, so it can be done both ways, but i would
recommend dracut, since is more straight forward in practice, and you
can setup once and then just generate initramfs that surely will work.
The most important part is your kernel boot comand line, giving
instructions so your system specific lvm volumes (root, usr and var if
separated). mine looks like this
"rd.lvm rd.lvm.vg=gentoovg rd.lvm.lv=gentoovg/root
rd.lvm.lv=gentoovg/usr root=/dev/mapper/gentoovg-root
ccinit=/usr/lib/systemd/systemd quiet"
A little too long in my opinion, but works, and the rd.lvm.lv parts
result redundant if rd.lvm.vg is already set, i think, it worked when
I tested, but I kept the redundancy just in case.
this can be setup in sevaral ways, directly when compiling the kernel,
using dracut the config file, or the bootloader, I used dracut since I
wanted to centralize the boot process configuration as much as
possible.
Also be sure that the lvm binaries are included in the initramfs, if
you will be using dracut you would need to add to /etc/dracut.conf:

use_fstab="yes"
host_cmdline="yes"
kernel_cmdline="your_cmd_line"

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Mon, May 12, 2014 at 5:15 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Mon, May 12, 2014 at 2:22 AM,  <covici@ccs.covici.com> wrote:
>> > Hi.  I have been trying to get systemd to boot, but I have run into
>> > several problems and need some help.  I am using everything but /boot as
>> > lvm's, with a separate user partition.  I had to copy systemd to /sbin
>> > because the initrd looks for the realinit too soon, but that is maybe
>> > another matter.
>>
>> Moving systemd to /sbin sounds like it's not going to work. Run
>> readelf -d /usr/lib/systemd/systemd; all the NEEDED libraries on
>> /usr/lib should be available to the binary at the time it's being
>> executed.
>
> How can I do this, genkernel looks for its init before it mounts /usr
> and genkernel-next will not mount the separate /usr at all.  My latest
> initrd is from the very latest genkernel.

With genkernel, I don't know; I never used it. On the other hand,
dracut is designed to work with systemd; if you use the systemd USE
flag and the systemd module, it even uses systemd *inside* the
initramfs.

> But how to get a complete history of systemd actions in the order that
> they are done, I thought the confirm_spawn would do this for me -- at
> least for my initial debugging.

The problem obviously is not in systemd, but in the integration of
genkernel+systemd. I repeat, I never used genkernel, so I don't know
what you can do.

That being said, "get a complete history of systemd actions in the
order that they are done" will not tell you much: systemd uses heavy
parallelization, so in some runs the order in which actions are
performed will be different from others.

The problem is that if systemd is installed into /usr/lib (which is
Gentoo's case), then /usr should be mounted before systemd starts.
That's responsibility of the initramfs, not of systemd, and the
solution lies in the initramfs, not in systemd.

My only possible recommendation would be for you to try dracut.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2014-05-12 4:15 GMT-06:00  <covici@ccs.covici.com>:
> 
> > How can I do this, genkernel looks for its init before it mounts /usr
> > and genkernel-next will not mount the separate /usr at all.  My latest
> > initrd is from the very latest genkernel.
> >
> > But how to get a complete history of systemd actions in the order that
> > they are done, I thought the confirm_spawn would do this for me -- at
> > least for my initial debugging.
> >
> 
> I have had this trouble too, and a very similar setup than you, and
> after a few workarounds I got to boot with a genkernel and a dracut
> generated initramfs, so it can be done both ways, but i would
> recommend dracut, since is more straight forward in practice, and you
> can setup once and then just generate initramfs that surely will work.
> The most important part is your kernel boot comand line, giving
> instructions so your system specific lvm volumes (root, usr and var if
> separated). mine looks like this
> "rd.lvm rd.lvm.vg=gentoovg rd.lvm.lv=gentoovg/root
> rd.lvm.lv=gentoovg/usr root=/dev/mapper/gentoovg-root
> ccinit=/usr/lib/systemd/systemd quiet"
> A little too long in my opinion, but works, and the rd.lvm.lv parts
> result redundant if rd.lvm.vg is already set, i think, it worked when
> I tested, but I kept the redundancy just in case.
> this can be setup in sevaral ways, directly when compiling the kernel,
> using dracut the config file, or the bootloader, I used dracut since I
> wanted to centralize the boot process configuration as much as
> possible.
> Also be sure that the lvm binaries are included in the initramfs, if
> you will be using dracut you would need to add to /etc/dracut.conf:
> 
> use_fstab="yes"
> host_cmdline="yes"
> kernel_cmdline="your_cmd_line"

My kernel command line is like this:
init=/linuxrc ramdisk=8192 real_root=/dev/mapper/linux--files-64--root
udev video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M dolvm
rootfstype=ext4 real_init=/sbin/systemd systemd.confirm_spawn=yes

I thought the dolvm would take care of all lvm related stuff, I don't
understand the rd.lvm parts at all, I have never seen such.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Mon, May 12, 2014 at 5:15 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Mon, May 12, 2014 at 2:22 AM,  <covici@ccs.covici.com> wrote:
> >> > Hi.  I have been trying to get systemd to boot, but I have run into
> >> > several problems and need some help.  I am using everything but /boot as
> >> > lvm's, with a separate user partition.  I had to copy systemd to /sbin
> >> > because the initrd looks for the realinit too soon, but that is maybe
> >> > another matter.
> >>
> >> Moving systemd to /sbin sounds like it's not going to work. Run
> >> readelf -d /usr/lib/systemd/systemd; all the NEEDED libraries on
> >> /usr/lib should be available to the binary at the time it's being
> >> executed.
> >
> > How can I do this, genkernel looks for its init before it mounts /usr
> > and genkernel-next will not mount the separate /usr at all.  My latest
> > initrd is from the very latest genkernel.
> 
> With genkernel, I don't know; I never used it. On the other hand,
> dracut is designed to work with systemd; if you use the systemd USE
> flag and the systemd module, it even uses systemd *inside* the
> initramfs.
> 
> > But how to get a complete history of systemd actions in the order that
> > they are done, I thought the confirm_spawn would do this for me -- at
> > least for my initial debugging.
> 
> The problem obviously is not in systemd, but in the integration of
> genkernel+systemd. I repeat, I never used genkernel, so I don't know
> what you can do.
> 
> That being said, "get a complete history of systemd actions in the
> order that they are done" will not tell you much: systemd uses heavy
> parallelization, so in some runs the order in which actions are
> performed will be different from others.
> 
> The problem is that if systemd is installed into /usr/lib (which is
> Gentoo's case), then /usr should be mounted before systemd starts.
> That's responsibility of the initramfs, not of systemd, and the
> solution lies in the initramfs, not in systemd.
> 
> My only possible recommendation would be for you to try dracut.
> 
> Regards.
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
> 

OK, I will try dracut, but I still want to know what systemd is doing,
what processes its spawning, etc.  -- how can I find this out -- I
thought to use the confirm_spawn, but it times out and keeps going, what
can I do instead?

Thanks people for all your responses, this is a great list.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
[snip]
> OK, I will try dracut,

I hope it works with dracut. This is my kernel command line and
RAID/LVM related stuff from GRUB2:

GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
GRUB_PRELOAD_MODULES="lvm mdraid1x"

And this is my dracut.conf (minus comments):

add_dracutmodules+="crypt lvm mdraid systemd"
add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
fscks="umount mount /sbin/fsck* e2fsck"

That's it. I didn't touched anything else to make dracut+systemd work
with LVM and RAID (and LUKS, but that doesn't matter).

Also, dracut comes with extensive and very clear documentation; check
the man pages included.

> but I still want to know what systemd is doing,
> what processes its spawning, etc.  -- how can I find this out -- I
> thought to use the confirm_spawn, but it times out and keeps going, what
> can I do instead?

You can use bootchart:

man 1 systemd-bootchart

It will produce a chart with all the processes, and how long it takes
for every one of them. But remember, the order depends on which one
finishes before, and that can change from boot to boot.

> Thanks people for all your responses, this is a great list.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
> [snip]
> > OK, I will try dracut,
> 
> I hope it works with dracut. This is my kernel command line and
> RAID/LVM related stuff from GRUB2:
> 
> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
> GRUB_PRELOAD_MODULES="lvm mdraid1x"
> 
> And this is my dracut.conf (minus comments):
> 
> add_dracutmodules+="crypt lvm mdraid systemd"
> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
> fscks="umount mount /sbin/fsck* e2fsck"
> 
> That's it. I didn't touched anything else to make dracut+systemd work
> with LVM and RAID (and LUKS, but that doesn't matter).
> 
> Also, dracut comes with extensive and very clear documentation; check
> the man pages included.
> 
> > but I still want to know what systemd is doing,
> > what processes its spawning, etc.  -- how can I find this out -- I
> > thought to use the confirm_spawn, but it times out and keeps going, what
> > can I do instead?
> 
> You can use bootchart:
> 
> man 1 systemd-bootchart
> 
> It will produce a chart with all the processes, and how long it takes
> for every one of them. But remember, the order depends on which one
> finishes before, and that can change from boot to boot.
> 
> > Thanks people for all your responses, this is a great list.
> 
> Regards.
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias

Well, since I am unable to see, the graph would not do me any good, any
way to get it in text form?  What I want to see (and I know the order
may change) is which starts first and so on, to make sure targets,
etc. do what I want them to do.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
>> [snip]
>> > OK, I will try dracut,
>>
>> I hope it works with dracut. This is my kernel command line and
>> RAID/LVM related stuff from GRUB2:
>>
>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
>> GRUB_PRELOAD_MODULES="lvm mdraid1x"
>>
>> And this is my dracut.conf (minus comments):
>>
>> add_dracutmodules+="crypt lvm mdraid systemd"
>> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
>> fscks="umount mount /sbin/fsck* e2fsck"
>>
>> That's it. I didn't touched anything else to make dracut+systemd work
>> with LVM and RAID (and LUKS, but that doesn't matter).
>>
>> Also, dracut comes with extensive and very clear documentation; check
>> the man pages included.
>>
>> > but I still want to know what systemd is doing,
>> > what processes its spawning, etc.  -- how can I find this out -- I
>> > thought to use the confirm_spawn, but it times out and keeps going, what
>> > can I do instead?
>>
>> You can use bootchart:
>>
>> man 1 systemd-bootchart
>>
>> It will produce a chart with all the processes, and how long it takes
>> for every one of them. But remember, the order depends on which one
>> finishes before, and that can change from boot to boot.
>>
>> > Thanks people for all your responses, this is a great list.
>>
>> Regards.
>> --
>> Canek Peláez Valdés
>> Profesor de asignatura, Facultad de Ciencias
>
> Well, since I am unable to see, the graph would not do me any good, any
> way to get it in text form?  What I want to see (and I know the order
> may change) is which starts first and so on, to make sure targets,
> etc. do what I want them to do.

Try adding this to your kernel command line:
systemd.log_target=console systemd.log_level=debug. It will add a lot
of output, including what is being executed.

Everything is documented in the man page: man  1 systemd.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-12 10:22 GMT-06:00  <covici@ccs.covici.com>:

> My kernel command line is like this:
> init=/linuxrc ramdisk=8192 real_root=/dev/mapper/linux--files-64--root
> udev video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M dolvm
> rootfstype=ext4 real_init=/sbin/systemd systemd.confirm_spawn=yes
>
> I thought the dolvm would take care of all lvm related stuff, I don't
> understand the rd.lvm parts at all, I have never seen such.
>
I tried several times with only dolvm, but that didn't work for me,  I
found the documentation for rd.lvm 'man 7 dracut.kernel', in the LVM
section.

Re: [gentoo-user] problems getting systemd to work

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2014-05-12 10:22 GMT-06:00  <covici@ccs.covici.com>:
> 
> > My kernel command line is like this:
> > init=/linuxrc ramdisk=8192 real_root=/dev/mapper/linux--files-64--root
> > udev video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M dolvm
> > rootfstype=ext4 real_init=/sbin/systemd systemd.confirm_spawn=yes
> >
> > I thought the dolvm would take care of all lvm related stuff, I don't
> > understand the rd.lvm parts at all, I have never seen such.
> >
> I tried several times with only dolvm, but that didn't work for me,  I
> found the documentation for rd.lvm 'man 7 dracut.kernel', in the LVM
> section.

Ahhh, these are dracut specific, that is why I had never heard of them
before.  So I am off to read the dracut docs before I change anything!

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2014-05-12 4:15 GMT-06:00  <covici@ccs.covici.com>:
> 
> > How can I do this, genkernel looks for its init before it mounts /usr
> > and genkernel-next will not mount the separate /usr at all.  My latest
> > initrd is from the very latest genkernel.
> >
> > But how to get a complete history of systemd actions in the order that
> > they are done, I thought the confirm_spawn would do this for me -- at
> > least for my initial debugging.
> >
> 
> I have had this trouble too, and a very similar setup than you, and
> after a few workarounds I got to boot with a genkernel and a dracut
> generated initramfs, so it can be done both ways, but i would
> recommend dracut, since is more straight forward in practice, and you
> can setup once and then just generate initramfs that surely will work.
> The most important part is your kernel boot comand line, giving
> instructions so your system specific lvm volumes (root, usr and var if
> separated). mine looks like this
> "rd.lvm rd.lvm.vg=gentoovg rd.lvm.lv=gentoovg/root
> rd.lvm.lv=gentoovg/usr root=/dev/mapper/gentoovg-root
> ccinit=/usr/lib/systemd/systemd quiet"
> A little too long in my opinion, but works, and the rd.lvm.lv parts
> result redundant if rd.lvm.vg is already set, i think, it worked when
> I tested, but I kept the redundancy just in case.
> this can be setup in sevaral ways, directly when compiling the kernel,
> using dracut the config file, or the bootloader, I used dracut since I
> wanted to centralize the boot process configuration as much as
> possible.
> Also be sure that the lvm binaries are included in the initramfs, if
> you will be using dracut you would need to add to /etc/dracut.conf:
> 
> use_fstab="yes"
> host_cmdline="yes"
> kernel_cmdline="your_cmd_line"

Hi.  Well, even with use_fstab=yes, it does not put one, just
/etc/fstab.empty of 0 length -- how can I fix?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 13.05.2014 05:46, schrieb covici@ccs.covici.com:

> Hi.  Well, even with use_fstab=yes, it does not put one, just
> /etc/fstab.empty of 0 length -- how can I fix?

I didn't read the full thread yet ... but let me get that straight for
me to understand the status:

* You want to have / and everything on LVM volumes (LVs) and /boot (not
/boot/efi, right? No EFI here?) as a separate partition.

Are you able to boot this via openrc?

* What is the status now with dracut? The mentioned options ... I don't
have them in my config (although my setup is now completely different
from yours ... anyway).

* Do you have systemd now installed in the default location?

* global USE-flag "systemd" set? and recompiled stuff ... ?

* grub-2, right?

Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 13.05.2014 05:46, schrieb covici@ccs.covici.com:
> 
> > Hi.  Well, even with use_fstab=yes, it does not put one, just
> > /etc/fstab.empty of 0 length -- how can I fix?
> 
> I didn't read the full thread yet ... but let me get that straight for
> me to understand the status:
> 
> * You want to have / and everything on LVM volumes (LVs) and /boot (not
> /boot/efi, right? No EFI here?) as a separate partition.

Correct.

> 
> Are you able to boot this via openrc?

Yes openrc works fine.

> 
> * What is the status now with dracut? The mentioned options ... I don't
> have them in my config (although my setup is now completely different
> from yours ... anyway).

I emerged it and want to use it to boot with systemd.

> 

 * Do you have systemd now installed in the default location?

Yes.

> 
> * global USE-flag "systemd" set? and recompiled stuff ... ?

Yes.

> 
> * grub-2, right?

Nope, lilo.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 13.05.2014 14:29, schrieb covici@ccs.covici.com:

>> * What is the status now with dracut? The mentioned options ... I
>> don't have them in my config (although my setup is now completely
>> different from yours ... anyway).
> 
> I emerged it and want to use it to boot with systemd.

Did you configure dracut as Canek's examples show?
Adding in the modules etc ?

Could you build the initramfs with it, matching your kernel?

Do you successfully use that initramfs with openrc then?

>> * grub-2, right?
> 
> Nope, lilo.

serious? Wow ... I have no experience with that combination ...

So you have something like:

 append = "quiet init=/usr/lib/systemd/systemd"

in your lilo.conf and applied it ... ?

Stefan

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-12 21:46 GMT-06:00  <covici@ccs.covici.com>:
> Hi.  Well, even with use_fstab=yes, it does not put one, just
> /etc/fstab.empty of 0 length -- how can I fix?
>
That is strange, never had this problem, actually adding this made it
work for me, I assume you actually used the ' "yes" ', might be
important for the syntax, I uncompressed my ramdisk a few minutes ago
to actually verify the fstab, and it is in fact included, might be
other parameters missing in cofiguration, all uncomented parameters in
my dracut.conf are these in case it might help you:

logfile=/var/log/dracut.log
fileloglvl=6
add_dracutmodules+="lvm bash dm kernel-modules systemd"
lvmconf="yes"
use_fstab="yes"
host_cmdline="yes"
kernel_cmdline="cmdline..."

And when generating I just simply run:
dracut --kver 'kernel_version'

As you see my configuration is pretty simple, I suggest you to try
forcing the inclussion of fstab(extract, and re-compress the image),
to verify if it solves your booting problem, it might be a dracut
bug(tough it seems a relatively simple feature to be that prone to
bugs).

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-13 7:02 GMT-06:00 Jc García <jyo.garcia@gmail.com>:
> 2014-05-12 21:46 GMT-06:00  <covici@ccs.covici.com>:
>> Hi.  Well, even with use_fstab=yes, it does not put one, just
>> /etc/fstab.empty of 0 length -- how can I fix?
>>
> That is strange, never had this problem, actually adding this made it
> work for me, I assume you actually used the ' "yes" ', might be
> important for the syntax, I uncompressed my ramdisk a few minutes ago
> to actually verify the fstab, and it is in fact included, might be
> other parameters missing in cofiguration, all uncomented parameters in
> my dracut.conf are these in case it might help you:
>
Sorry I did a wrong cd(I still sleepy, is early morning here), I have
the same fstab.empty with nothing inside. so I'm lost here.

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 13.05.2014 14:29, schrieb covici@ccs.covici.com:
> 
> >> * What is the status now with dracut? The mentioned options ... I
> >> don't have them in my config (although my setup is now completely
> >> different from yours ... anyway).
> > 
> > I emerged it and want to use it to boot with systemd.
> 
> Did you configure dracut as Canek's examples show?
> Adding in the modules etc ?
> 
> Could you build the initramfs with it, matching your kernel?
> 
> Do you successfully use that initramfs with openrc then?
> 
> >> * grub-2, right?
> > 
> > Nope, lilo.
> 
> serious? Wow ... I have no experience with that combination ...
> 
> So you have something like:
> 
>  append = "quiet init=/usr/lib/systemd/systemd"
> 
> in your lilo.conf and applied it ... ?

Nope, dracut does things different, so I am still working on the kernel
command line.  My question was about the /etc/fstab.empty problem.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-13 7:18 GMT-06:00  <covici@ccs.covici.com>:
>
> Nope, dracut does things different, so I am still working on the kernel
> command line.  My question was about the /etc/fstab.empty problem.
>
In the documentation it says, enabling this, uses the fstab instead of
 /proc/self/mountinfo, when generating the image, it does not say it
includes it, so I think that is working properly. Have you tried
booting manually from a grub command line(I read you use lilo, I don't
know if it has this feature, but the idea is manually write your
kernel command line before boot ), this has helped me several times
when finding booting problems, you can use anything with grub in it
(livecd, usb, etc...) so you don't have to install it, in case you are
not familiar with grub.

Re: [gentoo-user] problems getting systemd to work

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2014-05-12 21:46 GMT-06:00  <covici@ccs.covici.com>:
> > Hi.  Well, even with use_fstab=yes, it does not put one, just
> > /etc/fstab.empty of 0 length -- how can I fix?
> >
> That is strange, never had this problem, actually adding this made it
> work for me, I assume you actually used the ' "yes" ', might be
> important for the syntax, I uncompressed my ramdisk a few minutes ago
> to actually verify the fstab, and it is in fact included, might be
> other parameters missing in cofiguration, all uncomented parameters in
> my dracut.conf are these in case it might help you:
> 
> logfile=/var/log/dracut.log
> fileloglvl=6
> add_dracutmodules+="lvm bash dm kernel-modules systemd"
> lvmconf="yes"
> use_fstab="yes"
> host_cmdline="yes"
> kernel_cmdline="cmdline..."
> 
> And when generating I just simply run:
> dracut --kver 'kernel_version'
> 
> As you see my configuration is pretty simple, I suggest you to try
> forcing the inclussion of fstab(extract, and re-compress the image),
> to verify if it solves your booting problem, it might be a dracut
> bug(tough it seems a relatively simple feature to be that prone to
> bugs).

hmmm, do we really need add_dracutmodules+="lvm bash dm kernel-modules
systemd"


I had the fstab with and without the quotes,  but no difference.  Maybe
I need to include the thing individually?



-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Jc García <jyo.garcia@gmail.com> wrote:

> 2014-05-13 7:18 GMT-06:00  <covici@ccs.covici.com>:
> >
> > Nope, dracut does things different, so I am still working on the kernel
> > command line.  My question was about the /etc/fstab.empty problem.
> >
> In the documentation it says, enabling this, uses the fstab instead of
>  /proc/self/mountinfo, when generating the image, it does not say it
> includes it, so I think that is working properly. Have you tried
> booting manually from a grub command line(I read you use lilo, I don't
> know if it has this feature, but the idea is manually write your
> kernel command line before boot ), this has helped me several times
> when finding booting problems, you can use anything with grub in it
> (livecd, usb, etc...) so you don't have to install it, in case you are
> not familiar with grub.

Well, if this is OK, then I can proceed, I thought that the systemd
generator needed the actual /etc/fstab file to generate the correct
mount events, so I was concerned that this would not happen, but maybe
the initrd does not need to do that so much.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-13 7:43 GMT-06:00  <covici@ccs.covici.com>:
> Jc García <jyo.garcia@gmail.com> wrote:
>
>> 2014-05-12 21:46 GMT-06:00  <covici@ccs.covici.com>:
>> > Hi.  Well, even with use_fstab=yes, it does not put one, just
>> > /etc/fstab.empty of 0 length -- how can I fix?
>> >
>> That is strange, never had this problem, actually adding this made it
>> work for me, I assume you actually used the ' "yes" ', might be
>> important for the syntax, I uncompressed my ramdisk a few minutes ago
>> to actually verify the fstab, and it is in fact included, might be
>> other parameters missing in cofiguration, all uncomented parameters in
>> my dracut.conf are these in case it might help you:
>>
>> logfile=/var/log/dracut.log
>> fileloglvl=6
>> add_dracutmodules+="lvm bash dm kernel-modules systemd"
>> lvmconf="yes"
>> use_fstab="yes"
>> host_cmdline="yes"
>> kernel_cmdline="cmdline..."
>>
>> And when generating I just simply run:
>> dracut --kver 'kernel_version'
>>
>> As you see my configuration is pretty simple, I suggest you to try
>> forcing the inclussion of fstab(extract, and re-compress the image),
>> to verify if it solves your booting problem, it might be a dracut
>> bug(tough it seems a relatively simple feature to be that prone to
>> bugs).
>
> hmmm, do we really need add_dracutmodules+="lvm bash dm kernel-modules
> systemd"
>

It's not necessary  indeed, the Idea was you to compare this with
yours, since its working here, for example bash is actually a thing of
mine wanting a nice shell even in the initrd. you include what fits
your needs.
>
> I had the fstab with and without the quotes,  but no difference.  Maybe
> I need to include the thing individually?
>
>
>
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>          John Covici
>          covici@ccs.covici.com
>

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
> >> [snip]
> >> > OK, I will try dracut,
> >>
> >> I hope it works with dracut. This is my kernel command line and
> >> RAID/LVM related stuff from GRUB2:
> >>
> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
> >>
> >> And this is my dracut.conf (minus comments):
> >>
> >> add_dracutmodules+="crypt lvm mdraid systemd"
> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
> >> fscks="umount mount /sbin/fsck* e2fsck"
> >>
> >> That's it. I didn't touched anything else to make dracut+systemd work
> >> with LVM and RAID (and LUKS, but that doesn't matter).
> >>
> >> Also, dracut comes with extensive and very clear documentation; check
> >> the man pages included.
> >>
> >> > but I still want to know what systemd is doing,
> >> > what processes its spawning, etc.  -- how can I find this out -- I
> >> > thought to use the confirm_spawn, but it times out and keeps going, what
> >> > can I do instead?
> >>
> >> You can use bootchart:
> >>
> >> man 1 systemd-bootchart
> >>
> >> It will produce a chart with all the processes, and how long it takes
> >> for every one of them. But remember, the order depends on which one
> >> finishes before, and that can change from boot to boot.
> >>
> >> > Thanks people for all your responses, this is a great list.
> >>
> >> Regards.
> >> --
> >> Canek Peláez Valdés
> >> Profesor de asignatura, Facultad de Ciencias
> >
> > Well, since I am unable to see, the graph would not do me any good, any
> > way to get it in text form?  What I want to see (and I know the order
> > may change) is which starts first and so on, to make sure targets,
> > etc. do what I want them to do.
> 
> Try adding this to your kernel command line:
> systemd.log_target=console systemd.log_level=debug. It will add a lot
> of output, including what is being executed.
> 
> Everything is documented in the man page: man  1 systemd.

Well, I rebooted under dracut, but it did not do the lvmscan and so the
job trying to find the root file system timed out after 90 seconds.  It
took me to the emergency shell which I had specified, and I was able to
do the lvm_scan and them magically root got mounted under sysroot, but I
had no idea what to do next  to maybe get things going.

So how can I get dracut to do its lvm_scan -- I even added the line 
add_dracutmodules+="lvm"
but no joy.
I saved the rdsosreport.txt and if that is of any use, I can post it.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
> >> [snip]
> >> > OK, I will try dracut,
> >>
> >> I hope it works with dracut. This is my kernel command line and
> >> RAID/LVM related stuff from GRUB2:
> >>
> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
> >>
> >> And this is my dracut.conf (minus comments):
> >>
> >> add_dracutmodules+="crypt lvm mdraid systemd"
> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
> >> fscks="umount mount /sbin/fsck* e2fsck"
> >>
> >> That's it. I didn't touched anything else to make dracut+systemd work
> >> with LVM and RAID (and LUKS, but that doesn't matter).
> >>
> >> Also, dracut comes with extensive and very clear documentation; check
> >> the man pages included.
> >>
> >> > but I still want to know what systemd is doing,
> >> > what processes its spawning, etc.  -- how can I find this out -- I
> >> > thought to use the confirm_spawn, but it times out and keeps going, what
> >> > can I do instead?
> >>
> >> You can use bootchart:
> >>
> >> man 1 systemd-bootchart
> >>
> >> It will produce a chart with all the processes, and how long it takes
> >> for every one of them. But remember, the order depends on which one
> >> finishes before, and that can change from boot to boot.
> >>
> >> > Thanks people for all your responses, this is a great list.
> >>
> >> Regards.
> >> --
> >> Canek Peláez Valdés
> >> Profesor de asignatura, Facultad de Ciencias
> >
> > Well, since I am unable to see, the graph would not do me any good, any
> > way to get it in text form?  What I want to see (and I know the order
> > may change) is which starts first and so on, to make sure targets,
> > etc. do what I want them to do.
> 
> Try adding this to your kernel command line:
> systemd.log_target=console systemd.log_level=debug. It will add a lot
> of output, including what is being executed.

I also in my kernel command line said rd.lvm=1 just to make sure.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-14 3:43 GMT-06:00  <covici@ccs.covici.com>:

> I also in my kernel command line said rd.lvm=1 just to make sure.
>

Have tried this too(only rd.lvm), until I didn't tell what to
recognize nothing was done, this might be a bug, but I forgot about it
.

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-14 3:40 GMT-06:00  <covici@ccs.covici.com>:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
>> > Canek Peláez Valdés <caneko@gmail.com> wrote:
>> >
>> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
>> >> [snip]
>> >> > OK, I will try dracut,
>> >>
>> >> I hope it works with dracut. This is my kernel command line and
>> >> RAID/LVM related stuff from GRUB2:
>> >>
>> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
>> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
>> >>
>> >> And this is my dracut.conf (minus comments):
>> >>
>> >> add_dracutmodules+="crypt lvm mdraid systemd"
>> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
>> >> fscks="umount mount /sbin/fsck* e2fsck"
>> >>
>> >> That's it. I didn't touched anything else to make dracut+systemd work
>> >> with LVM and RAID (and LUKS, but that doesn't matter).
>> >>
>> >> Also, dracut comes with extensive and very clear documentation; check
>> >> the man pages included.
>> >>
>> >> > but I still want to know what systemd is doing,
>> >> > what processes its spawning, etc.  -- how can I find this out -- I
>> >> > thought to use the confirm_spawn, but it times out and keeps going, what
>> >> > can I do instead?
>> >>
>> >> You can use bootchart:
>> >>
>> >> man 1 systemd-bootchart
>> >>
>> >> It will produce a chart with all the processes, and how long it takes
>> >> for every one of them. But remember, the order depends on which one
>> >> finishes before, and that can change from boot to boot.
>> >>
>> >> > Thanks people for all your responses, this is a great list.
>> >>
>> >> Regards.
>> >> --
>> >> Canek Peláez Valdés
>> >> Profesor de asignatura, Facultad de Ciencias
>> >
>> > Well, since I am unable to see, the graph would not do me any good, any
>> > way to get it in text form?  What I want to see (and I know the order
>> > may change) is which starts first and so on, to make sure targets,
>> > etc. do what I want them to do.
>>
>> Try adding this to your kernel command line:
>> systemd.log_target=console systemd.log_level=debug. It will add a lot
>> of output, including what is being executed.
>>
>> Everything is documented in the man page: man  1 systemd.
>
> Well, I rebooted under dracut, but it did not do the lvmscan and so the
> job trying to find the root file system timed out after 90 seconds.  It
> took me to the emergency shell which I had specified, and I was able to
> do the lvm_scan and them magically root got mounted under sysroot, but I
> had no idea what to do next  to maybe get things going.
>
> So how can I get dracut to do its lvm_scan -- I even added the line
> add_dracutmodules+="lvm"

This is a must if you are not running 'dracut --lvmconf'

> but no joy.
> I saved the rdsosreport.txt and if that is of any use, I can post it.
>
In the dracut manpage, I found the '--print-cmdline' argument , it
generates a suggested kernel command line  , I hadn't used it before,
but this what it printed:

rd.lvm.lv=gentoovg/usr
rd.lvm.lv=gentoovg/root
root=/dev/mapper/gentoovg-root rootflags=defaults rootfstype=ext4

So I guess, its neccesary to have this in the command line. At the
time I struggled for an entire day with the same timeout when my LVs
where not recognized, did research trial/error with dracut and
genkernel, got them both working, stayed with dracut because I liked
it, I tried to avoid this struggle for you on my first response, but
I see is going to take you longer...

> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>          John Covici
>          covici@ccs.covici.com
>
PD: RTFM.

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Wed, May 14, 2014 at 4:43 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
>> > Canek Peláez Valdés <caneko@gmail.com> wrote:
>> >
>> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
>> >> [snip]
>> >> > OK, I will try dracut,
>> >>
>> >> I hope it works with dracut. This is my kernel command line and
>> >> RAID/LVM related stuff from GRUB2:
>> >>
>> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
>> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
>> >>
>> >> And this is my dracut.conf (minus comments):
>> >>
>> >> add_dracutmodules+="crypt lvm mdraid systemd"
>> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
>> >> fscks="umount mount /sbin/fsck* e2fsck"
>> >>
>> >> That's it. I didn't touched anything else to make dracut+systemd work
>> >> with LVM and RAID (and LUKS, but that doesn't matter).
>> >>
>> >> Also, dracut comes with extensive and very clear documentation; check
>> >> the man pages included.
>> >>
>> >> > but I still want to know what systemd is doing,
>> >> > what processes its spawning, etc.  -- how can I find this out -- I
>> >> > thought to use the confirm_spawn, but it times out and keeps going, what
>> >> > can I do instead?
>> >>
>> >> You can use bootchart:
>> >>
>> >> man 1 systemd-bootchart
>> >>
>> >> It will produce a chart with all the processes, and how long it takes
>> >> for every one of them. But remember, the order depends on which one
>> >> finishes before, and that can change from boot to boot.
>> >>
>> >> > Thanks people for all your responses, this is a great list.
>> >>
>> >> Regards.
>> >> --
>> >> Canek Peláez Valdés
>> >> Profesor de asignatura, Facultad de Ciencias
>> >
>> > Well, since I am unable to see, the graph would not do me any good, any
>> > way to get it in text form?  What I want to see (and I know the order
>> > may change) is which starts first and so on, to make sure targets,
>> > etc. do what I want them to do.
>>
>> Try adding this to your kernel command line:
>> systemd.log_target=console systemd.log_level=debug. It will add a lot
>> of output, including what is being executed.
>
> I also in my kernel command line said rd.lvm=1 just to make sure.

John, which version of dracut are you using? Also, what was the
command line you used to generate it?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 4:43 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
> >> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >> >
> >> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
> >> >> [snip]
> >> >> > OK, I will try dracut,
> >> >>
> >> >> I hope it works with dracut. This is my kernel command line and
> >> >> RAID/LVM related stuff from GRUB2:
> >> >>
> >> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
> >> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
> >> >>
> >> >> And this is my dracut.conf (minus comments):
> >> >>
> >> >> add_dracutmodules+="crypt lvm mdraid systemd"
> >> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
> >> >> fscks="umount mount /sbin/fsck* e2fsck"
> >> >>
> >> >> That's it. I didn't touched anything else to make dracut+systemd work
> >> >> with LVM and RAID (and LUKS, but that doesn't matter).
> >> >>
> >> >> Also, dracut comes with extensive and very clear documentation; check
> >> >> the man pages included.
> >> >>
> >> >> > but I still want to know what systemd is doing,
> >> >> > what processes its spawning, etc.  -- how can I find this out -- I
> >> >> > thought to use the confirm_spawn, but it times out and keeps going, what
> >> >> > can I do instead?
> >> >>
> >> >> You can use bootchart:
> >> >>
> >> >> man 1 systemd-bootchart
> >> >>
> >> >> It will produce a chart with all the processes, and how long it takes
> >> >> for every one of them. But remember, the order depends on which one
> >> >> finishes before, and that can change from boot to boot.
> >> >>
> >> >> > Thanks people for all your responses, this is a great list.
> >> >>
> >> >> Regards.
> >> >> --
> >> >> Canek Peláez Valdés
> >> >> Profesor de asignatura, Facultad de Ciencias
> >> >
> >> > Well, since I am unable to see, the graph would not do me any good, any
> >> > way to get it in text form?  What I want to see (and I know the order
> >> > may change) is which starts first and so on, to make sure targets,
> >> > etc. do what I want them to do.
> >>
> >> Try adding this to your kernel command line:
> >> systemd.log_target=console systemd.log_level=debug. It will add a lot
> >> of output, including what is being executed.
> >
> > I also in my kernel command line said rd.lvm=1 just to make sure.
> 
> John, which version of dracut are you using? Also, what was the
> command line you used to generate it?

I am using version 037 and the command line was very simple
dracut --force -M
and here is its output:
 Script started on Wed 14 May 2014 04:52:19 AM EDT
Executing: /usr/bin/dracut --force -M
00bootchart: Could not find command '/sbin/bootchartd'!
00dash: Could not find command '/bin/dash'!
50plymouth: Could not find command 'plymouthd'!
50plymouth: Could not find command 'plymouth'!
90btrfs: Could not find command 'btrfs'!
90dmraid: Could not find command 'dmraid'!
90mdraid: Could not find command 'mdadm'!
90multipath: Could not find command 'multipath'!
95fcoe-uefi: Could not find command 'dcbtool'!
95fcoe-uefi: Could not find command 'fipvlan'!
95fcoe-uefi: Could not find command 'lldpad'!
95iscsi: Could not find command 'iscsistart'!
95iscsi: Could not find command 'iscsi-iname'!
95nbd: Could not find command 'nbd-client'!
97biosdevname: Could not find command 'biosdevname'!
bash
caps
caps: does not work with systemd in the initramfs
modsign
dracut-install: ERROR: installing '/usr/bin/keyctl'
/usr/libexec/dracut-install -D /var/tmp/initramfs.dpEwDV /usr/bin/keyctl
i18n
network
crypt
dm
Skipping udev rule: 64-device-mapper.rules
Skipping udev rule: 60-persistent-storage-dm.rules
Skipping udev rule: 55-dm.rules
kernel-modules
Omitting driver i2o_scsi
lvm
Skipping udev rule: 64-device-mapper.rules
Skipping udev rule: 56-lvm.rules
Skipping udev rule: 60-persistent-storage-lvm.rules
cifs
nfs
resume
rootfs-block
terminfo
udev-rules
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
systemd
usrmount
base
fs-lib
shutdown
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Stripping files ***
*** Stripping files done ***
*** Store current command line parameters ***
*** Creating image file ***
*** Creating image file done ***

Script done on Wed 14 May 2014 04:52:50 AM EDT



-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
[snip]
> I am using version 037 and the command line was very simple

As I told you in [1], the 037 version has problems with LVM; please
also check the thread in [2], specially the post in [3].

Please try again with dracut-036-r4.

Regards.

[1] http://article.gmane.org/gmane.linux.gentoo.user/274340
[2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
[3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
(for some reason it doesn't appear in gmane).
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
> [snip]
> > I am using version 037 and the command line was very simple
> 
> As I told you in [1], the 037 version has problems with LVM; please
> also check the thread in [2], specially the post in [3].
> 
> Please try again with dracut-036-r4.
> 
> Regards.
> 
> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
> (for some reason it doesn't appear in gmane).
portage won't let me downgrade unless I downgrade systemd to 2.10 --
should I do that?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-14 9:42 GMT-06:00  <covici@ccs.covici.com>:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
>> [snip]
>> > I am using version 037 and the command line was very simple
>>
>> As I told you in [1], the 037 version has problems with LVM; please
>> also check the thread in [2], specially the post in [3].
>>
>> Please try again with dracut-036-r4.
>>
>> Regards.
>>
>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
>> (for some reason it doesn't appear in gmane).
> portage won't let me downgrade unless I downgrade systemd to 2.10 --
> should I do that?
>
>
I'm using dracut 037-r1 and got it to work.
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>          John Covici
>          covici@ccs.covici.com
>

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
>> [snip]
>> > I am using version 037 and the command line was very simple
>>
>> As I told you in [1], the 037 version has problems with LVM; please
>> also check the thread in [2], specially the post in [3].
>>
>> Please try again with dracut-036-r4.
>>
>> Regards.
>>
>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
>> (for some reason it doesn't appear in gmane).
> portage won't let me downgrade unless I downgrade systemd to 2.10 --
> should I do that?

You mean 210. I'm on 208; my LVM test system is basically stable.

However Jc says he's got it to work with dracut 037-r1; perhaps try
that version first?

What I do know is that with dracut 037, me and Stefan ran intro troubles.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:
> On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
>> Canek Peláez Valdés <caneko@gmail.com> wrote:
>>
>>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
>>> [snip]
>>> > I am using version 037 and the command line was very simple
>>>
>>> As I told you in [1], the 037 version has problems with LVM; please
>>> also check the thread in [2], specially the post in [3].
>>>
>>> Please try again with dracut-036-r4.
>>>
>>> Regards.
>>>
>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
>>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
>>> (for some reason it doesn't appear in gmane).
>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
>> should I do that?
>
> You mean 210. I'm on 208; my LVM test system is basically stable.
>
> However Jc says he's got it to work with dracut 037-r1; perhaps try
> that version first?
>
> What I do know is that with dracut 037, me and Stefan ran intro troubles.
>
I described it as a 'workaround' in my first post, aware of the fact
that the behavior is not normal, but dracut acctually gives help
finding this workaround, wich is telling the kernel what LVs to use at
boot.
> Regards.
> --
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
>

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Wed, May 14, 2014 at 10:55 AM, Jc García <jyo.garcia@gmail.com> wrote:
> 2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:
>> On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
>>> Canek Peláez Valdés <caneko@gmail.com> wrote:
>>>
>>>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
>>>> [snip]
>>>> > I am using version 037 and the command line was very simple
>>>>
>>>> As I told you in [1], the 037 version has problems with LVM; please
>>>> also check the thread in [2], specially the post in [3].
>>>>
>>>> Please try again with dracut-036-r4.
>>>>
>>>> Regards.
>>>>
>>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
>>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
>>>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
>>>> (for some reason it doesn't appear in gmane).
>>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
>>> should I do that?
>>
>> You mean 210. I'm on 208; my LVM test system is basically stable.
>>
>> However Jc says he's got it to work with dracut 037-r1; perhaps try
>> that version first?
>>
>> What I do know is that with dracut 037, me and Stefan ran intro troubles.
>>
> I described it as a 'workaround' in my first post, aware of the fact
> that the behavior is not normal, but dracut acctually gives help
> finding this workaround, wich is telling the kernel what LVs to use at
> boot.

Sorry, I forgot about that.

I just tried my test LVM system with dracur-037-r1 and it didn't work.
I have not tried yet your workaround, but there is obviously something
fishy going on with the latest version of dracut; I would stay with
036-r4.

I will try your workaround, although my system is a little more
complicated, since it uses RAID and LUKS besides LVM.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 10:55 AM, Jc García <jyo.garcia@gmail.com> wrote:
> > 2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:
> >> On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
> >>> Canek Peláez Valdés <caneko@gmail.com> wrote:
> >>>
> >>>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
> >>>> [snip]
> >>>> > I am using version 037 and the command line was very simple
> >>>>
> >>>> As I told you in [1], the 037 version has problems with LVM; please
> >>>> also check the thread in [2], specially the post in [3].
> >>>>
> >>>> Please try again with dracut-036-r4.
> >>>>
> >>>> Regards.
> >>>>
> >>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
> >>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
> >>>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
> >>>> (for some reason it doesn't appear in gmane).
> >>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
> >>> should I do that?
> >>
> >> You mean 210. I'm on 208; my LVM test system is basically stable.
> >>
> >> However Jc says he's got it to work with dracut 037-r1; perhaps try
> >> that version first?
> >>
> >> What I do know is that with dracut 037, me and Stefan ran intro troubles.
> >>
> > I described it as a 'workaround' in my first post, aware of the fact
> > that the behavior is not normal, but dracut acctually gives help
> > finding this workaround, wich is telling the kernel what LVs to use at
> > boot.
> 
> Sorry, I forgot about that.
> 
> I just tried my test LVM system with dracur-037-r1 and it didn't work.
> I have not tried yet your workaround, but there is obviously something
> fishy going on with the latest version of dracut; I would stay with
> 036-r4.
> 
> I will try your workaround, although my system is a little more
> complicated, since it uses RAID and LUKS besides LVM.

Here is what I got when I tried to emerge 036-r4 :

Script started on Wed 14 May 2014 11:45:56 AM EDT

These are the packages that would be merged, in order:

Calculating dependencies  ..... done!
[ebuild     UD ] sys-kernel/dracut-036-r4 [037] USE="systemd -debug (-selinux)" 250 kB
[blocks B      ] >=sys-apps/systemd-210 (">=sys-apps/systemd-210" is blocking sys-kernel/dracut-036-r4)

Total: 1 package (1 downgrade), Size of downloads: 250 kB
Conflict: 1 block (1 unsatisfied)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-apps/systemd-212-r4:0/2::gentoo, installed) pulled in by
    sys-apps/systemd:0/2= required by (gnome-base/gvfs-1.20.1:0/0::gnome, installed)
    >=sys-apps/systemd-183:0/2= required by (net-misc/networkmanager-0.9.8.10:0/0::gnome, installed)
    sys-apps/systemd:0/2=[abi_x86_64(-)] required by (media-sound/pulseaudio-5.0-r1:0/0::gentoo, installed)
    >=sys-apps/systemd-186:0= required by (sys-apps/accountsservice-0.6.37:0/0::gentoo, installed)
    >=sys-apps/systemd-206 required by (sys-process/procps-3.3.9-r1:0/0::gentoo, installed)
    >=sys-apps/systemd-183:0/2= required by (gnome-base/gnome-session-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-186:0/2= required by (sys-apps/accountsservice-0.6.37:0/0::gentoo, installed)
    >=sys-apps/systemd-208 required by (sys-fs/udisks-2.1.3:2/2::gentoo, installed)
    sys-apps/systemd required by (net-wireless/bluez-5.18:0/3::gentoo, installed)
    >=sys-apps/systemd-207 required by (sys-apps/gentoo-systemd-integration-4:0/0::gentoo, installed)
    >=sys-apps/systemd-183:0= required by (net-misc/networkmanager-0.9.8.10:0/0::gnome, installed)
    >=sys-apps/systemd-44:0= required by (x11-misc/colord-1.2.0:0/2::gentoo, installed)
    sys-apps/systemd:0= required by (sys-apps/dbus-1.8.2:0/0::gentoo, installed)
    >=sys-apps/systemd-186:0=[pam] required by (gnome-base/gdm-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-shell-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-44:0/2= required by (x11-misc/colord-1.2.0:0/2::gentoo, installed)
    sys-apps/systemd required by @selected
    sys-apps/systemd required by (gnome-base/gnome-settings-daemon-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-control-center-3.12.1:2/2::gnome, installed)
    >=sys-apps/systemd-208:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev,introspection?,static-libs(-)?] (>=sys-apps/systemd-208:0/2[abi_x86_64(-),gudev,introspection]) required by (virtual/libgudev-208:0/0::gentoo, installed)
    sys-apps/systemd:0=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] (sys-apps/systemd:0=[abi_x86_64(-)]) required by (media-sound/pulseaudio-5.0-r1:0/0::gentoo, installed)
    >=sys-apps/systemd-183:0= required by (gnome-base/gnome-session-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-208:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,static-libs(-)?] (>=sys-apps/systemd-208:0/2[abi_x86_64(-)]) required by (virtual/libudev-208:0/1::gentoo, installed)
    >=sys-apps/systemd-208:0 required by (virtual/udev-208-r2:0/0::gentoo, installed)
    sys-apps/systemd:0= required by (gnome-base/gvfs-1.20.1:0/0::gnome, installed)
    >=sys-apps/systemd-204[pam] required by (sys-auth/pambase-20140313:0/0::gentoo, installed)
    sys-apps/systemd required by (media-sound/mpd-0.18.10-r1:0/0::gentoo, installed)
    >=sys-apps/systemd-200 required by (sys-power/upower-0.99.0:0/2::gentoo, installed)
    sys-apps/systemd:0/2= required by (sys-apps/dbus-1.8.2:0/0::gentoo, installed)
    sys-apps/systemd:0= required by (sys-auth/polkit-0.112-r2:0/0::gentoo, installed)
    >=sys-apps/systemd-186:0/2=[pam] required by (gnome-base/gdm-3.12.1:0/0::gnome, installed)
    >=sys-apps/systemd-199 required by (sys-kernel/dracut-036-r4:0/0::gentoo, ebuild scheduled for merge)

  (sys-kernel/dracut-036-r4:0/0::gentoo, ebuild scheduled for merge) pulled in by
    =sys-kernel/dracut-036-r4
    sys-kernel/dracut required by @selected


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked


!!! The following installed packages are masked:
- virtual/jdk-1.8.0::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Tom Wijsman <TomWij@gentoo.org> (31 Mar 2014)
# Prevent users from switching JDK / JRE implementation.
#
# Unmask this if you want to upgrade or switch to Oracle JDK / JRE 1.8.

- virtual/jre-1.8.0::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.


Script done on Wed 14 May 2014 11:46:31 AM EDT


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-14 10:18 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:

> I will try your workaround, although my system is a little more
> complicated, since it uses RAID and LUKS besides LVM.
That surely makes things more complicated, and I wouldn't expect
something that simple to make the 'workaround', I would try to see
what kernel command line dracut recommends, it might add something
concerning RAID, the same it does with LVM.

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 14.05.2014 18:38, schrieb covici@ccs.covici.com:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
> 
>> On Wed, May 14, 2014 at 10:55 AM, Jc García <jyo.garcia@gmail.com> wrote:
>>> 2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:
>>>> On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
>>>>> Canek Peláez Valdés <caneko@gmail.com> wrote:
>>>>>
>>>>>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
>>>>>> [snip]
>>>>>>> I am using version 037 and the command line was very simple
>>>>>>
>>>>>> As I told you in [1], the 037 version has problems with LVM; please
>>>>>> also check the thread in [2], specially the post in [3].
>>>>>>
>>>>>> Please try again with dracut-036-r4.
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
>>>>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
>>>>>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
>>>>>> (for some reason it doesn't appear in gmane).
>>>>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
>>>>> should I do that?
>>>>
>>>> You mean 210. I'm on 208; my LVM test system is basically stable.
>>>>
>>>> However Jc says he's got it to work with dracut 037-r1; perhaps try
>>>> that version first?
>>>>
>>>> What I do know is that with dracut 037, me and Stefan ran intro troubles.
>>>>
>>> I described it as a 'workaround' in my first post, aware of the fact
>>> that the behavior is not normal, but dracut acctually gives help
>>> finding this workaround, wich is telling the kernel what LVs to use at
>>> boot.
>>
>> Sorry, I forgot about that.
>>
>> I just tried my test LVM system with dracur-037-r1 and it didn't work.
>> I have not tried yet your workaround, but there is obviously something
>> fishy going on with the latest version of dracut; I would stay with
>> 036-r4.
>>
>> I will try your workaround, although my system is a little more
>> complicated, since it uses RAID and LUKS besides LVM.
> 
> Here is what I got when I tried to emerge 036-r4 :
> 
> Script started on Wed 14 May 2014 11:45:56 AM EDT
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies  ..... done!
> [ebuild     UD ] sys-kernel/dracut-036-r4 [037] USE="systemd -debug (-selinux)" 250 kB
> [blocks B      ] >=sys-apps/systemd-210 (">=sys-apps/systemd-210" is blocking sys-kernel/dracut-036-r4)
> 
> Total: 1 package (1 downgrade), Size of downloads: 250 kB
> Conflict: 1 block (1 unsatisfied)
> 
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
> 
>   (sys-apps/systemd-212-r4:0/2::gentoo, installed) pulled in by
>     sys-apps/systemd:0/2= required by (gnome-base/gvfs-1.20.1:0/0::gnome, installed)
>     >=sys-apps/systemd-183:0/2= required by (net-misc/networkmanager-0.9.8.10:0/0::gnome, installed)
>     sys-apps/systemd:0/2=[abi_x86_64(-)] required by (media-sound/pulseaudio-5.0-r1:0/0::gentoo, installed)
>     >=sys-apps/systemd-186:0= required by (sys-apps/accountsservice-0.6.37:0/0::gentoo, installed)
>     >=sys-apps/systemd-206 required by (sys-process/procps-3.3.9-r1:0/0::gentoo, installed)
>     >=sys-apps/systemd-183:0/2= required by (gnome-base/gnome-session-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-186:0/2= required by (sys-apps/accountsservice-0.6.37:0/0::gentoo, installed)
>     >=sys-apps/systemd-208 required by (sys-fs/udisks-2.1.3:2/2::gentoo, installed)
>     sys-apps/systemd required by (net-wireless/bluez-5.18:0/3::gentoo, installed)
>     >=sys-apps/systemd-207 required by (sys-apps/gentoo-systemd-integration-4:0/0::gentoo, installed)
>     >=sys-apps/systemd-183:0= required by (net-misc/networkmanager-0.9.8.10:0/0::gnome, installed)
>     >=sys-apps/systemd-44:0= required by (x11-misc/colord-1.2.0:0/2::gentoo, installed)
>     sys-apps/systemd:0= required by (sys-apps/dbus-1.8.2:0/0::gentoo, installed)
>     >=sys-apps/systemd-186:0=[pam] required by (gnome-base/gdm-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-31 required by (gnome-base/gnome-shell-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-44:0/2= required by (x11-misc/colord-1.2.0:0/2::gentoo, installed)
>     sys-apps/systemd required by @selected
>     sys-apps/systemd required by (gnome-base/gnome-settings-daemon-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-31 required by (gnome-base/gnome-control-center-3.12.1:2/2::gnome, installed)
>     >=sys-apps/systemd-208:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev,introspection?,static-libs(-)?] (>=sys-apps/systemd-208:0/2[abi_x86_64(-),gudev,introspection]) required by (virtual/libgudev-208:0/0::gentoo, installed)
>     sys-apps/systemd:0=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] (sys-apps/systemd:0=[abi_x86_64(-)]) required by (media-sound/pulseaudio-5.0-r1:0/0::gentoo, installed)
>     >=sys-apps/systemd-183:0= required by (gnome-base/gnome-session-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-208:0/2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,static-libs(-)?] (>=sys-apps/systemd-208:0/2[abi_x86_64(-)]) required by (virtual/libudev-208:0/1::gentoo, installed)
>     >=sys-apps/systemd-208:0 required by (virtual/udev-208-r2:0/0::gentoo, installed)
>     sys-apps/systemd:0= required by (gnome-base/gvfs-1.20.1:0/0::gnome, installed)
>     >=sys-apps/systemd-204[pam] required by (sys-auth/pambase-20140313:0/0::gentoo, installed)
>     sys-apps/systemd required by (media-sound/mpd-0.18.10-r1:0/0::gentoo, installed)
>     >=sys-apps/systemd-200 required by (sys-power/upower-0.99.0:0/2::gentoo, installed)
>     sys-apps/systemd:0/2= required by (sys-apps/dbus-1.8.2:0/0::gentoo, installed)
>     sys-apps/systemd:0= required by (sys-auth/polkit-0.112-r2:0/0::gentoo, installed)
>     >=sys-apps/systemd-186:0/2=[pam] required by (gnome-base/gdm-3.12.1:0/0::gnome, installed)
>     >=sys-apps/systemd-199 required by (sys-kernel/dracut-036-r4:0/0::gentoo, ebuild scheduled for merge)
> 
>   (sys-kernel/dracut-036-r4:0/0::gentoo, ebuild scheduled for merge) pulled in by
>     =sys-kernel/dracut-036-r4
>     sys-kernel/dracut required by @selected


.... yes, it's a shame ... you would have to rebuild all these packages
after downgrading systemd. I had that myself back then. Hopefully it
helps you to find the issues (you won't need to rebuild all gnome-stuff
just to test your boot-process .... )

Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 10:55 AM, Jc García <jyo.garcia@gmail.com> wrote:
> > 2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:
> >> On Wed, May 14, 2014 at 10:42 AM,  <covici@ccs.covici.com> wrote:
> >>> Canek Peláez Valdés <caneko@gmail.com> wrote:
> >>>
> >>>> On Wed, May 14, 2014 at 10:05 AM,  <covici@ccs.covici.com> wrote:
> >>>> [snip]
> >>>> > I am using version 037 and the command line was very simple
> >>>>
> >>>> As I told you in [1], the 037 version has problems with LVM; please
> >>>> also check the thread in [2], specially the post in [3].
> >>>>
> >>>> Please try again with dracut-036-r4.
> >>>>
> >>>> Regards.
> >>>>
> >>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
> >>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
> >>>> [3] http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg145647.html
> >>>> (for some reason it doesn't appear in gmane).
> >>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
> >>> should I do that?
> >>
> >> You mean 210. I'm on 208; my LVM test system is basically stable.
> >>
> >> However Jc says he's got it to work with dracut 037-r1; perhaps try
> >> that version first?
> >>
> >> What I do know is that with dracut 037, me and Stefan ran intro troubles.
> >>
> > I described it as a 'workaround' in my first post, aware of the fact
> > that the behavior is not normal, but dracut acctually gives help
> > finding this workaround, wich is telling the kernel what LVs to use at
> > boot.
> 
> Sorry, I forgot about that.
> 
> I just tried my test LVM system with dracur-037-r1 and it didn't work.
> I have not tried yet your workaround, but there is obviously something
> fishy going on with the latest version of dracut; I would stay with
> 036-r4.
> 
> I will try your workaround, although my system is a little more
> complicated, since it uses RAID and LUKS besides LVM.

Well, the workaround sort of worked -- it went through the initrd -- I
had debug in the kernel command line, but it did not stop for nothing!
When it went to the real root, however it did not activate any of the
lvm volumes I had except for what I specified in the kernel command
line, causing things not to work well.  Also, I noticed that if insisted
on using the predictable network names, even though I have
/etc/udev/rules.d/70-persistent-net.rules and
/etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
me back my eth* names.  So all in all, it was a mess and took me to an
emergency shell and that was the end of that.  I did eventually activate
some volumes by lvchange -aay, but obviously that would not work well.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 14/05/14 19:40, covici@ccs.covici.com wrote:
> Well, I rebooted under dracut, but it did not do the lvmscan and so the job
> trying to find the root file system timed out after 90 seconds.  It took me
> to the emergency shell which I had specified, and I was able to do the
> lvm_scan and them magically root got mounted under sysroot, but I had no
> idea what to do next  to maybe get things going.

For what it's worth, I came across issues with my LVM/LUKS setup when I tried
dracut, and in my searches came across [1] (fedoraproject.org).  When dropped
to the dracut emergency shell, the idea is to locate and flag your root volume
in order to allow the boot process to continue.

It varies between setups, but the idea is that you make your root volume
accessible through whatever means (lvscan, cryptsetup, dm-crypt, whatever),
then symlink it to /dev/root.

Once that's done, you then `exit` the shell to allow the boot process to continue.

[1] http://is.gd/bmzmNu

Cheers.
- -wraeth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlNz+d4ACgkQXcRKerLZ91msnAD9GZ3oZ0rmQfeHx/yx6UlBn2U0
qkfzHR5uhvBnVK9Qi9IA/1VIVF3hYvYXUprWePQZcuLvewVzzW0xDVDFrLVgGoKo
=FDs+
-----END PGP SIGNATURE-----

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
[snip]
>
> Well, the workaround sort of worked -- it went through the initrd -- I
> had debug in the kernel command line, but it did not stop for nothing!
> When it went to the real root, however it did not activate any of the
> lvm volumes I had except for what I specified in the kernel command
> line, causing things not to work well.  Also, I noticed that if insisted
> on using the predictable network names, even though I have
> /etc/udev/rules.d/70-persistent-net.rules and
> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> me back my eth* names.  So all in all, it was a mess and took me to an
> emergency shell and that was the end of that.  I did eventually activate
> some volumes by lvchange -aay, but obviously that would not work well.

OK, I was a little mystified about why dracut-036 worked on my system
and 037 didn't. Before I tried any workaround, I wanted to know what
changed from the previous version to the current one.

So I generated an initramfs with dracut-036-r4 and another one with
dracut-037-r1, and I tried to see what changed from one to the other.
The answer is surprisingly easy: in /etc/cmdline.d/, the following
files where in the 036-r4 version, but not in the 037-r4:

90crypt.conf
90lvm.conf
90mdraid.conf
base.conf

Te contents of those files are (90crypt.conf is empty):

90lvm.conf
   rd.lvm.lv=vg/vol1
   rd.lvm.lv=vg/vol4
   rd.lvm.lv=vg/vol3

90mdraid.conf
   rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12

base.conf
   ro

So I just changed my /etc/default/grub file:

GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"

I regenerated my GRUB2 config, and now again my LVM test system works
perfectly with the latest dracut version.

The thing is, I *ALWAYS* use the -H (host only) option, so it was my
understanding that the command line should be automatically generated,
and it was on 036, but now it doesn't in 037. I think that's a bug.

John, with respect to your case: did you used "dracut --print-cmdline"
to get the command line? Also, have you tried to use -H to generate
your initramfs?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> [snip]
>>
>> Well, the workaround sort of worked -- it went through the initrd -- I
>> had debug in the kernel command line, but it did not stop for nothing!
>> When it went to the real root, however it did not activate any of the
>> lvm volumes I had except for what I specified in the kernel command
>> line, causing things not to work well.  Also, I noticed that if insisted
>> on using the predictable network names, even though I have
>> /etc/udev/rules.d/70-persistent-net.rules and
>> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
>> me back my eth* names.  So all in all, it was a mess and took me to an
>> emergency shell and that was the end of that.  I did eventually activate
>> some volumes by lvchange -aay, but obviously that would not work well.
>
> OK, I was a little mystified about why dracut-036 worked on my system
> and 037 didn't. Before I tried any workaround, I wanted to know what
> changed from the previous version to the current one.
>
> So I generated an initramfs with dracut-036-r4 and another one with
> dracut-037-r1, and I tried to see what changed from one to the other.
> The answer is surprisingly easy: in /etc/cmdline.d/, the following
> files where in the 036-r4 version, but not in the 037-r4:
>
> 90crypt.conf
> 90lvm.conf
> 90mdraid.conf
> base.conf
>
> Te contents of those files are (90crypt.conf is empty):
>
> 90lvm.conf
>    rd.lvm.lv=vg/vol1
>    rd.lvm.lv=vg/vol4
>    rd.lvm.lv=vg/vol3
>
> 90mdraid.conf
>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>
> base.conf
>    ro
>
> So I just changed my /etc/default/grub file:
>
> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>
> I regenerated my GRUB2 config, and now again my LVM test system works
> perfectly with the latest dracut version.

I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
BTW Jc, you used host_cmdline, I think the former is the correct one.

So, to resume: there is no bug, is just that before hostonly_cmdline
was yes by default, and now is no by default. This change was
documented, but I failed to notice it (and I think the ebuild in
Gentoo should print an einfo message).

Anyway, I think that explains all my problems; John, I don't know if
it will solve yours. Again: did you used "dracut --print-cmdline" to
get the command line? Also, have you tried to use -H to generate your
initramfs? And finally, have you tried with --hostonly-cmdline?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> [snip]
> >
> > Well, the workaround sort of worked -- it went through the initrd -- I
> > had debug in the kernel command line, but it did not stop for nothing!
> > When it went to the real root, however it did not activate any of the
> > lvm volumes I had except for what I specified in the kernel command
> > line, causing things not to work well.  Also, I noticed that if insisted
> > on using the predictable network names, even though I have
> > /etc/udev/rules.d/70-persistent-net.rules and
> > /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> > me back my eth* names.  So all in all, it was a mess and took me to an
> > emergency shell and that was the end of that.  I did eventually activate
> > some volumes by lvchange -aay, but obviously that would not work well.
> 
> OK, I was a little mystified about why dracut-036 worked on my system
> and 037 didn't. Before I tried any workaround, I wanted to know what
> changed from the previous version to the current one.
> 
> So I generated an initramfs with dracut-036-r4 and another one with
> dracut-037-r1, and I tried to see what changed from one to the other.
> The answer is surprisingly easy: in /etc/cmdline.d/, the following
> files where in the 036-r4 version, but not in the 037-r4:
> 
> 90crypt.conf
> 90lvm.conf
> 90mdraid.conf
> base.conf
> 
> Te contents of those files are (90crypt.conf is empty):
> 
> 90lvm.conf
>    rd.lvm.lv=vg/vol1
>    rd.lvm.lv=vg/vol4
>    rd.lvm.lv=vg/vol3
> 
> 90mdraid.conf
>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
> 
> base.conf
>    ro
> 
> So I just changed my /etc/default/grub file:
> 
> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
> 
> I regenerated my GRUB2 config, and now again my LVM test system works
> perfectly with the latest dracut version.
> 
> The thing is, I *ALWAYS* use the -H (host only) option, so it was my
> understanding that the command line should be automatically generated,
> and it was on 036, but now it doesn't in 037. I think that's a bug.
> 
> John, with respect to your case: did you used "dracut --print-cmdline"
> to get the command line? Also, have you tried to use -H to generate
> your initramfs?

I did not try the -H, I may test with that later.


I did look at the --print-cmdline and copied the volumes they mentioned,
but I have other lvm volumes in my fstab and none of them were activated,
only the ones I specified in the command line!  This is where I have run
into problems.  I have quite a few lvms, I want them all activated!

Also, since I wrote the last message, I have been looking at the
journalctl output and discovered a couple of things which I would like
some help on, but getting the lvms to work is more important.

First, whatever happened to DefaultControllers -- I want to disable
those cpu hierarchies, but that option seems to have disappeared without
a trace, although you can google and see it in some documentation.

The keyword also was not accepted in an install section I have, what is
the matter with that?  I want to use my sysklogd for my syslog, how can
I use that with systemd?

Thanks so much for all your help on these things.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> > On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> > [snip]
> >>
> >> Well, the workaround sort of worked -- it went through the initrd -- I
> >> had debug in the kernel command line, but it did not stop for nothing!
> >> When it went to the real root, however it did not activate any of the
> >> lvm volumes I had except for what I specified in the kernel command
> >> line, causing things not to work well.  Also, I noticed that if insisted
> >> on using the predictable network names, even though I have
> >> /etc/udev/rules.d/70-persistent-net.rules and
> >> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> >> me back my eth* names.  So all in all, it was a mess and took me to an
> >> emergency shell and that was the end of that.  I did eventually activate
> >> some volumes by lvchange -aay, but obviously that would not work well.
> >
> > OK, I was a little mystified about why dracut-036 worked on my system
> > and 037 didn't. Before I tried any workaround, I wanted to know what
> > changed from the previous version to the current one.
> >
> > So I generated an initramfs with dracut-036-r4 and another one with
> > dracut-037-r1, and I tried to see what changed from one to the other.
> > The answer is surprisingly easy: in /etc/cmdline.d/, the following
> > files where in the 036-r4 version, but not in the 037-r4:
> >
> > 90crypt.conf
> > 90lvm.conf
> > 90mdraid.conf
> > base.conf
> >
> > Te contents of those files are (90crypt.conf is empty):
> >
> > 90lvm.conf
> >    rd.lvm.lv=vg/vol1
> >    rd.lvm.lv=vg/vol4
> >    rd.lvm.lv=vg/vol3
> >
> > 90mdraid.conf
> >    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
> >
> > base.conf
> >    ro
> >
> > So I just changed my /etc/default/grub file:
> >
> > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> > rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> > rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
> >
> > I regenerated my GRUB2 config, and now again my LVM test system works
> > perfectly with the latest dracut version.
> 
> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
> BTW Jc, you used host_cmdline, I think the former is the correct one.
> 
> So, to resume: there is no bug, is just that before hostonly_cmdline
> was yes by default, and now is no by default. This change was
> documented, but I failed to notice it (and I think the ebuild in
> Gentoo should print an einfo message).
> 
> Anyway, I think that explains all my problems; John, I don't know if
> it will solve yours. Again: did you used "dracut --print-cmdline" to
> get the command line? Also, have you tried to use -H to generate your
> initramfs? And finally, have you tried with --hostonly-cmdline?

I did not use --hostonly-cmdline because I have other parameters and
wanted to keep everyting together -- should that make a difference?  If
I did use that then would I have append="" in lilo.conf  or the grub
equivalemt?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 11:39, schrieb covici@ccs.covici.com:

> I did not try the -H, I may test with that later.
> 
> 
> I did look at the --print-cmdline and copied the volumes they mentioned,
> but I have other lvm volumes in my fstab and none of them were activated,
> only the ones I specified in the command line!  This is where I have run
> into problems.  I have quite a few lvms, I want them all activated!

Sure. I remember having an extra lvm.service for systemd to have all the
LVs activated ... with that unit-file it worked more reliably for me
(maybe not needed since some time).

For sure that service file is only run *after* the initrd has
found/activated/mounted your LVM-based root ... might be a workaround to
specify the root-LV in the kernel command line (plus maybe "rd.auto
rd.lvm=1" ?) and then let the service file activate the rest of the LVs.

Just to get you started at last ;-)


> Also, since I wrote the last message, I have been looking at the
> journalctl output and discovered a couple of things which I would like
> some help on, but getting the lvms to work is more important.
> 
> First, whatever happened to DefaultControllers -- I want to disable
> those cpu hierarchies, but that option seems to have disappeared without
> a trace, although you can google and see it in some documentation.
> 
> The keyword also was not accepted in an install section I have, what is
> the matter with that?

What keyword? I don't understand right now.

>  I want to use my sysklogd for my syslog, how can
> I use that with systemd?

systemd's journal will be written to a socket if you configure it in
/etc/systemd/journald.conf

I would check "man journald.conf" and the option:

ForwardToSyslog=

and then let your chosen log-daemon listen there.

IMO you should take a look at journalctl then anyway ... new concepts,
but powerful features.

Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 15.05.2014 11:39, schrieb covici@ccs.covici.com:
> 
> > I did not try the -H, I may test with that later.
> > 
> > 
> > I did look at the --print-cmdline and copied the volumes they mentioned,
> > but I have other lvm volumes in my fstab and none of them were activated,
> > only the ones I specified in the command line!  This is where I have run
> > into problems.  I have quite a few lvms, I want them all activated!
> 
> Sure. I remember having an extra lvm.service for systemd to have all the
> LVs activated ... with that unit-file it worked more reliably for me
> (maybe not needed since some time).
> 
> For sure that service file is only run *after* the initrd has
> found/activated/mounted your LVM-based root ... might be a workaround to
> specify the root-LV in the kernel command line (plus maybe "rd.auto
> rd.lvm=1" ?) and then let the service file activate the rest of the LVs.
> 
> Just to get you started at last ;-)
> 
> 
> > Also, since I wrote the last message, I have been looking at the
> > journalctl output and discovered a couple of things which I would like
> > some help on, but getting the lvms to work is more important.
> > 
> > First, whatever happened to DefaultControllers -- I want to disable
> > those cpu hierarchies, but that option seems to have disappeared without
> > a trace, although you can google and see it in some documentation.
> > 
> > The keyword also was not accepted in an install section I have, what is
> > the matter with that?
> 
> What keyword? I don't understand right now.
> 
> >  I want to use my sysklogd for my syslog, how can
> > I use that with systemd?
> 
> systemd's journal will be written to a socket if you configure it in
> /etc/systemd/journald.conf
> 
> I would check "man journald.conf" and the option:
> 
> ForwardToSyslog=
> 
> and then let your chosen log-daemon listen there.
> 
> IMO you should take a look at journalctl then anyway ... new concepts,
> but powerful features.

Sure, but what I was looking for was a way to start syslogd and klogd
using systemd -- I do have a socket option so they can listen on the
socket so that should be OK.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> > On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> > [snip]
> >>
> >> Well, the workaround sort of worked -- it went through the initrd -- I
> >> had debug in the kernel command line, but it did not stop for nothing!
> >> When it went to the real root, however it did not activate any of the
> >> lvm volumes I had except for what I specified in the kernel command
> >> line, causing things not to work well.  Also, I noticed that if insisted
> >> on using the predictable network names, even though I have
> >> /etc/udev/rules.d/70-persistent-net.rules and
> >> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> >> me back my eth* names.  So all in all, it was a mess and took me to an
> >> emergency shell and that was the end of that.  I did eventually activate
> >> some volumes by lvchange -aay, but obviously that would not work well.
> >
> > OK, I was a little mystified about why dracut-036 worked on my system
> > and 037 didn't. Before I tried any workaround, I wanted to know what
> > changed from the previous version to the current one.
> >
> > So I generated an initramfs with dracut-036-r4 and another one with
> > dracut-037-r1, and I tried to see what changed from one to the other.
> > The answer is surprisingly easy: in /etc/cmdline.d/, the following
> > files where in the 036-r4 version, but not in the 037-r4:
> >
> > 90crypt.conf
> > 90lvm.conf
> > 90mdraid.conf
> > base.conf
> >
> > Te contents of those files are (90crypt.conf is empty):
> >
> > 90lvm.conf
> >    rd.lvm.lv=vg/vol1
> >    rd.lvm.lv=vg/vol4
> >    rd.lvm.lv=vg/vol3
> >
> > 90mdraid.conf
> >    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
> >
> > base.conf
> >    ro
> >
> > So I just changed my /etc/default/grub file:
> >
> > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> > rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> > rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
> >
> > I regenerated my GRUB2 config, and now again my LVM test system works
> > perfectly with the latest dracut version.
> 
> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
> BTW Jc, you used host_cmdline, I think the former is the correct one.
> 
> So, to resume: there is no bug, is just that before hostonly_cmdline
> was yes by default, and now is no by default. This change was
> documented, but I failed to notice it (and I think the ebuild in
> Gentoo should print an einfo message).
> 
> Anyway, I think that explains all my problems; John, I don't know if
> it will solve yours. Again: did you used "dracut --print-cmdline" to
> get the command line? Also, have you tried to use -H to generate your
> initramfs? And finally, have you tried with --hostonly-cmdline?

OK, I was looking through the journal output and I think the key to the
lvm's not activating is the following:
4 12:54:57 ccs systemd[1]: Got notification message for unit
systemd-journald.service
4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
message from PID 1750 (WATCHDOG=1...)
4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
status=5/NOTINSSTALLED)
4 12:54:57 ccs systemd[1]: Job
dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.

So what is not installed?

Also, for the first two lines, I get hundreds of thatpair of lines, how
can I prevent such.
So, between the lvm problem and the udev renaming my eth0 devices these
are the key as to why things are going wrong -- with openrc udev is not
renaming eth0 at all.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 12:19, schrieb covici@ccs.covici.com:

> Sure, but what I was looking for was a way to start syslogd and klogd
> using systemd -- I do have a socket option so they can listen on the
> socket so that should be OK.

So you look for service files?

A quick google finds examples for these 2 daemons here:

http://www.linuxfromscratch.org/hints/downloads/files/systemd.txt

If they work it would be great to file a bug for adding systemd unit
files to app-admin/sysklogd at bugs.gentoo.org ( I didn't check if the
ebuild brings unit-files but at least I see it doesn't have a systemd
USE flag).

Stefan

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 13:50, schrieb covici@ccs.covici.com:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
> 
>> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>>> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
>>> [snip]
>>>>
>>>> Well, the workaround sort of worked -- it went through the initrd -- I
>>>> had debug in the kernel command line, but it did not stop for nothing!
>>>> When it went to the real root, however it did not activate any of the
>>>> lvm volumes I had except for what I specified in the kernel command
>>>> line, causing things not to work well.  Also, I noticed that if insisted
>>>> on using the predictable network names, even though I have
>>>> /etc/udev/rules.d/70-persistent-net.rules and
>>>> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
>>>> me back my eth* names.  So all in all, it was a mess and took me to an
>>>> emergency shell and that was the end of that.  I did eventually activate
>>>> some volumes by lvchange -aay, but obviously that would not work well.
>>>
>>> OK, I was a little mystified about why dracut-036 worked on my system
>>> and 037 didn't. Before I tried any workaround, I wanted to know what
>>> changed from the previous version to the current one.
>>>
>>> So I generated an initramfs with dracut-036-r4 and another one with
>>> dracut-037-r1, and I tried to see what changed from one to the other.
>>> The answer is surprisingly easy: in /etc/cmdline.d/, the following
>>> files where in the 036-r4 version, but not in the 037-r4:
>>>
>>> 90crypt.conf
>>> 90lvm.conf
>>> 90mdraid.conf
>>> base.conf
>>>
>>> Te contents of those files are (90crypt.conf is empty):
>>>
>>> 90lvm.conf
>>>    rd.lvm.lv=vg/vol1
>>>    rd.lvm.lv=vg/vol4
>>>    rd.lvm.lv=vg/vol3
>>>
>>> 90mdraid.conf
>>>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>>>
>>> base.conf
>>>    ro
>>>
>>> So I just changed my /etc/default/grub file:
>>>
>>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
>>> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
>>> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>>>
>>> I regenerated my GRUB2 config, and now again my LVM test system works
>>> perfectly with the latest dracut version.
>>
>> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
>> BTW Jc, you used host_cmdline, I think the former is the correct one.
>>
>> So, to resume: there is no bug, is just that before hostonly_cmdline
>> was yes by default, and now is no by default. This change was
>> documented, but I failed to notice it (and I think the ebuild in
>> Gentoo should print an einfo message).
>>
>> Anyway, I think that explains all my problems; John, I don't know if
>> it will solve yours. Again: did you used "dracut --print-cmdline" to
>> get the command line? Also, have you tried to use -H to generate your
>> initramfs? And finally, have you tried with --hostonly-cmdline?
> 
> OK, I was looking through the journal output and I think the key to the
> lvm's not activating is the following:
> 4 12:54:57 ccs systemd[1]: Got notification message for unit
> systemd-journald.service
> 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
> message from PID 1750 (WATCHDOG=1...)
> 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
> 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
> 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
> status=5/NOTINSSTALLED)
> 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
> status=5/NOTINSSTALLED)
> 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
> status=5/NOTINSSTALLED)
> 4 12:54:57 ccs systemd[1]: Job
> dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
> 
> So what is not installed?

My search tells me that this might be a misinterpreted return code.
I might repeat myself but the thread gets quite large now:

Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
lvm.conf)?

I think you don't have to, I just ask to check.

What release of lvm2, btw?

> Also, for the first two lines, I get hundreds of thatpair of lines, how
> can I prevent such.

The PID1 stuff ?

> So, between the lvm problem and the udev renaming my eth0 devices these
> are the key as to why things are going wrong -- with openrc udev is not
> renaming eth0 at all.

We'll take care of eth0 as well as soon your box boots correctly ;-)


Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 15.05.2014 12:19, schrieb covici@ccs.covici.com:
> 
> > Sure, but what I was looking for was a way to start syslogd and klogd
> > using systemd -- I do have a socket option so they can listen on the
> > socket so that should be OK.
> 
> So you look for service files?
> 
> A quick google finds examples for these 2 daemons here:
> 
> http://www.linuxfromscratch.org/hints/downloads/files/systemd.txt
> 
> If they work it would be great to file a bug for adding systemd unit
> files to app-admin/sysklogd at bugs.gentoo.org ( I didn't check if the
> ebuild brings unit-files but at least I see it doesn't have a systemd
> USE flag).


OK, I will check, I did not see that in my search last time.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 15.05.2014 13:50, schrieb covici@ccs.covici.com:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> > 
> >> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> >>> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> >>> [snip]
> >>>>
> >>>> Well, the workaround sort of worked -- it went through the initrd -- I
> >>>> had debug in the kernel command line, but it did not stop for nothing!
> >>>> When it went to the real root, however it did not activate any of the
> >>>> lvm volumes I had except for what I specified in the kernel command
> >>>> line, causing things not to work well.  Also, I noticed that if insisted
> >>>> on using the predictable network names, even though I have
> >>>> /etc/udev/rules.d/70-persistent-net.rules and
> >>>> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> >>>> me back my eth* names.  So all in all, it was a mess and took me to an
> >>>> emergency shell and that was the end of that.  I did eventually activate
> >>>> some volumes by lvchange -aay, but obviously that would not work well.
> >>>
> >>> OK, I was a little mystified about why dracut-036 worked on my system
> >>> and 037 didn't. Before I tried any workaround, I wanted to know what
> >>> changed from the previous version to the current one.
> >>>
> >>> So I generated an initramfs with dracut-036-r4 and another one with
> >>> dracut-037-r1, and I tried to see what changed from one to the other.
> >>> The answer is surprisingly easy: in /etc/cmdline.d/, the following
> >>> files where in the 036-r4 version, but not in the 037-r4:
> >>>
> >>> 90crypt.conf
> >>> 90lvm.conf
> >>> 90mdraid.conf
> >>> base.conf
> >>>
> >>> Te contents of those files are (90crypt.conf is empty):
> >>>
> >>> 90lvm.conf
> >>>    rd.lvm.lv=vg/vol1
> >>>    rd.lvm.lv=vg/vol4
> >>>    rd.lvm.lv=vg/vol3
> >>>
> >>> 90mdraid.conf
> >>>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
> >>>
> >>> base.conf
> >>>    ro
> >>>
> >>> So I just changed my /etc/default/grub file:
> >>>
> >>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> >>> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> >>> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
> >>>
> >>> I regenerated my GRUB2 config, and now again my LVM test system works
> >>> perfectly with the latest dracut version.
> >>
> >> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
> >> BTW Jc, you used host_cmdline, I think the former is the correct one.
> >>
> >> So, to resume: there is no bug, is just that before hostonly_cmdline
> >> was yes by default, and now is no by default. This change was
> >> documented, but I failed to notice it (and I think the ebuild in
> >> Gentoo should print an einfo message).
> >>
> >> Anyway, I think that explains all my problems; John, I don't know if
> >> it will solve yours. Again: did you used "dracut --print-cmdline" to
> >> get the command line? Also, have you tried to use -H to generate your
> >> initramfs? And finally, have you tried with --hostonly-cmdline?
> > 
> > OK, I was looking through the journal output and I think the key to the
> > lvm's not activating is the following:
> > 4 12:54:57 ccs systemd[1]: Got notification message for unit
> > systemd-journald.service
> > 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
> > message from PID 1750 (WATCHDOG=1...)
> > 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
> > 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
> > 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
> > status=5/NOTINSSTALLED)
> > 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
> > status=5/NOTINSSTALLED)
> > 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
> > status=5/NOTINSSTALLED)
> > 4 12:54:57 ccs systemd[1]: Job
> > dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
> > 
> > So what is not installed?
> 
> My search tells me that this might be a misinterpreted return code.
> I might repeat myself but the thread gets quite large now:
> 
> Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
> lvm.conf)?
Yep, did not see that starting.

> 
> I think you don't have to, I just ask to check.
> 
> What release of lvm2, btw?
105-r2


> 
> > Also, for the first two lines, I get hundreds of thatpair of lines, how
> > can I prevent such.
> 
> The PID1 stuff ?

Nope, the notifications about journald and watchdog=1

> 
> > So, between the lvm problem and the udev renaming my eth0 devices these
> > are the key as to why things are going wrong -- with openrc udev is not
> > renaming eth0 at all.
> 
> We'll take care of eth0 as well as soon your box boots correctly ;-)
> 
> 
> Stefan

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 14:38, schrieb covici@ccs.covici.com:
> Stefan G. Weichinger <lists@xunil.at> wrote:
> 
>> Am 15.05.2014 13:50, schrieb covici@ccs.covici.com:
>>> Canek Peláez Valdés <caneko@gmail.com> wrote:
>>>
>>>> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>>>>> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
>>>>> [snip]
>>>>>>
>>>>>> Well, the workaround sort of worked -- it went through the initrd -- I
>>>>>> had debug in the kernel command line, but it did not stop for nothing!
>>>>>> When it went to the real root, however it did not activate any of the
>>>>>> lvm volumes I had except for what I specified in the kernel command
>>>>>> line, causing things not to work well.  Also, I noticed that if insisted
>>>>>> on using the predictable network names, even though I have
>>>>>> /etc/udev/rules.d/70-persistent-net.rules and
>>>>>> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
>>>>>> me back my eth* names.  So all in all, it was a mess and took me to an
>>>>>> emergency shell and that was the end of that.  I did eventually activate
>>>>>> some volumes by lvchange -aay, but obviously that would not work well.
>>>>>
>>>>> OK, I was a little mystified about why dracut-036 worked on my system
>>>>> and 037 didn't. Before I tried any workaround, I wanted to know what
>>>>> changed from the previous version to the current one.
>>>>>
>>>>> So I generated an initramfs with dracut-036-r4 and another one with
>>>>> dracut-037-r1, and I tried to see what changed from one to the other.
>>>>> The answer is surprisingly easy: in /etc/cmdline.d/, the following
>>>>> files where in the 036-r4 version, but not in the 037-r4:
>>>>>
>>>>> 90crypt.conf
>>>>> 90lvm.conf
>>>>> 90mdraid.conf
>>>>> base.conf
>>>>>
>>>>> Te contents of those files are (90crypt.conf is empty):
>>>>>
>>>>> 90lvm.conf
>>>>>    rd.lvm.lv=vg/vol1
>>>>>    rd.lvm.lv=vg/vol4
>>>>>    rd.lvm.lv=vg/vol3
>>>>>
>>>>> 90mdraid.conf
>>>>>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>>>>>
>>>>> base.conf
>>>>>    ro
>>>>>
>>>>> So I just changed my /etc/default/grub file:
>>>>>
>>>>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
>>>>> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
>>>>> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>>>>>
>>>>> I regenerated my GRUB2 config, and now again my LVM test system works
>>>>> perfectly with the latest dracut version.
>>>>
>>>> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
>>>> BTW Jc, you used host_cmdline, I think the former is the correct one.
>>>>
>>>> So, to resume: there is no bug, is just that before hostonly_cmdline
>>>> was yes by default, and now is no by default. This change was
>>>> documented, but I failed to notice it (and I think the ebuild in
>>>> Gentoo should print an einfo message).
>>>>
>>>> Anyway, I think that explains all my problems; John, I don't know if
>>>> it will solve yours. Again: did you used "dracut --print-cmdline" to
>>>> get the command line? Also, have you tried to use -H to generate your
>>>> initramfs? And finally, have you tried with --hostonly-cmdline?
>>>
>>> OK, I was looking through the journal output and I think the key to the
>>> lvm's not activating is the following:
>>> 4 12:54:57 ccs systemd[1]: Got notification message for unit
>>> systemd-journald.service
>>> 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
>>> message from PID 1750 (WATCHDOG=1...)
>>> 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
>>> 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
>>> 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
>>> status=5/NOTINSSTALLED)
>>> 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
>>> status=5/NOTINSSTALLED)
>>> 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
>>> status=5/NOTINSSTALLED)
>>> 4 12:54:57 ccs systemd[1]: Job
>>> dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
>>>
>>> So what is not installed?
>>
>> My search tells me that this might be a misinterpreted return code.
>> I might repeat myself but the thread gets quite large now:
>>
>> Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
>> lvm.conf)?
> Yep, did not see that starting.
> 
>>
>> I think you don't have to, I just ask to check.
>>
>> What release of lvm2, btw?
> 105-r2

Would you test downgrading to 2.02.104 for checking if that changes
something? Or 2.02.106 ...

I find various bugs on b.g.o. around lvm2 ....

Stefan

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-15 0:47 GMT-06:00 Canek Peláez Valdés <caneko@gmail.com>:

> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
> BTW Jc, you used host_cmdline, I think the former is the correct one.
>

I don't know right now how host_cmdline got in my config(that was a
crazy day between dracut, systemd, and lvm documentations), who knows
where I saw it or if I mistyped it, anyway thanks for the correction.

> So, to resume: there is no bug, is just that before hostonly_cmdline
> was yes by default, and now is no by default. This change was
> documented, but I failed to notice it (and I think the ebuild in
> Gentoo should print an einfo message).
>
I agree, that notification in the ebulid would have saved trouble, and
I think it should be included since for sure many will run into these
problems in future.
So, would this qualify for a gentoo bug, and make the developer
include that notification?

Again, thanks for clarifying more the working of dracut.

> Anyway, I think that explains all my problems; John, I don't know if
> it will solve yours. Again: did you used "dracut --print-cmdline" to
> get the command line? Also, have you tried to use -H to generate your
> initramfs? And finally, have you tried with --hostonly-cmdline?
>
> Regards.
> --
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
>

Re: [gentoo-user] problems getting systemd to work

[Jc García]

2014-05-15 6:38 GMT-06:00  <covici@ccs.covici.com>:

>> Did you enable lvm2-lvmetad.service or socket (and set use_lvmetad=1 in
>> lvm.conf)?
> Yep, did not see that starting.
>
I have seen an odd behaviour regarding this sometimes, particulary
when I upgrade kernel, for some reason in my first reboot, my other
LVs (I have another 2 VGs) aren't activated, but on the second
reboot(Ctrl+Alt+Supr when it has got stuck), it works fine. this has
happened to me in the last 4 kernel upgrades.

Re: [gentoo-user] problems getting systemd to work

[Tom H]

On Thu, May 15, 2014 at 2:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>
> OK, I was a little mystified about why dracut-036 worked on my system
> and 037 didn't. Before I tried any workaround, I wanted to know what
> changed from the previous version to the current one.
>
> So I generated an initramfs with dracut-036-r4 and another one with
> dracut-037-r1, and I tried to see what changed from one to the other.
> The answer is surprisingly easy: in /etc/cmdline.d/, the following
> files where in the 036-r4 version, but not in the 037-r4:
>
> 90crypt.conf
> 90lvm.conf
> 90mdraid.conf
> base.conf
>
> Te contents of those files are (90crypt.conf is empty):
>
> 90lvm.conf
>    rd.lvm.lv=vg/vol1
>    rd.lvm.lv=vg/vol4
>    rd.lvm.lv=vg/vol3
>
> 90mdraid.conf
>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>
> base.conf
>    ro
>
> So I just changed my /etc/default/grub file:
>
> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>
> I regenerated my GRUB2 config, and now again my LVM test system works
> perfectly with the latest dracut version.
>
> The thing is, I *ALWAYS* use the -H (host only) option, so it was my
> understanding that the command line should be automatically generated,
> and it was on 036, but now it doesn't in 037. I think that's a bug.
>
> John, with respect to your case: did you used "dracut --print-cmdline"
> to get the command line? Also, have you tried to use -H to generate
> your initramfs?

There are two new options, "--hostonly-cmdline" (store kernel command
line arguments needed in the initramfs) and "--no-hostonly-cmdline"
(Do not store kernel command line arguments needed in the initramfs).

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Thu, May 15, 2014 at 4:48 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>> > On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
>> > [snip]
>> >>
>> >> Well, the workaround sort of worked -- it went through the initrd -- I
>> >> had debug in the kernel command line, but it did not stop for nothing!
>> >> When it went to the real root, however it did not activate any of the
>> >> lvm volumes I had except for what I specified in the kernel command
>> >> line, causing things not to work well.  Also, I noticed that if insisted
>> >> on using the predictable network names, even though I have
>> >> /etc/udev/rules.d/70-persistent-net.rules and
>> >> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
>> >> me back my eth* names.  So all in all, it was a mess and took me to an
>> >> emergency shell and that was the end of that.  I did eventually activate
>> >> some volumes by lvchange -aay, but obviously that would not work well.
>> >
>> > OK, I was a little mystified about why dracut-036 worked on my system
>> > and 037 didn't. Before I tried any workaround, I wanted to know what
>> > changed from the previous version to the current one.
>> >
>> > So I generated an initramfs with dracut-036-r4 and another one with
>> > dracut-037-r1, and I tried to see what changed from one to the other.
>> > The answer is surprisingly easy: in /etc/cmdline.d/, the following
>> > files where in the 036-r4 version, but not in the 037-r4:
>> >
>> > 90crypt.conf
>> > 90lvm.conf
>> > 90mdraid.conf
>> > base.conf
>> >
>> > Te contents of those files are (90crypt.conf is empty):
>> >
>> > 90lvm.conf
>> >    rd.lvm.lv=vg/vol1
>> >    rd.lvm.lv=vg/vol4
>> >    rd.lvm.lv=vg/vol3
>> >
>> > 90mdraid.conf
>> >    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>> >
>> > base.conf
>> >    ro
>> >
>> > So I just changed my /etc/default/grub file:
>> >
>> > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
>> > rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
>> > rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>> >
>> > I regenerated my GRUB2 config, and now again my LVM test system works
>> > perfectly with the latest dracut version.
>>
>> I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
>> BTW Jc, you used host_cmdline, I think the former is the correct one.
>>
>> So, to resume: there is no bug, is just that before hostonly_cmdline
>> was yes by default, and now is no by default. This change was
>> documented, but I failed to notice it (and I think the ebuild in
>> Gentoo should print an einfo message).
>>
>> Anyway, I think that explains all my problems; John, I don't know if
>> it will solve yours. Again: did you used "dracut --print-cmdline" to
>> get the command line? Also, have you tried to use -H to generate your
>> initramfs? And finally, have you tried with --hostonly-cmdline?
>
> I did not use --hostonly-cmdline because I have other parameters and
> wanted to keep everyting together -- should that make a difference?

I think so.

>  If
> I did use that then would I have append="" in lilo.conf  or the grub
> equivalemt?

Nothing; dracut would take care of everything (in theory).

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Thu, May 15, 2014 at 4:39 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
>> [snip]
>> >
>> > Well, the workaround sort of worked -- it went through the initrd -- I
>> > had debug in the kernel command line, but it did not stop for nothing!
>> > When it went to the real root, however it did not activate any of the
>> > lvm volumes I had except for what I specified in the kernel command
>> > line, causing things not to work well.  Also, I noticed that if insisted
>> > on using the predictable network names, even though I have
>> > /etc/udev/rules.d/70-persistent-net.rules and
>> > /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
>> > me back my eth* names.  So all in all, it was a mess and took me to an
>> > emergency shell and that was the end of that.  I did eventually activate
>> > some volumes by lvchange -aay, but obviously that would not work well.
>>
>> OK, I was a little mystified about why dracut-036 worked on my system
>> and 037 didn't. Before I tried any workaround, I wanted to know what
>> changed from the previous version to the current one.
>>
>> So I generated an initramfs with dracut-036-r4 and another one with
>> dracut-037-r1, and I tried to see what changed from one to the other.
>> The answer is surprisingly easy: in /etc/cmdline.d/, the following
>> files where in the 036-r4 version, but not in the 037-r4:
>>
>> 90crypt.conf
>> 90lvm.conf
>> 90mdraid.conf
>> base.conf
>>
>> Te contents of those files are (90crypt.conf is empty):
>>
>> 90lvm.conf
>>    rd.lvm.lv=vg/vol1
>>    rd.lvm.lv=vg/vol4
>>    rd.lvm.lv=vg/vol3
>>
>> 90mdraid.conf
>>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
>>
>> base.conf
>>    ro
>>
>> So I just changed my /etc/default/grub file:
>>
>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
>> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
>> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
>>
>> I regenerated my GRUB2 config, and now again my LVM test system works
>> perfectly with the latest dracut version.
>>
>> The thing is, I *ALWAYS* use the -H (host only) option, so it was my
>> understanding that the command line should be automatically generated,
>> and it was on 036, but now it doesn't in 037. I think that's a bug.
>>
>> John, with respect to your case: did you used "dracut --print-cmdline"
>> to get the command line? Also, have you tried to use -H to generate
>> your initramfs?
>
> I did not try the -H, I may test with that later.
>
>
> I did look at the --print-cmdline and copied the volumes they mentioned,
> but I have other lvm volumes in my fstab and none of them were activated,
> only the ones I specified in the command line!  This is where I have run
> into problems.  I have quite a few lvms, I want them all activated!

I just have /, /boot, /usr and /home (encrypted) as lvms, but all are activated.

> Also, since I wrote the last message, I have been looking at the
> journalctl output and discovered a couple of things which I would like
> some help on, but getting the lvms to work is more important.
>
> First, whatever happened to DefaultControllers -- I want to disable
> those cpu hierarchies, but that option seems to have disappeared without
> a trace, although you can google and see it in some documentation.

That went away with the new cgroup handling that is being coordinated
between systemd and the kernel:

http://cgit.freedesktop.org/systemd/systemd/commit/?id=7ac807320a7416463d7ff3ef6ede574863a601c5

> The keyword also was not accepted in an install section I have, what is
> the matter with that?  I want to use my sysklogd for my syslog, how can
> I use that with systemd?

I think you can do that with systemd.log_target=kmsg in the kernel command line.

> Thanks so much for all your help on these things.

John, could you please include here the output of lsblk, your fstab,
your dracut.conf, and your lilo.conf?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 20:23, schrieb Canek Peláez Valdés:

> John, could you please include here the output of lsblk, your fstab,
> your dracut.conf, and your lilo.conf?

.. I agree! it's hard to keep track and overview in here :-)

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Thu, May 15, 2014 at 4:39 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Wed, May 14, 2014 at 5:26 PM,  <covici@ccs.covici.com> wrote:
> >> [snip]
> >> >
> >> > Well, the workaround sort of worked -- it went through the initrd -- I
> >> > had debug in the kernel command line, but it did not stop for nothing!
> >> > When it went to the real root, however it did not activate any of the
> >> > lvm volumes I had except for what I specified in the kernel command
> >> > line, causing things not to work well.  Also, I noticed that if insisted
> >> > on using the predictable network names, even though I have
> >> > /etc/udev/rules.d/70-persistent-net.rules and
> >> > /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
> >> > me back my eth* names.  So all in all, it was a mess and took me to an
> >> > emergency shell and that was the end of that.  I did eventually activate
> >> > some volumes by lvchange -aay, but obviously that would not work well.
> >>
> >> OK, I was a little mystified about why dracut-036 worked on my system
> >> and 037 didn't. Before I tried any workaround, I wanted to know what
> >> changed from the previous version to the current one.
> >>
> >> So I generated an initramfs with dracut-036-r4 and another one with
> >> dracut-037-r1, and I tried to see what changed from one to the other.
> >> The answer is surprisingly easy: in /etc/cmdline.d/, the following
> >> files where in the 036-r4 version, but not in the 037-r4:
> >>
> >> 90crypt.conf
> >> 90lvm.conf
> >> 90mdraid.conf
> >> base.conf
> >>
> >> Te contents of those files are (90crypt.conf is empty):
> >>
> >> 90lvm.conf
> >>    rd.lvm.lv=vg/vol1
> >>    rd.lvm.lv=vg/vol4
> >>    rd.lvm.lv=vg/vol3
> >>
> >> 90mdraid.conf
> >>    rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
> >>
> >> base.conf
> >>    ro
> >>
> >> So I just changed my /etc/default/grub file:
> >>
> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
> >> rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
> >> rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
> >>
> >> I regenerated my GRUB2 config, and now again my LVM test system works
> >> perfectly with the latest dracut version.
> >>
> >> The thing is, I *ALWAYS* use the -H (host only) option, so it was my
> >> understanding that the command line should be automatically generated,
> >> and it was on 036, but now it doesn't in 037. I think that's a bug.
> >>
> >> John, with respect to your case: did you used "dracut --print-cmdline"
> >> to get the command line? Also, have you tried to use -H to generate
> >> your initramfs?
> >
> > I did not try the -H, I may test with that later.
> >
> >
> > I did look at the --print-cmdline and copied the volumes they mentioned,
> > but I have other lvm volumes in my fstab and none of them were activated,
> > only the ones I specified in the command line!  This is where I have run
> > into problems.  I have quite a few lvms, I want them all activated!
> 
> I just have /, /boot, /usr and /home (encrypted) as lvms, but all are activated.
> 
> > Also, since I wrote the last message, I have been looking at the
> > journalctl output and discovered a couple of things which I would like
> > some help on, but getting the lvms to work is more important.
> >
> > First, whatever happened to DefaultControllers -- I want to disable
> > those cpu hierarchies, but that option seems to have disappeared without
> > a trace, although you can google and see it in some documentation.
> 
> That went away with the new cgroup handling that is being coordinated
> between systemd and the kernel:
> 
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=7ac807320a7416463d7ff3ef6ede574863a601c5
> 
> > The keyword also was not accepted in an install section I have, what is
> > the matter with that?  I want to use my sysklogd for my syslog, how can
> > I use that with systemd?
> 
> I think you can do that with systemd.log_target=kmsg in the kernel command line.
> 
> > Thanks so much for all your help on these things.
> 
> John, could you please include here the output of lsblk, your fstab,
> your dracut.conf, and your lilo.conf?

output of lsblk:
NAME                           MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                              8:0    0 931.5G  0 disk 
├─sda1                           8:1    0     3G  0 part /boot
├─sda2                           8:2    0  1000M  0 part /mnt/oldgentoo
└─sda3                           8:3    0 927.6G  0 part 
  ├─linux--files-64--root      253:0    0     3G  0 lvm  /
  ├─linux--files-swap          253:1    0     2G  0 lvm  [SWAP]
  ├─linux--files-64--usr       253:2    0    65G  0 lvm  /usr
  ├─linux--files-usr--src      253:3    0    35G  0 lvm  /usr/src
  ├─linux--files-tmp           253:4    0    10G  0 lvm  /tmp
  ├─linux--files-64--var       253:5    0    20G  0 lvm  /var
  ├─linux--files-home          253:6    0    30G  0 lvm  /home
  ├─linux--files-audio         253:7    0   990G  0 lvm  /audio
  ├─linux--files-usr--bbs      253:8    0   256M  0 lvm  /usr/bbs
  ├─linux--files-hard2         253:9    0   704M  0 lvm  /hard2
  ├─linux--files-scratch       253:10   0     1G  0 lvm  /mnt/scratch
  ├─linux--files-var           253:11   0     8G  0 lvm  /mnt/oldgentoo/var
  └─linux--files-usr           253:12   0    25G  0 lvm  /mnt/oldgentoo/usr
sdb                              8:16   0 931.5G  0 disk 
└─sdb1                           8:17   0 931.5G  0 part 
  ├─linux--files-64--root      253:0    0     3G  0 lvm  /
  ├─linux--files-64--usr       253:2    0    65G  0 lvm  /usr
  ├─linux--files-usr--src      253:3    0    35G  0 lvm  /usr/src
  ├─linux--files-64--var       253:5    0    20G  0 lvm  /var
  ├─linux--files-audio         253:7    0   990G  0 lvm  /audio
  └─linux--files-portage       253:13   0    25G  0 lvm  /var/tmp/portage
sdc                              8:32   0   2.7T  0 disk 
└─sdc1                           8:33   0   2.7T  0 part 
  └─backup--files-ccs--backups 253:14   0   2.7T  0 lvm  
sr0                             11:0    1  1024M  0 rom  

my fstab:
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't 
# needed; notail increases performance of ReiserFS (at the expense of storage 
# efficiency).  It's safe to drop the noatime options if you want and to 
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs>			<mountpoint>	<type>		<opts>		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#/dev/BOOT		/boot		ext2		noauto,noatime	1 2
/dev/mapper/linux--files-64--root		/		ext4		defaults 0 1
/dev/sda1 /boot ext4 defaults 0 1
/dev/mapper/linux--files-swap		none		swap		sw		0 0
#/dev/fd0		/mnt/floppy	auto		noauto		0 0

# NOTE: The next line is critical for boot!
proc			/proc		proc		defaults	0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for 
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
shm			/dev/shm	tmpfs		nodev,nosuid,noexec	0 0
/dev/mapper/linux--files-64--usr /usr ext4 defaults 0 2
/dev/mapper/linux--files-usr--src /usr/src ext4  defaults 0 2
/dev/mapper/linux--files-tmp /tmp ext4 defaults,nodev,nosuid,noexec 0 2
/dev/mapper/linux--files-64--var /var ext4 defaults 0 3
/dev/mapper/linux--files-portage  /var/tmp/portage ext4 defaults 0 3
/dev/mapper/linux--files-home /home ext4 defaults 0 3
/dev/mapper/linux--files-audio /audio ext4 defaults 0 3
/dev/mapper/linux--files-usr--bbs /usr/bbs ext4 defaults 0 3
/dev/mapper/linux--files-hard2 /hard2 ext4 defaults 0 3
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
/dev/mapper/linux--files-scratch /mnt/scratch ext4 defaults 0 3

/dev/sda2 /mnt/oldgentoo ext4 defaults 0 3
/dev/mapper/linux--files-usr /mnt/oldgentoo/usr ext3 defaults 0 3
/dev/mapper/linux--files-var /mnt/oldgentoo/var ext4 defaults 0 3

the dracut.conf:

# PUT YOUR CONFIG HERE OR IN separate files named *.conf
# in /etc/dracut.conf.d
# SEE man dracut.conf(5)

# Sample dracut config file

#logfile=/var/log/dracut.log
#fileloglvl=6

# Exact list of dracut modules to use.  Modules not listed here are not going
# to be included.  If you only want to add some optional modules use
# add_dracutmodules option instead.
#dracutmodules+=""

# dracut modules to omit
#omit_dracutmodules+=""

# dracut modules to add to the default
#add_dracutmodules+=""

# additional kernel modules to the default
#add_drivers+=""

# list of kernel filesystem modules to be included in the generic initramfs
#filesystems+=""

# build initrd only to boot current hardware
#hostonly="yes"
#

# install local /etc/mdadm.conf
#mdadmconf="no"

# install local /etc/lvm/lvm.conf
#lvmconf="no"

# A list of fsck tools to install. If it's not specified, module's hardcoded
# default is used, currently: "umount mount /sbin/fsck* xfs_db xfs_check
# xfs_repair e2fsck jfs_fsck reiserfsck btrfsck". The installation is
# opportunistic, so non-existing tools are just ignored.
#fscks=""

# inhibit installation of any fsck tools
#nofscks="yes"

# mount / and /usr read-only by default
#ro_mnt="no"

# set the directory for temporary files
# default: /var/tmp
#tmpdir=/tmp
use_fstab=yes

add_dracutmodules+="lvm"
install_items+="/etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-net-name-slot.rules"



the section of the lilo.conf:
image=/boot/vmlinuz-3.6.2-gentoo
label=3.6.2-systemd
read-only
append=" ramdisk=8192 root=/dev/mapper/linux--files-64--root  video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M rootfstype=ext4 init=/usr/lib/systemd/systemd rd.shell=1   systemd.log_level=debug debug rd.lvm.lv=linux-files/64-root rd.lvm.lv=linux-files/64-usr"
initrd=/boot/initramfs-3.6.2-gentoo.img


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:

> image=/boot/vmlinuz-3.6.2-gentoo

phew. 3.6.2 is from October 2012 ...
Did you recompile it with the suggested options for systemd?

Maybe it doesn't matter, but just a thought ... that kernel is quite old.

Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Stefan G. Weichinger <lists@xunil.at> wrote:

> Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
> 
> > image=/boot/vmlinuz-3.6.2-gentoo
> 
> phew. 3.6.2 is from October 2012 ...
> Did you recompile it with the suggested options for systemd?
> 
> Maybe it doesn't matter, but just a thought ... that kernel is quite old.

I did recompile a number of times, but for now I have to stick with this
one.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
>
>> image=/boot/vmlinuz-3.6.2-gentoo
>
> phew. 3.6.2 is from October 2012 ...
> Did you recompile it with the suggested options for systemd?
>
> Maybe it doesn't matter, but just a thought ... that kernel is quite old.

It doesn't matter, at least in theory systemd works with linux-3.0.

John, could you please send the output from dracut --print-cmdline? In
my case, it lists *ALL* my lvms, and (I think) therefore all of them
are mounted.

Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
rd.lvm.lv=linux-files/64-usr, I think that would explain why it
doesn't mount the others.

If dracut --print-cmdline doesn't print the others, could you try to
boot with rd.lvm.lv=linux-files/audio in the kernel command line
specified in your lilo.conf? If after booting /audio is mounted, then
I think we have found the problem. We'll need just to figure out why
dracut --print-cmdline does not print the other lvms.

Also, could you try to generate your initramfs again, but this time
with add_dracutmodules+="systemd lvm"?

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> > Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
> >
> >> image=/boot/vmlinuz-3.6.2-gentoo
> >
> > phew. 3.6.2 is from October 2012 ...
> > Did you recompile it with the suggested options for systemd?
> >
> > Maybe it doesn't matter, but just a thought ... that kernel is quite old.
> 
> It doesn't matter, at least in theory systemd works with linux-3.0.
> 
> John, could you please send the output from dracut --print-cmdline? In
> my case, it lists *ALL* my lvms, and (I think) therefore all of them
> are mounted.
> 
> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
> rd.lvm.lv=linux-files/64-usr, I think that would explain why it
> doesn't mount the others.
> 
> If dracut --print-cmdline doesn't print the others, could you try to
> boot with rd.lvm.lv=linux-files/audio in the kernel command line
> specified in your lilo.conf? If after booting /audio is mounted, then
> I think we have found the problem. We'll need just to figure out why
> dracut --print-cmdline does not print the other lvms.
> 
> Also, could you try to generate your initramfs again, but this time
> with add_dracutmodules+="systemd lvm"?
The secret to activate all the volumes, is to specify the volume groups
instead of each volume -- that got them all activated, but systemd still
is not working well.  The print-cmdline still just prints the volumes
necessary to mount the root and user file systems, which makes sense,
but why the rest of them do not activate, I have no clue.

Now for some systemd problems.  The root file system was read only when
I logged in, but I could remount it rw -- not sure why this was
happening.  Some units did start, but most did not.  Whenever I tried to
start one manually, I got a message like the following:
I wrote
systemctl start /usr/lib/systemd/system/ntpd.service and got the error
that it was unable to start because
it could not find ntpd.service.mount:]
May 16 01:59:52 ccs kernel: <31>systemd[1]: Failed to load configuration
for usr-lib-systemd-system-ntpd.service.mount: No such file or directory
May 16 01:59:52 ccs kernel: <31>systemd[1]: Trying to enqueue job
usr-lib-systemd-system-ntpd.service.mount/start/replace
May 16 01:59:53 ccs kernel: <31>systemd[1]: Sent message type=error
sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1
reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount
failed to load: No such file or directory.
May 16 01:59:53 ccs kernel: <31>systemd[1]: Failed to process message
[type=method_call sender=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.sys\temd1.Manager member=StartUnit
signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to
load: No such file or directory.

No matter what unit I tried to start I would get such a  message about
the service.mount.

Also, even though my network names were correct, they did not come up,
but I will try to look in the logs to see why not.

So we have made some progress, but still a long way to go yet.  Note
also, that I am not booting into a display manager, just a regular
console.


What a lot of work just to get the system booted!

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Stefan G. Weichinger]

Am 16.05.2014 12:53, schrieb covici@ccs.covici.com:

> Now for some systemd problems.  The root file system was read only when
> I logged in, but I could remount it rw -- not sure why this was
> happening.  Some units did start, but most did not.  

Maybe you only got into emergency mode?

> Also, even though my network names were correct, they did not come up,
> but I will try to look in the logs to see why not.
> 
> So we have made some progress, but still a long way to go yet.  Note
> also, that I am not booting into a display manager, just a regular
> console.
> 
> 
> What a lot of work just to get the system booted!

Oh yes! very complex stuff all around.

If you want send me the log off-list, I am curious to read through it.
This really gets a challenge here ;-)

Stefan

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> > Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
> >
> >> image=/boot/vmlinuz-3.6.2-gentoo
> >
> > phew. 3.6.2 is from October 2012 ...
> > Did you recompile it with the suggested options for systemd?
> >
> > Maybe it doesn't matter, but just a thought ... that kernel is quite old.
> 
> It doesn't matter, at least in theory systemd works with linux-3.0.
> 
> John, could you please send the output from dracut --print-cmdline? In
> my case, it lists *ALL* my lvms, and (I think) therefore all of them
> are mounted.
> 
> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
> rd.lvm.lv=linux-files/64-usr, I think that would explain why it
> doesn't mount the others.
> 
> If dracut --print-cmdline doesn't print the others, could you try to
> boot with rd.lvm.lv=linux-files/audio in the kernel command line
> specified in your lilo.conf? If after booting /audio is mounted, then
> I think we have found the problem. We'll need just to figure out why
> dracut --print-cmdline does not print the other lvms.
> 
> Also, could you try to generate your initramfs again, but this time
> with add_dracutmodules+="systemd lvm"?
Also, when I booted up, the systemd started a user slice and a new copy
of systemd in the slice -- whic I think I don't want -- is this normal?
-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Fri, May 16, 2014 at 5:53 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
>> > Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
>> >
>> >> image=/boot/vmlinuz-3.6.2-gentoo
>> >
>> > phew. 3.6.2 is from October 2012 ...
>> > Did you recompile it with the suggested options for systemd?
>> >
>> > Maybe it doesn't matter, but just a thought ... that kernel is quite old.
>>
>> It doesn't matter, at least in theory systemd works with linux-3.0.
>>
>> John, could you please send the output from dracut --print-cmdline? In
>> my case, it lists *ALL* my lvms, and (I think) therefore all of them
>> are mounted.
>>
>> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
>> rd.lvm.lv=linux-files/64-usr, I think that would explain why it
>> doesn't mount the others.
>>
>> If dracut --print-cmdline doesn't print the others, could you try to
>> boot with rd.lvm.lv=linux-files/audio in the kernel command line
>> specified in your lilo.conf? If after booting /audio is mounted, then
>> I think we have found the problem. We'll need just to figure out why
>> dracut --print-cmdline does not print the other lvms.
>>
>> Also, could you try to generate your initramfs again, but this time
>> with add_dracutmodules+="systemd lvm"?
> The secret to activate all the volumes, is to specify the volume groups
> instead of each volume -- that got them all activated, but systemd still
> is not working well.  The print-cmdline still just prints the volumes
> necessary to mount the root and user file systems, which makes sense,
> but why the rest of them do not activate, I have no clue.

I don't understand the current situation .So now you get ALL your
volumes activated, or not?

> Now for some systemd problems.  The root file system was read only when
> I logged in, but I could remount it rw -- not sure why this was
> happening.

Set systemd.log_level=debug in your command line, and post the exit
from journalctl -b.

>  Some units did start, but most did not.  Whenever I tried to
> start one manually, I got a message like the following:
> I wrote
> systemctl start /usr/lib/systemd/system/ntpd.service and got the error
> that it was unable to start because
> it could not find ntpd.service.mount:]
> May 16 01:59:52 ccs kernel: <31>systemd[1]: Failed to load configuration
> for usr-lib-systemd-system-ntpd.service.mount: No such file or directory
> May 16 01:59:52 ccs kernel: <31>systemd[1]: Trying to enqueue job
> usr-lib-systemd-system-ntpd.service.mount/start/replace
> May 16 01:59:53 ccs kernel: <31>systemd[1]: Sent message type=error
> sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1
> reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount
> failed to load: No such file or directory.
> May 16 01:59:53 ccs kernel: <31>systemd[1]: Failed to process message
> [type=method_call sender=n/a path=/org/freedesktop/systemd1
> interface=org.freedesktop.sys\temd1.Manager member=StartUnit
> signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to
> load: No such file or directory.
>
> No matter what unit I tried to start I would get such a  message about
> the service.mount.

That sounds like a problem with the cgroups hierarchy (which uses a
virtual filesystem). I don't remember seeing a problem like that
before.

> Also, even though my network names were correct, they did not come up,
> but I will try to look in the logs to see why not.

systemd will not (AFAIK) start your network, and before the 209 or 210
version it needed helper program (NetwokrManager, connman, ip,
ifconfig, etc.) to do it. Now it includes networkd, but you need to
set up .network files (like .service files) to configure it. See [1].

> So we have made some progress, but still a long way to go yet.  Note
> also, that I am not booting into a display manager, just a regular
> console.
>
>
> What a lot of work just to get the system booted!

Well, you have a setup that is not, by any means, simple. Also, in my
experience old LVM configurations seem to cause a lot of troubles to
bring to what systemd expects.

John, could you also post here your kernel config? Those cgroups
errors *may* be related to some missing functionality from the kernel.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Fri, May 16, 2014 at 7:46 AM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
>> > Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
>> >
>> >> image=/boot/vmlinuz-3.6.2-gentoo
>> >
>> > phew. 3.6.2 is from October 2012 ...
>> > Did you recompile it with the suggested options for systemd?
>> >
>> > Maybe it doesn't matter, but just a thought ... that kernel is quite old.
>>
>> It doesn't matter, at least in theory systemd works with linux-3.0.
>>
>> John, could you please send the output from dracut --print-cmdline? In
>> my case, it lists *ALL* my lvms, and (I think) therefore all of them
>> are mounted.
>>
>> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
>> rd.lvm.lv=linux-files/64-usr, I think that would explain why it
>> doesn't mount the others.
>>
>> If dracut --print-cmdline doesn't print the others, could you try to
>> boot with rd.lvm.lv=linux-files/audio in the kernel command line
>> specified in your lilo.conf? If after booting /audio is mounted, then
>> I think we have found the problem. We'll need just to figure out why
>> dracut --print-cmdline does not print the other lvms.
>>
>> Also, could you try to generate your initramfs again, but this time
>> with add_dracutmodules+="systemd lvm"?
> Also, when I booted up, the systemd started a user slice and a new copy
> of systemd in the slice -- whic I think I don't want -- is this normal?

Yes: every user session gets its own cgroup and systemd --user
instance. You can track them with loginctl.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Fri, May 16, 2014 at 5:53 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Thu, May 15, 2014 at 5:01 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> >> > Am 15.05.2014 22:38, schrieb covici@ccs.covici.com:
> >> >
> >> >> image=/boot/vmlinuz-3.6.2-gentoo
> >> >
> >> > phew. 3.6.2 is from October 2012 ...
> >> > Did you recompile it with the suggested options for systemd?
> >> >
> >> > Maybe it doesn't matter, but just a thought ... that kernel is quite old.
> >>
> >> It doesn't matter, at least in theory systemd works with linux-3.0.
> >>
> >> John, could you please send the output from dracut --print-cmdline? In
> >> my case, it lists *ALL* my lvms, and (I think) therefore all of them
> >> are mounted.
> >>
> >> Since your lilo.conf only lists rd.lvm.lv=linux-files/64-root and
> >> rd.lvm.lv=linux-files/64-usr, I think that would explain why it
> >> doesn't mount the others.
> >>
> >> If dracut --print-cmdline doesn't print the others, could you try to
> >> boot with rd.lvm.lv=linux-files/audio in the kernel command line
> >> specified in your lilo.conf? If after booting /audio is mounted, then
> >> I think we have found the problem. We'll need just to figure out why
> >> dracut --print-cmdline does not print the other lvms.
> >>
> >> Also, could you try to generate your initramfs again, but this time
> >> with add_dracutmodules+="systemd lvm"?
> > The secret to activate all the volumes, is to specify the volume groups
> > instead of each volume -- that got them all activated, but systemd still
> > is not working well.  The print-cmdline still just prints the volumes
> > necessary to mount the root and user file systems, which makes sense,
> > but why the rest of them do not activate, I have no clue.
> 
> I don't understand the current situation .So now you get ALL your
> volumes activated, or not?

Yep, they are all activated and they all get mounted.
> 
> > Now for some systemd problems.  The root file system was read only when
> > I logged in, but I could remount it rw -- not sure why this was
> > happening.
> 
> Set systemd.log_level=debug in your command line, and post the exit
> from journalctl -b.

I had debug in the command line by itself, would that make the correct
log_level?  The file is quite large, should I send it to you privately?

> 
> >  Some units did start, but most did not.  Whenever I tried to
> > start one manually, I got a message like the following:
> > I wrote
> > systemctl start /usr/lib/systemd/system/ntpd.service and got the error
> > that it was unable to start because
> > it could not find ntpd.service.mount:]
> > May 16 01:59:52 ccs kernel: <31>systemd[1]: Failed to load configuration
> > for usr-lib-systemd-system-ntpd.service.mount: No such file or directory
> > May 16 01:59:52 ccs kernel: <31>systemd[1]: Trying to enqueue job
> > usr-lib-systemd-system-ntpd.service.mount/start/replace
> > May 16 01:59:53 ccs kernel: <31>systemd[1]: Sent message type=error
> > sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1
> > reply_cookie=1 erro\r=Unit usr-lib-systemd-system-ntpd.service.mount
> > failed to load: No such file or directory.
> > May 16 01:59:53 ccs kernel: <31>systemd[1]: Failed to process message
> > [type=method_call sender=n/a path=/org/freedesktop/systemd1
> > interface=org.freedesktop.sys\temd1.Manager member=StartUnit
> > signature=ss]: Unit usr-lib-systemd-system-ntpd.service.mount failed to
> > load: No such file or directory.
> >
> > No matter what unit I tried to start I would get such a  message about
> > the service.mount.
> 
> That sounds like a problem with the cgroups hierarchy (which uses a
> virtual filesystem). I don't remember seeing a problem like that
> before.
> 
> > Also, even though my network names were correct, they did not come up,
> > but I will try to look in the logs to see why not.
I wrote a service file to start my network adaptors, here it is:
network@.service


[Unit]
Description=Network Connectivity for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
${gateway}'
ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=network.target

> 
> systemd will not (AFAIK) start your network, and before the 209 or 210
> version it needed helper program (NetwokrManager, connman, ip,
> ifconfig, etc.) to do it. Now it includes networkd, but you need to
> set up .network files (like .service files) to configure it. See [1].
> 
> > So we have made some progress, but still a long way to go yet.  Note
> > also, that I am not booting into a display manager, just a regular
> > console.
> >
> >
> > What a lot of work just to get the system booted!
> 
> Well, you have a setup that is not, by any means, simple. Also, in my
> experience old LVM configurations seem to cause a lot of troubles to
> bring to what systemd expects.
> 
> John, could you also post here your kernel config? Those cgroups
> errors *may* be related to some missing functionality from the kernel.

#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.6.2-gentoo Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_GPIO=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_CPU_AUTOPROBE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_DEFAULT_HOSTNAME="ccs"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_FHANDLE=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_WATCH=y
CONFIG_AUDIT_TREE=y
CONFIG_AUDIT_LOGINUID_IMMUTABLE=y
CONFIG_HAVE_GENERIC_HARDIRQS=y

#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y

#
# RCU Subsystem
#
CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_BOOST is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=21
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_RESOURCE_COUNTERS is not set
# CONFIG_CGROUP_PERF is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs"
CONFIG_INITRAMFS_ROOT_UID=0
CONFIG_INITRAMFS_ROOT_GID=0
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
# CONFIG_INITRAMFS_COMPRESSION_NONE is not set
CONFIG_INITRAMFS_COMPRESSION_GZIP=y
# CONFIG_INITRAMFS_COMPRESSION_BZIP2 is not set
# CONFIG_INITRAMFS_COMPRESSION_LZMA is not set
# CONFIG_INITRAMFS_COMPRESSION_XZ is not set
# CONFIG_INITRAMFS_COMPRESSION_LZO is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
# CONFIG_COMPAT_BRK is not set
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_PROFILING is not set
CONFIG_TRACEPOINTS=y
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
CONFIG_UPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
CONFIG_SYSV68_PARTITION=y
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_UNINLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
# CONFIG_INLINE_SPIN_UNLOCK_IRQ is not set
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
# CONFIG_INLINE_READ_UNLOCK is not set
# CONFIG_INLINE_READ_UNLOCK_BH is not set
# CONFIG_INLINE_READ_UNLOCK_IRQ is not set
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
# CONFIG_INLINE_WRITE_UNLOCK is not set
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
# CONFIG_INLINE_WRITE_UNLOCK_IRQ is not set
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y

#
# Processor type and features
#
CONFIG_ZONE_DMA=y
CONFIG_SMP=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_NO_BOOTMEM=y
CONFIG_MEMTEST=y
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
CONFIG_MCORE2=y
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_P6_NOP=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
# CONFIG_AMD_NUMA is not set
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=8
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
CONFIG_ARCH_DISCARD_MEMBLOCK=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_CLEANCACHE=y
CONFIG_FRONTSWAP=y
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_ARCH_RANDOM=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y

#
# Power management and ACPI options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
# CONFIG_PM_RUNTIME is not set
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_EC_DEBUGFS=m
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=y
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_PCI_SLOT=m
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
# CONFIG_ACPI_SBS is not set
CONFIG_ACPI_HED=y
# CONFIG_ACPI_CUSTOM_METHOD is not set
# CONFIG_ACPI_BGRT is not set
CONFIG_ACPI_APEI=y
CONFIG_ACPI_APEI_GHES=y
# CONFIG_ACPI_APEI_PCIEAER is not set
CONFIG_ACPI_APEI_EINJ=m
CONFIG_ACPI_APEI_ERST_DEBUG=m
CONFIG_SFI=y

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# x86 CPU frequency scaling drivers
#
CONFIG_X86_PCC_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_P4_CLOCKMOD=m

#
# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set
CONFIG_INTEL_IDLE=y

#
# Memory power savings
#
CONFIG_I7300_IDLE_IOAT_CHANNEL=y
CONFIG_I7300_IDLE=m

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
CONFIG_PCIEAER_INJECT=m
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
CONFIG_PCI_STUB=m
CONFIG_HT_IRQ=y
CONFIG_PCI_ATS=y
CONFIG_PCI_IOV=y
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not set
CONFIG_PCI_IOAPIC=y
CONFIG_PCI_LABEL=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
CONFIG_PCCARD=m
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=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=y
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_RAPIDIO is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=m
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=m
CONFIG_X86_X32=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_KEYS_COMPAT=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_X86_DEV_DMA_OPS=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_UNIX_DIAG=m
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=m
CONFIG_XFRM_USER=m
CONFIG_XFRM_SUB_POLICY=y
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_FIB_TRIE_STATS is not set
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_CLASSID=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
CONFIG_NET_IPGRE_DEMUX=m
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_NET_IPVTI=m
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=y
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_INET_UDP_DIAG=m
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
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_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
# CONFIG_IPV6_PIMSM_V2 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_ACCT=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_ZONES=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=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_BROADCAST=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_SNMP=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NF_CT_NETLINK_TIMEOUT=m
CONFIG_NF_CT_NETLINK_HELPER=m
CONFIG_NETFILTER_NETLINK_QUEUE_CT=y
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=m

#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
CONFIG_NETFILTER_XT_CONNMARK=m
CONFIG_NETFILTER_XT_SET=m

#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_AUDIT=m
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CT=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_HMARK=m
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_LOG=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TEE=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m

#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
CONFIG_NETFILTER_XT_MATCH_CLUSTER=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_CPU=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ECN=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=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_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_NFACCT=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=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_RECENT=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=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_IP_SET=m
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=m
CONFIG_IP_SET_BITMAP_IPMAC=m
CONFIG_IP_SET_BITMAP_PORT=m
CONFIG_IP_SET_HASH_IP=m
CONFIG_IP_SET_HASH_IPPORT=m
CONFIG_IP_SET_HASH_IPPORTIP=m
CONFIG_IP_SET_HASH_IPPORTNET=m
CONFIG_IP_SET_HASH_NET=m
CONFIG_IP_SET_HASH_NETPORT=m
CONFIG_IP_SET_HASH_NETIFACE=m
CONFIG_IP_SET_LIST_SET=m
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_RPFILTER=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=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_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=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_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV6=m
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RPFILTER=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_TFRC_LIB=y

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_RDS=m
CONFIG_RDS_RDMA=m
CONFIG_RDS_TCP=m
# CONFIG_RDS_DEBUG is not set
# CONFIG_TIPC is not set
CONFIG_ATM=m
# CONFIG_ATM_CLIP is not set
# CONFIG_ATM_LANE is not set
# CONFIG_ATM_BR2684 is not set
CONFIG_L2TP=m
CONFIG_L2TP_DEBUGFS=m
CONFIG_L2TP_V3=y
CONFIG_L2TP_IP=m
CONFIG_L2TP_ETH=m
CONFIG_STP=m
CONFIG_GARP=m
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_WAN_ROUTER is not set
CONFIG_PHONET=m
CONFIG_IEEE802154=m
CONFIG_IEEE802154_6LOWPAN=m
CONFIG_MAC802154=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_SFB=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_DRR=m
CONFIG_NET_SCH_MQPRIO=m
CONFIG_NET_SCH_CHOKE=m
CONFIG_NET_SCH_QFQ=m
CONFIG_NET_SCH_CODEL=m
CONFIG_NET_SCH_FQ_CODEL=m
CONFIG_NET_SCH_PLUG=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
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_CLS_CGROUP is not set
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_EMATCH_CANID=m
CONFIG_NET_EMATCH_IPSET=m
# CONFIG_NET_CLS_ACT is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
CONFIG_DNS_RESOLVER=y
# CONFIG_BATMAN_ADV is not set
CONFIG_OPENVSWITCH=m
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
CONFIG_NETPRIO_CGROUP=m
CONFIG_BQL=y
CONFIG_BPF_JIT=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_DROP_MONITOR is not set
# CONFIG_HAMRADIO is not set
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m

#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
CONFIG_CAN_SLCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_MCP251X=m
CONFIG_CAN_JANZ_ICAN3=m
CONFIG_PCH_CAN=m
CONFIG_CAN_SJA1000=m
# CONFIG_CAN_SJA1000_ISA is not set
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_EMS_PCMCIA=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_PEAK_PCMCIA=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=y
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PLX_PCI=m
CONFIG_CAN_C_CAN=m
CONFIG_CAN_C_CAN_PLATFORM=m
CONFIG_CAN_C_CAN_PCI=m
CONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not set
CONFIG_CAN_CC770_PLATFORM=m

#
# CAN USB interfaces
#
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
CONFIG_CAN_PEAK_USB=m
CONFIG_CAN_SOFTING=m
CONFIG_CAN_SOFTING_CS=m
# CONFIG_CAN_DEBUG_DEVICES is not set
# CONFIG_IRDA is not set
CONFIG_BT=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 is not set
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_ATH3K=y
CONFIG_BT_HCIUART_LL=y
# CONFIG_BT_HCIUART_3WIRE is not set
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_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
CONFIG_BT_ATH3K=m
CONFIG_BT_WILINK=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_MINSTREL_HT=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_WIMAX=m
CONFIG_WIMAX_DEBUG_LEVEL=8
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_REGULATOR is not set
CONFIG_NET_9P=m
CONFIG_NET_9P_VIRTIO=m
CONFIG_NET_9P_RDMA=m
# CONFIG_NET_9P_DEBUG is not set
CONFIG_CAIF=m
# CONFIG_CAIF_DEBUG is not set
CONFIG_CAIF_NETDEV=m
CONFIG_CAIF_USB=m
CONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set
# CONFIG_CEPH_LIB_USE_DNS_RESOLVER is not set
CONFIG_NFC=m
# CONFIG_NFC_NCI is not set
CONFIG_NFC_HCI=m
# CONFIG_NFC_SHDLC is not set
# CONFIG_NFC_LLCP is not set

#
# Near Field Communication (NFC) devices
#
CONFIG_PN544_NFC=m
CONFIG_NFC_PN533=m
CONFIG_HAVE_BPF_JIT=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
CONFIG_STANDALONE=y
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_GENERIC_CPU_DEVICES is not set
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_SPI=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD 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_MESSAGES=y

#
# 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_DEV_PCIESSD_MTIP32XX=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
# CONFIG_CISS_SCSI_TAPE is not set
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_DRBD=m
# CONFIG_DRBD_FAULT_INJECTION is not set
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_NVME=m
CONFIG_BLK_DEV_OSD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_VIRTIO_BLK=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_RBD=m

#
# Misc devices
#
CONFIG_SENSORS_LIS3LV02D=m
CONFIG_AD525X_DPOT=m
CONFIG_AD525X_DPOT_I2C=m
CONFIG_AD525X_DPOT_SPI=m
# CONFIG_IBM_ASM is not set
CONFIG_PHANTOM=m
CONFIG_INTEL_MID_PTI=m
# CONFIG_SGI_IOC4 is not set
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ICS932S401=m
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_CS5535_MFGPT=m
CONFIG_CS5535_MFGPT_DEFAULT_IRQ=7
CONFIG_CS5535_CLOCK_EVENT_SRC=m
CONFIG_HP_ILO=m
CONFIG_APDS9802ALS=m
CONFIG_ISL29003=m
CONFIG_ISL29020=m
CONFIG_SENSORS_TSL2550=m
CONFIG_SENSORS_BH1780=m
CONFIG_SENSORS_BH1770=m
CONFIG_SENSORS_APDS990X=m
CONFIG_HMC6352=m
CONFIG_DS1682=m
CONFIG_TI_DAC7512=m
CONFIG_VMWARE_BALLOON=m
CONFIG_BMP085=y
CONFIG_BMP085_I2C=m
CONFIG_BMP085_SPI=m
CONFIG_PCH_PHUB=m
CONFIG_USB_SWITCH_FSA9480=m
CONFIG_C2PORT=m
CONFIG_C2PORT_DURAMAR_2150=m

#
# EEPROM support
#
CONFIG_EEPROM_AT24=m
CONFIG_EEPROM_AT25=m
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
CONFIG_EEPROM_93CX6=m
CONFIG_EEPROM_93XX46=m
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not set
CONFIG_CB710_DEBUG_ASSUMPTIONS=y

#
# Texas Instruments shared transport line discipline
#
CONFIG_TI_ST=m
CONFIG_SENSORS_LIS3_I2C=m

#
# Altera FPGA firmware download module
#
CONFIG_ALTERA_STAPL=m
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# 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 is not set
CONFIG_SCSI_SAS_HOST_SMP=y
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_ISCSI_BOOT_SYSFS=m
CONFIG_SCSI_CXGB3_ISCSI=m
CONFIG_SCSI_CXGB4_ISCSI=m
CONFIG_SCSI_BNX2_ISCSI=m
CONFIG_SCSI_BNX2X_FCOE=m
CONFIG_BE2ISCSI=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_HPSA=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_3W_SAS=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 is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=5000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC94XX=m
CONFIG_AIC94XX_DEBUG=y
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_MVSAS_DEBUG=y
# CONFIG_SCSI_MVSAS_TASKLET is not set
CONFIG_SCSI_MVUMI=m
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_ARCMSR=m
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=y
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT2SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS_LOGGING is not set
CONFIG_SCSI_UFSHCD=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
CONFIG_VMWARE_PVSCSI=m
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
CONFIG_FCOE_FNIC=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_ISCI=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
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_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=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_TCM_QLA2XXX=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_DEBUG is not set
CONFIG_SCSI_PMCRAID=m
CONFIG_SCSI_PM8001=m
CONFIG_SCSI_SRP=m
CONFIG_SCSI_BFA_FC=m
CONFIG_SCSI_VIRTIO=m
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
CONFIG_PCMCIA_AHA152X=m
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_SCSI_OSD_INITIATOR=m
CONFIG_SCSI_OSD_ULD=m
CONFIG_SCSI_OSD_DPRINT_SENSE=1
# CONFIG_SCSI_OSD_DEBUG is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=m
CONFIG_SATA_AHCI_PLATFORM=m
CONFIG_SATA_INIC162X=m
CONFIG_SATA_ACARD_AHCI=m
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_SX4=m
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_SVW=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m

#
# PATA SFF controllers with BMDMA
#
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARASAN_CF=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_ATP867X=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CS5536=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
CONFIG_PATA_HPT3X3_DMA=y
CONFIG_PATA_IT8213=m
CONFIG_PATA_IT821X=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_PDC_OLD=m
CONFIG_PATA_RADISYS=m
CONFIG_PATA_RDC=m
CONFIG_PATA_SC1200=m
CONFIG_PATA_SCH=m
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_TOSHIBA=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m

#
# PIO-only SFF controllers
#
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_PCMCIA=m
CONFIG_PATA_RZ1000=m

#
# Generic fallback / legacy drivers
#
CONFIG_PATA_ACPI=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_LEGACY=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MULTICORE_RAID456=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_BUFIO=m
CONFIG_DM_PERSISTENT_DATA=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_THIN_PROVISIONING=m
# CONFIG_DM_DEBUG_BLOCK_STACK_TRACING is not set
CONFIG_DM_MIRROR=m
CONFIG_DM_RAID=m
CONFIG_DM_LOG_USERSPACE=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_QL=m
CONFIG_DM_MULTIPATH_ST=m
CONFIG_DM_DELAY=m
CONFIG_DM_UEVENT=y
# CONFIG_DM_FLAKEY is not set
CONFIG_DM_VERITY=m
CONFIG_TARGET_CORE=m
CONFIG_TCM_IBLOCK=m
CONFIG_TCM_FILEIO=m
CONFIG_TCM_PSCSI=m
CONFIG_LOOPBACK_TARGET=m
CONFIG_TCM_FC=m
# CONFIG_ISCSI_TARGET is not set
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_FUSION_LOGGING=y

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
CONFIG_FIREWIRE_NOSY=m
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=y
# CONFIG_MAC_EMUMOUSEBTN is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
CONFIG_NET_FC=y
CONFIG_MII=m
CONFIG_IEEE802154_DRIVERS=m
CONFIG_IEEE802154_FAKEHARD=m
CONFIG_IEEE802154_FAKELB=m
CONFIG_IEEE802154_AT86RF230=m
CONFIG_NET_TEAM=m
CONFIG_NET_TEAM_MODE_BROADCAST=m
CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
CONFIG_NET_TEAM_MODE_LOADBALANCE=m
CONFIG_MACVLAN=m
CONFIG_MACVTAP=m
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_VIRTIO_NET=m
CONFIG_SUNGEM_PHY=m
# CONFIG_ARCNET is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
# CONFIG_ATM_TCP is not set
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
CONFIG_ATM_FORE200E=m
# CONFIG_ATM_FORE200E_USE_TASKLET is not set
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
# CONFIG_ATM_HE is not set
CONFIG_ATM_SOLOS=m

#
# CAIF transport drivers
#
CONFIG_CAIF_TTY=m
CONFIG_CAIF_SPI_SLAVE=m
# CONFIG_CAIF_SPI_SYNC is not set
# CONFIG_CAIF_HSI is not set
CONFIG_ETHERNET=y
CONFIG_MDIO=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_3C589=m
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
CONFIG_NET_VENDOR_ADAPTEC=y
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_NET_VENDOR_ALTEON=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_NET_VENDOR_AMD=y
CONFIG_AMD8111_ETH=m
CONFIG_PCNET32=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_NET_VENDOR_ATHEROS=y
CONFIG_ATL2=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
CONFIG_ATL1C=m
CONFIG_NET_VENDOR_BROADCOM=y
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_BNX2=m
CONFIG_CNIC=m
CONFIG_TIGON3=m
CONFIG_BNX2X=m
CONFIG_NET_VENDOR_BROCADE=y
CONFIG_BNA=m
CONFIG_NET_CALXEDA_XGMAC=m
CONFIG_NET_VENDOR_CHELSIO=y
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T3=m
CONFIG_CHELSIO_T4=m
CONFIG_CHELSIO_T4VF=m
CONFIG_NET_VENDOR_CISCO=y
CONFIG_ENIC=m
CONFIG_DNET=m
CONFIG_NET_VENDOR_DEC=y
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_DE2104X_DSL=0
CONFIG_TULIP=m
CONFIG_TULIP_MWI=y
CONFIG_TULIP_MMIO=y
CONFIG_TULIP_NAPI=y
CONFIG_TULIP_NAPI_HW_MITIGATION=y
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
CONFIG_NET_VENDOR_DLINK=y
CONFIG_DE600=m
CONFIG_DE620=m
CONFIG_DL2K=m
CONFIG_SUNDANCE=m
CONFIG_SUNDANCE_MMIO=y
CONFIG_NET_VENDOR_EMULEX=y
CONFIG_BE2NET=m
CONFIG_NET_VENDOR_EXAR=y
CONFIG_S2IO=m
CONFIG_VXGE=m
# CONFIG_VXGE_DEBUG_TRACE_ALL is not set
CONFIG_NET_VENDOR_FUJITSU=y
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_NET_VENDOR_HP=y
CONFIG_HP100=m
CONFIG_NET_VENDOR_INTEL=y
CONFIG_E100=m
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IGB=m
CONFIG_IGB_DCA=y
# CONFIG_IGB_PTP is not set
CONFIG_IGBVF=m
CONFIG_IXGB=m
CONFIG_IXGBE=m
CONFIG_IXGBE_HWMON=y
CONFIG_IXGBE_DCA=y
CONFIG_IXGBE_DCB=y
# CONFIG_IXGBE_PTP is not set
CONFIG_IXGBEVF=m
CONFIG_NET_VENDOR_I825XX=y
CONFIG_ZNET=m
CONFIG_IP1000=m
CONFIG_JME=m
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
# CONFIG_SKGE_GENESIS is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_NET_VENDOR_MELLANOX=y
CONFIG_MLX4_EN=m
CONFIG_MLX4_EN_DCB=y
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_NET_VENDOR_MICREL=y
CONFIG_KS8842=m
CONFIG_KS8851=m
CONFIG_KS8851_MLL=m
CONFIG_KSZ884X_PCI=m
CONFIG_NET_VENDOR_MICROCHIP=y
CONFIG_ENC28J60=m
# CONFIG_ENC28J60_WRITEVERIFY is not set
CONFIG_NET_VENDOR_MYRI=y
CONFIG_MYRI10GE=m
CONFIG_MYRI10GE_DCA=y
CONFIG_FEALNX=m
CONFIG_NET_VENDOR_NATSEMI=y
CONFIG_NATSEMI=m
CONFIG_NS83820=m
CONFIG_NET_VENDOR_8390=y
CONFIG_PCMCIA_AXNET=m
CONFIG_NE2K_PCI=m
CONFIG_PCMCIA_PCNET=m
CONFIG_NET_VENDOR_NVIDIA=y
CONFIG_FORCEDETH=m
CONFIG_NET_VENDOR_OKI=y
CONFIG_PCH_GBE=m
CONFIG_ETHOC=m
# CONFIG_NET_PACKET_ENGINE is not set
CONFIG_NET_VENDOR_QLOGIC=y
CONFIG_QLA3XXX=m
CONFIG_QLCNIC=m
CONFIG_QLGE=m
CONFIG_NETXEN_NIC=m
CONFIG_NET_VENDOR_REALTEK=y
CONFIG_ATP=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R8169=m
CONFIG_NET_VENDOR_RDC=y
CONFIG_R6040=m
CONFIG_NET_VENDOR_SEEQ=y
CONFIG_SEEQ8005=m
CONFIG_NET_VENDOR_SILAN=y
CONFIG_SC92031=m
CONFIG_NET_VENDOR_SIS=y
CONFIG_SIS900=m
CONFIG_SIS190=m
CONFIG_SFC=m
CONFIG_SFC_MCDI_MON=y
CONFIG_SFC_SRIOV=y
CONFIG_NET_VENDOR_SMSC=y
CONFIG_PCMCIA_SMC91C92=m
CONFIG_EPIC100=m
CONFIG_SMSC9420=m
CONFIG_NET_VENDOR_STMICRO=y
CONFIG_STMMAC_ETH=m
CONFIG_STMMAC_PLATFORM=y
CONFIG_STMMAC_PCI=y
# CONFIG_STMMAC_DEBUG_FS is not set
# CONFIG_STMMAC_DA is not set
CONFIG_STMMAC_RING=y
# CONFIG_STMMAC_CHAINED is not set
CONFIG_NET_VENDOR_SUN=y
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NIU=m
CONFIG_NET_VENDOR_TEHUTI=y
CONFIG_TEHUTI=m
CONFIG_NET_VENDOR_TI=y
CONFIG_TLAN=m
CONFIG_NET_VENDOR_VIA=y
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_VIA_VELOCITY=m
CONFIG_NET_VENDOR_WIZNET=y
CONFIG_WIZNET_W5100=m
CONFIG_WIZNET_W5300=m
# CONFIG_WIZNET_BUS_DIRECT is not set
# CONFIG_WIZNET_BUS_INDIRECT is not set
CONFIG_WIZNET_BUS_ANY=y
CONFIG_NET_VENDOR_XIRCOM=y
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_FDDI=y
CONFIG_DEFXX=m
# CONFIG_DEFXX_MMIO is not set
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_NET_SB1000=m
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_AMD_PHY=m
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_BCM87XX_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
CONFIG_NATIONAL_PHY=m
CONFIG_STE10XP=m
CONFIG_LSI_ET1011C_PHY=m
CONFIG_MICREL_PHY=m
CONFIG_MDIO_BITBANG=m
CONFIG_MDIO_GPIO=m
CONFIG_MICREL_KS8995MA=m
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOATM=m
CONFIG_PPPOE=m
CONFIG_PPTP=m
CONFIG_PPPOL2TP=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_SLIP=m
CONFIG_SLHC=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y

#
# 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_CDC_EEM=m
CONFIG_USB_NET_CDC_NCM=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_SMSC75XX=m
CONFIG_USB_NET_SMSC95XX=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 is not set
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_NET_CX82310_ETH=m
CONFIG_USB_NET_KALMIA=m
CONFIG_USB_NET_QMI_WWAN=m
CONFIG_USB_HSO=m
CONFIG_USB_NET_INT51X1=m
CONFIG_USB_CDC_PHONET=m
CONFIG_USB_IPHETH=m
CONFIG_USB_SIERRA_NET=m
CONFIG_USB_VL600=m
CONFIG_WLAN=y
CONFIG_PCMCIA_RAYCS=m
CONFIG_LIBERTAS_THINFIRM=m
# CONFIG_LIBERTAS_THINFIRM_DEBUG is not set
CONFIG_LIBERTAS_THINFIRM_USB=m
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_AT76C50X_USB=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_RTL8187_LEDS=y
CONFIG_ADM8211=m
# CONFIG_MAC80211_HWSIM is not set
CONFIG_MWL8K=m
CONFIG_ATH_COMMON=m
# CONFIG_ATH_DEBUG is not set
CONFIG_ATH5K=m
# CONFIG_ATH5K_DEBUG is not set
# CONFIG_ATH5K_TRACER is not set
CONFIG_ATH5K_PCI=y
CONFIG_ATH9K_HW=m
CONFIG_ATH9K_COMMON=m
CONFIG_ATH9K_BTCOEX_SUPPORT=y
CONFIG_ATH9K=m
# CONFIG_ATH9K_PCI is not set
# CONFIG_ATH9K_AHB is not set
# CONFIG_ATH9K_DEBUGFS is not set
CONFIG_ATH9K_RATE_CONTROL=y
CONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
CONFIG_CARL9170=m
CONFIG_CARL9170_LEDS=y
CONFIG_CARL9170_WPC=y
# CONFIG_CARL9170_HWRNG is not set
CONFIG_ATH6KL=m
CONFIG_ATH6KL_SDIO=m
CONFIG_ATH6KL_USB=m
# CONFIG_ATH6KL_DEBUG is not set
CONFIG_B43=m
CONFIG_B43_BCMA=y
CONFIG_B43_BCMA_EXTRA=y
CONFIG_B43_SSB=y
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
CONFIG_B43_SDIO=y
CONFIG_B43_BCMA_PIO=y
CONFIG_B43_PIO=y
# CONFIG_B43_PHY_N is not set
CONFIG_B43_PHY_LP=y
CONFIG_B43_PHY_HT=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=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_HWRNG=y
CONFIG_B43LEGACY_DEBUG=y
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_BRCMUTIL=m
CONFIG_BRCMSMAC=m
# CONFIG_BRCMFMAC is not set
# CONFIG_BRCMDBG is not set
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
# CONFIG_HOSTAP_FIRMWARE_NVRAM is not set
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
# CONFIG_IPW2200_MONITOR is not set
# CONFIG_IPW2200_QOS is not set
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBIPW=m
# CONFIG_LIBIPW_DEBUG is not set
CONFIG_IWLWIFI=m
CONFIG_IWLDVM=m

#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not set
# CONFIG_IWLWIFI_DEVICE_TRACING is not set
# CONFIG_IWLWIFI_P2P is not set
# CONFIG_IWLWIFI_EXPERIMENTAL_MFP is not set
CONFIG_IWLEGACY=m
CONFIG_IWL4965=m
CONFIG_IWL3945=m

#
# iwl3945 / iwl4965 Debugging Options
#
# CONFIG_IWLEGACY_DEBUG is not set
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
CONFIG_LIBERTAS_SPI=m
# CONFIG_LIBERTAS_DEBUG is not set
# CONFIG_LIBERTAS_MESH is not set
CONFIG_HERMES=m
# CONFIG_HERMES_PRISM is not set
CONFIG_HERMES_CACHE_FW_ON_INIT=y
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_ORINOCO_USB=m
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
CONFIG_P54_SPI=m
CONFIG_P54_SPI_DEFAULT_EEPROM=y
CONFIG_P54_LEDS=y
# CONFIG_RT2X00 is not set
CONFIG_RTL8192CE=m
CONFIG_RTL8192SE=m
CONFIG_RTL8192DE=m
CONFIG_RTL8192CU=m
CONFIG_RTLWIFI=m
CONFIG_RTLWIFI_DEBUG=y
CONFIG_RTL8192C_COMMON=m
CONFIG_WL_TI=y
CONFIG_WL1251=m
CONFIG_WL1251_SPI=m
CONFIG_WL1251_SDIO=m
CONFIG_WL12XX=m
CONFIG_WL18XX=m
CONFIG_WLCORE=m
CONFIG_WLCORE_SPI=m
CONFIG_WLCORE_SDIO=m
CONFIG_WL12XX_PLATFORM_DATA=y
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_MWIFIEX=m
CONFIG_MWIFIEX_SDIO=m
CONFIG_MWIFIEX_PCIE=m
CONFIG_MWIFIEX_USB=m

#
# WiMAX Wireless Broadband devices
#
CONFIG_WIMAX_I2400M=m
CONFIG_WIMAX_I2400M_USB=m
CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8
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

#
# X.25/LAPB support is disabled
#
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300TOO=m
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
CONFIG_SBNI=m
CONFIG_SBNI_MULTILINE=y
CONFIG_VMXNET3=m
CONFIG_ISDN=y
CONFIG_ISDN_I4L=m
# CONFIG_ISDN_PPP is not set
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=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 is not set
# CONFIG_HISAX_NI1 is not set
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 is not set

#
# 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

#
# Active cards
#
CONFIG_ISDN_CAPI=m
# CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON is not set
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=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=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_CAPI=y
# CONFIG_GIGASET_I4L is not set
# CONFIG_GIGASET_DUMMYLL is not set
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
CONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not set
CONFIG_HYSDN=m
# CONFIG_HYSDN_CAPI is not set
CONFIG_MISDN=m
CONFIG_MISDN_DSP=m
CONFIG_MISDN_L1OIP=m

#
# mISDN hardware drivers
#
CONFIG_MISDN_HFCPCI=m
CONFIG_MISDN_HFCMULTI=m
CONFIG_MISDN_HFCUSB=m
CONFIG_MISDN_AVMFRITZ=m
CONFIG_MISDN_SPEEDFAX=m
CONFIG_MISDN_INFINEON=m
CONFIG_MISDN_W6692=m
CONFIG_MISDN_NETJET=m
CONFIG_MISDN_IPAC=m
CONFIG_MISDN_ISAR=m
CONFIG_ISDN_HDLC=m

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m
CONFIG_INPUT_SPARSEKMAP=m
CONFIG_INPUT_MATRIXKMAP=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_ADP5588=m
CONFIG_KEYBOARD_ADP5589=m
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_QT1070=m
CONFIG_KEYBOARD_QT2160=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_GPIO=m
CONFIG_KEYBOARD_GPIO_POLLED=m
CONFIG_KEYBOARD_TCA6416=m
CONFIG_KEYBOARD_TCA8418=m
CONFIG_KEYBOARD_MATRIX=m
CONFIG_KEYBOARD_LM8323=m
CONFIG_KEYBOARD_LM8333=m
CONFIG_KEYBOARD_MAX7359=m
CONFIG_KEYBOARD_MCS=m
CONFIG_KEYBOARD_MPR121=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_KEYBOARD_OPENCORES=m
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_OMAP4=m
CONFIG_KEYBOARD_XTKBD=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_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# 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_MOUSE_SYNAPTICS_I2C=m
CONFIG_MOUSE_SYNAPTICS_USB=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_AS5011=m
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_JOYSTICK_XPAD=m
# CONFIG_JOYSTICK_XPAD_FF is not set
# CONFIG_JOYSTICK_XPAD_LEDS is not set
CONFIG_JOYSTICK_WALKERA0701=m
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_HANWANG=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_TOUCHSCREEN_AD7877=m
CONFIG_TOUCHSCREEN_AD7879=m
CONFIG_TOUCHSCREEN_AD7879_I2C=m
CONFIG_TOUCHSCREEN_AD7879_SPI=m
CONFIG_TOUCHSCREEN_ATMEL_MXT=m
CONFIG_TOUCHSCREEN_AUO_PIXCIR=m
CONFIG_TOUCHSCREEN_BU21013=m
CONFIG_TOUCHSCREEN_CY8CTMG110=m
CONFIG_TOUCHSCREEN_CYTTSP_CORE=m
CONFIG_TOUCHSCREEN_CYTTSP_I2C=m
CONFIG_TOUCHSCREEN_CYTTSP_SPI=m
CONFIG_TOUCHSCREEN_DA9052=m
CONFIG_TOUCHSCREEN_DYNAPRO=m
CONFIG_TOUCHSCREEN_HAMPSHIRE=m
CONFIG_TOUCHSCREEN_EETI=m
CONFIG_TOUCHSCREEN_EGALAX=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_ILI210X=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_WACOM_W8001=m
CONFIG_TOUCHSCREEN_WACOM_I2C=m
CONFIG_TOUCHSCREEN_MAX11801=m
CONFIG_TOUCHSCREEN_MCS5000=m
CONFIG_TOUCHSCREEN_MMS114=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_INEXIO=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_EDT_FT5X06=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
CONFIG_TOUCHSCREEN_UCB1400=m
CONFIG_TOUCHSCREEN_PIXCIR=m
CONFIG_TOUCHSCREEN_WM97XX=m
CONFIG_TOUCHSCREEN_WM9705=y
CONFIG_TOUCHSCREEN_WM9712=y
CONFIG_TOUCHSCREEN_WM9713=y
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_MC13783=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_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_ELO=y
CONFIG_TOUCHSCREEN_USB_E2I=y
CONFIG_TOUCHSCREEN_USB_ZYTRONIC=y
CONFIG_TOUCHSCREEN_USB_ETT_TC45USB=y
CONFIG_TOUCHSCREEN_USB_NEXIO=y
CONFIG_TOUCHSCREEN_USB_EASYTOUCH=y
CONFIG_TOUCHSCREEN_TOUCHIT213=m
CONFIG_TOUCHSCREEN_TSC_SERIO=m
CONFIG_TOUCHSCREEN_TSC2005=m
CONFIG_TOUCHSCREEN_TSC2007=m
CONFIG_TOUCHSCREEN_PCAP=m
CONFIG_TOUCHSCREEN_ST1232=m
CONFIG_TOUCHSCREEN_TPS6507X=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_88PM80X_ONKEY=m
CONFIG_INPUT_AD714X=m
CONFIG_INPUT_AD714X_I2C=m
CONFIG_INPUT_AD714X_SPI=m
CONFIG_INPUT_BMA150=m
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_MC13783_PWRBUTTON=m
CONFIG_INPUT_MMA8450=m
CONFIG_INPUT_MPU3050=m
CONFIG_INPUT_APANEL=m
CONFIG_INPUT_GP2A=m
CONFIG_INPUT_GPIO_TILT_POLLED=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_KXTJ9=m
# CONFIG_INPUT_KXTJ9_POLLED_MODE is not set
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_CM109=m
# CONFIG_INPUT_UINPUT is not set
CONFIG_INPUT_PCF50633_PMU=m
CONFIG_INPUT_PCF8574=m
CONFIG_INPUT_GPIO_ROTARY_ENCODER=m
CONFIG_INPUT_DA9052_ONKEY=m
CONFIG_INPUT_PCAP=m
CONFIG_INPUT_ADXL34X=m
CONFIG_INPUT_ADXL34X_I2C=m
CONFIG_INPUT_ADXL34X_SPI=m
CONFIG_INPUT_CMA3000=m
CONFIG_INPUT_CMA3000_I2C=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 is not set
CONFIG_SERIO_ALTERA_PS2=m
CONFIG_SERIO_PS2MULT=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_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_NOZOMI=m
CONFIG_N_GSM=m
# CONFIG_TRACE_ROUTER is not set
CONFIG_TRACE_SINK=m

#
# KCopy
#
CONFIG_KCOPY=m
CONFIG_DEVKMEM=y

#
# 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=6
CONFIG_SERIAL_8250_RUNTIME_UARTS=6
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_MAX3100=m
CONFIG_SERIAL_MAX3107=m
CONFIG_SERIAL_MRST_MAX3110=m
CONFIG_SERIAL_MFD_HSU=m
CONFIG_SERIAL_UARTLITE=m
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_SERIAL_TIMBERDALE=m
CONFIG_SERIAL_ALTERA_JTAGUART=m
CONFIG_SERIAL_ALTERA_UART=m
CONFIG_SERIAL_ALTERA_UART_MAXPORTS=4
CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200
CONFIG_SERIAL_IFX6X60=m
CONFIG_SERIAL_PCH_UART=m
CONFIG_SERIAL_XILINX_PS_UART=m
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_VIRTIO_CONSOLE=m
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=m
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_VIA=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
# CONFIG_GEN_RTC_X is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
# CONFIG_TCG_TIS is not set
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_MUX=m

#
# Multiplexer I2C Chip support
#
CONFIG_I2C_MUX_GPIO=m
CONFIG_I2C_MUX_PCA9541=m
CONFIG_I2C_MUX_PCA954x=m
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=m
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

#
# ACPI drivers
#
CONFIG_I2C_SCMI=m

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_DESIGNWARE_CORE=m
CONFIG_I2C_DESIGNWARE_PCI=m
CONFIG_I2C_EG20T=m
CONFIG_I2C_GPIO=m
CONFIG_I2C_INTEL_MID=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_PCA_PLATFORM=m
# CONFIG_I2C_PXA_PCI is not set
CONFIG_I2C_SIMTEC=m
CONFIG_I2C_XILINX=m

#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_DIOLAN_U2C=m
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_TAOS_EVM=m
CONFIG_I2C_TINY_USB=m

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_ALTERA=m
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
CONFIG_SPI_GPIO=m
CONFIG_SPI_LM70_LLP=m
CONFIG_SPI_OC_TINY=m
# CONFIG_SPI_PXA2XX_PCI is not set
CONFIG_SPI_TOPCLIFF_PCH=m
CONFIG_SPI_XCOMM=m
CONFIG_SPI_XILINX=m
CONFIG_SPI_DESIGNWARE=m
CONFIG_SPI_DW_PCI=m
CONFIG_SPI_DW_MID_DMA=y

#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=m
CONFIG_SPI_TLE62X0=m
CONFIG_HSI=m
CONFIG_HSI_BOARDINFO=y

#
# HSI clients
#
CONFIG_HSI_CHAR=m

#
# PPS support
#
CONFIG_PPS=m
# CONFIG_PPS_DEBUG is not set
# CONFIG_NTP_PPS is not set

#
# PPS clients support
#
CONFIG_PPS_CLIENT_KTIMER=m
CONFIG_PPS_CLIENT_LDISC=m
CONFIG_PPS_CLIENT_PARPORT=m
CONFIG_PPS_CLIENT_GPIO=m

#
# PPS generators support
#

#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
CONFIG_GPIO_GENERIC=m
CONFIG_GPIO_MAX730X=m

#
# Memory mapped GPIO drivers:
#
CONFIG_GPIO_GENERIC_PLATFORM=m
CONFIG_GPIO_IT8761E=m
CONFIG_GPIO_SCH=m
CONFIG_GPIO_ICH=m
CONFIG_GPIO_VX855=m

#
# I2C GPIO expanders:
#
CONFIG_GPIO_ARIZONA=m
CONFIG_GPIO_MAX7300=m
CONFIG_GPIO_MAX732X=m
CONFIG_GPIO_PCA953X=m
CONFIG_GPIO_PCF857X=m
# CONFIG_GPIO_SX150X is not set
CONFIG_GPIO_ADP5588=m

#
# PCI GPIO expanders:
#
CONFIG_GPIO_CS5535=m
CONFIG_GPIO_AMD8111=m
# CONFIG_GPIO_LANGWELL is not set
CONFIG_GPIO_PCH=m
CONFIG_GPIO_ML_IOH=m
CONFIG_GPIO_TIMBERDALE=y
CONFIG_GPIO_RDC321X=m

#
# SPI GPIO expanders:
#
CONFIG_GPIO_MAX7301=m
CONFIG_GPIO_MCP23S08=m
CONFIG_GPIO_MC33880=m
CONFIG_GPIO_74X164=m

#
# AC97 GPIO expanders:
#
# CONFIG_GPIO_UCB1400 is not set

#
# MODULbus GPIO expanders:
#
CONFIG_GPIO_JANZ_TTL=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_DS1WM=m
CONFIG_W1_MASTER_GPIO=m

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2408=m
CONFIG_W1_SLAVE_DS2423=m
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=m
CONFIG_W1_SLAVE_DS2780=m
CONFIG_W1_SLAVE_DS2781=m
CONFIG_W1_SLAVE_DS28E04=m
CONFIG_W1_SLAVE_BQ27000=m
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_PDA_POWER=m
CONFIG_TEST_POWER=m
CONFIG_BATTERY_DS2760=m
CONFIG_BATTERY_DS2780=m
CONFIG_BATTERY_DS2781=m
CONFIG_BATTERY_DS2782=m
CONFIG_BATTERY_SBS=m
CONFIG_BATTERY_BQ27x00=m
# CONFIG_BATTERY_BQ27X00_I2C is not set
CONFIG_BATTERY_BQ27X00_PLATFORM=y
CONFIG_BATTERY_MAX17040=m
CONFIG_BATTERY_MAX17042=m
CONFIG_CHARGER_PCF50633=m
CONFIG_CHARGER_ISP1704=m
CONFIG_CHARGER_MAX8903=m
CONFIG_CHARGER_LP8727=m
CONFIG_CHARGER_GPIO=m
CONFIG_CHARGER_SMB347=m
# CONFIG_POWER_AVS is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7314=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_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DA9052_ADC=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_GPIO_FAN=m
CONFIG_SENSORS_HIH6130=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
CONFIG_SENSORS_LINEAGE=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=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_LTC4151=m
CONFIG_SENSORS_LTC4215=m
CONFIG_SENSORS_LTC4245=m
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_MCP3021=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_PMBUS=m
CONFIG_SENSORS_PMBUS=m
CONFIG_SENSORS_ADM1275=m
CONFIG_SENSORS_LM25066=m
CONFIG_SENSORS_LTC2978=m
CONFIG_SENSORS_MAX16064=m
CONFIG_SENSORS_MAX34440=m
CONFIG_SENSORS_MAX8688=m
CONFIG_SENSORS_UCD9000=m
CONFIG_SENSORS_UCD9200=m
CONFIG_SENSORS_ZL6100=m
CONFIG_SENSORS_SHT15=m
CONFIG_SENSORS_SHT21=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_SMM665=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
# CONFIG_SENSORS_SCH56XX_COMMON is not set
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
CONFIG_SENSORS_INA2XX=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA_CPUTEMP=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_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_MC13783_ADC=m

#
# ACPI drivers
#
CONFIG_SENSORS_ACPI_POWER=m
CONFIG_SENSORS_ATK0110=m
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
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_SDIOHOST_POSSIBLE=y
CONFIG_SSB_SDIOHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
CONFIG_BCMA_POSSIBLE=y

#
# Broadcom specific AMBA
#
CONFIG_BCMA=m
CONFIG_BCMA_BLOCKIO=y
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
# CONFIG_BCMA_HOST_PCI is not set
CONFIG_BCMA_DRIVER_GMAC_CMN=y
# CONFIG_BCMA_DEBUG is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_88PM860X is not set
CONFIG_MFD_88PM800=m
CONFIG_MFD_88PM805=m
CONFIG_MFD_SM501=m
# CONFIG_MFD_SM501_GPIO is not set
CONFIG_HTC_PASIC3=m
# CONFIG_HTC_I2CPLD is not set
CONFIG_UCB1400_CORE=m
CONFIG_MFD_LM3533=m
CONFIG_TPS6105X=m
CONFIG_TPS65010=m
CONFIG_TPS6507X=m
CONFIG_MFD_TPS65217=m
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
CONFIG_PMIC_DA9052=y
CONFIG_MFD_DA9052_SPI=y
CONFIG_MFD_DA9052_I2C=y
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX77686 is not set
CONFIG_MFD_MAX77693=y
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_SEC_CORE is not set
CONFIG_MFD_ARIZONA=y
CONFIG_MFD_ARIZONA_I2C=m
CONFIG_MFD_ARIZONA_SPI=m
# CONFIG_MFD_WM5102 is not set
# CONFIG_MFD_WM5110 is not set
CONFIG_MFD_WM8400=y
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
CONFIG_MFD_PCF50633=m
CONFIG_PCF50633_ADC=m
CONFIG_PCF50633_GPIO=m
CONFIG_MFD_MC13783=m
CONFIG_MFD_MC13XXX=m
CONFIG_MFD_MC13XXX_SPI=m
CONFIG_MFD_MC13XXX_I2C=m
# CONFIG_ABX500_CORE is not set
CONFIG_EZX_PCAP=y
CONFIG_MFD_CS5535=m
CONFIG_MFD_TIMBERDALE=m
CONFIG_LPC_SCH=m
CONFIG_LPC_ICH=m
CONFIG_MFD_RDC321X=m
CONFIG_MFD_JANZ_CMODIO=m
CONFIG_MFD_VX855=m
CONFIG_MFD_WL1273_CORE=m
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_PALMAS is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_DUMMY is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=m
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
CONFIG_REGULATOR_GPIO=m
# CONFIG_REGULATOR_AD5398 is not set
CONFIG_REGULATOR_ARIZONA=m
CONFIG_REGULATOR_DA9052=m
# CONFIG_REGULATOR_MC13783 is not set
# CONFIG_REGULATOR_MC13892 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_PCAP is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_PCF50633 is not set
CONFIG_REGULATOR_TPS6105X=m
CONFIG_REGULATOR_TPS62360=m
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
CONFIG_REGULATOR_TPS65217=m
# CONFIG_REGULATOR_TPS6524X is not set
# CONFIG_REGULATOR_WM8400 is not set
CONFIG_MEDIA_SUPPORT=m

#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_MEDIA_RC_SUPPORT=y
# CONFIG_MEDIA_CONTROLLER is not set
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_DVB_CORE=m
CONFIG_DVB_NET=y

#
# Media drivers
#
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_RC_CORE=m
CONFIG_RC_MAP=m
CONFIG_RC_DECODERS=y
CONFIG_LIRC=m
CONFIG_IR_LIRC_CODEC=m
CONFIG_IR_NEC_DECODER=m
CONFIG_IR_RC5_DECODER=m
CONFIG_IR_RC6_DECODER=m
CONFIG_IR_JVC_DECODER=m
CONFIG_IR_SONY_DECODER=m
CONFIG_IR_RC5_SZ_DECODER=m
CONFIG_IR_SANYO_DECODER=m
CONFIG_IR_MCE_KBD_DECODER=m
CONFIG_RC_DEVICES=y
CONFIG_RC_ATI_REMOTE=m
CONFIG_IR_ENE=m
CONFIG_IR_IMON=m
CONFIG_IR_MCEUSB=m
CONFIG_IR_ITE_CIR=m
CONFIG_IR_FINTEK=m
CONFIG_IR_NUVOTON=m
CONFIG_IR_REDRAT3=m
CONFIG_IR_STREAMZAP=m
CONFIG_IR_WINBOND_CIR=m
CONFIG_IR_IGUANA=m
CONFIG_RC_LOOPBACK=m
CONFIG_IR_GPIO_CIR=m
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=m
# CONFIG_MEDIA_TUNER_CUSTOMISE 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_MT2063=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_XC4000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MXL5007T=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_MEDIA_TUNER_MAX2165=m
CONFIG_MEDIA_TUNER_TDA18218=m
CONFIG_MEDIA_TUNER_FC0011=m
CONFIG_MEDIA_TUNER_FC0012=m
CONFIG_MEDIA_TUNER_FC0013=m
CONFIG_MEDIA_TUNER_TDA18212=m
CONFIG_MEDIA_TUNER_TUA9001=m
CONFIG_VIDEO_V4L2=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_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_DMA_CONTIG=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_IR_I2C=m

#
# Audio decoders, processors and mixers
#
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS5345=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m

#
# RDS decoders
#
CONFIG_VIDEO_SAA6588=m

#
# Video decoders
#
CONFIG_VIDEO_ADV7180=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_VPX3220=m

#
# Video and audio decoders
#
CONFIG_VIDEO_SAA717X=m
CONFIG_VIDEO_CX25840=m

#
# MPEG video encoders
#
CONFIG_VIDEO_CX2341X=m

#
# Video encoders
#
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m

#
# Camera sensor devices
#
CONFIG_VIDEO_OV7670=m

#
# Flash devices
#

#
# Video improvement chips
#
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m

#
# Miscelaneous helper chips
#
CONFIG_VIDEO_M52790=m
# CONFIG_VIDEO_VIVI is not set
CONFIG_V4L_USB_DRIVERS=y

#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_BENQ=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_CPIA1=m
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_JL2005BCD=m
CONFIG_USB_GSPCA_KINECT=m
CONFIG_USB_GSPCA_KONICA=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_NW80X=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_OV534_9=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7302=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SE401=m
CONFIG_USB_GSPCA_SN9C2028=m
CONFIG_USB_GSPCA_SN9C20X=m
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SPCA1528=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_SQ930X=m
CONFIG_USB_GSPCA_STK014=m
CONFIG_USB_GSPCA_STV0680=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TOPRO=m
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_VICAM=m
CONFIG_USB_GSPCA_XIRLINK_CIT=m
CONFIG_USB_GSPCA_ZC3XX=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_VIDEO_CPIA2 is not set
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
CONFIG_USB_SN9C102=m

#
# Webcam and/or TV USB devices
#
# CONFIG_VIDEO_EM28XX is not set

#
# TV USB devices
#
CONFIG_VIDEO_AU0828=m
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
CONFIG_VIDEO_TLG2300=m
CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_RC=y
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
# CONFIG_VIDEO_TM6000 is not set
CONFIG_VIDEO_USBVISION=m
CONFIG_V4L_PCI_DRIVERS=y
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_CX18=m
CONFIG_VIDEO_CX18_ALSA=m
CONFIG_VIDEO_CX23885=m
CONFIG_MEDIA_ALTERA_CI=m
# CONFIG_VIDEO_CX25821 is not set
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_CX88_MPEG=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_FB_IVTV=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_RC=y
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_SAA7164=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_V4L_ISA_PARPORT_DRIVERS is not set
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_VIDEO_CAFE_CCIC=m
CONFIG_VIDEO_VIA_CAMERA=m
CONFIG_VIDEO_TIMBERDALE=m
CONFIG_SOC_CAMERA=m
CONFIG_SOC_CAMERA_IMX074=m
CONFIG_SOC_CAMERA_MT9M001=m
CONFIG_SOC_CAMERA_MT9M111=m
CONFIG_SOC_CAMERA_MT9T031=m
CONFIG_SOC_CAMERA_MT9T112=m
CONFIG_SOC_CAMERA_MT9V022=m
CONFIG_SOC_CAMERA_RJ54N1=m
CONFIG_SOC_CAMERA_TW9910=m
CONFIG_SOC_CAMERA_PLATFORM=m
CONFIG_SOC_CAMERA_OV2640=m
CONFIG_SOC_CAMERA_OV5642=m
CONFIG_SOC_CAMERA_OV6650=m
CONFIG_SOC_CAMERA_OV772X=m
CONFIG_SOC_CAMERA_OV9640=m
CONFIG_SOC_CAMERA_OV9740=m
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_TESTDEV is not set
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_SI470X=y
CONFIG_USB_SI470X=m
CONFIG_I2C_SI470X=m
CONFIG_USB_MR800=m
CONFIG_USB_DSBR=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_SHARK=m
CONFIG_RADIO_SHARK2=m
CONFIG_I2C_SI4713=m
CONFIG_RADIO_SI4713=m
CONFIG_USB_KEENE=m
CONFIG_RADIO_TEA5764=m
CONFIG_RADIO_SAA7706H=m
CONFIG_RADIO_TEF6862=m
CONFIG_RADIO_TIMBERDALE=m
CONFIG_RADIO_WL1273=m

#
# Texas Instruments WL128x FM driver (ST based)
#
CONFIG_RADIO_WL128X=m
CONFIG_DVB_MAX_ADAPTERS=8
# CONFIG_DVB_DYNAMIC_MINORS is not set
CONFIG_DVB_CAPTURE_DRIVERS=y

#
# Supported SAA7146 based PCI Adapters
#
CONFIG_TTPCI_EEPROM=m
CONFIG_DVB_AV7110=m
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_PCTV452E=m
CONFIG_DVB_USB_DW2102=m
CONFIG_DVB_USB_CINERGY_T2=m
CONFIG_DVB_USB_ANYSEE=m
CONFIG_DVB_USB_DTV5100=m
CONFIG_DVB_USB_AF9015=m
CONFIG_DVB_USB_CE6230=m
CONFIG_DVB_USB_FRIIO=m
CONFIG_DVB_USB_EC168=m
CONFIG_DVB_USB_AZ6007=m
CONFIG_DVB_USB_AZ6027=m
CONFIG_DVB_USB_LME2510=m
CONFIG_DVB_USB_TECHNISAT_USB2=m
CONFIG_DVB_USB_IT913X=m
CONFIG_DVB_USB_MXL111SF=m
CONFIG_DVB_USB_RTL28XXU=m
CONFIG_DVB_USB_AF9035=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_SMS_SIANO_MDTV=m

#
# Siano module components
#
CONFIG_SMS_USB_DRV=m
CONFIG_SMS_SDIO_DRV=m

#
# 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 SDMC DM1105 Adapters
#
CONFIG_DVB_DM1105=m

#
# Supported Earthsoft PT1 Adapters
#
CONFIG_DVB_PT1=m

#
# Supported Mantis Adapters
#
CONFIG_MANTIS_CORE=m
CONFIG_DVB_MANTIS=m
CONFIG_DVB_HOPPER=m

#
# Supported nGene Adapters
#
CONFIG_DVB_NGENE=m

#
# Supported ddbridge ('Octopus') Adapters
#
CONFIG_DVB_DDBRIDGE=m

#
# Supported DVB Frontends
#

#
# Multistandard (satellite) frontends
#
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=m
CONFIG_DVB_STV6110x=m

#
# Multistandard (cable + terrestrial) frontends
#
CONFIG_DVB_DRXK=m
CONFIG_DVB_TDA18271C2DD=m

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_MT312=m
CONFIG_DVB_ZL10036=m
CONFIG_DVB_ZL10039=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TUNER_ITD1000=m
CONFIG_DVB_TUNER_CX24113=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_SI21XX=m
CONFIG_DVB_DS3000=m
CONFIG_DVB_MB86A16=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=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
CONFIG_DVB_AF9013=m
CONFIG_DVB_EC100=m
CONFIG_DVB_STV0367=m
CONFIG_DVB_CXD2820R=m
CONFIG_DVB_RTL2830=m
CONFIG_DVB_RTL2832=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_LGDT3305=m
CONFIG_DVB_LG2160=m
CONFIG_DVB_S5H1409=m
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m
CONFIG_DVB_S5H1411=m

#
# ISDB-T (terrestrial) frontends
#
CONFIG_DVB_DIB8000=m
CONFIG_DVB_MB86A20S=m

#
# Digital terrestrial only tuners/PLL
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TUNER_DIB0070=m
CONFIG_DVB_TUNER_DIB0090=m

#
# SEC control devices for DVB-S
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_LNBP22=m
CONFIG_DVB_ISL6405=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_ISL6423=m
CONFIG_DVB_LGS8GXX=m
CONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=m
CONFIG_DVB_IX2505V=m
CONFIG_DVB_IT913X_FE=m
CONFIG_DVB_M88RS2000=m
CONFIG_DVB_AF9033=m

#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set

#
# Graphics support
#
CONFIG_AGP=m
CONFIG_AGP_AMD64=m
CONFIG_AGP_INTEL=m
CONFIG_AGP_SIS=m
CONFIG_AGP_VIA=m
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
CONFIG_VGA_SWITCHEROO=y
CONFIG_DRM=m
CONFIG_DRM_USB=m
CONFIG_DRM_KMS_HELPER=m
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_DRM_TTM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_NOUVEAU is not set

#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
CONFIG_DRM_I915=m
# CONFIG_DRM_I915_KMS is not set
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
# CONFIG_DRM_VIA is not set
CONFIG_DRM_SAVAGE=m
# CONFIG_DRM_VMWGFX is not set
CONFIG_DRM_GMA500=m
# CONFIG_DRM_GMA600 is not set
# CONFIG_DRM_GMA3600 is not set
CONFIG_DRM_UDL=m
# CONFIG_DRM_AST is not set
CONFIG_DRM_MGAG200=m
CONFIG_DRM_CIRRUS_QEMU=m
# CONFIG_STUB_POULSBO is not set
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
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_WMT_GE_ROPS is not set
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_HECUBA=m
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=y
CONFIG_FB_VESA=y
CONFIG_FB_N411=m
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_I740=m
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
CONFIG_FB_S3=m
CONFIG_FB_S3_DDC=y
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
CONFIG_FB_VIA=m
# CONFIG_FB_VIA_DIRECT_PROCFS is not set
# CONFIG_FB_VIA_X_COMPATIBILITY is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
CONFIG_FB_VT8623=m
# CONFIG_FB_TRIDENT is not set
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 is not set
CONFIG_FB_TMIO=m
CONFIG_FB_TMIO_ACCELL=y
CONFIG_FB_SM501=m
CONFIG_FB_SMSCUFX=m
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_METRONOME=m
CONFIG_FB_MB862XX=m
CONFIG_FB_MB862XX_PCI_GDC=y
CONFIG_FB_MB862XX_I2C=y
CONFIG_FB_BROADSHEET=m
CONFIG_FB_AUO_K190X=m
CONFIG_FB_AUO_K1900=m
CONFIG_FB_AUO_K1901=m
# CONFIG_EXYNOS_VIDEO is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_L4F00242T03=m
CONFIG_LCD_LMS283GF05=m
CONFIG_LCD_LTV350QV=m
CONFIG_LCD_ILI9320=m
CONFIG_LCD_TDO24M=m
CONFIG_LCD_VGG2432A4=m
CONFIG_LCD_PLATFORM=m
CONFIG_LCD_S6E63M0=m
CONFIG_LCD_LD9040=m
CONFIG_LCD_AMS369FG06=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=m
CONFIG_BACKLIGHT_LM3533=m
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_CARILLO_RANCH=m
CONFIG_BACKLIGHT_PWM=m
CONFIG_BACKLIGHT_DA9052=m
CONFIG_BACKLIGHT_APPLE=m
CONFIG_BACKLIGHT_SAHARA=m
CONFIG_BACKLIGHT_ADP8860=m
CONFIG_BACKLIGHT_ADP8870=m
CONFIG_BACKLIGHT_PCF50633=m
CONFIG_BACKLIGHT_LP855X=m
CONFIG_BACKLIGHT_OT200=m

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
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_HRTIMER=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_KCTL_JACK=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_OPL3_LIB_SEQ=m
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
CONFIG_SND_EMU10K1_SEQ=m
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_ALOOP=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 is not set
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB16_DSP=m
CONFIG_SND_TEA575X=m
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ASIHPI=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=m
CONFIG_SND_CS5535AUDIO=m
CONFIG_SND_CTXFI=m
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_INDIGOIOX=m
CONFIG_SND_INDIGODJX=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_ES1968_INPUT=y
CONFIG_SND_ES1968_RADIO=y
CONFIG_SND_FM801=m
# CONFIG_SND_FM801_TEA575X_BOOL is not set
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=1
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_PATCH_LOADER=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_HDMI=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CA0132=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
# CONFIG_SND_HDA_POWER_SAVE is not set
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_LOLA=m
CONFIG_SND_LX6464ES=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MAESTRO3_INPUT=y
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 is not set
# CONFIG_SND_VIA82XX_MODEM is not set
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_UA101=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=m
CONFIG_SND_USB_6FIRE=m
CONFIG_SND_PCMCIA=y
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m
CONFIG_SND_SOC=m
CONFIG_SND_SOC_I2C_AND_SPI=m
CONFIG_SND_SOC_ALL_CODECS=m
CONFIG_SND_SOC_WM_HUBS=m
CONFIG_SND_SOC_AD1836=m
CONFIG_SND_SOC_AD193X=m
CONFIG_SND_SOC_AD73311=m
CONFIG_SND_SOC_ADAU1373=m
CONFIG_SND_SOC_ADAV80X=m
CONFIG_SND_SOC_ADS117X=m
CONFIG_SND_SOC_AK4104=m
CONFIG_SND_SOC_AK4535=m
CONFIG_SND_SOC_AK4641=m
CONFIG_SND_SOC_AK4642=m
CONFIG_SND_SOC_AK4671=m
CONFIG_SND_SOC_ALC5623=m
CONFIG_SND_SOC_ALC5632=m
CONFIG_SND_SOC_CS42L51=m
CONFIG_SND_SOC_CS42L52=m
CONFIG_SND_SOC_CS42L73=m
CONFIG_SND_SOC_CS4270=m
CONFIG_SND_SOC_CS4271=m
CONFIG_SND_SOC_CX20442=m
CONFIG_SND_SOC_JZ4740_CODEC=m
CONFIG_SND_SOC_L3=m
CONFIG_SND_SOC_DA7210=m
CONFIG_SND_SOC_DA732X=m
CONFIG_SND_SOC_DFBMCS320=m
CONFIG_SND_SOC_ISABELLE=m
CONFIG_SND_SOC_LM49453=m
CONFIG_SND_SOC_MAX98088=m
CONFIG_SND_SOC_MAX98095=m
CONFIG_SND_SOC_MAX9850=m
CONFIG_SND_SOC_PCM3008=m
CONFIG_SND_SOC_RT5631=m
CONFIG_SND_SOC_SGTL5000=m
CONFIG_SND_SOC_SPDIF=m
CONFIG_SND_SOC_SSM2602=m
CONFIG_SND_SOC_STA32X=m
CONFIG_SND_SOC_STA529=m
CONFIG_SND_SOC_TLV320AIC23=m
CONFIG_SND_SOC_TLV320AIC26=m
CONFIG_SND_SOC_TLV320AIC32X4=m
CONFIG_SND_SOC_TLV320AIC3X=m
CONFIG_SND_SOC_TLV320DAC33=m
CONFIG_SND_SOC_UDA134X=m
CONFIG_SND_SOC_UDA1380=m
CONFIG_SND_SOC_WL1273=m
CONFIG_SND_SOC_WM1250_EV1=m
CONFIG_SND_SOC_WM2000=m
CONFIG_SND_SOC_WM2200=m
CONFIG_SND_SOC_WM5100=m
CONFIG_SND_SOC_WM8400=m
CONFIG_SND_SOC_WM8510=m
CONFIG_SND_SOC_WM8523=m
CONFIG_SND_SOC_WM8580=m
CONFIG_SND_SOC_WM8711=m
CONFIG_SND_SOC_WM8727=m
CONFIG_SND_SOC_WM8728=m
CONFIG_SND_SOC_WM8731=m
CONFIG_SND_SOC_WM8737=m
CONFIG_SND_SOC_WM8741=m
CONFIG_SND_SOC_WM8750=m
CONFIG_SND_SOC_WM8753=m
CONFIG_SND_SOC_WM8770=m
CONFIG_SND_SOC_WM8776=m
CONFIG_SND_SOC_WM8782=m
CONFIG_SND_SOC_WM8804=m
CONFIG_SND_SOC_WM8900=m
CONFIG_SND_SOC_WM8903=m
CONFIG_SND_SOC_WM8904=m
CONFIG_SND_SOC_WM8940=m
CONFIG_SND_SOC_WM8955=m
CONFIG_SND_SOC_WM8960=m
CONFIG_SND_SOC_WM8961=m
CONFIG_SND_SOC_WM8962=m
CONFIG_SND_SOC_WM8971=m
CONFIG_SND_SOC_WM8974=m
CONFIG_SND_SOC_WM8978=m
CONFIG_SND_SOC_WM8983=m
CONFIG_SND_SOC_WM8985=m
CONFIG_SND_SOC_WM8988=m
CONFIG_SND_SOC_WM8990=m
CONFIG_SND_SOC_WM8991=m
CONFIG_SND_SOC_WM8993=m
CONFIG_SND_SOC_WM8995=m
CONFIG_SND_SOC_WM8996=m
CONFIG_SND_SOC_WM9081=m
CONFIG_SND_SOC_WM9090=m
CONFIG_SND_SOC_LM4857=m
CONFIG_SND_SOC_MAX9768=m
CONFIG_SND_SOC_MAX9877=m
CONFIG_SND_SOC_MC13783=m
CONFIG_SND_SOC_ML26124=m
CONFIG_SND_SOC_TPA6130A2=m
CONFIG_SND_SIMPLE_CARD=m
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m

#
# HID support
#
CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
CONFIG_HIDRAW=y
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=m

#
# Special HID drivers
#
CONFIG_HID_A4TECH=m
CONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not set
CONFIG_HID_APPLE=m
CONFIG_HID_AUREAL=m
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_PRODIKEYS=m
CONFIG_HID_CYPRESS=m
CONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
CONFIG_HID_EMS_FF=m
CONFIG_HID_ELECOM=m
CONFIG_HID_EZKEY=m
CONFIG_HID_HOLTEK=m
# CONFIG_HOLTEK_FF is not set
CONFIG_HID_KEYTOUCH=m
CONFIG_HID_KYE=m
CONFIG_HID_UCLOGIC=m
CONFIG_HID_WALTOP=m
CONFIG_HID_GYRATION=m
CONFIG_HID_TWINHAN=m
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LCPOWER=m
CONFIG_HID_LENOVO_TPKBD=m
CONFIG_HID_LOGITECH=m
CONFIG_HID_LOGITECH_DJ=m
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
# CONFIG_LOGIG940_FF is not set
CONFIG_LOGIWHEELS_FF=y
CONFIG_HID_MAGICMOUSE=m
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
CONFIG_HID_MULTITOUCH=m
CONFIG_HID_NTRIG=m
CONFIG_HID_ORTEK=m
CONFIG_HID_PANTHERLORD=m
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=m
CONFIG_HID_PICOLCD=m
CONFIG_HID_PICOLCD_FB=y
CONFIG_HID_PICOLCD_BACKLIGHT=y
CONFIG_HID_PICOLCD_LCD=y
CONFIG_HID_PICOLCD_LEDS=y
CONFIG_HID_PRIMAX=m
CONFIG_HID_ROCCAT=m
CONFIG_HID_SAITEK=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_HID_SPEEDLINK=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not set
CONFIG_HID_TIVO=m
CONFIG_HID_TOPSEED=m
CONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
CONFIG_HID_WACOM=m
CONFIG_HID_WIIMOTE=m
CONFIG_HID_WIIMOTE_EXT=y
CONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not set
CONFIG_HID_ZYDACRON=m

#
# USB HID support
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=m
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_DWC3=m
# CONFIG_USB_DWC3_DEBUG is not set
# CONFIG_USB_MON is not set
CONFIG_USB_WUSB=m
CONFIG_USB_WUSB_CBAF=m
# CONFIG_USB_WUSB_CBAF_DEBUG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_C67X00_HCD=m
CONFIG_USB_XHCI_HCD=m
CONFIG_USB_XHCI_PLATFORM=m
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
CONFIG_USB_OXU210HP_HCD=m
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_ISP1760_HCD=m
CONFIG_USB_ISP1362_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_HCD_SSB is not set
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_SL811_HCD_ISO is not set
CONFIG_USB_SL811_CS=m
CONFIG_USB_R8A66597_HCD=m
CONFIG_USB_RENESAS_USBHS_HCD=m
CONFIG_USB_WHCI_HCD=m
CONFIG_USB_HWA_HCD=m
CONFIG_USB_HCD_BCMA=m
CONFIG_USB_HCD_SSB=m
CONFIG_USB_MUSB_HDRC=m
CONFIG_USB_MUSB_TUSB6010=m
CONFIG_MUSB_PIO_ONLY=y
CONFIG_USB_CHIPIDEA=m
CONFIG_USB_CHIPIDEA_UDC=y
CONFIG_USB_CHIPIDEA_HOST=y
# CONFIG_USB_CHIPIDEA_DEBUG is not set
CONFIG_USB_RENESAS_USBHS=m

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
CONFIG_USB_TMC=m

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
CONFIG_USB_UAS=m
CONFIG_USB_LIBUSUAL=y

#
# 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_CP210X=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 is not set
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_F81232=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 is not set
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_METRO=m
CONFIG_USB_SERIAL_MOS7720=m
# CONFIG_USB_SERIAL_MOS7715_PARPORT is not set
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_QCAUX=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_SIEMENS_MPI=m
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_SYMBOL=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_VIVOPAY_SERIAL=m
CONFIG_USB_SERIAL_ZIO=m
CONFIG_USB_SERIAL_SSU100=m
CONFIG_USB_SERIAL_QT2=m
CONFIG_USB_SERIAL_DEBUG=m

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_SEVSEG=m
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=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_YUREX=m

#
# USB Physical Layer drivers
#
CONFIG_USB_ISP1301=m
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
CONFIG_USB_GADGET=m
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2

#
# USB Peripheral Controller
#
CONFIG_USB_R8A66597=m
CONFIG_USB_RENESAS_USBHS_UDC=m
CONFIG_USB_MV_UDC=m
CONFIG_USB_GADGET_MUSB_HDRC=m
CONFIG_USB_M66592=m
CONFIG_USB_AMD5536UDC=m
CONFIG_USB_NET2272=m
CONFIG_USB_NET2272_DMA=y
CONFIG_USB_NET2280=m
CONFIG_USB_GOKU=m
CONFIG_USB_EG20T=m
CONFIG_USB_DUMMY_HCD=m
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_GADGET_SUPERSPEED=y
CONFIG_USB_ZERO=m
CONFIG_USB_AUDIO=m
# CONFIG_GADGET_UAC1 is not set
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
# CONFIG_USB_ETH_EEM is not set
CONFIG_USB_G_NCM=m
CONFIG_USB_GADGETFS=m
CONFIG_USB_FUNCTIONFS=m
# CONFIG_USB_FUNCTIONFS_ETH is not set
CONFIG_USB_FUNCTIONFS_RNDIS=y
CONFIG_USB_FUNCTIONFS_GENERIC=y
CONFIG_USB_FILE_STORAGE=m
CONFIG_USB_FILE_STORAGE_TEST=y
CONFIG_USB_MASS_STORAGE=m
CONFIG_USB_GADGET_TARGET=m
CONFIG_USB_G_SERIAL=m
CONFIG_USB_MIDI_GADGET=m
CONFIG_USB_G_PRINTER=m
CONFIG_USB_CDC_COMPOSITE=m
CONFIG_USB_G_NOKIA=m
CONFIG_USB_G_ACM_MS=m
CONFIG_USB_G_MULTI=m
CONFIG_USB_G_MULTI_RNDIS=y
CONFIG_USB_G_MULTI_CDC=y
CONFIG_USB_G_HID=m
CONFIG_USB_G_DBGP=m
# CONFIG_USB_G_DBGP_PRINTK is not set
CONFIG_USB_G_DBGP_SERIAL=y
CONFIG_USB_G_WEBCAM=m

#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
CONFIG_USB_GPIO_VBUS=m
CONFIG_NOP_USB_XCEIV=m
CONFIG_UWB=y
CONFIG_UWB_HWA=m
CONFIG_UWB_WHCI=m
CONFIG_UWB_I1480U=m
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
# CONFIG_MMC_CLKGATE is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=y
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_SPI=m
CONFIG_MMC_SDRICOH_CS=m
CONFIG_MMC_CB710=m
CONFIG_MMC_VIA_SDMMC=m
CONFIG_MMC_VUB300=m
CONFIG_MMC_USHC=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_MEMSTICK_R592=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#
CONFIG_LEDS_LM3530=m
CONFIG_LEDS_LM3533=m
CONFIG_LEDS_PCA9532=m
# CONFIG_LEDS_PCA9532_GPIO is not set
CONFIG_LEDS_GPIO=m
CONFIG_LEDS_LP3944=m
CONFIG_LEDS_LP5521=m
CONFIG_LEDS_LP5523=m
CONFIG_LEDS_CLEVO_MAIL=m
CONFIG_LEDS_PCA955X=m
CONFIG_LEDS_PCA9633=m
CONFIG_LEDS_DA9052=m
CONFIG_LEDS_DAC124S085=m
CONFIG_LEDS_REGULATOR=m
CONFIG_LEDS_BD2802=m
CONFIG_LEDS_INTEL_SS4200=m
CONFIG_LEDS_LT3593=m
CONFIG_LEDS_DELL_NETBOOKS=m
CONFIG_LEDS_MC13783=m
CONFIG_LEDS_TCA6507=m
CONFIG_LEDS_LM3556=m
CONFIG_LEDS_OT200=m
CONFIG_LEDS_BLINKM=m
CONFIG_LEDS_TRIGGERS=y

#
# LED Triggers
#
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_ONESHOT=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_GPIO=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m

#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_LEDS_TRIGGER_TRANSIENT=m
CONFIG_ACCESSIBILITY=y
CONFIG_A11Y_BRAILLE_CONSOLE=y
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_QIB=m
CONFIG_INFINIBAND_AMSO1100=m
# CONFIG_INFINIBAND_AMSO1100_DEBUG is not set
CONFIG_INFINIBAND_CXGB3=m
# CONFIG_INFINIBAND_CXGB3_DEBUG is not set
CONFIG_INFINIBAND_CXGB4=m
CONFIG_MLX4_INFINIBAND=m
CONFIG_INFINIBAND_NES=m
# CONFIG_INFINIBAND_NES_DEBUG is not set
CONFIG_INFINIBAND_OCRDMA=m
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_CM is not set
CONFIG_INFINIBAND_IPOIB_DEBUG=y
# CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_SRPT=m
CONFIG_INFINIBAND_ISER=m
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set

#
# DMA Devices
#
CONFIG_INTEL_MID_DMAC=m
CONFIG_INTEL_IOATDMA=m
CONFIG_TIMB_DMA=m
CONFIG_PCH_DMA=m
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
CONFIG_DCA=m
CONFIG_AUXDISPLAY=y
CONFIG_KS0108=m
CONFIG_KS0108_PORT=0x378
CONFIG_KS0108_DELAY=2
CONFIG_CFAG12864B=m
CONFIG_CFAG12864B_RATE=20
CONFIG_UIO=m
CONFIG_UIO_CIF=m
CONFIG_UIO_PDRV=m
CONFIG_UIO_PDRV_GENIRQ=m
CONFIG_UIO_AEC=m
CONFIG_UIO_SERCOS3=m
CONFIG_UIO_PCI_GENERIC=m
CONFIG_UIO_NETX=m
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m

#
# Virtio drivers
#
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
CONFIG_VIRTIO_MMIO=m
# CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set

#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
CONFIG_STAGING=y
# CONFIG_ET131X is not set
# CONFIG_SLICOSS is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_W35UND is not set
# CONFIG_PRISM2_USB is not set
# CONFIG_ECHO is not set
# CONFIG_COMEDI is not set
# CONFIG_ASUS_OLED is not set
# CONFIG_PANEL is not set
# CONFIG_R8187SE is not set
# CONFIG_RTL8192U is not set
CONFIG_RTLLIB=m
CONFIG_RTLLIB_CRYPTO_CCMP=m
CONFIG_RTLLIB_CRYPTO_TKIP=m
CONFIG_RTLLIB_CRYPTO_WEP=m
# CONFIG_RTL8192E is not set
# CONFIG_R8712U is not set
# CONFIG_RTS_PSTOR is not set
CONFIG_RTS5139=m
# CONFIG_RTS5139_DEBUG is not set
# CONFIG_TRANZPORT is not set
# CONFIG_IDE_PHISON is not set
# CONFIG_LINE6_USB is not set
# CONFIG_USB_SERIAL_QUATECH2 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
# CONFIG_DX_SEP is not set
# CONFIG_ZSMALLOC is not set
# CONFIG_WLAGS49_H2 is not set
# CONFIG_WLAGS49_H25 is not set
# CONFIG_FB_SM7XX is not set
# CONFIG_CRYSTALHD is not set
# CONFIG_CXT1E1 is not set
# CONFIG_FB_XGI is not set
# CONFIG_ACPI_QUICKSTART is not set
# CONFIG_SBE_2T3E3 is not set
# CONFIG_USB_ENESTORAGE is not set
# CONFIG_BCM_WIMAX is not set
# CONFIG_FT1000 is not set

#
# Speakup console speech
#
CONFIG_SPEAKUP=y
# CONFIG_SPEAKUP_SYNTH_ACNTSA is not set
# CONFIG_SPEAKUP_SYNTH_ACNTPC is not set
# CONFIG_SPEAKUP_SYNTH_APOLLO is not set
# CONFIG_SPEAKUP_SYNTH_AUDPTR is not set
# CONFIG_SPEAKUP_SYNTH_BNS is not set
CONFIG_SPEAKUP_SYNTH_DECTLK=m
# CONFIG_SPEAKUP_SYNTH_DECEXT is not set
# CONFIG_SPEAKUP_SYNTH_DECPC is not set
# CONFIG_SPEAKUP_SYNTH_DTLK is not set
# CONFIG_SPEAKUP_SYNTH_KEYPC is not set
CONFIG_SPEAKUP_SYNTH_LTLK=m
CONFIG_SPEAKUP_SYNTH_SOFT=m
CONFIG_SPEAKUP_SYNTH_SPKOUT=y
# CONFIG_SPEAKUP_SYNTH_TXPRT is not set
# CONFIG_SPEAKUP_SYNTH_DUMMY is not set
CONFIG_TOUCHSCREEN_CLEARPAD_TM1217=m
CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4=m
# CONFIG_STAGING_MEDIA is not set

#
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
# CONFIG_ASHMEM is not set
CONFIG_ANDROID_LOGGER=m
CONFIG_ANDROID_TIMED_OUTPUT=y
CONFIG_ANDROID_TIMED_GPIO=m
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set
# CONFIG_PHONE is not set
CONFIG_USB_WPAN_HCD=m
CONFIG_IPACK_BUS=m
CONFIG_BOARD_TPCI200=m
CONFIG_SERIAL_IPOCTAL=m
CONFIG_WIMAX_GDM72XX=m
CONFIG_WIMAX_GDM72XX_QOS=y
CONFIG_WIMAX_GDM72XX_K_MODE=y
CONFIG_WIMAX_GDM72XX_WIMAX2=y
CONFIG_WIMAX_GDM72XX_USB=y
# CONFIG_WIMAX_GDM72XX_SDIO is not set
CONFIG_CSR_WIFI=m
CONFIG_X86_PLATFORM_DEVICES=y
CONFIG_ACER_WMI=m
CONFIG_ACERHDF=m
CONFIG_ASUS_LAPTOP=m
CONFIG_DELL_LAPTOP=m
CONFIG_DELL_WMI=m
CONFIG_DELL_WMI_AIO=m
CONFIG_FUJITSU_LAPTOP=m
# CONFIG_FUJITSU_LAPTOP_DEBUG is not set
CONFIG_FUJITSU_TABLET=m
CONFIG_AMILO_RFKILL=m
CONFIG_HP_ACCEL=m
CONFIG_HP_WMI=m
# CONFIG_MSI_LAPTOP is not set
CONFIG_PANASONIC_LAPTOP=m
CONFIG_COMPAL_LAPTOP=m
CONFIG_SONY_LAPTOP=m
CONFIG_SONYPI_COMPAT=y
CONFIG_IDEAPAD_LAPTOP=m
CONFIG_THINKPAD_ACPI=m
CONFIG_THINKPAD_ACPI_ALSA_SUPPORT=y
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
CONFIG_SENSORS_HDAPS=m
CONFIG_INTEL_MENLOW=m
CONFIG_ACPI_WMI=m
CONFIG_MSI_WMI=m
CONFIG_TOPSTAR_LAPTOP=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_TOSHIBA_BT_RFKILL=m
CONFIG_ACPI_CMPC=m
CONFIG_INTEL_IPS=m
CONFIG_IBM_RTL=m
CONFIG_XO15_EBOOK=m
# CONFIG_SAMSUNG_LAPTOP is not set
CONFIG_MXM_WMI=m
CONFIG_INTEL_OAKTRAIL=m
CONFIG_SAMSUNG_Q10=m
CONFIG_APPLE_GMUX=m

#
# Hardware Spinlock drivers
#
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
CONFIG_IOMMU_SUPPORT=y
# CONFIG_AMD_IOMMU is not set
# CONFIG_INTEL_IOMMU is not set
# CONFIG_IRQ_REMAP is not set

#
# Remoteproc drivers (EXPERIMENTAL)
#

#
# Rpmsg drivers (EXPERIMENTAL)
#
CONFIG_VIRT_DRIVERS=y
# CONFIG_PM_DEVFREQ is not set
CONFIG_EXTCON=m

#
# Extcon Device Drivers
#
CONFIG_EXTCON_GPIO=m
CONFIG_EXTCON_MAX77693=m
CONFIG_EXTCON_ARIZONA=m
# CONFIG_MEMORY is not set
# CONFIG_IIO is not set
# CONFIG_VME_BUS is not set
CONFIG_PWM=y

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
# CONFIG_GOOGLE_FIRMWARE is not set

#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=m
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
CONFIG_JBD2_DEBUG=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_DLM=y
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_OCFS2_FS_STATS=y
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
# CONFIG_BTRFS_FS is not set
CONFIG_NILFS2_FS=m
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=m
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_QUOTACTL_COMPAT=y
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_CUSE=m
CONFIG_GENERIC_ACL=y

#
# Caches
#
CONFIG_FSCACHE=m
# CONFIG_FSCACHE_STATS is not set
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
CONFIG_FSCACHE_OBJECT_LIST=y
CONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
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 is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
CONFIG_CRAMFS=m
CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
# CONFIG_SQUASHFS_LZO is not set
# CONFIG_SQUASHFS_XZ is not set
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_VXFS_FS is not set
CONFIG_MINIX_FS=m
CONFIG_OMFS_FS=m
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
CONFIG_QNX6FS_FS=m
# CONFIG_QNX6FS_DEBUG is not set
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_PSTORE=y
# CONFIG_PSTORE_CONSOLE is not set
CONFIG_PSTORE_FTRACE=y
CONFIG_PSTORE_RAM=m
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_EXOFS_FS=m
# CONFIG_EXOFS_DEBUG is not set
CONFIG_ORE=m
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=m
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_FSCACHE is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DEBUG=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
# CONFIG_NFSD_FAULT_INJECTION is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_XPRT_RDMA=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_SUNRPC_DEBUG=y
CONFIG_CEPH_FS=m
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_UPCALL is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_DFS_UPCALL is not set
# CONFIG_CIFS_FSCACHE is not set
CONFIG_NCP_FS=m
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
# CONFIG_NCPFS_EXTRAS is not set
CONFIG_CODA_FS=m
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
# CONFIG_AFS_FSCACHE is not set
# CONFIG_9P_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_MAC_ROMAN=m
CONFIG_NLS_MAC_CELTIC=m
CONFIG_NLS_MAC_CENTEURO=m
CONFIG_NLS_MAC_CROATIAN=m
CONFIG_NLS_MAC_CYRILLIC=m
CONFIG_NLS_MAC_GAELIC=m
CONFIG_NLS_MAC_GREEK=m
CONFIG_NLS_MAC_ICELAND=m
CONFIG_NLS_MAC_INUIT=m
CONFIG_NLS_MAC_ROMANIAN=m
CONFIG_NLS_MAC_TURKISH=m
CONFIG_NLS_UTF8=y
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=0
CONFIG_MAGIC_SYSRQ=y
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_READABLE_ASM is not set
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
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_KMEMLEAK is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_LOCK_STAT is not set
CONFIG_TRACE_IRQFLAGS=y
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
CONFIG_RCU_CPU_STALL_VERBOSE=y
CONFIG_RCU_CPU_STALL_INFO=y
# CONFIG_RCU_TRACE is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_LKDTM is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_LATENCYTOP=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACER_MAX_TRACE=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_EVENT_POWER_TRACING_DEPRECATED=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
CONFIG_FUNCTION_TRACER=y
CONFIG_FUNCTION_GRAPH_TRACER=y
CONFIG_IRQSOFF_TRACER=y
# CONFIG_PREEMPT_TRACER is not set
CONFIG_SCHED_TRACER=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_UPROBE_EVENT=y
CONFIG_PROBE_EVENTS=y
CONFIG_DYNAMIC_FTRACE=y
# CONFIG_FUNCTION_PROFILER is not set
CONFIG_FTRACE_MCOUNT_RECORD=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
CONFIG_RING_BUFFER_BENCHMARK=m
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
CONFIG_DYNAMIC_DEBUG=y
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
CONFIG_ASYNC_RAID6_TEST=m
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
CONFIG_TEST_KSTRTOX=m
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_X86_PTDUMP is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_SET_MODULE_RONX is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_DEBUG_TLBFLUSH is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
# CONFIG_DEBUG_NMI_SELFTEST is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_TRUSTED_KEYS is not set
CONFIG_ENCRYPTED_KEYS=m
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_SECURITY is not set
CONFIG_SECURITYFS=y
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y
CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=m
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_USER=m
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_PCRYPT=m
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=m
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_ABLK_HELPER_X86=m
CONFIG_CRYPTO_GLUE_HELPER_X86=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
CONFIG_CRYPTO_VMAC=m

#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CRC32C_INTEL=m
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
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_SHA1_SSSE3=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_AES_NI_INTEL=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_BLOWFISH_COMMON=m
CONFIG_CRYPTO_BLOWFISH_X86_64=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAMELLIA_X86_64=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=y
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_SERPENT_SSE2_X86_64=m
CONFIG_CRYPTO_SERPENT_AVX_X86_64=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_X86_64=m
CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m
CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_ZLIB=m
CONFIG_CRYPTO_LZO=m

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_USER_API=m
CONFIG_CRYPTO_USER_API_HASH=m
CONFIG_CRYPTO_USER_API_SKCIPHER=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_HAVE_KVM_MSI=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
# CONFIG_KVM_MMU_AUDIT is not set
CONFIG_VHOST_NET=m
CONFIG_TCM_VHOST=m
CONFIG_BINARY_PRINTF=y

#
# Library routines
#
CONFIG_RAID6_PQ=m
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_T10DIF=m
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_CRC8=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
CONFIG_XZ_DEC_TEST=m
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_ENC8=y
CONFIG_REED_SOLOMON_DEC8=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_BTREE=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_NLATTR=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
CONFIG_LRU_CACHE=m
CONFIG_AVERAGE=y
CONFIG_CORDIC=m
# CONFIG_DDR is not set


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Fri, May 16, 2014 at 12:17 PM,  <covici@ccs.covici.com> wrote:
[snip]
>> I don't understand the current situation .So now you get ALL your
>> volumes activated, or not?
>
> Yep, they are all activated and they all get mounted.

Cool, one problem less.

>> > Now for some systemd problems.  The root file system was read only when
>> > I logged in, but I could remount it rw -- not sure why this was
>> > happening.
>>
>> Set systemd.log_level=debug in your command line, and post the exit
>> from journalctl -b.
>
> I had debug in the command line by itself, would that make the correct
> log_level?  The file is quite large, should I send it to you privately?

I don't think is necessary, I may have found the real problem (see below).

>> >  Some units did start, but most did not.  Whenever I tried to
>> > start one manually, I got a message like the following:
[snip]
>> > No matter what unit I tried to start I would get such a  message about
>> > the service.mount.
>>
>> That sounds like a problem with the cgroups hierarchy (which uses a
>> virtual filesystem). I don't remember seeing a problem like that
>> before.
>>
>> > Also, even though my network names were correct, they did not come up,
>> > but I will try to look in the logs to see why not.
> I wrote a service file to start my network adaptors, here it is:
> network@.service
>
>
> [Unit]
> Description=Network Connectivity for %i
> Wants=network.target
> Before=network.target
> BindsTo=sys-subsystem-net-devices-%i.device
> After=sys-subsystem-net-devices-%i.device
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> EnvironmentFile=/etc/conf.d/network@%i
> ExecStart=/usr/bin/ip link set dev %i up
> ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
> ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
> ${gateway}'
> ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
> ExecStop=/usr/bin/ip addr flush dev %i
> ExecStop=/usr/bin/ip link set dev %i down
> [Install]
> WantedBy=network.target

Did you enabled network@ifaca.service? Also, WantedBy=network.target
doesn't do what you probably think it does (check [1]... and BTW, I
forgot my last footnote, is now on [2]).

I would use WantedBy=multi-user.target.

>> systemd will not (AFAIK) start your network, and before the 209 or 210
>> version it needed helper program (NetwokrManager, connman, ip,
>> ifconfig, etc.) to do it. Now it includes networkd, but you need to
>> set up .network files (like .service files) to configure it. See [1].
>>
>> > So we have made some progress, but still a long way to go yet.  Note
>> > also, that I am not booting into a display manager, just a regular
>> > console.
>> >
>> >
>> > What a lot of work just to get the system booted!
>>
>> Well, you have a setup that is not, by any means, simple. Also, in my
>> experience old LVM configurations seem to cause a lot of troubles to
>> bring to what systemd expects.
>>
>> John, could you also post here your kernel config? Those cgroups
>> errors *may* be related to some missing functionality from the kernel.

[snip kernel config]

John, your kernel is incorrectly configured to be used by systemd.
When you installed systemd, a warning should have appeared about some
missing configure options; you either didn't saw or ignored those
warnings. Install systemd again so you can see them.

From what I can tell, you are missing *AT LEAST* the following options:

CONFIG_AUTOFS4_FS
CONFIG_DMIID
CONFIG_FANOTIFY
CONFIG_INOTIFY_USER
CONFIG_PROC_FS
CONFIG_SYSFS

John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are
mandatory. I'm surprised you are able to boot to a semi-working state.

Yes, migrating to systemd is a lot of work. But if you don't see (or
ignore) your system messages, that work gets multiplied several times.

Reconfigure, recompile, and reinstall your kernel (don't forget to
reinstall the modules!), regenerate your initramfs, update lilo (if I
remember correctly, you need to run lilo -something-or-another every
time you change kernel and/or initramfs), and try again.

Regards

[1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
[2] http://www.freedesktop.org/software/systemd/man/systemd.network.html
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Fri, May 16, 2014 at 12:17 PM,  <covici@ccs.covici.com> wrote:
> [snip]
> >> I don't understand the current situation .So now you get ALL your
> >> volumes activated, or not?
> >
> > Yep, they are all activated and they all get mounted.
> 
> Cool, one problem less.
> 
> >> > Now for some systemd problems.  The root file system was read only when
> >> > I logged in, but I could remount it rw -- not sure why this was
> >> > happening.
> >>
> >> Set systemd.log_level=debug in your command line, and post the exit
> >> from journalctl -b.
> >
> > I had debug in the command line by itself, would that make the correct
> > log_level?  The file is quite large, should I send it to you privately?
> 
> I don't think is necessary, I may have found the real problem (see below).
> 
> >> >  Some units did start, but most did not.  Whenever I tried to
> >> > start one manually, I got a message like the following:
> [snip]
> >> > No matter what unit I tried to start I would get such a  message about
> >> > the service.mount.
> >>
> >> That sounds like a problem with the cgroups hierarchy (which uses a
> >> virtual filesystem). I don't remember seeing a problem like that
> >> before.
> >>
> >> > Also, even though my network names were correct, they did not come up,
> >> > but I will try to look in the logs to see why not.
> > I wrote a service file to start my network adaptors, here it is:
> > network@.service
> >
> >
> > [Unit]
> > Description=Network Connectivity for %i
> > Wants=network.target
> > Before=network.target
> > BindsTo=sys-subsystem-net-devices-%i.device
> > After=sys-subsystem-net-devices-%i.device
> > [Service]
> > Type=oneshot
> > RemainAfterExit=yes
> > EnvironmentFile=/etc/conf.d/network@%i
> > ExecStart=/usr/bin/ip link set dev %i up
> > ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
> > ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
> > ${gateway}'
> > ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
> > ExecStop=/usr/bin/ip addr flush dev %i
> > ExecStop=/usr/bin/ip link set dev %i down
> > [Install]
> > WantedBy=network.target
> 
> Did you enabled network@ifaca.service? Also, WantedBy=network.target
> doesn't do what you probably think it does (check [1]... and BTW, I
> forgot my last footnote, is now on [2]).
> 
> I would use WantedBy=multi-user.target.
> 
> >> systemd will not (AFAIK) start your network, and before the 209 or 210
> >> version it needed helper program (NetwokrManager, connman, ip,
> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to
> >> set up .network files (like .service files) to configure it. See [1].
> >>
> >> > So we have made some progress, but still a long way to go yet.  Note
> >> > also, that I am not booting into a display manager, just a regular
> >> > console.
> >> >
> >> >
> >> > What a lot of work just to get the system booted!
> >>
> >> Well, you have a setup that is not, by any means, simple. Also, in my
> >> experience old LVM configurations seem to cause a lot of troubles to
> >> bring to what systemd expects.
> >>
> >> John, could you also post here your kernel config? Those cgroups
> >> errors *may* be related to some missing functionality from the kernel.
> 
> [snip kernel config]
> 
> John, your kernel is incorrectly configured to be used by systemd.
> When you installed systemd, a warning should have appeared about some
> missing configure options; you either didn't saw or ignored those
> warnings. Install systemd again so you can see them.
> 
> From what I can tell, you are missing *AT LEAST* the following options:
> 
> CONFIG_AUTOFS4_FS
configured as a module.

> CONFIG_DMIID

set to Y

> CONFIG_FANOTIFY
set to y

> CONFIG_INOTIFY_USER
set to y


> CONFIG_PROC_FS
set to y

> CONFIG_SYSFS
set to y

> 
> John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are
> mandatory. I'm surprised you are able to boot to a semi-working state.
> 
> Yes, migrating to systemd is a lot of work. But if you don't see (or
> ignore) your system messages, that work gets multiplied several times.
> 
> Reconfigure, recompile, and reinstall your kernel (don't forget to
> reinstall the modules!), regenerate your initramfs, update lilo (if I
> remember correctly, you need to run lilo -something-or-another every
> time you change kernel and/or initramfs), and try again.
> 
> Regards
> 
> [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
> [2] http://www.freedesktop.org/software/systemd/man/systemd.network.html
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] problems getting systemd to work

[Canek Peláez Valdés]

On Fri, May 16, 2014 at 1:11 PM,  <covici@ccs.covici.com> wrote:
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
>> On Fri, May 16, 2014 at 12:17 PM,  <covici@ccs.covici.com> wrote:
>> [snip]
>> >> I don't understand the current situation .So now you get ALL your
>> >> volumes activated, or not?
>> >
>> > Yep, they are all activated and they all get mounted.
>>
>> Cool, one problem less.
>>
>> >> > Now for some systemd problems.  The root file system was read only when
>> >> > I logged in, but I could remount it rw -- not sure why this was
>> >> > happening.
>> >>
>> >> Set systemd.log_level=debug in your command line, and post the exit
>> >> from journalctl -b.
>> >
>> > I had debug in the command line by itself, would that make the correct
>> > log_level?  The file is quite large, should I send it to you privately?
>>
>> I don't think is necessary, I may have found the real problem (see below).
>>
>> >> >  Some units did start, but most did not.  Whenever I tried to
>> >> > start one manually, I got a message like the following:
>> [snip]
>> >> > No matter what unit I tried to start I would get such a  message about
>> >> > the service.mount.
>> >>
>> >> That sounds like a problem with the cgroups hierarchy (which uses a
>> >> virtual filesystem). I don't remember seeing a problem like that
>> >> before.
>> >>
>> >> > Also, even though my network names were correct, they did not come up,
>> >> > but I will try to look in the logs to see why not.
>> > I wrote a service file to start my network adaptors, here it is:
>> > network@.service
>> >
>> >
>> > [Unit]
>> > Description=Network Connectivity for %i
>> > Wants=network.target
>> > Before=network.target
>> > BindsTo=sys-subsystem-net-devices-%i.device
>> > After=sys-subsystem-net-devices-%i.device
>> > [Service]
>> > Type=oneshot
>> > RemainAfterExit=yes
>> > EnvironmentFile=/etc/conf.d/network@%i
>> > ExecStart=/usr/bin/ip link set dev %i up
>> > ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
>> > ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
>> > ${gateway}'
>> > ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
>> > ExecStop=/usr/bin/ip addr flush dev %i
>> > ExecStop=/usr/bin/ip link set dev %i down
>> > [Install]
>> > WantedBy=network.target
>>
>> Did you enabled network@ifaca.service? Also, WantedBy=network.target
>> doesn't do what you probably think it does (check [1]... and BTW, I
>> forgot my last footnote, is now on [2]).
>>
>> I would use WantedBy=multi-user.target.
>>
>> >> systemd will not (AFAIK) start your network, and before the 209 or 210
>> >> version it needed helper program (NetwokrManager, connman, ip,
>> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to
>> >> set up .network files (like .service files) to configure it. See [1].
>> >>
>> >> > So we have made some progress, but still a long way to go yet.  Note
>> >> > also, that I am not booting into a display manager, just a regular
>> >> > console.
>> >> >
>> >> >
>> >> > What a lot of work just to get the system booted!
>> >>
>> >> Well, you have a setup that is not, by any means, simple. Also, in my
>> >> experience old LVM configurations seem to cause a lot of troubles to
>> >> bring to what systemd expects.
>> >>
>> >> John, could you also post here your kernel config? Those cgroups
>> >> errors *may* be related to some missing functionality from the kernel.
>>
>> [snip kernel config]
>>
>> John, your kernel is incorrectly configured to be used by systemd.
>> When you installed systemd, a warning should have appeared about some
>> missing configure options; you either didn't saw or ignored those
>> warnings. Install systemd again so you can see them.
>>
>> From what I can tell, you are missing *AT LEAST* the following options:
>>
>> CONFIG_AUTOFS4_FS
> configured as a module.
>
>> CONFIG_DMIID
>
> set to Y
>
>> CONFIG_FANOTIFY
> set to y
>
>> CONFIG_INOTIFY_USER
> set to y
>
>
>> CONFIG_PROC_FS
> set to y
>
>> CONFIG_SYSFS
> set to y

I beg your pardon; GMail cut the config file and I didn't notice.

Well then, please send me privately the output from journalctl -b.

Regards.
-- 
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] problems getting systemd to work

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Fri, May 16, 2014 at 1:11 PM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Fri, May 16, 2014 at 12:17 PM,  <covici@ccs.covici.com> wrote:
> >> [snip]
> >> >> I don't understand the current situation .So now you get ALL your
> >> >> volumes activated, or not?
> >> >
> >> > Yep, they are all activated and they all get mounted.
> >>
> >> Cool, one problem less.
> >>
> >> >> > Now for some systemd problems.  The root file system was read only when
> >> >> > I logged in, but I could remount it rw -- not sure why this was
> >> >> > happening.
> >> >>
> >> >> Set systemd.log_level=debug in your command line, and post the exit
> >> >> from journalctl -b.
> >> >
> >> > I had debug in the command line by itself, would that make the correct
> >> > log_level?  The file is quite large, should I send it to you privately?
> >>
> >> I don't think is necessary, I may have found the real problem (see below).
> >>
> >> >> >  Some units did start, but most did not.  Whenever I tried to
> >> >> > start one manually, I got a message like the following:
> >> [snip]
> >> >> > No matter what unit I tried to start I would get such a  message about
> >> >> > the service.mount.
> >> >>
> >> >> That sounds like a problem with the cgroups hierarchy (which uses a
> >> >> virtual filesystem). I don't remember seeing a problem like that
> >> >> before.
> >> >>
> >> >> > Also, even though my network names were correct, they did not come up,
> >> >> > but I will try to look in the logs to see why not.
> >> > I wrote a service file to start my network adaptors, here it is:
> >> > network@.service
> >> >
> >> >
> >> > [Unit]
> >> > Description=Network Connectivity for %i
> >> > Wants=network.target
> >> > Before=network.target
> >> > BindsTo=sys-subsystem-net-devices-%i.device
> >> > After=sys-subsystem-net-devices-%i.device
> >> > [Service]
> >> > Type=oneshot
> >> > RemainAfterExit=yes
> >> > EnvironmentFile=/etc/conf.d/network@%i
> >> > ExecStart=/usr/bin/ip link set dev %i up
> >> > ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
> >> > ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
> >> > ${gateway}'
> >> > ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
> >> > ExecStop=/usr/bin/ip addr flush dev %i
> >> > ExecStop=/usr/bin/ip link set dev %i down
> >> > [Install]
> >> > WantedBy=network.target
> >>
> >> Did you enabled network@ifaca.service? Also, WantedBy=network.target
> >> doesn't do what you probably think it does (check [1]... and BTW, I
> >> forgot my last footnote, is now on [2]).
> >>
> >> I would use WantedBy=multi-user.target.
> >>
> >> >> systemd will not (AFAIK) start your network, and before the 209 or 210
> >> >> version it needed helper program (NetwokrManager, connman, ip,
> >> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to
> >> >> set up .network files (like .service files) to configure it. See [1].
> >> >>
> >> >> > So we have made some progress, but still a long way to go yet.  Note
> >> >> > also, that I am not booting into a display manager, just a regular
> >> >> > console.
> >> >> >
> >> >> >
> >> >> > What a lot of work just to get the system booted!
> >> >>
> >> >> Well, you have a setup that is not, by any means, simple. Also, in my
> >> >> experience old LVM configurations seem to cause a lot of troubles to
> >> >> bring to what systemd expects.
> >> >>
> >> >> John, could you also post here your kernel config? Those cgroups
> >> >> errors *may* be related to some missing functionality from the kernel.
> >>
> >> [snip kernel config]
> >>
> >> John, your kernel is incorrectly configured to be used by systemd.
> >> When you installed systemd, a warning should have appeared about some
> >> missing configure options; you either didn't saw or ignored those
> >> warnings. Install systemd again so you can see them.
> >>
> >> From what I can tell, you are missing *AT LEAST* the following options:
> >>
> >> CONFIG_AUTOFS4_FS
> > configured as a module.
> >
> >> CONFIG_DMIID
> >
> > set to Y
> >
> >> CONFIG_FANOTIFY
> > set to y
> >
> >> CONFIG_INOTIFY_USER
> > set to y
> >
> >
> >> CONFIG_PROC_FS
> > set to y
> >
> >> CONFIG_SYSFS
> > set to y
> 
> I beg your pardon; GMail cut the config file and I didn't notice.
> 
> Well then, please send me privately the output from journalctl -b.
I did find one error so far, I had network@.eth0 and eth2 when I should
have had network@eth0 and eth2 -- thanks to Stefan.

I will send you what logs I have.

Thanks.

> 
> Regards.
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com