Intel G965 graphics, X.org 7.2, and FreeBSD 6.2-RELEASE

On Jun 4, 7:04 pm, novem...@gmail.com wrote:
> On Jun 4, 3:16 pm, novem...@gmail.com wrote:
>
>
>
> > On Jun 2, 8:01 pm, conr...@cox.net (Conrad J. Sabatier) wrote:
>
> > > In article <1180649649.131164.137...@g4g2000hsf.googlegroups.c om>,
>
> > > wrote:
> > > >On May 31, 4:10 pm, "Conrad J. Sabatier" wrote:
> > > >> On Thu, 31 May 2007 13:56:25 -0700, novembre wrote:
> > > >> > On May 30, 3:30 pm, "Conrad J. Sabatier" wrote:
> > > >> >> On Wed, 30 May 2007 13:04:51 -0700, novembre wrote:
> > > >> >> > On May 28, 10:30 pm, "Conrad J. Sabatier" wrote:
>
> > > >> >> >> Well, just judging from the Xorg log output you've posted, it
> > > >> >> >> appears that the driver you're trying to use requires the agpgart
> > > >> >> >> device.
>
> > > >> >> >> Try manually loading the agp driver after booting and logging in
> > > >> >> >> with:
>
> > > >> >> >> kldload agp
>
> > > >> >> >> Then verify that the device is created:
>
> > > >> >> >> ls -l /dev/agpgart
>
> > > >> >> >> Then try starting X again, or reconfiguring X once more.
>
> > > >> >> >> If your device truly is *not* an AGP device, but the driver requires
> > > >> >> >> one, then you've got a real problem, to say the least. :-) Are you
> > > >> >> >> absolutely certain you're using the right driver?
>
> > > >> >> > "kldload agp" returns the following error message: ----- kldload:
> > > >> >> > can't load agp: File exists
> > > >> >> > -----
> > > >> >> > and so "ls /dev/" does not show any agp device...
>
> > > >> >> OK, so apparently, you have the agp device built into your kernel, but
> > > >> >> it's not configuring properly for some reason.
>
> > > >> >> Have you checked your BIOS setup? Some machines allow the graphics
> > > >> >> device to be configured as either a straight PCI device or as an AGP
> > > >> >> device.
>
> > > >> >> You can verify your kernel with 'kldstat|grep agp', BTW.
>
> > > >> >> --
> > > >> >> Conrad J. Sabatier
>
> > > >> > there is no mention of AGP in the BIOS on this machine. there is only a
> > > >> > PEG (PCI-Express Graphics, i guess) option. and i had tried 'kldstat'
> > > >> > before, and it does not show anything AGP either.
>
> > > >> > thanks
>
> > > >> Have you seen Michel Talon's followup in this thread? He had the same
> > > >> problem as you, upgraded to either 6-STABLE or 7-CURRENT, and it cured
> > > >> the problem.
>
> > > >> You may want to try a cvsup to STABLE, do a complete buildworld/
> > > >> buildkernel, and see if you get lucky.
>
> > > >> --
> > > >> Conrad J. Sabatier
>
> > > >yes, i have seen it...didn't have time to try it though one other
> > > >thing though: this graphics chip is PCI-Express and not AGP.
>
> > > >but i had installed -STABLE branch before, and that did not solve my
> > > >problem. so maybe i need to use the -CURRENT branch this time, but i'm
> > > >a bit reluctant, since i'm going to use this machine for numerical
> > > >calculations at the university, and i need something very stable (i
> > > >know that FreeBSD is the definition of stable, but the stability of -
> > > >CURRENT and -RELEASE branches are different IMO).
>
> > > FWIW, I've been running -CURRENT for quite some time now, and it's really
> > > pretty solid. Stability, I would say, is every bit the equal of -STABLE,
> > > or even of the latest -RELEASE.
>
> > > Right now, in fact, would be a good time to upgrade to -CURRENT, if you're
> > > so inclined. No earth-shaking changes in progress at the moment, so
> > > things are currently pretty well "settled" for the time being.
>
> > > >i don't like the idea of reinstalling the whole operating system, but
> > > >i also don't know how to replace only the agp module in the kernel.
> > > >how do i take the current agp module out from the kernel? do i need to
> > > >recompile the kernel? also, if i get the new agp source from, say, -
> > > >CURRENT, compile it myself, how can i load it? in loader.conf?
>
> > > Actually, since you mentioned before that kldstat showed no agp module, I
> > > have to wonder if you even have agp compiled into your kernel. Even if
> > > it's not working, it *should* still show up in kldstat.
>
> > I'm not quite sure what is wrong here! When booting, I can see the
> > loaded modules with 'lsmod', and agp is among them. Also, if I try to
> > load agp by 'load agp' there, it says that the module already exists.
> > Moreover, I do have load_agp="YES" in my loader.conf. And 'kldload
> > agp' returns
> > -----
> > kldload: can't load agp: File exists
> > -----
> > so I don't know what else to do to make 'kldstat' show the loaded agp
> > module!
>
> > > As far as using the agp module from -CURRENT, you could either build it
> > > into the kernel or load it as a module, it's up to you, and yes, it does
> > > require doing a "make buildkernel" either way (unless you have
> > > MODULES_WITH_WORLD defined in /etc/make.conf, in which case, of course,
> > > you'd need to do a buildworld as well).
>
> > > I would think, though, that it would be a lot simpler in the long run just
> > > to cvsup your source tree to -CURRENT, and do a full
> > > buildworld/buildkernel.
>
> > Thanks...I'll read the handbook whenever I get some free time to see
> > how I can upgrade the source tree and compile the kernel. Then I'll
> > report the results...
> > But still, I'm currently using agp.c, agp_intel.c, and agp_i810.c
> > (which I modified to include the devid of Intel G965) from the -
> > CURRENT branch, and the graphics chipset is not recognized. Do you
> > think that if I do the upgrade, it will help?
>
> > > >i apologize for all these questions, but i'm not very experience and
> > > >haven't done anything like this before.
>
> > > No problem, that's what this group is here for. :-)
>
> > Thanks so much. This is what I really like about FreeBSD groups...
>
> > > --
> > > Conrad J. Sabatier
>
> today, i again did some search on the net for Intel 965 graphics
> chipset and came up with the following post by Eric Anholt on the
> FreeBSD -CURRENT mailing list:http://docs.freebsd.org/cgi/getmsg.c...archive/2007/f...
>
> Considering that the mailing list post was made on April 20, 2007 and
> that the diff is made on top of agp_i810.c revision 1.39 (which was
> submitted 8 months ago to -CURRENT), I guess I was right in saying
> that this chip is still not supported even in the -CURRENT branch (I
> have compiled and am using 1.39 right now, and the chip is not
> detected). I'll try his patch and report back...


It seems that I can't compile the agp module after using his patch
which changes agp_i810.c and agpreg.h. I have been using -CURRENT
files agp.c, agp_intel.c, agp_i810.c, and agpreg.h and have applied
his patch on top of them. Do I need newer revisions of other files to
be able to compile that patch?

On Jun 6, 6:31 pm, novem...@gmail.com wrote:
> On Jun 4, 7:04 pm, novem...@gmail.com wrote:
>
>
>
> > On Jun 4, 3:16 pm, novem...@gmail.com wrote:
>
> > > On Jun 2, 8:01 pm, conr...@cox.net (Conrad J. Sabatier) wrote:
>
> > > > In article <1180649649.131164.137...@g4g2000hsf.googlegroups.c om>,
>
> > > > wrote:
> > > > >On May 31, 4:10 pm, "Conrad J. Sabatier" wrote:
> > > > >> On Thu, 31 May 2007 13:56:25 -0700, novembre wrote:
> > > > >> > On May 30, 3:30 pm, "Conrad J. Sabatier" wrote:
> > > > >> >> On Wed, 30 May 2007 13:04:51 -0700, novembre wrote:
> > > > >> >> > On May 28, 10:30 pm, "Conrad J. Sabatier" wrote:
>
> > > > >> >> >> Well, just judging from the Xorg log output you've posted, it
> > > > >> >> >> appears that the driver you're trying to use requires the agpgart
> > > > >> >> >> device.
>
> > > > >> >> >> Try manually loading the agp driver after booting and logging in
> > > > >> >> >> with:
>
> > > > >> >> >> kldload agp
>
> > > > >> >> >> Then verify that the device is created:
>
> > > > >> >> >> ls -l /dev/agpgart
>
> > > > >> >> >> Then try starting X again, or reconfiguring X once more.
>
> > > > >> >> >> If your device truly is *not* an AGP device, but the driver requires
> > > > >> >> >> one, then you've got a real problem, to say the least. :-) Are you
> > > > >> >> >> absolutely certain you're using the right driver?
>
> > > > >> >> > "kldload agp" returns the following error message: ----- kldload:
> > > > >> >> > can't load agp: File exists
> > > > >> >> > -----
> > > > >> >> > and so "ls /dev/" does not show any agp device...
>
> > > > >> >> OK, so apparently, you have the agp device built into your kernel, but
> > > > >> >> it's not configuring properly for some reason.
>
> > > > >> >> Have you checked your BIOS setup? Some machines allow the graphics
> > > > >> >> device to be configured as either a straight PCI device or as an AGP
> > > > >> >> device.
>
> > > > >> >> You can verify your kernel with 'kldstat|grep agp', BTW.
>
> > > > >> >> --
> > > > >> >> Conrad J. Sabatier
>
> > > > >> > there is no mention of AGP in the BIOS on this machine. there is only a
> > > > >> > PEG (PCI-Express Graphics, i guess) option. and i had tried 'kldstat'
> > > > >> > before, and it does not show anything AGP either.
>
> > > > >> > thanks
>
> > > > >> Have you seen Michel Talon's followup in this thread? He had the same
> > > > >> problem as you, upgraded to either 6-STABLE or 7-CURRENT, and it cured
> > > > >> the problem.
>
> > > > >> You may want to try a cvsup to STABLE, do a complete buildworld/
> > > > >> buildkernel, and see if you get lucky.
>
> > > > >> --
> > > > >> Conrad J. Sabatier
>
> > > > >yes, i have seen it...didn't have time to try it though one other
> > > > >thing though: this graphics chip is PCI-Express and not AGP.
>
> > > > >but i had installed -STABLE branch before, and that did not solve my
> > > > >problem. so maybe i need to use the -CURRENT branch this time, but i'm
> > > > >a bit reluctant, since i'm going to use this machine for numerical
> > > > >calculations at the university, and i need something very stable (i
> > > > >know that FreeBSD is the definition of stable, but the stability of -
> > > > >CURRENT and -RELEASE branches are different IMO).
>
> > > > FWIW, I've been running -CURRENT for quite some time now, and it's really
> > > > pretty solid. Stability, I would say, is every bit the equal of -STABLE,
> > > > or even of the latest -RELEASE.
>
> > > > Right now, in fact, would be a good time to upgrade to -CURRENT, if you're
> > > > so inclined. No earth-shaking changes in progress at the moment, so
> > > > things are currently pretty well "settled" for the time being.
>
> > > > >i don't like the idea of reinstalling the whole operating system, but
> > > > >i also don't know how to replace only the agp module in the kernel.
> > > > >how do i take the current agp module out from the kernel? do i need to
> > > > >recompile the kernel? also, if i get the new agp source from, say, -
> > > > >CURRENT, compile it myself, how can i load it? in loader.conf?
>
> > > > Actually, since you mentioned before that kldstat showed no agp module, I
> > > > have to wonder if you even have agp compiled into your kernel. Even if
> > > > it's not working, it *should* still show up in kldstat.
>
> > > I'm not quite sure what is wrong here! When booting, I can see the
> > > loaded modules with 'lsmod', and agp is among them. Also, if I try to
> > > load agp by 'load agp' there, it says that the module already exists.
> > > Moreover, I do have load_agp="YES" in my loader.conf. And 'kldload
> > > agp' returns
> > > -----
> > > kldload: can't load agp: File exists
> > > -----
> > > so I don't know what else to do to make 'kldstat' show the loaded agp
> > > module!
>
> > > > As far as using the agp module from -CURRENT, you could either build it
> > > > into the kernel or load it as a module, it's up to you, and yes, it does
> > > > require doing a "make buildkernel" either way (unless you have
> > > > MODULES_WITH_WORLD defined in /etc/make.conf, in which case, of course,
> > > > you'd need to do a buildworld as well).
>
> > > > I would think, though, that it would be a lot simpler in the long run just
> > > > to cvsup your source tree to -CURRENT, and do a full
> > > > buildworld/buildkernel.
>
> > > Thanks...I'll read the handbook whenever I get some free time to see
> > > how I can upgrade the source tree and compile the kernel. Then I'll
> > > report the results...
> > > But still, I'm currently using agp.c, agp_intel.c, and agp_i810.c
> > > (which I modified to include the devid of Intel G965) from the -
> > > CURRENT branch, and the graphics chipset is not recognized. Do you
> > > think that if I do the upgrade, it will help?
>
> > > > >i apologize for all these questions, but i'm not very experience and
> > > > >haven't done anything like this before.
>
> > > > No problem, that's what this group is here for. :-)
>
> > > Thanks so much. This is what I really like about FreeBSD groups...
>
> > > > --
> > > > Conrad J. Sabatier
>
> > today, i again did some search on the net for Intel 965 graphics
> > chipset and came up with the following post by Eric Anholt on the
> > FreeBSD -CURRENT mailing list:http://docs.freebsd.org/cgi/getmsg.c...archive/2007/f...
>
> > Considering that the mailing list post was made on April 20, 2007 and
> > that the diff is made on top of agp_i810.c revision 1.39 (which was
> > submitted 8 months ago to -CURRENT), I guess I was right in saying
> > that this chip is still not supported even in the -CURRENT branch (I
> > have compiled and am using 1.39 right now, and the chip is not
> > detected). I'll try his patch and report back...
>
> It seems that I can't compile the agp module after using his patch
> which changes agp_i810.c and agpreg.h. I have been using -CURRENT
> files agp.c, agp_intel.c, agp_i810.c, and agpreg.h and have applied
> his patch on top of them. Do I need newer revisions of other files to
> be able to compile that patch?


okay, here are error messages when I compiled the patched versions of
agp_i810.c and agpreg.h plus the -CURRENT versions of agp.c and
agp_intel.c:

----------
(*) when compiling agp.c:
/usr/src/sys/modules/agp/../../pci/agp.c: In function 'agp_find_caps':
/usr/src/sys/modules/agp/../../pci/agp.c:101: warning: implicit
declaration of function 'pci_find_extcap'
/usr/src/sys/modules/agp/../../pci/agp.c:101: warning: nested extern
declaration of 'pci_find_extcap'

(*) when compiling agp_i810.c:
/usr/src/sys/modules/agp/../../pci/agp_i810.c: In function
'agp_i810_attach':
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: implicit
declaration of function 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:401: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:415: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:437: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:448: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:470: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:500: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:545: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:554: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c:588: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
/usr/src/sys/modules/agp/../../pci/agp_i810.c: In function
'agp_i810_detach':
/usr/src/sys/modules/agp/../../pci/agp_i810.c:640: warning: nested
extern declaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
redeclaration of 'bus_release_resources'
/usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
implicit declaration of function 'bus_release_resources' was here
*** Error code 1

Stop in /usr/src/sys/modules/agp.
----------

It seems that 'bus_release_resources' is being redeclared in a lot of
different places if I'm not mistaken. I didn't have the time to look
at the sources yet. Also I realized that the switches -Wredundant-
decls and -Wnested-externs are being used in cc to compile the
sources.
So is just it stopping because of the warnings?

novembre-at-gmail.com wrote:
> /usr/src/sys/modules/agp/../../pci/agp_i810.c:640: warning: nested
> extern declaration of 'bus_release_resources'
> /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
> redeclaration of 'bus_release_resources'
> /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
> implicit declaration of function 'bus_release_resources' was here
> *** Error code 1
>
> Stop in /usr/src/sys/modules/agp.
> ----------
>
> It seems that 'bus_release_resources' is being redeclared in a lot of
> different places if I'm not mistaken. I didn't have the time to look
> at the sources yet. Also I realized that the switches -Wredundant-
> decls and -Wnested-externs are being used in cc to compile the
> sources.
> So is just it stopping because of the warnings?
>

Are you sure there is no
error:
message? warnings should not stop the compilation, except perhaps with
special compilation flags.

--

Michel TALON

On Jun 7, 3:14 am, t...@lpthe.jussieu.fr (Michel Talon) wrote:
> novem...@gmail.com wrote:
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:640: warning: nested
> > extern declaration of 'bus_release_resources'
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
> > redeclaration of 'bus_release_resources'
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
> > implicit declaration of function 'bus_release_resources' was here
> > *** Error code 1
>
> > Stop in /usr/src/sys/modules/agp.
> > ----------
>
> > It seems that 'bus_release_resources' is being redeclared in a lot of
> > different places if I'm not mistaken. I didn't have the time to look
> > at the sources yet. Also I realized that the switches -Wredundant-
> > decls and -Wnested-externs are being used in cc to compile the
> > sources.
> > So is just it stopping because of the warnings?
>
> Are you sure there is no
> error:
> message? warnings should not stop the compilation, except perhaps with
> special compilation flags.
>
> --
>
> Michel TALON


Oops! I just checked the message again and realized that I had missed
this one:

/usr/src/sys/modules/agp/../../pci/agp_i810.c:100: error: field
'resource_specs' has incomplete type

And here is the definition of 'resource_specs in agp_i810.c:

struct agp_i810_softc {
..
..
..
/* list of allocated resources */
struct resource_spec resource_specs[4];
struct resource *resources[4];
int resource_count;
};

Thanks

On Jun 7, 3:14 am, t...@lpthe.jussieu.fr (Michel Talon) wrote:
> novem...@gmail.com wrote:
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:640: warning: nested
> > extern declaration of 'bus_release_resources'
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
> > redeclaration of 'bus_release_resources'
> > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
> > implicit declaration of function 'bus_release_resources' was here
> > *** Error code 1
>
> > Stop in /usr/src/sys/modules/agp.
> > ----------
>
> > It seems that 'bus_release_resources' is being redeclared in a lot of
> > different places if I'm not mistaken. I didn't have the time to look
> > at the sources yet. Also I realized that the switches -Wredundant-
> > decls and -Wnested-externs are being used in cc to compile the
> > sources.
> > So is just it stopping because of the warnings?
>
> Are you sure there is no
> error:
> message? warnings should not stop the compilation, except perhaps with
> special compilation flags.
>
> --
>
> Michel TALON

Oops! I just checked the message again and have realized that I had
missed this error message:

/usr/src/sys/modules/agp/../../pci/agp_i810.c:100: error: field
'resource_specs' has incomplete type

and here is the definition of 'resource_specs' in agp_i810.c:

struct agp_i810_softc {
..
..
..
/* listof allocated resources */
struct resource_spec resource_specs[4];
struct resource *resources[4];
int resource_count;
};

Thanks

novembre-at-gmail.com wrote:

> I'm not quite sure what is wrong here! When booting, I can see the
> loaded modules with 'lsmod', and agp is among them. Also, if I try to
> load agp by 'load agp' there, it says that the module already exists.
> Moreover, I do have load_agp="YES" in my loader.conf. And 'kldload
> agp' returns
> -----
> kldload: can't load agp: File exists
> -----
> so I don't know what else to do to make 'kldstat' show the loaded agp
> module!

As far as I can remember, I have never seen kldstat displaying something
which was compiled into the kernel. To me, kldstat only showed things
which were not included in the kernel but was separately loaded from a .ko
kernel module file (regardless of being loaded manually by kldload or
automatically from loader.conf).
And that was my experience on 4.x, 5.x and 6.x too.

So if I were you, I wouldn't really try too hard to see agp in kldstat if
it is compiled into your kernel.

> kldload: can't load agp: File exists

This is a perfect sign that the agp module is already there for you, most
probably being built-into the kernel.

I hope this helps a little!

Regards,
Keve

--
Keve Nagy * Debrecen * HUNGARY
if you need to reply directly:
keve(at)mail(dot)poliod(dot)hu

On Jun 7, 2:18 pm, novem...@gmail.com wrote:
> On Jun 7, 3:14 am, t...@lpthe.jussieu.fr (Michel Talon) wrote:
>
>
>
> > novem...@gmail.com wrote:
> > > /usr/src/sys/modules/agp/../../pci/agp_i810.c:640: warning: nested
> > > extern declaration of 'bus_release_resources'
> > > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: redundant
> > > redeclaration of 'bus_release_resources'
> > > /usr/src/sys/modules/agp/../../pci/agp_i810.c:389: warning: previous
> > > implicit declaration of function 'bus_release_resources' was here
> > > *** Error code 1
>
> > > Stop in /usr/src/sys/modules/agp.
> > > ----------
>
> > > It seems that 'bus_release_resources' is being redeclared in a lot of
> > > different places if I'm not mistaken. I didn't have the time to look
> > > at the sources yet. Also I realized that the switches -Wredundant-
> > > decls and -Wnested-externs are being used in cc to compile the
> > > sources.
> > > So is just it stopping because of the warnings?
>
> > Are you sure there is no
> > error:
> > message? warnings should not stop the compilation, except perhaps with
> > special compilation flags.
>
> > --
>
> > Michel TALON
>
> Oops! I just checked the message again and realized that I had missed
> this one:
>
> /usr/src/sys/modules/agp/../../pci/agp_i810.c:100: error: field
> 'resource_specs' has incomplete type
>
> And here is the definition of 'resource_specs in agp_i810.c:
>
> struct agp_i810_softc {
> .
> .
> .
> /* list of allocated resources */
> struct resource_spec resource_specs[4];
> struct resource *resources[4];
> int resource_count;
>
> };
>
> Thanks


The problem was that 'resource_spec' was not defined in /usr/src/sys/
sys/bus.h as it should have been! I downloaded the -CURRENT version of
bus.h, but with that I got tons of errors, so I reverted back to the
6.2-RELEASE version and added the following definition of
'resource_spec' from -CURRENT bus.h:

struct resource_spec {
int type;
int rid;
int flags;
};

Then, the compilation went okay (I was still getting all the warnings
listed on my previous post, but they are just warnings). Then again,
'kldxref /boot/kernel' was done by 'make' itself, so I just rebooted
the machine. Again, at the loader prompt, 'lsmod' shows 'agp.1', so I
assume that agp is in the kernel.
But after booting, 'dmesg | grep agp' returns nothing, 'kldstat' shows
no agp, and 'pciconf -lv' returns 'none0ci0:2:0: ...' as before for
the VGA device.
So Eric Anholt's patch does not work on my machine, and I have no idea
why...maybe I should completely update my source tree to -CURRENT and
do a recompile of the agp module. I guess I'll also try posting in the
-CURRENT mailing list to see if Eric will help me in this case.

Any suggestions would be greatly appreciated...

On Jun 10, 11:20 am, Keve Nagy wrote:
> novem...@gmail.com wrote:
> > I'm not quite sure what is wrong here! When booting, I can see the
> > loaded modules with 'lsmod', and agp is among them. Also, if I try to
> > load agp by 'load agp' there, it says that the module already exists.
> > Moreover, I do have load_agp="YES" in my loader.conf. And 'kldload
> > agp' returns
> > -----
> > kldload: can't load agp: File exists
> > -----
> > so I don't know what else to do to make 'kldstat' show the loaded agp
> > module!
>
> As far as I can remember, I have never seen kldstat displaying something
> which was compiled into the kernel. To me, kldstat only showed things
> which were not included in the kernel but was separately loaded from a .ko
> kernel module file (regardless of being loaded manually by kldload or
> automatically from loader.conf).
> And that was my experience on 4.x, 5.x and 6.x too.
>
> So if I were you, I wouldn't really try too hard to see agp in kldstat if
> it is compiled into your kernel.
>
> > kldload: can't load agp: File exists
>
> This is a perfect sign that the agp module is already there for you, most
> probably being built-into the kernel.
>
> I hope this helps a little!
>
> Regards,
> Keve
>
> --
> Keve Nagy * Debrecen * HUNGARY
> if you need to reply directly:
> keve(at)mail(dot)poliod(dot)hu


Keve Nagy, I just saw your post! Thanks for replying
I'm basically a newbie, so please guide me here...the fact that
'kldload agp' shows 'kldload: can't load agp: File exists' means that
the module is compiled into the kernel, so whatever I'm doing here
(updating the sources, compiling agp from /usr/src/sys/modules/agp/,
kldxref /boot/kernel) is useless?
I mean do I need to unload the built-in agp module from the kernel and
load the new one which I have just compiled (is it even possible to do
OR do I need to recompile the whole kernel?)? And if so, how am I
supposed to do the unload/load? And if not, does 'make all install
clean' do it by executing 'kldxref /boot/kernel'?

Thanks

novembre-at-gmail.com wrote:
> Keve Nagy, I just saw your post! Thanks for replying
> I'm basically a newbie, so please guide me here...the fact that
> 'kldload agp' shows 'kldload: can't load agp: File exists' means that
> the module is compiled into the kernel, so whatever I'm doing here
> (updating the sources, compiling agp from /usr/src/sys/modules/agp/,
> kldxref /boot/kernel) is useless?

As i said in my first post, remove device agp from kernel config file,
and compile a new kernel if you want to play with agp as a module.
Otherwise it will never load, of course.

--

Michel TALON

On Jun 12, 2:41 am, t...@lpthe.jussieu.fr (Michel Talon) wrote:
> novem...@gmail.com wrote:
> > Keve Nagy, I just saw your post! Thanks for replying
> > I'm basically a newbie, so please guide me here...the fact that
> > 'kldload agp' shows 'kldload: can't load agp: File exists' means that
> > the module is compiled into the kernel, so whatever I'm doing here
> > (updating the sources, compiling agp from /usr/src/sys/modules/agp/,
> > kldxref /boot/kernel) is useless?
>
> As i said in my first post, remove device agp from kernel config file,
> and compile a new kernel if you want to play with agp as a module.
> Otherwise it will never load, of course.
>
> --
>
> Michel TALON


Thanks I just did that and compiled the kernel again after removing
'device agp' from the kernel configuration file using 6.2-RELEASE
versions of all agp* files (using -CURRENT versions would result in
errors when compiling). After compiling and installing the kernel, I
recompiled the agp module using the -CURRENT versions of agp.c,
agp_intel.c and patched versions of agp_i810.c, agpreg.h, and bus.h
and rebooted the machine. At the loader prompt, 'lsmod' shows agp
loaded as a module now:

0xae6000: /boot/kernel/agp.ko (elf module. 0x14768)
modules: agp.1

but after booting, I get the following error message in 'dmesg':

link_elf: symbol pci_find_extcap undefined
KLD file agp.ko - could not finalize loading

I checked the sources from CVS online, and pci_find_extcap was
mentioned in agp.c and drm_agpsupport.c. So I decided to load the i915
module at the loader prompt as well (which automatically loads drm.ko
as well), but that made the computer freeze right after booting!

A little search confirmed that pci_find_extcap was added to agp.c in
revision 1.46.2.2 (whereas 6.2-RELEASE uses 1.46.2.1) and to
drm_agpsupport.c (in /usr/src/sys/dev/drm/) in revision 1.1.2.4
(whereas 6.2-RELEASE uses 1.1.2.3). In fact, the only difference
between the two revisions of drm_agpsupport.c is that 1.1.2.4 uses the
updated __FreeBSD_version check for pci_find_extcap() that is now
present in 6.x. So I'm assuming that I have to update drm_agpsupport.c
to 1.1.2.4 and recompile the kernel.

I just realized that i915_drm.h is also updated to include support for
Intel 965 Express Chipset. I guess I need to update more files then...

Thanks