ATI RV410 [Radeon X700 Pro (PCIE)] driver fails

Bug #1177568 reported by AZ
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hi,

I upgrade this system to onerice and since then or so my radeon graphics card can only be used using the Xorg vesa driver, thus lacking bigger than 1024x768 resolution support and all the other stuff radeons driver support.
The system used to work fine with precise and older ubuntu releases.

The Xorg radeon driver fails with (Xorg.log)
[ 27.806] (II) [KMS] drm report modesetting isn't supported.
[ 27.806] (WW) Falling back to old probe method for modesetting
[ 27.806] (EE) open /dev/dri/card0: No such file or directory
[ 27.806] (EE) open /dev/dri/card0: No such file or directory
[ 27.806] (WW) Falling back to old probe method for fbdev

And the kernel shows in dmesg:
[ 1.392989] [drm] radeon kernel modesetting enabled.
[ 1.399427] radeon 0000:01:00.0: VRAM: 128M 0x00000000C8000000 - 0x00000000CFFFFFFF (128M used)
[ 1.399435] radeon 0000:01:00.0: GTT: 512M 0x00000000A8000000 - 0x00000000C7FFFFFF
[ 1.399534] radeon 0000:01:00.0: irq 42 for MSI/MSI-X
[ 1.399558] radeon 0000:01:00.0: radeon: using MSI.
[ 1.399597] [drm] radeon: irq initialized.
[ 1.401674] [drm] radeon: 128M of VRAM memory ready
[ 1.401678] [drm] radeon: 512M of GTT memory ready.
[ 1.406080] [drm] radeon: 2 quad pipes, 1 z pipes initialized.
[ 1.406197] radeon 0000:01:00.0: WB enabled
[ 1.406205] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000a8000000 and cpu addr 0xffc77000
[ 1.521091] [drm] radeon: ring at 0x00000000A8001000
[ 1.521453] radeon 0000:01:00.0: Fatal error during modeset init
[ 1.521465] [drm] radeon: finishing device.
[ 1.521632] [drm] radeon: cp finalized
[ 1.522384] radeon 0000:01:00.0: f3678000 unpin not necessary
[ 1.522561] [drm] radeon: ttm finalized
[ 1.522914] radeon: probe of 0000:01:00.0 failed with error -12

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-extra-3.5.0-28-generic 3.5.0-28.48
ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9
Uname: Linux 3.5.0-28-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 3352 F.... pulseaudio
                      michael 3400 F.... xfce4-volumed
Date: Tue May 7 23:24:11 2013
HibernationDevice: RESUME=
MachineType: MEDIONPC MS-7091
MarkForUpload: True
ProcEnviron:
 LANGUAGE=de_DE:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-28-generic root=UUID=b08039b8-681f-4878-a516-8498f72d9e9f ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-28-generic N/A
 linux-backports-modules-3.5.0-28-generic N/A
 linux-firmware 1.95.1
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2013-04-07 (30 days ago)
dmi.bios.date: 04/01/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7091
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/01/2005:svnMEDIONPC:pnMS-7091:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7091:rvr:cvn:ct3:cvr:
dmi.product.name: MS-7091
dmi.sys.vendor: MEDIONPC

Revision history for this message
AZ (m-dev) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
AZ (m-dev) wrote :

The kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/ fixes the problem for me.

tags: added: kernel-fixed-upstream
Revision history for this message
AZ (m-dev) wrote :

dmesg on kernel 3.9.0-030900-generic

[ 1.961649] [drm] radeon kernel modesetting enabled.
[ 1.967058] radeon 0000:01:00.0: VRAM: 128M 0x00000000C8000000 - 0x00000000CFFFFFFF (128M used)
[ 1.967077] radeon 0000:01:00.0: GTT: 512M 0x00000000A8000000 - 0x00000000C7FFFFFF
[ 1.967243] radeon 0000:01:00.0: irq 42 for MSI/MSI-X
[ 1.967288] radeon 0000:01:00.0: radeon: using MSI.
[ 1.967356] [drm] radeon: irq initialized.
[ 1.984446] [drm] radeon: 128M of VRAM memory ready
[ 1.984451] [drm] radeon: 512M of GTT memory ready.
[ 1.988845] [drm] radeon: 2 quad pipes, 1 z pipes initialized.
[ 1.988904] radeon 0000:01:00.0: WB enabled
[ 1.988914] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000a8000000 and cpu addr 0xffc95000
[ 1.989447] [drm] radeon: ring at 0x00000000A8001000
[ 2.040108] fbcon: radeondrmfb (fb0) is primary device
[ 2.111464] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 2.111470] radeon 0000:01:00.0: registered panic notifier
[ 2.111484] [drm] Initialized radeon 2.30.0 20080528 for 0000:01:00.0 on minor 0

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

AZ, could you please test for this in Saucy via http://cdimage.ubuntu.com/daily-live/current/ ?

tags: added: kernel-fixed-upstream-v3.9 regression-release
removed: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.