I wonder if the package maintainer of kernel26 in CURRENT to be able to have every updated kernel modified for ATI.
All he has to do is change these in config:
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_RADEON_DEBUG is not set
So in every update of the kernel we don't have to recompile it.
Thank you in advance!
Powered by Arch Linux
There is ABSOLUTELY no point reporting this here - you should have put it in the bugtracker months and months ago!
Take the most recent Arch config, make the changes you suggest, make a diff and submit the diff on the bugtracker with the reasons as to why it should be done. I am certain that, unless there is a good reason not to, Judd will then include the changes in the next release.
From then I will rebuild the ati-drivers against the stock kernel
This is a suggestion and not bug that could HELP all Ati users out there and not just me.
I have been using Arch Linux for 2 months now and linux in general for about 8 months and I am very satisfied by the Arch distro.
I am quite a newbie in linux so making this diff is not in my knowledge yet and if I knew it I would have done it. Yes I am NOT a linux guru but I can make my system running Arch and any other distro quite easily.
Sorry reporting it in the first place.
(Although Gentoo is not for newbies people in their forum always seem more friendly)
Powered by Arch Linux
dude, I am, and always have been, trying to help you and numerous other people with those ati-drivers so I think you owe me an apology there!
I'll do it myself shall I? I'll make the config file, the diff and submit the bug for you.
I also charge $200 an hour so I hope you have a paypal account
Friend I didn't try to offend you in any way because I recognise your contribution in the ATI drivers problem.
My suggestion was meant only to improve an already great distro that I use everyday.
I told you if I knew how to do it I could do it myself. If you cannot do it maybe someone else who charges less ($200 per hour is way out of my budget) !!
Your previous post was rather aggressive for a linux newbie like me. I don't know everything about linux but using this distro I learned quite a few things.
Powered by Arch Linux
Well, sorry if you thought it was agressive - it was supposed to be exasperated. Here is the diff file:
diff -Naur config config-new --- config 2005-07-20 13:13:08.000000000 +0100 +++ config-new 2005-08-09 18:06:58.000000000 +0100 @@ -1572,17 +1574,17 @@ # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set -CONFIG_AGP=y -CONFIG_AGP_ALI=y -CONFIG_AGP_ATI=y -CONFIG_AGP_AMD=y -CONFIG_AGP_AMD64=y -CONFIG_AGP_INTEL=y -CONFIG_AGP_NVIDIA=y -CONFIG_AGP_SIS=y -CONFIG_AGP_SWORKS=y -CONFIG_AGP_VIA=y -CONFIG_AGP_EFFICEON=y +CONFIG_AGP=m +CONFIG_AGP_ALI=m +CONFIG_AGP_ATI=m +CONFIG_AGP_AMD=m +CONFIG_AGP_AMD64=m +CONFIG_AGP_INTEL=m +CONFIG_AGP_NVIDIA=m +CONFIG_AGP_SIS=m +CONFIG_AGP_SWORKS=m +CONFIG_AGP_VIA=m +CONFIG_AGP_EFFICEON=m CONFIG_DRM=m CONFIG_DRM_TDFX=m # CONFIG_DRM_GAMMA is not set @@ -1895,9 +1897,9 @@ # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set -CONFIG_FB_I810=y +CONFIG_FB_I810=m CONFIG_FB_I810_GTF=y -CONFIG_FB_INTEL=y +CONFIG_FB_INTEL=m # CONFIG_FB_INTEL_DEBUG is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set
AFAIK that has all the required changes - I'll post it in the bugtracker as a feature request
and here is the bug report:
I would not recommend CONFIG_DRM=y. That will screw over all users of DRI/Mesa CVS and snapshots... And remember, the kernel's default DRM is already built AS A MODULE! You can LOAD IT AT BOOT! Compiling it into the kernel instead of as a module is USELESS.
(Sorry for the above rant, but it annoys the hell out of me to have stuff compiled into the kernel unnecessarily when said stuff has compatibility issues in a compiled-in state. Modules are there for a reason!)
I see that you corrected it... Sorry.
Why do the framebuffer drivers have to be set as modules? Please answer immediately with a fully referenced anwer if you would like ati driver "support" in the next official kernel. Or you can post in the big thread here http://bugs.archlinux.org/index.php?do= … ments#tabs
@@ -1895,9 +1897,9 @@ # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set -CONFIG_FB_I810=y +CONFIG_FB_I810=m CONFIG_FB_I810_GTF=y -CONFIG_FB_INTEL=y +CONFIG_FB_INTEL=m # CONFIG_FB_INTEL_DEBUG is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set
Get into menuconfig (cd /usr/src/your-kernel && make menuconfig) and check the following:
Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading
Processor type and features --->
[*] MTRR (Memory Type Range Register) support
Device Drivers --->
Character Devices --->
<M> /dev/agpgart (AGP Support)
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
Graphics support --->
[ ] Support for framebuffer devices
Kernel Hacking --->
[ ] Kernel debugging
And I think in our old wiki qwerty said that it was necessary for the driver to compile correctly.
Powered by Arch Linux
I installed the kernel 'kernel26archck' to get the new ATI drivers working but as usaul with installing non vanilla Arch kernels I had problems with my other non standard module 'ipw2200' not working. So out of interest I installed the new ATI drivers against the 2.6.12-ARH kernel and it just worked.
So it would seem ATI have fixed the issues with needing AGP, etc built as modules in the kernel.
with installing non vanilla Arch kernels I had problems with my other non standard module 'ipw2200' not working. So out of interest I installed the new ATI drivers against the 2.6.12-ARH kernel and it just worked.
Same here. ipw2200 no longer works with the new kernel. I re-installed it, same as with my nvidia driver but no luck. I've been extremely busy, so I haven't had any time at all to troubleshoot it myself yet - maybe I'll have some time in the next few days. Luckily I don't currently need my wireless (or I can boot with the old vanilla kernel if I do)..
Some of the world's greatest feats were
accomplished by people not smart enough
to know they were impossible.
-- Doug Larson
I had a similar problem and described it here. Basically, you have to re-makepkg the ipw2200 module, but before doing that you have to makepkg ieee80211 against the new kernel source too.
So I can get my ipw2200 module to load fine now, but still having no luck with getting my wireless connection working. Used to be fine. If anyone knows the next step after getting the ipw2200 please help. See this thread I started.