intel 82810e dc-133 vga controller driver update

mrmazda · 05-10-2021, 03:30 AM

Making progress:

Code:

# inxi -GISay
System:
  Host: gx110 Kernel: 4.9.0-15-686 i686 bits: 32 compiler: gcc v: 6.3.0
  parameters: root=LABEL=08w4deb09 ipv6.disable=1 net.ifnames=0 noresume
  mitigations=none drm.debug=0x06 log_buf_len=1M iomem=relaxed
  video=i810fb:1680x1050-16@60
Desktop: Trinity R14.0.10 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 vt: 7
  dm: TDM Distro: Debian GNU/Linux 9 (stretch)
Graphics:
  Device-1: Intel 82810E DC-133 Graphics vendor: Dell OptiPlex GX110
  driver: i810fb v: kernel bus-ID: 00:01.0 chip-ID: 8086:7125 class-ID: 0300
  Display: server: X.Org 1.19.2 driver: loaded: fbdev
  unloaded: modesetting,vesa display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 445x278mm (17.5x10.9")
  s-diag: 525mm (20.7")
  Monitor-1: default res: 1680x1050 hz: 60
  OpenGL: renderer: N/A v: N/A direct render: N/A
Info:...Shell: Bash v: 4.4.12 running-in: konsole  inxi: 3.3.04
# cat /etc/modules
...
drm
drm_kms_helper
i810
i810fb
video

More to come. I may be on track to get the Intel DDX driver working.

mrmazda · 05-11-2021, 03:44 AM

In Debian 9 Stretch, the following two settings seem to be the minimum required manual configuration to reach native display mode using the Intel DDX driver:

Code:

> cat /etc/modules
i810
> cat /etc/X11/xorg.conf.d/50-device.conf
Section "Device"
    Identifier  "Default Device"
        Driver  "intel"
EndSection

The i810 kernel driver, if loaded automatically, results in various types of breakage, so needs to be forced at the outset.
Without explicitly specifying the Intel DDX driver, 640x480 resolution results from use of the VESA driver, with no opportunity to correct via xrandr, as the VESA X driver is unable to discover or utilize CRTC output names.

The following shows what results from using the above configuration:

Code:

> lsmod | sort | egrep 'drm|dri|i810|i915|intel|video' | grep -v snd
drm                   258048  3 i810
i810                   24576  1
intel_rng              16384  0
rng_core               16384  2 intel_rng
> inxi -GISay
System:
  Host: gx110.ij.net Kernel: 4.9.0-15-686 i686 bits: 32 compiler: gcc v: 6.3.0
  parameters: root=LABEL=08w4deb09 noresume
  Desktop: Trinity R14.0.10 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 vt: 7
  dm: TDM Distro: Debian GNU/Linux 9 (stretch)
Graphics:
  Device-1: Intel 82810E DC-133 Graphics vendor: Dell OptiPlex GX110
  driver: N/A bus-ID: 00:01.0 chip-ID: 8086:7125 class-ID: 0300
  Display: server: X.Org 1.19.2 driver: loaded: intel
  display-ID: :0  screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 90 s-size: 474x303mm (18.7x11.9")
  s-diag: 563mm (22.1")
  Monitor-1: default res: 1680x1050 hz: 60
  OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.9 128 bits)
  v: 3.3 Mesa 13.0.6 compat-v: 3.0 direct render: Yes
Info:...Shell: Bash v: 4.4.12 running-in: konsole  inxi: 3.3.04
> xrandr | head -n13
Screen 0: minimum 640 x 400, current 1680 x 1050, maximum 1680 x 1050
default connected 1680x1050+0+0 0mm x 0mm
   1680x1050     60.00*
   1600x1000     60.00
   1400x1050     75.00    70.00    60.00
   1280x1024     75.00    72.00    60.00
   1440x900      75.00    60.00
   1280x960      60.00
   1360x768      60.00
   1152x864      75.00    70.00    60.00
   1024x768      75.00    70.00    60.00
   832x624       75.00
   800x600       75.00    72.00    60.00    56.00

Some of the docs perused prior to determining this solution:

sirius57 · 05-11-2021, 07:53 PM

That's great news. I follow what you posted in the output. Did you edit the xorg.conf file to make debian use the intel driver?

mrmazda · 05-11-2021, 08:25 PM

Quote:

Originally Posted by sirius57

Did you edit the xorg.conf file to make debian use the intel driver?

No.

Code:

> cat /etc/X11/xorg.conf
cat: /etc/X11/xorg.conf: No such file or directory
> cat /etc/X11/xorg.conf.d/50-device.conf
Section "Device"
    Identifier  "Default Device"
        Driver  "intel"
EndSection

mrmazda · 05-11-2021, 09:04 PM

The same configuration that works for Stretch also works for Buster. For Bullseye, the appropriate kernel modules autoload, so no forcing of the appropriate kernel module (i915, as i810 no longer exists) is needed, while explicit Intel DDX driver configuration remains required.