Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-14 Thread Markus Hiereth 
Hello Felix and Xorg team

Felix Miata schrieb am 10. August 2019 um 23:00

> > As I annonced, I made an
> > attempt with disabled DRI option for the video card, i.e. I introduced
> 
> >   Option  "DRI" "False" 
 
> I suppose DRI support is supposed to be auto-detected but maybe is
> not working as expected in your environments.
> https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure
 
> > in the device section of xorg.conf. The result was that the X server
> > started as expected.  Below the respective logfile.
> 
> > Thus, the problem is solved though I do not know or try to imagine
> > what benefits DRI "Direct rendering infrastructure" might have.
 
> Does this PC with AGP slot and G400 have 4G or more physical RAM? If
> it does not, as I have no AGP slot boards that support more than 2G
> and suspect maybe there exists no such things, for completeness sake
> I would undo the DRI false option and try the non-PAE kernel. See
> here why I make this suggestion:
> https://bugzilla.opensuse.org/show_bug.cgi?id=1118689#c29 Anyway,
> great to know these great old GPUs remain useful for others than
> myself. :-)

The working memory of this PC is 512 Megabyte. I booted it with the
non-PAE kernel and commented out the DRI option. The X server failed
again to start. (Logfile attached)

> --
> Markus Hiereth composed on 2019-08-10 22:27 (UTC+0200):
> 
> > [  3974.700] (II) MGA(0): VESA VBE DDC supported
> > [  3974.700] (II) MGA(0): VESA VBE DDC Level none
> > [  3974.700] (II) MGA(0): VESA VBE DDC transfer in appr. 0 sec.
> > [  3974.844] (II) MGA(0): VESA VBE DDC read failed
 
> I spotted another unexpected difference. Mine:
> [  1679.533] (II) MGA(0): VESA VBE DDC supported
> [  1679.533] (II) MGA(0): VESA VBE DDC Level 2
> [  1679.533] (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec.
> [  1681.106] (II) MGA(0): VESA VBE DDC read successfully
 
> This suggests to me your problem's root could be in your display's
> EDID. Have you tried with other displays?

I suppose my monitor does not deliver EDID information. It is
remarkably older than yours (2000 versus 2011). From a working
configuration of the system with Debian 8 (it is a dual boot system) I
copied a modeline with adequate settings for this monitor.

Thanks for your additional hints
Markus
[  2111.172] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[  2111.172] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[  2111.172] Current Operating System: Linux lune 4.19.0-5-686 #1 SMP Debian 
4.19.37-5 (2019-06-19) i686
[  2111.172] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686 
root=/dev/sda7
[  2111.172] Build Date: 05 March 2019  08:11:12PM
[  2111.172] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[  2111.173] Current version of pixman: 0.36.0
[  2111.173]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  2111.173] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2111.173] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 11 19:42:57 
2019
[  2111.174] (==) Using config file: "/etc/X11/xorg.conf"
[  2111.174] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2111.175] (==) ServerLayout "X.org Configured"
[  2111.175] (**) |-->Screen "Screen0" (0)
[  2111.175] (**) |   |-->Monitor "Monitor0"
[  2111.177] (**) |   |-->Device "Card0"
[  2111.177] (**) |-->Input Device "Mouse0"
[  2111.177] (**) |-->Input Device "Keyboard0"
[  2111.177] (==) Automatically adding devices
[  2111.177] (==) Automatically enabling devices
[  2111.177] (==) Automatically adding GPU devices
[  2111.178] (==) Max clients allowed: 256, resource mask: 0x1f
[  2111.178] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  2111.178]Entry deleted from font path.
[  2111.178] (**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  2111.178] (**) ModulePath set to "/usr/lib/xorg/modules"
[  2111.178] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 
'vmmouse' will be disabled.
[  2111.178] (WW) Disabling Mouse0
[  2111.178] (WW) Disabling Keyboard0
[  2111.178] (II) Loader magic: 0x75c740
[  2111.178] (II) Module ABI versions:
[  2111.178]X.Org ANSI C Emulation: 0.4
[  2111.178]X.Org Video Driver: 24.0
[  2111.178]

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-14 Thread Markus Hiereth 
Hello Felix and X server experts

first of all: Thank You for the logfile.

According to the selected strings from the card's BIOS ...

# selected strings from video BIOS dump
IBM COMPATIBLE MATROX/Matrox G400 VGA/VBE BIOS (V2.1) b35 
MATROX POWER GRAPHICS ACCELERATOR
MGA Series
VGA/VBE BIOS, Version V2.1
Copyright (C) 1998, Matrox Graphics Inc.
DATE: 11/21/00
Revision: 0.35 
Matrox Graphics Inc.
Matrox G400

... I conclude our cards work with the same Version 2.1 of the VGA
BIOS. As I wrote, I updated my BIOS using the content of your zip file.

Below are the results of my comparison. There are differences, but
would not say that I found something very suspicious - as the MTRR
failure messages I noticed earlier. A test I am about to make now is
disabling "DRI" / "drm". Perhaps this is possible using the module
section in xorg.conf.

Best regards
Markus



Your mga module was compiled for another version of the server:

