2007年09月06日

今日回来逛逛,猛然发现多了三条评论。其中一条在问RHAS4上怎么配置alsa来支持AD1988B的声卡。其实这个博客,我久已不再更新了。我搬家了,搬到Google的blogspot上去了。地址是http://lophyxp.blogspot.com/。先别忙点,你进不去的(稍后我会说明为什么)。
先说说我搬家的原因,有好几个:
首先,是因为donews自身,经常有访问中断的情况;其次,是因为内容,这个博客上的很多东西,是转载的,而博客最可贵的是原创性。当时初开博客的时候,并不了解这一点,现在了解了,就像有所改变;三就是,所谓博客Blog,就是网络日志,日志者,日记也,自然会有一些心底的密码。所以我希望能有一道保护墙,帮我守护这个秘密。
选择blogspot的原因,是因为它充分满足了第三个条件。当然,还有其他很多博客也满足,比如my.opera.com,只是当初做选择的时候,我只认识blogspot。
一把钥匙开一把锁,开启blogspot的钥匙要你自己去寻找,关键词是firefox、torbutton和Vidalia。剩下的,去问Google吧。

2006年10月10日

好久没有写blog了。今天看到了豆腐生活的blog,又燃起了一丝写点的欲望,于是有了这一片东东。
前些日子,本本坏了。因为我刷了万恶的1.07版的BIOS了,黑屏,不启动。于是返厂一个月。这次返修,顺带解决了半年前出现的上表面外壳轴部出现裂纹的问题。不过由此也损失了逼人200现大洋——主板还好,外壳已经过保了。算来这个本已经买了块一年半了。质保果然是个很重要的东西。
9月29号,本本维修完毕,返回三门峡。下午销售商就打电话到我的手机,叫我领本去。我还在上班,就叫我父亲去了。紧接着十一同学婚礼,马不停蹄的赶到开封。见到了阔别多日的同学们,也见到了朝思暮想的alan——果然我是个邪恶的人,人家已经有男朋友了,我却还是念念不忘。同学见面,相谈甚欢。彼此之间有说不完的亲密。alan大呼:“这是我今年最快乐的两天之一”。
小强带着女朋友去了,居然和楠的妹妹同名同姓,很漂亮的一个女孩。大家的感情事业都发展的很快么。酒席上大家被灌的很惨,开封的服务员很能劝酒,从不粘酒的大家最终解决了一瓶53度的五星茅台。小强有些把持不住了,小猪一样的拱进女朋友的怀里。新娘的鲜花交到了小强的手里,大家便嚷着“让小强三个月后赶紧解决婚礼”——其实是我嚷得很厉害。
婚礼后,做新郎得林请客,大家去K歌。如同众所周知的,房间都满了。不过还有一间最大的,里面的设备稍微有点问题。需要修理一下,大家不愿再跑了,就定下了这间。房间很大,沙发很软。大家逮着没有伴奏的麦克风show着,工作人员修着机器——貌似其实是电脑坏了。大家都沉浸在婚礼的感动中。我昨晚熬夜,缺觉,找了个角落的沙发睡去了。迷迷糊糊间听到alan讲自己的感情故事,我顿时睡意全无,树着耳朵听,alan说她很小的时候喜欢上一个男孩,但终于有缘无分。前些日子见面,却还能做朋友。突然金导大叫我的名字,我迷迷糊糊装刚睡醒。电脑彻底修不好了,已经下午5点了。空房很多,大家就换了一间小包。两间包间的路上,老赵一把拍住我,低声说道:“你真是个HanZi”。
在小包中,我感觉自己的喉咙哽咽着。楠一如既往的想做麦霸,遭抗议,知趣的把机会多留给了别人。alan和金导快乐的唱着,林和新娘一会也来了,show了两首幸福的对唱。强和他的女友躲在里间,继续做小猪——以致于后来几天金导对他很大意见。我终于还是被感染了,咳清沙哑的嗓子。一起加入了幸福的歌声。
人生得意需尽欢,莫使金尊空对月。貌似所谓幸福,就是一群相投的人聚在一起,如此而已。幸福无需奢求太多的。
离别的时刻还是到来了,新郎用车把我们送到车站附近,就被大家赶了回去。大家稍微光了一下传说中的开封夜市,吃了几笼灌汤包作为晚餐,便定下了块10点的火车打道回郑州。没有定到座位,大家有些担心。尤其是我和郭杰,在来的路上深深体味到了站着的滋味。
火车终于进站了,接着传来惊呼声。一部分人开始飞跑起来,其中也包括我们——十一期间的不可思议出现了——空车。车上实在空的可以,只要愿意的话,一个人躺一个位置都绰绰有余。路上,我和alan、老赵用手机上的蓝牙相互传着铃声。楠和金导、郭杰在谈论国庆后的上班安排。就这样,带着一路欢笑到了郑州。
到了郑州站,大家简单话别之后就分开了。我没地方住就去了楠家。又可以和楠睡一张床了^_^(为避免误会,这里解释一下,楠是男的。而我,也没有什么特别的嗜好)。楠show了他单位发的IBM X30,其轻薄(指本)震撼了我。下载买本非12英寸不选,神舟什么的,就无视了吧。
随后的几天,和郭杰逛了一下郑州的电脑卖场。为我的SONY T11配了个1G内存。然后就返程了。
=================我是分隔线=======================
原本是想写本本内存的检测心得,没想到写着写着就变成了记十一的一次同学聚会。看来幸福的事更容易流注于笔端。就这样吧,为了幸福,作文以记之。至于内存和DocMem,就下回再写吧。

