ATI RS485 VIDEO DRIVER

The email address entered is already associated to an account. To post a comment you must log in. It’s just the backtrace at the time gdb attaches to the process, which implicitly stops its execution. The information about this bug in Launchpad is automatically pulled daily from the remote bug. I have to unplug the second monitor, boot to X, replug the monitor, restart X and then it works correctly.

Uploader: Tat
Date Added: 18 April 2013
File Size: 40.22 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 77215
Price: Free* [*Free Regsitration Required]

The issue thus seems to be solved, I now have to get familiar with the new Xrandr stuff though.

RadeonXpress – Community Help Wiki

Any hint howto proceed any further? Please visit this page to clear all LQ-related cookies. Please assign your manual to a product: Having a problem logging in?

Just to confuse the issue.

Where does it say error? I tried this on the old driver as well and it didn’t help – X guys evidently fixed it: If you need to reset your password, click here.

Last Drivers  CALLAWAY FT-I XXV DRIVER DOWNLOAD

I found a solution: Find More Posts by diegoh. Ask a Question Usually answered in minutes! By now the backtrace is meaningless:. I’m assuming this is a ai headed radeon? Registration is quick, simple and absolutely free.

If you find any other problems let me know. When switching to a virtual console, the monitor powers off. To my surprise, the movie was shown on both displays! Other bug subscribers Subscribe someone else.

If you haven’t installed it, you can do it from here; http: Org Video Driver, version 2. Are you new to LinuxQuestions. And it zti correctly now!

Bryce Harrington bryce wrote on Can you get a backtrace of the crash with gdb? I probably need to add a special case fall back for single crtc chips.

Ati driver motherboard rs485 com awrdacpi

ATI ES e not recognized Thanks for your report. Issue persists for all 6.

Entry deleted from font path. However, the X server now ignores the x mode entry in xorg. After the handle and continuing, when I change to a VT I get the following gdb log:. The KVM is driving 64 machines and the only time I’ve seen it lose the mouse like this is with this patched package. The resolutions are both quite uncommon and share an interesting trait: You can’t post answers that contain an email address.