Bug 36812
Summary: | Radeon fails to load firmware | ||
---|---|---|---|
Product: | Drivers | Reporter: | James Cloos (cloos) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | akpm, alexdeucher |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.0-rc2 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
James Cloos
2011-06-06 23:54:53 UTC
If it was Ok a couple of weeks ago then I assume that this is a psot-2.6.39 regression? Longer than that. The box is usually headless; when I first got it the missing firmware prevented booting, so I added radeon.modeset=0 to the grub config and manually changed that for those occasions when I moved the box to the TV. Today I changed the grub config in honour of the upcoming 3.0. ☺ (That it boots now even though it fails to load that firmware is a nice progression.) My best guess, based on the timestamps of my .config archive, is that I last connected it to the TV during the 38-rc1 timeframe. I forgot to add: I don’t see from git-grep(1)ing the tree where or how the kernel knows to find firmware in /lib/firmware. All I can see is /lib/firmware as the target to make firmware_install and several comments specifying /lib/firmware as the typical location. What am I missing? Most likely you did not include the firmware in your initrd. Ah. OK. The driver tries to load the firmware before / is mounted, then? As I do not use initrd there the answer seems to be: -CONFIG_EXTRA_FIRMWARE="" +CONFIG_EXTRA_FIRMWARE="radeon/R600_rlc.bin" +CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" to the .config. Closing as invalid. Will reopen if the above .config change doesn’t fix it. (Last time I must have manually done what EXTRA_FIRMWARE does. I lost that clone in the meantime, though, so that is only a guess. (It was a clone of my local, pristine clone. And the .configs were backed up in their own git repo. So that loss didn’t seem like much of a nuisance. But I obviously forgot about this issue in the meantime. ☹) |