radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?

radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?

[Stuffed Crust]

[-- Attachment #1: Type: text/plain, Size: 5348 bytes --]

I have an AMD64 laptop with a Radeon Mobility X700, and a 1680x1050
screen.  I'm trying to get it to work with the "new" radeonfb driver in
Linux 2.6.15-rc6.  I have not tested the "old" driver.  As best as I can 
tell, I'm the second person to ask about this particular bit of 
hardware.

The Radeon M26, aka Mobility X700, is supposedly a derivative of the
desktop X700, aka RV410, which in turn is supposedly derived from the
R423. (They certainly make this rather confusing..) As configured, mine 
has 128 megs of RAM and a PCI ID of 1002:5653.  

This deviceid is not present in the device table, but to get it detected 
to begin with, I added this to the device table in radeon_base.c: 

CHIP_DEF(PCI_CHIP_RV410_XX,     R420,   CHIP_HAS_CRTC2 | CHIP_IS_MOBILITY),

And in ati_ids.h:

#define PCI_CHIP_RV410_XX               0x5653

As I mentioned, this chip (M26, RV410) is supposedly closer to the X800 
(R420) than the X600 (RV380).  Just in case, I tried setting it to a 
'RV380' target as well, with similar results. 

Basically what happens is that on initialization the screen goes blank 
but the system is otherwise responsive.  logging in remotely, I'm able 
to get this output from the point where 'modprobe radeonfb' is called:

ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 217
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=0.00 MHz (RefDiv=0) Memory=200.00 Mhz, System=200.00 MHz
radeonfb: PLL min 0 max 36438016
radeonfb: No connector info table detected
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type CRT found
radeonfb: panel ID string: J�����&�Q
radeonfb: detected LVDS panel size from BIOS: 9728x1734
radeondb: BIOS provided dividers will be used
radeonfb: Assuming panel size 9728x1734
radeonfb: Dynamic Clock Power Management enabled
Console: switching to colour frame buffer device 80x25
radeonfb (0000:01:00.0): ATI Radeon VS 

Meanwhile, 'modprobe radeonfb panel_yres=1050 monitor_layout=LVDS 
	   ignore_edid=1 nomodeset=1 force_measure_pll=1 
           mode_option=1280x1024-8@60 force_dfp=1' gives:

ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 217
xtal calculation failed: 4674
radeonfb: Used default PLL infos
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=166.00 Mhz, System=166.00 MHz
radeonfb: PLL min 12000 max 35000
radeonfb: No connector info table detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: J�����&�Q
radeonfb: detected LVDS panel size from BIOS: 9728x1734
radeondb: BIOS provided dividers will be used
radeonfb: Assuming panel size 9728x1734
radeonfb: Dynamic Clock Power Management enabled
Console: switching to colour frame buffer device 80x25
radeonfb (0000:01:00.0): ATI Radeon VS 

Mucking with module options has no discernable effect, and the LVDS
panel information is consistently misdetected, obviously..  It would
seem that all of the panel information is garbage.  (does fetching the
panel info from the BIOS work when running on an x86-64 system?)

Finally, the output 'lspci -vv', after the modprobe:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE) (prog-if 00 [VGA])
        Subsystem: Acer Incorporated [ALI]: Unknown device 007e
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 217
        Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 9000 [size=256]
        Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
                Device: Latency L0s <256ns, L1 <4us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
                Link: Latency L0s <256ns, L1 <2us
                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x16
        Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [100] Advanced Error Reporting

I can provide additional information as needed, and of course act as a
guniea pig.  I'll be installing a i386 kernel (+userland) on this box
tomorrow to see it it behaves any differently.

Any suggestions on what I can do?

 - Solomon
-- 
Solomon Peachy        				 ICQ: 1318344
Melbourne, FL 					 
Quidquid latine dictum sit, altum viditur.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?

[Petr Vandrovec]

Stuffed Crust wrote:
> I have an AMD64 laptop with a Radeon Mobility X700, and a 1680x1050
> screen.  I'm trying to get it to work with the "new" radeonfb driver in
> Linux 2.6.15-rc6.  I have not tested the "old" driver.  As best as I can 
> tell, I'm the second person to ask about this particular bit of 
> hardware.
> 
> The Radeon M26, aka Mobility X700, is supposedly a derivative of the
> desktop X700, aka RV410, which in turn is supposedly derived from the
> R423. (They certainly make this rather confusing..) As configured, mine 
> has 128 megs of RAM and a PCI ID of 1002:5653.  
> 
> This deviceid is not present in the device table, but to get it detected 
> to begin with, I added this to the device table in radeon_base.c: 
> 
> CHIP_DEF(PCI_CHIP_RV410_XX,     R420,   CHIP_HAS_CRTC2 | CHIP_IS_MOBILITY),
> 
> And in ati_ids.h:
> 
> #define PCI_CHIP_RV410_XX               0x5653
> 
> As I mentioned, this chip (M26, RV410) is supposedly closer to the X800 
> (R420) than the X600 (RV380).  Just in case, I tried setting it to a 
> 'RV380' target as well, with similar results. 

I have simillar notebook, just with 1920x1200 panel.  Unfortunately new 
BIOS these pieces use has information in other places, so radeonfb does 
not find anything (as far as I can tell, panel ID string is not in the 
BIOS image at all, and i2c busses are connected elsewhere than on 
hardware radeonfb knows about).

> Mucking with module options has no discernable effect, and the LVDS
> panel information is consistently misdetected, obviously..  It would
> seem that all of the panel information is garbage.  (does fetching the
> panel info from the BIOS work when running on an x86-64 system?)

It is not in the BIOS anymore.  VESA call 0x4F15 works fine, but I did 
not bothered with looking at the BIOS yet.  With my hardware radeonfb 
correctly finds that LVDS output is programmed for 1920x1200 and does 
not touch it, unfortunately it has some problems with memory fetches 
which cause pixels (+-)512-768 and 1536-1792 to be missing on display, 
and right side of picture being black.

For now I use vesafb - unfortunately BIOS does not have 1920x1200 
videomode, but 1600x1200 works more or less acceptable, those pixels are 
really small...
								Petr



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?

[Benjamin Herrenschmidt]

> It is not in the BIOS anymore.  VESA call 0x4F15 works fine, but I did 
> not bothered with looking at the BIOS yet.  With my hardware radeonfb 
> correctly finds that LVDS output is programmed for 1920x1200 and does 
> not touch it, unfortunately it has some problems with memory fetches 
> which cause pixels (+-)512-768 and 1536-1792 to be missing on display, 
> and right side of picture being black.
> 
> For now I use vesafb - unfortunately BIOS does not have 1920x1200 
> videomode, but 1600x1200 works more or less acceptable, those pixels are 
> really small...

Does it work with a recent X.org ? What does it say in the log ? The ATI
BIOS tables have changed format and radeonfb doesn't (yet) know about
the new format.

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: radeonfb: Radeon Mobility X700 (M26) + x86-64 supported?

[Petr Vandrovec]

Benjamin Herrenschmidt wrote:
>>It is not in the BIOS anymore.  VESA call 0x4F15 works fine, but I did 
>>not bothered with looking at the BIOS yet.  With my hardware radeonfb 
>>correctly finds that LVDS output is programmed for 1920x1200 and does 
>>not touch it, unfortunately it has some problems with memory fetches 
>>which cause pixels (+-)512-768 and 1536-1792 to be missing on display, 
>>and right side of picture being black.
>>
>>For now I use vesafb - unfortunately BIOS does not have 1920x1200 
>>videomode, but 1600x1200 works more or less acceptable, those pixels are 
>>really small...
> 
> 
> Does it work with a recent X.org ? What does it say in the log ? The ATI
> BIOS tables have changed format and radeonfb doesn't (yet) know about
> the new format.

I've put logs at http://platan.vc.cvut.cz/ftp/private/radeon/.  It works fine 
with fglrx driver.  With radeon driver from X.org 6.9 it tries to do something, 
but it is hopelessly off - I can see that it attempts to show black/white X 
screen with mouse cursor, but lines are not horizontally synchronized and 
vertically picture is shifted so that vertical blanking is somewhere around 
LCD's 66%.  I can try to grab movie if you want...

ddcprobe.txt is output from ddcprobe, dmesg.txt are radeonfb's boot messages, 
vga.rom is BIOS, and fglrx.xorg.log and radeon.xorg.log are X.org logs.
								Petr



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click