Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Starting X on a DEC Alpha
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures
View previous topic :: View next topic  
Author Message
Maquis196
n00b
n00b


Joined: 02 Apr 2003
Posts: 62
Location: London

PostPosted: Mon Feb 12, 2024 12:47 pm    Post subject: Starting X on a DEC Alpha Reply with quote

Hi, so after much compiling, and years of trying (including a bug found in the MGA driver that was fixed - thanks!), I'm struggling to actually get X running on this box.

Code:

[  1399.159] (EE) Backtrace:
[  1399.163] (EE) 0: /usr/bin/X (xorg_backtrace+0x7c) [0x2000119106c]
[  1399.163] (EE) 1: /usr/bin/X (0x20001000000+0x196518) [0x20001196518]
[  1399.167] (EE) 2: /lib/libc.so.6.1 (0x20000940000+0x485c0) [0x200009885c0]
[  1399.167] (EE) 3: /usr/lib/xorg/modules/drivers/mga_drv.so (0x200014c0000+0x1a5c0) [0x200014da5c0]
[  1399.167] (EE) 4: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x5858) [0x20001785858]
[  1399.167] (EE) 5: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x5e54) [0x20001785e54]
[  1399.167] (EE) 6: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x68a0) [0x200017868a0]
[  1399.169] (EE) 7: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x4454) [0x20001784454]
[  1399.169] (EE) 8: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x9c04) [0x20001789c04]
[  1399.171] (EE) 9: /usr/lib/xorg/modules/libexa.so (0x20001780000+0x105c8) [0x200017905c8]
[  1399.173] (EE) 10: /usr/bin/X (0x20001000000+0xf2ec0) [0x200010f2ec0]
[  1399.173] (EE) 11: /usr/bin/X (CompositePicture+0x228) [0x200010ffb88]
[  1399.175] (EE) 12: /usr/bin/X (0x20001000000+0xd65d8) [0x200010d65d8]
[  1399.176] (EE) 13: /usr/bin/X (0x20001000000+0xd0d0c) [0x200010d0d0c]
[  1399.176] (EE) 14: /usr/bin/X (ProcessWorkQueue+0x4c) [0x2000109718c]
[  1399.178] (EE) 15: /usr/bin/X (WaitForSomething+0xf4) [0x2000118d9b4]
[  1399.180] (EE) 16: /usr/bin/X (0x20001000000+0x907e0) [0x200010907e0]
[  1399.180] (EE) 17: /usr/bin/X (0x20001000000+0x95c68) [0x20001095c68]
[  1399.182] (EE) 18: /usr/bin/X (0x20001000000+0x4db58) [0x2000104db58]
[  1399.184] (EE) 19: /lib/libc.so.6.1 (0x20000940000+0x2cfb0) [0x2000096cfb0]
[  1399.185] (EE) 20: /lib/libc.so.6.1 (__libc_start_main+0xc4) [0x2000096d0f4]
[  1399.185] (EE) 21: /usr/bin/X (__start+0x38) [0x2000104dba8]
[  1399.187] (EE)
[  1399.187] (EE) Segmentation fault at address 0x0
[  1399.189] (EE)


The MGA driver appears to load, but the above happens and I'll then be unable to get the console back (on the monitor at least), serial/ssh unaffected.

Any ideas of what I could try? I've tried googling but not able to find anything similar. Happy to try another video driver, but theres not many on this platform.

Dmesg;

https://pastebin.com/GUYYepUz

xorg.log

https://pastebin.com/GXLntBrf
Back to top
View user's profile Send private message
Maquis196
n00b
n00b


Joined: 02 Apr 2003
Posts: 62
Location: London

PostPosted: Tue Feb 13, 2024 12:43 pm    Post subject: Reply with quote

Advice on IRC was to recompile with some debug flags to raise issue with upstream.

This included an upgrade to xorg-server but alas the segfault no longer happens, still a blank screen to the point the monitor turns off; new Xorg.log is here

https://pastebin.com/Tmzdv45m
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 53951
Location: 56N 3W

PostPosted: Tue Feb 13, 2024 2:09 pm    Post subject: Reply with quote

Maquis196,

Your log says
Code:
[code][   133.964] (==) Matched mga as autoconfigured driver 0
[   133.965] (==) Matched modesetting as autoconfigured driver 1
[   133.965] (==) Matched fbdev as autoconfigured driver 2[/code]
...
[   134.072] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   134.074] (WW) Falling back to old probe method for modesetting
[   134.074] (EE) open /dev/dri/card0: No such file or directory

Its truncated too, which suggest bad things happened.