66c80
> (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
< (II) Loading /usr/local/lib/xorg/modules/drivers/mga_drv.so
68c82,88
<   compiled for 1.20.4, module version = 2.0.0
---
>   compiled for 1.20.3, module version = 2.0.0
>   Module class: X.Org Video Driver
>   ABI class: X.Org Video Driver, version 24.0
> (II) LoadModule: "modesetting"
> (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> (II) Module modesetting: vendor="X.Org Foundation"
>   compiled for 1.20.4, module version = 1.20.4


Only my logfile conains this warninng:

< (WW) xf86OpenConsole: setpgid failed: Operation not permitted
< (WW) xf86OpenConsole: setsid failed: Operation not permitted


Large differences, but maybe due to monitor detection that does not take
place with my configuration:

139,142c168,248
< (II) MGA(0): VESA VBE DDC Level none
< (II) MGA(0): VESA VBE DDC transfer in appr. 0 sec.
< (II) MGA(0): VESA VBE DDC read failed
< (II) MGA(0): UNMAPPING framebuffer 0xB6258000, 0x100.
---
> (II) MGA(0): VESA VBE DDC Level 2
> (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec.
> (II) MGA(0): VESA VBE DDC read successfully
> (II) MGA(0): VBE monitor info
> (II) MGA(0): Manufacturer: LEN  Model: a12  Serial#: 16843009
> (II) MGA(0): Year: 2011  Week: 10
> (II) MGA(0): EDID Version: 1.3
> (II) MGA(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
> (II) MGA(0): Sync:  Separate  Composite
> (II) MGA(0): Max Image Size [cm]: horiz.: 47  vert.: 30
> (II) MGA(0): Gamma: 2.20
> (II) MGA(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
> (II) MGA(0): Default color space is primary color space
> (II) MGA(0): First detailed timing is preferred mode
> (II) MGA(0): redX: 0.639 redY: 0.343   greenX: 0.332 greenY: 0.617
> (II) MGA(0): blueX: 0.151 blueY: 0.068   whiteX: 0.313 whiteY: 0.329
> (II) MGA(0): Supported established timings:
> (II) MGA(0): 720x400@70Hz
> (II) MGA(0): 640x480@60Hz
> (II) MGA(0): 640x480@67Hz
> (II) MGA(0): 640x480@72Hz
> (II) MGA(0): 640x480@75Hz
> (II) MGA(0): 800x600@60Hz
> (II) MGA(0): 800x600@72Hz
> (II) MGA(0): 800x600@75Hz
> (II) MGA(0): 1024x768@60Hz
> (II) MGA(0): 1024x768@70Hz
> (II) MGA(0): 1024x768@75Hz
> (II) MGA(0): 1280x1024@75Hz
> (II) MGA(0): Manufacturer's mask: 0
> (II) MGA(0): Supported standard timings:
> (II) MGA(0): #0: hsize: 1152  vsize 864  refresh: 75  vid: 20337
> (II) MGA(0): #1: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
> (II) MGA(0): #2: hsize: 1280  vsize 1024  refresh: 72  vid: 35969
> (II) MGA(0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
> (II) MGA(0): #4: hsize: 1440  vsize 900  refresh: 75  vid: 3989
> (II) MGA(0): #5: hsize: 1600  vsize 1000  refresh: 60  vid: 169
> (II) MGA(0): #6: hsize: 1680  vsize 1050  refresh: 60  vid: 179
> (II) MGA(0): #7: hsize: 1680  vsize 1050  refresh: 75  vid: 4019
> (II) MGA(0): Supported detailed timing:
> (II) MGA(0): clock: 146.3 MHz   Image Size:  474 x 296 mm
> (II) MGA(0): h_active: 1680  h_sync: 1784  h_sync_end 1960 h_blank_end 2240 
> h_border: 0
> (II) MGA(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking: 1089 
> v_border: 0
> (II) MGA(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 83 kHz, 
> PixClock max 205 MHz
> (II) MGA(0): Monitor name: L2251x Wide
> (II) MGA(0): Serial No: 6V647310
> (II) MGA(0): EDID (in hex):
> (II) MGA(0):  000030ae120a01010101
> (II) MGA(0):  0a1501036c2f1e78eeb0e5a357559e26
> (II) MGA(0):  115054bdcf00714f8180818c9500950f
> (II) MGA(0):  a900b300b30f26399030621a274068b0
> (II) MGA(0):  3600da28111c00fd00324b1e
> (II) MGA(0):  5314000a20202020202000fc004c
> (II) MGA(0):  323235317820576964650a2000ff
> (II) MGA(0):  0036563634373331300a2020202000c9
> (II) MGA(0): end of monitor info
> (II) MGA(0): UNMAPPING framebuffer 0xB6288000, 0x100.
> (II) MGA(0): EDID vendor "LEN", prod id 2578
> (II) MGA(0): Using EDID range info for horizontal sync
> (II) MGA(0): Using

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-14 Thread Markus Hiereth 
Hello Felix and Xorg team,

Felix Miata schrieb am 10. August 2019 um 21:55

> I have no /usr/local/lib/xorg/* here, nor any idea how to explain my
> mga_drv.so reporting compiled for 1.20.3. There is minimal
> corruption here at window and panel edges, but it doesn't interfere
> with normal use.  Here's a fresh log, nominally larger, 691 lines
> instead of 683:
> http://fm.no-ip.com/Tmp/Linux/Xorg/Mga/xorg.0.log-gx27c-deb10-G400-normal

thank You for delivering a second logfile. As I annonced, I made an
attempt with disabled DRI option for the video card, i.e. I introduced

  Option  "DRI" "False"

in the device section of xorg.conf. The result was that the X server
started as expected.  Below the respective logfile.

Thus, the problem is solved though I do not know or try to imagine
what benefits DRI "Direct rendering infrastructure" might have.

Thanks a lot for Your help and all other contributions from members of
this mailing list.

Markus

---

[  3972.964] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[  3972.967] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[  3972.968] Current Operating System: Linux lune 4.19.0-5-686-pae #1 SMP 
Debian 4.19.37-5 (2019-06-19) i686
[  3972.969] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae 
root=/dev/sda7
[  3972.971] Build Date: 05 March 2019  08:11:12PM
[  3972.971] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[  3972.972] Current version of pixman: 0.36.0
[  3972.973]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  3972.974] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  3972.976] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 10 21:46:56 
2019
[  3972.978] (++) Using config file: "/etc/X11/xorg_05.conf"
[  3972.979] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  3972.980] (==) ServerLayout "X.org Configured"
[  3972.981] (**) |-->Screen "Screen0" (0)
[  3972.981] (**) |   |-->Monitor "Monitor0"
[  3972.983] (**) |   |-->Device "Card0"
[  3972.983] (**) |-->Input Device "Mouse0"
[  3972.983] (**) |-->Input Device "Keyboard0"
[  3972.983] (==) Automatically adding devices
[  3972.983] (==) Automatically enabling devices
[  3972.983] (==) Automatically adding GPU devices
[  3972.983] (==) Max clients allowed: 256, resource mask: 0x1f
[  3972.983] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  3972.984]Entry deleted from font path.
[  3972.984] (**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  3972.984] (**) ModulePath set to "/usr/lib/xorg/modules"
[  3972.984] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 
'vmmouse' will be disabled.
[  3972.984] (WW) Disabling Mouse0
[  3972.984] (WW) Disabling Keyboard0
[  3972.984] (II) Loader magic: 0x678740
[  3972.984] (II) Module ABI versions:
[  3972.984]X.Org ANSI C Emulation: 0.4
[  3972.984]X.Org Video Driver: 24.0
[  3972.984]X.Org XInput driver : 24.1
[  3972.984]X.Org Server Extension : 10.0
[  3972.990] (--) using VT number 2

[  3972.990] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[  3972.993] (II) xfree86: Adding drm device (/dev/dri/card0)
[  3973.004] (--) PCI:*(1@0:0:0) 102b:0525:102b:19d8 rev 4, Mem @ 
0xdc00/33554432, 0xdfefc000/16384, 0xdf00/8388608, BIOS @ 
0x/131072
[  3973.004] (II) "glx" will be loaded. This was enabled by default and also 
specified in the config file.
[  3973.005] (II) LoadModule: "glx"
[  3973.006] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  3973.290] (II) Module glx: vendor="X.Org Foundation"
[  3973.290]compiled for 1.20.4, module version = 1.0.0
[  3973.290]ABI class: X.Org Server Extension, version 10.0
[  3973.290] (II) LoadModule: "mga"
[  3973.291] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
[  3973.526] (II) Module mga: vendor="X.Org Foundation"
[  3973.526]compiled for 1.20.4, module version = 2.0.0
[  3973.526]Module class: X.Org Video Driver
[  3973.526]ABI class: X.Org Video Driver, version 24.0
[  3973.526] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, 
mga2164w,
mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-14 Thread Markus Hiereth 

Hello Felix,

could You send a Xorg.log - file that allows a comparison of the
startup procedures of the X server on your and on my system.  

Best regards
Markus
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-11 Thread Felix Miata 
Markus Hiereth composed on 2019-08-11 22:05 (UTC+0200):
...
I was able to replicate the (EE) tail of your attached log via an
/etc/X11/xorg.conf file containing the following:

Section "Monitor
...
DefaultDepth16
...
EndSection

Commenting away DefaultDepth restored normal X operation.

I suggest removing any similar line you find anywhere in /etc/X11/xorg.conf.d/*,
and if that alone is insufficient, then remove /etc/X11/xorg.conf if it exists,
and all files in /etc/X11/xorg.conf.d/ that contain any of the following lines:

Section "Device"
Section "Monitor"
Section "Screen"

whatever their filenames may be, then try.

If it still doesn't work, add the attached /etc/X11/xorg.conf verified working
here. Try it as-is first. It may need HorizSync and VertRefresh adjusted to 
match
your display. X is smart enough to auto-generate suitable modelines given
appropriate HorizSync and Vertrefresh.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
Section "Device"
Identifier "DefaultDevice"
Driver  "mga"
EndSection

Section "Monitor"
Identifier "DefaultMonitor"
VendorName  "Dell"
ModelName   "DELL 1704FPT"
HorizSync   30-81
VertRefresh 56-76
EndSection

Section "Screen"
Identifier "DefaultScreen"
Device "DefaultDevice"
Monitor "DefaultMonitor"
EndSection
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-10 Thread Felix Miata 
Markus Hiereth composed on 2019-08-10 22:27 (UTC+0200):

> [  3974.700] (II) MGA(0): VESA VBE DDC supported
> [  3974.700] (II) MGA(0): VESA VBE DDC Level none
> [  3974.700] (II) MGA(0): VESA VBE DDC transfer in appr. 0 sec.
> [  3974.844] (II) MGA(0): VESA VBE DDC read failed

I spotted another unexpected difference. Mine:
[  1679.533] (II) MGA(0): VESA VBE DDC supported
[  1679.533] (II) MGA(0): VESA VBE DDC Level 2
[  1679.533] (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec.
[  1681.106] (II) MGA(0): VESA VBE DDC read successfully

This suggests to me your problem's root could be in your display's EDID. Have 
you
tried with other displays?
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-10 Thread Felix Miata 
Markus Hiereth composed on 2019-08-10 22:27 (UTC+0200):

> Felix Miata schrieb am 10. August 2019 um 21:55

> As I annonced, I made an
> attempt with disabled DRI option for the video card, i.e. I introduced

>   Option  "DRI" "False" 

I suppose DRI support is supposed to be auto-detected but maybe is not working 
as
expected in your environments.
https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure

> in the device section of xorg.conf. The result was that the X server
> started as expected.  Below the respective logfile.

> Thus, the problem is solved though I do not know or try to imagine
> what benefits DRI "Direct rendering infrastructure" might have.

Does this PC with AGP slot and G400 have 4G or more physical RAM? If it does 
not,
as I have no AGP slot boards that support more than 2G and suspect maybe there
exists no such things, for completeness sake I would undo the DRI false option 
and
try the non-PAE kernel. See here why I make this suggestion:
https://bugzilla.opensuse.org/show_bug.cgi?id=1118689#c29

Anyway, great to know these great old GPUs remain useful for others than 
myself. :-)
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-10 Thread Felix Miata 
Markus Hiereth composed on 2019-08-10 20:24 (UTC+0200):

> Your mga module was compiled for another version of the server:

> 66c80
>> (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
> < (II) Loading /usr/local/lib/xorg/modules/drivers/mga_drv.so
> 68c82,88
> < compiled for 1.20.4, module version = 2.0.0
> ---
>>  compiled for 1.20.3, module version = 2.0.0
>>  Module class: X.Org Video Driver
>>  ABI class: X.Org Video Driver, version 24.0
>> (II) LoadModule: "modesetting"
>> (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
>> (II) Module modesetting: vendor="X.Org Foundation"
>>  compiled for 1.20.4, module version = 1.20.4

My Buster /etc/apt/sources.list:

deb http://ftp.debian.org/debian buster main contrib non-free
deb http://ftp.debian.org/debian buster-backports main
deb http://security.debian.org/ buster/updates main contrib non-free
deb http://ftp.debian.org/debian buster-updates main
deb http://mirror.xcer.cz/trinity-sb buster deps-r14 main-r14
deb-src http://mirror.xcer.cz/trinity-sb buster deps-r14 main-r14
deb http://www.deb-multimedia.org buster main non-free

I have no /usr/local/lib/xorg/* here, nor any idea how to explain my mga_drv.so
reporting compiled for 1.20.3. There is minimal corruption here at window and
panel edges, but it doesn't interfere with normal use.

Here's a fresh log, nominally larger, 691 lines instead of 683:
http://fm.no-ip.com/Tmp/Linux/Xorg/Mga/xorg.0.log-gx27c-deb10-G400-normal
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-09 Thread Felix Miata 
Markus Hiereth composed on 2019-08-09 11:35 (UTC+0200):

> could You send a Xorg.log - file that allows a comparison of the
> startup procedures of the X server on your and on my system.  

http://fm.no-ip.com/Tmp/Linux/Xorg/Mga/xorg.0.log-mga400-deb10-201908090655-0400
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-05 Thread Markus Hiereth 
Hello Marius, Adam and Xorg-Team,

for Marius: 
with some delay, I noticed Your hint to create debugging packages in
Debian. I Think I compiled the X server and the mga module successfully,
but I doubt whether the files are installed correctly. E.g. the dates of
the binaries are not in accordance with the compilation and in the case
of the binary /usr xorg-compilation See Section 1 below:

for Adam:
In Section 2 below, there is the output of and invocation of Xorg
through gdb on a remote computer 

Best regards
Markus

---
Section 1
---

Created Packages with Debugging-Information:
  hiereth@lune:~$ ls -l /home/hiereth/archiv/burn/software/built/deb-dbgsym/*
  -rw-r--r-- 1 hiereth users  5524772 Aug  2 20:20 
/home/hiereth/archiv/software/built/deb-dbgsym/xdmx-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users   213608 Aug  2 20:20 
/home/hiereth/archiv/software/built/deb-dbgsym/xdmx-tools-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users  4096636 Aug  2 20:20 
/home/hiereth/archiv/software/built/deb-dbgsym/xnest-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users  7660064 Aug  2 20:21 
/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xephyr-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users 10481176 Aug  2 20:19 
/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-core-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users 9024 Aug  2 20:22 
/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-legacy-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users   498720 Aug  2 20:31 
/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-video-mga-dbgsym_2.0.0-1_i386.deb
  -rw-r--r-- 1 hiereth users  4985344 Aug  2 20:21 
/home/hiereth/archiv/software/built/deb-dbgsym/xvfb-dbgsym_1.20.4-1_i386.deb
  -rw-r--r-- 1 hiereth users  7322820 Aug  2 20:22 
/home/hiereth/archiv/software/built/deb-dbgsym/xwayland-dbgsym_1.20.4-1_i386.deb

Check whether these packages have been installed:

  root@lune:/home/hiereth# apt install 
/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-core-dbgsym_1.20.4-1_i386.deb
 
  Paketlisten werden gelesen... 0%Paketlisten werden gelesen... 0%Paketlisten 
werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut 0%Abhängigkeitsbaum wird aufgebaut 
0%Abhängigkeitsbaum wird aufgebaut 0%Abhängigkeitsbaum wird aufgebaut 
50%Abhängigkeitsbaum wird aufgebaut 50%Abhängigkeitsbaum wird 
aufgebaut 78%Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen 0%Statusinformationen werden 
eingelesen 0%Statusinformationen werden eingelesen Fertig
  Hinweis: »xserver-xorg-core-dbgsym« wird an Stelle von 
»/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-core-dbgsym_1.20.4-1_i386.deb«
 gewählt.
  xserver-xorg-core-dbgsym ist schon die neueste Version (2:1.20.4-1).
  0 aktualisiert, 0 neu installiert, 0 zu entfernen und 47 nicht aktualisiert.

  root@lune:/home/hiereth# apt install 
/home/hiereth/archiv/software/built/deb-dbgsym/xorg-video-mga-dbgsym_2.0.0-1_i386.deb
 
  Paketlisten werden gelesen... 0%Paketlisten werden gelesen... 0%Paketlisten 
werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut 0%Abhängigkeitsbaum wird aufgebaut 
0%Abhängigkeitsbaum wird aufgebaut 0%Abhängigkeitsbaum wird aufgebaut 
50%Abhängigkeitsbaum wird aufgebaut 50%Abhängigkeitsbaum wird aufgebaut.  
 
  Statusinformationen werden eingelesen 0%Statusinformationen werden 
eingelesen 0%Statusinformationen werden eingelesen Fertig
  Hinweis: »xserver-xorg-video-mga-dbgsym« wird an Stelle von 
»/home/hiereth/archiv/software/built/deb-dbgsym/xserver-xorg-video-mga-dbgsym_2.0.0-1_i386.deb«
 gewählt.
  xserver-xorg-video-mga-dbgsym ist schon die neueste Version (1:2.0.0-1).
  0 aktualisiert, 0 neu installiert, 0 zu entfernen und 47 nicht aktualisiert.

Check whether installed binarys have debugging information (as recommended in 
debian wiki):

  root@lune:/home/hiereth# file /usr/lib/xorg/Xorg 
  /usr/lib/xorg/Xorg: ELF 32-bit LSB pie executable, Intel 80386, version 1 
(SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=a4d93c3aed64f8a3bdae2d63ea1661f3c4e672f7, stripped


Checking the date of this binaries:
  root@lune:/home/hiereth# ls -l /lib/xorg/Xorg 
  -rwxr-xr-x 1 root root 2610544 Mär  5 21:11 /usr/lib/xorg/Xorg
  ls -l /lib/modules/4.19.0-5-686-pae/kernel/drivers/gpu/drm/mga*/*
  /lib/modules/4.19.0-5-686-pae/kernel/drivers/gpu/drm/mga:
  insgesamt 36
  -rw-r--r-- 1 root root 35808 Jun 20 00:16 mga.ko
  /lib/modules/4.19.0-5-686-pae/kernel/drivers/gpu/drm/mgag200:
  insgesamt 60
  -rw-r--r-- 1 root root 57164 Jun 20 00:16

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-08-02 Thread Markus Hiereth 
Hello Xorg-Team,

yesterday, I managed to update the VGA BIOS of the graphic card (using
FreeDOS which was, in contrast to Microsoft DOS 6.2, able to execute the
ubiosdos file from the Matrox utilities) recommended by Felix and as
well updated the main board BIOS.

This did not solve the problem. The X server still fails to start (black
screen) and returns to the text terminal. The logs notice a segmentation
fault.

Attached:

a) logfile Xorg-deb10-190731a_0.log which
- logs a start attempt introduced by systemd
- uses a personal xorg.config file
- uses the mga module compiled on my own

b) logfile Xorg-deb10-190731b_0.log which
- logs a start attempt introduced by systemd
- without xorg.config file, using xorg defaults and hardware
  recognition procedures 
- uses the mga module from Debian 10

c) a diff-file between the log file with the differences between
- the start procedure with Debian 10 (after upgrading from Debian 9
  that failed with MGA driver version 1.6.5) which fails with MGA
  driver version 2.0.0 and
- the start procedure logged in logfile b

Best regards
Markus



Xorg_deb10_190731a_0.log
Description: logfile a


Xorg_deb10_190731b_0.log
Description: logfile b
1,5d0
< Diese Logdatei entstand
< - ohne manuelles Anlegen eines MTRR-Speicherbereichs
< - nach Starten des X-Servers via systemctl start xdm
< 
<  
10c5
< Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae root=UUID=aaa814b3-21a1-432d-91eb-1289958cdd6e ro quiet
---
> Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae root=/dev/sda7
19c14
< (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 15 21:07:35 2019
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 31 22:43:20 2019
44c39
< (II) Loader magic: 0x774740
---
> (II) Loader magic: 0x708740
50c45
< (++) using VT number 7
---
> (--) using VT number 4
89,90d83
< (WW) xf86OpenConsole: setpgid failed: Operation not permitted
< (WW) xf86OpenConsole: setsid failed: Operation not permitted
105,106c98,99
< (II) MGA(0): MAPPED Framebuffer DC00 200 to B524D000.
< (II) MGA(0): UNMAPPING framebuffer 0xB524D000, 0x200.
---
> (II) MGA(0): MAPPED Framebuffer DC00 200 to B52E6000.
> (II) MGA(0): UNMAPPING framebuffer 0xB52E6000, 0x200.
119c112
< (--) MGA(0): Video BIOS info block at offset 0x07A80
---
> (--) MGA(0): Video BIOS info block at offset 0x07CE0
127c120
< (II) MGA(0): MAPPED Framebuffer DC00 100 to B6231000.
---
> (II) MGA(0): MAPPED Framebuffer DC00 100 to B62CA000.
147c140
< (II) MGA(0): VESA VBE Version 2.0
---
> (II) MGA(0): VESA VBE Version 3.0
150c143
< (II) MGA(0): VESA VBE OEM Software Rev: 1.5
---
> (II) MGA(0): VESA VBE OEM Software Rev: 2.1
158c151
< (II) MGA(0): UNMAPPING framebuffer 0xB6231000, 0x100.
---
> (II) MGA(0): UNMAPPING framebuffer 0xB62CA000, 0x100.
408c401
< (II) MGA(0): MAPPED Framebuffer DC00 100 to B6215000.
---
> (II) MGA(0): MAPPED Framebuffer DC00 100 to B62AE000.
432c425
< (II) MGA(0): Start at 0xb6215000, size ffec00, osb 301000
---
> (II) MGA(0): Start at 0xb62ae000, size ffec00, osb 301000
565,566c558,559
< (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x122) [0x6a6cf2]
< (EE) 1: linux-gate.so.1 (?+0x0) [0xb7ee0d87]
---
> (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x122) [0x63acf2]
> (EE) 1: linux-gate.so.1 (?+0x0) [0xb7f7bd87]
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-31 Thread Markus Hiereth 
Hallo xorg Team,

thanks for Your hints so far, but the problem still remains.


@ Dennis

I managed to compile the source package

  
http://deb.debian.org/debian/pool/main/x/xserver-xorg-video-mga/xserver-xorg-video-mga_2.0.0.orig.tar.gz

It was necessary to replace xserver-xorg by xserver-xorg-de

  
http://ftp.de.debian.org/debian/pool/main/x/xorg-server/xserver-xorg-dev_1.20.4-1_i386.deb


@ Adam

attached is the latest logfile which was created when gdb invoked Xorg
from a remote machine. The mga driver compiled on my own has been used.



@ Felix


I tried to use the tool ubiosdos.exe in Your zip file. Maybe the drivers
are newer: For example

-r-xr-xr-x 1 32768 Jul 23  1999 897-15.bin (on the CDROM shipped with my card)
-rw-rw-rw- 1 32768 Nov 21  2000 897-21.bin (in Your zip-File)


But using ubiosdos.exe, I got the error message "Bad Command or
Filename". First I thought this was due to another directory name than
c:\matrox\util. But renaming did not change anything. Remarkably, the
tools makedisk (for creating a vga bios recovery disk) and pcispy for
diagnosis of the card do work.

For example the latter provides adresses that might be useful to flash
the bios of the video card using linux commands cat or dd

   Adresse  Size
FrameBufferAperturedc00 0200
ControlAperatureBase   dfefc000 4000
DMA Base   df00 0080
ROM Base   dfee

Thee is a second site that offers software for updating the vga bios

  http://www.opendrivers.com/download/driver-34715.html

But I suppose the newer drivers are for newer Matrox video cards. And
the executable file needs Windows instead of DOS which is not
installed on my PC.


The sources code of mga contains a file mga_bios.c that covers how to
access the BIOS of the card. 

I hope that a solution can be found.
Markus



Xorg_deb10_190729b_0.log
Description: Binary data
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-23 Thread Markus Hiereth 
Hello Adam,

Adam Jackson schrieb am 22. Juli 2019 um 20:22

> > apparently I am able to run gdb locally on my computer.   
 
> The reason I mentioned ssh is: if you start X under gdb from the
> console, the X server will switch away to a new virtual terminal while
> it initializes. Then, when it crashes, it will halt in gdb; but you
> won't be able to switch virtual terminals back to gdb, because X has
> put the vt into process mode, and is now halted under gdb so it can't
> run the code to release the vt back to the kernel.

installing the openssh-server - package made no problem. So I was able
to invoke gdb from my backup computer via ssh.

  gdb /usr/lib/xorg/Xorg

and within gdb

  run

introduced an attempt to start the X server. The logging is attached.
I do not know whether it contains a hint what is going wrong. Perhaps
the line "Cannot open /dev/tty0" are due to usage of gdb. Maybe
necessary configuration information to analyse the situation

  ~$ ls -l /dev/tty0
  crw--w 1 root tty 4, 0 Jul 22 21:46 /dev/tty0

  grep tty /etc/group
  tty:x:5:

Best regards
Markus
[   652.694] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[   652.697] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[   652.698] Current Operating System: Linux lune 4.19.0-5-686-pae #1 SMP 
Debian 4.19.37-5 (2019-06-19) i686
[   652.698] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae 
root=/dev/sda7
[   652.700] Build Date: 05 March 2019  08:11:12PM
[   652.701] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[   652.702] Current version of pixman: 0.36.0
[   652.703]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   652.704] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   652.707] (==) Log file: "/home/hiereth/.local/share/xorg/Xorg.0.log", Time: 
Mon Jul 22 21:57:01 2019
[   652.708] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   652.710] (==) No Layout section.  Using the first Screen section.
[   652.711] (==) No screen section available. Using defaults.
[   652.712] (**) |-->Screen "Default Screen Section" (0)
[   652.712] (**) |   |-->Monitor ""
[   652.716] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   652.717] (==) Automatically adding devices
[   652.718] (==) Automatically enabling devices
[   652.719] (==) Automatically adding GPU devices
[   652.720] (==) Max clients allowed: 256, resource mask: 0x1f
[   652.721] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   652.721]Entry deleted from font path.
[   652.722] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   652.723] (==) ModulePath set to "/usr/lib/xorg/modules"
[   652.724] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   652.724] (II) Loader magic: 0x678740
[   652.724] (II) Module ABI versions:
[   652.724]X.Org ANSI C Emulation: 0.4
[   652.724]X.Org Video Driver: 24.0
[   652.724]X.Org XInput driver : 24.1
[   652.724]X.Org Server Extension : 10.0
[   652.744] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_35
[   652.748] (II) xfree86: Adding drm device (/dev/dri/card0)
[   652.751] (EE) systemd-logind: failed to take device /dev/dri/card0: 
Operation not permitted
[   652.763] (--) PCI:*(1@0:0:0) 102b:0525:102b:19d8 rev 4, Mem @ 
0xdc00/33554432, 0xdfefc000/16384, 0xdf00/8388608, BIOS @ 
0x/131072
[   652.768] (II) LoadModule: "glx"
[   652.770] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   653.058] (II) Module glx: vendor="X.Org Foundation"
[   653.058]compiled for 1.20.4, module version = 1.0.0
[   653.060]ABI class: X.Org Server Extension, version 10.0
[   653.061] (==) Matched mga as autoconfigured driver 0
[   653.062] (==) Matched modesetting as autoconfigured driver 1
[   653.063] (==) Matched fbdev as autoconfigured driver 2
[   653.063] (==) Matched vesa as autoconfigured driver 3
[   653.064] (==) Assigned the driver to the xf86ConfigLayout
[   653.065] (II) LoadModule: "mga"
[   653.066] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
[   653.102] (II) Module mga: vendor="X.Org Foundation"
[   653.102]compiled for 1.20.3, module version = 2.0.0
[   653.102]Module class: X.Org Video Driver
[   653.102]ABI class: X.Org Video Driver, version 24.0
[   653.102] (II) LoadModule: "modesetting"
[   653.103] (II) Loading

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-23 Thread Markus Hiereth 
Hallo Adam


