X-fi platinum makes my video card biff
My video card?doesn't want to work after installing the X-fi.When I go to device manager it says that the x-fi works fine,the video card doesn't have enough resources to work, andthe media controller isn't working. HELP?gig DDR2 RAMPentium 4 3.4GhzNvidia 6600 28M RAMWindows XP Pro edition?
NevaMynde wrote:
I have just purchased a new X-Fi Platinum. As soon as I install it, my video card ( XFX nVidia GeForce 6800 GS AGP) reverts to 800x600 4bit (YES! 4bit) colour.
In Device manager it comes up with "Error 2" - not enough free resources...
I have no other PCI cards installed. Also removed all USB & IEEE 394 devices.
I am using Abit AI7 P4 Mainboard - latest BIOS flash (ai79.bin) didnt make a difference.
It is a fresh install [formatted C:]of XP(SP2). On-board sound disabled. Not overclocked. Not Raided.
Also latest Forceware drivers used (84.2). Tried X-Fi Web Update2 drivers as well to no avail. Previous audio was an Audigy (no issues.
As soon as I remove the X-fi, video card returns to normal on next boot. I have read the forums and have seen alot of people having issues with their X-Fi. I have always bought Creative audio cards and never had any issues before. Please help! I dont want to be ANOTHER disgruntled cutomer with a $300(AUD) technological lemon!
Maybe changes on AAS setting can help - http://forums.creative.com/creativelabs/search?board_id=soundblaster&submitted=true&q=aper ture
jutapa
Similar Messages
-
How can i make my video card and sounds work on Windows 7 on my Macbook Pro 2.2? Help please...
How can i make my video card and sounds work on Windows 7 on my Macbook Pro 2.2? Help please...
i lost my Mac OSX dvd...
-
Windows 7 - Pci-to-Pci Bridge (Error: Code 10) - PCI Video Card
Before I state my issues I will list what I'm running and what I'm trying to accomplish.
I'm running Windows 7 Enterprise 64-bit edition, not the Beta or RC. I have 3 video cards in my possession (listed below).
- (PCIe) Evga GTX260
- (PCI) Evga 9400GT
- (PCI) Evga Fx5500
Out of those 3 cards I only use the GTX260 and the 9400GT. I had to 'retire' the Fx5500 because the latest WHQL (certified) drivers only provide support as far down as the "6 series" Nvidia cards. Unfortunately the Fx5500 is a "5 series" and falls below that line. I have already tried to use the GTX260 and Fx5500 in previous versions of Windows (XP and Vista), but there is no way to download and install two separate drivers for two of the same make of video card - you'll get nothing but errors. There is the option of going to a place like guru3d.com and downloading a custom supported driver that covers both the GTX260 and Fx5500, but the drivers are not certified and lack support. Therefore, I purchased and now use the 9400GT which is covered under the drivers for the GTX260 and eliminates the need for messing around with custom drivers. Also, the 9400GT has a better graphics processor and more memory than the Fx5500, so it was time to upgrade anyway.
Now that you have some background info here is my issue Whenever I install the 9400GT I get a second 'pci-to-pci bridge' entry (the other entry has no errors) that shows up under 'System Devices' in the Device Manager. The second pci-to-pci bridge entry has a yellow triangle with an exclamation mark on it that refers to a problem. When you check the properties of this device it more or less says that Windows has detected a problem (Error Code 10). The GTX260 still works and even shows up under the 'Display Adapters' as a GTX260, but no entry for the 9400GT exists. I have tried the 9400GT in both PCI slots and each time it does the same thing. If I pull out the GTX260 and ONLY run the 9400GT, I still get the pci-to-pci bridge issue, BUT I do get a picture and can boot into Windows 7 without a hitch. When I do this there is still nothing listed under the 'Display Adapters' as a 9400GT or even a VGA compatible device.
After messing around with this for 10 hours (yes, I said 10 hours) I decided to dig out my retired PCI video card (the Fx5500). When I installed this card I had no 2nd pci-to-pci bridge entry appear under 'System Devices', and the one that was listed had no yellow triangle or error codes. I then checked under 'Display Adapters' and Windows 7 had recognized it as a VGA compatible device and was asking for drivers.
I have now concluded that there is definitely no issue with the motherboard or any of my hardware (including video cards). At first EVGA Support and I had suspected that the motherboard may be bad because of all of the pre-diagnostic steps I had taken during my 10 hour ordeal. I'm not going to list everything I did because it would literally take 3 hours to type it all in. Just believe me when I say that I have tried most things including but not limited to the latest bios updates (flashed 4 times and completely reset to ensure accuracy), custom IRQ management, entire OS re-installation X2, multiple/latest chipset drivers installed, multiple/latest video drivers installed, memtest testing, complete hardware teardown and re-build (adding one device at a time), and MUCH more. The only thing I did not try was installing a different OS other than Windows 7 64-bit to see if I could replicate the issue. This is a waste of time though because lets say that I install Windows XP Pro and the 9400GT doesn't have this issue... Well, that's great, but who gives a damn about XP Pro when I have been using it for the last 9 years and when I have a full version of Windows 7 that I want to use? I'm certainly not going to run XP Pro over Windows 7 just to use this PCI video card. Second, if I install XP Pro and it still gives me the same pci-to-pci bridge error then again, I've only wasted more time because if its not going to work in either OS then Im sure as hell not going to leave XP Pro installed when I can use Windows 7.
Thanks,
piyushMaybe stupid question now but has your posting anything to do with Toshiba and Toshiba notebooks?
-
Receiving New iMac Free - Video Card Question
Much to my relief, Apple is replacing my 2008 24" iMac after I have brought it in to them 3 times for the same issue in a month (failure to startup, they have replaced two video cards, one MLB, and the display but the problem repeats itself within 1-2 weeks). They are replacing it with a newer model that has a 27" display, twice the ram (4 GB) and twice the HD space (1 TB). My question is about the video card in the new iMac, it is a ATI Radeon HD 4670 with 256 MB, and the card in my old iMac was a NVIDIA 8800 GS with 512 MB. My primary application for my iMac is gaming, which I believe makes the video card the most important component. Does anyone know the difference between 256 and 512 or anything about this new card? Should I ask them if I can pay to upgrade to the Radeon HD 4850 512 MB before I go in to pick up my new iMac?
crazy00eyes wrote:
Much to my relief, Apple is replacing my 2008 24" iMac after I have brought it in to them 3 times for the same issue in a month (failure to startup, they have replaced two video cards, one MLB, and the display but the problem repeats itself within 1-2 weeks). They are replacing it with a newer model that has a 27" display, twice the ram (4 GB) and twice the HD space (1 TB). My question is about the video card in the new iMac, it is a ATI Radeon HD 4670 with 256 MB, and the card in my old iMac was a NVIDIA 8800 GS with 512 MB. My primary application for my iMac is gaming, which I believe makes the video card the most important component. Does anyone know the difference between 256 and 512 or anything about this new card? Should I ask them if I can pay to upgrade to the Radeon HD 4850 512 MB before I go in to pick up my new iMac?
Hi Crazy,
I had the exact same problem... my 18month old 24" iMac (with 512MB Video card) went belly up.
I pointed out that what they wanted to offer me had only the 256Mb Card ? ....and he said; "oops I didn't notice that"... so we will send your new 27" iMac - with a 512MB (ATI 4850) at no charge,
So... buddy you just need to tell them - and they will configure your replacement 27" to equal or better the minimum specification of your faulty unit. -
What Video Cards ACTUALLY WORK with my G5
I have a Dual core 2.3GHz G5 with a GeForce 6600. I really want to upgrade my video card, but as usual, I can't figure out if any card will actual work. I'm really interested in the 7800 GT and GTX. Nvidia's site says that the entire 7 series of cards work in OS X, but none of the companies that actually make the cards have any mention of Mac support. I'm so frustrated because Nvidia doesn't make any cards, the companies that make them make 4 different versions of each card and don't sell them and the places that do sell them know nothing about them. So can someone PLEASE, post links to the actual cards that work in my machine. thank you.
Nvidia doesn't make the Video Cards.
They make the chips (GPU) that run on the Video Card itself. Most of the Nvidia chipsets are supported by Mac OS X.
The problem is that all Video Cards carry a firmware PROM chip that contains the early-boot code for the card as well as the card's internal operating parameters.
There is a PC version of the firmware, commonly called the VGA BIOS, and there is a Mac version of the firmware, which is designed for OpenFirmware.
The two are completly seperate from each other. A PC card will not operate in a Macintosh, nor will a Macintosh card operate in a PC.
That's your problem- is that the Nvidia chipsets support Mac OS X, but the firmware on the card (which, is up to the manufacture which one they include) may or may not support the Macintosh platform.
Saying that, the only two cards available for the G5 is the 7800 GT and the Quadro 4500. Both cards contain the Apple firmware required for the card to work in a G5.
There are no other manufactures who offer Mac G5 compatible solutions, probably due to Apple's unwillingness to release the said Mac firmware for third party video cards. Thus, it's really one or the other, and Welovemacs.com seems to be the only retailer offering ether of the cards for seperate purchase.
-S'Captain -
[VIA] Do I need a video card to make this MB run?
My MSI KM4M-V arrived today. It replaced a Shuttle motherboard I just could not make it show anything on the monitor. I returned it as defective. Well, I just installed my MSI and darn it, the same thing is happening. Nothing shows on the monitor.
My son said I need a video card. It has a monitor connection sticking out the back, so I assumed it came equipped to run a monitor.
Now, I'm not a pro at these things, but I followed the installation book to a tee. And since is the second motherboard that has performed this way, I think it must me something I am doing wrong. But what can it be?
I am assuming I can hook it right in and it wil run my old hard drive like they came together. Am I wrong? Must I format the drive and run the software? I can't load rhe software fi I can't see the monitor.
When pluged in and unconnected my monitor flashes a blue and white "please check video cable connection" message. When I connect it to the MSI motherboard the flash stops. So something is working.
Any suggestions and advice will be greatly appreciated. My computer is devoted to genealogy and it's ben down for 2 months and I am very anxious to get it tuning again.
Sandy
AIM - SANDY 8771Save this reading till the power and beeps from Wonkanoby have been resolved. I think "used" is a relative thing...
No, if you plugged everything in while power was off it is alright.
Now comes the processor part, which one it was. This motherboard can hold most, but XP3000 and XP3200.
It is getting a bit late here, so I want to prepare you for some other things that might come up:
The seating of the processor is very important. This is best done while the motherboard is out of the case.
Between the motherboard and the case there are stand-offs. Too many is a bigger problem than too few.
You might even have to test-run the motherboard out of the case, to eliminate the risk of shorts.
What memory do you have? Stick of RAM, that is. Model and speed, please.
Off topic: I didn't know either, Wonkanoby, you used a 500W in a Shuttle - half should suffice. A new one for you, maybe: Too big a PSU. But it is one overstated, again: http://www.amamax.com/pomaxceb5020.html "+3.3V-24A, +5V-36A, +12V-16A" -
What video card do I need to make Photoshop CC 2014 to use 3D? I have NVIDIA GeForce GTX 780M 4096 MB graphics.
A couple of questions:
1. Have you tried resetting your preferences?
2. If you go to Preferences > Performance - is "Use Graphics Processor" enabled? If not, can you select it?
Your system should be fine to support 3D in PS CC 2014. Once I have more information from you we can move onto next steps if necessary.
Thanks,
Adam -
MSI P6N SLI Platinum - Two Video Cards Non SLI
I have a P6N SLI Platinum that I am trying to get two video cards working at the same time, but not in an SLI configuration. I'm wanting to use them for 3 monitors at the same time. The cards are both Nvidia 8800GS, but one is by EVGA and one is XFX. Both cards work individually, but when trying to use both of them at the same time, Windows will not recognize them. I am currently running Windows XP Pro. Is this type of configuration possible with this motherboard? Any help would be appreciated.
Thanksi think you will be told by msi to be able to use two card on one mobo you have to have sli enabled.
-
Having Dual video cards or SLI in premiere CC will it make a difference?
I have the Geforce 980x
IF i have 2 in SLI
will it make any difference for my render timeSee Tweakers Page - Exporting Style and Tweakers Page - What video card to use?
Do you have at least:
6-core or 8-core i7, overclocked to 4.2+ GHz or dual Xeon 10-core E5 v3 or better, and
64 or 128 GB RAM, and
Sustained transfer rates on all volumes of more than 400 MB/s, and
32+ unused PCIe-3.0 lanes available.
If the answer is YES to all 4 points above, then a dual GTX 980 may - just may - be beneficial if:
you render for previews all the time using accelerated effects, or
you export from source to destination with rescaling (i.e. 4K to HD or HD to SD), frame rate changes, frame blending almost always.
If your workflow does not include these two points almost all the time, having two video cards is a waste of money.
Using SLI is irrelevant for PR, since the video cards are treated as separate components. If anything, using the SLI bridge can only complicate matters and reduce performance, because of the inherent overhead of the SLI design. -
MSI R48R4870-T2D1G-OC video card and the MSI K9A2 Platinum
I recently bought the new video card for my system the R4870-T2D1G-OC.
MSI stated that the power cord for the video is not a required, and the MSI board has its own connection for power to the video.
When I tried installing the new card all I get is a series of beeps, as if there is not video card installed. BEfore I send it back and replace it with another I would like to verify that it does not require the power connector and that perhaps I need to do something special before I repalce the card.
I have always used the MSI mainboards and never had a problem till now.
DanielQuote
The system boots and I see the dos screen, then it goes black
You mean you see the BIOS logo / POST screen, and then nothing? So the card is working then, no beeps?
Quote
I have replaced the power supply and loaded the drivers supplied by MSI. Now I have no video.
Can you elaborate, as I don't know how you can install drivers if you're not getting any display? ???
Quote
What can be done to get the APPROPRIATE drivers for windos Vista, or do I need to install the 3rd party software to get the ATI cards to work.
Download the Full Catalyst Suite for your appropiate OS version from here:
http://game.amd.com/us-en/drivers_catalyst.aspx -
K8N neo4 platinum /sli & msi 6800gt video card problem.... urgent help!!!!
I simply can't get the video card to work in the firts PCI-E port, however if the card is in the second port it works fine without the D-bracket locking the PC. Does someone know why this happened?, is the motherboard damaged?, or is there a solution to this problem?
Note: D-bracket is indicating a Memory detection test problem, but as
I said if the Video card is in the second PCI-e port the PC works fine
Plase help does someone knows why this is happening?Could you add the list of your components to your signature (e.g. power suppy, memory, etc).
I am assuming that the SLI connector card is firmly in place and set for non-SLI operation and
that the video card only works when inserted into the slot that what would normally be used
by a second SLI video card. Is this correct?
Have you tried resetting your BIOS? -
How to SET or Configure BIOS to use XFX6200 TC video card for MSI K8N NEO4 Plat.
Hello Friends,
Can any body help me to the following problem?
I am having XFX 6200 TC Geforce / nvidia Grafix card for my MSI K8N NEO4 Platinum Ultra board.
The BIOS states PCIE clock speed as 100 Mhz as default. The setting can be changed upto 145Mhz.
My Video card can be configured upto 350 Mhz. How to do this and which is the right way to use the display card with optimum setting?
Thanks for all those who reply to this.the coolbits link http://downloads.guru3d.com/download.php?det=815
to manually set the clocks on the graphic card, after installing coolbits, just follow the instruction on that page:
Quote
Unpack the achive (self extracting) and then in the setup directory simply click on the .reg file. To get to these options simply right-click on your desktop and go to 'NVIDIA Analog Display' (Win XP/2003). For Win 2000 and lower you may need to get to the Nvidia Control Panel the old way. Right click desktop > Properties > Settings > Advanced > GeForce xxxx
for overclocking just take a look at the overclocking sections of the forum. make sure to read the stickies before you do anything. -
MSI NEW P.E. Series Video Card - GTX670 Power Edition 2GD5/OC with Twin Frozr 4
Glad to be back in the forum and I was been busy for awhile. By this time lots of PC hardware already came out especially from Nvidia. Just like today my share would be MSI's N670GTX PE 2GD5/OC video card.
First of all lets talk about the GTX670 GPU chip. This GPU is the younger sibling of GTX680 which uses the same 28nm GK104 chip but with one disabled shader cluster/core.The reference or standard GPU clock is 915Mhz with a turbo boost of 980 and as for the memory is concerned, it has a 256bit memory bus connected to a 2GB GDDR5 memory with speed of 6008Mhz. Just like with any Kepler based architecture, the card would also have all the goodies like "Adaptive V-Sync", "AA TXAA (Temporal Super Sampling)", supports "DX11.1" and improved 3D Vision Surround.
Moving on, let's check out now what MSI did with their GTX670 SKU based video card. The card is under a new Series named "Power Edition" (series comparison table below) and it comes factory overclocked from GPU clock of 915MHz to 1020MHz and Turbo boost of 980Mhz to 1080Mhz. It also comes with the 4th version of Twin Frozr Thermal Cooling design with a theme color of Black and Blue which matches the color of MSI's midrange to high-end motherboards as well. The dual 8cm PWM fan based cooler are equipped with Propeller Fan Blades which draws air better and now has the so called "Dust Removal Technology", basically as you startup your PC the fan will rotate counter clockwise for 30 seconds clearing the dust from the cooling heatsink. Adding a finishing touch, MSI equipped the video card with their Military Class III components ensuring the best performance, efficiency, higher overclocks and durability.
Additional Box Shots of the N670GTX PE OC
MSI Series Comparison Table
New Power Edition Series which is a notch higher than the basic Twin Frozr Series.
Below are some other basic specs of the card which not been mentioned above.
•CUDA Cores: 1344 Units
•Output: DisplayPort / HDMI / DL-DVI-I / DL-DVI-D
•Total Draw Power: 200W
•Card Dimension: 267x117x38mm
•DirectX: DX 11.1
•OpenGL: 4.2
•PCI Express: 3.0
•SLI: 3-Way Capable
•3D Vision Surround: 3 Output per Single Card
•Pure Video HD: Y
•HDCP: Y
•Minimum Power Requirement: 550W with 38A for the +12V Rail
Actual shot of the Rear Ports
The card is powered up by additional 2x 6Pin power connectors.
Five 8mm thick heatpipes design
In the future, there might be a GTX670 4GB GDDR5 version as you can see the empty spaces between the GPU memory chips
Bundled Accessories included in the package
•1x DVI to VGA Dongle
•2x 4 Pins Molex to 6 Pins VGA Power
•DVD Driver/Utility Disc
•Manual and Quick Guide
Test Sytem and Configuration
Processor: Intel i7 3770K @ Stock Speed / 4.8GHz / 4.849GHz
Cooler: Thermaltake Advanced Frio
Memory: 2x4GB Kingston HyperX DDR3 2133Mhz
SSD: Kingston HyperX 3K SSD 90GB
Motherboard: Z77A-GD80
Videocard: N670GTX Power Edition 2GB OC
PSU: Antec TPQ 1200
Softwares: Windows 7 64bit Ultimate, MSI Afterburner 2.2.2, Nvidia Forceware 304.48, GPU-Z 0.6.2, CPU-Z 1.60.1.x64, Futurmark Benchmark Softwares, HwBot Heaven DX11
Okey let the benchies begin 1st set of benchies @ stock settings
3dMark06 - 28799
Vantage - P31817
3dMark11 - P9530
Heaven DX11 - 1956.985
2nd Set - Processor @ 4.8GHz while the video card is still running at stock speed
3dMark06 - 35852 From the previous score of 28K it jumped to 35K. This is becuase 3dMark06, relies heavily on the clock frequency of the processor.
Vantage - P34377
3dMark11 - P9861
Heaven DX11 - 1986.539
3rd Set - i7 3770K @ 4.849GHz and the video card GPU clock @ 1070mhz with turbo boost at 1148Mhz and memory clock speed @ 1717MHz (6868Mhz effective rate)
3dmark06 - 36402
Vantage - P36194
3dMark11 - P10263
Heaven DX11 - 2140.223
That's it. I will share another hardware soon@Bernhard
The card is not with me already :( it was just left for few days. Don't worry next time I will make some tests using Virtu MVP.
@Update
Afterburner 2.2.3 is already out and with this new version. You can overclock the PE better -
Genius needs to help! problems with my video card and system
Hey guys! I'm going to post my specs first so that you get a good idea of what I'm running on:
MSI Neo2 LS 865PE.....MAT=Slow
Pentium4 2.4C.....FSB=233=2.8C hyperthreading enabled ~>1.55V
Corsair TwinX 1gig PC3700.....memory on "AUTO" in BIOS with timings at 3,4,4,8 ~> 2.7V
Radeon 9700NP.....stock speeds ~>1.7V
AlienX case with 2 fan400 watt power supply and 6 case fans
Zalman Alum/Copper heatsink fan
1:I've had this motherboard for a few months now. I upgraded my video card from a nVidia Ti4200(128meg) to a Radeon 9800 a month ago, but I couldn't get it working at 8X AGP, no matter what voltages I threw at it. I returned it for a Radeon 9700NP hoping that it would work, but it still won't.
I'm using BIOS 1.9 and since there is no option to select your AGP speed, I could only try using ATI's drivers. Once booted into Windows, there is a slider you can move to select you AGP speed. On my machine It says that It has performed some tests and has concluded that AGP 4x is the best for my system....but my system supports AGP 8X!
I've moved the slider over to 8x (which requires a reboot) at least 5 times with each card but the slider refuses to move past 4xAGP after the reboot.
2: My second problem: I had an old stick of KingMax PC3200 and decided to buy 3 more sticks. Unfortunatly, the 3 I bought did not match the one I had, so I only put 2 of the new sticks I bought into my system. Immediatly, My system would crash, lock up, files were corrupt, and I got PLENTY of blue screens of death with a long message containing: 0x0000007 with all these other numbers and "0"s. I did a search online and found out I had a hardware incompatibility problem. I never got this with my old stick of ram.
I returned the 3 sticks of Ram and replaced them with the Corsair. Put my new Radeon 9700 in, formatted my hard drive....and within 24 hours, my system locked up 3 times, rebooted itself 5 times, and gave me the same BSOD as mentioned above with the same long message.
I didn't change anything except for the memory and the video card. I've been wanting to overclock, (thats why i bought the faster memory ) but I'm not sure what to do at this point.
I have my FSB at 233 but I'm scared to go any higher because of previous system instability at stock speeds. My RAM was running on 400 and MAT=Turbo with the most relaxed timings at 3,4,4,8.
I've given myself hours of sleepless nights formatting when my system wouldnt boot into windows; overclocking....etc. I NEED HELP. PLEASE. PLEASE. Anything could work at this point.
I'm trying to get more info on how to run my system at a 5:4 ratio, also.
If anyone has problems like me or knows what could be the problem with my system, please reply to this post, it would help me a lot. I've been trying to fix these problems for a few months now so anything is greatly appreciated.Thanks a lot to you guys that responded. I brought my computer home this past holiday and I want to let you know where I stand as of now. I guess this thread is like my blog for my computer. I want to clear some things before my first post makes everyone confused.
1- I have only 2 sticks of memory in my system: the Corsair PC3700 TwinX 512x2
I returned the 3 KingMax I bought, and still keep my old stick just in case.
2- I am using the 400 watt power supply that came with the case. I read some reviews of the case and I know the reviewer did not have problems with the power supply. In my BIOS, there are some voltages it is weak on. Lets say: it it should be 5.00+, my power supply will be feeding it 4.96v or something like that, but I dont know, or think, that is a major problem...
3- My computer will refuse to boot if memory speeds are set at anything below 400. SO....if I want to use a 5:4 ratio and have to set my memory speeds to "333" in BIOS, my system refuses to boot.
4- This morning, I did manage to overclock my FSB to 250. Specs are as follow:
Memory Timing @3,4,4,8,4.....speed set at "AUTO".....MAT at "SLOW"
MY 2.4C's FSB was raised to 250 = 3.0gig
AGP/PCI frequency: 67.xx/3x.xx (cant go any lower)
CPU voltage: 1.5500
Memory voltage: 2.75
Video Card voltage: 1.7
Everything was fine for the whole day until I heard something click in my computer around midnight, and then seconds later, my computer froze and made a continuous beeeeeeeeeeeeeeeeeep. (you can imagine)
This "click" and system crash has been plaguing me for months now. I dont know whay it happens. I was just using AIM when I heard the click and my heart stopped.
My memory speeds have been set to "AUTO" even at the FSB of 250. But I don't know if this still means my system is at a 1:1 ratio. I know the BIOS then adjusts the memory to work at 500 if my FSB is 250...so I assume it is? I love 3gig, but somehow I feel that 2.8 is faster, since the FSB=233 running parallel to my memory, also at 233
A FSB of 250 is good enough for me, that's what I've been waiting 6 months for. If anyone knows how to set other ratios to achieve a FSB of 250+, please let me know, but as I said, my memory won't boot if its set at "333" -
Fglrx not finding my video card
holla balloj!
vid card: ATI radeon X850XT on a x86_64
Uncommonly enough i have some ati drivers that doesn't wanna do what i tell em to do. And it seem to be the fglrx module that cant find my card and then the fglrx(0) shows up and it seem like my dear X buddy is loading the vesa driver and thus i can't watch the one and only season of Firefly in a druuling 720p quality.
Please help me see Firefly in 720p
(and switch desktops without 2 secs delays etc etc (including to play a number of pc games))
Xorg.conf
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "AllowEmptyInput" "0"
EndSection
Section "Files"
EndSection
Section "Module"
Load "freetype"
# Load "xtt"
Load "extmod"
Load "glx"
Load "dri"
Load "dbe"
Load "record"
Load "xtrap"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/input/mice"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "dvorak"
EndSection
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 90.0
VertRefresh 50.0 - 70.0
EndSection
Section "Device"
Identifier "Card0"
Driver "fglrx"
Card "** ATI Radeon (generic) [radeon]"
BusID "PCI:5:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1280x1024" "1024x768"
EndSubSection
EndSection
And the log!
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH x86_64
Current Operating System: Linux juppaCom 2.6.27-ARCH #1 SMP PREEMPT Sun Dec 21 09:13:30 UTC 2008 x86_64
Build Date: 17 December 2008 10:46:49PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 28 02:42:13 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(**) Option "AllowEmptyInput" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x7b54e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@5:0:0) ATI Technologies Inc R480 [Radeon X850XT (PCIE)] (Primary) rev 0, Mem @ 0xd0000000/268435456, 0xfd7f0000/65536, I/O @ 0x00006c00/256, BIOS @ 0x????????/131072
(--) PCI: (0@5:0:1) ATI Technologies Inc R480 [Radeon X850XT (PCIE)] (Secondary) rev 0, Mem @ 0xfd7e0000/65536
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(==) AIGLX disabled
(WW) fglrx: Force AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "record"
(WW) Warning, couldn't open module record
(II) UnloadModule: "record"
(EE) Failed to load module "record" (module does not exist, 0)
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DEC-XTRAP
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.56.4
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) Primary Device is: PCI 05@00:00:0
(WW) Falling back to old probe method for fglrx
(II) ATI Proprietary Linux Driver Version Identifier:8.56.4
(II) ATI Proprietary Linux Driver Release Identifier: 8.561
(II) ATI Proprietary Linux Driver Build Date: Dec 1 2008 14:56:52
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 4.1
(WW) fglrx: No matching Device section for instance (BusID PCI:0@5:0:1) found
(--) Chipset Supported AMD Graphics Processor (0x5D52) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@5:0:1) found
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) fglrx(0): pEnt->device->identifier=0x181c200
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[20] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[22] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[24] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[25] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[26] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[27] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[28] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): PCI bus 5 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(II) fglrx(0): Loading PCS database from /etc/ati/amdpcsdb
(II) fglrx(0): 10BitPixelFormat disabled by default
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.56.4
ABI class: X.Org Server Extension, version 1.1
(--) fglrx(0): Chipset: "RADEON X850 XT" (Chipset = 0x5d52)
(--) fglrx(0): (PciSubVendor = 0x1002, PciSubDevice = 0x0b12)
(--) fglrx(0): board vendor info: original ATI graphics adapter
(--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
(--) fglrx(0): MMIO registers at 0xfd7f0000
(--) fglrx(0): I/O port at 0x00006c00
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.1.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 9.7
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2003, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: R480
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID PCI:5:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports PCI:5:0:0
(II) fglrx(0): Using adapter: 5:0.0.
(II) fglrx(0): [FB] MC range(MCFBBase = 0xc0000000, MCFBSize = 0x10000000)
(--) fglrx(0): Video RAM: 262144 kByte, Type: DDR3
(II) fglrx(0): PCIE card detected
(II) fglrx(0): board/chipset is supported by this driver (original ATI board)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000001, disabled=0x00000000
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: PHL Model: e01e Serial#: 717343
(II) fglrx(0): Year: 2005 Week: 3
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) fglrx(0): Sync: Separate
(II) fglrx(0): Max Image Size [cm]: horiz.: 36 vert.: 27
(II) fglrx(0): Gamma: 2.96
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) fglrx(0): Default color space is primary color space
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): GTF timings supported
(II) fglrx(0): redX: 0.631 redY: 0.329 greenX: 0.276 greenY: 0.600
(II) fglrx(0): blueX: 0.143 blueY: 0.057 whiteX: 0.283 whiteY: 0.297
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 720x400@88Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) fglrx(0): #1: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) fglrx(0): #2: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
(II) fglrx(0): #3: hsize: 1920 vsize 1440 refresh: 60 vid: 16593
(II) fglrx(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) fglrx(0): #5: hsize: 1600 vsize 1200 refresh: 65 vid: 17833
(II) fglrx(0): #6: hsize: 1280 vsize 960 refresh: 85 vid: 22913
(II) fglrx(0): #7: hsize: 1600 vsize 1200 refresh: 70 vid: 19113
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 202.0 MHz Image Size: 360 x 270 mm
(II) fglrx(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0
(II) fglrx(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0
(II) fglrx(0): Serial No: CX 717343
(II) fglrx(0): Monitor name: PHILIPS 109B6
(II) fglrx(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 97 kHz, PixClock max 230 MHz
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff00410c1ee01ff20a00
(II) fglrx(0): 030f010368241bc4ef9ea8a154469924
(II) fglrx(0): 0e484cffef80455961598199d140a940
(II) fglrx(0): a9458159a94ae84e403062b0324040c0
(II) fglrx(0): 1300680e1100001e000000ff00204358
(II) fglrx(0): 20203731373334330a20000000fc0050
(II) fglrx(0): 48494c495053203130394236000000fd
(II) fglrx(0): 0032a01e6117000a2020202020200006
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000001
(II) fglrx(0): POWERplay version 3. 1 power state available:
(II) fglrx(0): 1. 520/540MHz @ 0Hz [enable load balancing]
(==) fglrx(0): QBS disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 27 modes found for primary display.
(--) fglrx(0): Virtual size is 1600x1200 (pitch 0)
(**) fglrx(0): *Mode "1600x1200": 162.0 MHz (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 (75.0 kHz)
(**) fglrx(0): *Mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024"x70.0 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync (74.6 kHz)
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 (64.0 kHz)
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024"x47.0 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync (50.9 kHz)
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024"x43.0 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync (46.3 kHz)
(**) fglrx(0): *Mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768"x70.0 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync (56.5 kHz)
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync (48.4 kHz)
(**) fglrx(0): Default mode "1440x900": 106.5 MHz (scaled from 0.0 MHz), 55.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1440x900"x60.0 106.50 1440 1520 1672 1904 900 903 909 934 +vsync (55.9 kHz)
(**) fglrx(0): Default mode "1400x1050": 121.8 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 +hsync (65.3 kHz)
(**) fglrx(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 (60.0 kHz)
(**) fglrx(0): Default mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x768"x60.0 79.50 1280 1344 1472 1664 768 771 778 798 +hsync (47.8 kHz)
(**) fglrx(0): Default mode "1280x720": 74.5 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 +hsync (44.8 kHz)
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864"x70.0 96.76 1152 1224 1344 1536 864 865 868 900 +hsync (63.0 kHz)
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 +hsync (53.7 kHz)
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864"x47.0 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync (43.0 kHz)
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864"x43.0 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync (39.2 kHz)
(**) fglrx(0): Default mode "960x720": 55.9 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "960x720"x60.0 55.85 960 1008 1104 1248 720 721 724 746 +hsync (44.8 kHz)
(**) fglrx(0): Default mode "864x648": 45.1 MHz (scaled from 0.0 MHz), 40.2 kHz, 60.0 Hz
(II) fglrx(0): Modeline "864x648"x60.0 45.08 864 904 992 1120 648 649 652 671 +hsync (40.2 kHz)
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600"x70.0 45.50 800 840 920 1040 600 601 604 625 +hsync (43.8 kHz)
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 (37.9 kHz)
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600"x56.0 36.00 800 824 896 1024 600 601 603 625 (35.2 kHz)
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576"x60.0 32.66 720 744 816 912 576 577 580 597 +hsync (35.8 kHz)
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480"x60.0 25.18 640 656 752 800 480 490 492 525 +hsync +vsync (31.5 kHz)
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400"x60.0 24.92 640 664 760 792 400 460 462 525 (31.5 kHz)
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300"x60.0 22.33 400 416 480 496 300 601 605 742 doublescan (45.0 kHz)
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240"x60.0 12.59 320 328 376 400 240 491 493 525 doublescan (31.5 kHz)
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200"x60.0 12.59 320 336 384 400 200 457 459 524 doublescan (31.5 kHz)
(--) fglrx(0): Display dimensions: (360, 270) mm
(--) fglrx(0): DPI set to (112, 112)
(--) fglrx(0): Virtual size is 1600x1200 (pitch 1600)
(**) fglrx(0): *Mode "1600x1200": 162.0 MHz (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 (75.0 kHz)
(**) fglrx(0): *Mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024"x70.0 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync (74.6 kHz)
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 (64.0 kHz)
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024"x47.0 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync (50.9 kHz)
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024"x43.0 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync (46.3 kHz)
(**) fglrx(0): *Mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768"x70.0 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync (56.5 kHz)
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync (48.4 kHz)
(**) fglrx(0): Default mode "1440x900": 106.5 MHz (scaled from 0.0 MHz), 55.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1440x900"x60.0 106.50 1440 1520 1672 1904 900 903 909 934 +vsync (55.9 kHz)
(**) fglrx(0): Default mode "1400x1050": 121.8 MHz (scaled from 0.0 MHz), 65.3 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 +hsync (65.3 kHz)
(**) fglrx(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 (60.0 kHz)
(**) fglrx(0): Default mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x768"x60.0 79.50 1280 1344 1472 1664 768 771 778 798 +hsync (47.8 kHz)
(**) fglrx(0): Default mode "1280x720": 74.5 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 +hsync (44.8 kHz)
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864"x70.0 96.76 1152 1224 1344 1536 864 865 868 900 +hsync (63.0 kHz)
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 +hsync (53.7 kHz)
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864"x47.0 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync (43.0 kHz)
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864"x43.0 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync (39.2 kHz)
(**) fglrx(0): Default mode "960x720": 55.9 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "960x720"x60.0 55.85 960 1008 1104 1248 720 721 724 746 +hsync (44.8 kHz)
(**) fglrx(0): Default mode "864x648": 45.1 MHz (scaled from 0.0 MHz), 40.2 kHz, 60.0 Hz
(II) fglrx(0): Modeline "864x648"x60.0 45.08 864 904 992 1120 648 649 652 671 +hsync (40.2 kHz)
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600"x70.0 45.50 800 840 920 1040 600 601 604 625 +hsync (43.8 kHz)
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 (37.9 kHz)
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600"x56.0 36.00 800 824 896 1024 600 601 603 625 (35.2 kHz)
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576"x60.0 32.66 720 744 816 912 576 577 580 597 +hsync (35.8 kHz)
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480"x60.0 25.18 640 656 752 800 480 490 492 525 +hsync +vsync (31.5 kHz)
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400"x60.0 24.92 640 664 760 792 400 460 462 525 (31.5 kHz)
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300"x60.0 22.33 400 416 480 496 300 601 605 742 doublescan (45.0 kHz)
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240"x60.0 12.59 320 328 376 400 240 491 493 525 doublescan (31.5 kHz)
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200"x60.0 12.59 320 336 384 400 200 457 459 524 doublescan (31.5 kHz)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(==) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.2.1
ABI class: X.Org Video Driver, version 4.1
(==) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x4000000b
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(II) fglrx(0): [pcie] 262144 kB allocated
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(II) fglrx(0): Direct rendering enabled
(II) fglrx(0): AC Adapter is used
(II) fglrx(0): Interrupt handler installed at IRQ 18.
(II) fglrx(0): Exposed events to the /proc interface
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[20] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[22] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[24] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[25] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[26] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[27] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[28] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(II) fglrx(0): detected X.org 7.4.3.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): DRIScreenInit for fglrx driver
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID PCI:5:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports PCI:5:0:0
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:5:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0x7fd22f841000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.56.4
(II) fglrx(0): Date: Dec 1 2008
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.27-ARCH
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x00004000
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x00960000
(II) fglrx(0): FBMM initialized for area (0,0)-(1600,1536)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1600,1200) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1600 x 336
(==) fglrx(0): Backing store disabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(II) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Solid Lines
Dashed Lines
Setting up tile and stipple cache:
24 128x128 slots
(II) fglrx(0): Acceleration enabled
(II) LoadModule: "amdxmm"
(II) Loading /usr/lib/xorg/modules//amdxmm.so
(II) Module amdxmm: vendor="X.Org Foundation"
compiled for 1.4.99.906, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID PCI:5:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports PCI:5:0:0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "dvorak"
(**) Keyboard0: XkbLayout: "dvorak"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Mouse0: Device: "/dev/input/mice"
(**) Mouse0: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/input/mice"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(**) Mouse0: Sensitivity: 1
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) AIGLX: Suspending AIGLX clients for VT switch
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) Mouse0: ps2EnableDataReporting: succeeded
output of lspci
05:00.0 VGA compatible controller: ATI Technologies Inc R480 [Radeon X850XT (PCIE)] (Primary)
05:00.1 Display controller: ATI Technologies Inc R480 [Radeon X850XT (PCIE)] (Secondary)
Ive tried telling my dear drivers where the graph card is by extracting the info from lspci and put in
"PCI:5:0:0"
But that doesn't seem to help (and 5:0:1 makes the X go bananas and refuse to start, but i have no idea why i have two of them pci busses occupied by me video card according to pciutils)
Then i realize that the fglrx module probably do find the bus! Just not a device to match with it (that's what the log sais), so after some searching i found something about that maybe the device identifier wasn't created in the /dev dir (/dev/dri/<device identifier>) But of what i could list it actully where there under the name of card0 wich i assumed the card identifier had to be named aswell, but after changing that... no dice. And it seemes like the vesa driver finds the device .
It is for me admitingly weird that when loading the vesa driver Ce X finds my card under /dev/dri/card0 But not from the begging with the "ati-driver"
I reasently switched from debian, after switching from gentoo, after switching from ubuntu. And i remembered that the stable ati driver for the x850xt card didnt work with debians new kernel (!) so had to use the one from the test branch... But trying that here on arch (using the 8.12-2 driver) didnt work either. And unfortunally i cant find the info again on what driver the debian ppl had modified that did and did not work.
It feels like there is some minor fault i myself overlooked the past 3 days, so hope that providing this information to you might make a bell ring out there for someone.
Juppa
PS! hope i didnt confuse you to much, im abit confused by the log and the texts ive read, apparently fglrx is the ati module and catalyst is the driver, but you are sposed to put fglrx as driver in the xorg.conf so it must be the driver? And accorinding to the log it involves the fglrx eh... module when loading the vesa driver, or is the log just telling me that the fglrx module/driver has been disabled (fglrx(0)) and that they went on trying with the vesa driver/module instead?In order to be viewed on the iPhone, YouTube is transcoding all their content to H.264. The initial announcement said- They'll have 10,000 videos ready by June 29th, and should complete transcoding the collection by this fall.
Since there are literally hundreds of thousands of YouTube videos out there (if not more), they just haven't gotten to transcoding your video yet (doing their Most Viewed videos first).
Maybe you are looking for
-
Ipod nano version 1.2 not reconized by pc or itunes
help, i have tried everything, the 5 steps re-install itunes 7. restart pc. and ipod. and nothing. my pc and itunes does not recongnize my ipod nano. HELP. also like to say that after reading all the complaints on here i wonder now why anyone would e
-
Dump is coming after Moving the request to Quality server.
Dear All, Dump is coming in a ABAP code after moving the same to quality server. Kindly refer the attached screenshot. Kindly suggest. Thanks and Regards Jai
-
Deleting old flat files inside a SSIS package - SSIS 2005
Hi, after each flat file import, I need to move the acquired file into an history folder and deleting old files of 1 week ago. How can I cancel these files, acting inside my SSIS 2005 pckg? Many thanks
-
I am freeing up some space and am using osx lion, but i have 12gb of back ups, how can i delete these and what are they?
-
Hide the title bar of a movie window like QuickTime X
Love the feature of QuickTime X of not showing the title bar/the control bar of a movie window (still waiting for Pro version, though. Is it coming out at all?) I'm wondering if anyone has figured out a way/tweak to hide the title bar of a iTunes mov