Tiny Core 8 with Intel HD Graphics 500 on Intel Atom E3930 CPU

[Juanito]

was graphics-KERNEL loaded?

[Juanito]

The gnome-terminal.tcz extension also doesn't display the bad behaviour as aterm.  It has other bad points (and btw it is missing dependency libffi5.tcz, but even after providing that it won't launch from the icon on wbar.  I had to launch it using sudo, from aterm.)

gnome-terminal and vte-gtk3 recompiled and posted - thanks for reporting this

[pq5190362]

[juanito] my apologies, I modified this post rather than quoting it and can't get it back 

[dspence]

Juanito, thanks!  No, graphics-KERNEL was not loaded!  I have added it to onboot.lst, and it works, and there is no visual corruption now with aterm!

From Xorg.0.log:

...

Code: [Select]

[    25.614] (II) xfree86: Adding drm device (/dev/dri/card0)
[    25.739] (--) PCI:*(0:0:2:0) 8086:5a85:8086:2212 rev 11, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[    25.739] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    25.740] (II) LoadModule: "glx"
[    25.741] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    25.760] (II) Module glx: vendor="X.Org Foundation"
[    25.760] compiled for 1.19.5, module version = 1.0.0
[    25.760] ABI class: X.Org Server Extension, version 10.0
[    25.761] (==) Matched intel as autoconfigured driver 0
[    25.761] (==) Matched intel as autoconfigured driver 1
[    25.761] (==) Matched modesetting as autoconfigured driver 2
[    25.761] (==) Matched fbdev as autoconfigured driver 3
[    25.761] (==) Matched vesa as autoconfigured driver 4
[    25.761] (==) Assigned the driver to the xf86ConfigLayout
[    25.761] (II) LoadModule: "intel"
[    25.761] (WW) Warning, couldn't open module intel
[    25.761] (II) UnloadModule: "intel"
[    25.761] (II) Unloading intel
[    25.761] (EE) Failed to load module "intel" (module does not exist, 0)
[    25.761] (II) LoadModule: "modesetting"
[    25.761] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    25.764] (II) Module modesetting: vendor="X.Org Foundation"
[    25.764] compiled for 1.19.5, module version = 1.19.5
[    25.764] Module class: X.Org Video Driver
[    25.764] ABI class: X.Org Video Driver, version 23.0
[    25.764] (II) LoadModule: "fbdev"
[    25.764] (WW) Warning, couldn't open module fbdev
[    25.764] (II) UnloadModule: "fbdev"
[    25.764] (II) Unloading fbdev
[    25.764] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    25.764] (II) LoadModule: "vesa"
[    25.764] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[    25.765] (II) Module vesa: vendor="X.Org Foundation"
[    25.765] compiled for 1.19.1, module version = 2.3.4
[    25.765] Module class: X.Org Video Driver
[    25.765] ABI class: X.Org Video Driver, version 23.0
[    25.765] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    25.765] (II) VESA: driver for VESA chipsets: vesa
[    25.765] (--) using VT number 2