> installing the openssh-server - package made no problem. So I was able
> to invoke gdb from my backup computer via ssh.
> 
>   gdb /usr/lib/xorg/Xorg
> 
> and within gdb
> 
>   run
> 
> introduced an attempt to start the X server. The logging is attached.
> I do not know whether it contains a hint what is going wrong. Perhaps
> the line "Cannot open /dev/tty0" are due to usage of gdb. Maybe
> necessary configuration information to analyse the situation
> 
>   ~$ ls -l /dev/tty0
>   crw--w 1 root tty 4, 0 Jul 22 21:46 /dev/tty0
> 
>   grep tty /etc/group
>   tty:x:5:

an explanation for the permission problem seems to be that I was logged in with 
my normal user account, then started gdb as normal error.

In another attempt, I used su, starting gdb afterwards. Invokation of
Xorg still ends with a black screen, but the logging file differs. It
is attached here.

Best regards
Markus
[   221.168] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[   221.170] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[   221.171] Current Operating System: Linux lune 4.19.0-5-686-pae #1 SMP 
Debian 4.19.37-5 (2019-06-19) i686
[   221.172] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae 
root=/dev/sda7
[   221.174] Build Date: 05 March 2019  08:11:12PM
[   221.175] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[   221.176] Current version of pixman: 0.36.0
[   221.177]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   221.177] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   221.181] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 22 22:36:16 
2019
[   221.183] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   221.185] (==) No Layout section.  Using the first Screen section.
[   221.186] (==) No screen section available. Using defaults.
[   221.187] (**) |-->Screen "Default Screen Section" (0)
[   221.187] (**) |   |-->Monitor ""
[   221.191] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   221.192] (==) Automatically adding devices
[   221.193] (==) Automatically enabling devices
[   221.194] (==) Automatically adding GPU devices
[   221.195] (==) Max clients allowed: 256, resource mask: 0x1f
[   221.196] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   221.196]Entry deleted from font path.
[   221.198] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   221.198] (==) ModulePath set to "/usr/lib/xorg/modules"
[   221.199] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   221.199] (II) Loader magic: 0x678740
[   221.199] (II) Module ABI versions:
[   221.199]X.Org ANSI C Emulation: 0.4
[   221.199]X.Org Video Driver: 24.0
[   221.199]X.Org XInput driver : 24.1
[   221.199]X.Org Server Extension : 10.0
[   221.206] (--) using VT number 2

