agp_try_unsupported=1 ??

[Balthasar]

I have a computer with the Apollo DDR 266 motherboard, that has an unsupported AGP chipset. I have read and been told to use the agp_try_unsupported=1 in modules.conf .

I was wondering if anyone had any suggestions and tell me if this would be right..

[chrispy]

First of all, you need to have the agpgart option compiled as module with your kernel. (choose the (M) next to it instead of a (*) )
recompile the kernel, reboot.

then, open the /etc/modules.d/aliases

[Balthasar]

Still no Direct Rendering...

The output from dmesg :

[chrispy]

so you have the DRI option set and NONE of the DRM modules compiled in ? (either as module or built-in)

Have you tried with gatos as well ?

first thing I think of is : since you have agpgart working, try those :

[Balthasar]

Yea, I had the radeon compiled in as module in the kernel.

I removed the modules after I made the changes and whatnot, just to make sure they got loaded properly.

You have the same board ? If you got that working with mm-sources, I have no problem trying those. This is actually my friends computer I'm working on, I normally use ac-sources, but those didn't seem to compile on his box.

[chrispy]

no, I don't have that board, I just had the same "agp_try_unsupported=1" problem with a VIA chipset on a Shuttle board, and couldn't get agp working until I tried with mm-sources, because they include more drivers.

gentoo-sources is a nice set, but for tricky hardware it can be a pain to get it to work. I never tried ac-sources.

changing to a dev kernel can be source of troubles (I experienced many headaches before I got it right) so unless you're comfortable with having 2 totally different kernels on the same computer (having to re-link the /usr/src/linux-beta etc, etc...) I wouldn't recommend it.

Please see what happens if you compile the radeon as a static option in the kernel first.

[Balthasar]

I can't compile is statically unless the agpgart option is also static, and wouldn't that cause the agp_try_unsupported=1 to be useless ?

My apologies for not knowing, I have no problem trying things, but kernels have kinda confused me since I started. I am comfortable working with them to get things working, as I have also had a friend who got the brand spanking new (at the time) via82xxx chipset, which I ended up going through about 4 kernels before finding one with the support for it.

So trying things is no problem

[chrispy]

ah yeah, I spoke too fast :/

well, the via chipset IS fully supported in the mm-sources without having to use strange module options, but I can't stress it enough, it's "risky".

now, you say the radeon drm is not loaded in X ... but, can you find the related output in the xfree logs ?


Once you get the agp thing working in the kernel, it's just a matter of sorting things in X, and I know that there are a lot of threads about using radeon cards...

[Balthasar]

Well it seems the drm module loads. but the Direct Rendering Support isn't there.

Here is what I get from glxinfo:

[chrispy]

uhm k
but what about the Xfree log ??
how did you configure X ?

and what USE flags are/were you using to compile Xfree ?

the 2.5 kernels compile pretty much like a 2.4 one, with some variations, and some stuff you need to activate in order to work correctly in gentoo.
I suggest some careful reading so you know what problems you might be facing with a 2.5 kernel :
https://forums.gentoo.org/viewtopic.php?t=62490
https://forums.gentoo.org/viewtopic.php?t=61212
https://forums.gentoo.org/viewtopic.php?t=56676

[Balthasar]

I think the agpgart part may be working now, since I am no longer getting the error that told me to try the agp_try_unsupported=1

Now I am using the module that is included with the kernel, since with my Radeon 7500 at home I have had more luck with using that module, but looking at the X log I found where the it has a problem loading the radeon module, and says the DRI options will be disabled

[Balthasar]

Sorry, GL is still working, just had to run opengl-update ati..

[chrispy]

Then don't load the radeon module and try to use the one included in Xfree. This one should not complain about version mismatch.


[edit]
by the way, check those out :
https://forums.gentoo.org/viewtopic.php?t=54793&highlight=radeon+dri
https://forums.gentoo.org/viewtopic.php?t=63675&highlight=radeon+dri
https://forums.gentoo.org/viewtopic.php?t=29264&highlight=radeon+dri
[/edit]

[Balthasar]

Yea, I'm cycling through testing each of the different ATI driver sets now, I'm also working on the 2.5 branch, that seems to has many benefits, I'm sure many downsides as well being a dev. kernel, but if I can get it working, without all the hassle, I'd be worth it.

I will have this working in the next 24 hrs... I hope..

Thanks

[chrispy]

good luck to you, and remember to have a working kernel to boot from in case of emergency ! be sure to report your progresses here

cheers

[Balthasar]

Always keeping my working kernel as the default

I remember a time when I didn't do that (still just a n00b then), man do rescue disk ever help! Stupid debian kernel config, heh.

Currently, I'm trying the 2.5 kernel on my system, just to see if I can get one running at all, is there anything VITAL I should know about install 2.5 ? Or is it basically the same , minus the new make options of course.

[chrispy]

basically same, i can't access my machine right now so i cannot paste some examples, but :
be sure to check the "virtual filesytem" (or something to that extent) section in the config and get the /proc fs and the /dev fs compiled in
well, pretty much everything is "common sense", just be certain to check all the sections carefully. (as long as you don't have anything "exotic" you will have a working dev kernel in no time)

[Balthasar]

Do you know if any know issues with the 3c59x module ?

It seems either way if I compile it in, or load as module, network doesn't work.
I also cannot open terminals while in X for some reason.. Perhaps I should post this elsewhere, but figured I'd ask here first.

[chrispy]

for the 3com card i don't know. but for the X terminals, very easy :
be sure to compile devpts in the kernel and add to your fstab :

[deathdruid]

For development kernels, you need module-init-tools.