I pushed commits to fix this, the wpa_supplicant*, and hostapd* ports last
night.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message
, Nuno Teixeira writes:
>
> (...)
>
> commit 108d
On June 1, 2024 1:35:29 AM PDT, Nuno Teixeira wrote:
>(...)
>
>commit 108de784513d87bbe850e7b003a73e26b5b54caa
>Author: Val Packett
>Date: Fri May 31 08:45:02 2024 -0600
>
>Redefine CLOCK_BOOTTIME to alias CLOCK_MONOTONIC, not CLOCK_UPTIME
>
>Nuno Teixeira escreveu (sábado, 1/06/2024 à(s)
(...)
commit 108de784513d87bbe850e7b003a73e26b5b54caa
Author: Val Packett
Date: Fri May 31 08:45:02 2024 -0600
Redefine CLOCK_BOOTTIME to alias CLOCK_MONOTONIC, not CLOCK_UPTIME
Nuno Teixeira escreveu (sábado, 1/06/2024 à(s) 09:01):
> Hello all,
>
> Anyone seeing this error on main?
>
>
Hello all,
Anyone seeing this error on main?
Thanks
[ 28% 661/2246] cc -Isrc/intel/common/libintel_common.a.p
-Isrc/intel/common -I../src/intel/common -Iinclude -I../include -Isrc
-I../src -Isrc/intel -I../src/intel -Isrc/intel/genxml -Isrc/intel/dev
-I/usr/local/
include -I/usr/local/include/li
Re: my e-mail of 25th June (below)
If I lock mesa-dri and mesa-libs before pkg upgrade, then I am free of
the software rasteriser problem following an upgrade.
However: the locks cause libglvnd to not install at upgrade time; and
then applications such as Firefox and Thunderbird will not
Hi
It looks like HD5000 should be supported but I can't get it to work on the
new MacBook Air.
Attached the log which will show that there is no /dev/dri device.
I compiled drivers and libraries the same way as I've done on HD4000
(Panasonic laptop) which works just fine (except sw
On 2012-06-09 21:57, O. Hartmann wrote:
...
> Now, with your patch set installed again, graphics/dri compiles without
> a flaw.
>
> I was wondering why there are not more people/FreeBSD users out there
> having the very same problem.
Most likely because neither WITH_NEW_XORG n
On 06/09/12 19:34, Dimitry Andric wrote:
> On 2012-06-09 19:00, O. Hartmann wrote:
> ...
>> I try to track down problems on one of our FreeBSD 10.0-CURRENT/amd64
>> boxes and therefore, I try recompiling "xorg".
>>
>> One box is constantly failing to compi
On 2012-06-09 19:00, O. Hartmann wrote:
...
> I try to track down problems on one of our FreeBSD 10.0-CURRENT/amd64
> boxes and therefore, I try recompiling "xorg".
>
> One box is constantly failing to compile port graphics/dri with a
> obviously well know error, as &q
I try to track down problems on one of our FreeBSD 10.0-CURRENT/amd64
boxes and therefore, I try recompiling "xorg".
One box is constantly failing to compile port graphics/dri with a
obviously well know error, as "googling" reveals (
http://lists.freedesktop.org/archives/me
Dimitry Andric wrote:
On 2012-04-28 13:12, Volodymyr Kostyrko wrote:
O. Hartmann wrote:
Is there in "official" way to get this fixed with CLANG? I see that
files folder in graphics/dri is missing, so none of the fixes for both
the faulty source files
I think the patch should go t
Am 04/28/12 18:52, schrieb Dimitry Andric:
> On 2012-04-28 13:12, Volodymyr Kostyrko wrote:
>> O. Hartmann wrote:
>>> Is there in "official" way to get this fixed with CLANG? I see that
>>> files folder in graphics/dri is missing, so none of the fixes for bot
Am 04/28/12 13:12, schrieb Volodymyr Kostyrko:
> O. Hartmann wrote:
>> Is there in "official" way to get this fixed with CLANG? I see that
>> files folder in graphics/dri is missing, so none of the fixes for both
>> the faulty source files
>
> I think
On 2012-04-28 13:12, Volodymyr Kostyrko wrote:
> O. Hartmann wrote:
>> Is there in "official" way to get this fixed with CLANG? I see that
>> files folder in graphics/dri is missing, so none of the fixes for both
>> the faulty source files
>
> I think
O. Hartmann wrote:
Is there in "official" way to get this fixed with CLANG? I see that
files folder in graphics/dri is missing, so none of the fixes for both
the faulty source files
I think the patch should go to graphics/libGL.
cd /usr/ports/graphics/libGL/files
fetch -ra
Compiling Xorg stuff with the switch set in /etc/make.conf for the new
Xorg graphics/dri mesa 7.11.x and xorg-server 1.10.6 with CLANG on bot
FreeBSD 10 and 9 end up in an error:
nouveau_array.c:49:16: error: illegal storage class on function
*extract_u = EXTRACT(char, unsigned
Sorry, I should have posted this in the ports mailing list and will do so.
On Fri, Oct 22, 2010 at 2:13 PM, Chris wrote:
> Hello,
>
> Seeing this on an amd64 box when doing a fresh Xorg build:
>
> ===> Building for dri-7.6.1,2
> gmake[1]: Entering directory `/usr/ports/g
Hello,
Seeing this on an amd64 box when doing a fresh Xorg build:
===> Building for dri-7.6.1,2
gmake[1]: Entering directory `/usr/ports/graphics/dri/work/Mesa-7.6.1/src'
Making sources for autoconf
gmake[2]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-7.6.1/src/glx/x11'
-RELEASE wasn't friendly to -CURRENT.
I've got just a basic install with my custom kernel. I'm using the packages
for X from the 5.1-RELEASE cd running twm. Hangs on restart are gone!
I restarted about 10 times in a row and ran glxinfo and glxgears each time
to verify DRI was stil
Okay. I won't worry about the messages then.
I mentioned the suspend/resume problem only because it
actually worked correctly when using option ForcePCIMode;
I was shocked when it did and was hoping that your fix for
AGP accelerated DRI would pull off the same trick.
I should note here t
restarted about 10 times in a row and ran glxinfo and glxgears each time
> to verify DRI was still activated and working -- no issues. VT switches are
> fine (even while running glxgears). The one thing that does not work is
> resume from acpiconf -s 4 (disk) -- there is a failure to refresh i
-RELEASE wasn't friendly to -CURRENT.
I've got just a basic install with my custom kernel. I'm using the packages
for X from the 5.1-RELEASE cd running twm. Hangs on restart are gone!
I restarted about 10 times in a row and ran glxinfo and glxgears each time
to verify DRI was stil
ing off some of the options in the X config.
> > >
> > > On Tue, 26 Aug 2003 12:21:56 -0500 (GMT) Sean Welch
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > Is anyone else seeing this issue? I'm running into it on desktop
> > > > b
On Tue, 26 Aug 2003, Eric Anholt wrote:
> (CC'ed to -current since it's not -stable specific)
>
> Everyone that's experiencing this and is using the DRI, what version of
> the radeon DRM is loaded? (dmesg | grep drm) Is anyone experiencing
> this without the
Okay, one more message before I *finally* go to bed.
I got kind of excited by the stuff below...
I decided to update my DRI install to see if things
would improve. Now 4.8-RELEASE responds to the
forcepcimode option nearly as well as 5.1-RELEASE does
for me! I thought I had it made -- I&#x
is a little less than half what it was with the AGP.
I haven't had a chance to try that option on my desktops.
If it works there I'll be mighty happy!
Your other message about the newest version of X having
this fixed is very interesting; I track both XFree86 and
DRI CVS daily. The
2:21:56 -0500 (GMT) Sean Welch
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Is anyone else seeing this issue? I'm running into it on desktop
> > > boxes and a laptop running 4.8-RELEASE with up to date ports
> > > collections and various versions o
On Tue, Aug 26, 2003 at 01:27:11PM -0700, Eric Anholt wrote:
...snip...
> Everyone that's experiencing this and is using the DRI, what version
> of the radeon DRM is loaded? (dmesg | grep drm) Is anyone experiencing
> this without the DRI loaded? The ForcePCIMode workaround is
XF86Config file any longer -- I was
> getting a "no space left on device" error. I ended up taking out all
> options short of disabling DRI altogether and eventually discovered
> the only way I could run with DRI switches on and forcepcimode set
> to true was to unload the agp
, 26 Aug 2003 12:21:56 -0500 (GMT)
> > Sean Welch <[EMAIL PROTECTED]> wrote:
> >
> > > Is anyone else seeing this issue? I'm running into it
> > > on desktop boxes and a laptop running 4.8-RELEASE with
> > > up to date ports collections and
2:21:56 -0500 (GMT) Sean Welch
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Is anyone else seeing this issue? I'm running into it on desktop
> > > boxes and a laptop running 4.8-RELEASE with up to date ports
> > > collections and various versions o
taking out all options short of disabling DRI altogether
and eventually discovered the only way I could run with
DRI switches on and forcepcimode set to true was to unload
the agp module from kernel space. This got it started just
fine but there was no DRI. It seems that X is getting
confused and
anyone else seeing this issue? I'm running into it
> > on desktop boxes and a laptop running 4.8-RELEASE with
> > up to date ports collections and various versions of
> > DRI installed over a ports version of X. I'm also seeing
> > this under 5.1-RELEASE on the la
In message: <[EMAIL PROTECTED]>
Lefteris Chatzibarbas <[EMAIL PROTECTED]> writes:
: Is DRI on FreeBSD unmaintained? Am I sending my problem report to the
: wrong place? What should I do or who should I contact about this?
anholt is currently on vacatio
On Sat, Jun 21, 2003 at 04:12:48PM +0300, Lefteris Chatzibarbas wrote:
> Hello,
>
> I believe that the web page related to DRI on BSD (FreeBSD and NetBSD)
> is:
>
> http://people.freebsd.org/~anholt/dri/index.html
>
> I have mailed both this mailing list and [E
On Sat, 2003-06-21 at 09:12, Lefteris Chatzibarbas wrote:
> Hello,
>
> I believe that the web page related to DRI on BSD (FreeBSD and NetBSD)
> is:
>
> http://people.freebsd.org/~anholt/dri/index.html
>
> I have mailed both this mailing list and [EMAIL PROTECTED] (con
Hello,
I believe that the web page related to DRI on BSD (FreeBSD and NetBSD)
is:
http://people.freebsd.org/~anholt/dri/index.html
I have mailed both this mailing list and [EMAIL PROTECTED] (contact address
as stated in the aforementioned web page), about a problem with DRI on
FreeBSD and
Hello,
I have a problem with DRI on FreeBSD. Specifically, in some OpenGL
programs, objects are not drawn at all (in some cases only some of them
get drawn) (DRI enabled), but when DRI is disabled all work fine.
A simple example of such program is:
http://www.opengl.org/developers/code
Julian St. wrote:
It seems not to be related, but when I try to kill my X Server using
Ctrl+Alt+Backspace, my box powers down (jsut like an APM power-down). I
started noticing it using 4-STABLE+ NVidia driver, but it continued to
be the case on -CURRENT with Xfree86's nv driver.
I always see this
Am Sa, 2003-04-05 um 16.52 schrieb Julian St.:
> Am Fr, 2003-04-04 um 23.30 schrieb Eric Anholt:
> > As the subject says, I'm wondering if anyone out there has experienced
> > hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
> > matrox (perhaps r128, too) cards using the upda
Eric, this isn't precisely the situation you asked about, but
it may be related.
I've had similar problems to what was noted by MKB but an
older setup.
I'm running 5.0-RELEASE on my I8K with the Mobility Radeon
7500 (M7 chip with 64MB) configured with XFree86-4.2.0_1,1
and DRI co
22:31
Till: [EMAIL PROTECTED]
Ämne: Anyone had hangs with Radeon, XF86 4.3.0, and DRI on logout?
As the subject says, I'm wondering if anyone out there has experienced
hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
matrox (perhaps r128, too) cards using the updated D
Am Fr, 2003-04-04 um 23.30 schrieb Eric Anholt:
> As the subject says, I'm wondering if anyone out there has experienced
> hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
> matrox (perhaps r128, too) cards using the updated DRM in -current and
> XFree86 4.3.0. If so, I may
Hi,
On Fri, 4 Apr 2003, Eric Anholt wrote:
> Date: 04 Apr 2003 13:30:39 -0800
> From: Eric Anholt <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Anyone had hangs with Radeon, XF86 4.3.0, and DRI on logout?
>
> As the subject says, I'm wondering if anyone out
On Fri, Apr 04, 2003 at 01:30:39PM -0800, Eric Anholt wrote:
> As the subject says, I'm wondering if anyone out there has experienced
> hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
> matrox (perhaps r128, too) cards using the updated DRM in -current and
> XFree86 4.3.0.
Eric Anholt wrote:
As the subject says, I'm wondering if anyone out there has experienced
hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
matrox (perhaps r128, too) cards using the updated DRM in -current and
XFree86 4.3.0. If so, I may have a fix, but I'm wondering if thi
As the subject says, I'm wondering if anyone out there has experienced
hangs on logging out from xdm (or perhaps switching VTs) with Radeon or
matrox (perhaps r128, too) cards using the updated DRM in -current and
XFree86 4.3.0. If so, I may have a fix, but I'm wondering if this
affects FreeBSD.
and they don't
even
> > compile under 5.x. I built kernel with "device
mgadrm"
> > and "options DRM_LINUX", as well as "options
> > COMPAT_LINUX". After launching glxgears system
hangs
> > up completely. Problem seems to be within libdrm.
So
ith FreeBSD 4.x, and they don't even
compile under 5.x. I built kernel with "device mgadrm"
and "options DRM_LINUX", as well as "options
COMPAT_LINUX". After launching glxgears system hangs
up completely. Problem seems to be within libdrm. So
far I have no DRI, but so
quot;options DRM_LINUX", as well as "options
COMPAT_LINUX". After launching glxgears system hangs
up completely. Problem seems to be within libdrm. So
far I have no DRI, but software OpenGL, and 162fps
compared to 368fps under 4.7.
---
Regards,
Rhett
___
From: "Chuck Robey" <[EMAIL PROTECTED]>
Sent: Monday, December 30, 2002 5:02 PM
> The moral is, I think you need to rebuild/reinstall dri-devel if you're
> running FreeBSD-current.
I have found that it's generally a good idea to rebuild any modules you have
from
To those of you running the radeon.ko dri module from the ports
(ports/graphics/dri-devel) IF YOU'RE RUNNING CURRENT then you might want
to listen up.
I just did a rebuild of the system for the first time in about 6 days, and
my system rebooted immediately when XFree86 attempted loadin
+---[ 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
+---[ David W. Chapman Jr. ]--
| Anyone know if -current supports Direct Rendering Infrastructure?
XFree4 supports it, it's not really a FreeBSD issue, other than
actually building the drm kernel module.
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | An
Anyone know if -current supports Direct Rendering Infrastructure?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
56 matches
Mail list logo