[   221.207] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[   221.211] (II) xfree86: Adding drm device (/dev/dri/card0)
[   221.223] (--) PCI:*(1@0:0:0) 102b:0525:102b:19d8 rev 4, Mem @ 
0xdc00/33554432, 0xdfefc000/16384, 0xdf00/8388608, BIOS @ 
0x/131072
[   221.228] (II) LoadModule: "glx"
[   221.230] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   221.511] (II) Module glx: vendor="X.Org Foundation"
[   221.512]compiled for 1.20.4, module version = 1.0.0
[   221.513]ABI class: X.Org Server Extension, version 10.0
[   221.515] (==) Matched mga as autoconfigured driver 0
[   221.515] (==) Matched modesetting as autoconfigured driver 1
[   221.516] (==) Matched fbdev as autoconfigured driver 2
[   221.517] (==) Matched vesa as autoconfigured driver 3
[   221.518] (==) Assigned the driver to the xf86ConfigLayout
[   221.519] (II) LoadModule: "mga"
[   221.520] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
[   221.555] (II) Module mga: vendor="X.Org Foundation"
[   221.555]compiled for 1.20.3, module version = 2.0.0
[   221.555]Module class: X.Org Video Driver
[   221.556]ABI class: X.Org Video Driver, version 24.0
[   221.556] (II) LoadModule: "modesetting"
[   221.556] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   221.599] (II) Module modesetting: vendor="X.Org Foundation"
[   221.599]compiled for 1.20.4, module version = 1.20.4
[   221.599]Module class: X.Org Video Driver
[   221.599]ABI class:

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-22 Thread Felix Miata 
Markus Hiereth composed on 2019-07-16 11:05 (UTC+0200):
...
I have Buster working with P4 and G400 mostly OK here. xrandr --dpi 120 cannot 
get
size of gamma for output default.

