Aurelien Nephtali wrote:
On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote:
Aurelien Nephtali wrote:
Hi,
I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
I've attached the error log.
Any help would be appreciated :)
-- Aurelien
1) How did you upgrade?
2) W
> On Mon, 23 Dec 2002 10:11:29 +0100, Aurelien Nephtali
><[EMAIL PROTECTED]> said:
>> >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
>> >I've attached the error log.
>> >
>> 1) How did you upgrade?
>> 2) What's the name of your machine?
>>
On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote:
> Aurelien Nephtali wrote:
> >Hi,
> >
> >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
> >I've attached the error log.
> >
> >Any help would be appreciated :)
> >
> >-- Aurelien
>
> 1) How did you upgrade?
> 2)
Aurelien Nephtali wrote:
Hi,
I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
I've attached the error log.
Any help would be appreciated :)
-- Aurelien
1) How did you upgrade?
2) What's the name of your machine?
--
L i W W W i Jens Rehsack
Hi Aurelien
I was able to get X running once I recompiled (the server) with
-fno-merge-constants. Unfortunately, I do not know if it has anything to
do with the GCC ABI issue.
Aurelien Nephtali wrote:
Hi,
I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
I've attached the
Hi,
I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/
I've attached the error log.
Any help would be appreciated :)
-- Aurelien
Script started on Sun Dec 22 22:34:05 2002
[m[27m[Jnebula% [K[70C~[71Dsstartx
xauth: (argv):1: bad display name "nebula.wanadoo.fr:0" i
On Fri, 8 Nov 2002, Terry Lambert wrote:
> Horen wrote:
> > Now the missing facts:
> >
> >4.x binaries will not run on 5.0, lib.c inconsistency.
>
> You are not running the most recent 5.x. We can't help you, I
> think.
>
>
> >Identical XFree86 sources compiled nativly on 4.6, 4.7 and
Horen wrote:
> Now the missing facts:
>
>4.x binaries will not run on 5.0, lib.c inconsistency.
You are not running the most recent 5.x. We can't help you, I
think.
>Identical XFree86 sources compiled nativly on 4.6, 4.7 and 5.0.
>4.6-4.7: no problem
>5.0: logout from X blocks
On Fri, 8 Nov 2002, Horen wrote:
> On Thu, 7 Nov 2002, Terry Lambert wrote:
>
> > Horen wrote:
> > > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work.
> > > Don't you think it is OS related. ?
> >
> > THere are a lot of MS-DOS programs that won't run on FreeBSD;
> > I don't think that
Horen <[EMAIL PROTECTED]> writes:
> Posted a week ago the question, didn't get any reaction.
>
> Everything with current from last night works fine but killing
> X or logging out ends in a black screen. No way to activate the
> display without reboot. Remote login is fine. Typing blind works
> to
Horen wrote:
> On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work.
> Don't you think it is OS related. ?
>
> I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works.
> Only on FreeBSD 5,0 , it doesn't work.
Install X from FreeBSD 4.6 or 4.7 on FreeBSD 5.0... plain enough?
-- Terry
re (this is not a FreeBSD
> specific problem, if it is not happening because of FreeBSD
> specific code).
>
> The only possible way this could be a FreeBSD specific problem
> is if you were using, e.g., the AGP driver, and it wasn't working.
I have exactly the same problem wit
Horen wrote:
> > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs
>
> Do you think, it makes sense, that I grab an other version,
> 4.2.0 or even 4.1.x to check ?
No, I think the source code version is much less relevent than
the platform and compiler which was used to compile the X
Horen wrote:
> > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the
> > Exact same version of the X Server (pkg_info | grep XFree86-Server)?
> XFree86-Server-4.2.1_5 XFree86-4 X server and related programs
That's the version of the source code. Are you running the same
binaries? Or
Horen wrote:
> On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work.
> Don't you think it is OS related. ?
THere are a lot of MS-DOS programs that won't run on FreeBSD;
I don't think that's FreeBSD-related, I think it's the code
doing the wrong things to run on FreeBSD.
> I even installed
>
>
> On 7 Nov 2002, Eric Anholt wrote:
>
> > On Thu, 2002-11-07 at 16:56, Horen wrote:
> > >
> > >
> > >
> > > On 7 Nov 2002, Eric Anholt wrote:
> > >
> > > > On Thu, 2002-11-07 at 04:40, Horen wrote:
> > > > >
> > > > >
> > > > > On 6 Nov 2002, Eric Anholt wrote:
> > > > >
> > > > > > On Wed, 20
On 7 Nov 2002, Eric Anholt wrote:
> On Thu, 2002-11-07 at 16:56, Horen wrote:
> >
> >
> >
> > On 7 Nov 2002, Eric Anholt wrote:
> >
> > > On Thu, 2002-11-07 at 04:40, Horen wrote:
> > > >
> > > >
> > > > On 6 Nov 2002, Eric Anholt wrote:
> > > >
> > > > > On Wed, 2002-11-06 at 18:34, Horen wrote
On Thu, 2002-11-07 at 16:56, Horen wrote:
>
>
>
> On 7 Nov 2002, Eric Anholt wrote:
>
> > On Thu, 2002-11-07 at 04:40, Horen wrote:
> > >
> > >
> > > On 6 Nov 2002, Eric Anholt wrote:
> > >
> > > > On Wed, 2002-11-06 at 18:34, Horen wrote:
> > > > >
> > > > > Posted a week ago the question, did
On Thu, 7 Nov 2002, Terry Lambert wrote:
> Horen wrote:
> > > You stated "Typing blind starts X again".
> > >
> > > Can you tell us what you mean by this?
> > >
> > > o It restarts X, as if you typed "startx"
> >
> > Exactly that.
>
> The problem is clearly in the X11 code, then, since it is
Horen wrote:
> > You stated "Typing blind starts X again".
> >
> > Can you tell us what you mean by this?
> >
> > o It restarts X, as if you typed "startx"
>
> Exactly that.
The problem is clearly in the X11 code, then, since it is not
resetting the card to the video mode it was in before X s
On 7 Nov 2002, Eric Anholt wrote:
> On Thu, 2002-11-07 at 04:40, Horen wrote:
> >
> >
> > On 6 Nov 2002, Eric Anholt wrote:
> >
> > > On Wed, 2002-11-06 at 18:34, Horen wrote:
> > > >
> > > > Posted a week ago the question, didn't get any reaction.
> > > >
> > > > Everything with current from l
On Thu, 7 Nov 2002, Terry Lambert wrote:
> Horen wrote:
> > Tried all combinations. Disabled every chip related feature, that isn't
> > required to bring X up. Screensaver is disabled. No way to get
> > any readable display back without reboot.
> >
> > Installed a fresh XFree86 built from the po
On Thu, 2002-11-07 at 04:40, Horen wrote:
>
>
> On 6 Nov 2002, Eric Anholt wrote:
>
> > On Wed, 2002-11-06 at 18:34, Horen wrote:
> > >
> > > Posted a week ago the question, didn't get any reaction.
> > >
> > > Everything with current from last night works fine but killing
> > > X or logging out
> From [EMAIL PROTECTED] Thu Nov 7 19:30:04 2002
> Date: Thu, 07 Nov 2002 16:19:57 -0800
> From: Terry Lambert <[EMAIL PROTECTED]>
> To: Horen <[EMAIL PROTECTED]>
> Cc: Eric Anholt <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: XFree
>
> Horen w
Horen wrote:
> Tried all combinations. Disabled every chip related feature, that isn't
> required to bring X up. Screensaver is disabled. No way to get
> any readable display back without reboot.
>
> Installed a fresh XFree86 built from the ports tree, hour before
> updated. No luck :-(
You state
Tried all combinations. Disabled every chip related feature, that isn't
required to bring X up. Screensaver is disabled. No way to get
any readable display back without reboot.
Installed a fresh XFree86 built from the ports tree, hour before
updated. No luck :-(
-Horen
>
>
> Thanks,
>
> will
Thanks,
will check on that, hope it will help.
-Horen
On Thu, 7 Nov 2002, Terry Lambert wrote:
> Horen wrote:
> > > > How long has this been going on? Did it start at any particular point
> > > > (a specific kernel or XFree86 upgrade)? What video card do you use?
> > > > Does starting X aga
Horen wrote:
> > > How long has this been going on? Did it start at any particular point
> > > (a specific kernel or XFree86 upgrade)? What video card do you use?
> > > Does starting X again not work?
>
> Typing blind starts X again.
>
> Do you have any idea what could be the problem.
xset s o
walt wrote:
> Horen wrote:
> > Posted a week ago the question, didn't get any reaction.
> >
> > Everything with current from last night works fine but killing
> > X or logging out ends in a black screen. No way to activate the
> > display without reboot. Remote login is fine. Typing blind works
> >
>
>
> On 6 Nov 2002, Eric Anholt wrote:
>
> > On Wed, 2002-11-06 at 18:34, Horen wrote:
> > >
> > > Posted a week ago the question, didn't get any reaction.
> > >
> > > Everything with current from last night works fine but killing
> > > X or logging out ends in a black screen. No way to activat
Thanks for the tip, was my first idea too, because you can
type blind. But it doesn't help, it still stays everything
black.
Remote login works fine, there are no suspicious processes
running.
-Horen
On Thu, 7 Nov 2002, walt wrote:
> Horen wrote:
> > Posted a week ago the question, didn't get
Horen wrote:
Posted a week ago the question, didn't get any reaction.
Everything with current from last night works fine but killing
X or logging out ends in a black screen. No way to activate the
display without reboot. Remote login is fine. Typing blind works
too.
I have exactly the same prob
On 6 Nov 2002, Eric Anholt wrote:
> On Wed, 2002-11-06 at 18:34, Horen wrote:
> >
> > Posted a week ago the question, didn't get any reaction.
> >
> > Everything with current from last night works fine but killing
> > X or logging out ends in a black screen. No way to activate the
> > display wi
On Wed, 6 Nov 2002, Steve Kargl wrote:
> On Wed, Nov 06, 2002 at 09:34:39PM -0500, Horen wrote:
> >
> > Posted a week ago the question, didn't get any reaction.
> >
> > Everything with current from last night works fine but killing
> > X or logging out ends in a black screen. No way to activate
On Wed, 2002-11-06 at 18:34, Horen wrote:
>
> Posted a week ago the question, didn't get any reaction.
>
> Everything with current from last night works fine but killing
> X or logging out ends in a black screen. No way to activate the
> display without reboot. Remote login is fine. Typing blind
On Wed, Nov 06, 2002 at 09:34:39PM -0500, Horen wrote:
>
> Posted a week ago the question, didn't get any reaction.
>
> Everything with current from last night works fine but killing
> X or logging out ends in a black screen. No way to activate the
> display without reboot. Remote login is fine.
Posted a week ago the question, didn't get any reaction.
Everything with current from last night works fine but killing
X or logging out ends in a black screen. No way to activate the
display without reboot. Remote login is fine. Typing blind works
too.
Is there a fix in sight, would be great he
5.0 built and installed 10/22 runs fine on a Tyan Thunder K7
with 2 Athlons.
Exception:
Shutdown of the X server, no matter when and how, causes
complete black display. The box is remotely reachable. The only way to
restore the console display is to reboot.
Guess a known issue. It happens a
+---[ Sameh Ghane ]--
| Hi,
|
| Did anyone find a way to compile the x11-servers/XFree86-4-Server port ?
|
| According to the Makefile it is not possible to build it since FreeBSD 500013.
| Will a package built under < 500013 work under > 500013 ?
It's busted since the K
Hi,
Did anyone find a way to compile the x11-servers/XFree86-4-Server port ?
According to the Makefile it is not possible to build it since FreeBSD 500013.
Will a package built under < 500013 work under > 500013 ?
Another way to have DRI/M rendering with mga/G400 and XFree under -c
On Sun, 25 Feb 2001, Martin Blapp wrote:
>
> Daniel,
>
> > I don't know, what port builds libGL.so.1?
> > Something has to link in the threads library...
>
> Yep, XFree86 libs should be linked against -lc_r,
> I got this working with this.
>
> It's still broken in FreeBSD ports, all GL depende
Hi,
> konq_undo.kidl /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined
> symbol "_flockfile"
> /usr/local/bin/dcopidl2cpp --c++-suffix cc --no-stub konq_undo.kidl
> /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol
> "_flockfile
Sorry, fixed this with recompling qt.
Mart
Daniel,
> I don't know, what port builds libGL.so.1?
> Something has to link in the threads library...
Yep, XFree86 libs should be linked against -lc_r,
I got this working with this.
It's still broken in FreeBSD ports, all GL dependent
programms are broken for CURRENT at the moment.
I've anot
On Fri, Feb 25, 2000 at 03:06:55PM -0800, Joel Ray Holveck wrote:
> [Followups to -current]
>
> >>I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
> >> KDE 1.1.2. All from monday's ports tree.
> >>Well, I think I can'
[Followups to -current]
>> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
>> KDE 1.1.2. All from monday's ports tree.
>> Well, I think I can't say I am running this system, for I am getting
>> the following message whenever
hi, there!
On Wed, 23 Feb 2000 [EMAIL PROTECTED] wrote:
> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
> KDE 1.1.2. All from monday's ports tree.
> Well, I think I can't say I am running this system, for I am getting
> the follo
it did more harm than good.
-Will
On Tue, 22 Feb 2000, Will Andrews wrote:
> On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
> > Dear guys,
> >
> > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
> > KDE 1.1.2. All from m
On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
> Dear guys,
>
> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
> KDE 1.1.2. All from monday's ports tree.
> Well, I think I can't say I am running this system, fo
On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
> Dear guys,
>
> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
> KDE 1.1.2. All from monday's ports tree.
> Well, I think I can't say I am running this system, fo
Dear guys,
I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
KDE 1.1.2. All from monday's ports tree.
Well, I think I can't say I am running this system, for I am getting
the following message whenever I try startx:
Authentication failed - cannot
I managed to fix this problem temporarily for myself, but was hoping
the tree would fix itself soon enough.
At the top of FSConServ.c add the line
#define _P1003_1B_VISIBLE
I believe (I deleeted the X source tree), and it'll build fine.
Excerpts from FreeBSD-Current: 15-Oct-99
I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box.
It compile well, but when it's the time of the install I receive this error :
rm -f FSConnServ.o
cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
-I../../ex
ports/include -DCSRG_BASED -DFUNCPRO
Fritz Heinrichmeyer wrote:
>
> as i accidentally deleted my libc.so.3 i thought it would be a good time
> to rebuild xfree, but i came in a preprocessor hell due to siginfo_t
> _POSIX_SOURCE or not ... definition at the stage of building makedepend.
> In file included from mai
as i accidentally deleted my libc.so.3 i thought it would be a good time
to rebuild xfree, but i came in a preprocessor hell due to siginfo_t
_POSIX_SOURCE or not ... definition at the stage of building makedepend.
In file included from main.c:41:
/usr/include/signal.h:72: warning: `union
Randy Bush wrote:
> is this for real or is it an aout-to-elf thing?
This is for real. Tk80 is looking for ELFed X11 (You did recompile
your X, Right? If not then it is an ELF thing). The XFree86 port
is rather good, IMHO.
M
> randy
>
>
> ===> Generating temporary packing list
> /bin/ln -sf l
is this for real or is it an aout-to-elf thing?
randy
===> Generating temporary packing list
/bin/ln -sf libtcl80.so.1 /usr/local/lib/libtcl80.so
/usr/bin/env OBJFORMAT=elf /sbin/ldconfig -m /usr/local/lib
/usr/bin/env PKG_PREFIX=/usr/local /bin/sh
/usr/ports/lang/tcl80/pkg/INSTALL.tclsh
===>
ny gettys configured in in /etc/ttys
as MAXCONS in the kernel, so XFree wasn't able to allocate an
unused vty, obviously. Disabling one getty solved the problem.
Maybe this pitfall could be documented somewhere... But then
again, maybe I'm the only one who's too dumb to g
>I'm using -current as of 1998-01-14 with the new syscons (with
>separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a
>Matrox G200). The keyboard and mouse are plain PS/2 models,
>they work fine under syscons (i.e. not using XFree).
[...]
>XFree used to allocate t
Hi,
I'm using -current as of 1998-01-14 with the new syscons (with
separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a
Matrox G200). The keyboard and mouse are plain PS/2 models,
they work fine under syscons (i.e. not using XFree).
The kernel contains the following en
59 matches
Mail list logo
