I had a problem with using an ATI RADEON 9250 AGP graphics card on Windows 7. the manufacturer didn't make windows driver for this graphics card, there is only Windows XP/2000 available. I downloaded Windows XP driver from ATI website and then did force installation by using device manager. It installed successfully but produced another problem. When I do shutting down as usual using start menu shut down option, there a blue screen came up and within few seconds it restarted rather than shut it down itself which was very annoying to me. After having that problem, I spent many hours and on internet researching the solution on google. I found many solutions for this issue on net by many expertises but none of them worked for me. I was almost hopeless and was deciding to buy a new AGP graphics card that supports Windows 7. Then again, I decided to do last try using my driverpack solution program. It also failed to install the ATI Radeon 9250 driver for Windows 7 but it gave me a nice clue. It referred a website page link to download the XP driver for Radeon 9250. I downloaded the referred XP driver and extracted the downloaded file by using winrar. Then I went to device manager and installed it manually. Finally I became successful to make this graphics card working under my Windows 7 Operationg System.
If the driver listed is not the right version or operating system, search our driver archive for the correct version. Enter Palit Radeon 9250 into the search box above and then submit. In the results, choose the best match for your PC and operating system.
If the driver listed is not the right version or operating system, search our driver archive for the correct version. Enter ATI Radeon 9250 into the search box above and then submit. In the results, choose the best match for your PC and operating system.
This release for all Radeon family products updates the AMD display driver to the latest version. This unified driver has been further enhanced to provide the highest level of power, performance, and reliability.
The GATOS project has long been known as the path to take for enabling TV output support with the open-source X.Org driver on the Radeon 8500 to 9250 (R200) series, but soon you may no longer need to worry about the GATOS patch. Hanno has announced on the project mailing list that all of those involved with the GATOS project have agreed to move away from the GPL in favor of the MIT/X11 license. This relicensing makes it possible for the GATOS code to be merged with the X.Org Radeon R200 driver.
This morning AMD has re-released the 8.39.4 fglrx driver after it was taken down last week over watermark problems. This latest 8.39.4 revision available from the AMD website should properly produce the needed signature to remove this small annoyance from the display. No other changes had went into this release. If you run into any problems with the 8.39.4 driver, be sure to stop by the Phoronix Forums.
Last month was an odd month where an aticonfig issue had caused two fglrx display drivers to be released in the same month (8.38.6 and 8.38.7). Though it seems the AMD release train has run off the tracks once more and we'll probably see another driver out of the AMD camp in the coming days. If you're using the distribution-specific packaging scripts or obtaining the fglrx driver from a distribution repository, it's recommended to not upgrade to fglrx v8.39.4. While not an issue that will harm you, you'll be stuck with an AMD watermark in the bottom right hand corner of the screen that reads "Testing use only".
Today AMD had released the 8.39.4 display driver, which offers support for Fedora 7 and also corrects some bugs. However, at least one serious issue has crept into this driver. If you are running the fglrx driver right now, chances are there's a black and green watermark in the lower right hand corner of your screen that says "AMD Testing Use Only". This watermark is only supposed to display on internal/beta fglrx builds.
The ATI 6.6.191 display driver has been released. No no, not the fglrx blob but instead a new release for the open-source ATI Radeon display driver. The ATI 6.6.191 release is a driver in the path to the ATI v6.7.0. The 6.6.191 driver contains major rewrites of the output subsystem and other changes. RandR 1.2 code will be merged with the ATI Radeon driver once X.Org 7.3 is out. The release announcement can be found at FreeDesktop.org.
Many Linux users have expressed concern over ATI's Catalyst Linux drivers for various reasons, but most of these users seem to be taking the wrong approach. These users express their disapproval and seek improvements by flaming on forums, forming petitions, bombarding the BugZilla, and using the ATI feedback form. However, this isn't really effective. On Michael's Phoronix web-blog he has outlined some strategies for actively engaging ATI/AMD's OEM/ODM/AIB partners in seeking Linux display driver improvements. He also states that at least one major OEM is interested in improved Linux drivers, but they are afraid of adverse effects to the Windows Catalyst drivers.
If you are interested in running the AMD fglrx display drivers with Fedora 7 (Test 1), Michael Larabel is providing details on this process at MichaelLarabel.com. At the time of posting this news entry, he is still working on verifying that the new packaging scripts are working with Fedora 7. Stay tuned.
After publishing our NVIDIA AYiR 2006 earlier this month, we have now posted our ATI AYiR 2006. This nine page piece covers and re-tests all twelve of the fglrx display drivers released this year. We also share a few details about the forecast for ATI next year when it comes to their Linux software. This article can be discussed here and Digged here.
Advanced Micro Devices has released the ATI fglrx 8.31.5 Linux display driver. This new driver brings X11R72 support, official Radeon X1950 series support added, and quite a few bug fixes. The latest Linux display drivers for x86 and x86_64 along with accessing the release notes can be accessed from the Proprietary ATI Linux Driver page. The Phoronix review of these drivers can be found here along with Radeon X1950PRO Linux benchmarks. If you run into issues or want to share your thoughts on these drivers, be sure to stop by the forums.
AMD has issued the new fglrx display drivers -- coming only two weeks after 8.30.3. The changes are minimal though there is improved X-Video performance for Radeon X1000 products. The Phoronix review can be read here. Meanwhile join in on the discussion here and the release notes are at AMD.
ATI has come out today with the 8.29.6 CATALYST Linux display drivers. New in this release is Linux 2.6.18 kernel support, bug fixes, and R200 support has been removed. The Phoronix review of these new Linux display drivers can be read here, while the Phoronix Forums have an active discussion.
Well well, the day has finally come. It is now day number 50; the final day for this ATI Linux trial. With that said, it's about time for me to share some concluding remarks regarding ATI's recent Linux efforts with their monthly fglrx display drivers. On the first day, I didn't know whether I would be able to survive without going green (no pun intended), but towards the end of this experience, it was almost like achieving nirvana...Read the final Phoronix Redblog post here.
There is nothing like starting the week off with a bang as ATI delivers the Windows CATALYST 6.6 and fglrx 8.26.18 Linux display drivers. Yes, the ATI drivers are shipping on a Monday compared against their usual Wednesday routine. After last month's belated 8.25.18 release, these new drivers were originally scheduled to ship on June 7; however, there was a delay on the Windows CATALYST side followed by a second delay bringing it to today. However, the ATI Linux drivers are bringing a fair amount of changes to the table as they had done last month with a host of fixes and other improvements. At Phoronix we have our usual details to share about this fglrx release as well as our traditional performance take... MOREATI Release Notes (8.26.18)
Without subscribers, LWN would simply not exist. Please consider signing up for a subscription and helping to keep LWN publishing By Jonathan CorbetFebruary 8, 2008 The X window system is the kernel of the desktop Linux experience; if Xdoes not work well, nothing built on top of it will work well either. Despiteits crucial role, X suffered from relative neglect for a number of yearsbefore being revitalized by the X.org project. Two talks at linux.conf.aucovered the current state of the X window system and where we can expectthings to go in the near future.Keith Packard is a fixture at Linux-related events, so it was no surpriseto see him turn up at LCA. His talk covered X at a relatively high,feature-oriented level. There is a lot going on with X, to say the least. Keith started, though, with the announcement that Intel had releasedcomplete documentation for some of its video chips - a welcome move, beyondany doubt.There are a lot of things that X.org is shooting for in the near future.The desktop should be fully composited, allowing software layers to provideall sorts of interesting effects. There should be no tearing (thebriefly inconsistent windows which result from partial updates). We needintegrated 2D and 3D graphics - a goal which is complicated by the factthat the 2D and 3D APIs do not talk to each other. A flicker-free boot(where the X server starts early and never restarts) is on mostdistributors' wishlist. Other desired features include fast and secureuser switching, "hotplug everywhere," reduced power consumption, and areduction in the (massive) amount of code which runs with root privileges.So where do things stand now? 2D graphics and textured video work well.Overlaid video (where video data is sent directly to the frame buffer - a performance technique used by some video playback applications)does not work with compositing, though. 3D graphics does not always workthat well either; Keith put up the classic example of glxgears runningwhile the window manager is doing the "desktops on a cube" routine - the 3Dapplication runs outside of the normal composite mechanism and so cannot berotated with all the other windows.On the tearing front, only 3D graphics supports no-tearing operations now.Avoiding tearing is really just a matter of waiting for the video retracebefore making changes, but the 2D API lacks support for that.The integration of APIs is an area requiring some work still. One problemis that Xv (video) output cannot be drawn offscreen - again, a problem forcompositing. Some applications still use overlays, which really just haveno place on the contemporary desktop. It is impossible to do 3D graphicsto or from pixmaps, which defeats any attempt to pass graphical databetween the 2D and 3D APIs. On the other side, 2D operations do notsupport textures.Fast user switching can involve switching between virtual terminals, whichis "painful." Only one user session can be running 3D graphics at a time,which is a big limitation. On the hotplug front, there are somelimitations on how the framebuffer is handled. In particular, the X servercannot resize the framebuffer, and it can only associate one framebufferwith the graphics processor. Some GPUs have maximum line widths, so theone-framebuffer issue limits the maximum size of the internal desktop.With regard to power usage: Keith noted that using framebuffer compressionin the Intel driver saves 1/2 watt of power. But there are a number ofthings to be fixed yet. 2D graphics busy-waits on the GPU, meaning that agraphics-intensive program can peg the system's CPU, even though the GPU isdoing all of the real work. But the GPU could be doing more as well; forexample, video playback does most of the decoding, rescaling, and colorconversion in the CPU. But contemporary graphics processors can do all ofthat work - they can, for example, take the bit stream directly from a DVDand display it. The GPU requires less power than the CPU, so shifting thatwork over would be good for power consumption as well as systemresponsiveness.Having summarized the state of the art, Keith turned his attention to thefuture. There is quite a bit of work being done in a number of areas - andnot being done in others - which leads toward a better X for everybody. Onthe 3D compositing front, what's needed is to eliminate the "shared backbuffers" used for 3D rendering so that the rendered output can be handledlike any other graphical data.Eliminating tearing requires providing the ability to synchronize with thevertical retrace operation in the graphics card. The core mechanism to dothis is already there in the form of the X Sync extension. But, saysKeith, nobody is working on bringing all of this together at the moment.Getting rid of boot-time flickering, instead, is a matter of getting the Xserver properly set up sufficiently early in the process. That's mostly adistributor's job.To further integrate APIs, one thing which must be done is to get rid ofoverlays and to allow all graphical operations (including Xv operations) todraw into pixmaps. There is a need for some 3D extensions to create achannel between GLX and pixmaps.Supporting fast user switching means adding the ability to work withmultiple DRM master. Framebuffer resizing, instead, means movingcompletely over to the EXA acceleration architecture and finishing thetransition to the TTM memorymanager. In the process, it may become necessary to break all existingDRI applications, unfortunately. And multiple framebuffer support is theobjective of a project called "shatter," which will allow screens to besplit across framebuffers.Improving the power consumption means getting rid of the busy-waiting with2D graphics (Keith say the answer is simple: "block"). The XvMC protocolshould be extended beyond MPEG; in particular, it needs work to be able toproperly support HDTV. All of this stuff is currently happening.Finally, on the security issue, Keith noted the ongoing work to movegraphical mode setting into the kernel. That will eliminate the need forthe server to directly access the hardware - at least, when DRM-based 2Dgraphics are being done. In that case, it will become possible to run theX server as "nobody," eliminating all privilege. There are few people whowould argue against the idea of taking root privileges away from a massiveprogram like the X server.In a separate talk, Dave Airlie covered the state of Linux graphics at alower level - support for graphics adapters. He, too, talked about movinggraphical mode setting into the kernel, bringing an end to a longstanding"legacy issue" and turning the X server into just a rendering system. Thatwill reduce security problems and help with other nagging issues (graphicalboot, suspend and resume) as well.Mode setting is the biggest area of work at the moment. Beyond that, thegraphics developers are working on getting TTM into the kernel; this willgive them a much better handle on what is happening with graphics memory.Then, graphics drivers are slowly being reworked around the Gallium3Darchitecture. This will improve and simplify these drivers significantly, but "it'sgoing to be a while" before this work is ready. The upcoming DRI2 work will improve buffering andfix the "glxgears on a cube" problem.Moving on to graphics adapters: AMD/ATI has, of course, begun the processof releasing documentation for its hardware. This happened in aninteresting way, though: AMD went to SUSE in order to get a driverdeveloped ahead of the documentation release; the result was the "radeonhd"driver. Meanwhile, the Avivo project, which had been reverse-engineeringATI cards, had made significant progress toward a working driver. Davetook that work and the AMD documentation to create theimproved "radeon" driver. So now there are two competing projects writingdrivers for ATI adapters. Dave noted that code is moving in bothdirections, though, so it is not a complete duplication of work. (As anaside, from what your editor has heard, most observers expect the radeondriver to win out in the end).The ATI R500 architecture is a logical addition to the earlier (supported)chipsets, so R500 support will come relatively quickly. R600, instead, isa totally new processor, so R600 owners will be "in for a wait" before aworking driver is available.Intel has, says Dave, implemented the "perfect solution": it develops freedrivers for its own hardware. These drivers are generally well done andwell documented. Intel is "doing it right."NVIDIA, of course, is not doing it right. The Nouveau driver is comingalong, now, with 5-6 developers working on it. Dave had an RandRimplementation in a state of half-completion for some time; he finallydecided that he would not be able to push it forward and merged it into themainline repository. Since then, others have run with it and RandR supportis moving forward quickly. It was, he says, a classic example of why it isgood to get the code out there early, whether or not it is "ready."Performance is starting to get good, to the point that NVIDIA suddenlyadded some new acceleration improvements to its binary-only driver.Dave is still hoping that NVIDIA might yet release some documents - if ithappens by next year, he says, he'll stand in front of the room and dance ajig. Index entries for this article Conferencelinux.conf.au/2008 (Log in to post comments) ATI + xrandr Posted Feb 8, 2008 20:33 UTC (Fri) by hathawsh (guest, #11289) [Link] 2b1af7f3a8