# dpkg-query -l | grep mga
ii  xserver-xorg-video-mga 1:2.0.0-1 i386 X.Org X server -- MGA display driver
# inxi -GxxSa
System:Host: gx27c Kernel: 4.19.0-5-686 i686 bits: 32 compiler: gcc v: 8.3.0
   parameters: root=/dev/sda20 ipv6.disable_ipv6=1 net.ifnames=0 
noresume mitigations=auto consoleblank=0 3
   Desktop: Trinity R14.0.7 tk: Qt 3.5.0 wm: Twin dm: startx Distro: 
Debian GNU/Linux 10 (buster)
Graphics:  Device-1: Matrox Systems MGA G400/G450 driver: N/A bus ID: 01:00.0 
chip ID: 102b:0525
   Display: tty server: X.Org 1.20.4 driver: mga unloaded: modesetting 
alternate: fbdev,vesa
   resolution: 1680x1050~60Hz
   OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
compat-v: 3.1 direct render: Yes

Which BIOS version does your G400 have? I upgraded mine to 2.1 about 10 years 
ago.
I have the software that did the upgrade if you need it. It doesn't seem 
available
from matrox.com any more.
http://fm.no-ip.com/Tmp/Hardware/Gfxcard/mgabios.zip
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-22 Thread Adam Jackson 
On Sun, 2019-07-21 at 23:05 +0200, Markus Hiereth wrote:
> 
> > If you have a second machine, can you try to launch Xorg from gdb? You
> > will need to ssh into the machine and su to root first, but gdb is
> > generally much better at decoding backtraces than either glibc's
> > backtrace function or libunwind. It should be just:
> 
> apparently I am able to run gdb locally on my computer.   

