| View previous topic :: View next topic |
| Author |
Message |
chronophobic
Apprentice
Joined: 07 Mar 2005
Posts: 237
Location: Sofia, Bulgaria
|
 Posted: Wed Nov 23, 2005 2:37 pm Post subject: unknown symbol pci_pretty_name for savage.ko |
 |
|
Hi, I'm trying desperately to enable hardware acceleration for my ProSavage video card. I was reading http://www.gentoo.org/doc/en/dri-howto.xml and I did the steps exactly as it is written there, even re-did them a couple of times to make sure. All the documentation indicates that my model is indeed supported (be it barely). Upon emerging x11-drm I get the following:
WARNING: //lib/modules/2.6.14-gentoo/x11-drm/via.ko needs unknown symbol pci_pretty_name
WARNING: //lib/modules/2.6.14-gentoo/x11-drm/savage.ko needs unknown symbol pci_pretty_name
Still, when I reboot and startx and run glxinfo, I still get "direct rendering: No".
If agpgart is compiled as a module and I try
I get the pci_pretty_name error in dmesg. I tried googling that error, but the only thing I could find was some obscure sed "workaround" which didn't seem to help at all and some statement that the error is propagated since some 2.6.13 kernel... I've tried recompiling everything which I thought is related to acceleration, from xorg to numerous kernel and x11-drm compiles. I checked and double-checked my xorg.conf, the kernel configs and everything that I could think of... Can anybody help with diagnosing the problem? Just tell me what you need and I can post the related configs/logs.
| Code: | # lspci | grep AGP
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] |
| Code: | # lspci | grep Savage
0000:01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] |
P.S. I apologize for seemingly re-posting, but my other similar post was in "Gamers and Players" and when I wrote about the problem I still wasn't sure what was causing it.
_________________
Confutatis maledictis, flammis acribus addictis! |
|
| Back to top |
|
 |
