Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-24 Thread Mick 
On Sunday, 24 December 2017 04:10:55 GMT Adam Carter wrote:

> > 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
> 
> Earlier I saw
> 
> CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin
> radeon/RV730_smc.bin radeon/RV710_uvd.bin"

Yes, other than the Intel microcode I followed the Gentoo Wiki page for my 
graphics card:

https://wiki.gentoo.org/wiki/Radeon

> For radeon/R700_rlc.bin
> $ find /lib/firmware/ -name \*R700\*
> /lib/firmware/radeon/R700_rlc.bin
> 
> For radeon/RV730_smc.bin
> $ find /lib/firmware/ -name \*RV730\*
> /lib/firmware/radeon/RV730_pfp.bin
> /lib/firmware/radeon/RV730_smc.bin
> /lib/firmware/radeon/RV730_me.bin
> 
> For adeon/RV710_uvd.bin
> $ find /lib/firmware/ -name \*RV710\*
> /lib/firmware/radeon/RV710_me.bin
> /lib/firmware/radeon/RV710_pfp.bin
> /lib/firmware/radeon/RV710_smc.bin
> /lib/firmware/radeon/RV710_uvd.bin
> 
> So it looks like you're trying to load firmware from three different
> models.

Yes, this is what the Wiki recommends for RV730.