The reason I mentioned ssh is: if you start X under gdb from the
console, the X server will switch away to a new virtual terminal while
it initializes. Then, when it crashes, it will halt in gdb; but you
won't be able to switch virtual terminals back to gdb, because X has
put the vt into process mode, and is now halted under gdb so it can't
run the code to release the vt back to the kernel.

- ajax

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-22 Thread Marius Gedminas 
On Sun, Jul 21, 2019 at 11:05:35PM +0200, Markus Hiereth wrote:
> > Missing separate debuginfos, use: dnf debuginfo-install 
> > xorg-x11-server-Xorg-1.20.4-3.fc30.x86_64
> 
> The command and the package You mention seems to be related to
> rpm. Is there an equivalent package for the Debian package management?

This should be helpful:
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

HTH,
Marius Gedminas
-- 
A Law of Computer Programming:
Make it possible for programmers to write in English
and you will find that programmers cannot write in English.


signature.asc
Description: PGP signature
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-22 Thread Markus Hiereth 
Hello Adam,

Adam Jackson schrieb am 19. Juli 2019 um 19:53

> Hmph. The log shows the server mostly initializing correctly, and
> doesn't give the details about the location of the crash I was hoping
> for. I don't expect the MTRR setup failures are what's fatal here
> though.
 
> If you have a second machine, can you try to launch Xorg from gdb? You
> will need to ssh into the machine and su to root first, but gdb is
> generally much better at decoding backtraces than either glibc's
> backtrace function or libunwind. It should be just:

