Does anyone have any experience with the combination of a Thinkpad R40 and the ATI Radeon Mobility M6 LY video chip? I've had CentOS 4.1, 4.2, and now 4.3 running just great with 1024x768 resolution, but according the IBM specs, this chip is capable of 1280x1024.
A quick lspci -v | grep ATI spewed the following:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
I can successfully change the settings under the display menu to 1280x1024, but upon restarting X the default greeter crashes. After that, it picks another greeter and allows me to log in, with it still picking 1024x768. I've played around with trying to manually change the settings in /etc/X11/xorg.conf file. I've tried various depth settings to no avail.
The section identifying the card in xorg.conf is:
Section "Device" Identifier "Videocard0" Driver "radeon" VendorName "Videocard vendor" BoardName "ATI Radeon Mobility M6" EndSection
According to what I've been reading, that's what is supposed to be there. I've found a few things stating that DRI could be a problem, but I'm not too familiar with this.
Also, a friend has an R40 but has the ATI Mobility Radeon 7500 chip, instead of the M6 like mine. He's also running CentOS 4.3 and having the exact same problem I'm having. Same deal, according to the IBM specs his chipset as well as mine should be capable of 1280x1024. Any thoughts or related experience with this? If not, it's not a huge deal, I've been using it 1024x768 for well over a year now, but the extra resolution would be wonderful. Thanks!
Max
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 28, 2006 at 11:10:57AM -0500, Max wrote:
Does anyone have any experience with the combination of a Thinkpad R40 and the ATI Radeon Mobility M6 LY video chip? I've had CentOS 4.1, 4.2, and now 4.3 running just great with 1024x768 resolution, but according the IBM specs, this chip is capable of 1280x1024.
It might be, but is your screen capable of that resolution ?
This might also (very likely, actually) be a modeline related problem. In that case, you are in for some pain.
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
Rodrigo Barbosa wrote:
It might be, but is your screen capable of that resolution ?
This might also (very likely, actually) be a modeline related problem. In that case, you are in for some pain.
Yeah, I'm sure my screen is capable of this resolution, because the spec page I'm looking at is for my particular laptop model. These are specs directly from IBM. Technically IBM says the display is capable of 2048x1536 at the maximum, and 1280x1024 is listed as well.
If it's going to be extremely difficult to get it working, I'm not sure it's worth the pain to me. Thanks.
Max
On Tue, 2006-03-28 at 13:22 -0500, Max H. wrote:
Rodrigo Barbosa wrote:
It might be, but is your screen capable of that resolution ?
This might also (very likely, actually) be a modeline related problem. In that case, you are in for some pain.
Yeah, I'm sure my screen is capable of this resolution, because the spec page I'm looking at is for my particular laptop model. These are specs directly from IBM. Technically IBM says the display is capable of 2048x1536 at the maximum, and 1280x1024 is listed as well.
If it's going to be extremely difficult to get it working, I'm not sure it's worth the pain to me. Thanks.
Max
<snip>
Perhaps... After it's booted run X config and see what it'll go for? Then you end up with somethings like this in your xorg.conf
Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
It may be that you have to boot into the lower res but can get higher res after modules are loaded? Or modify initrd to include a needed module?
HTH BILL
William L. Maltby wrote:
It may be that you have to boot into the lower res but can get higher res after modules are loaded? Or modify initrd to include a needed module?
It'll let you make the change to 1280x1024 just fine, but the display simply won't go. The default is to load DRI (direct rendering) modules, but when I run glxinfo I get the following output stating it's actually not on. Perhaps this is a reason for it not working, I'm not sure.
name of display: :0.0 display: :0 screen: 0 direct rendering: No
This is way beyond my knowledge of X11, so I think for now I'm not going to worry about it. I might Google a bit on how to turn on direct rendering, if not it works fine with 1024x768...
Thanks again.
Max
On Mar 28, 2006, at 12:41 PM, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 28, 2006 at 11:10:57AM -0500, Max wrote:
Does anyone have any experience with the combination of a Thinkpad R40 and the ATI Radeon Mobility M6 LY video chip? I've had CentOS 4.1, 4.2, and now 4.3 running just great with 1024x768 resolution, but according the IBM specs, this chip is capable of 1280x1024.
It might be, but is your screen capable of that resolution ?
This might also (very likely, actually) be a modeline related problem. In that case, you are in for some pain.
hm. it might be a good idea to verify that the "IgnoreEDID" option is set to "off" in the radeon driver settings in xorg.conf. dealing with LCD panels got a lot easier for me once i started checking that.
-steve
--- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
Steve Huff wrote:
hm. it might be a good idea to verify that the "IgnoreEDID" option is set to "off" in the radeon driver settings in xorg.conf. dealing with LCD panels got a lot easier for me once i started checking that.
I tried with the option you said, and it's still not working. I also took an external IBM LCD monitor (I know for sure it's capable of higher resolutions than 1280x1024) and I can't get it to work either. It works good at 1024x768. I made it even boot up on the external from the BIOS settings just to ensure the laptop LCD wasn't getting in the way. That for sure rules out the problem being limited to the LCD screen.
Max