chronophobic
Apprentice
Joined: 07 Mar 2005
Posts: 237
Location: Sofia, Bulgaria
|
| Posted: Thu Nov 24, 2005 3:42 am Post subject: |
|
|
I have the following software versions:
x11-base/x11-drm-20050502 (the later, ~x86 version in Portage didn't seem to do any better than this one)
xorg-x11-6.8.2-r6 (I updated xorg to ~x86 just for the hell of it...)
gentoo-sources-2.6.14-r2 (no difference b/n gentoo-sources 2.6.14 and -r2)
If anybody has even the slightest idea of where to start with this problem, I can post dmesg, xorg.conf, glxinfo output, the X logs or anything that might be relevant... I don't think I can figure this one out on my own.
_________________
Confutatis maledictis, flammis acribus addictis! |
|
| Back to top |
|
|
chronophobic
Apprentice
Joined: 07 Mar 2005
Posts: 237
Location: Sofia, Bulgaria
|
| Posted: Thu Nov 24, 2005 5:13 am Post subject: |
|
|
Latest newsflash... After another kernel and x11-drm recompile, itseems that savage.ko is finally built properly and can be loaded through modprobe... From dmesg I get:
| Code: | [drm] Initialized drm 1.0.0 20040925
[drm] Initialized savage 2.4.1 20050313 on minor 0:
[drm] Used old pci detect: framebuffer loaded |
After rebooting, however, the final verdict doesn't change...
| Code: | | direct rendering: No |
Ideas? Suggestions (we already established that I can't change my video card, so, OTHER suggestions)?
_________________
Confutatis maledictis, flammis acribus addictis! |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Dec 07, 2005 4:39 pm Post subject: |
|
|
Hey chronophobic. exact same problem here with the *exact* same card (I had to rub my eyes a bit, I've been looking for someone else with this card). I'm still at the 'pretty_print' problem though. At first I build savage.ko that came with the kernel (BTW same kernel here; 2.6.14) and everything loaded and said that it worked fine, but no 3daccel. Then I (finally) got x11-drm to compile but savage won't load.
Maybe we can join forces and figure this out.
If it was a problem that started with 2.6.13 I'll try 2.6.12 and see if that works.
_________________
-Josh |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Dec 07, 2005 8:28 pm Post subject: |
|
|
Tried 2.6.12. No luck. It worked without errors and dmesg looked fine (like yours) but there's no 3d accel. I did notice however, that even with 2.6.14 when savage failed to load, I could still use some savage video options like: Option "Rotate" "CW" and it worked. rotated the screen. I used to have a voodoo 5. At some point everything seemed to work, but no direct rendering. I eventually had to swipe some files from someones nvidia install (glx.h and some others) and then remerge something (can't quite remember what though). Maybe its something along those lines.
_________________
-Josh |
|
| Back to top |
|
|
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Wed Dec 07, 2005 8:40 pm Post subject: |
|
|
Moved from Desktop Environments to Kernel & Hardware.
Kernel problem, so moved here
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
chronophobic
Apprentice
Joined: 07 Mar 2005
Posts: 237
Location: Sofia, Bulgaria
|
| Posted: Wed Dec 07, 2005 10:24 pm Post subject: |
|
|
| josh wrote: | | Tried 2.6.12. No luck. It worked without errors and dmesg looked fine (like yours) but there's no 3d accel. I did notice however, that even with 2.6.14 when savage failed to load, I could still use some savage video options like: Option "Rotate" "CW" and it worked. rotated the screen. I used to have a voodoo 5. At some point everything seemed to work, but no direct rendering. I eventually had to swipe some files from someones nvidia install (glx.h and some others) and then remerge something (can't quite remember what though). Maybe its something along those lines. |
Well, I changed the /usr/src/linux link to point to the new kernel sources after I recompiled a new gentoo kernel then re-emerged x11-drm and the problem disappeared. Everything worked, no errors in the X log, modules load perfectly, x11-drm compiles cleanly and all is right except the direct rendering doesn't work... I guess it's not a kernel problem after all.
And I'm past trying to fix this... The only shot I have right now is to wait for the xorg 7 to be un-hardmasked and see how it goes from there. I think I did everything I could for a week, and got to the "no errors but doesn't work" part so I'm done trying (after installing the hardmasked xorg which... guess what, didn't work for my hardware).
_________________
Confutatis maledictis, flammis acribus addictis! |
|
| Back to top |
|
|
chronophobic
Apprentice
Joined: 07 Mar 2005
Posts: 237
Location: Sofia, Bulgaria
|
| Posted: Wed Dec 07, 2005 10:28 pm Post subject: |
|
|
| josh wrote: |
Maybe we can join forces and figure this out.
|
I'm not sure what else I can do... I'm still stuck with the unsolvable and mostly unheard-of problems related with downgrading xorg (to the non-hardmasked version in portage). If you've got any suggestions or any fixes for the 3d accel I'd gradly try them out tho (even if that's not my biggest problem atm).
_________________
Confutatis maledictis, flammis acribus addictis! |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Thu Dec 08, 2005 3:24 pm Post subject: |
|
|
Understandable. I'm pretty much at the same point. I've tried a few different combinations of kernel and xorg and x11-drm. I think that there is still something that we can do, but as to what it is I have no idea. I can only hope that someone else reads this who has figured it out. I haven't seen anyone else get it working with this exact card. And even "man savage" doesn't list this card as supported by the driver. It seems like the driver works for it except for the 3d accel.
_________________
-Josh |
|
| Back to top |
|
|
avramidg
n00b
Joined: 30 Jun 2004
Posts: 12
|
|
| Back to top |
|
|
MartyParish
n00b
Joined: 08 Oct 2004
Posts: 40
Location: Maryland-US
|
| Posted: Thu Dec 15, 2005 4:21 pm Post subject: |
|
|
I just went through the same problem and finally got it fixed. It is the bug mentioned above.
Here is my thread:
https://forums.gentoo.org/viewtopic-t-412236.html
Here is the page that helped me:
http://archive.netbsd.se/?ml=dri-devel&a=2005-10&m=1431088
Try this: (it worked for me)
1) cd /usr/src/linux
2) make menuconfig
2) Recompile your kernel with these options:
<*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support (or your applicable choice)
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
<*> Savage video cards
3) make && make modules_install
4) cp arch/i386/boot/bzImage /boot/yourkernelname
5) edit /etc/grub/grub.conf to point to new kernel image
** Here is the fix **
6) using the link above, edit these two files
/usr/src/linux-(kernel version)/drivers/char/drm/drmP.h
/usr/src/linux-(kernel version)/drivers/char/drm/savage_drv.c
In drmP.h, remove these lines:
#ifndef pci_pretty_name
#define pci_pretty_name(dev) ""
#endif
In savage_drv.c, replace:
DRM_INFO( "Initialized %s %d.%d.%d %s on minor %d: %s\n",
...with...
DRM_INFO("Initialized %s %d.%d.%d %s on minor %d\n",
and replace:
dev->primary.minor,
pci_pretty_name(dev->pdev)
...with...
dev->primary.minor
That's it. Now reboot into your new kernel and, hopefully, you will now have direct rendering! I did! This was after three days of searching and tweaking!
Good luck with it! |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Thu Dec 15, 2005 7:01 pm Post subject: |
|
|
Thanks man. Still no go thoug. I made the changes. I removed x11-drm first. And I tried compiling everything into the kernel as well as as modules. Everything appears nominal. I beleive that the driver *is* working. Just no acceleration. The only thing that is "off" looking from dmesg is some stuff about mtrr:
| Code: | Linux agpgart interface v0.101 (c) Dave Jones
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
mtrr: base(0xe2000000) is not aligned on a size(0x5000000) boundary
[drm] Initialized savage 2.4.1 20050313 on minor 0
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
it87: Found IT8705F chip at 0x290, revision 2
it87-isa 9191-0290: Detected broken BIOS defaults, disabling PWM interface
mtrr: no MTRR for e0000000,2000000 found
mtrr: no MTRR for e0000000,1000000 found
mtrr: no MTRR for e1000000,800000 found
mtrr: no MTRR for e1800000,400000 found
mtrr: no MTRR for e1c00000,200000 found
mtrr: no MTRR for e1e00000,100000 found
mtrr: no MTRR for e1f00000,40000 found |
the last mtrr messages occured while trying various things with xorg.conf. MTRR is enabled in my kernel. I found some vague posts at dev.gentoo.org about /proc/mtrr . But nothing looked specific to my situation. Any other suggesting Martyr? Should I try to install x11-drm now?
_________________
-Josh |
|
| Back to top |
|
|
MartyParish
n00b
Joined: 08 Oct 2004
Posts: 40
Location: Maryland-US
|
| Posted: Fri Dec 16, 2005 2:32 am Post subject: |
|
|
I found this while doing a MTTR search:
http://www.rage3d.com/board/showpost.php?p=1333981360&postcount=18
| Quote: | SYMPTOM:
dmesg and XFree86.0.log reports MTRR errors and disables direct rendering (accelerated OpenGL)[/u]. 2D acceleration works fine.
TEST:
$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=984064MB: write-back, count=1
The exact size may differ slightly, but always a large value, abour 1TB!
(984064MB is about 984GByte ~ 1TB)
This value is surely wrong, since a tipical machine has about 128Mb..2Gb memory.
CAUSE:
It seems that some BIOSes sets wrong MTRR values. The mainboard above is a real-world example. The wrong MTRR write-back region is larger than the 4Gbyte address space. This conflicts with ANY new MTRRs set by X or other driver/application.
SOLUTION:
We must clear the wrong and conficting MTRR entry on every boot with an rcS.d init script.
Create a text file named fix_mtrr in /etc/init.d and copy this text into it:
#!/bin/sh
# Fix wrong MTRR setting
echo "disable=0" >| /proc/mtrr
echo "base=0x0 size=0x40000000 type=write-back" >| /proc/mtrr
Replace 0x40000000 with the size of your main memory (not video memory)! Help:
0x08000000 = 128Mb
0x10000000 = 256Mb
0x40000000 = 1Gb
0x60000000 = 1.5Gb
0x80000000 = 2Gb
Add execute privileges:
chmod +x /etc/init.d/fix_mtrr
Create a symlink: /etc/rcS.d/S02fix_mtrr
The symlink must point to: ../init.d/fix_mtrr
Reboot your system.
It the kernel options above are set correctly and your ATI driver is configured properly, then 2D and 3D acceleration sould work fine.
TEST:
Your can run:
$ cat /proc/mtrr
Your should get something like:
reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1
reg02: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=1 |
|
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Fri Dec 16, 2005 2:05 pm Post subject: |
|
|
I ran across a similar thing while searching around for mtrr. But my /proc/mtrr doesn't seem to report any incorrect values. Or at least not any that are too big. My system memory is 512 but it reports a bit less. I'm assuming that some of it is taken up by video? (the video is onboard).
| Code: | root@mars:~$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x1e000000 ( 480MB), size= 32MB: uncachable, count=1
reg02: base=0xe8000000 (3712MB), size= 64MB: write-combining, count=1
reg03: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=3
root@mars:~$ free -m
total used free shared buffers cached
Mem: 471 462 9 0 157 99
-/+ buffers/cache: 204 266
Swap: 1953 0 1953 |
So I'm not sure if I should try this if /proc/mtrr is ok. Or should I put '471' into it? Maybe I'll try it out with both 512 and 471 and see what happens.
_________________
-Josh |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Fri Dec 16, 2005 2:37 pm Post subject: |
|
|
Oh duh. yeah. The last 2 entries look slightly out of range.
_________________
-Josh |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Mon Dec 19, 2005 2:33 pm Post subject: |
|
|
Well, I did alot of reading in /usr/src/linux/Documentation/mtrr.txt just to get a feel for it. But no matter what I take out of /proc/mtrr or put into it It always ended up looking like this:
| Code: | reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=3 |
And then I end up with this in dmesg when I insert agpgart,drm, and savage:
| Code: | Linux agpgart interface v0.101 (c) Dave Jones
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
mtrr: base(0xe2000000) is not aligned on a size(0x5000000) boundary
[drm] Initialized savage 2.4.1 20050313 on minor 0 |
Everything else seems to work fine. But no direct rendering. And after doing some more searching around those /proc/mtrr values seem to within reasonable limits.
but I'm wondering if that "ACPI: PCI Interrupt" line is something to look into. I haven't found anything on it though. I think I read somewhere that IRQ 11 is generally for the ethernet. If thats true then that could be the problem.
_________________
-Josh |
|
| Back to top |
|
|
thompson42
n00b
Joined: 03 May 2002
Posts: 20
Location: Connecticut, USA
|
| Posted: Mon Dec 19, 2005 10:42 pm Post subject: |
|
|
Did you get the pci_pretty_name error corrected? grep pretty /var/log/messages to be sure.
If so, does Xorg.0.log confirm that it's working?
# grep "Direct rendering enabled" /var/log/Xorg.0.log
(II) SAVAGE(0): Direct rendering enabled
#
If so, did you try the opengl-update trick in Section 2.5 at http://dri.freedesktop.org/wiki/Building to tell Gentoo to use your new drivers?
I just got direct rendering working on a ProSavage8 KM266/KL266 embedded in a Shuttle motherboard (what a nightmare), and even with it working I still see mtrr errors in dmesg (see below), so I'm wondering if the mtrr thing might not be a red herring.
# dmesg|grep mtrr
mtrr: v2.0 (20020519)
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x2000000
mtrr: base(0xe2000000) is not aligned on a size(0x5000000) boundary
#
Same thing with the PCI interrupts. I see them as well, even with direct rendering working.
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 18 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 21 |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Tue Dec 20, 2005 2:25 pm Post subject: |
|
|
| thompson42 wrote: | | Did you get the pci_pretty_name error corrected? grep pretty /var/log/messages to be sure. |
| Code: | root@mars:~$ grep pretty /var/log/messages
Dec 7 11:20:53 mars savage: Unknown symbol pci_pretty_name
Dec 7 12:13:46 mars savage: Unknown symbol pci_pretty_name
Dec 7 12:20:20 mars savage: Unknown symbol pci_pretty_name
Dec 7 13:01:30 mars savage: Unknown symbol pci_pretty_name
Dec 7 13:02:06 mars savage: Unknown symbol pci_pretty_name
Dec 7 13:06:30 mars savage: Unknown symbol pci_pretty_name
Dec 7 16:03:03 mars savage: Unknown symbol pci_pretty_name
Dec 7 16:03:48 mars savage: Unknown symbol pci_pretty_name
Dec 7 16:05:53 mars savage: Unknown symbol pci_pretty_name
Dec 8 09:30:17 mars savage: Unknown symbol pci_pretty_name
Dec 9 09:12:54 mars savage: Unknown symbol pci_pretty_name
Dec 12 11:51:39 mars savage: Unknown symbol pci_pretty_name |
Note that the latest time is before I corrected the problem a-la above. I can reinsert the modules and reboot and whatnot and everything is peachy now.
| thompson42 wrote: | If so, does Xorg.0.log confirm that it's working?
# grep "Direct rendering enabled" /var/log/Xorg.0.log
(II) SAVAGE(0): Direct rendering enabled
# |
| Code: | josh@mars ~ $ grep render /var/log/Xorg.0.log
josh@mars ~ $ glxinfo |grep render
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect |
This has been the problem: Everything seems to work fine and without complaints but there is no Direct Rendering. I can even use various features of the savage driver like 'Option "Rotate" "CW"' to rotate the screen ClockWise.
I've seen this before but was never sure: Should I be building all of xorg from scratch? Should I install mesa via emerge or should I build it from cvs?
| thompson42 wrote: | I just got direct rendering working on a ProSavage8 KM266/KL266 embedded in a Shuttle motherboard (what a nightmare), and even with it working I still see mtrr errors in dmesg (see below), so I'm wondering if the mtrr thing might not be a red herring.
# dmesg|grep mtrr
mtrr: v2.0 (20020519)
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x2000000
mtrr: base(0xe2000000) is not aligned on a size(0x5000000) boundary
#
Same thing with the PCI interrupts. I see them as well, even with direct rendering working.
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 18 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 21 |
This gives me hope. Sounds like we have the same card and maybe same mobo (is your card integrated into the board?). All I'm missing is the Direct Rendering. Thanks man!
_________________
-Josh |
|
| Back to top |
|
|
thompson42
n00b
Joined: 03 May 2002
Posts: 20
Location: Connecticut, USA
|
| Posted: Wed Dec 21, 2005 5:16 am Post subject: |
|
|
josh wrote:
| Quote: | thompson42 wrote:
I've seen this before but was never sure: Should I be building all of xorg from scratch?
|
Well, I did, to get a 2.0+ version of the Savage driver. Not sure it's truly necessary (see https://forums.gentoo.org/viewtopic-t-409401.html).
josh wrote:
| Quote: | | Should I install mesa via emerge or should I build it from cvs? |
From CVS. That's what I did anyhow.
"Let me 'splain. No, there is too much, let me sum up" [Princess Bride reference]:
What I did:
Followed instructions on http://www.gentoo.org/doc/en/dri-howto.xml; no luck, had to build from CVS.
Followed instructions on http://dri.freedesktop.org/wiki/Building with these caveats:
- I had trouble getting the modules for VIA, AGP, and Savage to load in the correct order, so I built support for AGP and the VIA chipset directly into my kernel instead, works fine. Therefore I'm not using the pre-install commands in my module.conf.
- The pci_pretty_name patch needs be addressed in some fashion. Sounds like you've done that.
- For some reason it took me several tries to figure out that I had to set the environment variable PKG_CONFIG_PATH to get the "make linux-dri-x86" command to work. I'd like to say that the documentation was weak on that point, but it's more likely that I'm just dense.
- opengl-update trick per above.
- Had to remove framebuffer support from my kernel to stop [drm:savage_bci_wait_event_shadow] errors in glxgears.
- Had to add
Option "DmaType" "PCI"
to "Devices" in xorg.conf to stop 'wild mouse syndrome'.
After all this, glxgears increased from 130 fps to just 230 fps. Sigh. Even so, X is noticeably more responsive now, so the box is more fun to use. This is on a Shuttle SK41G I had laying around. The Savage video is a chip on the motherboard. |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Dec 21, 2005 2:13 pm Post subject: |
|
|
| thompson42 wrote: | | "Let me 'splain. No, there is too much, let me sum up" [Princess Bride reference]: |
...You killed my father. Prepare to die.
The only thing I'm worried about from installing X from scratch is it stepping on the toes of gentoo's X and other packages that depend on it. I will try to install mesa and just the drivers first.
This is only my work computer. But it would be nice to take advantage of some of the cool xscreensavers. Also X is somewhat not as responsive as I'd like it to be.
_________________
-Josh |
|
| Back to top |
|
|
thompson42
n00b
Joined: 03 May 2002
Posts: 20
Location: Connecticut, USA
|
| Posted: Thu Dec 22, 2005 2:21 am Post subject: |
|
|
I had understood that the Mesa and Savage driver code from CVS were to be built against the X.org code in CVS. I'd be surprised if they worked with older releases. In fact, it's ...
Inconceivable! |
|
| Back to top |
|
|
thompson42
n00b
Joined: 03 May 2002
Posts: 20
Location: Connecticut, USA
|
| Posted: Mon Dec 26, 2005 4:16 am Post subject: |
|
|
After living with this for a while, it appears that I didn't have this working solidly after all, though glxinfo said "direct rendering: Yes". I kept getting
[drm:savage_bci_wait_event_shadow] *ERROR* failed!
in /var/log/messages, and occasionallly X would go to 95% CPU and stay there. So I grabbed a $60 nVidia card while Christmas shopping, followed the nVidia how-to plus recent posts, and now have 1170 fps. As a bonus I can do 1600x1200 now, whereas the Savage maxed out at 1280x1024.
I'm not saying that the Savage driver doesn't work, I'm just saying I didn't have it working as well as I thought, and I chose not to keep wrestling with it. I'm only posting now so that my earlier posts don't give anyone false hope. |
|
| Back to top |
|
|
Hydraulix
Guru
Joined: 12 Dec 2003
Posts: 447
|
| Posted: Sat Dec 31, 2005 9:24 pm Post subject: |
|
|
I have the same problem. So there isn't a solution to fix this?
_________________
It is the fate of operating systems to become free.
- Neal Stephenson |
|
| Back to top |
|
|
Hydraulix
Guru
Joined: 12 Dec 2003
Posts: 447
|
| Posted: Sun Jan 08, 2006 9:13 pm Post subject: |
|
|
Ok the savage module loads fine now. I am using the ~x86 version of x11-drm. But I still can't enable direct rendering. Here's some info about my system.
dmesg
| Code: |
Linux version 2.6.14-gentoo-r5 (root@toshiba) (gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #3 PREEMPT Mon Dec 26 16:46:55 EST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e8000 - 00000000000e8640 (reserved)
BIOS-e820: 00000000000e8640 - 00000000000e8840 (ACPI NVS)
BIOS-e820: 00000000000e8840 - 00000000000ec030 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000017fe0000 (usable)
BIOS-e820: 0000000017fe0000 - 0000000017ff0000 (ACPI data)
BIOS-e820: 0000000017ff0000 - 0000000018000000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
383MB LOWMEM available.
On node 0 totalpages: 98272
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 94176 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 TOSHIB ) @ 0x000f07d0
ACPI: RSDT (v001 TOSHIB 750 0x00970814 TASM 0x04010000) @ 0x17fe0000
ACPI: FADT (v001 TOSHIB 750 0x00970814 TASM 0x04010000) @ 0x17fe0054
ACPI: DSDT (v001 TOSHIB 2800 0x20001116 MSFT 0x0100000a) @ 0x00000000
Allocating PCI resources starting at 20000000 (gap: 18000000:e7f80000)
Built 1 zonelists
Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768-32@75 splash=silent,fadein,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01302000)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 696.683 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 382716k/393088k available (3529k kernel code, 9716k reserved, 976k data, 212k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1395.04 BogoMIPS (lpj=2790080)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0387f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0387f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0800)
checking if image is initramfs... it is
Freeing initrd memory: 1235k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xff85c, last bus=21
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 4000-403f claimed by PIIX4 ACPI
PCI quirk: region 4060-407f claimed by PIIX4 SMB
PIIX4 devres B PIO at 006c-006f
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [PIHD] (on)
ACPI: Power Resource [PMHD] (on)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: Power Resource [PFAN] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
PCI: setting IRQ 13 as level-triggered
pnp: PnP ACPI: found 11 devices
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: f0000000-f7ffffff
PREFETCH window: 28000000-280fffff
PCI: Bus 2, cardbus bridge: 0000:00:0b.0
IO window: 00001000-000010ff
IO window: 00001400-000014ff
PREFETCH window: 20000000-21ffffff
MEM window: 22000000-23ffffff
PCI: Bus 6, cardbus bridge: 0000:00:0b.1
IO window: 00001800-000018ff
IO window: 00001c00-00001cff
PREFETCH window: 24000000-25ffffff
MEM window: 26000000-27ffffff
PCI: Enabling device 0000:00:0b.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Enabling device 0000:00:0b.1 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0b.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
Machine check exception polling timer started.
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1136694438.948:1): initialized
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
Limiting direct PCI/PCI transfers.
lp: driver loaded but no devices found
Toshiba System Managment Mode driver v1.11 26/9/2001
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 256M @ 0xd0000000
vesafb: unrecognized option mtrr
vesafb: S3 Incorporated., VBE 2.0, Rev 1.1 (OEM: S3 Incorporated. M7 BIOS)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:8751
vesafb: pmi: set display start = c00c87b1, set palette = c00c87fa
vesafb: no monitor limits have been set
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=2048
Console: switching to colour frame buffer device 128x48
fbsplash: console 0 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 0
vesafb: framebuffer at 0xf0000000, mapped to 0xd8900000, using 8192k, total 8192k
fb0: VESA VGA frame buffer device
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb1: VGA16 VGA frame buffer device
ACPI: AC Adapter [ADP1] (off-line)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Fan [FAN] (off)
ACPI: Video Device [VGA] (multi-head: yes rom: yes post: no)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Thermal Zone [THRM] (46 C)
toshiba_acpi: Toshiba Laptop ACPI Extras version 0.18
toshiba_acpi: HCI method: \_SB_.VALD.GHCI
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:08.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
mice: PS/2 mouse device common for all mice
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
e100: eth0: e100_probe: addr 0xeffff000, irq 11, MAC addr 00:10:A4:14:1F:B2
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:05.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfff0-0xfff7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfff8-0xffff, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard on isa0060/serio0
logips2pp: Detected unknown logitech mouse model 0
hda: ST96812A, ATA DISK drive
input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: UJDA540, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 117210240 sectors (60011 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4
hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
libata version 1.12 loaded.
ieee1394: raw1394: /dev/raw1394 device initialized
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:0b.0 [1179:0001]
Yenta: ISA IRQ mask 0x0438, PCI irq 11
Socket status: 30000020
ACPI: PCI Interrupt 0000:00:0b.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:0b.1 [1179:0001]
Yenta: ISA IRQ mask 0x0438, PCI irq 11
Socket status: 30000007
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:05.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:05.2: UHCI Host Controller
uhci_hcd 0000:00:05.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:05.2: irq 11, io base 0x0000ff80
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.10rc1 (Mon Sep 12 08:13:09 2005 UTC).
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
ALSA device list:
#0: Yamaha DS-XG (YMF754) at 0xefdf0000, irq 11
oprofile: using timer interrupt.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
ip_conntrack version 2.3 (3071 buckets, 24568 max) - 216 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002 David S. Miller
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI wakeup devices:
USB VIY0 VIY1 MPC0 MPC1 LID
ACPI: (supports S0 S1 S4 S5)
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 212k freed
Adding 506036k swap on /dev/hda2. Priority:-1 extents:1 across:506036k
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
wlan: 0.8.4.5 (EXPERIMENTAL)
ath_rate_amrr: 0.1
ath_pci: 0.9.4.12 (EXPERIMENTAL)
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: mac 7.8 phy 4.5 radio 5.6
ath0: 802.11 address: 00:11:50:70:4f:e4
ath0: Use hw queue 0 for WME_AC_BE traffic
ath0: Use hw queue 1 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Atheros 5212: mem=0x22000000, irq=11
[drm] Initialized drm 1.0.1 20051102
PCI: Unable to reserve mem region #1:8000000@f0000000 for device 0000:01:00.0
[drm] Initialized savage 2.4.1 20050313 on minor 0:
[drm] Used old pci detect: framebuffer loaded
pcmcia: Detected deprecated PCMCIA ioctl usage.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xa00-0xaff: clean.
ath0 (WE) : Driver using old /proc/net/wireless support, please fix driver !
fbsplash: console 1 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 1
fbsplash: console 2 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 2
fbsplash: console 3 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 3
fbsplash: console 4 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 4
fbsplash: console 5 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 5
fbsplash: console 6 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 6
fbsplash: console 7 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 7
fbsplash: console 8 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 8
fbsplash: console 9 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 9
fbsplash: console 10 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 10
|
xorg.conf
| Code: |
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbModel" "toshiba_s3000"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/input/mouse0"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5 - 57.0
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-90
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "** S3 Savage (generic) [savage]"
Driver "savage"
#VideoRam 16384
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "** S3 Savage (generic) [savage]"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
|
_________________
It is the fate of operating systems to become free.
- Neal Stephenson |
|
| Back to top |
|
|
Hydraulix
Guru
Joined: 12 Dec 2003
Posts: 447
|
| Posted: Sun Jan 08, 2006 9:20 pm Post subject: |
|
|
emerge info
| Code: |
Gentoo Base System version 1.6.13
Portage 2.0.53 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r5 i686)
=================================================================
System uname: 2.6.14-gentoo-r5 i686 Pentium III (Coppermine)
ccache version 2.3 [enabled]
dev-lang/python: 2.3.5-r2, 2.4.2
sys-apps/sandbox: 1.2.12
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1
sys-devel/libtool: 1.5.20
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://prometheus.cs.wmich.edu/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.mirrors.tds.net/gentoo http://distro.ibiblio.org/pub/linux/distributions/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac acpi aim alsa apm arts audiofile avi berkdb bitmap-fonts bmp bonobo bzip2 crypt cups dga directfb dri dvd eds emboss encode esd ethereal exif expat fam ffb ffmpeg flash foomaticdb fortran gdbm gif glut gpm gstreamer gtk gtk2 gtkhtml guile idn imlib ipv6 java jpeg lcms libg++ libwww lm_sensors mad mikmod mmx mng mono motif mp3 mpeg ncurses nls ogg oggvorbis opengl oscar oss pam pcmcia pcre pdflib perl pic png python qt quicktime readline sdl spell sqlite sse ssl tcpd tiff truetype truetype-fonts type1-fonts udev usb vorbis wifi win32codecs xml xml2 xmms xv xvid zlib video_cards_savage userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
|
_________________
It is the fate of operating systems to become free.
- Neal Stephenson |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