apparently I am able to run gdb locally on my computer.   

> # gdb /usr/libexec/Xorg
> Reading symbols from /usr/libexec/Xorg...
> (No debugging symbols found in /usr/libexec/Xorg)

I got this message too. See attached logs created with script, the
first invoking Xorg, the second using the systemd routine that starts
the x server)

> Missing separate debuginfos, use: dnf debuginfo-install 
> xorg-x11-server-Xorg-1.20.4-3.fc30.x86_64

The command and the package You mention seems to be related to
rpm. Is there an equivalent package for the Debian package management?

Thanks for your support
Markus

Script started on 2019-07-21 22:30:33+02:00 [TERM="linux" TTY="/dev/tty1" 
COLUMNS="80" LINES="25"]
root@lune:~# gdb 
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) file /usr/lib/xorg/Xorg
Reading symbols from /usr/lib/xorg/Xorg...(no debugging symbols found)...done.
(gdb) run -verbose
Starting program: /usr/lib/xorg/Xorg -verbose
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
Current Operating System: Linux lune 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5 
(2019-06-19) i686
Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686-pae root=/dev/sda7 ro 
single
Build Date: 05 March 2019  08:11:12PM
xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 21 22:31:26 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Automatically adding GPU devices
(==) Max clients allowed: 256, resource mask: 0x1f
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
(--) using VT number 3