2006年08月15日

昨天是第一天,今天是第二天。

2006年08月03日

最初是被空调吹着了,感冒(果然我不是享福的体质)。吃了三天药,转为发烧38.3,于是see a professional doctor,被挂了三天点滴。莫非我和这个地方范克?上一次来这里面试的时候,也是被空调吹着了。

点滴的时候和医生谈起了药价,(我当然知道点滴是由护士扎针,我后两天是在校诊所输的),回忆起小时候第一次点滴,也是发烧,2天输掉了100多块钱。这次是第二次,目前3天的花费是4.5专家号+50.5药费+10输液费(校外,输液管很不错)+10输液费(校内,2次)=75,居然还便宜了。医生说,以前的常用的只有青霉素和链霉素,其他的属于新药,当时很轨。原来药价不是贵了,而是便宜里。不过,长这么大了只输过两次液,从这一点看我的体质还可以么^_^

烧还没有退净,明天看来还要挨一针。看来以后有病还是要see a doctor的。

2006年07月30日

安装了exchange server,M$的东西不需要什么配置,直接就能工作。收发邮件的速度好快!!到底是本域。

使用OutLook Express的时候出现了一个问题。
我安装的域是lophy.com(内部域名,没有注册的。DNS解析有本机处理),当用OE向gmail.com和163.com有效用户发送邮件的时候, 
由于服务器拒绝收件人之一,无法发送邮件。被拒绝的电子邮件地址是“xxxx@gmail.com”。主题’hello’;账户:’administrator’,服务器:’smtp.163.com’,协议:SMTP,服务器响应:’550 5.7.1 Unable to relay for xxxx@gmail.com,端口:25,安全(SSL):否,服务器错误:550,错误号:0×800CCC79

一开始以为是各个邮件服务商对邮件投递增加了认证,而我的域名有没有在Internet上注册。所以投递失败。
但是,以前使用Linux的时候,适用本机的sendmail投递邮件,没有出现拒收的现象啊。

后来搜到了这篇文章。
http://bbs.dreammail.org/archiver/tid-1552.html

文章提到,使用OE就会出现Unable to relay,而是用Outlook(office中的那个)和OWA就不会。我立刻登陆上exchange的web邮箱上尝试了一下,果然邮件成功发送。

so,又是集成windows验证在捣鬼。打开exchange system manage->"servers"->2b1->"protocal"->"smtp"
打开"default smtp virtual server"的属性。
在"access"标签中找到"authentication"按钮,点一下。
在弹出的"Authentication"窗口中把"integrated Windows Authentication"前面的勾去掉。
P.S.顺便把"Anonymouse access"的勾也去掉,是smtp开始身份验证。

OK,万事大吉。邮件很迅速的发送出去了。

哇塞,这要是结合自建的DNS,可以以任何地址给别人发邮件了。这个~~太恐怖了。

很荣幸的通过了全省的选拔考试,最终加入了河南省工商局的信息中心。很无奈从此以后要经常面对M$的东西,而不是Linux了。新开一个分类,记录下有关心得和心情。

今天已经是培训的第7天了。

2006年06月13日

下载

http://sourceforge.net/projects/grub4dos/
下载

安装
打开下载的压缩包
把里面的grldr文件和boot文件夹复制到c:\下
编辑c:\boot.ini文件,添加一行
c:\grldr="Fedora Core 5"

