[blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

[rhubarbpieguy via blfs-support]

The Xorg Intel Driver-20180223 documentation states the following
regarding kernel configuration:

Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
selected.

I see no "Intel i810" option with make menuconfig.

Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I
don't see that specific option, does it refer to 'Kernel modesetting
driver for MGA G200 server engines?'  I don't see another KMS option.

[Ken Moffat via blfs-support]

The Xorg Intel Driver-20180223 documentation states the following regarding
Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.

While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

ĸen

[renodr via blfs-support]

On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via

The Xorg Intel Driver-20180223 documentation states the following regarding
Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.
Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.
While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

Are you sure you're not thinking Kaby? My Skylake doesn't have an ounce
of firmware installed and performs excellent

ĸen
--
If a man stands before a mirror and sees in it his reflection, what
he sees is not a true reproduction, but a picture of himself when he
was a younger man. -- de Selby

[Ken Moffat via blfs-support]

Post by Ken Moffat via blfs-support
While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

Are you sure you're not thinking Kaby? My Skylake doesn't have an ounce of
firmware installed and performs excellent

It was a gentoo link after searching for something like linux I915
modesetting.

But when you say that, I hope you are only talking about video
firmware and not CPU microcode ;-)

ĸen

[Bruce Dubbs via blfs-support]

Post by Ken Moffat via blfs-support

The Xorg Intel Driver-20180223 documentation states the following regarding
Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree. We can probably just delete everything in that paragraph after
the first sentence.

Post by Ken Moffat via blfs-support
Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.

DRM_KMS_HELPER is selected by several different combinations of options,
but it is not selected directly. For me it is

DRM_FBDEV_EMULATION [=y] && HAS_IOMEM [=y] && DRM [=y]

Post by Ken Moffat via blfs-support
While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

My skylake (i5-6500) originally had no firmware and did not have a
problem with graphics. I am now using microcode-06-5e-03.img as an
initrd now, but I don't think that does anything for graphics.

-- Bruce

[renodr via blfs-support]

Post by Bruce Dubbs via blfs-support

On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via

The Xorg Intel Driver-20180223 documentation states the following regarding
Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be
selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree. We can probably just delete everything in that paragraph after
the first sentence.

I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

Post by Bruce Dubbs via blfs-support

Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.

DRM_KMS_HELPER is selected by several different combinations of
options, but it is not selected directly. For me it is
DRM_FBDEV_EMULATION [=y] && HAS_IOMEM [=y] && DRM [=y]

While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

My skylake (i5-6500) originally had no firmware and did not have a
problem with graphics. I am now using microcode-06-5e-03.img as an
initrd now, but I don't think that does anything for graphics.
-- Bruce

[Bruce Dubbs via blfs-support]

Post by renodr via blfs-support

On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via

The Xorg Intel Driver-20180223 documentation states the following regarding
    Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs
to be
    selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..."  However, I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree.  We can probably just delete everything in that paragraph after
the first sentence.

I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

We need a volunteer for that. The current editors' plates are pretty full.

-- Bruce

Post by renodr via blfs-support

Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers.  Kernel
options change, the book does not always keep up.

DRM_KMS_HELPER is selected by several different combinations of
options, but it is not selected directly.  For me it is
DRM_FBDEV_EMULATION [=y] && HAS_IOMEM [=y] && DRM [=y]

While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working.  I either
didn't know, or had forgotten, that.

My skylake (i5-6500) originally had no firmware and did not have a
problem with graphics.  I am now using microcode-06-5e-03.img as an
initrd now, but I don't think that does anything for graphics.
  -- Bruce

[rhubarbpieguy via blfs-support]

Post by renodr via blfs-support

On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via

The Xorg Intel Driver-20180223 documentation states the following regarding
    Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs
to be
    selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..." However,
I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree.  We can probably just delete everything in that paragraph after
the first sentence.

I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

We need a volunteer for that.  The current editors' plates are pretty
full.
  -- Bruce

I realize you're probably looking for something more sophisticated, but
I compared the documentation against the kernel menu.  I believe I found
the following:


                    documentation                 kernel menu


autofs

                    Kernel automounter version 4 support (also supports
v3)                        Kernel automounter support (supports v3, v4
and v5)

                    CIFS support (advanced network filesystem, SMBFS
successor)              non-existent?


bluez          Should RFCOMM TTV support, Multicast Filter support, and
Protocol filter support be indented for consistency?


sane - The documentation mentions Kernel Configuration but none seems to
exist.  Should that be stricken from the documentation?

The kernel menu does list several modules as (NEW), which the
documentation does not.  I ignored that and the modules in brackets in
the documentation, which I consider a nice touch.

[Bruce Dubbs via blfs-support]

Post by rhubarbpieguy via blfs-support