(II) systemd-logind: logind integration requires -keeptty and -keeptty was not 
provided, disabling logind integration
(II) xfree86: Adding drm device (/dev/dri/card0)
(--) PCI:*(1@0:0:0) 102b:0525:102b:19d8 rev 4, Mem @ 0xdc00/33554432, 
0xdfefc000/16384, 0xdf00/8388608, BIOS @ 0x/131072
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.20.4, module version = 1.0.0
(==) Matched mga as autoconfigured driver 0
(==) Matched modesetting as autoconfigured driver 1
(==) Matched fbdev as autoconfigured driver 2
(==) Matched vesa as autoconfigured driver 3
(==) Assigned the driver to the xf86ConfigLayout
(II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
(II) Module mga: vendor="X.Org

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-19 Thread Adam Jackson 
On Thu, 2019-07-18 at 11:11 +0200, Markus Hiereth wrote:
> Hello Adam,
> 
> Adam Jackson  schrieb am 17. Juli 2019 um 17:06
> 
> > Try this again, but invoke the server as 'Xorg -verbose' so we can see
> > the complete set of messages being printed.
> 
> I made some more tests but I am not able to identify what log entries
> are decisive. Therefore complete logfiles attached here.
> 
> What I tried to find out is whether the X-server starts after creating
> the MTRR storage areas using a bash command echo "base=.." >|
> /proc/mtrr. It is not the case. But it reduces the number of error
> messages. Thus, probably two mtrr storage areas are involved. I also
> wonder about the meaning of the output for "count".

Hmph. The log shows the server mostly initializing correctly, and
doesn't give the details about the location of the crash I was hoping
for. I don't expect the MTRR setup failures are what's fatal here
though.

If you have a second machine, can you try to launch Xorg from gdb? You
will need to ssh into the machine and su to root first, but gdb is
generally much better at decoding backtraces than either glibc's
backtrace function or libunwind. It should be just:

# gdb /usr/libexec/Xorg
Reading symbols from /usr/libexec/Xorg...
(No debugging symbols found in /usr/libexec/Xorg)
Missing separate debuginfos, use: dnf debuginfo-install 
xorg-x11-server-Xorg-1.20.4-3.fc30.x86_64
(gdb) run -verbose
...
(gdb) bt f

Debian might install it to /usr/bin/Xorg instead, and if you get a
message like the above about installing debugging symbols, quit gdb and
install those first.

- ajax

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-17 Thread Adam Jackson 
On Tue, 2019-07-16 at 11:05 +0200, Markus Hiereth wrote:

> root@lune:~# Xorg
> 
> X.Org X Server 1.20.4
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
> Current Operating System: Linux lune 4.19.0-5-686 #1 SMP Debian 4.19.37-5 
> (2019-06-19) i686
> Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-686 
> root=UUID=aaa814b3-21a1-432d-91eb-1289958cdd6e ro quiet
> Build Date: 05 March 2019  08:11:12PM
> xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
> Current version of pixman: 0.36.0
>   Before reporting problems, check http://wiki.x.org
>   to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
>   (++) from command line, (!!) notice, (II) informational,
>   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 15 11:31:25 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86TokenToOptinfo: table is NULL
> xf86TokenToOptinfo: table is NULL
> error setting MTRR (base = 0xdc00, size = 0x0200, type = 1) 
> Invalid argument (22)
> error setting MTRR (base = 0xdc00, size = 0x0100, type = 1) 
> Invalid argument (22)
> (EE) 
> (EE) Backtrace:
> (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x122) [0x637cf2]
> (EE) 1: linux-gate.so.1 (?+0x0) [0xb7f30d57]
> (EE) 2: ? (?+0x0) [0xc000]
> (EE) unw_step failed: unspecified (general) error [-1]
> (EE) Segmentation fault at address 0xc000
> Fatal server error:
> (EE) Caught signal 11 (Segmentation fault). Server aborting
> (EE) Server terminated with error (1). Closing log file.
> Abgebrochen

Try this again, but invoke the server as 'Xorg -verbose' so we can see
the complete set of messages being printed.

- ajax

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: XOrg in Debian10/Buster not usable with AMD Duron / Matrox G400

2019-07-16 Thread Dennis Clarke 

On 7/16/19 5:05 AM, Markus Hiereth wrote:

Hello,

I updated my PC with Debian 10 which contains the package
xserver-xorg-core 2:1.20.4-1.



I also have a very old machine still running fine. It also has
a Matrox graphics PCI card and one must compile the driver for
that from the sources. At least that was what I had to do.

Otherwise it works great.


--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux support
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s