ried
seeing if using a Nov 16th vinum binary would load them, but after doing
a stop/start, the system paniced, and it seems my swap is too small to
dump on. Kernel was built using configure MYKERNEL; cd
../compile/MYKERNEL; make depend all install instead of buildk
gt; Jason
This error has been reported by both FreeBSD and Linux users for several
months. Does it prevent the DRI from initializing? Looks like it
should. Under what circumstances do you get this error?
--
Eric Anholt[EMAIL PROTECTED]
http://peo
debug this. How can I disable agp0 on boot time?
Would this be appropriate to commit to AGP, to disable the ali agp in
case it reports 0 size (perhaps something in the BIOS has disabled it?)
and to have agp_alloc_gatt() just fail instead of panicing in
contigmalloc if the aperture size is 0?
--
Eri
nfig(s)? Or is this a real
> Problem?
Linux users have also been experiencing those *ERROR* messages. I'm not
sure what's going on here. I don't think the hangs are related to the
error, since Linux people haven't been complaining about hangs. The agp
message, however, is
cribed to
> -stable.
5.1 is -current, not -stable, so you should be mailing the -current
list. I've reset the cc: appropriately.
If you're not using up to date -current, please upgrade to -current past
October 24th, which included some DRM IRQ fixes. If the problem
persists, c
sion), but I don't
have the time for it myself. One thing that's been suggested by linux
folks for other purposes is getting things fixed so that only KDE things
that need libGL to link to libGL.
--
Eric Anholt[EMAIL PROTECTED]
http
if
glxgears is your only app running, in which case you'll get a server
regenerate on exit of glxgears.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
really start KDE up fully, because it's a read-only netboot
system, which KDE didn't like very much.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EM
all+0x310
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x280bed2f, esp = 0xbfbff38c, ebp
> = 0xbfbff3b8 ---
>
> Any idea?
I just committed a fix for this to CVS. Sorry for the trouble.
--
Eric Anholt
> Same here, using an Ati Radeon R100. I see functions that have 'radeon' in the
> name in the trace. Is there any more information I can provide?
Not sure what went wrong here. I'm cvsupping to do a fresh build (going
really slow, our internet con
ied adding a line like this
>
> BusID"PCI 01:00:0"
>
> to Section "Device"? Maybe also try "PCI 1:0:1"
> I had the same error with a different card and this helped.
Actually, the problem here (as I just replied in a private email) was
that that card
On Tue, 2003-08-26 at 20:37, Glenn Johnson wrote:
> On Tue, Aug 26, 2003 at 01:27:11PM -0700, Eric Anholt wrote:
>
> > On Tue, 2003-08-26 at 18:05, Vulpes Velox wrote:
> >
> > > I had similar problem with a 7200 and OGL. I solved the problem by
> > > turn
g these ports), but it should include radeon 9800 support.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.or
On Tue, 2003-10-21 at 15:42, Scott Long wrote:
> Eric Anholt wrote:
> > Is there any concept of PCI domains in the kernel?
> >
> > This is for the DRM, while dealing with a complaint from Linus recently:
> >
> >
> >>Please fix the fact that mod
quot;,
> which allows fro multiple independent PCI subsystems in the same machine.
>
> On linux, you can use "pci_name(pdev)" to get a truly unique descriptor of
> the device (within the PCI subsystem). It will look something like
>
> :00:02.0
>
> fo
On Thu, 2003-10-16 at 23:03, Eric Anholt wrote:
> I've been working on locking of the DRM, based off of the work that was
> already done for linux and ported to BSD. I think the current locking
> was wrong, including that it used lockmgr and simplelocks on -stable
> when as far
.[ch] ./
Quick question: If open returns an error, close doesn't get called, does
it?
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing
Error code 1
>
> Stop in /home/FreeBSD/ports/x11/XFree86-4-clients.
> *** Error code 1
>
> Stop in /home/FreeBSD/ports/x11/XFree86-4.
>
> I had this same error a week ago, someone have a clue?
Fixed yesterday. cvsup and try again.
(The fix is in XFree86-4-libraries/file
to make
> /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop
>
> Dave.
It should be fixed now. Please cvsup (in ~1hour) and try again.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org
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 a
n't find any change I (or anyone else) has made
that would have caused this.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
htt
h this. I'll be updating XFree86-4-Server-snap when I can so
people can try this out.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EMAIL PROTECTED]
/bin/XFree86 -auth /var/run/xauth/A:0-2CitM
>
> What is ode? Typo? pid?
>
> I don't see how XFree86 can use i386_set_ldt(). It doesn't
> reference it on my box:
>
> $ nm /usr/X11R6/bin/XFree86 | grep ldt
> $
XFree86 loads various modules from /usr/X
-B to
kill the server, then startx again. The second time, the screen
displays for a brief moment then goes black. The system isn't hung, and
I can exit using C-A-B again. Is this what everyone else sees?
Everyone that's experiencing this and is using t
ts FreeBSD.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
pci/agp_i810.c: In function `agp_i810_match':
> > /usr/src/sys/pci/agp_i810.c:112: `AGP_I85X_CAPID' undeclared (first use in this
>function)
>
> Revert sys/pci/agp_i810.c to revision 1.16 and it will all build fine.
Or cvsup as of 7 hours ago.
--
Eric Anholt
/des/src/sys/pci/agp_i810.c:353: `AGP_I855_GCC1_GMS_STOLEN_16M' undeclared (first
>use in this function)
> /h/des/src/sys/pci/agp_i810.c:356: `AGP_I855_GCC1_GMS_STOLEN_32M' undeclared (first
>use in this function)
> *** Error code 1
I'm very sorry abo
only.
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/34030
seems to be a similar problem.
We've seen this with the agp module when it's in the kernel and in
loader.conf. In the agp case, it appears to initialize, but then
doesn't function when other devices (DRM) try to use it. I
n this
> happening since the update from revision 5 to 6 of the port (I'm not
> sure about the exact date, but I think it happened about a week or so
> ago.) Has anyone seen this? How do I fix it?
Please remove your nonstandard CFLAGS and try again.
--
Eric Anholt
ll still be able to get the information from it. (The
question is whether imake is detecting whether that flag is available in
gcc or not).
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
To Unsubscribe: send mai
On Wed, 2003-01-29 at 15:17, Eric Anholt wrote:
> On Wed, 2003-01-29 at 11:29, Charlie ROOT wrote:
> > On Tue, 28 Jan 2003, joseph wrote:
> >
> > > Try a make build world and see if that version of libc_r works.
> > > It should fix the problem. joseph
> >
b/modules/fonts/libbitmap.a is
> unresolved!
I'm sorry this error was still around. Apparently I had looked at a CVS
version of X when trying to figure out why it was happening, and CVS X
has it fixed. Until I commit a fix, you can add -fno-merge-constan
PI to calculate font sizes more and more. For
some reason it's probed wrong on my system (2500mm x 2500mm or some
such). Adding the following line to my XF86Config's Monitor section
fixed it.
DisplaySize 310 270
If this is the problem, could you tell me what card you&
it seemed close enough. IIRC, it wasn't
The 'ati' driver detects what type of ATI card you have and loads the
appropriate driver (radeon, r128, atimisc).
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/dri/ [EMAIL
binaries to use
the DRI.
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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 1
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 curren
n is fine. Typing blind works
> too.
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?
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
* We must call VOP_INACTIVE with the node locked.
2165 * If we are doing a vput, the node is already locked,
2166 * but, in the case of vrele, we must explicitly lock
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To
the alarm. Finding where
the server is sitting would be valuable.
If you have a hardware cursor and smooth mouse on (it's default) you'll
still be able to move the mouse because the mouse response is done in a
signal handler, so a busy server doesn't make your mouse stop working.
Sti
On Sun, 2002-10-13 at 23:00, Eric Anholt wrote:
> On Sun, 2002-10-13 at 21:14, Kris Kennaway wrote:
> > On Sun, Oct 13, 2002 at 11:28:51PM -0400, Wesley Morgan wrote:
> >
> > > I know there is some work being done on the recent signal changes to fix
> > > some th
ber or
-stable? If not, without some sort of hints of where an issue really
is, I'm going to chalk this up to kernel bugs.
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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 was a mozilla bug that was supposed to
be fixed.
--
Eric Anholt <[EMAIL PROTECTED]>
htt
curity holes.
I wish we could accept having some sort of suid Xwrapper installed with
XFree86-4-Server, but that would probably be shot down for security
concerns by those who don't use startx.
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe:
.pl. Stop
I'm aware of this one. Currently the solution is "use portupgrade -RiN
XFree86-4". I hope to get these dependencies fixed so it's not
necessary to do this, but I haven't made it around to that yet.
Also, for anyone reading this, one thing that'll help figure
On Wed, 2002-07-17 at 20:59, Peter Wemm wrote:
> Eric Anholt wrote:
>
> > This looks like the classic error of the agp module having been loaded
> > by the drm because it's required, but agp doesn't probe/attach because
> > a generic bridge driver has already cl
as no problem
> initializing agpgart when XDM starts up. I do not know why I
> started to need that line in /boot/loader.conf, when I had never
> actually needed it before (and I've never had 'device agp' in my
> kernel). But, I'm happy enough to have finally tracked
On Tue, 2002-07-16 at 19:38, Garance A Drosihn wrote:
> At 7:27 PM -0600 7/16/02, Eric Anholt wrote:
> >It notably doesn't include md5summing of Wraphelp.c. If I can
> >find what's the 'best' Wraphelp.c (and most legal? What's the
> >status of wraph
On Tue, 2002-07-16 at 17:25, Eric Anholt wrote:
> As far as the Wraphelp.c issues, I'm working on cleaning that mess up
> right now (testing the patch on a full XFree86-4 build on clean
> -current).
I've put the patch up at
http://people.freebsd.org/~anholt/files/x420
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 2002-07-13 at 11:23, Michael Nottebrock wrote:
> Eric Anholt wrote:
> I have just compiled a world with the 20020711.diff. It sure runs fast,
> but the quality isn't very good. I tested with glxgears and gltron and
> in both there is a lot of flashing and lighting er
On Fri, 2002-07-12 at 13:49, Stanislav Grozev wrote:
> On Fri, Jul 12, 2002 at 01:06:31PM -0600, Eric Anholt wrote:
> > Luckily for you, support for mach64s (Rage Pros specifically, which I
> > think your chip is) is being worked on in DRI CVS, so it should be
> > available
the
Mach64 DRM from Linux to the Linux/BSD framework we've got in DRI CVS
now. It's a pretty straightforward process now for most chipsets, but
does take some time.
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
stall for imake in /usr/ports/devel/imake-4
===> Extracting for imake-4.2.0_1
>> Checksum OK for xc/X420src-1.tgz.
===> imake-4.2.0_1 depends on executable: perl5.6.1 - found
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
Index: Mk/bsd.port.mk
===
On Thu, 2002-07-11 at 13:49, Eric Anholt wrote:
> http://people.freebsd.org/files/x420diff-1), I would be happy to
Augh, why can't I type?
http://people.freebsd.org/~anholt/files/x420diff-1
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe
in
particular, I think the perl dependency is missing in some of them, but
I'm not sure if it's a compile-time only dependency as iirc other
X-related ports require it as a run_depends, too)
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscr
t.h
> and nothing showed up. any ideas?
Missed the N on my cvs diff -uN. New patch is uploaded, including not
stripping FreeBSD ID tags.
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsu
On Wed, 2002-07-10 at 17:17, Eric Anholt wrote:
> I've posted a diff to the DRM at
> http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta
Evolution's "send" button is way too big.
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff
is t
I've posted a diff to the DRM at
http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta
--
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
(0) [76])
(nil)))
../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in
failed_reload, at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See http://www.gnu.org/software/gcc/bugs.html> for instructions.
If someone is interested I can give
On Fri, 2002-04-26 at 01:03, moto kawasaki wrote:
>
> Thank you very much, Mr. Eric Anholt,
>
> I have been testing your code on my PC, and found that kernel cannot
> initialize agpgart device so far.
The i8x0 DRM drivers require AGP to be working. I took a look at your
i830 p
The DRM kernel modules (kernel support for 3d hardware acceleration
through the DRI) may be integrated into our sys tree soon. I may be
getting a commit bit soon to work on this. I think getting the modules
in the sys tree will help keep the DRI supported on FreeBSD even if I
become less active,
a very nasty connection that keeps dropping and making me route
delete, ifconfig -a ( & repeat), route add again.
If there is any other info needed, I would be glad to post.
--
--
Eric Anholt
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
othing.)
>On Mon, 10 Jul 2000 10:39:44 MST, Eric Anholt wrote:
>
>> Nope, same old device sc 1. I've tried unmodified GENERIC, and it
>> does the same thing. Why am I special?
>
>I believe that the attached commit message describes the fix to the
>problem. How
nd.
A few bits of the hints, as reported by "show" from the loader
console=vidconsole
hint.atkbd.at=atkbdc
hint.atkbd.0.flags=0x1
hint.atkbd.0.irq=1
hint.atkbdc.0.at=isa
hint.atkbdc.0.port=0x060
hint.sc.0.at=isa
hint.sc.0.flags=0x100
hint.vga.0.at=isa
hint.vt.0.at=isa
Any help wo
the OS
detection.
If you drop a #define __FreeBSD__ in config/cf/Imake.cf, it'll detect and
get at least farther along. (still having troubles compiling from their
cvs, going to submit a report rsn). Hopefully we can find a bit nicer way
of doing things soon.
--
Eric Anholt
[EMAIL PROTECTED]
66 matches
Mail list logo