Post by renodr via blfs-support

Post by Ken Moffat via blfs-support

The Xorg Intel Driver-20180223 documentation states the following regarding
    Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs
to be
    selected.
I see no "Intel i810" option with make menuconfig.
Also, "If you select the latter, “Enable modesetting...” is needed too."
confuses me.  I assume that refers to "Intel 8xx/9xx..." However,
I don't
see that specific option, does it refer to 'Kernel modesetting driver for
MGA G200 server engines?'  I don't see another KMS option.

I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree.  We can probably just delete everything in that paragraph after
the first sentence.

I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

We need a volunteer for that.  The current editors' plates are pretty
full.
  -- Bruce

I realize you're probably looking for something more sophisticated, but
I compared the documentation against the kernel menu.  I believe I found
                    documentation                 kernel menu
autofs
                    Kernel automounter version 4 support (also supports
v3)                        Kernel automounter support (supports v3, v4
and v5)
                    CIFS support (advanced network filesystem, SMBFS
successor)              non-existent?
bluez          Should RFCOMM TTV support, Multicast Filter support, and
Protocol filter support be indented for consistency?
sane - The documentation mentions Kernel Configuration but none seems to
exist.  Should that be stricken from the documentation?
The kernel menu does list several modules as (NEW), which the
documentation does not.  I ignored that and the modules in brackets in
the documentation, which I consider a nice touch.

That's helpful. Did you find any discrepancies in the CONFIG_*
listings? Those cna be useful in menuconfig if you are searching for an
item or want to find out more info about an option.

-- Bruce

[rhubarbpieguy via blfs-support]

I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

Post by rhubarbpieguy via blfs-support

We need a volunteer for that.  The current editors' plates are
pretty full.
  -- Bruce

I realize you're probably looking for something more sophisticated,
but I compared the documentation against the kernel menu.  I believe
                     documentation                 kernel menu
autofs
                     Kernel automounter version 4 support (also
supports v3)                        Kernel automounter support
(supports v3, v4 and v5)
                     CIFS support (advanced network filesystem, SMBFS
successor)              non-existent?
bluez          Should RFCOMM TTV support, Multicast Filter support,
and Protocol filter support be indented for consistency?
sane - The documentation mentions Kernel Configuration but none seems
to exist.  Should that be stricken from the documentation?
The kernel menu does list several modules as (NEW), which the
documentation does not.  I ignored that and the modules in brackets
in the documentation, which I consider a nice touch.

That's helpful.  Did you find any discrepancies in the CONFIG_*
listings?  Those cna be useful in menuconfig if you are searching for
an item or want to find out more info about an option.
  -- Bruce

I hope I understand your question.  Using the 4.19.6 kernel and 12/03/18
development documentation I checked all occurences of [CONFIG_*]'s not
listed in the .config file generated by 'make menuconfig' and found only
the following:

CONFIG_INCOMP_PAR_MOD - introduction/conventions.html
CONFIG_OPT_PAR - introduction/conventions.html
CONFIG_REQU_PAR_MOD - introduction/conventions.html
CONFIG_REQU_PAR_NMOD - introduction/conventions.html

But as those are illustrative only they're probably not a big deal.

[Bruce Dubbs via blfs-support]

Post by renodr via blfs-support
I honestly think it'd be smart to pull up the Kernel Configuration
section in the Index and verify that every package that has special
kernel configuration hasn't had it's options moved.

Post by rhubarbpieguy via blfs-support

We need a volunteer for that.  The current editors' plates are
pretty full.
  -- Bruce

I realize you're probably looking for something more sophisticated,
but I compared the documentation against the kernel menu.  I believe
                     documentation                 kernel menu
autofs
                     Kernel automounter version 4 support (also
supports v3)                        Kernel automounter support
(supports v3, v4 and v5)
                     CIFS support (advanced network filesystem, SMBFS
successor)              non-existent?
bluez          Should RFCOMM TTV support, Multicast Filter support,
and Protocol filter support be indented for consistency?
sane - The documentation mentions Kernel Configuration but none seems
to exist.  Should that be stricken from the documentation?
The kernel menu does list several modules as (NEW), which the
documentation does not.  I ignored that and the modules in brackets
in the documentation, which I consider a nice touch.

That's helpful.  Did you find any discrepancies in the CONFIG_*
listings?  Those cna be useful in menuconfig if you are searching for
an item or want to find out more info about an option.
  -- Bruce

I hope I understand your question.  Using the 4.19.6 kernel and 12/03/18
development documentation I checked all occurences of [CONFIG_*]'s not
listed in the .config file generated by 'make menuconfig' and found only

Thank you.

