David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports
On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
On Mon, 2003-10-13 at 16:05, Peter Wemm wrote:
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds,
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter David Gilbert wrote:
I don't really have a clue where to look for this fix as there
seems to be a serious amount of magic going into the divided
XFree86-4 port builds, but my XFree86-4-clients port fails saying:
make: don't know how to
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert
wrote: I don't really have a clue where to look for this fix as
there seems to be a serious amount of magic going into the
divided XFree86-4 port builds,
On Mon, 2003-10-13 at 14:54, David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make
Well, I am running a -CURRENT build from April 8. XF86-4.3.0 with a GF4
Ti4200 64MB with a 19 Sony Trinitron CRT (at 1600x1200, 72-75Hz), using the
official NVIDIA binary driver kernel module (compiled/installed from
/usr/ports/x11/nvidia-driver/).
Here's my XF86config (note that it
You can forcibly delete wrapper package, and the do pkgdb -F and delete
dependency on it... Only XFree metaport is depends on it.
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
On Thu, 20 Mar 2003, CARTER Anthony wrote:
I realise what wrapper is
wrapper is needed to run script startx by ordinary user, not root... Seems
like gdm works well for me without wrapper.
Shall we need to make XFree86-4.3.0,1 an option to install without wrapper
package?
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL
CARTER Anthony wrote:
Xfree requires wrapper but seems to break GDM for user logins. Is this
normal, and can I force un-install wrapper without breaking anything?
Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just
change this symbolic link:
/usr/X11R6/bin/X@ - Xwrapper-4
to
I realise what wrapper is for, but if I type pkg_delete wrappe-1.0_2 at
the command line, I get:
pkg_delete: package 'wrapper-1.0_2' is required by these other packages
and may not be deinstalled:
XFree86-4.3.0,1
I never installed wrapper, but when I did a portupgrade to the latest
XFree, I
Andrei Popov [EMAIL PROTECTED] writes:
There's something fishy with Xkb in 4.3: whenever I try cyrillic
layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes,
cyrillic fonts are listed in font path).
Running xev shows that event is there. Anyone seen the same
behavior/knows what
Please try setting the locale:
export LC_CTYPE=ru_RU.KOI8-R
or
setenv LC_CTYPE ru_RU.KOI8-R
Yow! Worked -- which is a bit strange: with 4.2 nothing like this was
necessary...
--
Alexander Pohoyda
[EMAIL PROTECTED]
Thanks,
-- Andrei
__
Hello,
On Tue, Dec 31, 2002 at 11:09:28AM +0100, Frode Nordahl wrote:
Hello,
Has anyone had any success with this combo?
Yes. Apart from the known problem with my S3 Virge GX2 graphics adapter,
which causes random freezes under X when only the reset button helps.
But this has been happening
On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote:
Hmmm. I have the same version of X as you (roughly, the tag was already
in place by the time I built although I always use HEAD, I built on 23rd
December) and FreeBSD is from 25th December.
I just updated the sources to HEAD, and I see
On Tue, Dec 31, 2002 at 11:51:34AM +0100, Frode Nordahl wrote:
On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote:
Hmmm. I have the same version of X as you (roughly, the tag was already
in place by the time I built although I always use HEAD, I built on 23rd
December) and FreeBSD is from
On Tue, Oct 29, 2002 at 10:01:07PM -0800, Paul A. Scott wrote:
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and
4.7. It is not possible to run the graphical configuration utility at all.
After running curses configuration utility, running startx produces signal
11. No
On Tue, 15 Oct 2002 11:39:22 -0700 (PDT)
Saurabh Gupta [EMAIL PROTECTED] wrote:
Any help will be very much appreciated.
When it freezes again, wait some minutes (~10). If it unfreezes then, it
is a known problem. And if you see some aborts (signal 6) of XFree86,
then it is a known problem too.
On Sun, Sep 29, 2002 at 12:17:54PM -0700, Eric Anholt wrote:
On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?
On Sun, 29
I think it should be fixed in FreeBSD ports before 4.7, because it
is really annoying when server crashes without any particular
reason.
Eric, what do you think about it?
-Maxim
On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote:
Hey,
On Sun, 2002-09-29 at 14:51, walt wrote:
Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?
On Sun, 29 Sep 2002, Maxim Sobolev wrote:
I think it should be fixed in FreeBSD ports before 4.7, because it
is really annoying
On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?
On Sun, 29 Sep 2002, Maxim Sobolev wrote:
I think it should be fixed in
On Sun, 2002-09-29 at 21:17, Eric Anholt wrote:
From what I had heard on the lists it was only a thing that happened
when people upgraded kernels, and that it had stopped after some date of
kernel. I hadn't experienced it, so I ignored it. I don't know about
that link posted, I thought that
Yes, i don't see any -stable systems bombing out. But it _always_ occurrs
when typing. No matter what app... Sometimes in the linux opera, sometimes
in the konq address bar. I dont think it ever happened when typing in an
Xterm though.
On 29 Sep 2002, Frode Nordahl wrote:
On Sun, 2002-09-29 at
Wesley Morgan wrote:
Yes, i don't see any -stable systems bombing out. But it _always_ occurrs
when typing. No matter what app...
I've seen in most often when starting X/gnome. Almost always happens
when gnome-panel is just appearing on screen. No typing going on yet,
naturally.
If
It seems Martin Blapp wrote:
I used to have a functionaly working X. After I made world
I see now this:
...
I've removed everything and build a new X. Same symptoms.
Mmap problem ?
I saw the same problem here, but after upgrading to sources around
1200GMT aug 21 the problem seems to be
Hi,
I don't know why, but adding this to XF86Config:
Option NoInt10
Solved the problem.
Thank you anyways ;-)
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Peter Schultz [EMAIL PROTECTED] writes:
Amazing, the obvious. Now I get this:
Hmm, I didn't get any more trouble after I fixed the pragma problem.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
Wilko
I'm getting the following error on a just built -current, which was a
fresh
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do
Alfred Perlstein wrote:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
#pragma weak foo = bar
What's the correct way to do this now?
I dont know. :-( There are hacks that can work around it, but I think this
is unintentional breakage. I tried changing this:
#pragma weak foo = bar
to
__weak_reference(bar, foo);
void f () __attribute__ ((weak, alias
Alfred Perlstein [EMAIL PROTECTED] writes:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do this now?
#pragma weak foo = bar
as you'd have guessed if you'd bothered to read the error message and
look at
Dag-Erling Smorgrav wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do this now?
#pragma weak foo = bar
as you'd have guessed if you'd
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
I'm getting the following error on a just built -current, which was a
fresh install of 5.0-CURRENT-20020519-JPSNAP:
Yes, and if you'd been reading the mailing list like you're supposed
to you would have already known about this.
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
Wilko
I'm getting the following error on a just built -current, which was a
fresh install of 5.0-CURRENT-20020519-JPSNAP:
installing in lib/XThrStub...
rm -f
On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote:
Kris Kennaway wrote:
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you got at
On Fri, Apr 19, 2002 at 08:56:50PM -0700, James Satterfield wrote:
I've found that wrapper needs to be updated with XFree86-4.
wrapper always needs to be rebuilt when you update X, yes.
Kris
msg37453/pgp0.pgp
Description: PGP signature
Kris Kennaway wrote:
On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote:
Kris Kennaway wrote:
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you
On Sat, Apr 20, 2002 at 10:39:22PM +0200, John Angelmo wrote:
Well X starts but just to the gray area, no windowmanager starts and the
error I get(after I have exited) is:
AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from
local host
AUDIT: Fri Apr 19 22:09:15 2002:
On Sat, 20 Apr 2002 13:35:32 -0700
Kris Kennaway [EMAIL PROTECTED] wrote:
KK wrapper always needs to be rebuilt when you update X, yes.
All you really need to do is reset the X symlink (unless you are
upgrading from 3 to 4 in which case you need a new wrapper).
--
C:WIN
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you got at install-time and install the wrapper
port.
Kris
msg37428/pgp0.pgp
Description: PGP signature
Kris Kennaway wrote:
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote:
After yesterdays new build I found a problem
Xfree86-4 can't start as regular user (exept root)
Read the fine message you got at install-time and install the wrapper
port.
Kris
Wrapper is installed
it
I've found that wrapper needs to be updated with XFree86-4.
James.
- Original Message -
From: John Angelmo [EMAIL PROTECTED]
To: current [EMAIL PROTECTED]
Sent: Friday, April 19, 2002 1:13 PM
Subject: Xfree86-4 problem
After yesterdays new build I found a problem
Xfree86-4 can't
On Wed, 3 Apr 2002, Coleman Kane wrote:
Its usb. Someone with working serial console need look at this.
I have been having major issues with XFree86 recently. It seems to just
completely halt the machine hard whenever I try starting it. If I run
it from a remote terminal with -verbose all
On Wed, Apr 03, 2002 at 03:14:43AM -0500, Coleman Kane wrote:
I have been having major issues with XFree86 recently. It seems to just
completely halt the machine hard whenever I try starting it. If I run
it from a remote terminal with -verbose all the way up, it seems to halt
at the section
Yeah, I rememver that. I think it is the USB though, it crashes right at the
point where it attempts to attach Input devs.
--
coleman
On Wed, Apr 03, 2002 at 02:35:50PM +0200, Pierre Beyssac wrote:
On Wed, Apr 03, 2002 at 03:14:43AM -0500, Coleman Kane wrote:
I have been having major issues
That's what I suspected. I may try setting up the serial console on
that box and see what I can find.
--
coleman
On Wed, Apr 03, 2002 at 11:33:40AM +0300, Andrew Bliznak wrote:
On Wed, 3 Apr 2002, Coleman Kane wrote:
Its usb. Someone with working serial console need look at this.
I have
On Fri, Mar 22, 2002 at 01:01:57AM -0600, Eric Liedtke wrote:
While trying to build the XFree86-4-Server port this evening(cvsuped
today around 1PM CST)
the build died due to a redefinition of xf86ioctl. The file
On Wed, Mar 20, 2002 at 11:29:46AM +0100, Riccardo Torrini wrote:
With last update of world and ports I'm unable to start XFree86.
I have a matrox G200 (agp) and I have tryed with and without the
WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump
when starting X. At the same
What are the plans about replacing XFree86 3.3.6 with XFree86 4?
According to plan, FreeBSD 4.6-RELEASE will have XFree86 4, so sometime
after this month and before the next release.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On 2001-Nov-30 10:55:39 +0200, Maxim Sobolev [EMAIL PROTECTED] wrote:
Peter Jeremy wrote:
With a recently re-built XFree86, running on -current from last Sunday,
whenever I hit one of the keypad keys, the X server crashes. This is
somewhat disconcerting...
...
Apply the following patch and
Peter Jeremy wrote:
With a recently re-built XFree86, running on -current from last Sunday,
whenever I hit one of the keypad keys, the X server crashes. This is
somewhat disconcerting...
The kernel prints sigreturn: eflags = 0x13282, was 0x256 (the old
eflags value an addition I made to
On Fri, Oct 19, 2001 at 11:44:42AM -0700, David O'Brien wrote:
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote:
Is a real need for ports under -CURRENT to require (from a
week or two, I don't remember) XFree86-libraries?
Yes.
To elaborate a bit, the default XFree86
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote:
Is a real need for ports under -CURRENT to require (from a
week or two, I don't remember) XFree86-libraries?
Yes.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote:
Is a real need for ports under -CURRENT to require (from a
week or two, I don't remember) XFree86-libraries?
They asks for XFree86-libraries-4.1.0, but I have 3.3.6_10
installed. Can I (safetly) mix 3.3.6 and 4.1.0?
Is the
On Sun, Jan 21, 2001 at 01:50:28PM -0600, Chris wrote:
If you are currently running 4.0.1, I would seriously recommend skipping
this
minor revision. I have run into a multitude of problems with it, and am now
back right where I started.
One, is the lack of DRM support for the matrox
On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:
the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports,
and it built fine for a long time, and then after about 35300 lines of
output to the screen, ran into
make: don't know how to make
Kris Kennaway wrote:
On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:
the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports,
and it built fine for a long time, and then after about 35300 lines of
output to the screen, ran into
make: don't know how
Patrick Gardella wrote:
In file included from /usr/include/sys/wait.h:93,
from vgaHW.c:44:
/usr/include/machine/endian.h:72: syntax error before
`__uint16_swap_unit32'
/usr/include/machine/endian.h:72: syntax error before `__x'
snip
The following 2 patches solve the
* From: Marcel Moolenaar [EMAIL PROTECTED]
* The following 2 patches solve the problem when building XFree86-3.3.6
* with only the VGA16 and SVGA servers. Building other servers may still
* be broken.
Yikes. The same problem is killing (at least) all the emacsen too.
On 26 Oct 2000, Satoshi - Ports Wraith - Asami wrote:
* From: Marcel Moolenaar [EMAIL PROTECTED]
* The following 2 patches solve the problem when building XFree86-3.3.6
* with only the VGA16 and SVGA servers. Building other servers may still
* be broken.
Yikes. The same problem is
Satoshi - Ports Wraith - Asami wrote:
* From: Marcel Moolenaar [EMAIL PROTECTED]
* The following 2 patches solve the problem when building XFree86-3.3.6
* with only the VGA16 and SVGA servers. Building other servers may still
* be broken.
Yikes. The same problem is killing (at
On Thu, 26 Oct 2000 13:58:09 -0400, Marcel Moolenaar [EMAIL PROTECTED] said:
Eventually yes, but not this way. According to Bruce sys/types is a
prerequisite for sys/wait.
This is currently true, but should be fixed this year (probably not
this month -- it depends on how much energy I have).
In file included from /usr/include/sys/wait.h:93,
from vgaHW.c:44:
/usr/include/machine/endian.h:72: syntax error before
`__uint16_swap_unit32'
/usr/include/machine/endian.h:72: syntax error before `__x'
snip
I've not seen this reported before, nor a work around.
I don't know
"Rogier R. Mulhuijzen" wrote:
In file included from /usr/include/sys/wait.h:93,
from vgaHW.c:44:
/usr/include/machine/endian.h:72: syntax error before
`__uint16_swap_unit32'
/usr/include/machine/endian.h:72: syntax error before `__x'
snip
I've not seen this reported
Rogier R. Mulhuijzen wrote:
In file included from /usr/include/sys/wait.h:93,
from vgaHW.c:44:
/usr/include/machine/endian.h:72: syntax error before
`__uint16_swap_unit32'
/usr/include/machine/endian.h:72: syntax error before `__x'
snip
I've not seen this reported
Patrick Gardella wrote:
I built and installed -current on a laptop yesterday (10/23/00), and
went to build XFree86 3.3.6_3 today from the ports directory.
It built fine, but when you run make install, it dies, complaining of
syntax errors in machine/endian.h:
In file included from
Original Message
On 9/7/00, 10:51:14 AM, Piotr Woniak [EMAIL PROTECTED]
wrote regarding XFree86:
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea
-
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
How can I do it?
Piotr
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea -
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
Tcl/Tk.
Build X, clean it out. Build Tcl/Tk 8.2. Build X again. You'll have XF86Setup.
BTW - there is no XF86Setup in XFree86-4
Original Message
On 9/7/00, 12:18:07 PM, Mark Murray [EMAIL PROTECTED] wrote regarding
Re: XFree86 :
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea
-
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
Tcl/Tk.
Build X
Mark Murray wrote:
BTW - there is no XF86Setup in XFree86-4 yet.
No, but there is xf86cfg, which is even better ;^)
It correctly autodetected both my Monitor and Video card, meaning that I
was able to get maximum performance out of both (proper Modelines).
Though 1962x1440 is pushing it on
On Mon, Mar 20, 2000 at 11:48:16PM +0300, Ilya Naumov wrote:
i've tried to build XFree86 4.0 on my 5.0-CURRENT and 4.0-RELEASE box, and
encountered
a problem.
"make all" finishes successfully, but "make install" fails with the
following error message:
making all in
I can varify this on 4.0-STABLE as of March 19, ports cvsup the same time.
I had a look at it, and though I'm not much of a programmer, I cant see
where the parse error is.. maybe I'm blind.
Matt
--
Matt Heckaman [[EMAIL PROTECTED]|[EMAIL PROTECTED]] [Please do not send me]
!Powered by
On Tue, 14 Mar 2000, Ted Sikora wrote:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
options SHMALL=1025
options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
options SHMMAXPGS=1025
options SHMMIN=2
options SHMMNI=256
options SHMSEG=128
On Tue, 14 Mar 2000, Ted Sikora wrote:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
Any ideas on a fix. Xfree86-4.0 is solid otherwise.
There was quite some discussion about this recent on either -hackers or
-current. You should be able to find it in the archives.
Andrey Sverdlichenko wrote:
On Tue, 14 Mar 2000, Ted Sikora wrote:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
options SHMALL=1025
options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
options SHMMAXPGS=1025
options SHMMIN=2
options
"Michael L. Imamura" wrote:
I haven't tried xfce, but I had some problems running Enlightenment 16.3,
all related to shared memory. I disabled shared pixmaps in my Imlib
configuration and that got rid of the random crashing, but is again not a
very optimal solution :) I'm guessing it's a
On Sat, Mar 11, 2000 at 12:24:10PM -0800, Nawfal M. Rouyan wrote:
Hi,
I've installed XFree86 version 4 trough the ports
collection
but it won't start and I think it is because of the
missing mouse module. Since I'm using lynx, I can't
attached the /var/log/XFree86.0.log file for your
On Sat, Mar 11, 2000 at 04:10:26PM -0500, Ted Sikora wrote:
My problem is a little different. XFree86-4.0 loads
fine looks great but the mouse does not work. There
are no errors. I tried PS/2 , serial, etc same with
them all. The pointer appears then moves to the upper
right and
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7 +197,7 @@
echo "#define
Nawfal M Rouyan writes:
Hi,
I've installed XFree86 version 4 trough the ports
collection
but it won't start and I think it is because of the
missing mouse module. Since I'm using lynx, I can't
attached the /var/log/XFree86.0.log file for your
reference. I can only paste the error
"Michael L. Imamura" wrote:
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7
I haven't tried xfce, but I had some problems running Enlightenment 16.3,
all related to shared memory. I disabled shared pixmaps in my Imlib
configuration and that got rid of the random crashing, but is again not a
very optimal solution :) I'm guessing it's a problem with the current GTK
Ted Sikora wrote:
My problem is a little different. XFree86-4.0 loads
fine looks great but the mouse does not work. There
are no errors. I tried PS/2 , serial, etc same with
them all. The pointer appears then moves to the upper
right and dissappers. I tried moving it...Mouse1, etc.
but
On Thu, 9 Mar 2000, Devin Butterfield wrote:
Just wondering if there are plans in the works to get Xfree86 4.0 into
FreeBSD 4.0. I just noticed that X 4.0 has finally been released.
Looks a bit green for inclusion in a release not to mention that its list
of supported devices is a bit short in
That's odd... I just built it tonight, and I havn't had anything but this:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont
On Wed, 23 Feb 2000, Kenneth Wayne Culver wrote:
That's odd... I just built it tonight, and I havn't had anything but this:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension:
That's odd... I just built it tonight, and I havn't had anything but this:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
"Patrick M. Hausen" wrote:
Hi all!
I don't know if this has been addressed already, but the archives are
offline.
I started using current by installing 2127-SNAP of current.freebsd.org
including XFree86 3.3.6. The Xfree86 a.out libraries were missing
from the installtion tarballs,
(trimmed the long cc:-list)
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste wrote:
The problem with 3.3.5 was something to do with refreshing, example
after doing some ls -la in xterm the xterm screen got blank completely
or showed some lines of text in the bottom but otherwise
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste [EMAIL PROTECTED]
wrote:
I can say that I tried building the 3.9.17 with both official compiler
in -current and also with gcc-devel, both built fine but didn't install.
Seems like my fault, nothing else. Time to try again.
It seems
On Mon, Jan 17, 2000 at 06:19:23PM +0100, Ollivier Robert [EMAIL PROTECTED]
wrote:
I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything
special except removing doc from the list of subdirs...
-=-=-
./to_wfont -o Roman.phont Roman.src
./to_wfont -o Roman_M.phont
I had to get rid of some things from Xext to make it install properly
myself.
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at
Vallo Kallaste wrote:
Have you tried to install it? It does builds but barfs at some point for
install process. Not that I care so much about it, 3.3.6 works for my
G400 now, thanks god.
What I did was: build it using the stock gcc-2.95.2 compiler, for
make World. During make install, I
Hi,
On Mon, Jan 17, 2000 at 06:05:54PM -0500, Donn Miller wrote:
Have you tried to install it? It does builds but barfs at some point for
install process. Not that I care so much about it, 3.3.6 works for my
G400 now, thanks god.
... what was the problem with the G400 in earlier revisions?
On Tue, Jan 18, 2000 at 01:17:53AM +0100, Andreas Braukmann wrote:
Is the gcc-2.96-current in the ports collection?
Yes. /usr/ports/lang/gcc-devel
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
On Tue, Jan 18, 2000 at 01:17:53AM +0100, Andreas Braukmann [EMAIL PROTECTED]
wrote:
... what was the problem with the G400 in earlier revisions?
3.3.5 (built from the port) lives quite happily on my G400?
I'm very eager to get my hands on a XFree86 with dual-head support
and
1 - 100 of 112 matches
Mail list logo
