Radeon HD 3300 not recognized

[Steve Kondik]

Binary package hint: xserver-xorg-video-ati

The Radeon HD 3300 device onboard my Asus M3A78-T is not recognized by the ATI driver in Intrepid. It's working with FGLRX (with it's own set of bugs). Hopefully it is just a case of a missing device ID?

Xorg.0.log snippet:

(--) PCI:*(0@1:5:0) ATI Technologies Inc Radeon HD 3300 Graphics rev 0, Mem @ 0xd0000000/0, 0xfe9f0000/0, 0xfe800000/0, I/O @ 0x0000d000/0
(II) Primary Device is: PCI 01@00:05:0
(EE) No devices detected.

Fatal server error:
no screens found

lspci -vvv output:

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 Graphics
 Subsystem: ASUSTeK Computer Inc. Device 834d
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 18
 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Region 1: I/O ports at d000 [size=256]
 Region 2: Memory at fe9f0000 (32-bit, non-prefetchable) [size=64K]
 Region 5: Memory at fe800000 (32-bit, non-prefetchable) [size=1M]
 Capabilities: <access denied>
 Kernel driver in use: fglrx_pci
 Kernel modules: fglrx

[Steve Kondik (cyanogen)]

Also, it seems to confuse Intrepid's beta installer. It attempts to load the ATI driver for the card and the X server just exits repeatedly and never goes into failsafe mode, essentially breaking the graphical install on this hardware.

[simon (simon-segfault-info)]

Same issue here.

I have the same Hardware, an Asus M3A78-T with an onboard Radeon HD 3300 device.

I had a look at the driver source and i think adding the Radeon HD 3300 ID should be sufficient to make the driver work with the card.

The PCI-ID of the Radeon HD 3300 is: 9614

Look here:
http://developer.amd.com/drivers/pc_vendor_id/Pages/default.aspx
http://developer.amd.com/gpu_assets/ATI_Device_IDs_Sept_08.txt

[Bryce Harrington (bryce)]

I'd love to see a full Xorg.0.log to be certain. Also, would anyone like to have a shot at proposing a patch to add that pci id? (should be a pretty easy patch)

[goto (gotolaunchpad)]

Unfortunately there are two drivers for your graphics chip. Could you please try also the radeonhd driver? If it does not work there, too, could you please report that, too? Thanks!

[Bryce Harrington (bryce)]

Should be working in Jaunty; this chip is listed in the -ati driver source:

./src/radeon_chipset_gen.h: { PCI_CHIP_RS780_9614, "ATI Radeon HD 3300 Graphics" },

Typically support for new chips is too invasive to be SRU'd, but you could request it through -backports if you'd like.

Anyway, since it's fixed int he development release I'll go ahead and close it; feel free to reopen if you see the same issue on Jaunty. Note since this is new support there could be secondary problems; please file those as new bugs. A helpful shortcut for doing this is `ubuntu-bug xserver-xorg-video-ati`, which will capture the necessary logs, config files, etc.

[Heitzso (heitzso)]

In jaunty it is severely broken as of early April, with vesa, radeon, radeonhd, fglrx all failing to work -- the monitor locks up when trying to start x; so you cannot jump over to a console, e.g. ALT-CTL-F1. You can still ssh in. Mobo is Gigabyte GA-MA790GP w/ all memory slots filled (4G total). Googling around it seems the problem may be related to having all memory slots filled, i.e. if I pull two memory sticks and drop back to 2G then it might work. I haven't tried that. But that might explain why someone might believe 3300 works in Jaunty, if they tested on a system without all memory slots filled.

[mgcsinc (mgcsinc)]

Exact same issues as Heitzso. My RAM is also filled and haven't tried removing any, but will soon.