Post by renodr via blfs-support
CONFIG_INCOMP_PAR_MOD - introduction/conventions.html
CONFIG_OPT_PAR - introduction/conventions.html
CONFIG_REQU_PAR_MOD - introduction/conventions.html
CONFIG_REQU_PAR_NMOD - introduction/conventions.html
But as those are illustrative only they're probably not a big deal.

Right. They are not supposed to be real values. More completely:

Required parameter [CONFIG_REQU_PAR]

The (fake) CONFIG name mirrors the description.

-- Bruce

[Ken Moffat via blfs-support]

Post by Ken Moffat via blfs-support
I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree. We can probably just delete everything in that paragraph after the
first sentence.

Post by Ken Moffat via blfs-support
Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.

DRM_KMS_HELPER is selected by several different combinations of options, but
it is not selected directly. For me it is
DRM_FBDEV_EMULATION [=y] && HAS_IOMEM [=y] && DRM [=y]

Post by Ken Moffat via blfs-support
While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

My skylake (i5-6500) originally had no firmware and did not have a problem
with graphics. I am now using microcode-06-5e-03.img as an initrd now, but
I don't think that does anything for graphics.
-- Bruce

I've now got firefox and its deps built on my fresh system, so I
took another look. The link is https://wiki.gentoo.org/wiki/Intel

The text there says:

| Systems using Kaby Lake, Skylake or Broxton Intel graphics will
| need to install additional firmware[1] from
| sys-kernel/linux-firmware package

|Otherwise errors such as the following might be visible in dmesg:

| kernel: i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1_26.bin failed with error -2
| kernel: i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management.

And it also warns:

| Including the firmware in-kernel may cause suspend-to-ram to fail,
| if this is a concern don't include the blob built into the kernel.

It also mentions loading GuC firmware.

Brief details of what the TLAs do is at
https://01.org/linuxgraphics/downloads/firmware

More at https://wiki.archlinux.org/index.php/intel_graphics#Loading

Summary: For skylake it is not clear if these are for *all*
skylakes, or only for the higher-end (Iris, Iris Pro). And it
appears that the relevant parts work - albeit not with all the
available powersaving or encoding bells and whistles.

ĸen

[Bruce Dubbs via blfs-support]

Post by Ken Moffat via blfs-support

Post by Ken Moffat via blfs-support
I'm not sure what happened to the I810, and not really interested -
it predated modern intel CPUs.

Agree. We can probably just delete everything in that paragraph after the
first sentence.

Post by Ken Moffat via blfs-support
Modesetting is probably now activated by DRM_KMS_HELPER, and that is
now selected by at least the main in-kernel DRM drivers. Kernel
options change, the book does not always keep up.

DRM_KMS_HELPER is selected by several different combinations of options, but
it is not selected directly. For me it is
DRM_FBDEV_EMULATION [=y] && HAS_IOMEM [=y] && DRM [=y]

Post by Ken Moffat via blfs-support
While I was checking on this I noticed that Skylake and later
apparently need firmware to get the graphics working. I either
didn't know, or had forgotten, that.

My skylake (i5-6500) originally had no firmware and did not have a problem
with graphics. I am now using microcode-06-5e-03.img as an initrd now, but
I don't think that does anything for graphics.
-- Bruce

I've now got firefox and its deps built on my fresh system, so I
took another look. The link is https://wiki.gentoo.org/wiki/Intel
| Systems using Kaby Lake, Skylake or Broxton Intel graphics will
| need to install additional firmware[1] from
| sys-kernel/linux-firmware package
| kernel: i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1_26.bin failed with error -2
| kernel: i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management.
| Including the firmware in-kernel may cause suspend-to-ram to fail,
| if this is a concern don't include the blob built into the kernel.
It also mentions loading GuC firmware.
Brief details of what the TLAs do is at
https://01.org/linuxgraphics/downloads/firmware
More at https://wiki.archlinux.org/index.php/intel_graphics#Loading
Summary: For skylake it is not clear if these are for *all*
skylakes, or only for the higher-end (Iris, Iris Pro). And it
appears that the relevant parts work - albeit not with all the
available powersaving or encoding bells and whistles.

I'm sorry you took the time to show me where I was wrong. I completely
forgot to look at the kernel configuration on my system:

CONFIG_EXTRA_FIRMWARE="i915/skl_dmc_ver1_26.bin rtl_nic/rtl8168h-2.fw"

Yes, that firmware is built into my kernel.

-- Bruce

[Ken Moffat via blfs-support]

Post by Bruce Dubbs via blfs-support
I'm sorry you took the time to show me where I was wrong. I completely
CONFIG_EXTRA_FIRMWARE="i915/skl_dmc_ver1_26.bin rtl_nic/rtl8168h-2.fw"
Yes, that firmware is built into my kernel.
-- Bruce

No problem.

ĸen