Bug 54338 - [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
Summary: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-31 18:23 UTC by xela
Modified: 2019-11-19 08:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description xela 2012-08-31 18:23:36 UTC
Hi, I'm using the most recent kernel — 3.5.3, before switching to it I used 3.5.0. I'm using amd64 Gentoo Linux. The problem is radeon driver is completely unable to load on my laptop (Dell Vostro 3350)

Here're some outputs:

$ dmesg | grep radeon
[    6.062962] [drm] radeon defaulting to kernel modesetting.
[    6.062966] [drm] radeon kernel modesetting enabled.
[    6.063009] radeon 0000:01:00.0: enabling device (0000 -> 0003)
[    6.628886] radeon 0000:01:00.0: Invalid ROM contents
[    6.628941] radeon 0000:01:00.0: Invalid ROM contents
[    6.628948] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[    6.628950] radeon 0000:01:00.0: Fatal error during GPU init
[    6.628953] [drm] radeon: finishing device.
[    6.629996] radeon 0000:01:00.0: no bo for sa manager
[    6.630126] radeon: probe of 0000:01:00.0 failed with error -22

$ uname -a
Linux 3.5.3 #1 SMP PREEMPT Fri Aug 31 20:42:09 EEST 2012 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Seymour XT/PRO [Radeon HD 7400M Series]

# lsmod | grep radeon
radeon                831358  0 
cfbfillrect             3717  2 i915,radeon
cfbimgblt               2073  2 i915,radeon
cfbcopyarea             3289  2 i915,radeon
ttm                    61238  1 radeon
i2c_algo_bit            5079  2 i915,radeon
drm_kms_helper         31193  2 i915,radeon
drm                   212584  5 ttm,i915,drm_kms_helper,radeon

# eix -e xorg-server
[D] x11-base/xorg-server
     Available versions:  1.9.5-r1 1.10.6-r1 1.11.4-r1 1.12.2 (~)1.12.3 (~)1.12.99.903 {{dmx doc ipv6 kdrive minimal nptl selinux static-libs tslib +udev xnest xorg xvfb}}
     Installed versions:  1.12.99.905(05:55:47 PM 08/31/2012)(ipv6 nptl udev xnest xorg -dmx -doc -kdrive -minimal -selinux -static-libs -tslib -xvfb)
     Homepage:            http://xorg.freedesktop.org/
     Description:         X.Org X servers

I'm not using xorg.conf file.

http://bpaste.net/show/43054/ — dmesg
http://bpaste.net/show/43055/ — kernel config
Comment 1 Alex Deucher 2012-08-31 18:40:38 UTC
(In reply to comment #0)
> Hi, I'm using the most recent kernel — 3.5.3, before switching to it I used
> 3.5.0. I'm using amd64 Gentoo Linux. The problem is radeon driver is completely
> unable to load on my laptop (Dell Vostro 3350)

Is this a regression?  If so can you bisect?
Comment 2 xela 2012-08-31 19:06:11 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > Hi, I'm using the most recent kernel — 3.5.3, before switching to it I used
> > 3.5.0. I'm using amd64 Gentoo Linux. The problem is radeon driver is completely
> > unable to load on my laptop (Dell Vostro 3350)
> 
> Is this a regression?  If so can you bisect?

No, I'm just trying various kernel versions to get my card working. However, I just tried Fedora 17 live CD (kernel 3.3) and there radeon module loaded normally. 

So, I have to compare two linux kernel versions — 3.3 and 3.5.3 ?
Comment 3 Alex Deucher 2012-09-04 03:45:58 UTC
(In reply to comment #2)
> No, I'm just trying various kernel versions to get my card working. However, I
> just tried Fedora 17 live CD (kernel 3.3) and there radeon module loaded
> normally. 

Can you attach the dmesg from the working boot?

> 
> So, I have to compare two linux kernel versions — 3.3 and 3.5.3 ?

you might want to test 3.4 or even some early 3.5 kernels to see if you can narrow it down further.  At that point you can use git to bisect and find what commit broke things.
Comment 4 Martin Peres 2019-11-19 08:28:57 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/297.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.