[lucid] Intel 82855PM AGP stuck at 1x mode

[Wenzhuo Zhang]

I upgraded my ThinkPad X32 to Ubuntu 10.04 beta last weekend. I noticed that the 4x AGP video adapter (ATI Technologies Inc Radeon Mobility M6 LY) is stuck at 1x mode.

$ dmesg | grep -i agp
[ 0.098646] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
[ 16.687261] Linux agpgart interface v0.103
[ 16.801167] agpgart-intel 0000:00:00.0: Intel 855PM Chipset
[ 16.914364] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 17.273550] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
[ 17.273572] agpgart-intel 0000:00:00.0: putting AGP V2 device into 1x mode
[ 17.273609] radeon 0000:01:00.0: putting AGP V2 device into 1x mode

and setting the AGPMode option in the Device section of /etc/X11/xorg.conf no longer works:

$ grep -i agp /var/log/Xorg.0.log
...
(--) RADEON(0): Chipset: "ATI Radeon Mobility M6 LY (AGP)" (ChipID = 0x4c59)
(II) RADEON(0): AGP card detected
(WW) RADEON(0): Option "AGPMode" is not used

WORKAROUND: Add:
options radeon agpmode=4

to:
/etc/modprobe.d/radeon-kms.conf

update initramfs:
sudo update-initramfs -u && sudo reboot now

[Martin Reiche (grimsrud)]

Same here on an IBM X31 with the same video adapter.

[Martin Reiche (grimsrud)]

Just wanted to let you know that you can enable AGPmode 4 by adding
options radeon agpmode=4
to /etc/modprobe.d/radeon-kms.conf
After that update initramfs:
sudo update-initramfs -u
Than reboot. Thats it :-)

[Wenzhuo Zhang (wenzhuo)]

It works here. Thanks.

After agpmode=4 is passed to the kernel driver radeon, dmesg shows:

[ 17.992868] [drm] radeon kernel modesetting enabled.
[ 17.993022] radeon 0000:01:00.0: power state changed by ACPI to D0
[ 17.993037] radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[ 18.002328] [drm] radeon: Initializing kernel modesetting.
[ 18.009602] [drm] register mmio base: 0xC0100000
[ 18.009606] [drm] register mmio size: 65536
[ 18.010023] [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
[ 18.010046] [drm] AGP mode requested: 4
[ 18.010053] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
[ 18.010074] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
[ 18.010111] radeon 0000:01:00.0: putting AGP V2 device into 4x mode
[ 18.010144] [drm] radeon: VRAM 64M
[ 18.010146] [drm] radeon: VRAM from 0x00000000 to 0x03FFFFFF
[ 18.010149] [drm] radeon: GTT 256M
[ 18.010151] [drm] radeon: GTT from 0xD0000000 to 0xDFFFFFFF
[ 18.010182] [drm] radeon: irq initialized.
[ 18.011330] [drm] Detected VRAM RAM=64M, BAR=128M
[ 18.011335] [drm] RAM width 32bits DDR
[ 18.012913] [TTM] Zone kernel: Available graphics memory: 441986 kiB.
[ 18.012917] [TTM] Zone highmem: Available graphics memory: 642374 kiB.
[ 18.012939] [drm] radeon: 16M of VRAM memory ready
[ 18.012942] [drm] radeon: 256M of GTT memory ready.
[ 18.040258] [drm] radeon: cp idle (0x00008080)
[ 18.040556] [drm] Loading R100 Microcode
[ 18.040881] platform radeon_cp.0: firmware: requesting radeon/R100_cp.bin
[ 18.061943] [drm] radeon: ring at 0x00000000D0000000
[ 18.061965] [drm] ring test succeeded in 1 usecs
[ 18.069418] [drm] radeon: ib pool ready.
[ 18.069525] [drm] ib test succeeded in 0 usecs
[ 18.070475] [drm] Panel ID String: 1024x768
[ 18.070479] [drm] Panel Size 1024x768
[ 18.070759] [drm] Radeon Display Connectors
[ 18.070762] [drm] Connector 0:
[ 18.070764] [drm] VGA
[ 18.070767] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[ 18.070769] [drm] Encoders:
[ 18.070772] [drm] CRT1: INTERNAL_DAC1
[ 18.070774] [drm] Connector 1:
[ 18.070776] [drm] LVDS
[ 18.070777] [drm] Encoders:
[ 18.070779] [drm] LCD1: INTERNAL_LVDS
[ 18.186940] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
[ 18.187498] yenta_cardbus 0000:02:00.1: CardBus bridge found [1014:0532]
[ 18.205147] [drm] fb mappable at 0xE0040000
[ 18.205152] [drm] vram apper at 0xE0000000
[ 18.205154] [drm] size 786432
[ 18.205156] [drm] fb depth is 8
[ 18.205158] [drm] pitch is 1024
[ 18.235234] fb0: radeondrmfb frame buffer device
[ 18.235238] registered panic notifier
[ 18.235247] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0

[Jeremy Foshee (jeremyfoshee)]

Hi Wenzhuo,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 544988

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Martin Reiche (grimsrud)]

I am not the orig. reporter of this bug but I can confirm that the problem still exists with an IBM X31 in 10.10 alpha3.

[Martin Reiche (grimsrud)]

Still exists with an IBM X31 in 10.10 beta

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Martin Reiche (grimsrud)]

The 10.10 RC has still this problem. At least with the Live-CD.
Can't comment on Mainline-Kernel as my X31 runs Debian now.

Greets

[penalvch (penalvch)]

Wenzhuo Zhang, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[oliver (oliver-schinagl)]

13.04 still has the same issue, same fix applies.

[penalvch (penalvch)]

oliver, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.