Bug 90655 - [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 INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: PowerPC Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-26 08:45 UTC by Mathieu Malaterre
Modified: 2016-04-19 12:15 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mathieu Malaterre 2015-05-26 08:45:02 UTC
On my old Mac Mini G4 (PowerPC) I am seeing this dmesg output:

[   12.058859] [drm] Initialized drm 1.1.0 20060810
[   13.051939] [drm] radeon kernel modesetting enabled.
[   13.055867] checking generic (9c008000 5a000) vs hw (98000000 8000000)
[   13.055875] fb: switching to radeondrmfb from OFfb ATY,RockHo
[   13.059702] Console: switching to colour dummy device 80x25
[   13.060655] radeon 0000:00:10.0: enabling device (0006 -> 0007)
[   13.061195] [drm] initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962).
[   13.061227] [drm] register mmio base: 0x90000000
[   13.061236] [drm] register mmio size: 65536
[   13.061318] radeon 0000:00:10.0: Invalid ROM contents
[   13.061341] radeon 0000:00:10.0: Invalid ROM contents
[   13.061356] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[   13.061379] [drm] Using device-tree clock info
[   13.061417] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 4x mode
[   13.061433] radeon 0000:00:10.0: putting AGP V2 device into 4x mode
[   13.061484] radeon 0000:00:10.0: GTT: 256M 0x00000000 - 0x0FFFFFFF


It would be nice to either remove this error report as I believe it is erroneous.

Using debian/jessie with:

$ apt-cache policy libdrm-radeon1
libdrm-radeon1:
  Installé : 2.4.58-2
  Candidat : 2.4.58-2
 Table de version :
 *** 2.4.58-2 0
        500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
        100 /var/lib/dpkg/status
Comment 1 joro-2013 2015-05-26 17:51:30 UTC
(In reply to Mathieu Malaterre from comment #0)
> On my old Mac Mini G4 (PowerPC) I am seeing this dmesg output:
> 
> [   12.058859] [drm] Initialized drm 1.1.0 20060810
> [   13.051939] [drm] radeon kernel modesetting enabled.
> [   13.055867] checking generic (9c008000 5a000) vs hw (98000000 8000000)
> [   13.055875] fb: switching to radeondrmfb from OFfb ATY,RockHo
> [   13.059702] Console: switching to colour dummy device 80x25
> [   13.060655] radeon 0000:00:10.0: enabling device (0006 -> 0007)
> [   13.061195] [drm] initializing kernel modesetting (RV280 0x1002:0x5962
> 0x1002:0x5962).
> [   13.061227] [drm] register mmio base: 0x90000000
> [   13.061236] [drm] register mmio size: 65536
> [   13.061318] radeon 0000:00:10.0: Invalid ROM contents
> [   13.061341] radeon 0000:00:10.0: Invalid ROM contents
> [   13.061356] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
> [   13.061379] [drm] Using device-tree clock info
> [   13.061417] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 4x
> mode
> [   13.061433] radeon 0000:00:10.0: putting AGP V2 device into 4x mode
> [   13.061484] radeon 0000:00:10.0: GTT: 256M 0x00000000 - 0x0FFFFFFF
> 
> 
> It would be nice to either remove this error report as I believe it is
> erroneous.
> 
> Using debian/jessie with:
> 
> $ apt-cache policy libdrm-radeon1
> libdrm-radeon1:
>   Installé : 2.4.58-2
>   Candidat : 2.4.58-2
>  Table de version :
>  *** 2.4.58-2 0
>         500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages
>         100 /var/lib/dpkg/status

Hi,

actually the "error report" is correct, on PPC platforms there is no BIOS but the hardware is configured via Open Firmware. I've been getting this message for years, it's totally harmless.

By the way: Do you have AGP mode working stable on the Mac Mini G4 ? I've been trying to do that for years with no success :-(
Comment 2 Mathieu Malaterre 2016-04-19 12:15:22 UTC
Ok. Closing as invalid then.


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.