Hello and sorry please my English. I'm running X.Org 1.4.2 server ... ((BTW: How to find out the version? (7.4, ...) X -showconfig gives also just :"1.4.2" )) on "radeon" driver on my Radeon 7000 AGP 32MB card with 2 VGA outputs. The problem is, that if no "Virtual" line in Screen in xorg.conf is set, then the maximum of screen size is set to 1600x1200. This is too little for my card - She supports (accel.) up to 2048x1200 [or 2048x1200 - I'm not sure]. This is also reported in /var/log/Xorg.0.log: "(II) RADEON(0): Max desktop size set to 2048x1200" But after start of X xrandr reports: "Screen 0: minimum 320 x 200, current 1600 x 600, maximum 1600 x 1200" ?? Why is the maximum down from 2048x1200 to 1600x1200 ?? This let me use my DUALHEAD just by 2x 800x600 :-( The problem is, that by use of LiveCD Linuxes the xorg.conf is setup-ed automatically and I can not change the Virtual size. xrandr --fb XxY don't work. Also: could You please do, that X.Org will respect the Virtual size reported by driver ? Or at least: make it possible to let xrandr change maximal Virtual size ? Thank You Karel Petranek
(In reply to comment #0) > I'm running X.Org 1.4.2 server ... > ((BTW: How to find out the version? (7.4, ...) X -showconfig gives also just > :"1.4.2" )) 1.4.2 is the version of the Xorg server, and the version that developers need to investigate bugs. X11R7.4 would be the version of a collection of all the X module releases, including libraries, client programs, server, and drivers, and reporting that makes developers have to go look up which Xorg server version was included (assuming you even have the exact version included in X11R7.4 - most distros don't ship an exact X11R7.x collection, but include newer bug fix or feature releases of modules released between the once or twice a year X11R7.x collections). [Sorry, I don't know why your screen size isn't being set correctly, so can't help you there, but can explain the versioning.]
Fixed with KMS, and probably not fixable without.
(In reply to comment #2) > Fixed with KMS, and probably not fixable without. > Thank You, but what is KMS ? And what should I do ?
(In reply to comment #3) > but what is KMS ? Kernel ModeSetting, available for R100-R500 as of Linux 2.6.31. > And what should I do ? As your concern seems to be about live CDs, I guess you'll have to try / wait for one which provides radeon KMS support. E.g. I think current snapshots of Ubuntu karmic have radeon KMS, but I'm not sure if there are any live CDs with it available yet.
(In reply to comment #4) Oh .... I'm afraid it will be bad! See my other bug report: http://bugs.freedesktop.org/show_bug.cgi?id=23421 Kernel with KMS break my dualhead down total :-/ If it is the future .... BTW - o You think, that with KMS would be possible to set video mode like 2048x768 ?! And it would set up dualhead mode ? Thank You Karel
(In reply to comment #5) > http://bugs.freedesktop.org/show_bug.cgi?id=23421 > > Kernel with KMS break my dualhead down total :-/ > If it is the future .... It's a bug that will probably be fixed at some point (if it isn't fixed already with current upstream), not an inherent KMS feature. > BTW - o You think, that with KMS would be possible to set video mode like > 2048x768 ?! And it would set up dualhead mode ? Not sure what you mean, but with KMS you can dynamically and arbitrarily change the virtual screen size up to the hardware limits.
(In reply to comment #6) > > BTW - o You think, that with KMS would be possible to set video mode like > > 2048x768 ?! And it would set up dualhead mode ? > > Not sure what you mean, but with KMS you can dynamically and arbitrarily change > the virtual screen size up to the hardware limits. > I mean - today I set my resolutions and dualhead configuration with xrandr, and if I had understand the sense of KMS, in future this would by done by kernel itself - Xorg just will call some kernel function (if user will request e.g. resolution or dualhead configuration change). Also my question is - how to set/change graphic output parms (virtual size, dualhead config.) BEFORE Xorg comes up ? Maybe if dualhead is set up correctly before X, then it stays correct also after Xorg starts.
(In reply to comment #7) > I mean - today I set my resolutions and dualhead configuration with xrandr, and > if I had understand the sense of KMS, in future this would by done by kernel > itself - Xorg just will call some kernel function (if user will request e.g. > resolution or dualhead configuration change). > xrandr will still work. The radeon driver will pass the request to the kernel rather than banging the hw itself. > Also my question is - how to set/change graphic output parms (virtual size, > dualhead config.) BEFORE Xorg comes up ? You should get a console on the drm framebuffer device before X starts. You'll need to start X to enable dualhead, etc. However, as was stated before, you don't have to specify a virtual size since the kernel will dynamically resize the framebuffer based on the requested output setup.
(In reply to comment #8) > > Also my question is - how to set/change graphic output parms (virtual size, > > dualhead config.) BEFORE Xorg comes up ? > > You should get a console on the drm framebuffer device before X starts. You'll > need to start X to enable dualhead, etc. However, as was stated before, you > don't have to specify a virtual size since the kernel will dynamically resize > the framebuffer based on the requested output setup. > I'm not sure, that this is so. It is the main problem discussed here. When the initial virtual size (e.g. set to 1600x1200) is too small to include my dualhead display (e.g. 2048*768), then it fails to set it - "... it must fit in virtual resolution". I have to shut down X, modify xorg.conf (add VirualSize ...) and restart X. ... no "dynamically resize" :-(
BTW - in Fedora 11 (with KMS) The initial virtual is set up contrariwise too big. And is also problem, then in this case, HW acceleration will not work, if the virtual size exceed the HW supported maximum. Also I would expect: - the initial virtual size is set to maximum (with accel.) supported by Card - with possibility to extend it
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.