Generally (EE) open /dev/dri/card0, means Xorg cannot work. Certainly, modesetting, which is your fallback Xorg driver cannot work.
As I've never used MGA, I don't know if in needs DRM kernel support or not. That's one for #gentoo-alpha

Your GPU is
Code:
[   133.671] (--) PCI:*(0@0:9:0) 102b:0519

That's
Quote:
a vendor: 102b ("Matrox Electronics Systems Ltd."), device: 0519 ("MGA 2064W [Millennium]")

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Maquis196
n00b
n00b


Joined: 02 Apr 2003
Posts: 62
Location: London

PostPosted: Thu Feb 15, 2024 12:37 pm    Post subject: Reply with quote

So irony is, using my regular `make.conf` settings, I get a segfault. When I recompile with my `debug.conf` settings. It doesn't segfault; it doesn't work either so still need to solve why I'm getting a blank screen. So once I get X working I'll revisit the segfault issue.

debug.conf
Code:

CFLAGS="-mieee -O0 -ggdb3 -pipe"
CXXFLAGS="${CFLAGS}"
FEATURES="nostrip installsources"


make.conf

Code:

CFLAGS="-mieee -pipe -O2 -mcpu=pca56"
CXXFLAGS="${CFLAGS}"
CHOST="alpha-unknown-linux-gnu"
USE="-ldap -gnome -kde -minimal -qt4 -ssp dbus jpeg lock session startup-notification thunar X bindist gudev udev flac mp3 vorbis alsa opengl elogind"

## Global features, ccache is enabled per package
FEATURES="distcc"

L10N="en-GB en"
INPUT_DEVICES="evdev"
VIDEO_CARDS="mga"

CCACHE_SIZE="5G"
CCACHE_DIR="/var/cache/ccache"

PORTDIR="/usr/portage"
MAKEOPTS="-j17"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"
ACCEPT_KEYWORDS="~alpha"


lastest Xorg log is https://pastebin.com/JxzvjWzD

Still just a blank screen where the monitor goes into sleep mode, but from the logs you'd never know.

huh, wonder if the env file is removing the mcpu flag... I'll have to run more experiments on that.


Last edited by Maquis196 on Thu Feb 15, 2024 7:41 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 53951
Location: 56N 3W

PostPosted: Thu Feb 15, 2024 7:39 pm    Post subject: Reply with quote

Maquis196,

The log is truncated. That means that something horrible happened, like it crashed and logging could not continue.
After you try to start Xorg, what is at the end of dmesg?

You will need to log in over ssh or use a serial console to see that.
Its unlikely the VT switching will work.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Maquis196
n00b
n00b


Joined: 02 Apr 2003
Posts: 62
Location: London

PostPosted: Thu Feb 15, 2024 7:48 pm    Post subject: Reply with quote

Yep, have both serial and ssh up.

So without the crashing, and running `X -configure` I also get more from the Xorg.0.log ;

Code:

[   166.314] (II) MGA(0): VESA BIOS detected
[   166.317] (II) MGA(0): VESA VBE Version 2.0
[   166.317] (II) MGA(0): VESA VBE Total Mem: 2048 kB
[   166.317] (II) MGA(0): VESA VBE OEM: Matrox Graphics Inc.
[   166.317] (II) MGA(0): VESA VBE OEM Software Rev: 2.2
[   166.317] (II) MGA(0): VESA VBE OEM Vendor: Matrox
[   166.317] (II) MGA(0): VESA VBE OEM Product: MILLENNIUM
[   166.319] (II) MGA(0): VESA VBE OEM Product Rev: 00
[   167.380] (II) MGA(0): VESA VBE DDC supported
[   167.382] (II) MGA(0): VESA VBE DDC Level none
[   167.383] (II) MGA(0): VESA VBE DDC transfer in appr. 0 sec.
[   169.088] (II) MGA(0): VESA VBE DDC read failed


but I think it fails to pick up what my monitor can do/monitor at all since I have;

Code:

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        SubSection "Display"
                Viewport   0 0
                Depth     1
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     4
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     8
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     15
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection


but I have some kind of xorg.conf to play around with now[/code]
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 53951
Location: 56N 3W

PostPosted: Thu Feb 15, 2024 8:03 pm    Post subject: Reply with quote

Maquis196,

Code:
[   169.088] (II) MGA(0): VESA VBE DDC read failed


That means that Xorg tried to read your display capabilities and failed.
Its been a long time since I've seen that. It's not a fatal error. Xorg goes on to use 640x480@60Hz unless you provide a
Code:
Section "Monitor"

See
Code:
man xorg.conf


Being old and cynical, I don't have any autoblackmagic at all.
My /etc/X11/xorg.conf started life in 1999 and has accumulated a lot of cruft but it works for me today.
You may find odd fragments useful.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum