Re: Xorg fatal server error segmentation fault i686

Richmond composed on 2021-05-05 12:49 (UTC+0100): > 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 ro

Re: Xorg fatal server error segmentation fault i686

Dan Ritter 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: >> >> 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

Re: Xorg fatal server error segmentation fault i686

On Wed, 05 May 2021 18:36:50 +0100 Richmond 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

Re: Xorg fatal server error segmentation fault i686

Brad Rogers writes: > On Wed, 05 May 2021 15:31:25 +0100 > Richmond 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 wrote:

Re: Xorg fatal server error segmentation fault i686

Dan Ritter writes: > Richmond wrote: >> Dan Ritter 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 displ

Re: Xorg fatal server error segmentation fault i686

On Wed, 05 May 2021 15:31:25 +0100 Richmond 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 wrote: >Or else look for this nvidia detection

Re: Xorg fatal server error segmentation fault i686

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.

Re: Xorg fatal server error segmentation fault i686

Greg Wooledge 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.l

Re: Xorg fatal server error segmentation fault i686

Richmond wrote: > Dan Ritter 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. > >

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

Richmond 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

Re: Xorg fatal server error segmentation fault i686

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/ I

Re: Xorg fatal server error segmentation fault i686

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: > > 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 t

Xorg fatal server error segmentation fault i686

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 DISPL

[SOLVED] Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

I believe the problem comes from an incompatibility between FGLRX version 12-4-1 and xorg 1.12. I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1. Make sure to downgrade the input packages too. Thanks for the feedback. Will try out and feedback the result. Hi Issa

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On 06/11/2012 06:01 AM, Issam Mehssani wrote: I believe the problem comes from an incompatibility between FGLRX version 12-4-1 and xorg 1.12. I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1. Make sure to downgrade the input packages too. Thanks for the feedback. Wil

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

Hi, I believe the problem comes from an incompatibility between FGLRX version 12-4-1 and xorg 1.12. I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1. Make sure to downgrade the input packages too.

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

Hi, Is this bug (Bug#665000: SUMO2: blank screen after load "radeon" module) related to my issue? As I am using Sumo chip too AMD Llano A6-3670 APU with Radeon(tm) HD Graphics stepping 00 root@szechuan:~#: dmesg | grep -i sumo [ 7.451590] [drm] initializing kernel modesetting (SUMO 0x1002:0x9

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On Mon, May 21, 2012 at 09:27:32AM +0800, Hor Jiun Shyong wrote: > >grep -v \^# /etc/inittab [output same as mine] Can't see anything different there. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppr

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

grep -v \^# /etc/inittab id:2:initdefault: si::sysinit:/etc/init.d/rcS ~~:S:wait:/sbin/sulogin l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 z6:6:res

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On Mon, May 21, 2012 at 01:34:59AM +1200, Chris Bannister wrote: > On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote: > > I checked and noticed the default runlevel under inittab is 5. (I > > must have changed it for reason I can't remember now).I have > > changed it back to run

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote: > I checked and noticed the default runlevel under inittab is 5. (I > must have changed it for reason I can't remember now).I have > changed it back to run level 2 and will try the ati driver again to > see if the problem still p

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On Thu, 17 May 2012 12:14:01 +0800, Hor wrote in message <4fb47b09.9080...@gmail.com>: > Is amd-driver-installer-12-4-x86.x86_64.run driver the same with the > non free debianised fglrx driver ? > amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961 ..I dunno, I only use the fre

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

Is amd-driver-installer-12-4-x86.x86_64.run driver the same with the non free debianised fglrx driver ? amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961 lspci result under amd-driver-installer-12-4-x86.x86_64.run driver: Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VG

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On 05/16/2012 01:23 AM, Indulekha wrote: Maybe something (like /etc/inittab) got edited, and tty7 was repurposed for a getty? It's important to leave tty7 alone or X won't run. Also if inittab did get edited, could be you're calling a getty that isn't installed... I checked and noticed the

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

Hi, ..this isn't a kernel panic? What happens _immediately_before_ your blinking dash? Kernel is able to boot up. ..this is relevant only if it was written between your boot and your blinking dash. Yes it is so. ..your Xorg log is "gnome 3 under fallback mode"? Yes ..first

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

On Tue, 15 May 2012 21:03:12 +0800, Hor wrote in message <4fb25410.5050...@gmail.com>: > Hi All, > > Would be grateful if anyone could provide feedback on the below, > thanks. > > After installing proprietary driver > amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console > and X

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

an provide a more > > insightful view on this issue :-) > > > > > After installing proprietary driver > > > amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console and > > > X cannot be started. All was left after booting is a blinking "-"

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

; amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console and > > X cannot be started. All was left after booting is a blinking "-" > > prompt. Xorg log as below. > > Let me move up the fatal error: > > > [ 312.888] Fatal server error: > > [ 3

Re: Fatal server error: xf86OpenConsole: Cannot find a free VT

a blinking "-" > prompt. Xorg log as below. Let me move up the fatal error: > [ 312.888] Fatal server error: > [ 312.888] xf86OpenConsole: Cannot find a free VT > [ 312.888] > [ 312.888] That's weird... It's like the xserver is not able to allocate a virtu

Fatal server error: xf86OpenConsole: Cannot find a free VT

312.881] Module class: X.Org Video Driver [ 312.881] (II) Loading sub module "fglrxdrm" [ 312.881] (II) LoadModule: "fglrxdrm" [ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so [ 312.881] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."

Fatal server error: xf86OpenConsole: Cannot find a free VT

312.881] Module class: X.Org Video Driver [ 312.881] (II) Loading sub module "fglrxdrm" [ 312.881] (II) LoadModule: "fglrxdrm" [ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so [ 312.881] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc.&quo

Re: Fatal server error: no screens found - Xfree86 Problems

Hello Scott Barlow (<[EMAIL PROTECTED]>) wrote: > I am a reasonable newbie to Debian and have been trying unsucceffully > to get X (specifically kde) working on my box. I have modified the > XF86Config-4 file through the dpkg-reconfigure xserver-xfree86 command > but am having no luck. > [...]

Re: Fatal server error: no screens found - Xfree86 Problems

On Wed, 06 Oct 2004 16:01:06 +1000, Scott Barlow <[EMAIL PROTECTED]> wrote: > Hi, > > I am a reasonable newbie to Debian and have been trying unsucceffully to get > X > (specifically kde) working on my box. I have modified the XF86Config-4 file > through the dpkg-reconfigure xserver-xfree86 comman

Fatal server error: no screens found - Xfree86 Problems

(II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (**) NV(0): O

Re: Fatal server error

Hello Gruessle (<[EMAIL PROTECTED]>) wrote: > I get this > > Fatal server error: > no screens found > > Trying to start startx If you want to ask a question on the list, please write a new mail from scratch instead of answering to an existing message. If you want h

Re: Fatal server error

"Gruessle" <[EMAIL PROTECTED]> said on Sun, 14 Dec 2003 23:34:16 -0800: > > > I get this > > Fatal server error: > no screens found > > Trying to start startx > > Thank you That's OK. Um, thank me for what exactly? Oh, BTW - you migh

Fatal server error

I get this Fatal server error: no screens found Trying to start startx Thank you -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: fatal server error: no screens found (SOLVED)

nd have just completed a fresh install of unstable. > >When xdm (or gdm) are launched, they display a black screen 3 times and then fail. When startx is launched it also fails. The error I receive is: > >(EE) Screen(s) found, but none have a usable configuration. >Fatal server error: &

Re: fatal server error: no screens found (closer)

lack screen 3 times and then fail. When startx is launched it also fails. The error I receive is: > >(EE) Screen(s) found, but none have a usable configuration. >Fatal server error: >no screens found > login as root run XFree86 -configure A working XF86Config file should now be

Re: fatal server error: no screens found

launched, they display a black screen 3 times and then >fail. When startx is launched it also fails. The error I receive is: > >(EE) Screen(s) found, but none have a usable configuration. >Fatal server error: >no screens found > login as root run XFree86 -configure A working XF86Conf

Re: fatal server error: no screens found

On Mon, Mar 11, 2002 at 01:23:31PM -0500, timothy bauscher wrote: > > I have run xf86config and xf86cfg with different resolutions and color > depths, but I still end up with the same error. > > Any help would be appreciated, I have run out of ideas. > Make sure you have xserver-xfree86 insta

fatal server error: no screens found

also fails. The error I receive is: (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found I have run xf86config and xf86cfg with different resolutions and color depths, but I still end up with the same error. Any help would be appreciated, I have run out

Re: Fatal server error: Number Nine I128 and XF86 4.1.0

High, On Wed, 9 Jan 2002, Sebastian Canagaratna wrote: > Hi: > > I am having a fatal server error with XFree86 4.1.0 with my > Number Nine Imagine I128 Card. > > Section "Device" > ### Available Driver options are:- > ### Values: :

Fatal server error: Number Nine I128 and XF86 4.1.0

Hi: I am having a fatal server error with XFree86 4.1.0 with my Number Nine Imagine I128 Card. The specifications of the card are: Chip Set Cirrus CL-GD5424 Memory 512 RAMDAC Cirrus Logic Built-in 15/16/24-Bit DAC (6-Bit wide-loop) Attached

Re: XFree86: Fatal Server error

On Tue, Dec 11, 2001 at 12:30:28PM -0500, Branden Robinson wrote: > Some font package -- and no one has yet been able to figure out which > one -- is apparently managing to clobber the > /usr/X11R6/lib/X11/fonts/misc/fonts.alias file. The xawtv package drops three fonts into /usr/X11R6/lib/X11/fon

Re: XFree86: Fatal Server error

On Tue, Dec 11, 2001 at 07:21:00PM +0100, Scott H. Hawley wrote: > Thanks very much. I followed your advice, and I did some further checking > in hopes of finding this rogue package to no avail. > > I have tried removing xfonts-base and re-installing it, to no avail. > I even removed everythi

Re: XFree86: Fatal Server error

Branden, Thanks very much. I followed your advice, and I did some further checking in hopes of finding this rogue package to no avail. I have tried removing xfonts-base and re-installing it, to no avail. I even removed everything in the /usr/X11R6/lib/X11/fonts/misc/ directory. I removed all

Re: XFree86: Fatal Server error

On Tue, Dec 11, 2001 at 06:07:28PM +0100, Scott H. Hawley wrote: > I just installed XFree86 in a new installation of Debain (testing). > When I try to run it XFree86, I get an error: > > Fatal server error > could not open default font 'fixed' > > I've inst

XFree86: Fatal Server error

I just installed XFree86 in a new installation of Debain (testing). When I try to run it XFree86, I get an error: Fatal server error could not open default font 'fixed' I've installed the xfonts-base (and of course xfree86-common) but I'm still not having any luck. I look

Re: fatal server error

R/usr/X11R6/lib/X11/xkb -xkm -m > us -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml > "Errors from xkbcomp are not fatal to the X server" keymap/xfree86 > /var/tmp/xfree86.xkm' > > Fatal server error: > Cannot op

fatal server error

quot; -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" keymap/xfree86 /var/tmp/xfree86.xkm'   Fatal server error: Cannot open mouse (No such file or directory)   When I did xf86config, I used the default for the mouse(/dev/mouse) but when I use mc to find i

Re: startx - Fatal server error

I agree on Karasten's analysys but I would do slightly different. I usually install gpm daemon too (Typical default potato install). Then using repeater device as imput to X may be better, IMO. If mouse hanges for any reason, you can restart gpm to reinitialize it. Try it by unplugging it, if you

Re: startx - Fatal server error

on Sat, Apr 14, 2001 at 12:43:43PM -0500, George M. Butler ([EMAIL PROTECTED]) wrote: > Hi all, > > I am sure this is an old one too. But I just installed Debian > (potato) r2. I issue startx at the commnand line and get > > fatal sever error > Can't open mouse (no such file or directory ) >

Re: startx - Fatal server error

I don't know if this will work, but in the config file you could try putting /dev/psaux instead of /dev/mouse Just a thought Terry On Sat, Apr 14, 2001 at 12:43:43PM -0500, George M. Butler babbled: > Hi all, > > I am sure this is an old one too. But I just installed Debian (potato) > r2. > I

startx - Fatal server error

Hi all, I am sure this is an old one too. But I just installed Debian (potato) r2. I issue startx at the commnand line and get fatal sever error Can't open mouse (no such file or directory ) I have run xf86config 4 times now and each time I select 4, the PS/2 mouse, the 3 button emulation, and

Re: Fatal Server Error: No Valid Modes Found

ton wrote: >> >> When passing command 'startx', receive following error message: >> Fatal Server Error: No Valid Modes Found > >[...] > >> (--) FBDev: Mode "1024x768" needs hsync freq of 70.24 kHz. Deleted. > >[...] > >> HorizSync 3

Re: XFree86 - Fatal Server Error: could not open default font 'fixed'

> since I upgraded to the X3.3.6-11 version X started complaining about this > and won't run!! Any idea about what could be causing this ? Just download the fonts file and unpack it in the fonts directory. I think the font that you need should be in the misc directory. I had this problem two da

XFree86 - Fatal Server Error: could not open default font 'fixed'

hi, since I upgraded to the X3.3.6-11 version X started complaining about this and won't run!! Any idea about what could be causing this ? thanks very much for any help :-) jan ps.: I tried 'mkfontdir' again in all font directories, I checked permissions, I'm using exactly the same configurat

re: Re: fatal server error!

-Original Message- From: Bob Nielsen <[EMAIL PROTECTED]> To: rod peters <[EMAIL PROTECTED]> Cc: debian Date: Saturday, January 30, 1999 2:10 PM Subject: Re: fatal server error! >X was split up into more packages, which don't get installed during an >upgrade (th

Re: fatal server error!

handling; information is available in xbase's README.Debian (hmm, I don't seem to have this file, although 'dpkg -L xbase' says I do!) In short, you will need to install some additional packages, notably xfonts-base. Bob On Sat, 30 Jan 1999, rod peters wrote: > Cripes! &

fatal server error!

Cripes!    fatal server error: could not open default font 'fixed' _X11TransSocketUNIXConnect:  can't connect: errno = 111 giving up.   xinit: connection refused (errno 111): unable to connect to X server   xinit: no such process (errno 3): server error     I just upgraded t

Fatal server error - cannot open mouse

Hi all, I have a problem starting X. It gives the following error: Fatal server error: Cannot open mouse (Operation not supported by device) This is the relevant section from /etc/X11/XF86Config: Section "Pointer" Protocol "Microsoft" Devi

Re: Fatal Server error

On Mon, 16 Feb 1998, K.Y.Lo wrote: : Hi : : I have a problem with X-windows setup. : : Fatal Server error: : Cannot open mouse (I/O error) : : Help me! : : I have MS mouse (serial port). Should I use insmod to set mouse on? Did you configure X correctly? And does the device for

Fatal Server error

Hi I have a problem with X-windows setup. Fatal Server error: Cannot open mouse (I/O error) Help me! I have MS mouse (serial port). Should I use insmod to set mouse on? -- Cheers K.Y.Lo Email: [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscrib

Re: HELP: FATAL SERVER ERROR

the X server keeps its "socket" (the connection point for new X programs which want to display on your screen), the new xterm you started could not connect to that socket, and so could not display itself on your screen, instead bombing out without being able to tell you what was

Re: HELP: FATAL SERVER ERROR

"Albert Hurd" <[EMAIL PROTECTED]> writes: > It began with a cd to /tmp and then a rm -r /tmp. I then wanted to cd ~ but > did cd ` byy mistake. You removed your /tmp dir. The Xserver (and other programms) save temporary data in it, so you get into problems as you saw by yourself. If you want to

Re: HELP: FATAL SERVER ERROR

Albert Hurd wrote: > Could anyone tell me what happened and how to recover. Thanhs so much. As root: mkdir /tmp chmod 1777 /tmp -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .

HELP: FATAL SERVER ERROR

hen rebooted and got the the following when I tried startx: Fatal server error: Could not create lock file in /tmp/.tX-lock -X11TransSockeetUNIXConnect: Can't connect: errno=2 xinit: No such file or directory (errno=2): unable to

Re: Fatal server error

"K.Y.Lo" wrote: >Hi > >I have installed Debian 1.3.1.r6 with X-windows package. > >install xbase,xlib6,xfntbase, xserver-svga into harddisc. done >and set up xf86config. it went bummer. > >Fatal server error: >No valid modes found. >

Fatal server error

Hi I have installed Debian 1.3.1.r6 with X-windows package. install xbase,xlib6,xfntbase, xserver-svga into harddisc. done and set up xf86config. it went bummer. Fatal server error: No valid modes found. what does that mean? it is something missing the X package? mine is 486DX4 with 16mb and

Re: Fatal server error: xf86OpenConsole: Server must be run as root

On Fri, 5 Sep 1997 [EMAIL PROTECTED] wrote: > Karsten Bolding writes: > > > > Hi > > > > Just installed a new machine and updated my old one, so same versions on > > both. > > > > When I try to start x (startx) as a normal user on the new m

Re: Fatal server error: xf86OpenConsole: Server must be run as root

On Fri, 05 Sep 1997 08:36:27 EDT [EMAIL PROTECTED] wrote: > Karsten Bolding writes: > > > > When I try to start x (startx) as a normal user on the new machine I get: > [snip] > > Fatal server error: > > xf86OpenConsole: Server must be run as root > > Easi

Re: Fatal server error: xf86OpenConsole: Server must be run as root

Karsten Bolding writes: > > Hi > > Just installed a new machine and updated my old one, so same versions on both. > > When I try to start x (startx) as a normal user on the new machine I get: [snip] > Fatal server error: > xf86OpenConsole: Server must be run as root

Re: Fatal server error: xf86OpenConsole: Server must be run as root

video7, ct65520, ct65525, ct65530, ct65535, > ct65540, ct65545, ct65546, ct65548, ct65550, ct65554, ct64200, > ct64300, ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek, > AP6422, AT24, s3_virge, generic > > Fatal server error: > xf86OpenConsole: Serv

Re: Fatal server error: xf86OpenConsole: Server must be run as root

> Fatal server error: > xf86OpenConsole: Server must be run as root [EMAIL PROTECTED](p2):bhmit1$ find /usr/X11R6 -perm +4000 /usr/X11R6/bin/xterm /usr/X11R6/bin/X /usr/X11R6/bin/rxvt-xpm /usr/X11R6/bin/rxvt-debian I'd check /usr/X11R6/bin/X first, but I'd be extremely

Fatal server error: xf86OpenConsole: Server must be run as root

, generic Fatal server error: xf86OpenConsole: Server must be run as root When reporting a problem related to a server crash, please send the full server output, not just the last messages _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up. xinit: Connection refused (errno 111): u

Re: fatal server error..

.. when I start up I get a message "fatal server > error: could not create audio connection block info" and the machine > seems to hang for quite awhile. Obviously there's something I haven't > done here, but I'm still trying to get a handle on this stuff. >

fatal server error..

I am running Debian release 1.2 on my 586/133mhz...and trying to get XFree86 up and going... when I start up I get a message "fatal server error: could not create audio connection block info" and the machine seems to hang for quite awhile. Obviously there's something I haven'