On Wednesday, 20 December 2017 17:27:25 GMT Mike Gilbert wrote: > On Wed, Dec 20, 2017 at 11:51 AM, Mick <michaelkintz...@gmail.com> wrote:
> > What step am I missing to arrive at a bootable kernel with all necessary
> > firmware?
>
> Are you using an initramfs? Does the initramfs contain the necessary
> firmware blobs?
Thanks again Mike, no I am not using an initramfs. I just had a further look
to see why the 4.14.7 does not boot. I discovered radeon/RV730_pfp.bin blob
does not load and xserver segfaults.
CPU microcode and WiFi firmware loads fine. So seems more relevant to a
radeon firmware problem.
Some additional observations:
When I boot with 4.14.7 the xserver segfaults:
==============================================
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series,
REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series,
AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
MULLINS, KAVERI, HAWAII
[ 30.806] (++) using VT number 7
[ 30.808] (EE)
[ 30.808] (EE) Backtrace:
[ 30.808] (EE) 0: /usr/bin/X (xorg_backtrace+0x4a) [0x55f50ff8d4aa]
[ 30.808] (EE) 1: /usr/bin/X (0x55f50fde0000+0x1b1199) [0x55f50ff91199]
[ 30.808] (EE) 2: /lib64/libpthread.so.0 (0x7f32631b0000+0x13d30)
[0x7f32631c3d30]
[ 30.808] (EE) 3: /usr/bin/X (xf86PlatformDeviceCheckBusID+0xa7)
[0x55f50fe950e7]
[ 30.808] (EE) 4: /usr/bin/X (0x55f50fde0000+0xaf8f2) [0x55f50fe8f8f2]
[ 30.809] (EE) 5: /usr/bin/X (xf86CallDriverProbe+0xb0) [0x55f50fe67970]
[ 30.809] (EE) 6: /usr/bin/X (xf86BusConfig+0x46) [0x55f50fe682b6]
[ 30.809] (EE) 7: /usr/bin/X (InitOutput+0x961) [0x55f50fe76211]
[ 30.809] (EE) 8: /usr/bin/X (0x55f50fde0000+0x54866) [0x55f50fe34866]
[ 30.809] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf1)
[0x7f3262e21541]
[ 30.809] (EE) 10: /usr/bin/X (_start+0x2a) [0x55f50fe1e6ea]
[ 30.809] (EE)
[ 30.809] (EE) Segmentation fault at address 0x0
[ 30.809] (EE)
Fatal server error:
[ 30.809] (EE) Caught signal 11 (Segmentation fault). Server aborting
==============================================
Looking at dmesg I notice this:
======================================================
[ 1.069560] [drm] radeon kernel modesetting enabled.
[ 1.070133] [drm] initializing kernel modesetting (RV730 0x1002:0x9488
0x1028:0x02FE 0x00).
[ 1.070309] resource sanity check: requesting [mem 0x000c0000-0x000dffff],
which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
[ 1.070505] caller pci_map_rom+0x53/0xd0 mapping multiple BARs
[ 1.070655] ATOM BIOS: BR036993
[ 1.070813] radeon 0000:02:00.0: VRAM: 1024M 0x0000000000000000 -
0x000000003FFFFFFF (1024M used)
[ 1.070995] radeon 0000:02:00.0: GTT: 1024M 0x0000000040000000 -
0x000000007FFFFFFF
[ 1.071219] [drm] Detected VRAM RAM=1024M, BAR=256M
[ 1.071352] [drm] RAM width 128bits DDR
[ 1.071773] [TTM] Zone kernel: Available graphics memory: 2012374 kiB
[ 1.071883] [TTM] Initializing pool allocator
[ 1.071990] [TTM] Initializing DMA pool allocator
[ 1.072241] [drm] radeon: 1024M of VRAM memory ready
[ 1.072372] [drm] radeon: 1024M of GTT memory ready.
[ 1.072525] [drm] Loading RV730 Microcode
[ 1.072679] radeon 0000:02:00.0: Direct firmware load for radeon/
RV730_pfp.bin failed with error -2
[ 1.072859] r600_cp: Failed to load firmware "radeon/RV730_pfp.bin"
[ 1.072974] [drm:rv770_init] *ERROR* Failed to load firmware!
[ 1.073183] radeon 0000:02:00.0: Fatal error during GPU init
[ 1.073294] [drm] radeon: finishing device.
[ 1.084495] ACPI: Battery Slot [BAT0] (battery present)
[ 1.095528] [TTM] Finalizing pool allocator
[ 1.095637] [TTM] Finalizing DMA pool allocator
[ 1.095903] [TTM] Zone kernel: Used memory at exit: 0 kiB
[ 1.096082] [drm] radeon: ttm finalized
[ 1.096832] radeon: probe of 0000:02:00.0 failed with error -2
[ 1.097301] [drm] Initialized vgem 1.0.0 20120112 for virtual device on
minor 0
[ 1.103389] brd: module loaded
[ 1.105711] loop: module loaded
[ 1.105810] mtip32xx Version 1.3.1
=====================================
Comparing firmware between kernels 4.12.12 and 4.14.7 I see:
$ ls -l /usr/src/linux-4.12.12-gentoo/firmware/radeon/RV730*
-rw-r--r-- 1 root root 5440 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_me.bin
-rw-r--r-- 1 root root 454 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_me.bin.gen.S
-rw-r--r-- 1 root root 6704 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_me.bin.gen.o
-rw-r--r-- 1 root root 14972 Jul 3 00:07 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_me.bin.ihex
-rw-r--r-- 1 root root 3392 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_pfp.bin
-rw-r--r-- 1 root root 461 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_pfp.bin.gen.S
-rw-r--r-- 1 root root 4656 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_pfp.bin.gen.o
-rw-r--r-- 1 root root 9340 Jul 3 00:07 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_pfp.bin.ihex
-rw-r--r-- 1 root root 467 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_smc.bin.gen.S
-rw-r--r-- 1 root root 17952 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/
firmware/radeon/RV730_smc.bin.gen.o
$ ls -l /usr/src/linux-4.14.7-gentoo/firmware/radeon/RV730*
-rw-r--r-- 1 root root 467 Dec 20 11:46 /usr/src/linux-4.14.7-gentoo/
firmware/radeon/RV730_smc.bin.gen.S
-rw-r--r-- 1 root root 17952 Dec 20 11:46 /usr/src/linux-4.14.7-gentoo/
firmware/radeon/RV730_smc.bin.gen.o
As you can see above there is a marked difference between the firmware built
by the two kernels. In any case, my '/lib/firmware/' path contains:
$ ls -l /lib/firmware/radeon/RV730*
-rw-r--r-- 1 root root 5440 Dec 20 17:29 /lib/firmware/radeon/RV730_me.bin
-rw-r--r-- 1 root root 3392 Dec 20 17:29 /lib/firmware/radeon/RV730_pfp.bin
-rw-r--r-- 1 root root 16684 Dec 20 17:29 /lib/firmware/radeon/RV730_smc.bin
How should I proceed from here?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