配置
编辑c:\boot\grub\menu.lst文件,具体方法同grub.conf(google此关键词得到更多方法)。
e.g.
我的FC5配置
==========================menu.lst===========================
color black/cyan yellow/cyan
timeout 0
default 0
menuhidden

title Fedora Core 5
kernel (hd0,6)/boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quiet
initrd (hd0,6)/boot/initrd-2.6.15-1.2054_FC5.img
=============================end============================

2006年06月02日

cp -v
显示复制的详细信息

cp -g
显示复制的速率

2006年05月12日

Radeon Manual Page
镭驱动使用手册
From MorLUG
Contents
内容
[hide]

    * 1 RADEON
          o 1.1 NAME
          o 1.2 SYNOPSIS
          o 1.3 DESCRIPTION
          o 1.4 SUPPORTED HARDWARE
          o 1.5 CONFIGURATION DETAILS
          o 1.6 SEE ALSO
          o 1.7 AUTHORS
          o 1.8 Index

[edit]
RADEON

Section: XFree86 (4x)
Updated: Version

#Index


[edit]
NAME

radeon – ATI Radeon video driver
[edit]
SYNOPSIS

Section Device
     Identifier devname
     Driver radeon
     …
EndSection

[edit]
DESCRIPTION

radeon

is an XFree86 driver for the ATI Radeon family of video cards. The driver fully supports 2D hardware acceleration, and provides support for framebuffer depths of 8, 15, 16, and 24. All visual types are supported for depth 8; TrueColor and DirectColor visuals are supported for the other depths. Multi-head configurations are supported. The X-Video extension is supported.
[edit]
SUPPORTED HARDWARE

The radeon

driver supports most Radeon cards. In particular, the following cards are known to work (FIXME: check list):

ATI Radeon 8500 series

    All-In-Wonder Radeon 8500

    All-In-Wonder Radeon 8500DV

    Radeon 8500 128MB

    Radeon 8500 64MB

    Radeon 8500LE


ATI Radeon 7500 series

    All-In-Wonder Radeon 7500

    Radeon 7500


ATI Radeon 7000 series

    Radeon 7000 (also known as the Radeon VE)


ATI Radeon series

    Radeon All-In-Wonder

    Radeon 64MB DDR (VIVO)

    Radeon 64MB SDR

    Radeon 32MB DDR

    Radeon 32MB SDR


ATI Radeon Mobility series

    Radeon Mobility M6

    Radeon Mobility M7


3D hardware acceleration is supported for most (but not all) cards.


If you have a Radeon card not on the above list, don’t assume the card is unsupported; if it is only a minor variation of one of the supported cards, then it may

still work. In either case, if you have a Radeon card not listed above, please report whether it works for you to the XFree86 developers. (FIXME: say how to report.)


Note that the following cards are known not

to work with the radeon

driver. Support for these cards will be added in a future release of XFree86 (FIXME: check both of these assertions): </p>

ATI Radeon 9700 series

    ATI Radeon 9700


ATI Radeon 9000 series

    ATI Radeon 9000 Pro

    ATI Radeon 9000

[edit]
CONFIGURATION DETAILS

Please refer to XF86Config (5x) for general configuration details, as this section documents only the Options

which are specific to the radeon

driver.


For all cards, the driver auto-detects the specific card and the amount of video memory (RAM) present.


Unless otherwise noted, all number values given are in decimal (base 10).


The following Options

apply to all (or mostly all) Radeon cards:

Option Dac6Bit boolean

    If set to true,

    6 bits per color component are used when in 8 bpp mode. This setting emulates VGA mode. The default is false

    (meaning, all 8 bits per color component are used).


        (FIXME: why would one want to set this?)

Option Dac8Bit boolean

    This Option

    is recognized for backward compatibility, but setting it has no effect. Use the Dac6Bit

    Option

    to control whether 6 or 8 bits per color component are used when 8 bpp mode.