[    25.799] (II) modeset(0): using drv /dev/dri/card0
[    25.799] (WW) Falling back to old probe method for vesa
[    25.799] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[    25.799] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    25.799] (==) modeset(0): RGB weight 888
[    25.799] (==) modeset(0): Default visual is TrueColor
[    25.799] (II) Loading sub module "glamoregl"
[    25.799] (II) LoadModule: "glamoregl"
[    25.800] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so
[    25.842] (II) Module glamoregl: vendor="X.Org Foundation"
[    25.842] compiled for 1.19.5, module version = 1.0.0
[    25.842] ABI class: X.Org ANSI C Emulation, version 0.4
[    25.842] (II) glamor: OpenGL accelerated X.org driver based.
[    25.843] couldn't get display device
[    25.843] (EE) modeset(0): glamor initialization failed
[    25.843] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[    25.843] (II) modeset(0): Double-buffered shadow updates: off
[    25.844] (II) modeset(0): Output eDP-1 has no monitor section
[    25.844] (II) modeset(0): Output DP-1 has no monitor section
[    25.845] (II) modeset(0): Output HDMI-1 has no monitor section
[    25.845] (II) modeset(0): Output DP-2 has no monitor section
[    26.057] (II) modeset(0): Output HDMI-2 has no monitor section
[    26.059] (II) modeset(0): EDID for output eDP-1
[    26.059] (II) modeset(0): Printing probed modes for output eDP-1
[    26.059] (II) modeset(0): Modeline "640x480"x60.0   25.18  640 656 752 800  480 492 494 525 -hsync -vsync (31.5 kHz P)
[    26.059] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
[    26.059] (II) modeset(0): Modeline "512x384"x120.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[    26.059] (II) modeset(0): Modeline "400x300"x120.6   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[    26.059] (II) modeset(0): Modeline "400x300"x112.7   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[    26.059] (II) modeset(0): Modeline "320x240"x120.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[    26.059] (II) modeset(0): EDID for output DP-1
[    26.060] (II) modeset(0): EDID for output HDMI-1
[    26.060] (II) modeset(0): EDID for output DP-2
[    26.274] (II) modeset(0): EDID for output HDMI-2
[    26.274] (II) modeset(0): Output eDP-1 connected
[    26.274] (II) modeset(0): Output DP-1 disconnected
[    26.274] (II) modeset(0): Output HDMI-1 disconnected
[    26.274] (II) modeset(0): Output DP-2 disconnected
[    26.274] (II) modeset(0): Output HDMI-2 disconnected
[    26.274] (II) modeset(0): Using exact sizes for initial modes
[    26.274] (II) modeset(0): Output eDP-1 using initial mode 640x480 +0+0
[    26.274] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    26.274] (++) modeset(0): DPI set to (96, 96)
[    26.274] (II) Loading sub module "fb"
[    26.274] (II) LoadModule: "fb"
[    26.274] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[    26.283] (II) Module fb: vendor="X.Org Foundation"
[    26.283] compiled for 1.19.5, module version = 1.0.0
[    26.283] ABI class: X.Org ANSI C Emulation, version 0.4
[    26.283] (II) Loading sub module "shadow"
[    26.283] (II) LoadModule: "shadow"
[    26.284] (II) Loading /usr/local/lib/xorg/modules/libshadow.so
[    26.285] (II) Module shadow: vendor="X.Org Foundation"
[    26.285] compiled for 1.19.5, module version = 1.1.0
[    26.285] ABI class: X.Org ANSI C Emulation, version 0.4
[    26.285] (II) UnloadModule: "vesa"
[    26.285] (II) Unloading vesa
[    26.285] (==) Depth 24 pixmap format is 32 bpp
[    26.289] (==) modeset(0): Backing store enabled
[    26.289] (==) modeset(0): Silken mouse enabled
[    26.289] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    26.290] (==) modeset(0): DPMS enabled
[    26.290] (--) RandR disabled
[    26.290] (II) AIGLX: Screen 0 is not DRI2 capable
[    26.290] (EE) AIGLX: reverting to software rendering
[    26.290] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[    26.290] (EE) GLX: could not load software renderer
[    26.290] (II) GLX: no usable GL providers found for screen 0
[    26.291] (II) modeset(0): Damage tracking initialized
[    26.291] (II) modeset(0): Setting screen physical size to 169 x 126
...

The performance seems good on this chip.

I tried the same on the older Atoms that I have.  Performance is not good on those, so I think I'll use xf86-video-intel on those, and the modesetting driver on this one.


    [EDIT] Added code tags.  Rich

[Rich]

Hi dspence
Instead of using  tt  tags please use  code  tags. This will still preserve spacing as it too uses a monotype font in addition to
adding scroll bars for longer printouts.

[dspence]

Rich: Sorry!  I'll try to remember to use code tags in future.

I tried rxvt, and it had the same problem as aterm.  I went back all the way to the Tiny Core 4 extension repository and got xterm.tcz, and it was mostly okay, so there's a chance I would have used that one.



pq5190362: Thanks for the info!  It looks like the modesetting driver is easier than that to get running, though.  Juanito's solution of not loading xf86-video-intel, but loading graphics-KERNEL, worked for me, without needing configuration files.

[pq5190362]

It looks like the modesetting driver is easier than that to get running, though.  Juanito's solution of not loading xf86-video-intel, but loading graphics-KERNEL, worked for me, without needing configuration files.

There is no "not loading xf86-video-intel BUT loading graphics-KERNEL".

The reason xf86-video-intel did not work very likely is due to you not having installed graphics-KERNEL.

So, since you have installed graphics-KERNEL now, you might also want to re-install xf86-video-intel and compare it with xf86-video-modesetting.

And, yes, not installing xf86-video-intel results in xf86-video-modesetting automatically loading since it is built into xorg-server. The configuration file allows you to have xf86-video-intel installed but forcing xf86-video-modesetting to load instead of xf86-video-intel (i.e. using xf86-video-modesetting without uninstalling xf86-video-intel).

[dspence]

pq5190362,

No, graphics-KERNEL is a dependency of xf86-video-intel.  It was there, it was just not loaded anymore after removing xf86-video-intel from onboot.lst.  I added it on its own, and now the modesetting driver works.

[pq5190362]

Then maybe graphics-KERNEL should be made a dependency of Xorg-7.7-3d or even xorg-server, since xf86-video-modesetting is built into xorg-server.

[curaga]

It is a relatively big file, and many Xorg users do not need to load it. Generally optional dependencies are listed in info files.

[Juanito]

Xorg-7.7 info file modified accordingly