I don't load fglrx at the same time of course, I just want to be able to load it from time to time (it used to garble the framebuffer console completely if you used radeonfb, might even have caused lockups, can't remember exactly).
I can of course try radeonfb instead of vesa with the new radeon drm module, but I think it should run with vesa - I don't think I'm the only one using that...
I do not use gatos driver. I don't think I have a module loaded which should interfere with the monitor i2c device, though I do have a bunch of i2c modules loaded (for lm_sensors, and bttv-driven tuner card).
I did update drm cvs just right before I tried it an hour ago...



Roland


Jon Smirl wrote:
you can't have the fglrx driver loaded with the newer DRM's. They are
both trying to control the same piece of hardware.

On Mon, 18 Oct 2004 22:52:45 +0200, Roland Scheidegger
<[EMAIL PROTECTED]> wrote:

Jon Smirl wrote:

Do you have the new radeon framebuffer driver loaded? If so, try
loading the old one. Let me know and I'll check it out more here.

No, I'm using the old vesa framebuffer (compiled in). I'll have radeonfb compiled as a module, but it's not loaded. (I'm basically using vesa due to earlier problems, and afaik still present problems with the fglrx driver which I sometimes use for testing)

Roland







------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to