Option DDCMode boolean

    If set to false,

    (the default), then XFree86 will not attempt to query the monitor to discover the various video modes it supports. Rather, for each screen resolution (mode) defined in XF86Config (5x), XFree86 will pick the best matching Video Electronics Standards Association (VESA) standard mode timing which the monitor is capable of (according to its HorizSync

    and VertRefresh

    settings in XF86Config(5x). (XFree86 has a built-in list of all VESA standard mode timings.)


        If set to true,

        then instead of relying VESA standard mode timings, XFree86 will attempt to query the monitor using the VESA Display Data Channel Command Interface (DDC/CI) standard. If the display device can be successfully queried, then XFree86 will read the list of mode timings which the monitor claims to support. For each mode defined in XF86Config(5x), XFree86 will pick the best matching mode timing from the list of mode timings the monitor returns.

        Note that not all monitors and not all Radeon cards support the VESA DDC/CI standard. If DDCMode

        is enabled, but the monitor and/or card does not support the VESA DDC/CI standard, then XFree86 will emit a warning message and use the standard VESA mode timings instead.

        The advantage of not using DDCMode

        is that the VESA standard mode timings are supported by virtually all monitors. Additionally, a monitor which does not

        support the VESA standard mode timings will almost certainly not support the VESA DDC/CI standard.


        The advantage of using DDCMode

        is that your particular monitor may support non-standard (i.e., non-VESA) mode timings which are better (e.g., a higher refresh rate) than the VESA standard mode timings. Additionally, for flat panel displays being used in analog mode, DDCMode

        will avoid using unstable modes (some VESA standard modes don’t really work with these panels).

Option NoAccel boolean

    If set to true,

    all hardware acceleration is disabled (e.g., for debugging purposes). The default is false

    (meaning, hardware acceleration is enabled).


Option NoLineAccel boolean

    If set to true,

    hardware line acceleration is disabled (e.g., for debugging purposes). The default is false

    (meaning, hardware line acceleration is enabled).


        Setting this Option

        has no effect if the NoAccel

        Option

        is set to true.

Option SWcursor boolean

    If set to true,

    the software cursor is used; if false,

    the hardware cursor is used. The default is false

    (meaning, the hardware cursor is used).


        (FIXME: what is the cursor? What is the difference between software and hardware? What are the advantages and disadvantages of each?

Option UseFBDev boolean

    If set to true,

    XFree86 will attempt to use use an OS-specific framebuffer interface. See fbdevhw(4x) for further information. The default is false

    (meaning, an OS-specific framebuffer interface will not be used).


        Note that OS-specific framebuffer interfaces are not supported on all operating systems.

Option VideoKey integer

    This Option

    can be used to override the default video key value of 30.


        (FIXME: what does the video key do? Why would one want to override the default value?)


The following Options

are designed for Radeon cards with multiple video ports, such as desktop Radeon cards with both Video Graphics Array (VGA) and Digital Video Interface (DVI) connectors, and integrated laptop Radeon cards which support both a flat panel display and an external VGA connector. For desktop Radeon cards, the Cathode Ray Tube (CRT) port drives the VGA connector, and the DVI port drives the DVI connector (in either analog or digital mode); for integrated laptop Radeon cards, the CRT port drives the external VGA connector, and the DVI port drives the laptop display in digital mode).


If both ports are enabled, the DVI port will be treated as the primary port (the first screen in XF86Config(5x)), and the CRT port will be treated as the secondary port (the second screen in XF86Config(5x)). If only one screen is specified in XF86Config(5x), and the DVI port has a display connected to it, the screen will be used for the DVI port. If only one screen is specified in the XF86Config(5x), and the DVI port does not

have a display connected to it, the screen will be used for the CRT port.


Specifying these Options

for cards without multiple video ports will have no effect. (FIXME: is this true?)
</p>

The Options are:

Option CloneDisplay boolean
    If set to true, then the DVI port will be cloned onto the CRT port. The default is false (meaning, the DVI port will not be cloned onto the CRT port).

    Although two screens can be configured in XF86Config (5x) such that the same content is displayed on both screens, this scenario has problems with the cursor, overlay, and DRI. If the goal is to have only a single screen definition in XF86Config (5x), but have the contents of the screen replicated on both the DVI port and the CRT port, use the CloneDisplay Option. FIXME: the "Here is a hack for cloning first display on the second head" comments in radeon_driver.c (in the RADEONPreInitModes function) seem to imply that if both the DVI and CRT ports are being used, and both have displays connected to them, and only one screen is defined in XF86Config(5x), and CloneDisplay isn’t being used, then the monitor connected to the CRT port will be driven according to the capability of the monitor/panel connected to the DVI port. But the "VE and M6 have both DVI and CRT ports" comments (in the RADEONGetBIOSParameters function) seem to imply that if both the DVI and CRT ports are being used, and both have displays connected to them, and only one screen is defined in XF86Config(5x), then the screen will be used for the DVI port, and the CRT port won’t be used. These sets of comments seem incongruous with each other; what’s the real deal? See also the PanelOff Option.

Option PanelOff boolean
    This Option works in conjunction with the CloneDisplay option. If CloneDisplay is set to true, and PanelOff is also set to true, then the only device XFree86 will use is the CRT port instead of the DVI port, regardless of whether the DVI port has a display connected to it. The default is false (meaning, XFree86 will use both the DVI port and the CRT port, if both are enabled).

    The PanelOff Option is intended for laptop systems (which is why it’s named "PanelOff" instead of something like "DVIOff"). Unlike desktop Radeon cards, on laptops, it isn’t possible to disconnect the flat panel display from the DVI port. Because XFree86 prefers the DVI port over the CRT port if both ports have monitors connected to them (and only a single screen is defined in XF86Config(5x)), without the PanelOff Option, it wouldn’t be possible to use exclusively the external VGA connector on laptops. The PanelOff Option has no effect unless the CloneDisplay Option is set to true. </p>

Option CloneMode string
    When operating in CloneDisplay mode, the cloned display inherits the display modes from the primary display. The CloneMode Option can be used to add a single additional display mode to the display modes inherited by the cloned display from the primary display. The string argument must be a single display mode (e.g., "1280×1024").

    The CloneMode Option has no effect unless the CloneDisplay Option is set to true. See also the CloneHSync and CloneVRefresh Options.

Option CloneHSync string
    When operating in CloneDisplay mode, the CloneHSync Option can be used to specify the horizontal sync range for the monitor attached to the cloned display.

    Note that unlike the HorizSync and VertRefresh Options, which allow great flexibility in how frequency ranges are specified (see the descriptions in XF86Config(5x)), the argument to the CloneHSync Option is a string, in the form of lower-upper, where lower and upper are floating-point numbers. (For example, "30-95.5" would be a valid argument to the CloneHSync Option.) The CloneHSync Option has no effect unless the CloneDisplay Option is set to true. See also the CloneMode and CloneVRefresh Options.

Option CloneVRefresh string
    When operating in CloneDisplay mode, the CloneVRefresh Option can be used to specify the vertical refresh range for the monitor attached to the cloned display.

    Note that unlike the HorizSync and VertRefresh Options, which allow great flexibility in how frequency ranges are specified (see the descriptions in XF86Config(5x)), the argument to the CloneVRefresh Option is a string, in the form of lower-upper, where lower and upper are floating-point numbers. (For example, "48.5-160" would be a valid argument to the CloneVRefresh Option.) The CloneVRefresh Option has no effect unless the CloneDisplay Option is set to true. See also the CloneMode and CloneHSync Options.

The following Options can be used to override default values for Direct Rendering Interface (DRI) support. The default values do not typically need to be overridden. The radeon driver does not currently support DRI on all Radeon cards. If DRI is not supported on a particular card, DRI support will not be enabled, and all DRI-related Options will be silently ignored. The Options are:

Option ForcePCIMode boolean

    This Option

    can be used to force DRI to use the PCI bus, instead of the AGP bus. The default is false

    (meaning, DRI will use the AGP bus).


        Note that DRI currently supports the PCI bus only on the alpha

        architecture. If you set ForcePCIMode

        on any other architecture, DRI support will be disabled.


        (FIXME: I’m probably misunderstanding this option. How would one force an AGP Radeon card to work on the PCI bus? Or a PCI Radeon card (are there any?) to work on the AGP bus? Are there "dual-bus" integrated Radeon cards floating around, which can sit on either the PCI or AGP bus?)

Option CPPIOMode boolean

    This Option

    can be used to force the CP into Programmable I/O (PIO) mode instead of BM mode. The default is false

    (meaning, the CP will use BM mode).


        (FIXME: What is CP? What is BM? What are the advantages and disadvantages of using PIO versus BM?) </p>

Option CPusecTimeout integer

    This Option

    can be used to override the default CPusecTimeout value of 10000. (FIXME: what does this do? Why would one want to override the default value?)


Option AGPMode integer

    This Option

    controls the transmission rate of the AGP bus. The default value (used if the AGPMode

    Option

    isn’t specified) is 1.

    Setting AGPMode

    to 2

    will double the transmission rate; setting AGPMode

    to 4

    will quadruple the transmission rate.


        Higher rates usually offer at least slightly better performance, but the desired rate must be supported by both your system and your particular Radeon card. (Note that some systems can have stability problems with higher rates.)


        Legal values for the AGPMode

        Option

        are 1

        through 4,

        inclusive. (Note that although 3

        is accepted as a legal value, very few systems will support it.)


        (FIXME: on PCs, does XFree86 actually override the AGP mode as set in the system BIOS?)

Option AGPSize integer

    This Option

    sets the AGP aperture size, in units of megabytes. The default value (used if the AGPSize

    Option

    isn’t specified) is 8.


        Legal values for AGPSize

        are 4

        through 256,

        inclusive, in powers of two. (I.e., 4,

        8,

        16,

        32,

        64,

        128,

        and 256.)

        The AGP aperture size is the maximum amount of system RAM that the AGP bus can appropriate (e.g. for storing textures). The more video RAM an AGP card has, the less likely it is that the card will run out of video RAM and have to "steal" system RAM.


        Typically reasonable values for the AGP aperture size are 64

        and 128.

        The larger the AGP aperture size, the larger the Graphics Address Remapping Table (GART) table will be, so setting the AGP aperture size to an arbitrarily high value isn’t a good idea, especially as high values will not improve performance.


        (FIXME: on PCs, does XFree86 actually override the AGP aperture size as set in the system BIOS?)

Option RingSize integer

    This Option

    controls the size of the ring buffer, in units of megabytes. The default value (used if the RingSize

    Option

    isn’t specified) is 1.


        Legal values for RingSize

        are 1

        through AGPSize,

        inclusive.


        (FIXME: what does this do? In PCs, does this correspond to one of the common AGP-related BIOS options? If so, does XFree86 actually override the value set in the system BIOS?) </p>

Option BufferSize integer

    This Option

    controls the size of the vertex/indirect buffers, in units of megabytes. The default value (used if the BufferSize

    Option

    isn’t specified) is 2.


        Legal values for BufferSize

        are 1

        and 2.

        (If a value greater than 2

        is specified, it will be noisily clamped to 2.)

        BufferSize

        must also be less than AGPSize.

        Finally, the sum of RingSize,

        BufferSize,

        and the AGP texture size (1 MB; not customizable) must be less than or equal to AGPSize.


        (FIXME: is this explanation correct? In PCs, does this correspond to one of the common AGP-related BIOS options? If so, does XFree86 actually override the value set in the system BIOS?) </p>

Option EnableDepthMoves boolean

    If set to true,

    then depth moves are enabled. Since depth moves are extremely slow, the default is false

    (meaning, depth moves are disabled).


        (FIXME: what are depth moves? Find out and flush out this explanation more.)

[edit]
SEE ALSO

XFree86</a>(1)

XF86Config(5x)

xf86config(1)

Xserver(1)

X (7x)

fbdevhw(4x)
[edit]
AUTHORS

Authors include: Kevin E. Martin, Rickard E. Faith, Alan Hourihane. Patches have been contributed by many others.

Initial credits to Ani Joshi, for providing source code to his Radeon driver.
[edit]
Index

#NAME
#SYNOPSIS
#DESCRIPTION
#SUPPORTED HARDWARE
#CONFIGURATION DETAILS
#SEE ALSO
#AUTHORS

This document was created by man2html, using the manual pages.
Time: 22:27:36 GMT, November 12, 2002

前一段时间给我的Linux安装上了DRI驱动。但是有两个问题一直没有解决,一个是agp aperture太小,被限制到了8M;一个是agp的速度太低,被限制到了1x。今天在网上查到一个文档
Radeon Manual Page(use keywords:dri agp aperture option)
根据这篇文档,只需要在
Drivers "radeon"
后面添加
Option "AGPMode" "4"
Option "AGPSize" "256"
Option "RingSize" "32"
#Option "BufferSize" "2"
就可以解决。

其中AGPSize就是传说中的AGP Aperture的大小,DRI不会读取BIOS或者VRAM中的aperture的设置。我们必须
用agpsize参数设置它。
RingSize控制Ring Buffer的大小。最好不要超过aperture的1/8,不然会引起OpenGL程序Crash。
BufferSize控制Vertex/Indirect Buffer的大小。最大只能设置为2M,(最小只能设为1),超过了DRI会忽略它。
基本上ring buffer + vertex/indirect buffer + texture buffer = agp aperture
这一点可以通过查阅X的启动记录来确定(/var/log/Xorg.0.log)
根据常识(熟悉BIOS的人都知道的),AGP Aperture不要超过主存总容量的1/2。

心情太激动了,要马上去试一试。