> Run lspci -v to determine which is correct one, then load all the firmwares
> for that model.

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV730/M96-XT [Mobility Radeon HD 4670] (prog-if 00 [VGA controller])
Subsystem: Dell RV730/M96-XT [Mobility Radeon HD 4670]
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at d000 (32-bit, prefetchable) [size=256M]
I/O ports at 2000 [size=256]
Memory at cfef (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 

Kernel driver in use: radeon

02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI 
Audio [Radeon HD 4000 series]
Subsystem: Dell RV710/730 HDMI Audio [Radeon HD 4000 series]
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at cfeec000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 

Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel


It seems the blobs changed.  The firmware_install message confused me by 
making me think this was the cause of not being able to initiate the graphics 
card when I tried to boot the new kernel, rather than the missing blobs.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-23 Thread Adam Carter 
>
> 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
>

Earlier I saw

CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin
radeon/RV730_smc.bin radeon/RV710_uvd.bin"

For radeon/R700_rlc.bin
$ find /lib/firmware/ -name \*R700\*
/lib/firmware/radeon/R700_rlc.bin

For radeon/RV730_smc.bin
$ find /lib/firmware/ -name \*RV730\*
/lib/firmware/radeon/RV730_pfp.bin
/lib/firmware/radeon/RV730_smc.bin
/lib/firmware/radeon/RV730_me.bin

For adeon/RV710_uvd.bin
$ find /lib/firmware/ -name \*RV710\*
/lib/firmware/radeon/RV710_me.bin
/lib/firmware/radeon/RV710_pfp.bin
/lib/firmware/radeon/RV710_smc.bin
/lib/firmware/radeon/RV710_uvd.bin

So it looks like you're trying to load firmware from three different
models.

Run lspci -v to determine which is correct one, then load all the firmwares
for that model.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Peter Humphrey 
On Wednesday, 20 December 2017 15:51:03 GMT Mick wrote:
> On Wednesday, 20 December 2017 15:28:03 GMT Peter Humphrey wrote:
> > On Wednesday, 20 December 2017 12:22:29 GMT Mick wrote:
> > > Has something changed in 4.14.7-gentoo sources from its predecessors?
> 
> [snip ...]
> 
> > What firmware are you trying to install? This box needs firmware for the
> > graphics card and the Intel CPU, and I've been declaring the file names
> > in CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR. As the display
> > works fine, and so does opencl on the GPU since I emerged
> > dev-libs/amdgpu-pro- opencl, I assume that the firmware is being
> > loaded. I didn't even know about a firmware_install make target.
> 
> Thanks Peter,
> 
> I am also declaring relevant firmware in the kernel for CPU microcode and
> GPU, but they do not get loaded when I build kernel 4.14.7:
> 
> $ grep FIRMWARE /usr/src/linux/.config
> CONFIG_PREVENT_FIRMWARE_BUILD=y
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin radeon/
> RV730_smc.bin radeon/RV710_uvd.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
> # CONFIG_CYPRESS_FIRMWARE is not set
> # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FIRMWARE_MEMMAP=y
> # CONFIG_GOOGLE_FIRMWARE is not set
> # CONFIG_TEST_FIRMWARE is not set

Hm. Mine is:

# grep FIRMWARE /usr/src/linux/.config
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-3f-02 intel-ucode/06-3f-04 amdgpu/
polaris10_ce.bin amdgpu/polaris10_k_smc.bin amdgpu/polaris10_mc.bin amdgpu/
polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/
polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin 
amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/
polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_FIRMWARE_EDID=y
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_GOOGLE_FIRMWARE is not set
# CONFIG_TEST_FIRMWARE is not set

I don't see that cypress entry (why not? Are you using gentoo-sources?), but 
otherwise it looks the same. If I didn't have all that polaris stuff I 
wouldn't have an X display; that's how I started off, and I had to go 
looking for the right set of amdgpu modules to load.

> So I can't load a desktop because xserver will not launch.  I also recall
> having additional firmware for WiFi/BT cards on this laptop.
> 
> The same problem exists on other systems, some running AMD.

We must differ in some other way, I suppose in the way we build our kernels. 
This is my kernel build script on this UEFI box:

# cat /usr/local/bin/kmake
#!/bin/bash
mount /boot
cd /usr/src/linux
time (make -j12 && make modules_install && make install &&\
/bin/ls -lh --color=auto /boot && echo &&\
cp -v ./arch/x86/boot/bzImage /boot/EFI/Boot/bootX64.efi
) &&\
echo; echo "Rebuilding modules" && echo &&\
emerge --jobs --load-average=48 @module-rebuild @x11-module-rebuild && echo 
&&\
echo "Remounting /sys/firmware/efi/efivars read-write" &&\
mount -oremount,rw /sys/firmware/efi/efivars && echo &&\
echo "Don't forget to bootctl-install the new kernel!" && echo

HTH, but I wonder...

-- 
Regards,
Peter.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mike Gilbert 
On Wed, Dec 20, 2017 at 12:39 PM, Mick  wrote:
> [1.072525] [drm] Loading RV730 Microcode
> [1.072679] radeon :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!

Does this error occur before your root filesystem has been mounted?
You should see a message about mounting root further down in the dmesg
output.

If that's the case, and your kernel needs the firmware blob before
root has been mounted, you will probably need to start using an
initramfs, or add radeon/RV730_pfp.bin to CONFIG_EXTRA_FIRMWARE.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Floyd Anderson 

On Wed, 20 Dec 2017 16:51:04 +
Mick  wrote:

On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote:

On Wed, Dec 20, 2017 at 9:26 AM, Mick  wrote:



> You are quite right, there is no firmware_install in the 4.14.7 release.
> What does this mean?  How are we meant to install firmware now?

I believe all firmware has been removed from the kernel sources.

You should install sys-kernel/linux-firmware, or grab just the files
you need from the git repo.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git


Thank you all, but I see to have a mental disconnect here:

I already have sys-kernel/linux-firmware-20170314 installed.

I have specified in the kernel which blobs I need and /lib/firmware/ as the
path for the kernel to find any firmware it may need.

I used to run make firmware_install and the kernel was able to load whatever
firmware I had specified so that CPU/GPU can function properly at boot time.

With 4.14.7 I (can) no longer do this;


Since I fully encrypt my drives and therefore using an EFI-stub kernel 
with an embedded initramfs, I use genkernel-next and different scripts 
to build my kernels. It can be tricky and feels like a tool-chain but 
also works for me.




AND

the newly compiled kernel does not load at boot time any of the needed
firmware.

What step am I missing to arrive at a bootable kernel with all necessary
firmware?


Assuming your specified blobs are all available and required kernel 
options like CONFIG_MICROCODE and CONFIG_MICROCODE_INTEL [1] are proper 
set, I’m not sure it makes any difference but the default is:


   CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

without the appended forward slash.


[1] 


--
Regards,
floyd

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mick 
On Wednesday, 20 December 2017 17:27:25 GMT Mike Gilbert wrote:
> On Wed, Dec 20, 2017 at 11:51 AM, Mick  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 (0x55f50fde+0x1b1199) [0x55f50ff91199]
[30.808] (EE) 2: /lib64/libpthread.so.0 (0x7f32631b+0x13d30) 
[0x7f32631c3d30]
[30.808] (EE) 3: /usr/bin/X (xf86PlatformDeviceCheckBusID+0xa7) 
[0x55f50fe950e7]
[30.808] (EE) 4: /usr/bin/X (0x55f50fde+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 (0x55f50fde+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 0x000c-0x000d], 
which spans more than PCI Bus :00 [mem 0x000d4000-0x000d7fff window]
[1.070505] caller pci_map_rom+0x53/0xd0 mapping multiple BARs
[1.070655] ATOM BIOS: BR036993
[1.070813] radeon :02:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[1.070995] radeon :02:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[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 :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 :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 :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

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mike Gilbert 
On Wed, Dec 20, 2017 at 11:51 AM, Mick  wrote:
> On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote:
>> On Wed, Dec 20, 2017 at 9:26 AM, Mick  wrote:
>
>> > You are quite right, there is no firmware_install in the 4.14.7 release.
>> > What does this mean?  How are we meant to install firmware now?
>>
>> I believe all firmware has been removed from the kernel sources.
>>
>> You should install sys-kernel/linux-firmware, or grab just the files
>> you need from the git repo.
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
>
> Thank you all, but I see to have a mental disconnect here:
>
> I already have sys-kernel/linux-firmware-20170314 installed.
>
> I have specified in the kernel which blobs I need and /lib/firmware/ as the
> path for the kernel to find any firmware it may need.
>
> I used to run make firmware_install and the kernel was able to load whatever
> firmware I had specified so that CPU/GPU can function properly at boot time.
>
> With 4.14.7 I (can) no longer do this;
>
> AND
>
> the newly compiled kernel does not load at boot time any of the needed
> firmware.
>
> 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?

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mick 
On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote:
> On Wed, Dec 20, 2017 at 9:26 AM, Mick  wrote:

> > You are quite right, there is no firmware_install in the 4.14.7 release. 
> > What does this mean?  How are we meant to install firmware now?
> 
> I believe all firmware has been removed from the kernel sources.
> 
> You should install sys-kernel/linux-firmware, or grab just the files
> you need from the git repo.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

Thank you all, but I see to have a mental disconnect here:

I already have sys-kernel/linux-firmware-20170314 installed.

I have specified in the kernel which blobs I need and /lib/firmware/ as the 
path for the kernel to find any firmware it may need.

I used to run make firmware_install and the kernel was able to load whatever 
firmware I had specified so that CPU/GPU can function properly at boot time.

With 4.14.7 I (can) no longer do this;

AND

the newly compiled kernel does not load at boot time any of the needed 
firmware.

What step am I missing to arrive at a bootable kernel with all necessary 
firmware?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mike Gilbert 
On Wed, Dec 20, 2017 at 9:26 AM, Mick  wrote:
> On Wednesday, 20 December 2017 12:52:16 GMT Floyd Anderson wrote:
>> On Wed, 20 Dec 2017 12:22:29 +
>>
>> Mick  wrote:
>> >Has something changed in 4.14.7-gentoo sources from its predecessors?
>> >
>> >I'm getting this on two systems:
>> >
>> >[snip ...]
>> >
>> >  INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko
>> >  INSTALL sound/pci/hda/snd-hda-codec.ko
>> >  INSTALL sound/pci/hda/snd-hda-intel.ko
>> >  DEPMOD  4.14.7-gentoo
>> >
>> >make: *** No rule to make target 'firmware_install'.  Stop.
>>
>> Yes, there is a change to drop the target rule ‘firmware_install’ [1].
>> I’ve noticed also [2] but in the end it seems the rule is finally
>> dropped:
>>
>>   /usr/src/linux-4.12.12-gentoo/scripts/Makefile.fwinst...  exists
>>   /usr/src/linux-4.14.4-gentoo/scripts/Makefile.fwinst ...  no such file
>>
>> To check it’s there look for ‘Other generic targets’ in kernel dir:
>>
>> sudo make help
>>
>> or just grep:
>>
>> grep -q 'firmware_install' /usr/src/linux/Makefile
>>
>>
>> References:
>>   - [1] 
>>   - [2] 
>
> You are quite right, there is no firmware_install in the 4.14.7 release.  What
> does this mean?  How are we meant to install firmware now?

I believe all firmware has been removed from the kernel sources.

You should install sys-kernel/linux-firmware, or grab just the files
you need from the git repo.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mick 
On Wednesday, 20 December 2017 15:28:03 GMT Peter Humphrey wrote:
> On Wednesday, 20 December 2017 12:22:29 GMT Mick wrote:
> > Has something changed in 4.14.7-gentoo sources from its predecessors?
[snip ...]

> What firmware are you trying to install? This box needs firmware for the
> graphics card and the Intel CPU, and I've been declaring the file names in
> CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR. As the display works
> fine, and so does opencl on the GPU since I emerged dev-libs/amdgpu-pro-
> opencl, I assume that the firmware is being loaded. I didn't even know about
> a firmware_install make target.

Thanks Peter,

I am also declaring relevant firmware in the kernel for CPU microcode and GPU, 
but they do not get loaded when I build kernel 4.14.7:

$ grep FIRMWARE /usr/src/linux/.config
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin radeon/
RV730_smc.bin radeon/RV710_uvd.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
# CONFIG_CYPRESS_FIRMWARE is not set
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_FIRMWARE_EDID=y
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_GOOGLE_FIRMWARE is not set
# CONFIG_TEST_FIRMWARE is not set

So I can't load a desktop because xserver will not launch.  I also recall 
having additional firmware for WiFi/BT cards on this laptop.

The same problem exists on other systems, some running AMD.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Peter Humphrey 
On Wednesday, 20 December 2017 12:22:29 GMT Mick wrote:
> Has something changed in 4.14.7-gentoo sources from its predecessors?
> 
> I'm getting this on two systems:
> 
> [snip ...]
>   INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko
>   INSTALL sound/pci/hda/snd-hda-codec.ko
>   INSTALL sound/pci/hda/snd-hda-intel.ko
>   DEPMOD  4.14.7-gentoo
> make: *** No rule to make target 'firmware_install'.  Stop.

What firmware are you trying to install? This box needs firmware for the 
graphics card and the Intel CPU, and I've been declaring the file names in 
CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR. As the display works 
fine, and so does opencl on the GPU since I emerged dev-libs/amdgpu-pro-
opencl, I assume that the firmware is being loaded. I didn't even know about 
a firmware_install make target.

-- 
Regards,
Peter.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mick 
On Wednesday, 20 December 2017 12:52:16 GMT Floyd Anderson wrote:
> On Wed, 20 Dec 2017 12:22:29 +
> 
> Mick  wrote:
> >Has something changed in 4.14.7-gentoo sources from its predecessors?
> >
> >I'm getting this on two systems:
> >
> >[snip ...]
> >
> >  INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko
> >  INSTALL sound/pci/hda/snd-hda-codec.ko
> >  INSTALL sound/pci/hda/snd-hda-intel.ko
> >  DEPMOD  4.14.7-gentoo
> >
> >make: *** No rule to make target 'firmware_install'.  Stop.
> 
> Yes, there is a change to drop the target rule ‘firmware_install’ [1].
> I’ve noticed also [2] but in the end it seems the rule is finally
> dropped:
> 
>   /usr/src/linux-4.12.12-gentoo/scripts/Makefile.fwinst...  exists
>   /usr/src/linux-4.14.4-gentoo/scripts/Makefile.fwinst ...  no such file
> 
> To check it’s there look for ‘Other generic targets’ in kernel dir:
> 
> sudo make help
> 
> or just grep:
> 
> grep -q 'firmware_install' /usr/src/linux/Makefile
> 
> 
> References:
>   - [1] 
>   - [2] 

You are quite right, there is no firmware_install in the 4.14.7 release.  What 
does this mean?  How are we meant to install firmware now?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Floyd Anderson 

On Wed, 20 Dec 2017 12:22:29 +
Mick  wrote:

Has something changed in 4.14.7-gentoo sources from its predecessors?

I'm getting this on two systems:

[snip ...]
 INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko
 INSTALL sound/pci/hda/snd-hda-codec.ko
 INSTALL sound/pci/hda/snd-hda-intel.ko
 DEPMOD  4.14.7-gentoo
make: *** No rule to make target 'firmware_install'.  Stop.


Yes, there is a change to drop the target rule ‘firmware_install’ [1]. 
I’ve noticed also [2] but in the end it seems the rule is finally 
dropped:


 /usr/src/linux-4.12.12-gentoo/scripts/Makefile.fwinst...  exists
 /usr/src/linux-4.14.4-gentoo/scripts/Makefile.fwinst ...  no such file 


To check it’s there look for ‘Other generic targets’ in kernel dir:

   sudo make help

or just grep:

   grep -q 'firmware_install' /usr/src/linux/Makefile


References:
 - [1] 
 - [2] 


--
Regards,
floyd

[gentoo-user] 'firmware_install' won't on 4.14.7-gentoo

2017-12-20 Thread Mick 
Has something changed in 4.14.7-gentoo sources from its predecessors?

I'm getting this on two systems:  

[snip ...]
  INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko
  INSTALL sound/pci/hda/snd-hda-codec.ko
  INSTALL sound/pci/hda/snd-hda-intel.ko
  DEPMOD  4.14.7-gentoo
make: *** No rule to make target 'firmware_install'.  Stop.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.