Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Xorg fatal server error segmentation fault i686

31 views
Skip to first unread message

Richmond

unread,
May 5, 2021, 8:10:05 AM5/5/21
to
I installed debian on an old PC i686. I chose the mate desktop. When I
tried to log in throught display manager I could not, so:

I closed X down with telinit 3
I logged in on the console as root
I ran xinit -- :0
I switched to a non root user in the xterm window on the display
I typed export DISPLAY=:0
I ran mate-session
X crashed with a segmentation fault

The backtrace is on the console so I cannot cut and paste it. It says it
is in Xorg at _start+0x31

What can I do? Perhaps use a different xserver. The display driver is
nouveau.

Dan Ritter

unread,
May 5, 2021, 8:30:04 AM5/5/21
to
I wouldn't expect that to segfault, but I also wouldn't expect
it to work -- you did not authorize your non-root user to run in
that X session.

Try this:

As your non-root user, write a .xinitrc:

#!/bin/sh
xterm &
exec mate-session

and then run

startx

Tell us what happens then. If it crashes, let us see your
/etc/apt/sources.list and anything in sources.list.d/

-dsr-

Greg Wooledge

unread,
May 5, 2021, 8:30:04 AM5/5/21
to
On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote:
> As your non-root user, write a .xinitrc:
>
> #!/bin/sh
> xterm &
> exec mate-session
>
> and then run
>
> startx
>
> Tell us what happens then. If it crashes, let us see your
> /etc/apt/sources.list and anything in sources.list.d/

In addition to this:

1) Identify your video hardware. Use "lspci -nn" for this.

2) Check for any missing firmware. Use "dmesg | grep -i firmware" for
this.

If there are any missing firmware files that the kernel wants to use,
figure out which (non-free) package they're in, install that, and
reboot.

The OP mentioned "nouveau", which means an nvidia device is in play. This
means it may also be necessary to install some proprietary nvidia drivers.
We won't know for sure until we know which device it is.

Richmond

unread,
May 5, 2021, 9:00:04 AM5/5/21
to
Richmond <rich...@criptext.com> writes:

> I installed debian on an old PC i686. I chose the mate desktop. When I
> tried to log in throught display manager I could not, so:
>
> I closed X down with telinit 3
> I logged in on the console as root
> I ran xinit -- :0
> I switched to a non root user in the xterm window on the display
> I typed export DISPLAY=:0
> I ran mate-session
> X crashed with a segmentation fault
>
> The backtrace is on the console so I cannot cut and paste it. It says it
> is in Xorg at _start+0x31

I think that was start_

>
> What can I do? Perhaps use a different xserver. The display driver is
> nouveau.

I am currently using icewm manager instead but would rather use Mate.

Richmond

unread,
May 5, 2021, 10:20:05 AM5/5/21
to
It crashed. The errors on the console are several fatal errors from
mate-panel, marco, mate-session, and xterm. The xorg log shows a
segmentation fault but I cannot be sure when it happened as the date is
in an inhuman format.

I'll bet it is to do with desktop effects.

Here is the sources.list. There is nothing in sources.d. I don't
understand this file because I installed from the DVD-1, and I am using an
i686. After the installation I commented out the second cdrom line
because it was prompting me when I tried to install software. The first
line was already commented out. During the installation I enabled online
repos so that it would be up to date.



====================
#

# deb cdrom:[Debian GNU/Linux 10.8.0 _Buster_ - Official amd64 NETINST 20210206-10:34]/ buster main

# deb cdrom:[Debian GNU/Linux 10.8.0 _Buster_ - Official amd64 NETINST 20210206-10:34]/ buster main

deb http://deb.debian.org/debian/ buster main contrib non-free
deb-src http://deb.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main
deb-src http://security.debian.org/debian-security buster/updates main

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main
deb-src http://deb.debian.org/debian/ buster-updates main

deb http://deb.debian.org/debian buster-backports main

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Richmond

unread,
May 5, 2021, 10:30:05 AM5/5/21
to
Scrap the previous /etc/apt/sources I forgot I was using ssh into a
different pc.

cat /etc/apt/sources.list
#

# deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary-1 20210327-10:50]/ buster contrib main

# deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary-1 20210327-10:50]/ buster contrib main
deb-src http://deb.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main contrib
deb-src http://security.debian.org/debian-security buster/updates main contrib

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main contrib
deb-src http://deb.debian.org/debian/ buster-updates main contrib

Dan Ritter

unread,
May 5, 2021, 10:50:04 AM5/5/21
to
Richmond wrote:
> Dan Ritter <d...@randomstring.org> writes:
>
> > Richmond wrote:
> >> I installed debian on an old PC i686. I chose the mate desktop. When I
> >> tried to log in throught display manager I could not, so:
...
> >> What can I do? Perhaps use a different xserver. The display driver is
> >> nouveau.
> >
> > I wouldn't expect that to segfault, but I also wouldn't expect
> > it to work -- you did not authorize your non-root user to run in
> > that X session.
>
> It crashed. The errors on the console are several fatal errors from
> mate-panel, marco, mate-session, and xterm. The xorg log shows a
> segmentation fault but I cannot be sure when it happened as the date is
> in an inhuman format.
>
> I'll bet it is to do with desktop effects.
>
> Here is the sources.list. There is nothing in sources.d. I don't

Good, we're making progress. Time to chase down Greg's idea,
which is that you have driver problems.

Answer his questions about lspci and such, and check for the
installation of

