VectorLinux
April 23, 2014, 10:38:19 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: Fatal server error: caught signal 11  (Read 5282 times)
el0gic
Member
*
Posts: 3


« on: September 15, 2008, 04:00:46 am »

I'm using VL 5.9 Light on a Toshiba 7010CT laptop. It has a Neomagic video card (2.5MB).

When I first installed and booted, I was sent to a graphical login and then onto a desktop (which had inverted colours, but I'll get onto that some other time). I did some config stuff using the graphical vasm, including setting the default initial runlevel to a console login. I've fairly happily got my laptop configured and working through the console (wireless etc.). However:

Now when I startx, the server aborts. Here's some bits I pulled from /var/log/Xorg.0.log:


(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) NEOMAGIC(0): VESA VBE DDC supported
(II) NEOMAGIC(0): VESA VBE DDC Level 2
(II) NEOMAGIC(0): VESA VBE DDC transfer in appr. 1 sec.
f000:d561: 01 ILLEGAL EXTENDED X86 OPCODE!
(II) NEOMAGIC(0): VESA VBE DDC invalid
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module "i2c" already built-in
(II) NEOMAGIC(0):


Could not init font path element /usr/share/fonts/OTF, removing from list!

Backtrace:
0: X(xf86SigHandler+0x80) [0x80dbde0]
1: [0xb7ef8420]
2: X(FreeClientResources+0xa0) [0x806f5b0]
3: X(FreeAllResources+0x66) [0x806f6d6]
4: X(main+0x4c3) [0x806dde3]
5: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7cdadf8]
6: X(FontFileCompleteXLFD+0x20d) [0x806d0e1]

Fatal server error:
Caught signal 11.  Server aborting



I've tried the automated vasm x configs, and I've tried xorgconfig. I've also tried removing and installing the xorg-server package. DeLi Linux 0.72 (a 2.4 kernel) runs X fine on this laptop, so I'm really quite stuck.

Can anyone see what's wrong or has anyone had this problem before? Thanks.
Logged
caitlyn
Packager
Vectorian
****
Posts: 2839



WWW
« Reply #1 on: September 15, 2008, 04:08:51 am »

Try using the xorg.conf-fbdev file supplied with Vector Linux.  I have a different Toshiba model than you do but many Toshibas do not support VESA.  Vector Linux (and a lot of other distros) have real problems with Toshiba machines.  The fbdev conf file works well on mine.

Logged

eMachines EL-1300G desktop, 1.6GHz AMD Athlon 2650e CPU, 4GB RAM, nVidia GeForce 6150 SE video
VLocity Linux 7.0-rc1

HP Mini 110 netbook, 1.6GHz Intel Atom CPU, 2GB RAM, Intel 950 video
VL 7.0 Light
el0gic
Member
*
Posts: 3


« Reply #2 on: September 15, 2008, 05:52:35 am »

Ok, I tried fbdev, but that didn't work either. Also, after I tried it, using vasm I accidentally overwrote the xorg.conf-fbdev because xorg.conf linked to it (I was trying generic VGA, which doesn't work either).

Worse, I tried several different settings, so my xorg log file doesn't contain the fbdev error messages anymore. The jist of it was something to do with it not being able to find FBIO..something (useless, I know), but it didn't have a 'caught signal 11'.

Maybe I deleted some library at some point, because x was working straight after install. I could just reinstall, there isn't that much configuration I'd have to do again.
Logged
el0gic
Member
*
Posts: 3


« Reply #3 on: September 15, 2008, 08:08:20 am »

I reinstalled and now it works. I must have deleted something important  Roll Eyes
Logged
caitlyn
Packager
Vectorian
****
Posts: 2839



WWW
« Reply #4 on: September 21, 2008, 12:38:01 pm »

I'd still like to know what cause this but I'm glad you got it working in the end.  I'm certain there was a configuration error in x.org.  What was that error?  I still have no idea

It's a good idea to change your subject line to include [SOLVED] on the original post when something is fixed.
Logged

eMachines EL-1300G desktop, 1.6GHz AMD Athlon 2650e CPU, 4GB RAM, nVidia GeForce 6150 SE video
VLocity Linux 7.0-rc1

HP Mini 110 netbook, 1.6GHz Intel Atom CPU, 2GB RAM, Intel 950 video
VL 7.0 Light
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!