firmware-misc-nonfree

You probably need that for your graphics card, and it probably
needs a full reboot after.

-dsr-

Richmond

unread,
May 5, 2021, 11:00:04 AM5/5/21
to
Greg Wooledge <gr...@wooledge.org> writes:

> On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote:
>> As your non-root user, write a .xinitrc:
>>
>> #!/bin/sh
>> xterm &
>> exec mate-session
>>
>> and then run
>>
>> startx
>>
>> Tell us what happens then. If it crashes, let us see your
>> /etc/apt/sources.list and anything in sources.list.d/
>
> In addition to this:
>
> 1) Identify your video hardware. Use "lspci -nn" for this.

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
[GeForce2 MX/MX 400] [10de:0110] (rev b2)

>
> 2) Check for any missing firmware. Use "dmesg | grep -i firmware" for
> this.
>

No output.

Greg Wooledge

unread,
May 5, 2021, 11:20:05 AM5/5/21
to
On Wed, May 05, 2021 at 03:31:25PM +0100, Richmond wrote:
> > 1) Identify your video hardware. Use "lspci -nn" for this.
>
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
> [GeForce2 MX/MX 400] [10de:0110] (rev b2)

OK. This is... a rather old device.

<https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_10_.22Buster.22>
has instructions for three different proprietary nvidia drivers.
The problem is I don't know which one you need. You may just need
to try all three, one at a time, and see what happens.

Or else look for this nvidia detection script that I've heard about
in the past, which is supposed to tell you.

There are links to lists of supported devices, and yours is listed under
the section that says it's supported by something called the "96.43.xx"
driver, but I do not know how that designation maps to any of the three
different Debian package names for nvidia drivers.

Richmond

unread,
May 5, 2021, 11:30:04 AM5/5/21
to
I managed to get mate working after a fashion by installing mate-tweaks,
then changing the window manager to marco nocompositor. So mate works,
but there was nothing on the panel so I had to add a menu.

Brad Rogers

unread,
May 5, 2021, 11:30:05 AM5/5/21
to
On Wed, 05 May 2021 15:31:25 +0100
Richmond <rich...@criptext.com> wrote:

Hello Richmond,

>01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
>[GeForce2 MX/MX 400] [10de:0110] (rev b2)

As mentioned by Greg;

On Wed, 5 May 2021 11:14:44 -0400
Greg Wooledge <gr...@wooledge.org> wrote:
>Or else look for this nvidia detection script that I've heard about
>in the past, which is supposed to tell you.

The package you'll need is nvidia-detect. It runs from the command
line (simply; nvidia-detect) and gives an output which includes a
recommendation as to which suite of packages to use (i.e. current, or
one of the legacy packages).

As an example;

brad@earth:~$ nvidia-detect
Detected NVIDIA GPUs:
07:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116
[GeForce GTX 1650 SUPER] [10de:2187] (rev a1)

Checking card: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev
a1) Your card is supported by the default drivers.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
It is recommended to install the
nvidia-driver
package.



--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
All these things are mine!
Money is Not Our God - Killing Joke

Richmond

unread,
May 5, 2021, 2:00:04 PM5/5/21
to
I have added non-free contrib to sources but there does not seem to be a
package called nvidia-detect for this architecture. There is such a
package on a laptop I have but that is 64 bit.

I think the driver is this one:

https://www.nvidia.co.uk/Download/driverResults.aspx/1252/en-uk

But I don't want to risk installing it from there.

Certainly I have used an nvidia driver on the PC many years ago with
opensuse but they don't support 32 bit anymore except with tumbleweed
and that doesn't include nvidia driver installation.

Brad Rogers

unread,
May 5, 2021, 2:20:04 PM5/5/21
to
On Wed, 05 May 2021 18:36:50 +0100
Richmond <rich...@criptext.com> wrote:

Hello Richmond,

>package called nvidia-detect for this architecture.

Oops, I'm sorry - you're right - I didn't check properly.

Again, sorry about getting your hopes up.

--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Well I don't want you to think I'm being obscene
Fish - The Damned

Felix Miata

unread,
May 5, 2021, 11:40:05 PM5/5/21
to
Richmond composed on 2021-05-05 12:49 (UTC+0100):
I use nouveau kernel driver, modesetting X driver:
# inxi -CGISxxy
System:
Host: gx27c Kernel: 4.19.0-16-686 i686 bits: 32 compiler: gcc v: 8.3.0
Desktop: Trinity R14.0.10 tk: Qt 3.5.0 wm: Twin dm: TDM
Distro: Debian GNU/Linux 10 (buster)
CPU:
Info: Single Core model: Intel Pentium 4 bits: 32 type: MCP
arch: Netburst Northwood rev: 9 cache: L1: 8 KiB L2: 512 KiB
flags: pae sse sse2 bogomips: 4788
Speed: 2394 MHz min/max: N/A Core speed (MHz): 1: 2394
Graphics:
Device-1: NVIDIA NV11 [GeForce2 MX/MX 400] vendor: Palit Microsystems
driver: nouveau v: kernel bus-ID: 01:00.0 chip-ID: 10de:0110
Display: x11 server: X.Org 1.20.4 driver: loaded: modesetting
resolution: 1680x1050~60Hz s-dpi: 96
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
compat-v: 3.1 direct render: Yes
Info:
Processes:...Shell: Bash v: 5.0.3 running-in: konsole inxi: 3.3.04
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata *** http://fm.no-ip.com/
0 new messages